Home » The PARIS Forums » PARIS: Main » OT MIDI HELL or MOTU IS USELESS
| OT MIDI HELL or MOTU IS USELESS [message #64921] |
Fri, 24 February 2006 21:27  |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_006B_01C639A2.497976A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
This is after over a week of Midi Hell. I am fairly well
versed with midi as a whole. This has been far less pleasant
than my first day with multi-timberal synths, controllers, editors,
computers, midi merging, SMPTE to Midi Song Pointer and=20
no information to start with.
Problem #1:
After not being able to transmit sysex from my Amiga
to my TX7s without it 'taking out' the Motu 8x8 patch bay
and crashing Windows into an auto restart from black screen
I loaded FM Alive. This allows the PC (instead of Amiga)
to send this sysex data. Well the problems didn't go away,they
just changed. FM Alive was getting long sysex messages that made=20
no sense. It would work at editing the synths but irrelevant data=20
was constantly being seen to the program. I disconnected all midi=20
connections from the Motu 8x8 and STILL USB-MIDI data was being seen. =20
Cubase wasn't open. I have not been beaten.
I decided to try my original concept of using this Motu 8x8
as a stand alone and program a few presets, disconnect
the USB, reinstall my Fastlane 2x2 and hook it up the=20
old fashioned way. Midi in/out of Cubase through
Fastlane to one input/output of Motu 8x8 then routed
to all ins/outs of hardware synths. Piece of cake so I thought.=20
Now to dig up the drivers for the FastLane again... I loaded what=20
I thought were the right ones but they weren't. They were for the com =
port.
Okay, so I download the newest ones from Motu's site. I bring
them into the computer to realize minus Clockworks they are
the exact same drivers that were already in there for the 8x8. Well
the 8x8 wasn't working flawlessly so I thought I'd 'remove'
then 'reinstall' them just to be safe. After the reinstall, the
directions are to plug in the device (USB cable) and Windows should=20
recognize the new hardware. The only thing that was recognized was the=20
smell of burning components. I quickly shut down two computers to
find out that the green FastLane smoked!
This is the final straw. =20
Drivers from Motu are flakey as hell.
I swear they sent a higher than normal voltage down the USB=20
line somehow. =20
I now need a new small in/out box (2x2) and a stand alone 8x8=20
that works and merges without Fn drivers.
What is there?
The "sick of it all" guy,
Tom
PS Midi is still cool. Motu is not.
------=_NextPart_000_006B_01C639A2.497976A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>This is after =
over a week=20
of Midi Hell. I am fairly well</FONT></DIV>
<DIV><FONT size=3D2><FONT face=3D"Comic Sans MS"><FONT =
color=3D#800000>versed with=20
midi as a whole. This has been <FONT size=3D3>far less=20
pleasant</FONT></FONT></FONT></FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>than my first =
day with=20
multi-timberal synths, controllers, editors,</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>computers, =
midi=20
merging, SMPTE to Midi Song Pointer and </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>no =
</FONT><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>information to start=20
with.</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>Problem =
#1:</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>After not =
being able to=20
transmit sysex from my Amiga</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>to my TX7s =
without it=20
'taking out' the Motu 8x8 patch bay</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>and crashing =
Windows into=20
an auto restart from black screen</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>I loaded FM =
Alive. =20
This allows the PC (instead of Amiga)</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>to send this =
sysex=20
data. Well the problems didn't go away,they</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>just =
changed. FM=20
Alive </FONT><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>was =
getting long=20
sysex messages that made </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>no =
sense. It would=20
</FONT><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>work at =
editing the=20
synths but irrelevant data </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>was =
constantly being=20
seen to the program. </FONT><FONT face=3D"Comic Sans MS" =
color=3D#800000=20
size=3D2>I disconnected all midi </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>connections =
from the Motu=20
8x8 and </FONT><FONT face=3D"Comic Sans MS" color=3D#800000 =
size=3D2>STILL USB-MIDI=20
data was being seen. </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>Cubase wasn't =
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I have not been beaten.</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>I decided to =
try my=20
original concept of using this Motu 8x8</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>as a stand =
alone and=20
program a few presets, disconnect</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>the USB, =
reinstall my=20
Fastlane 2x2 and hook it up the </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>old fashioned =
way. =20
Midi in/out of Cubase through</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>Fastlane to =
one=20
input/output of Motu 8x8 then routed</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>to all =
ins/outs of hardware=20
synths. Piece of cake so I thought. </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2> Now to =
dig=20
</FONT><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>up the =
drivers for the=20
FastLane again... I loaded what </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>I =
</FONT><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>thought were the right =
ones but they=20
weren't. They were for the com port.</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>Okay, so I =
</FONT><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>download the newest ones =
from Motu's=20
site. I bring</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>them into the =
computer to=20
realize minus Clockworks they are</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>the exact =
same drivers that=20
were already in there for the 8x8. Well</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>the 8x8 =
wasn't working=20
flawlessly so I thought I'd 'remove'</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>then =
'reinstall' them just=20
to be safe. After the reinstall, the</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>directions =
are to plug in=20
the device (USB cable) and Windows should </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>recognize the =
new=20
hardware. The only thing that was recognized was the </FONT></DIV>
<DIV><FONT size=3D2><FONT face=3D"Comic Sans MS"><FONT =
color=3D#800000><FONT=20
size=3D3>smell of burning components.</FONT> I quickly shut down =
two=20
computers to</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3D"Comic Sans MS"><FONT =
color=3D#800000>find out that=20
<FONT size=3D3>the green FastLane =
smoked!</FONT></FONT></FONT></FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>This is the =
final=20
straw. </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>Drivers from =
Motu are=20
flakey as hell.</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>I swear they =
sent a higher=20
than normal voltage down the USB </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>line =
somehow. =20
</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>I now need a =
new small=20
in/out box (2x2) and a stand alone 8x8 </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>that works =
</FONT><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>and merges without Fn=20
drivers.</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>What is =
there?</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000></FONT> </DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2>The "sick of =
it all"=20
guy,</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 =
size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000></FONT> </DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000>PS Midi is still =
cool. Motu=20
is not.</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS" color=3D#800000 size=3D2> =20
</FONT></DIV></FONT></DIV></BODY></HTML>
------=_NextPart_000_006B_01C639A2.497976A0--
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64928 is a reply to message #64921] |
Sat, 25 February 2006 01:06  |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
i had to switch to m-audio when i couldn't get my M24 controller to
work.
On Sat, 25 Feb 2006 00:27:40 -0500, "Tom Bruhl" <arpegio@comcast.net>
wrote:
>This is after over a week of Midi Hell. I am fairly well
>versed with midi as a whole. This has been far less pleasant
>than my first day with multi-timberal synths, controllers, editors,
>computers, midi merging, SMPTE to Midi Song Pointer and
>no information to start with.
>
>Problem #1:
>After not being able to transmit sysex from my Amiga
>to my TX7s without it 'taking out' the Motu 8x8 patch bay
>and crashing Windows into an auto restart from black screen
>I loaded FM Alive. This allows the PC (instead of Amiga)
>to send this sysex data. Well the problems didn't go away,they
>just changed. FM Alive was getting long sysex messages that made
>no sense. It would work at editing the synths but irrelevant data
>was constantly being seen to the program. I disconnected all midi
>connections from the Motu 8x8 and STILL USB-MIDI data was being seen.
>Cubase wasn't open. I have not been beaten.
>
>I decided to try my original concept of using this Motu 8x8
>as a stand alone and program a few presets, disconnect
>the USB, reinstall my Fastlane 2x2 and hook it up the
>old fashioned way. Midi in/out of Cubase through
>Fastlane to one input/output of Motu 8x8 then routed
>to all ins/outs of hardware synths. Piece of cake so I thought.
>
> Now to dig up the drivers for the FastLane again... I loaded what
>I thought were the right ones but they weren't. They were for the com port.
>Okay, so I download the newest ones from Motu's site. I bring
>them into the computer to realize minus Clockworks they are
>the exact same drivers that were already in there for the 8x8. Well
>the 8x8 wasn't working flawlessly so I thought I'd 'remove'
>then 'reinstall' them just to be safe. After the reinstall, the
>directions are to plug in the device (USB cable) and Windows should
>recognize the new hardware. The only thing that was recognized was the
>smell of burning components. I quickly shut down two computers to
>find out that the green FastLane smoked!
>This is the final straw.
>
>Drivers from Motu are flakey as hell.
>I swear they sent a higher than normal voltage down the USB
>line somehow.
>
>I now need a new small in/out box (2x2) and a stand alone 8x8
>that works and merges without Fn drivers.
>What is there?
>
>The "sick of it all" guy,
>Tom
>
>PS Midi is still cool. Motu is not.
>
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64937 is a reply to message #64921] |
Sat, 25 February 2006 08:29 |
Chris Ludwig
Messages: 868
Registered: May 2006
|
Senior Member |
|
|
Hi Tom,
Sadly a common MOTU experience. The M-Audio stuff has always worked for
me as well as the Edirol stuff.
Does your sound card have midi ports on it? I couldn't find a mention
which it is you have.
Hopefully the MOTU didn't damage your on board USB ports!!
Chris
Tom Bruhl wrote:
> This is after over a week of Midi Hell. I am fairly well
> versed with midi as a whole. This has been far less pleasant
> than my first day with multi-timberal synths, controllers, editors,
> computers, midi merging, SMPTE to Midi Song Pointer and
> no information to start with.
>
> Problem #1:
> After not being able to transmit sysex from my Amiga
> to my TX7s without it 'taking out' the Motu 8x8 patch bay
> and crashing Windows into an auto restart from black screen
> I loaded FM Alive. This allows the PC (instead of Amiga)
> to send this sysex data. Well the problems didn't go away,they
> just changed. FM Alive was getting long sysex messages that made
> no sense. It would work at editing the synths but irrelevant data
> was constantly being seen to the program. I disconnected all midi
> connections from the Motu 8x8 and STILL USB-MIDI data was being seen.
> Cubase wasn't open. I have not been beaten.
>
> I decided to try my original concept of using this Motu 8x8
> as a stand alone and program a few presets, disconnect
> the USB, reinstall my Fastlane 2x2 and hook it up the
> old fashioned way. Midi in/out of Cubase through
> Fastlane to one input/output of Motu 8x8 then routed
> to all ins/outs of hardware synths. Piece of cake so I thought.
>
> Now to dig up the drivers for the FastLane again... I loaded what
> I thought were the right ones but they weren't. They were for the com port.
> Okay, so I download the newest ones from Motu's site. I bring
> them into the computer to realize minus Clockworks they are
> the exact same drivers that were already in there for the 8x8. Well
> the 8x8 wasn't working flawlessly so I thought I'd 'remove'
> then 'reinstall' them just to be safe. After the reinstall, the
> directions are to plug in the device (USB cable) and Windows should
> recognize the new hardware. The only thing that was recognized was the
> smell of burning components. I quickly shut down two computers to
> find out that the green FastLane smoked!
> This is the final straw.
>
> Drivers from Motu are flakey as hell.
> I swear they sent a higher than normal voltage down the USB
> line somehow.
>
> I now need a new small in/out box (2x2) and a stand alone 8x8
> that works and merges without Fn drivers.
> What is there?
>
> The "sick of it all" guy,
> Tom
>
> PS Midi is still cool. Motu is not.
>
--
Chris Ludwig
ADK
chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
www.adkproaudio.com <http://www.adkproaudio.com/>
(859) 635-5762
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64946 is a reply to message #64937] |
Sat, 25 February 2006 11:48 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
it does seem to work with the HUI.
On Sat, 25 Feb 2006 11:29:52 -0500, Chris Ludwig
<chrisl@adkproaudio.com> wrote:
>Hi Tom,
>Sadly a common MOTU experience. The M-Audio stuff has always worked for
>me as well as the Edirol stuff.
>Does your sound card have midi ports on it? I couldn't find a mention
>which it is you have.
>Hopefully the MOTU didn't damage your on board USB ports!!
>
>Chris
>
>Tom Bruhl wrote:
>
>> This is after over a week of Midi Hell. I am fairly well
>> versed with midi as a whole. This has been far less pleasant
>> than my first day with multi-timberal synths, controllers, editors,
>> computers, midi merging, SMPTE to Midi Song Pointer and
>> no information to start with.
>>
>> Problem #1:
>> After not being able to transmit sysex from my Amiga
>> to my TX7s without it 'taking out' the Motu 8x8 patch bay
>> and crashing Windows into an auto restart from black screen
>> I loaded FM Alive. This allows the PC (instead of Amiga)
>> to send this sysex data. Well the problems didn't go away,they
>> just changed. FM Alive was getting long sysex messages that made
>> no sense. It would work at editing the synths but irrelevant data
>> was constantly being seen to the program. I disconnected all midi
>> connections from the Motu 8x8 and STILL USB-MIDI data was being seen.
>> Cubase wasn't open. I have not been beaten.
>>
>> I decided to try my original concept of using this Motu 8x8
>> as a stand alone and program a few presets, disconnect
>> the USB, reinstall my Fastlane 2x2 and hook it up the
>> old fashioned way. Midi in/out of Cubase through
>> Fastlane to one input/output of Motu 8x8 then routed
>> to all ins/outs of hardware synths. Piece of cake so I thought.
>>
>> Now to dig up the drivers for the FastLane again... I loaded what
>> I thought were the right ones but they weren't. They were for the com port.
>> Okay, so I download the newest ones from Motu's site. I bring
>> them into the computer to realize minus Clockworks they are
>> the exact same drivers that were already in there for the 8x8. Well
>> the 8x8 wasn't working flawlessly so I thought I'd 'remove'
>> then 'reinstall' them just to be safe. After the reinstall, the
>> directions are to plug in the device (USB cable) and Windows should
>> recognize the new hardware. The only thing that was recognized was the
>> smell of burning components. I quickly shut down two computers to
>> find out that the green FastLane smoked!
>> This is the final straw.
>>
>> Drivers from Motu are flakey as hell.
>> I swear they sent a higher than normal voltage down the USB
>> line somehow.
>>
>> I now need a new small in/out box (2x2) and a stand alone 8x8
>> that works and merges without Fn drivers.
>> What is there?
>>
>> The "sick of it all" guy,
>> Tom
>>
>> PS Midi is still cool. Motu is not.
>>
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64948 is a reply to message #64937] |
Sat, 25 February 2006 14:40 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0164_01C63A32.9CD10E40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Chris,
No midi on the Delta 66 but that's soon to be gone as
is the whole computer during the summer. I plan
to get an RME with ADAT and midi interfaces. I will
still need the 8x8 though.
It's between emagic unitor 8, MidiSport 8x8 or
Edirol UM 880.
Anyone like these?
Tom
"Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =
news:44008766@linux...
Hi Tom,
Sadly a common MOTU experience. The M-Audio stuff has always worked =
for=20
me as well as the Edirol stuff.
Does your sound card have midi ports on it? I couldn't find a mention=20
which it is you have.
Hopefully the MOTU didn't damage your on board USB ports!!
Chris
Tom Bruhl wrote:
> This is after over a week of Midi Hell. I am fairly well
> versed with midi as a whole. This has been far less pleasant
> than my first day with multi-timberal synths, controllers, editors,
> computers, midi merging, SMPTE to Midi Song Pointer and
> no information to start with.
> =20
> Problem #1:
> After not being able to transmit sysex from my Amiga
> to my TX7s without it 'taking out' the Motu 8x8 patch bay
> and crashing Windows into an auto restart from black screen
> I loaded FM Alive. This allows the PC (instead of Amiga)
> to send this sysex data. Well the problems didn't go away,they
> just changed. FM Alive was getting long sysex messages that made
> no sense. It would work at editing the synths but irrelevant data
> was constantly being seen to the program. I disconnected all midi
> connections from the Motu 8x8 and STILL USB-MIDI data was being =
seen.=20
> Cubase wasn't open. I have not been beaten.
> =20
> I decided to try my original concept of using this Motu 8x8
> as a stand alone and program a few presets, disconnect
> the USB, reinstall my Fastlane 2x2 and hook it up the
> old fashioned way. Midi in/out of Cubase through
> Fastlane to one input/output of Motu 8x8 then routed
> to all ins/outs of hardware synths. Piece of cake so I thought.=20
> =20
> Now to dig up the drivers for the FastLane again... I loaded what
> I thought were the right ones but they weren't. They were for the =
com port.
> Okay, so I download the newest ones from Motu's site. I bring
> them into the computer to realize minus Clockworks they are
> the exact same drivers that were already in there for the 8x8. Well
> the 8x8 wasn't working flawlessly so I thought I'd 'remove'
> then 'reinstall' them just to be safe. After the reinstall, the
> directions are to plug in the device (USB cable) and Windows should
> recognize the new hardware. The only thing that was recognized was =
the
> smell of burning components. I quickly shut down two computers to
> find out that the green FastLane smoked!
> This is the final straw.=20
> =20
> Drivers from Motu are flakey as hell.
> I swear they sent a higher than normal voltage down the USB
> line somehow.=20
> =20
> I now need a new small in/out box (2x2) and a stand alone 8x8
> that works and merges without Fn drivers.
> What is there?
> =20
> The "sick of it all" guy,
> Tom
> =20
> PS Midi is still cool. Motu is not.
> =20
--=20
Chris Ludwig
ADK
chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
www.adkproaudio.com <http://www.adkproaudio.com/>
(859) 635-5762
------=_NextPart_000_0164_01C63A32.9CD10E40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Chris,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>No midi on the Delta 66 but that's soon =
to be gone=20
as</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is the whole computer during the =
summer. I=20
plan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to get an RME with ADAT and midi =
interfaces. =20
I will</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>still need the 8x8 though.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It's between </FONT>emagic unitor 8, =
MidiSport 8x8=20
or</DIV>
<DIV>Edirol UM 880.</DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyone like these?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Chris Ludwig" <<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
wrote in=20
message <A =
href=3D"news:44008766@linux">news:44008766@linux</A>...</DIV>Hi=20
Tom,<BR>Sadly a common MOTU experience. The M-Audio stuff has always =
worked=20
for <BR>me as well as the Edirol stuff.<BR>Does your sound card have =
midi=20
ports on it? I couldn't find a mention <BR>which it is you =
have.<BR>Hopefully=20
the MOTU didn't damage your on board USB =
ports!!<BR><BR>Chris<BR><BR>Tom Bruhl=20
wrote:<BR><BR>> This is after over a week of Midi Hell. I am =
fairly=20
well<BR>> versed with midi as a whole. This has been far less =
pleasant<BR>> than my first day with multi-timberal synths, =
controllers,=20
editors,<BR>> computers, midi merging, SMPTE to Midi Song Pointer=20
and<BR>> no information to start with.<BR>> <BR>> =
Problem=20
#1:<BR>> After not being able to transmit sysex from my =
Amiga<BR>> to my=20
TX7s without it 'taking out' the Motu 8x8 patch bay<BR>> and =
crashing=20
Windows into an auto restart from black screen<BR>> I loaded FM=20
Alive. This allows the PC (instead of Amiga)<BR>> to send =
this sysex=20
data. Well the problems didn't go away,they<BR>> just =
changed. =20
FM Alive was getting long sysex messages that made<BR>> no =
sense. It=20
would work at editing the synths but irrelevant data<BR>> was =
constantly=20
being seen to the program. I disconnected all midi<BR>> =
connections=20
from the Motu 8x8 and STILL USB-MIDI data was being seen. <BR>> =
Cubase=20
wasn't=20
=
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I have not been beaten.<BR>> <BR>> I decided to try my =
original=20
concept of using this Motu 8x8<BR>> as a stand alone and program a =
few=20
presets, disconnect<BR>> the USB, reinstall my Fastlane 2x2 and =
hook it up=20
the<BR>> old fashioned way. Midi in/out of Cubase =
through<BR>>=20
Fastlane to one input/output of Motu 8x8 then routed<BR>> to all =
ins/outs=20
of hardware synths. Piece of cake so I thought. <BR>> =20
<BR>> Now to dig up the drivers for the FastLane again... I =
loaded=20
what<BR>> I thought were the right ones but they weren't. =
They were=20
for the com port.<BR>> Okay, so I download the newest ones from =
Motu's=20
site. I bring<BR>> them into the computer to realize minus =
Clockworks=20
they are<BR>> the exact same drivers that were already in there for =
the=20
8x8. Well<BR>> the 8x8 wasn't working flawlessly so I thought =
I'd=20
'remove'<BR>> then 'reinstall' them just to be safe. After =
the=20
reinstall, the<BR>> directions are to plug in the device (USB =
cable) and=20
Windows should<BR>> recognize the new hardware. The only =
thing that=20
was recognized was the<BR>> smell of burning components. I =
quickly=20
shut down two computers to<BR>> find out that the green FastLane=20
smoked!<BR>> This is the final straw. <BR>> <BR>> =
Drivers from=20
Motu are flakey as hell.<BR>> I swear they sent a higher than =
normal=20
voltage down the USB<BR>> line somehow. <BR>> <BR>> I =
now need=20
a new small in/out box (2x2) and a stand alone 8x8<BR>> that works =
and=20
merges without Fn drivers.<BR>> What is there?<BR>> =
<BR>> The=20
"sick of it all" guy,<BR>> Tom<BR>> <BR>> PS Midi is =
still=20
cool. Motu is not.<BR>> <BR><BR>-- <BR>Chris=20
Ludwig<BR>ADK<BR><A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR><A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>(859)=20
635-5762</BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0164_01C63A32.9CD10E40--
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64960 is a reply to message #64948] |
Sat, 25 February 2006 23:03 |
Chris Ludwig
Messages: 868
Registered: May 2006
|
Senior Member |
|
|
Hi Tom,
The would shoot for the M-Audio or Edirol. The Emagic PC driver
development/support is non existent.
Chris
Tom Bruhl wrote:
> Chris,
> No midi on the Delta 66 but that's soon to be gone as
> is the whole computer during the summer. I plan
> to get an RME with ADAT and midi interfaces. I will
> still need the 8x8 though.
>
> It's between emagic unitor 8, MidiSport 8x8 or
> Edirol UM 880.
>
> Anyone like these?
> Tom
>
>
>
> "Chris Ludwig" <chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com>> wrote in message news:44008766@linux...
> Hi Tom,
> Sadly a common MOTU experience. The M-Audio stuff has always worked for
> me as well as the Edirol stuff.
> Does your sound card have midi ports on it? I couldn't find a mention
> which it is you have.
> Hopefully the MOTU didn't damage your on board USB ports!!
>
> Chris
>
> Tom Bruhl wrote:
>
> > This is after over a week of Midi Hell. I am fairly well
> > versed with midi as a whole. This has been far less pleasant
> > than my first day with multi-timberal synths, controllers, editors,
> > computers, midi merging, SMPTE to Midi Song Pointer and
> > no information to start with.
> >
> > Problem #1:
> > After not being able to transmit sysex from my Amiga
> > to my TX7s without it 'taking out' the Motu 8x8 patch bay
> > and crashing Windows into an auto restart from black screen
> > I loaded FM Alive. This allows the PC (instead of Amiga)
> > to send this sysex data. Well the problems didn't go away,they
> > just changed. FM Alive was getting long sysex messages that made
> > no sense. It would work at editing the synths but irrelevant data
> > was constantly being seen to the program. I disconnected all midi
> > connections from the Motu 8x8 and STILL USB-MIDI data was being
> seen.
> > Cubase wasn't open. I have not been beaten.
> >
> > I decided to try my original concept of using this Motu 8x8
> > as a stand alone and program a few presets, disconnect
> > the USB, reinstall my Fastlane 2x2 and hook it up the
> > old fashioned way. Midi in/out of Cubase through
> > Fastlane to one input/output of Motu 8x8 then routed
> > to all ins/outs of hardware synths. Piece of cake so I thought.
> >
> > Now to dig up the drivers for the FastLane again... I loaded what
> > I thought were the right ones but they weren't. They were for
> the com port.
> > Okay, so I download the newest ones from Motu's site. I bring
> > them into the computer to realize minus Clockworks they are
> > the exact same drivers that were already in there for the 8x8. Well
> > the 8x8 wasn't working flawlessly so I thought I'd 'remove'
> > then 'reinstall' them just to be safe. After the reinstall, the
> > directions are to plug in the device (USB cable) and Windows should
> > recognize the new hardware. The only thing that was recognized
> was the
> > smell of burning components. I quickly shut down two computers to
> > find out that the green FastLane smoked!
> > This is the final straw.
> >
> > Drivers from Motu are flakey as hell.
> > I swear they sent a higher than normal voltage down the USB
> > line somehow.
> >
> > I now need a new small in/out box (2x2) and a stand alone 8x8
> > that works and merges without Fn drivers.
> > What is there?
> >
> > The "sick of it all" guy,
> > Tom
> >
> > PS Midi is still cool. Motu is not.
> >
>
> --
> Chris Ludwig
> ADK
> chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> <mailto:chrisl@adkproaudio.com>
> www.adkproaudio.com <http://www.adkproaudio.com>
> <http://www.adkproaudio.com/>
> (859) 635-5762
--
Chris Ludwig
ADK
chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
www.adkproaudio.com <http://www.adkproaudio.com/>
(859) 635-5762
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64961 is a reply to message #64960] |
Sat, 25 February 2006 23:44 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0187_01C63A7E.951576E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I'm trying to avoid drivers at all costs.
Midi in/out sounds far more stable to me.
I want a stand alone box.
USB/MIDI =3D Extra unknown sysex data
Computer crashes
Smoked hardware
Midi Communication loss
7 days of lost revenue
or is that just Motu?
"Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =
news:44015426@linux...
Hi Tom,
The would shoot for the M-Audio or Edirol. The Emagic PC driver=20
development/support is non existent.
Chris
Tom Bruhl wrote:
> Chris,
> No midi on the Delta 66 but that's soon to be gone as
> is the whole computer during the summer. I plan
> to get an RME with ADAT and midi interfaces. I will
> still need the 8x8 though.
> =20
> It's between emagic unitor 8, MidiSport 8x8 or
> Edirol UM 880.
> =20
> Anyone like these?
> Tom
> =20
> =20
>=20
> "Chris Ludwig" <chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com>> wrote in message =
news:44008766@linux...
> Hi Tom,
> Sadly a common MOTU experience. The M-Audio stuff has always =
worked for
> me as well as the Edirol stuff.
> Does your sound card have midi ports on it? I couldn't find a =
mention
> which it is you have.
> Hopefully the MOTU didn't damage your on board USB ports!!
>=20
> Chris
>=20
> Tom Bruhl wrote:
>=20
> > This is after over a week of Midi Hell. I am fairly well
> > versed with midi as a whole. This has been far less pleasant
> > than my first day with multi-timberal synths, controllers, =
editors,
> > computers, midi merging, SMPTE to Midi Song Pointer and
> > no information to start with.
> >=20
> > Problem #1:
> > After not being able to transmit sysex from my Amiga
> > to my TX7s without it 'taking out' the Motu 8x8 patch bay
> > and crashing Windows into an auto restart from black screen
> > I loaded FM Alive. This allows the PC (instead of Amiga)
> > to send this sysex data. Well the problems didn't go =
away,they
> > just changed. FM Alive was getting long sysex messages that =
made
> > no sense. It would work at editing the synths but irrelevant =
data
> > was constantly being seen to the program. I disconnected all =
midi
> > connections from the Motu 8x8 and STILL USB-MIDI data was =
being
> seen.
> > Cubase wasn't open. I have not been =
beaten.
> >=20
> > I decided to try my original concept of using this Motu 8x8
> > as a stand alone and program a few presets, disconnect
> > the USB, reinstall my Fastlane 2x2 and hook it up the
> > old fashioned way. Midi in/out of Cubase through
> > Fastlane to one input/output of Motu 8x8 then routed
> > to all ins/outs of hardware synths. Piece of cake so I =
thought.
> >=20
> > Now to dig up the drivers for the FastLane again... I loaded =
what
> > I thought were the right ones but they weren't. They were =
for
> the com port.
> > Okay, so I download the newest ones from Motu's site. I =
bring
> > them into the computer to realize minus Clockworks they are
> > the exact same drivers that were already in there for the =
8x8. Well
> > the 8x8 wasn't working flawlessly so I thought I'd 'remove'
> > then 'reinstall' them just to be safe. After the reinstall, =
the
> > directions are to plug in the device (USB cable) and Windows =
should
> > recognize the new hardware. The only thing that was =
recognized
> was the
> > smell of burning components. I quickly shut down two =
computers to
> > find out that the green FastLane smoked!
> > This is the final straw.
> >=20
> > Drivers from Motu are flakey as hell.
> > I swear they sent a higher than normal voltage down the USB
> > line somehow.
> >=20
> > I now need a new small in/out box (2x2) and a stand alone 8x8
> > that works and merges without Fn drivers.
> > What is there?
> >=20
> > The "sick of it all" guy,
> > Tom
> >=20
> > PS Midi is still cool. Motu is not.
> >=20
>=20
> --=20
> Chris Ludwig
> ADK
> chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> <mailto:chrisl@adkproaudio.com>
> www.adkproaudio.com <http://www.adkproaudio.com>
> <http://www.adkproaudio.com/>
> (859) 635-5762
--=20
Chris Ludwig
ADK
chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
www.adkproaudio.com <http://www.adkproaudio.com/>
(859) 635-5762
------=_NextPart_000_0187_01C63A7E.951576E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'm trying to avoid drivers at all=20
costs.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Midi in/out sounds far more stable to =
me.<BR>I want=20
a stand alone box.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>USB/MIDI =3D Extra unknown sysex=20
data</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p; &nbs p;=20
Computer crashes</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p; =20
Smoked hardware</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p; &nbs p; Midi=20
Communication loss</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p; &nbs p; =20
7 days of lost revenue</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>or is that just Motu?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Chris Ludwig" <<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
wrote in=20
message <A =
href=3D"news:44015426@linux">news:44015426@linux</A>...</DIV>Hi=20
Tom,<BR>The would shoot for the M-Audio or Edirol. The Emagic PC =
driver=20
<BR>development/support is non =
existent.<BR><BR><BR>Chris<BR><BR><BR>Tom Bruhl=20
wrote:<BR>> Chris,<BR>> No midi on the Delta 66 but that's soon =
to be=20
gone as<BR>> is the whole computer during the summer. I =
plan<BR>>=20
to get an RME with ADAT and midi interfaces. I will<BR>> =
still need=20
the 8x8 though.<BR>> <BR>> It's between emagic unitor 8, =
MidiSport=20
8x8 or<BR>> Edirol UM 880.<BR>> <BR>> Anyone like=20
these?<BR>> Tom<BR>> <BR>> <BR>>=20
<BR>> "Chris Ludwig" <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;>=20
wrote in message <A=20
=
href=3D"news:44008766@linux">news:44008766@linux</A>...<BR>> &nbs=
p; =20
Hi Tom,<BR>> Sadly a common MOTU =
experience. The=20
M-Audio stuff has always worked for<BR>> me =
as well=20
as the Edirol stuff.<BR>> Does your sound =
card have=20
midi ports on it? I couldn't find a =
mention<BR>> =20
which it is you have.<BR>> Hopefully the =
MOTU=20
didn't damage your on board USB ports!!<BR>>=20
<BR>> Chris<BR>>=20
<BR>> Tom Bruhl wrote:<BR>>=20
<BR>> > This is after over a week =
of Midi=20
Hell. I am fairly well<BR>> =
> versed=20
with midi as a whole. This has been far less=20
pleasant<BR>> > than my first day =
with=20
multi-timberal synths, controllers,=20
editors,<BR>> > computers, midi =
merging,=20
SMPTE to Midi Song Pointer and<BR>> =
> no=20
information to start with.<BR>> >=20
<BR>> > Problem=20
#1:<BR>> > After not being able to =
transmit sysex from my Amiga<BR>> =
> to my=20
TX7s without it 'taking out' the Motu 8x8 patch=20
bay<BR>> > and crashing Windows =
into an=20
auto restart from black screen<BR>> =
> I=20
loaded FM Alive. This allows the PC (instead of=20
Amiga)<BR>> > to send this sysex=20
data. Well the problems didn't go=20
away,they<BR>> > just =
changed. FM=20
Alive was getting long sysex messages that=20
made<BR>> > no sense. It =
would work=20
at editing the synths but irrelevant=20
data<BR>> > was constantly being =
seen to=20
the program. I disconnected all=20
midi<BR>> > connections from the =
Motu 8x8=20
and STILL USB-MIDI data was being<BR>> =20
seen.<BR>> > Cubase wasn't=20
=
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I have not been beaten.<BR>> >=20
<BR>> > I decided to try my =
original=20
concept of using this Motu 8x8<BR>> =
> as a=20
stand alone and program a few presets,=20
disconnect<BR>> > the USB, =
reinstall my=20
Fastlane 2x2 and hook it up the<BR>> =
> old=20
fashioned way. Midi in/out of Cubase=20
through<BR>> > Fastlane to one=20
input/output of Motu 8x8 then =
routed<BR> > =2 0
> to all ins/outs of hardware synths. Piece of cake so I=20
thought.<BR>> >=20
<BR>> > Now to dig up the =
drivers=20
for the FastLane again... I loaded =
what<BR> > =2 0
> I thought were the right ones but they weren't. They were=20
for<BR>> the com=20
port.<BR>> > Okay, so I download =
the=20
newest ones from Motu's site. I=20
bring<BR>> > them into the =
computer to=20
realize minus Clockworks they =
are<BR>> >=20
the exact same drivers that were already in there for the 8x8. =20
Well<BR>> > the 8x8 wasn't working =
flawlessly so I thought I'd =
'remove'<BR> > =2 0
> then 'reinstall' them just to be safe. After the reinstall, =
the<BR>> > directions are to plug =
in the=20
device (USB cable) and Windows =
should<BR> > =2 0
> recognize the new hardware. The only thing that was=20
recognized<BR>> was=20
the<BR>> > smell of burning=20
components. I quickly shut down two computers=20
to<BR>> > find out that the green =
FastLane=20
smoked!<BR>> > This is the final=20
straw.<BR>> >=20
<BR>> > Drivers from Motu are =
flakey as=20
hell.<BR>> > I swear they sent a =
higher=20
than normal voltage down the USB<BR>> =
>=20
line somehow.<BR>> >=20
<BR>> > I now need a new small =
in/out box=20
(2x2) and a stand alone 8x8<BR>> > =
that=20
works and merges without Fn =
drivers.<BR> > =2 0
> What is there?<BR>> >=20
<BR>> > The "sick of it all"=20
guy,<BR>> >=20
Tom<BR>> >=20
<BR>> > PS Midi is still =
cool. Motu=20
is not.<BR>> > <BR>>=20
<BR>> -- <BR>> =
Chris=20
Ludwig<BR>> =
ADK<BR>> <A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
<A href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
<<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
(859) 635-5762<BR><BR>-- <BR>Chris Ludwig<BR>ADK<BR><A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR><A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>(859)=20
635-5762</BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0187_01C63A7E.951576E0--
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64965 is a reply to message #64961] |
Sun, 26 February 2006 02:25 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
"I want a stand alone box." they still have drivers but i've not had
any problems with the m-audio stuff.
On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" <arpegio@comcast.net>
wrote:
>I'm trying to avoid drivers at all costs.
>Midi in/out sounds far more stable to me.
>I want a stand alone box.
>
>USB/MIDI = Extra unknown sysex data
> Computer crashes
> Smoked hardware
> Midi Communication loss
> 7 days of lost revenue
>
>or is that just Motu?
>
>
> "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message news:44015426@linux...
> Hi Tom,
> The would shoot for the M-Audio or Edirol. The Emagic PC driver
> development/support is non existent.
>
>
> Chris
>
>
> Tom Bruhl wrote:
> > Chris,
> > No midi on the Delta 66 but that's soon to be gone as
> > is the whole computer during the summer. I plan
> > to get an RME with ADAT and midi interfaces. I will
> > still need the 8x8 though.
> >
> > It's between emagic unitor 8, MidiSport 8x8 or
> > Edirol UM 880.
> >
> > Anyone like these?
> > Tom
> >
> >
> >
> > "Chris Ludwig" <chrisl@adkproaudio.com
> > <mailto:chrisl@adkproaudio.com>> wrote in message news:44008766@linux...
> > Hi Tom,
> > Sadly a common MOTU experience. The M-Audio stuff has always worked for
> > me as well as the Edirol stuff.
> > Does your sound card have midi ports on it? I couldn't find a mention
> > which it is you have.
> > Hopefully the MOTU didn't damage your on board USB ports!!
> >
> > Chris
> >
> > Tom Bruhl wrote:
> >
> > > This is after over a week of Midi Hell. I am fairly well
> > > versed with midi as a whole. This has been far less pleasant
> > > than my first day with multi-timberal synths, controllers, editors,
> > > computers, midi merging, SMPTE to Midi Song Pointer and
> > > no information to start with.
> > >
> > > Problem #1:
> > > After not being able to transmit sysex from my Amiga
> > > to my TX7s without it 'taking out' the Motu 8x8 patch bay
> > > and crashing Windows into an auto restart from black screen
> > > I loaded FM Alive. This allows the PC (instead of Amiga)
> > > to send this sysex data. Well the problems didn't go away,they
> > > just changed. FM Alive was getting long sysex messages that made
> > > no sense. It would work at editing the synths but irrelevant data
> > > was constantly being seen to the program. I disconnected all midi
> > > connections from the Motu 8x8 and STILL USB-MIDI data was being
> > seen.
> > > Cubase wasn't open. I have not been beaten.
> > >
> > > I decided to try my original concept of using this Motu 8x8
> > > as a stand alone and program a few presets, disconnect
> > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > old fashioned way. Midi in/out of Cubase through
> > > Fastlane to one input/output of Motu 8x8 then routed
> > > to all ins/outs of hardware synths. Piece of cake so I thought.
> > >
> > > Now to dig up the drivers for the FastLane again... I loaded what
> > > I thought were the right ones but they weren't. They were for
> > the com port.
> > > Okay, so I download the newest ones from Motu's site. I bring
> > > them into the computer to realize minus Clockworks they are
> > > the exact same drivers that were already in there for the 8x8. Well
> > > the 8x8 wasn't working flawlessly so I thought I'd 'remove'
> > > then 'reinstall' them just to be safe. After the reinstall, the
> > > directions are to plug in the device (USB cable) and Windows should
> > > recognize the new hardware. The only thing that was recognized
> > was the
> > > smell of burning components. I quickly shut down two computers to
> > > find out that the green FastLane smoked!
> > > This is the final straw.
> > >
> > > Drivers from Motu are flakey as hell.
> > > I swear they sent a higher than normal voltage down the USB
> > > line somehow.
> > >
> > > I now need a new small in/out box (2x2) and a stand alone 8x8
> > > that works and merges without Fn drivers.
> > > What is there?
> > >
> > > The "sick of it all" guy,
> > > Tom
> > >
> > > PS Midi is still cool. Motu is not.
> > >
> >
> > --
> > Chris Ludwig
> > ADK
> > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > <mailto:chrisl@adkproaudio.com>
> > www.adkproaudio.com <http://www.adkproaudio.com>
> > <http://www.adkproaudio.com/>
> > (859) 635-5762
>
> --
> Chris Ludwig
> ADK
> chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> www.adkproaudio.com <http://www.adkproaudio.com/>
> (859) 635-5762
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64968 is a reply to message #64965] |
Sun, 26 February 2006 11:15 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_01C1_01C63ADF.29582B80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
M-Audio is first on the list of two then...
Thanks you guys.
Tom
"rick" <parnell68@hotmail.com> wrote in message =
news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
"I want a stand alone box." they still have drivers but i've not had
any problems with the m-audio stuff.
On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" <arpegio@comcast.net>
wrote:
>I'm trying to avoid drivers at all costs.
>Midi in/out sounds far more stable to me.
>I want a stand alone box.
>
>USB/MIDI =3D Extra unknown sysex data
> Computer crashes
> Smoked hardware
> Midi Communication loss
> 7 days of lost revenue
>
>or is that just Motu?
>
>
> "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =
news:44015426@linux...
> Hi Tom,
> The would shoot for the M-Audio or Edirol. The Emagic PC driver=20
> development/support is non existent.
>
>
> Chris
>
>
> Tom Bruhl wrote:
> > Chris,
> > No midi on the Delta 66 but that's soon to be gone as
> > is the whole computer during the summer. I plan
> > to get an RME with ADAT and midi interfaces. I will
> > still need the 8x8 though.
> > =20
> > It's between emagic unitor 8, MidiSport 8x8 or
> > Edirol UM 880.
> > =20
> > Anyone like these?
> > Tom
> > =20
> > =20
> >=20
> > "Chris Ludwig" <chrisl@adkproaudio.com
> > <mailto:chrisl@adkproaudio.com>> wrote in message =
news:44008766@linux...
> > Hi Tom,
> > Sadly a common MOTU experience. The M-Audio stuff has always =
worked for
> > me as well as the Edirol stuff.
> > Does your sound card have midi ports on it? I couldn't find a =
mention
> > which it is you have.
> > Hopefully the MOTU didn't damage your on board USB ports!!
> >=20
> > Chris
> >=20
> > Tom Bruhl wrote:
> >=20
> > > This is after over a week of Midi Hell. I am fairly well
> > > versed with midi as a whole. This has been far less =
pleasant
> > > than my first day with multi-timberal synths, controllers, =
editors,
> > > computers, midi merging, SMPTE to Midi Song Pointer and
> > > no information to start with.
> > >=20
> > > Problem #1:
> > > After not being able to transmit sysex from my Amiga
> > > to my TX7s without it 'taking out' the Motu 8x8 patch bay
> > > and crashing Windows into an auto restart from black =
screen
> > > I loaded FM Alive. This allows the PC (instead of Amiga)
> > > to send this sysex data. Well the problems didn't go =
away,they
> > > just changed. FM Alive was getting long sysex messages =
that made
> > > no sense. It would work at editing the synths but =
irrelevant data
> > > was constantly being seen to the program. I disconnected =
all midi
> > > connections from the Motu 8x8 and STILL USB-MIDI data was =
being
> > seen.
> > > Cubase wasn't open. I have not =
been beaten.
> > >=20
> > > I decided to try my original concept of using this Motu =
8x8
> > > as a stand alone and program a few presets, disconnect
> > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > old fashioned way. Midi in/out of Cubase through
> > > Fastlane to one input/output of Motu 8x8 then routed
> > > to all ins/outs of hardware synths. Piece of cake so I =
thought.
> > >=20
> > > Now to dig up the drivers for the FastLane again... I =
loaded what
> > > I thought were the right ones but they weren't. They were =
for
> > the com port.
> > > Okay, so I download the newest ones from Motu's site. I =
bring
> > > them into the computer to realize minus Clockworks they =
are
> > > the exact same drivers that were already in there for the =
8x8. Well
> > > the 8x8 wasn't working flawlessly so I thought I'd =
'remove'
> > > then 'reinstall' them just to be safe. After the =
reinstall, the
> > > directions are to plug in the device (USB cable) and =
Windows should
> > > recognize the new hardware. The only thing that was =
recognized
> > was the
> > > smell of burning components. I quickly shut down two =
computers to
> > > find out that the green FastLane smoked!
> > > This is the final straw.
> > >=20
> > > Drivers from Motu are flakey as hell.
> > > I swear they sent a higher than normal voltage down the =
USB
> > > line somehow.
> > >=20
> > > I now need a new small in/out box (2x2) and a stand alone =
8x8
> > > that works and merges without Fn drivers.
> > > What is there?
> > >=20
> > > The "sick of it all" guy,
> > > Tom
> > >=20
> > > PS Midi is still cool. Motu is not.
> > >=20
> >=20
> > --=20
> > Chris Ludwig
> > ADK
> > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > <mailto:chrisl@adkproaudio.com>
> > www.adkproaudio.com <http://www.adkproaudio.com>
> > <http://www.adkproaudio.com/>
> > (859) 635-5762
>
> --=20
> Chris Ludwig
> ADK
> chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> www.adkproaudio.com <http://www.adkproaudio.com/>
> (859) 635-5762
------=_NextPart_000_01C1_01C63ADF.29582B80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>M-Audio is first on the list of two=20
then...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks you guys.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"rick" <<A=20
href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h597i=
7bptq7jeq5ca7h4j9o2j9r8@4ax.com</A>...</DIV>"I=20
want a stand alone box." they still have drivers but i've =
not=20
had<BR>any problems with the m-audio stuff.<BR><BR>On Sun, 26 Feb 2006 =
02:44:36 -0500, "Tom Bruhl" <<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>wrote:=
<BR><BR>>I'm=20
trying to avoid drivers at all costs.<BR>>Midi in/out sounds far =
more=20
stable to me.<BR>>I want a stand alone box.<BR>><BR>>USB/MIDI =
=3D =20
Extra unknown sysex=20
=
data<BR> > &a mp;nbsp; &=
nbsp; & nbsp; =20
Computer=20
=
crashes<BR> > &a mp;nbsp; &nbs=
p; &nbs p; =20
Smoked=20
=
hardware<BR> > &a mp;nbsp; &nb=
sp; &nb sp; =20
Midi Communication=20
=
loss<BR> > &a mp;nbsp; &=
nbsp; & nbsp; =20
7 days of lost revenue<BR>><BR>>or is that just=20
Motu?<BR>><BR>><BR>> "Chris Ludwig" <<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
wrote in=20
message <A =
href=3D"news:44015426@linux">news:44015426@linux</A>...<BR>> =20
Hi Tom,<BR>> The would shoot for the M-Audio or Edirol. The =
Emagic PC=20
driver <BR>> development/support is non=20
existent.<BR>><BR>><BR>> =
Chris<BR>><BR>><BR>> =20
Tom Bruhl wrote:<BR>> > Chris,<BR>> > No midi =
on the=20
Delta 66 but that's soon to be gone as<BR>> > is the whole =
computer during the summer. I plan<BR>> > to get an =
RME with=20
ADAT and midi interfaces. I will<BR>> > still need =
the 8x8=20
though.<BR>> > <BR>> > It's between =
emagic=20
unitor 8, MidiSport 8x8 or<BR>> > Edirol UM =
880.<BR>> =20
> <BR>> > Anyone like these?<BR>> >=20
Tom<BR>> > <BR>> > <BR>> =
>=20
<BR>> > "Chris Ludwig" <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
> <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;>=20
wrote in message <A=20
href=3D"news:44008766@linux">news:44008766@linux</A>...<BR>> =20
> Hi Tom,<BR>> =20
> Sadly a common MOTU experience. The =
M-Audio stuff=20
has always worked for<BR>> > me as =
well as=20
the Edirol stuff.<BR>> > Does your =
sound=20
card have midi ports on it? I couldn't find a mention<BR>> =20
> which it is you have.<BR>> =20
> Hopefully the MOTU didn't damage your on =
board=20
USB ports!!<BR>> > <BR>> =
> =20
Chris<BR>> > <BR>> > =
Tom Bruhl=20
wrote:<BR>> > <BR>> =
> =2 0
> This is after over a week of Midi Hell. I am fairly=20
well<BR>> > > versed with =
midi as=20
a whole. This has been far less pleasant<BR>> =20
> > than my first day with =
multi-timberal=20
synths, controllers, editors,<BR>> =
> =2 0
> computers, midi merging, SMPTE to Midi Song Pointer =
and<BR>> =20
> > no information to start=20
with.<BR>> > > =
<BR>> =20
> > Problem #1:<BR>> =20
> > After not being able to =
transmit sysex=20
from my Amiga<BR>> > > to =
my TX7s=20
without it 'taking out' the Motu 8x8 patch bay<BR>> =20
> > and crashing Windows into an =
auto=20
restart from black screen<BR>> =
> =2 0
> I loaded FM Alive. This allows the PC (instead of=20
Amiga)<BR>> > > to send =
this=20
sysex data. Well the problems didn't go away,they<BR>> =20
> > just changed. FM Alive =
was=20
getting long sysex messages that made<BR>> =20
> > no sense. It would work =
at=20
editing the synths but irrelevant data<BR>> =20
> > was constantly being seen to =
the=20
program. I disconnected all midi<BR>> =20
> > connections from the Motu 8x8 =
and=20
STILL USB-MIDI data was being<BR>> =
> =20
seen.<BR>> > > Cubase =
wasn't=20
=
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I have not been beaten.<BR>> =
> >=20
<BR>> > > I decided to =
try my=20
original concept of using this Motu 8x8<BR>> =20
> > as a stand alone and program a =
few=20
presets, disconnect<BR>> > =
> the=20
USB, reinstall my Fastlane 2x2 and hook it up the<BR>> =20
> > old fashioned way. Midi =
in/out=20
of Cubase through<BR>> > =
>=20
Fastlane to one input/output of Motu 8x8 then routed<BR>> =20
> > to all ins/outs of hardware=20
synths. Piece of cake so I thought.<BR>> =20
> > <BR>> =20
> > Now to dig up the =
drivers for=20
the FastLane again... I loaded what<BR>> =20
> > I thought were the right ones =
but they=20
weren't. They were for<BR>> =
> the=20
com port.<BR>> > > Okay, =
so I=20
download the newest ones from Motu's site. I bring<BR>> =
> > them into the computer to =
realize=20
minus Clockworks they are<BR>> =
> =2 0
> the exact same drivers that were already in there for the =
8x8. =20
Well<BR>> > > the 8x8 =
wasn't=20
working flawlessly so I thought I'd 'remove'<BR>> =20
> > then 'reinstall' them just to =
be=20
safe. After the reinstall, the<BR>> =20
> > directions are to plug in the =
device=20
(USB cable) and Windows should<BR>> =20
> > recognize the new =
hardware. The=20
only thing that was recognized<BR>> =
> was=20
the<BR>> > > smell of =
burning=20
components. I quickly shut down two computers to<BR>> =20
> > find out that the green =
FastLane=20
smoked!<BR>> > > This is =
the=20
final straw.<BR>> > >=20
<BR>> > > Drivers from =
Motu are=20
flakey as hell.<BR>> > > =
I swear=20
they sent a higher than normal voltage down the USB<BR>> =20
> > line somehow.<BR>> =20
> > <BR>> =20
> > I now need a new small in/out =
box=20
(2x2) and a stand alone 8x8<BR>> =
> =2 0
> that works and merges without Fn drivers.<BR>> =20
> > What is there?<BR>> =20
> > <BR>> =20
> > The "sick of it all"=20
guy,<BR>> > > =
Tom<BR>> =20
> > <BR>> =20
> > PS Midi is still cool. =
Motu is=20
not.<BR>> > > =
<BR>> >=20
<BR>> > -- <BR>> =20
> Chris Ludwig<BR>> =20
> ADK<BR>> =
> <A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> <A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
> <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> (859) 635-5762<BR>><BR>> --=20
<BR>> Chris Ludwig<BR>> ADK<BR>> <A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
<A href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
(859) 635-5762<BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_01C1_01C63ADF.29582B80--
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64973 is a reply to message #64968] |
Sun, 26 February 2006 14:02 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_01FC_01C63AF6.6390FD10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Rick,
Are you using the M-audio 8x8 with XP?
I am reading about just as many unhappy customers
using this box as the Motu.
I'd hate to return one problem for another...
Tom
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:4402008b@linux...
M-Audio is first on the list of two then...
Thanks you guys.
Tom
"rick" <parnell68@hotmail.com> wrote in message =
news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
"I want a stand alone box." they still have drivers but i've not =
had
any problems with the m-audio stuff.
On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" =
<arpegio@comcast.net>
wrote:
>I'm trying to avoid drivers at all costs.
>Midi in/out sounds far more stable to me.
>I want a stand alone box.
>
>USB/MIDI =3D Extra unknown sysex data
> Computer crashes
> Smoked hardware
> Midi Communication loss
> 7 days of lost revenue
>
>or is that just Motu?
>
>
> "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =
news:44015426@linux...
> Hi Tom,
> The would shoot for the M-Audio or Edirol. The Emagic PC driver=20
> development/support is non existent.
>
>
> Chris
>
>
> Tom Bruhl wrote:
> > Chris,
> > No midi on the Delta 66 but that's soon to be gone as
> > is the whole computer during the summer. I plan
> > to get an RME with ADAT and midi interfaces. I will
> > still need the 8x8 though.
> > =20
> > It's between emagic unitor 8, MidiSport 8x8 or
> > Edirol UM 880.
> > =20
> > Anyone like these?
> > Tom
> > =20
> > =20
> >=20
> > "Chris Ludwig" <chrisl@adkproaudio.com
> > <mailto:chrisl@adkproaudio.com>> wrote in message =
news:44008766@linux...
> > Hi Tom,
> > Sadly a common MOTU experience. The M-Audio stuff has =
always worked for
> > me as well as the Edirol stuff.
> > Does your sound card have midi ports on it? I couldn't find =
a mention
> > which it is you have.
> > Hopefully the MOTU didn't damage your on board USB ports!!
> >=20
> > Chris
> >=20
> > Tom Bruhl wrote:
> >=20
> > > This is after over a week of Midi Hell. I am fairly =
well
> > > versed with midi as a whole. This has been far less =
pleasant
> > > than my first day with multi-timberal synths, =
controllers, editors,
> > > computers, midi merging, SMPTE to Midi Song Pointer and
> > > no information to start with.
> > >=20
> > > Problem #1:
> > > After not being able to transmit sysex from my Amiga
> > > to my TX7s without it 'taking out' the Motu 8x8 patch =
bay
> > > and crashing Windows into an auto restart from black =
screen
> > > I loaded FM Alive. This allows the PC (instead of =
Amiga)
> > > to send this sysex data. Well the problems didn't go =
away,they
> > > just changed. FM Alive was getting long sysex messages =
that made
> > > no sense. It would work at editing the synths but =
irrelevant data
> > > was constantly being seen to the program. I =
disconnected all midi
> > > connections from the Motu 8x8 and STILL USB-MIDI data =
was being
> > seen.
> > > Cubase wasn't open. I have not =
been beaten.
> > >=20
> > > I decided to try my original concept of using this Motu =
8x8
> > > as a stand alone and program a few presets, disconnect
> > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > old fashioned way. Midi in/out of Cubase through
> > > Fastlane to one input/output of Motu 8x8 then routed
> > > to all ins/outs of hardware synths. Piece of cake so I =
thought.
> > >=20
> > > Now to dig up the drivers for the FastLane again... I =
loaded what
> > > I thought were the right ones but they weren't. They =
were for
> > the com port.
> > > Okay, so I download the newest ones from Motu's site. I =
bring
> > > them into the computer to realize minus Clockworks they =
are
> > > the exact same drivers that were already in there for =
the 8x8. Well
> > > the 8x8 wasn't working flawlessly so I thought I'd =
'remove'
> > > then 'reinstall' them just to be safe. After the =
reinstall, the
> > > directions are to plug in the device (USB cable) and =
Windows should
> > > recognize the new hardware. The only thing that was =
recognized
> > was the
> > > smell of burning components. I quickly shut down two =
computers to
> > > find out that the green FastLane smoked!
> > > This is the final straw.
> > >=20
> > > Drivers from Motu are flakey as hell.
> > > I swear they sent a higher than normal voltage down the =
USB
> > > line somehow.
> > >=20
> > > I now need a new small in/out box (2x2) and a stand =
alone 8x8
> > > that works and merges without Fn drivers.
> > > What is there?
> > >=20
> > > The "sick of it all" guy,
> > > Tom
> > >=20
> > > PS Midi is still cool. Motu is not.
> > >=20
> >=20
> > --=20
> > Chris Ludwig
> > ADK
> > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > <mailto:chrisl@adkproaudio.com>
> > www.adkproaudio.com <http://www.adkproaudio.com>
> > <http://www.adkproaudio.com/>
> > (859) 635-5762
>
> --=20
> Chris Ludwig
> ADK
> chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> www.adkproaudio.com <http://www.adkproaudio.com/>
> (859) 635-5762
------=_NextPart_000_01FC_01C63AF6.6390FD10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Rick,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Are you using the M-audio 8x8 with =
XP?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I am reading about just as many =
unhappy=20
customers</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>using this box as the =
Motu.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I'd hate to return one problem for=20
another...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
<A href=3D"news:4402008b@linux">news:4402008b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>M-Audio is first on the list of two=20
then...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks you guys.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"rick" <<A=20
href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h597i=
7bptq7jeq5ca7h4j9o2j9r8@4ax.com</A>...</DIV>"I=20
want a stand alone box." they still have drivers but =
i've not=20
had<BR>any problems with the m-audio stuff.<BR><BR>On Sun, 26 Feb =
2006=20
02:44:36 -0500, "Tom Bruhl" <<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>wrote:=
<BR><BR>>I'm=20
trying to avoid drivers at all costs.<BR>>Midi in/out sounds far =
more=20
stable to me.<BR>>I want a stand alone =
box.<BR>><BR>>USB/MIDI=20
=3D Extra unknown sysex=20
=
data<BR> > &a mp;nbsp; &=
nbsp; & nbsp; =20
Computer=20
=
crashes<BR> > &a mp;nbsp; &nbs=
p; &nbs p; =20
Smoked=20
=
hardware<BR> > &a mp;nbsp; &nb=
sp; &nb sp; =20
Midi Communication=20
=
loss<BR> > &a mp;nbsp; &=
nbsp; & nbsp; =20
7 days of lost revenue<BR>><BR>>or is that just=20
Motu?<BR>><BR>><BR>> "Chris Ludwig" <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:44015426@linux">news:44015426@linux</A>...<BR>> Hi =
Tom,<BR>> The would shoot for the M-Audio or Edirol. The =
Emagic PC=20
driver <BR>> development/support is non=20
existent.<BR>><BR>><BR>> =
Chris<BR>><BR>><BR>> =20
Tom Bruhl wrote:<BR>> > Chris,<BR>> > No =
midi on the=20
Delta 66 but that's soon to be gone as<BR>> > is the =
whole=20
computer during the summer. I plan<BR>> > to get =
an RME=20
with ADAT and midi interfaces. I will<BR>> > still =
need=20
the 8x8 though.<BR>> > <BR>> > It's =
between=20
emagic unitor 8, MidiSport 8x8 or<BR>> > Edirol UM=20
880.<BR>> > <BR>> > Anyone like=20
these?<BR>> > Tom<BR>> > =
<BR>> =20
> <BR>> > <BR>> =
> =20
"Chris Ludwig" <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
> <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;>=20
wrote in message <A=20
=
href=3D"news:44008766@linux">news:44008766@linux</A>...<BR>> =20
> Hi Tom,<BR>> =20
> Sadly a common MOTU experience. The =
M-Audio=20
stuff has always worked for<BR>> =
> me as=20
well as the Edirol stuff.<BR>> > =
Does=20
your sound card have midi ports on it? I couldn't find a=20
mention<BR>> > which it is you=20
have.<BR>> > Hopefully the MOTU =
didn't=20
damage your on board USB ports!!<BR>> > <BR>> =20
> Chris<BR>> > <BR>> =
> Tom Bruhl wrote:<BR>> >=20
<BR>> > > This is after =
over a=20
week of Midi Hell. I am fairly well<BR>> =20
> > versed with midi as a =
whole. =20
This has been far less pleasant<BR>> =20
> > than my first day with=20
multi-timberal synths, controllers, editors,<BR>> =20
> > computers, midi merging, =
SMPTE to=20
Midi Song Pointer and<BR>> =
> >=20
no information to start with.<BR>> =20
> > <BR>> =20
> > Problem #1:<BR>> =20
> > After not being able to =
transmit=20
sysex from my Amiga<BR>> > =
> to=20
my TX7s without it 'taking out' the Motu 8x8 patch bay<BR>> =
> > and crashing Windows into an =
auto=20
restart from black screen<BR>> =
> =2 0
> I loaded FM Alive. This allows the PC (instead of=20
Amiga)<BR>> > > to send =
this=20
sysex data. Well the problems didn't go =
away,they<BR>> =20
> > just changed. FM Alive =
was=20
getting long sysex messages that made<BR>> =20
> > no sense. It would =
work at=20
editing the synths but irrelevant data<BR>> =20
> > was constantly being seen to =
the=20
program. I disconnected all midi<BR>> =20
> > connections from the Motu =
8x8 and=20
STILL USB-MIDI data was being<BR>> =
> =20
seen.<BR>> > > Cubase =
wasn't=20
=
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I have not been beaten.<BR>> =
> =2 0
> <BR>> > > I =
decided to try=20
my original concept of using this Motu 8x8<BR>> =20
> > as a stand alone and program =
a few=20
presets, disconnect<BR>> > =
>=20
the USB, reinstall my Fastlane 2x2 and hook it up the<BR>> =20
> > old fashioned way. =
Midi in/out=20
of Cubase through<BR>> > =
>=20
Fastlane to one input/output of Motu 8x8 then routed<BR>> =20
> > to all ins/outs of hardware=20
synths. Piece of cake so I thought.<BR>> =20
> > <BR>> =20
> > Now to dig up the =
drivers for=20
the FastLane again... I loaded what<BR>> =20
> > I thought were the right =
ones but=20
they weren't. They were for<BR>> =
> =20
the com port.<BR>> > > =
Okay, so=20
I download the newest ones from Motu's site. I =
bring<BR>> =20
> > them into the computer to =
realize=20
minus Clockworks they are<BR>> =
> =2 0
> the exact same drivers that were already in there for the =
8x8. =20
Well<BR>> > > the 8x8 =
wasn't=20
working flawlessly so I thought I'd 'remove'<BR>> =20
> > then 'reinstall' them just =
to be=20
safe. After the reinstall, the<BR>> =20
> > directions are to plug in =
the device=20
(USB cable) and Windows should<BR>> =20
> > recognize the new =
hardware. =20
The only thing that was recognized<BR>> =20
> was the<BR>> =20
> > smell of burning =
components. I=20
quickly shut down two computers to<BR>> =20
> > find out that the green =
FastLane=20
smoked!<BR>> > > This =
is the=20
final straw.<BR>> > >=20
<BR>> > > Drivers from =
Motu are=20
flakey as hell.<BR>> > =
> I=20
swear they sent a higher than normal voltage down the =
USB<BR>> =20
> > line somehow.<BR>> =20
> > <BR>> =20
> > I now need a new small =
in/out box=20
(2x2) and a stand alone 8x8<BR>> =
> =2 0
> that works and merges without Fn drivers.<BR>> =20
> > What is there?<BR>> =
> > <BR>> =20
> > The "sick of it all"=20
guy,<BR>> > > =
Tom<BR>> =20
> > <BR>> =20
> > PS Midi is still cool. =
Motu is=20
not.<BR>> > > =
<BR>> =20
> <BR>> > -- <BR>> =20
> Chris Ludwig<BR>> =20
> ADK<BR>> =
> =20
<A href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> <A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
> <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> (859) 635-5762<BR>><BR>> -- =
<BR>> Chris Ludwig<BR>> ADK<BR>> <A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
<A href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> =
<<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
(859) 635-5762<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_01FC_01C63AF6.6390FD10--
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64983 is a reply to message #64973] |
Sun, 26 February 2006 22:33 |
Neil
Messages: 1645
Registered: April 2006
|
Senior Member |
|
|
How many of you guys that are having issues with interfaces
have installed XP Service Pack 2?
The reason I ask is that I upgraded to a new mobo & CPU
recently, and my RME Multiface was working OK until I loaded
Service Pack 2, and now the drivers aren't being recognized at
all, and I'm having difficulty getting it to roll back properly
to the system restore point before SP#2.
Anyone else experiencing driver issues with SP2, or could it be
something else completely?
Neil
"Tom Bruhl" <arpegio@comcast.net> wrote:
>
>
>Rick,
>Are you using the M-audio 8x8 with XP?
>I am reading about just as many unhappy customers
>using this box as the Motu.
>
>I'd hate to return one problem for another...
>Tom
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
>news:4402008b@linux...
> M-Audio is first on the list of two then...
>
> Thanks you guys.
> Tom
>
>
> "rick" <parnell68@hotmail.com> wrote in message =
>news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
> "I want a stand alone box." they still have drivers but i've not =
>had
> any problems with the m-audio stuff.
>
> On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" =
><arpegio@comcast.net>
> wrote:
>
> >I'm trying to avoid drivers at all costs.
> >Midi in/out sounds far more stable to me.
> >I want a stand alone box.
> >
> >USB/MIDI =3D Extra unknown sysex data
> > Computer crashes
> > Smoked hardware
> > Midi Communication loss
> > 7 days of lost revenue
> >
> >or is that just Motu?
> >
> >
> > "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =
>news:44015426@linux...
> > Hi Tom,
> > The would shoot for the M-Audio or Edirol. The Emagic PC driver=20
> > development/support is non existent.
> >
> >
> > Chris
> >
> >
> > Tom Bruhl wrote:
> > > Chris,
> > > No midi on the Delta 66 but that's soon to be gone as
> > > is the whole computer during the summer. I plan
> > > to get an RME with ADAT and midi interfaces. I will
> > > still need the 8x8 though.
> > > =20
> > > It's between emagic unitor 8, MidiSport 8x8 or
> > > Edirol UM 880.
> > > =20
> > > Anyone like these?
> > > Tom
> > > =20
> > > =20
> > >=20
> > > "Chris Ludwig" <chrisl@adkproaudio.com
> > > <mailto:chrisl@adkproaudio.com>> wrote in message =
>news:44008766@linux...
> > > Hi Tom,
> > > Sadly a common MOTU experience. The M-Audio stuff has =
>always worked for
> > > me as well as the Edirol stuff.
> > > Does your sound card have midi ports on it? I couldn't find
=
>a mention
> > > which it is you have.
> > > Hopefully the MOTU didn't damage your on board USB ports!!
> > >=20
> > > Chris
> > >=20
> > > Tom Bruhl wrote:
> > >=20
> > > > This is after over a week of Midi Hell. I am fairly =
>well
> > > > versed with midi as a whole. This has been far less =
>pleasant
> > > > than my first day with multi-timberal synths, =
>controllers, editors,
> > > > computers, midi merging, SMPTE to Midi Song Pointer and
> > > > no information to start with.
> > > >=20
> > > > Problem #1:
> > > > After not being able to transmit sysex from my Amiga
> > > > to my TX7s without it 'taking out' the Motu 8x8 patch =
>bay
> > > > and crashing Windows into an auto restart from black =
>screen
> > > > I loaded FM Alive. This allows the PC (instead of =
>Amiga)
> > > > to send this sysex data. Well the problems didn't go =
>away,they
> > > > just changed. FM Alive was getting long sysex messages
=
>that made
> > > > no sense. It would work at editing the synths but =
>irrelevant data
> > > > was constantly being seen to the program. I =
>disconnected all midi
> > > > connections from the Motu 8x8 and STILL USB-MIDI data =
>was being
> > > seen.
> > > > Cubase wasn't open. I have not
=
>been beaten.
> > > >=20
> > > > I decided to try my original concept of using this Motu
=
>8x8
> > > > as a stand alone and program a few presets, disconnect
> > > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > > old fashioned way. Midi in/out of Cubase through
> > > > Fastlane to one input/output of Motu 8x8 then routed
> > > > to all ins/outs of hardware synths. Piece of cake so I
=
>thought.
> > > >=20
> > > > Now to dig up the drivers for the FastLane again... I =
>loaded what
> > > > I thought were the right ones but they weren't. They =
>were for
> > > the com port.
> > > > Okay, so I download the newest ones from Motu's site. I
=
>bring
> > > > them into the computer to realize minus Clockworks they
=
>are
> > > > the exact same drivers that were already in there for =
>the 8x8. Well
> > > > the 8x8 wasn't working flawlessly so I thought I'd =
>'remove'
> > > > then 'reinstall' them just to be safe. After the =
>reinstall, the
> > > > directions are to plug in the device (USB cable) and =
>Windows should
> > > > recognize the new hardware. The only thing that was =
>recognized
> > > was the
> > > > smell of burning components. I quickly shut down two =
>computers to
> > > > find out that the green FastLane smoked!
> > > > This is the final straw.
> > > >=20
> > > > Drivers from Motu are flakey as hell.
> > > > I swear they sent a higher than normal voltage down the
=
>USB
> > > > line somehow.
> > > >=20
> > > > I now need a new small in/out box (2x2) and a stand =
>alone 8x8
> > > > that works and merges without Fn drivers.
> > > > What is there?
> > > >=20
> > > > The "sick of it all" guy,
> > > > Tom
> > > >=20
> > > > PS Midi is still cool. Motu is not.
> > > >=20
> > >=20
> > > --=20
> > > Chris Ludwig
> > > ADK
> > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > > <mailto:chrisl@adkproaudio.com>
> > > www.adkproaudio.com <http://www.adkproaudio.com>
> > > <http://www.adkproaudio.com/>
> > > (859) 635-5762
> >
> > --=20
> > Chris Ludwig
> > ADK
> > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > www.adkproaudio.com <http://www.adkproaudio.com/>
> > (859) 635-5762
>
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META http-equiv=3DContent-Type content=3D"text/html; =
>charset=3Diso-8859-1">
><META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>Rick,</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>Are you using the M-audio 8x8 with =
>XP?</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>I am reading about just as many =
>unhappy=20
>customers</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>using this box as the =
>Motu.</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>I'd hate to return one problem for=20
>another...</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
><BLOCKQUOTE dir=3Dltr=20
>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=20
> href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
>in message=20
> <A href=3D"news:4402008b@linux">news:4402008b@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>M-Audio is first on the list of two=20
> then...</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Thanks you guys.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <BLOCKQUOTE=20
> style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"rick" <<A=20
> href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A>> =
>wrote in=20
> message <A=20
> =
>href=3D"news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h597i=
>7bptq7jeq5ca7h4j9o2j9r8@4ax.com</A>...</DIV>"I=20
> want a stand alone box." they still have drivers but =
>i've not=20
> had<BR>any problems with the m-audio stuff.<BR><BR>On Sun, 26 Feb =
>2006=20
> 02:44:36 -0500, "Tom Bruhl" <<A=20
> =
>href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>wrote:=
><BR><BR>>I'm=20
> trying to avoid drivers at all costs.<BR>>Midi in/out sounds far =
>more=20
> stable to me.<BR>>I want a stand alone =
>box.<BR>><BR>>USB/MIDI=20
> =3D Extra unknown sysex=20
> =
>data<BR>> &=
>nbsp; =20
> Computer=20
> =
>crashes<BR>> &nbs=
>p; =20
> Smoked=20
> =
>hardware<BR>> &nb=
>sp; =20
> Midi Communication=20
> =
>loss<BR>> &=
>nbsp; =20
> 7 days of lost revenue<BR>><BR>>or is that just=20
> Motu?<BR>><BR>><BR>> "Chris Ludwig" <<A=20
> =
>href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
>wrote in=20
> message <A=20
> =
>href=3D"news:44015426@linux">news:44015426@linux</A>...<BR>> Hi =
>
> Tom,<BR>> The would shoot for the M-Audio or Edirol. The =
>Emagic PC=20
> driver <BR>> development/support is non=20
> existent.<BR>><BR>><BR>> =
>Chris<BR>><BR>><BR>> =20
> Tom Bruhl wrote:<BR>> > Chris,<BR>> > No =
>midi on the=20
> Delta 66 but that's soon to be gone as<BR>> > is the =
>whole=20
> computer during the summer. I plan<BR>> > to get =
>an RME=20
> with ADAT and midi interfaces. I will<BR>> > still =
>need=20
> the 8x8 though.<BR>> > <BR>> > It's =
>between=20
> emagic unitor 8, MidiSport 8x8 or<BR>> > Edirol UM=20
> 880.<BR>> > <BR>> > Anyone like=20
> these?<BR>> > Tom<BR>> > =
><BR>> =20
> > <BR>> > <BR>> =
>> =20
> "Chris Ludwig" <<A=20
> =
>href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
> =20
> > <<A=20
> =
>href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
>gt;>=20
> wrote in message <A=20
> =
>href=3D"news:44008766@linux">news:44008766@linux</A>...<BR>> =20
> > Hi Tom,<BR>> =20
> > Sadly a common MOTU experience. The =
>M-Audio=20
> stuff has always worked for<BR>> =
>> me as=20
> well as the Edirol stuff.<BR>> > =
>Does=20
> your sound card have midi ports on it? I couldn't find a=20
> mention<BR>> > which it is you=20
> have.<BR>> > Hopefully the MOTU =
>didn't=20
> damage your on board USB ports!!<BR>> > <BR>> =20
> > Chris<BR>> > <BR>> =
>
> > Tom Bruhl wrote:<BR>> >=20
> <BR>> > > This is after =
>over a=20
> week of Midi Hell. I am fairly well<BR>> =20
> > > versed with midi as a =
>whole. =20
> This has been far less pleasant<BR>> =20
> > > than my first day with=20
> multi-timberal synths, controllers, editors,<BR>> =20
> > > computers, midi merging, =
>SMPTE to=20
> Midi Song Pointer and<BR>> =
>> >=20
> no information to start with.<BR>> =20
> > > <BR>> =20
> > > Problem #1:<BR>> =20
> > > After not being able to =
>transmit=20
> sysex from my Amiga<BR>> > =
>> to=20
> my TX7s without it 'taking out' the Motu 8x8 patch bay<BR>> =
>
> > > and crashing Windows into an =
>auto=20
> restart from black screen<BR>> =
>> =20
> > I loaded FM Alive. This allows the PC (instead of=20
> Amiga)<BR>> > > to send =
>this=20
> sysex data. Well the problems didn't go =
>away,they<BR>> =20
> > > just changed. FM Alive =
>was=20
> getting long sysex messages that made<BR>> =20
> > > no sense. It would =
>work at=20
> editing the synths but irrelevant data<BR>> =20
> > > was constantly being seen to =
>the=20
> program. I disconnected all midi<BR>> =20
> > > connections from the Motu =
>8x8 and=20
> STILL USB-MIDI data was being<BR>> =
>> =20
> seen.<BR>> > > Cubase =
>wasn't=20
> =
>open. &n=
>bsp; &nb=
>sp; =20
> I have not been beaten.<BR>> =
>> =20
> > <BR>> > > I =
>decided to try=20
> my original concept of using this Motu 8x8<BR>> =20
> > > as a stand alone and program =
>a few=20
> presets, disconnect<BR>> > =
>>=20
> the USB, reinstall my Fastlane 2x2 and hook it up the<BR>> =20
> > > old fashioned way. =
>Midi in/out=20
> of Cubase through<BR>> > =
>>=20
> Fastlane to one input/output of Motu 8x8 then routed<BR>> =20
> > > to all ins/outs of hardware=20
> synths. Piece of cake so I thought.<BR>> =20
> > > <BR>> =20
> > > Now to dig up the =
>drivers for=20
> the FastLane again... I loaded what<BR>> =20
> > > I thought were the right =
>ones but=20
> they weren't. They were for<BR>> =
>> =20
> the com port.<BR>> > > =
>Okay, so=20
> I download the newest ones from Motu's site. I =
>bring<BR>> =20
> > > them into the computer to =
>realize=20
> minus Clockworks they are<BR>> =
>> =20
> > the exact same drivers that were already in there for the =
>8x8. =20
> Well<BR>> > > the 8x8 =
>wasn't=20
> working flawlessly so I thought I'd 'remove'<BR>> =20
> > > then 'reinstall' them just =
>to be=20
> safe. After the reinstall, the<BR>> =20
> > > directions are to plug in =
>the device=20
> (USB cable) and Windows should<BR>> =20
> > > recognize the new =
>hardware. =20
> The only thing that was recognized<BR>> =20
> > was the<BR>> =20
> > > smell of burning =
>components. I=20
> quickly shut down two computers to<BR>> =20
> > > find out that the green =
>FastLane=20
> smoked!<BR>> > > This =
>is the=20
> final straw.<BR>> > >=20
> <BR>> > > Drivers from =
>Motu are=20
> flakey as hell.<BR>> > =
>> I=20
> swear they sent a higher than normal voltage down the =
>USB<BR>> =20
> > > line somehow.<BR>> =20
> > > <BR>> =20
> > > I now need a new small =
>in/out box=20
> (2x2) and a stand alone 8x8<BR>> =
>> =20
> > that works and merges without Fn drivers.<BR>> =20
> > > What is there?<BR>> =
>
> > > <BR>> =20
> > > The "sick of it all"=20
> guy,<BR>> > > =
>Tom<BR>> =20
> > > <BR>> =20
> > > PS Midi is still cool. =
>Motu is=20
> not.<BR>> > > =
><BR>> =20
> > <BR>> > -- <BR>> =20
> > Chris Ludwig<BR>> =20
> > ADK<BR>> =
>> =20
> <A href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>
=
><<A=20
> =
>href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
>gt;<BR>> =20
> > <<A=20
> =
>href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
>gt;<BR>> =20
> > <A=20
> href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
> =
>href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>>> =20
> > <<A=20
> =
>href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
>BR>> =20
> > (859) 635-5762<BR>><BR>> -- =
>
> <BR>> Chris Ludwig<BR>> ADK<BR>> <A=20
> href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
><<A=20
> =
>href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
>gt;<BR>> =20
> <A href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> =
><<A=20
> =
>href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
>BR>> =20
> (859) 635-5762<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
>
>
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64984 is a reply to message #64983] |
Sun, 26 February 2006 22:03 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0052_01C63B39.A0A85980
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I'm SP1 both Paris and Cubase.
"Neil" <OIUOIU@OIU.com> wrote in message news:44028f33$1@linux...
How many of you guys that are having issues with interfaces
have installed XP Service Pack 2?
The reason I ask is that I upgraded to a new mobo & CPU
recently, and my RME Multiface was working OK until I loaded
Service Pack 2, and now the drivers aren't being recognized at
all, and I'm having difficulty getting it to roll back properly
to the system restore point before SP#2.
Anyone else experiencing driver issues with SP2, or could it be
something else completely?
Neil
"Tom Bruhl" <arpegio@comcast.net> wrote:
>
>
>Rick,
>Are you using the M-audio 8x8 with XP?
>I am reading about just as many unhappy customers
>using this box as the Motu.
>
>I'd hate to return one problem for another...
>Tom
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:4402008b@linux...
> M-Audio is first on the list of two then...
>
> Thanks you guys.
> Tom
>
>
> "rick" <parnell68@hotmail.com> wrote in message =3D
>news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
> "I want a stand alone box." they still have drivers but i've =
not =3D
>had
> any problems with the m-audio stuff.
>
> On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" =3D
><arpegio@comcast.net>
> wrote:
>
> >I'm trying to avoid drivers at all costs.
> >Midi in/out sounds far more stable to me.
> >I want a stand alone box.
> >
> >USB/MIDI =3D3D Extra unknown sysex data
> > Computer crashes
> > Smoked hardware
> > Midi Communication loss
> > 7 days of lost revenue
> >
> >or is that just Motu?
> >
> >
> > "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =3D
>news:44015426@linux...
> > Hi Tom,
> > The would shoot for the M-Audio or Edirol. The Emagic PC =
driver=3D20
> > development/support is non existent.
> >
> >
> > Chris
> >
> >
> > Tom Bruhl wrote:
> > > Chris,
> > > No midi on the Delta 66 but that's soon to be gone as
> > > is the whole computer during the summer. I plan
> > > to get an RME with ADAT and midi interfaces. I will
> > > still need the 8x8 though.
> > > =3D20
> > > It's between emagic unitor 8, MidiSport 8x8 or
> > > Edirol UM 880.
> > > =3D20
> > > Anyone like these?
> > > Tom
> > > =3D20
> > > =3D20
> > >=3D20
> > > "Chris Ludwig" <chrisl@adkproaudio.com
> > > <mailto:chrisl@adkproaudio.com>> wrote in message =3D
>news:44008766@linux...
> > > Hi Tom,
> > > Sadly a common MOTU experience. The M-Audio stuff has =
=3D
>always worked for
> > > me as well as the Edirol stuff.
> > > Does your sound card have midi ports on it? I couldn't =
find
=3D
>a mention
> > > which it is you have.
> > > Hopefully the MOTU didn't damage your on board USB =
ports!!
> > >=3D20
> > > Chris
> > >=3D20
> > > Tom Bruhl wrote:
> > >=3D20
> > > > This is after over a week of Midi Hell. I am fairly =
=3D
>well
> > > > versed with midi as a whole. This has been far less =
=3D
>pleasant
> > > > than my first day with multi-timberal synths, =3D
>controllers, editors,
> > > > computers, midi merging, SMPTE to Midi Song Pointer =
and
> > > > no information to start with.
> > > >=3D20
> > > > Problem #1:
> > > > After not being able to transmit sysex from my Amiga
> > > > to my TX7s without it 'taking out' the Motu 8x8 patch =
=3D
>bay
> > > > and crashing Windows into an auto restart from black =
=3D
>screen
> > > > I loaded FM Alive. This allows the PC (instead of =
=3D
>Amiga)
> > > > to send this sysex data. Well the problems didn't go =
=3D
>away,they
> > > > just changed. FM Alive was getting long sysex =
messages
=3D
>that made
> > > > no sense. It would work at editing the synths but =
=3D
>irrelevant data
> > > > was constantly being seen to the program. I =3D
>disconnected all midi
> > > > connections from the Motu 8x8 and STILL USB-MIDI data =
=3D
>was being
> > > seen.
> > > > Cubase wasn't open. I have =
not
=3D
>been beaten.
> > > >=3D20
> > > > I decided to try my original concept of using this =
Motu
=3D
>8x8
> > > > as a stand alone and program a few presets, =
disconnect
> > > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > > old fashioned way. Midi in/out of Cubase through
> > > > Fastlane to one input/output of Motu 8x8 then routed
> > > > to all ins/outs of hardware synths. Piece of cake so =
I
=3D
>thought.
> > > >=3D20
> > > > Now to dig up the drivers for the FastLane again... =
I =3D
>loaded what
> > > > I thought were the right ones but they weren't. They =
=3D
>were for
> > > the com port.
> > > > Okay, so I download the newest ones from Motu's site. =
I
=3D
>bring
> > > > them into the computer to realize minus Clockworks =
they
=3D
>are
> > > > the exact same drivers that were already in there for =
=3D
>the 8x8. Well
> > > > the 8x8 wasn't working flawlessly so I thought I'd =
=3D
>'remove'
> > > > then 'reinstall' them just to be safe. After the =3D
>reinstall, the
> > > > directions are to plug in the device (USB cable) and =
=3D
>Windows should
> > > > recognize the new hardware. The only thing that was =
=3D
>recognized
> > > was the
> > > > smell of burning components. I quickly shut down two =
=3D
>computers to
> > > > find out that the green FastLane smoked!
> > > > This is the final straw.
> > > >=3D20
> > > > Drivers from Motu are flakey as hell.
> > > > I swear they sent a higher than normal voltage down =
the
=3D
>USB
> > > > line somehow.
> > > >=3D20
> > > > I now need a new small in/out box (2x2) and a stand =
=3D
>alone 8x8
> > > > that works and merges without Fn drivers.
> > > > What is there?
> > > >=3D20
> > > > The "sick of it all" guy,
> > > > Tom
> > > >=3D20
> > > > PS Midi is still cool. Motu is not.
> > > >=3D20
> > >=3D20
> > > --=3D20
> > > Chris Ludwig
> > > ADK
> > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > > <mailto:chrisl@adkproaudio.com>
> > > www.adkproaudio.com <http://www.adkproaudio.com>
> > > <http://www.adkproaudio.com/>
> > > (859) 635-5762
> >
> > --=3D20
> > Chris Ludwig
> > ADK
> > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > www.adkproaudio.com <http://www.adkproaudio.com/>
> > (859) 635-5762
>
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META http-equiv=3D3DContent-Type content=3D3D"text/html; =3D
>charset=3D3Diso-8859-1">
><META content=3D3D"MSHTML 6.00.2800.1400" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Rick,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Are you using the M-audio 8x8 =
with =3D
>XP?</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I am reading about just as many =
=3D
>unhappy=3D20
>customers</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2>using this box as the =3D
>Motu.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I'd hate to return one problem =
for=3D20
>another...</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Tom</FONT></DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A href=3D3D"news:4402008b@linux">news:4402008b@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>M-Audio is first on the list =
of two=3D20
> then...</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Thanks you guys.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Tom</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <BLOCKQUOTE=3D20
> style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"rick" <<A=3D20
> =
href=3D3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A>> =3D
>wrote in=3D20
> message <A=3D20
> =3D
=
>href=3D3D"news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h5=
97i=3D
>7bptq7jeq5ca7h4j9o2j9r8@4ax.com</A>...</DIV>"I=3D20
> want a stand alone box." they still have drivers but =3D
>i've not=3D20
> had<BR>any problems with the m-audio stuff.<BR><BR>On Sun, 26 Feb =
=3D
>2006=3D20
> 02:44:36 -0500, "Tom Bruhl" <<A=3D20
> =3D
=
>href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>wrote:=
=3D
><BR><BR>>I'm=3D20
> trying to avoid drivers at all costs.<BR>>Midi in/out sounds far =
=3D
>more=3D20
> stable to me.<BR>>I want a stand alone =3D
>box.<BR>><BR>>USB/MIDI=3D20
> =3D3D Extra unknown sysex=3D20
> =3D
>data<BR>> &=3D
>nbsp; =3D20
> Computer=3D20
> =3D
>crashes<BR>> &nbs=3D
>p; =3D20
> Smoked=3D20
> =3D
>hardware<BR>> &nb=3D
>sp; =3D20
> Midi Communication=3D20
> =3D
>loss<BR>> &=3D
>nbsp; =3D20
> 7 days of lost revenue<BR>><BR>>or is that just=3D20
> Motu?<BR>><BR>><BR>> "Chris Ludwig" <<A=3D20
> =3D
>href=3D3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
=3D
>wrote in=3D20
> message <A=3D20
> =3D
>href=3D3D"news:44015426@linux">news:44015426@linux</A>...<BR>> Hi =3D
>
> Tom,<BR>> The would shoot for the M-Audio or Edirol. The =3D
>Emagic PC=3D20
> driver <BR>> development/support is non=3D20
> existent.<BR>><BR>><BR>> =3D
>Chris<BR>><BR>><BR>> =3D20
> Tom Bruhl wrote:<BR>> > Chris,<BR>> > No =3D
>midi on the=3D20
> Delta 66 but that's soon to be gone as<BR>> > is the =3D
>whole=3D20
> computer during the summer. I plan<BR>> > to get =3D
>an RME=3D20
> with ADAT and midi interfaces. I will<BR>> > still =3D
>need=3D20
> the 8x8 though.<BR>> > <BR>> > It's =3D
>between=3D20
> emagic unitor 8, MidiSport 8x8 or<BR>> > Edirol UM=3D20
> 880.<BR>> > <BR>> > Anyone like=3D20
> these?<BR>> > Tom<BR>> > =3D
><BR>> =3D20
> > <BR>> > <BR>> =3D
>> =3D20
> "Chris Ludwig" <<A=3D20
> =3D
=
>href=3D3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=3D
> =3D20
> > <<A=3D20
> =3D
=
>href=3D3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</=
A>&=3D
>gt;>=3D20
> wrote in message <A=3D20
> =3D
>href=3D3D"news:44008766@linux">news:44008766@linux</A>...<BR>> =3D20
> > Hi Tom,<BR>> =3D20
> > Sadly a common MOTU experience. The =3D
>M-Audio=3D20
> stuff has always worked for<BR>> =3D
>> me as=3D20
> well as the Edirol stuff.<BR>> > =3D
>Does=3D20
> your sound card have midi ports on it? I couldn't find a=3D20
> mention<BR>> > which it is you=3D20
> have.<BR>> > Hopefully the MOTU =3D
>didn't=3D20
> damage your on board USB ports!!<BR>> > <BR>> =3D20
> > Chris<BR>> > <BR>> =3D
>
> > Tom Bruhl wrote:<BR>> >=3D20
> <BR>> > > This is after =3D
>over a=3D20
> week of Midi Hell. I am fairly well<BR>> =3D20
> > > versed with midi as a =3D
>whole. =3D20
> This has been far less pleasant<BR>> =3D20
> > > than my first day with=3D20
> multi-timberal synths, controllers, editors,<BR>> =3D20
> > > computers, midi merging, =3D
>SMPTE to=3D20
> Midi Song Pointer and<BR>> =3D
>> >=3D20
> no information to start with.<BR>> =3D20
> > > <BR>> =3D20
> > > Problem #1:<BR>> =3D20
> > > After not being able to =3D
>transmit=3D20
> sysex from my Amiga<BR>> > =3D
>> to=3D20
> my TX7s without it 'taking out' the Motu 8x8 patch bay<BR>> =3D
>
> > > and crashing Windows into an =3D
>auto=3D20
> restart from black screen<BR>> =3D
>> =3D20
> > I loaded FM Alive. This allows the PC (instead of=3D20
> Amiga)<BR>> > > to send =3D
>this=3D20
> sysex data. Well the problems didn't go =3D
>away,they<BR>> =3D20
> > > just changed. FM Alive =3D
>was=3D20
> getting long sysex messages that made<BR>> =3D20
> > > no sense. It would =3D
>work at=3D20
> editing the synths but irrelevant data<BR>> =3D20
> > > was constantly being seen to =3D
>the=3D20
> program. I disconnected all midi<BR>> =3D20
> > > connections from the Motu =3D
>8x8 and=3D20
> STILL USB-MIDI data was being<BR>> =3D
>> =3D20
> seen.<BR>> > > Cubase =3D
>wasn't=3D20
> =3D
>open. &n=3D
>bsp; &nb=3D
>sp; =3D20
> I have not been beaten.<BR>> =3D
>> =3D20
> > <BR>> > > I =3D
>decided to try=3D20
> my original concept of using this Motu 8x8<BR>> =3D20
> > > as a stand alone and program =3D
>a few=3D20
> presets, disconnect<BR>> > =3D
>>=3D20
> the USB, reinstall my Fastlane 2x2 and hook it up the<BR>> =3D20
> > > old fashioned way. =3D
>Midi in/out=3D20
> of Cubase through<BR>> > =3D
>>=3D20
> Fastlane to one input/output of Motu 8x8 then routed<BR>> =3D20
> > > to all ins/outs of hardware=3D20
> synths. Piece of cake so I thought.<BR>> =3D20
> > > <BR>> =3D20
> > > Now to dig up the =3D
>drivers for=3D20
> the FastLane again... I loaded what<BR>> =3D20
> > > I thought were the right =3D
>ones but=3D20
> they weren't. They were for<BR>> =3D
>> =3D20
> the com port.<BR>> > > =3D
>Okay, so=3D20
> I download the newest ones from Motu's site. I =3D
>bring<BR>> =3D20
> > > them into the computer to =3D
>realize=3D20
> minus Clockworks they are<BR>> =3D
>> =3D20
> > the exact same drivers that were already in there for the =3D
>8x8. =3D20
> Well<BR>> > > the 8x8 =3D
>wasn't=3D20
> working flawlessly so I thought I'd 'remove'<BR>> =3D20
> > > then 'reinstall' them just =3D
>to be=3D20
> safe. After the reinstall, the<BR>> =3D20
> > > directions are to plug in =3D
>the device=3D20
> (USB cable) and Windows should<BR>> =3D20
> > > recognize the new =3D
>hardware. =3D20
> The only thing that was recognized<BR>> =3D20
> > was the<BR>> =3D20
> > > smell of burning =3D
>components. I=3D20
> quickly shut down two computers to<BR>> =3D20
> > > find out that the green =3D
>FastLane=3D20
> smoked!<BR>> > > This =3D
>is the=3D20
> final straw.<BR>> > >=3D20
> <BR>> > > Drivers from =3D
>Motu are=3D20
> flakey as hell.<BR>> > =3D
>> I=3D20
> swear they sent a higher than normal voltage down the =3D
>USB<BR>> =3D20
> > > line somehow.<BR>> =3D20
> > > <BR>> =3D20
> > > I now need a new small =3D
>in/out box=3D20
> (2x2) and a stand alone 8x8<BR>> =3D
>> =3D20
> > that works and merges without Fn drivers.<BR>> =3D20
> > > What is there?<BR>> =3D
>
> > > <BR>> =3D20
> > > The "sick of it all"=3D20
> guy,<BR>> > > =3D
>Tom<BR>> =3D20
> > > <BR>> =3D20
> > > PS Midi is still cool. =3D
>Motu is=3D20
> not.<BR>> > > =3D
><BR>> =3D20
> > <BR>> > -- <BR>> =3D20
> > Chris Ludwig<BR>> =3D20
> > ADK<BR>> =3D
>> =3D20
> <A =
href=3D3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>
=3D
><<A=3D20
> =3D
=
>href=3D3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</=
A>&=3D
>gt;<BR>> =3D20
> > <<A=3D20
> =3D
=
>href=3D3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</=
A>&=3D
>gt;<BR>> =3D20
> > <A=3D20
> href=3D3D"http://www.adkproaudio.com">www.adkproaudio.com</A> =
<<A=3D20
> =3D
=
>href=3D3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
=3D
>>> =3D20
> > <<A=3D20
> =3D
=
>href=3D3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
=3D
>BR>> =3D20
> > (859) 635-5762<BR>><BR>> -- =3D
>
> <BR>> Chris Ludwig<BR>> ADK<BR>> <A=3D20
> =
href=3D3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =3D
><<A=3D20
> =3D
=
>href=3D3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</=
A>&=3D
>gt;<BR>> =3D20
> <A href=3D3D"http://www.adkproaudio.com">www.adkproaudio.com</A> =
=3D
><<A=3D20
> =3D
=
>href=3D3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
=3D
>BR>> =3D20
> (859) 635-5762<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0052_01C63B39.A0A85980
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'm SP1 both Paris and =
Cubase.</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Neil" <<A =
href=3D"mailto:OIUOIU@OIU.com">OIUOIU@OIU.com</A>> wrote=20
in message <A=20
=
href=3D"news:44028f33$1@linux">news:44028f33$1@linux</A>...</DIV><BR>How =
many of=20
you guys that are having issues with interfaces<BR>have installed XP =
Service=20
Pack 2?<BR><BR>The reason I ask is that I upgraded to a new mobo & =
CPU<BR>recently, and my RME Multiface was working OK until I =
loaded<BR>Service=20
Pack 2, and now the drivers aren't being recognized at<BR>all, and I'm =
having=20
difficulty getting it to roll back properly<BR>to the system restore =
point=20
before SP#2.<BR><BR>Anyone else experiencing driver issues with SP2, =
or could=20
it be<BR>something else completely?<BR><BR>Neil<BR><BR><BR>"Tom Bruhl" =
<<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>>=20
wrote:<BR>><BR>><BR>>Rick,<BR>>Are you using the M-audio =
8x8 with=20
XP?<BR>>I am reading about just as many unhappy =
customers<BR>>using this=20
box as the Motu.<BR>><BR>>I'd hate to return one problem for=20
another...<BR>>Tom<BR>> "Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
=3D<BR>>news:4402008b@linux...<BR>> M-Audio is first on =
the list of=20
two then...<BR>><BR>> Thanks you guys.<BR>> =20
Tom<BR>><BR>><BR>> "rick" <<A=20
href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A>> =
wrote in=20
message=20
=
=3D<BR>>news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...<BR>>&nbs=
p; =20
"I want a stand alone box." they still have drivers but =
i've not=20
=3D<BR>>had<BR>> any problems with the m-audio =
stuff.<BR>><BR>> On Sun, 26 Feb 2006 02:44:36 =
-0500,=20
"Tom Bruhl" =3D<BR>><<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>>&n=
bsp; =20
wrote:<BR>><BR>> >I'm trying to avoid =
drivers at=20
all costs.<BR>> >Midi in/out sounds far more =
stable to=20
me.<BR>> >I want a stand alone=20
box.<BR>> ><BR>> =
>USB/MIDI=20
=3D3D Extra unknown sysex data<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Computer crashes<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Smoked hardware<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Midi Communication loss<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
7 days of lost revenue<BR>> =20
><BR>> >or is that just=20
Motu?<BR>> ><BR>> =20
><BR>> > "Chris Ludwig" <<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
wrote in=20
message =3D<BR>>news:44015426@linux...<BR>> =
> =20
Hi Tom,<BR>> > The would shoot for the =
M-Audio=20
or Edirol. The Emagic PC driver=3D20<BR>> =
> =20
development/support is non existent.<BR>> =20
><BR>> ><BR>> =
> =20
Chris<BR>> ><BR>> =20
><BR>> > Tom Bruhl=20
wrote:<BR>> > >=20
Chris,<BR>> > > No midi on the Delta =
66 but=20
that's soon to be gone as<BR>> > > is =
the=20
whole computer during the summer. I =
plan<BR>> =20
> > to get an RME with ADAT and midi interfaces. I=20
will<BR>> > > still need the 8x8=20
though.<BR>> > >=20
=3D20<BR>> > > It's between emagic =
unitor 8,=20
MidiSport 8x8 or<BR>> > > Edirol UM=20
880.<BR>> > > =
=3D20<BR>> =20
> > Anyone like these?<BR>> =
> >=20
Tom<BR>> > > =
=3D20<BR>> =20
> > =3D20<BR>> > =20
>=3D20<BR>> > =
> =20
"Chris Ludwig" <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
> > <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;>=20
wrote in message =
=3D<BR>>news:44008766@linux...<BR>> =20
> > Hi =
Tom,<BR>> =20
> > Sadly a common MOTU =
experience. The=20
M-Audio stuff has =3D<BR>>always worked =
for<BR>> =20
> > me as well as the Edirol=20
stuff.<BR>> > =
> Does=20
your sound card have midi ports on it? I couldn't find<BR>=3D<BR>>a =
mention<BR>> > =
> =20
which it is you have.<BR>> > =20
> Hopefully the MOTU didn't damage your on =
board=20
USB ports!!<BR>> > =20
>=3D20<BR>> > =
> =20
Chris<BR>> > =
>=3D20<BR>> =20
> > Tom Bruhl=20
wrote:<BR>> > =
>=3D20<BR>> =20
> > > This is after over =
a week=20
of Midi Hell. I am fairly =
=3D<BR>>well<BR>> =20
> > > versed with midi as =
a=20
whole. This has been far less=20
=3D<BR>>pleasant<BR>> > =20
> > than my first day with =
multi-timberal=20
synths, =3D<BR>>controllers, editors,<BR>> =
> =20
> > computers, midi merging, SMPTE =
to Midi=20
Song Pointer and<BR>> > =20
> > no information to start=20
with.<BR>> > =
> =2 0
>=3D20<BR>> > =20
> > Problem =
#1:<BR>> =20
> > > After not being =
able to=20
transmit sysex from my Amiga<BR>> > =20
> > to my TX7s without it 'taking =
out' the=20
Motu 8x8 patch =3D<BR>>bay<BR>> > =20
> > and crashing Windows into an =
auto=20
restart from black =3D<BR>>screen<BR>> =
> =20
> > I loaded FM Alive. This =
allows=20
the PC (instead of =3D<BR>>Amiga)<BR>> =
> =20
> > to send this sysex data. =
Well=20
the problems didn't go =3D<BR>>away,they<BR>> =
> =20
> > just changed. FM Alive =
was=20
getting long sysex messages<BR>=3D<BR>>that =
made<BR>> =20
> > > no sense. It =
would=20
work at editing the synths but =3D<BR>>irrelevant=20
data<BR>> > =
> =2 0
> was constantly being seen to the program. I =
=3D<BR>>disconnected=20
all midi<BR>> > =20
> > connections from the Motu 8x8 =
and=20
STILL USB-MIDI data =3D<BR>>was being<BR>> =
> =20
> seen.<BR>> =
> =20
> > Cubase wasn't=20
=
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I have not<BR>=3D<BR>>been beaten.<BR>> =
> =20
> >=3D20<BR>> =
> > > I decided to try my =
original concept of using this =
Motu<BR>=3D<BR>>8x8<BR>> =20
> > > as a stand alone =
and=20
program a few presets, disconnect<BR>> > =
> > the USB, reinstall my Fastlane =
2x2 and=20
hook it up the<BR>> > =20
> > old fashioned way. Midi =
in/out=20
of Cubase through<BR>> > =20
> > Fastlane to one input/output =
of Motu=20
8x8 then routed<BR>> > =20
> > to all ins/outs of hardware=20
synths. Piece of cake so=20
I<BR>=3D<BR>>thought.<BR>> > =20
> >=3D20<BR>> =
> > > Now to dig up =
the=20
drivers for the FastLane again... I =3D<BR>>loaded=20
what<BR>> > =
> =2 0
> I thought were the right ones but they weren't. They =
=3D<BR>>were=20
for<BR>> > > =
the com=20
port.<BR>> > =
> =2 0
> Okay, so I download the newest ones from Motu's site. =20
I<BR>=3D<BR>>bring<BR>> > =20
> > them into the computer to =
realize=20
minus Clockworks they<BR>=3D<BR>>are<BR>> =
> =20
> > the exact same drivers that =
were=20
already in there for =3D<BR>>the 8x8. =
Well<BR>> =20
> > > the 8x8 wasn't =
working=20
flawlessly so I thought I'd =
=3D<BR>>'remove'<BR>> =20
> > > then 'reinstall' =
them just=20
to be safe. After the =3D<BR>>reinstall, =
the<BR>> =20
> > > directions are to =
plug in=20
the device (USB cable) and =3D<BR>>Windows =
should<BR>> =20
> > > recognize the new=20
hardware. The only thing that was=20
=3D<BR>>recognized<BR>> > =20
> was the<BR>> =
> =20
> > smell of burning =
components. I=20
quickly shut down two =3D<BR>>computers =
to<BR>> =20
> > > find out that the =
green=20
FastLane smoked!<BR>> > =20
> > This is the final=20
straw.<BR>> > =
> =2 0
>=3D20<BR>> > =20
> > Drivers from Motu are flakey =
as=20
hell.<BR>> > =
> =2 0
> I swear they sent a higher than normal voltage down=20
the<BR>=3D<BR>>USB<BR>> > =20
> > line=20
somehow.<BR>> > =20
> >=3D20<BR>> =
> > > I now need a new =
small=20
in/out box (2x2) and a stand =3D<BR>>alone =
8x8<BR>> =20
> > > that works and =
merges=20
without Fn drivers.<BR>> > =20
> > What is=20
there?<BR>> > =
> =2 0
>=3D20<BR>> > =20
> > The "sick of it all"=20
guy,<BR>> > =
> =2 0
> Tom<BR>> > =20
> >=3D20<BR>> =
> > > PS Midi is still=20
cool. Motu is not.<BR>> > =20
> >=3D20<BR>> =
> >=3D20<BR>> > =20
> --=3D20<BR>> =
> =20
> Chris Ludwig<BR>> =
> =20
> ADK<BR>> > =20
> <A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > <A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
> > <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> > (859)=20
635-5762<BR>> ><BR>> =
> =20
--=3D20<BR>> > Chris=20
Ludwig<BR>> > =
ADK<BR>> =20
> <A =
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> <A =
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> (859) 635-5762<BR>><BR>><BR>><!DOCTYPE HTML =
PUBLIC=20
"-//W3C//DTD HTML 4.0=20
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.2800.1400"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Rick,</FONT></DIV& ;gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>Are you using the M-audio 8x8 with=20
=3D<BR>>XP?</FONT></DIV> <BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2>I am reading about just as many=20
=
=3D<BR>>unhappy=3D20<BR>>customers</FONT></DIV> <BR>>=
<DIV><FONT=20
face=3D3DArial size=3D3D2>using this box as the=20
=3D<BR>>Motu.</FONT></DIV> <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I'd hate to return one problem=20
=
for=3D20<BR>>another...</FONT></DIV> <BR>><DIV><=
;FONT=20
face=3D3DArial =
size=3D3D2>Tom</FONT></DIV&g t; <BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: =
5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:4402008b@linux">news:4402008b@linux</A>...</DIV'>news:440200=
8b@linux">news:4402008b@linux</A>...</DIV</A>><BR>>&nbs=
p;=20
<DIV><FONT face=3D3DArial size=3D3D2>M-Audio is first on =
the list of=20
two=3D20<BR>> then...</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial =
size=3D3D2>Thanks=20
you guys.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial =
size=3D3D2>Tom</FONT></DIV&g t; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>> =20
<BLOCKQUOTE=3D20<BR>> style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT:=20
5px; MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"rick"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:parnell68@hotmail.com">parnell68@hotmail.com</A'>mailto:pa=
rnell68@hotmail.com">parnell68@hotmail.com</A</A>>>=20
=3D<BR>>wrote in=3D20<BR>> message=20
<A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h597i=
'>news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h597i</A=
>=3D<BR>>7bptq7jeq5ca7h4j9o2j9r8@4ax.com</A>...</DIV>"I=3D=
20<BR>> =20
want a stand alone box." they still have drivers but =3D<BR>>i've=20
not=3D20<BR>> had<BR>any problems with the =
m-audio=20
stuff.<BR><BR>On Sun, 26 Feb=20
=3D<BR>>2006=3D20<BR>> 02:44:36 -0500, "Tom =
Bruhl"=20
<<A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>wrote'>ma=
ilto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>w=
rote</A>:=3D<BR> ><BR><BR>>I'm=3D20 <BR>> &=
nbsp;=20
trying to avoid drivers at all costs.<BR>>Midi in/out sounds =
far=20
=3D<BR>>more=3D20<BR>> stable to =
me.<BR>>I want a=20
stand alone=20
=
=3D<BR> >box.<BR>><BR>& ;gt;USB/MIDI=3D20 <BR>> &nb=
sp; =20
=3D3D Extra unknown sysex=3D20<BR>> =20
=3D<BR>>data<BR>> &=3D<BR>>nbsp; =
=3D20<BR>> =20
Computer=3D20<BR>> =
=3D<BR>>crashes<BR>>=20
&nbs=3D<BR>>p; =3D20<BR>> =20
Smoked=3D20<BR>> =
=3D<BR>>hardware<BR>>=20
&nb=3D<BR>>sp; =3D20<BR>> Midi=20
Communication=3D20<BR>> =
=3D<BR>>loss<BR>>=20
&=3D<BR>>nbsp; =3D20<BR>> 7 days of lost=20
revenue<BR>><BR>>o r is that=20
just=3D20<BR>> =20
Motu?<BR>><BR>>&am p;lt;BR>> "Chris Ludwig"=20
<<A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A'>mailto:=
chrisl@adkproaudio.com">chrisl@adkproaudio.com</A</A>>>=20
=3D<BR>>wrote in=3D20<BR>> message=20
<A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'news:44015426@linux">news:44015426@linux</A>...<BR'>news:44015426=
@linux">news:44015426@linux</A>...<BR</A>>>=20
Hi =3D<BR>><BR>> Tom,<BR>> The would =
shoot for=20
the M-Audio or Edirol. The =3D<BR>>Emagic =
PC=3D20<BR>> =20
driver <BR>> development/support is =
non=3D20<BR>> =20
existent.<BR>><BR>> ;<BR>>=20
=3D<BR> >Chris<BR>><BR>&am p;gt;<BR>>=20
=3D20<BR>> Tom Bruhl wrote:<BR>> >=20
Chris,<BR>> > No =3D<BR>>midi on =
the=3D20<BR>> =20
Delta 66 but that's soon to be gone as<BR>> > is the=20
=3D<BR>>whole=3D20<BR>> computer during the =
summer. I=20
plan<BR>> > to get =3D<BR>>an =
RME=3D20<BR>> =20
with ADAT and midi interfaces. I will<BR>> > still=20
=3D<BR>>need=3D20<BR>> the 8x8 =
though.<BR>> >=20
<BR>> > It's =
=3D<BR>>between=3D20<BR>> emagic=20
unitor 8, MidiSport 8x8 or<BR>> > Edirol=20
UM=3D20<BR>> 880.<BR>> > =
<BR>> >=20
Anyone like=3D20<BR>> these?<BR>> >=20
Tom<BR>> > =3D<BR>><BR>> =
=3D20<BR>> =20
> <BR>> > <BR>> =3D<BR>>>=20
=3D20<BR>> "Chris Ludwig"=20
<<A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR'>mai=
lto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR</A>=
>>=3D<BR>>=20
=3D20<BR>> > =
<<A=3D20<BR>> =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A'>=
mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A</A>=
>&=3D<BR>>gt;>=3D20<BR>> =20
wrote in message <A=3D20<BR>> =
=3D<BR>>href=3D3D"<A=20
=
href=3D'news:44008766@linux">news:44008766@linux</A>...<BR'>news:44008766=
@linux">news:44008766@linux</A>...<BR</A>>>=20
=3D20<BR>> > Hi Tom,<BR>>=20
=3D20<BR>> > Sadly a common MOTU experience. =
The=20
=3D<BR>>M-Audio=3D20<BR>> stuff has always =
worked=20
for<BR>> =3D<BR>>> me as=3D20<BR>> =
well as the=20
Edirol stuff.<BR>> > =
=3D<BR>>Does=3D20<BR>> =20
your sound card have midi ports on it? I couldn't find=20
a=3D20<BR>> mention<BR>> > which it =
is=20
you=3D20<BR>> have.<BR>> > Hopefully =
the MOTU=20
=3D<BR>>didn't=3D20<BR>> damage your on board =
USB=20
ports!!<BR>> > <BR>> =
=3D20<BR>> >=20
Chris<BR>> > <BR>> =
=3D<BR>><BR>> =20
> Tom Bruhl wrote:<BR>> =
>=3D20<BR>> =20
<BR>> > > This is after =3D<BR>>over=20
a=3D20<BR>> week of Midi Hell. I am fairly=20
well<BR>> =3D20<BR>> > > versed =
with midi as=20
a =3D<BR>>whole. =3D20<BR>> This has been far =
less=20
pleasant<BR>> =3D20<BR>> > > than =
my first=20
day with=3D20<BR>> multi-timberal synths, =
controllers,=20
editors,<BR>> =3D20<BR>> > > =
computers, midi=20
merging, =3D<BR>>SMPTE to=3D20<BR>> Midi Song =
Pointer=20
and<BR>> =3D<BR>>> >=3D20<BR>> =
no=20
information to start with.<BR>> =
=3D20<BR>> >=20
> <BR>> =3D20<BR>> > > Problem=20
#1:<BR>> =3D20<BR>> > > After not =
being able=20
to =3D<BR>>transmit=3D20<BR>> sysex from my=20
Amiga<BR>> > =3D<BR>>> =
to=3D20<BR>> my TX7s=20
without it 'taking out' the Motu 8x8 patch bay<BR>>=20
=3D<BR>><BR>> > > and crashing Windows =
into an=20
=3D<BR>>auto=3D20<BR>> restart from black=20
screen<BR>> =3D<BR>>> =3D20<BR>> =
> I loaded=20
FM Alive. This allows the PC (instead =
of=3D20<BR>> =20
Amiga)<BR>> > > to send=20
=3D<BR>>this=3D20<BR>> sysex data. Well the =
problems=20
didn't go =3D<BR>>away,they<BR>> =
=3D20<BR>> >=20
> just changed. FM Alive =
=3D<BR>>was=3D20<BR>> getting=20
long sysex messages that made<BR>> =
=3D20<BR>> >=20
> no sense. It would =3D<BR>>work =
at=3D20<BR>> editing=20
the synths but irrelevant data<BR>> =
=3D20<BR>> =20
> > was constantly being seen to=20
=3D<BR>>the=3D20<BR>> program. I disconnected =
all=20
midi<BR>> =3D20<BR>> > > =
connections from=20
the Motu =3D<BR>>8x8 and=3D20<BR>> STILL =
USB-MIDI data was=20
being<BR>> =3D<BR>>> =3D20<BR>> =20
seen.<BR>> > > Cubase=20
=3D<BR>>wasn't=3D20<BR>> =3D<BR>>open.=20
&n=3D<BR>>bsp; &nb=3D<BR>>sp; =
=3D20<BR>> I have=20
not been beaten.<BR>> =3D<BR>>> =
=3D20<BR>> =20
> <BR>> > > I =3D<BR>>decided to=20
try=3D20<BR>> my original concept of using this =
Motu=20
8x8<BR>> =3D20<BR>> > > as a stand =
alone and=20
program =3D<BR>>a few=3D20<BR>> presets,=20
disconnect<BR>> > =
=3D<BR>>>=3D20<BR>> the=20
USB, reinstall my Fastlane 2x2 and hook it up the<BR>>=20
=3D20<BR>> > > old fashioned way. =
=3D<BR>>Midi=20
in/out=3D20<BR>> of Cubase through<BR>> =
>=20
=3D<BR>>>=3D20<BR>> Fastlane to one =
input/output of=20
Motu 8x8 then routed<BR>> =3D20<BR>> =
> > to=20
all ins/outs of hardware=3D20<BR>> synths. Piece =
of cake so=20
I thought.<BR>> =3D20<BR>> > >=20
<BR>> =3D20<BR>> > > Now to dig up =
the=20
=3D<BR>>drivers for=3D20<BR>> the FastLane =
again... I=20
loaded what<BR>> =3D20<BR>> > > I =
thought=20
were the right =3D<BR>>ones but=3D20<BR>> they =
weren't.=20
They were for<BR>> =3D<BR>>> =
=3D20<BR>> the=20
com port.<BR>> > > =3D<BR>>Okay,=20
so=3D20<BR>> I download the newest ones from =
Motu's site. I=20
=3D<BR>>bring<BR>> =3D20<BR>> > =
> them into=20
the computer to =3D<BR>>realize=3D20<BR>> =
minus Clockworks=20
they are<BR>> =3D<BR>>> =3D20<BR>> =
> the=20
exact same drivers that were already in there for the =3D<BR>>8x8.=20
=3D20<BR>> Well<BR>> > > the 8x8=20
=3D<BR>>wasn't=3D20<BR>> working flawlessly so =
I thought=20
I'd 'remove'<BR>> =3D20<BR>> > > =
then=20
'reinstall' them just =3D<BR>>to be=3D20<BR>> =
safe. After=20
the reinstall, the<BR>> =3D20<BR>> > =
>=20
directions are to plug in =3D<BR>>the =
device=3D20<BR>> =20
(USB cable) and Windows should<BR>> =
=3D20<BR>> =20
> > recognize the new =3D<BR>>hardware. =
=3D20<BR>> =20
The only thing that was recognized<BR>> =
=3D20<BR>> =20
> was the<BR>> =3D20<BR>> > > =
smell of=20
burning =3D<BR>>components. I=3D20<BR>> =
quickly shut down=20
two computers to<BR>> =3D20<BR>> > =
> find=20
out that the green =3D<BR>>FastLane=3D20<BR>> =20
smoked!<BR>> > > This =3D<BR>>is=20
the=3D20<BR>> final straw.<BR>> >=20
>=3D20<BR>> <BR>> > > Drivers =
from=20
=3D<BR>>Motu are=3D20<BR>> flakey as =
hell.<BR>>=20
> =3D<BR>>> I=3D20<BR>> swear they sent =
a higher=20
than normal voltage down the =3D<BR>>USB<BR>>=20
=3D20<BR>> > > line somehow.<BR>>=20
=3D20<BR>> > > <BR>>=20
=3D20<BR>> > > I now need a new small =
=3D<BR>>in/out=20
box=3D20<BR>> (2x2) and a stand alone =
8x8<BR>>=20
=3D<BR>>> =3D20<BR>> > that works and =
merges without=20
Fn drivers.<BR>> =3D20<BR>> > > =
What is=20
there?<BR>> =3D<BR>><BR>> > >=20
<BR>> =3D20<BR>> > > The "sick of =
it=20
all"=3D20<BR>> guy,<BR>> > >=20
=3D<BR>>Tom<BR>> =3D20<BR>> > > =
<BR>> =3D20<BR>> > > PS Midi is =
still cool.=20
=3D<BR>>Motu is=3D20<BR>> not.<BR>> =
> >=20
=3D<BR>><BR>> =3D20<BR>> > =
<BR>> >=20
-- <BR>> =3D20<BR>> > Chris=20
Ludwig<BR>> =3D20<BR>> > =
ADK<BR>>=20
=3D<BR>>> =3D20<BR>> <A href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A'>mailto:=
chrisl@adkproaudio.com">chrisl@adkproaudio.com</A</A>><BR>=3D<BR=
>><<A=3D20<BR>> =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A'>=
mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A</A>=
>&=3D<BR>>gt;<BR>>=20
=3D20<BR>> > =
<<A=3D20<BR>> =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A'>=
mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A</A>=
>&=3D<BR>>gt;<BR>>=20
=3D20<BR>> > =
<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'http://www.adkproaudio.com">www.adkproaudio.com</A'>http://www.ad=
kproaudio.com">www.adkproaudio.com</A</A>>=20
<<A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR'>h=
ttp://www.adkproaudio.com">http://www.adkproaudio.com</A>><=
;BR</A>=3D<BR>>>>=20
=3D20<BR>> > =
<<A=3D20<BR>> =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.adkproaudio.com/">http://www.adkproaudio.com/</A'>http=
://www.adkproaudio.com/">http://www.adkproaudio.com/</A</A>>>=
<=3D<BR>>BR>>=20
=3D20<BR>> > (859) =
635-5762<BR>><BR>> =20
-- =3D<BR>><BR>> <BR>> Chris=20
Ludwig<BR>> ADK<BR>> =
<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A'>mailto:=
chrisl@adkproaudio.com">chrisl@adkproaudio.com</A</A>>=20
=3D<BR>><<A=3D20<BR>> =
=3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A'>=
mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A</A>=
>&=3D<BR>>gt;<BR>>=20
=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'http://www.adkproaudio.com">www.adkproaudio.com</A'>http://www.ad=
kproaudio.com">www.adkproaudio.com</A</A>>=20
=3D<BR>><<A=3D20<BR>> =
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.adkproaudio.com/">http://www.adkproaudio.com/</A'>http=
://www.adkproaudio.com/">http://www.adkproaudio.com/</A</A>>>=
<=3D<BR>>BR>>=20
=3D20<BR>> (859)=20
=
635-5762<BR></BLOCKQUOTE>< ;/BLOCKQUOTE></BODY><=
/HTML><BR>><BR>><BR></BLOCKQUOTE> </BODY></HTML>
------=_NextPart_000_0052_01C63B39.A0A85980--
|
|
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64987 is a reply to message #64973] |
Mon, 27 February 2006 01:57 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
no, i'm using the 4x4 for the m24 controller (3 I/O's) and one for the
keystation. actually it's connected to both the mac and a pc via usb
to allow sharing of hardware.
On Sun, 26 Feb 2006 17:02:13 -0500, "Tom Bruhl" <arpegio@comcast.net>
wrote:
>Rick,
>Are you using the M-audio 8x8 with XP?
>I am reading about just as many unhappy customers
>using this box as the Motu.
>
>I'd hate to return one problem for another...
>Tom
> "Tom Bruhl" <arpegio@comcast.net> wrote in message news:4402008b@linux...
> M-Audio is first on the list of two then...
>
> Thanks you guys.
> Tom
>
>
> "rick" <parnell68@hotmail.com> wrote in message news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
> "I want a stand alone box." they still have drivers but i've not had
> any problems with the m-audio stuff.
>
> On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" <arpegio@comcast.net>
> wrote:
>
> >I'm trying to avoid drivers at all costs.
> >Midi in/out sounds far more stable to me.
> >I want a stand alone box.
> >
> >USB/MIDI = Extra unknown sysex data
> > Computer crashes
> > Smoked hardware
> > Midi Communication loss
> > 7 days of lost revenue
> >
> >or is that just Motu?
> >
> >
> > "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message news:44015426@linux...
> > Hi Tom,
> > The would shoot for the M-Audio or Edirol. The Emagic PC driver
> > development/support is non existent.
> >
> >
> > Chris
> >
> >
> > Tom Bruhl wrote:
> > > Chris,
> > > No midi on the Delta 66 but that's soon to be gone as
> > > is the whole computer during the summer. I plan
> > > to get an RME with ADAT and midi interfaces. I will
> > > still need the 8x8 though.
> > >
> > > It's between emagic unitor 8, MidiSport 8x8 or
> > > Edirol UM 880.
> > >
> > > Anyone like these?
> > > Tom
> > >
> > >
> > >
> > > "Chris Ludwig" <chrisl@adkproaudio.com
> > > <mailto:chrisl@adkproaudio.com>> wrote in message news:44008766@linux...
> > > Hi Tom,
> > > Sadly a common MOTU experience. The M-Audio stuff has always worked for
> > > me as well as the Edirol stuff.
> > > Does your sound card have midi ports on it? I couldn't find a mention
> > > which it is you have.
> > > Hopefully the MOTU didn't damage your on board USB ports!!
> > >
> > > Chris
> > >
> > > Tom Bruhl wrote:
> > >
> > > > This is after over a week of Midi Hell. I am fairly well
> > > > versed with midi as a whole. This has been far less pleasant
> > > > than my first day with multi-timberal synths, controllers, editors,
> > > > computers, midi merging, SMPTE to Midi Song Pointer and
> > > > no information to start with.
> > > >
> > > > Problem #1:
> > > > After not being able to transmit sysex from my Amiga
> > > > to my TX7s without it 'taking out' the Motu 8x8 patch bay
> > > > and crashing Windows into an auto restart from black screen
> > > > I loaded FM Alive. This allows the PC (instead of Amiga)
> > > > to send this sysex data. Well the problems didn't go away,they
> > > > just changed. FM Alive was getting long sysex messages that made
> > > > no sense. It would work at editing the synths but irrelevant data
> > > > was constantly being seen to the program. I disconnected all midi
> > > > connections from the Motu 8x8 and STILL USB-MIDI data was being
> > > seen.
> > > > Cubase wasn't open. I have not been beaten.
> > > >
> > > > I decided to try my original concept of using this Motu 8x8
> > > > as a stand alone and program a few presets, disconnect
> > > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > > old fashioned way. Midi in/out of Cubase through
> > > > Fastlane to one input/output of Motu 8x8 then routed
> > > > to all ins/outs of hardware synths. Piece of cake so I thought.
> > > >
> > > > Now to dig up the drivers for the FastLane again... I loaded what
> > > > I thought were the right ones but they weren't. They were for
> > > the com port.
> > > > Okay, so I download the newest ones from Motu's site. I bring
> > > > them into the computer to realize minus Clockworks they are
> > > > the exact same drivers that were already in there for the 8x8. Well
> > > > the 8x8 wasn't working flawlessly so I thought I'd 'remove'
> > > > then 'reinstall' them just to be safe. After the reinstall, the
> > > > directions are to plug in the device (USB cable) and Windows should
> > > > recognize the new hardware. The only thing that was recognized
> > > was the
> > > > smell of burning components. I quickly shut down two computers to
> > > > find out that the green FastLane smoked!
> > > > This is the final straw.
> > > >
> > > > Drivers from Motu are flakey as hell.
> > > > I swear they sent a higher than normal voltage down the USB
> > > > line somehow.
> > > >
> > > > I now need a new small in/out box (2x2) and a stand alone 8x8
> > > > that works and merges without Fn drivers.
> > > > What is there?
> > > >
> > > > The "sick of it all" guy,
> > > > Tom
> > > >
> > > > PS Midi is still cool. Motu is not.
> > > >
> > >
> > > --
> > > Chris Ludwig
> > > ADK
> > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > > <mailto:chrisl@adkproaudio.com>
> > > www.adkproaudio.com <http://www.adkproaudio.com>
> > > <http://www.adkproaudio.com/>
> > > (859) 635-5762
> >
> > --
> > Chris Ludwig
> > ADK
> > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > www.adkproaudio.com <http://www.adkproaudio.com/>
> > (859) 635-5762
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #64990 is a reply to message #64987] |
Mon, 27 February 2006 03:32 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_00F3_01C63B67.91BA8C30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Rick,
As Mr. Davis (not Sammy) would say:
"You're freakin' me out..."
Two comps both connected via USB? Hubs are great huh?
I'm spooked but it's good that you got that happening.
I think the Motu Clockworks software is the problem
at this end. Now that it's programmed I won't let it see
the software. I know many are happy with Motu products.
I am so disgusted with drivers, incompatibility and bugs
that I am less patient than I used to be. Most hardware that
is software driven (internally) is usually very stable if not=20
missing a few features. I'd prefer stability anytime.
T.
"rick" <parnell68@hotmail.com> wrote in message =
news:p4j502po6jf055k5ue2gv7fqhfbh5pj3kr@4ax.com...
no, i'm using the 4x4 for the m24 controller (3 I/O's) and one for the
keystation. actually it's connected to both the mac and a pc via usb
to allow sharing of hardware.
On Sun, 26 Feb 2006 17:02:13 -0500, "Tom Bruhl" <arpegio@comcast.net>
wrote:
>Rick,
>Are you using the M-audio 8x8 with XP?
>I am reading about just as many unhappy customers
>using this box as the Motu.
>
>I'd hate to return one problem for another...
>Tom
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:4402008b@linux...
> M-Audio is first on the list of two then...
>
> Thanks you guys.
> Tom
>
>
> "rick" <parnell68@hotmail.com> wrote in message =
news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
> "I want a stand alone box." they still have drivers but i've =
not had
> any problems with the m-audio stuff.
>
> On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" =
<arpegio@comcast.net>
> wrote:
>
> >I'm trying to avoid drivers at all costs.
> >Midi in/out sounds far more stable to me.
> >I want a stand alone box.
> >
> >USB/MIDI =3D Extra unknown sysex data
> > Computer crashes
> > Smoked hardware
> > Midi Communication loss
> > 7 days of lost revenue
> >
> >or is that just Motu?
> >
> >
> > "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =
news:44015426@linux...
> > Hi Tom,
> > The would shoot for the M-Audio or Edirol. The Emagic PC =
driver=20
> > development/support is non existent.
> >
> >
> > Chris
> >
> >
> > Tom Bruhl wrote:
> > > Chris,
> > > No midi on the Delta 66 but that's soon to be gone as
> > > is the whole computer during the summer. I plan
> > > to get an RME with ADAT and midi interfaces. I will
> > > still need the 8x8 though.
> > > =20
> > > It's between emagic unitor 8, MidiSport 8x8 or
> > > Edirol UM 880.
> > > =20
> > > Anyone like these?
> > > Tom
> > > =20
> > > =20
> > >=20
> > > "Chris Ludwig" <chrisl@adkproaudio.com
> > > <mailto:chrisl@adkproaudio.com>> wrote in message =
news:44008766@linux...
> > > Hi Tom,
> > > Sadly a common MOTU experience. The M-Audio stuff has =
always worked for
> > > me as well as the Edirol stuff.
> > > Does your sound card have midi ports on it? I couldn't =
find a mention
> > > which it is you have.
> > > Hopefully the MOTU didn't damage your on board USB =
ports!!
> > >=20
> > > Chris
> > >=20
> > > Tom Bruhl wrote:
> > >=20
> > > > This is after over a week of Midi Hell. I am fairly =
well
> > > > versed with midi as a whole. This has been far less =
pleasant
> > > > than my first day with multi-timberal synths, =
controllers, editors,
> > > > computers, midi merging, SMPTE to Midi Song Pointer =
and
> > > > no information to start with.
> > > >=20
> > > > Problem #1:
> > > > After not being able to transmit sysex from my Amiga
> > > > to my TX7s without it 'taking out' the Motu 8x8 patch =
bay
> > > > and crashing Windows into an auto restart from black =
screen
> > > > I loaded FM Alive. This allows the PC (instead of =
Amiga)
> > > > to send this sysex data. Well the problems didn't go =
away,they
> > > > just changed. FM Alive was getting long sysex =
messages that made
> > > > no sense. It would work at editing the synths but =
irrelevant data
> > > > was constantly being seen to the program. I =
disconnected all midi
> > > > connections from the Motu 8x8 and STILL USB-MIDI data =
was being
> > > seen.
> > > > Cubase wasn't open. I have =
not been beaten.
> > > >=20
> > > > I decided to try my original concept of using this =
Motu 8x8
> > > > as a stand alone and program a few presets, =
disconnect
> > > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > > old fashioned way. Midi in/out of Cubase through
> > > > Fastlane to one input/output of Motu 8x8 then routed
> > > > to all ins/outs of hardware synths. Piece of cake so =
I thought.
> > > >=20
> > > > Now to dig up the drivers for the FastLane again... =
I loaded what
> > > > I thought were the right ones but they weren't. They =
were for
> > > the com port.
> > > > Okay, so I download the newest ones from Motu's site. =
I bring
> > > > them into the computer to realize minus Clockworks =
they are
> > > > the exact same drivers that were already in there for =
the 8x8. Well
> > > > the 8x8 wasn't working flawlessly so I thought I'd =
'remove'
> > > > then 'reinstall' them just to be safe. After the =
reinstall, the
> > > > directions are to plug in the device (USB cable) and =
Windows should
> > > > recognize the new hardware. The only thing that was =
recognized
> > > was the
> > > > smell of burning components. I quickly shut down two =
computers to
> > > > find out that the green FastLane smoked!
> > > > This is the final straw.
> > > >=20
> > > > Drivers from Motu are flakey as hell.
> > > > I swear they sent a higher than normal voltage down =
the USB
> > > > line somehow.
> > > >=20
> > > > I now need a new small in/out box (2x2) and a stand =
alone 8x8
> > > > that works and merges without Fn drivers.
> > > > What is there?
> > > >=20
> > > > The "sick of it all" guy,
> > > > Tom
> > > >=20
> > > > PS Midi is still cool. Motu is not.
> > > >=20
> > >=20
> > > --=20
> > > Chris Ludwig
> > > ADK
> > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > > <mailto:chrisl@adkproaudio.com>
> > > www.adkproaudio.com <http://www.adkproaudio.com>
> > > <http://www.adkproaudio.com/>
> > > (859) 635-5762
> >
> > --=20
> > Chris Ludwig
> > ADK
> > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > www.adkproaudio.com <http://www.adkproaudio.com/>
> > (859) 635-5762
------=_NextPart_000_00F3_01C63B67.91BA8C30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Rick,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As Mr. Davis (not Sammy) would =
say:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>"You're freakin' me =
out..."</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Two comps both connected via USB? =
Hubs are=20
great huh?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm spooked but it's good that you got =
that=20
happening.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I think the Motu Clockworks software is =
the=20
problem</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>at this end. Now =
that it's=20
programmed I won't let it see</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the software. I know many are =
happy with Motu=20
products.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I am so disgusted with drivers, =
incompatibility and=20
bugs</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that I am less patient than I used to =
be. =20
Most hardware that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is software driven (internally) is =
usually very=20
stable if not </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>missing a few features. I'd =
prefer stability=20
anytime.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>T.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"rick" <<A=20
href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:p4j502po6jf055k5ue2gv7fqhfbh5pj3kr@4ax.com">news:p4j502po6jf=
055k5ue2gv7fqhfbh5pj3kr@4ax.com</A>...</DIV>no,=20
i'm using the 4x4 for the m24 controller (3 I/O's) and one for=20
the<BR>keystation. actually it's connected to both the mac and a =
pc via=20
usb<BR>to allow sharing of hardware.<BR><BR>On Sun, 26 Feb 2006 =
17:02:13=20
-0500, "Tom Bruhl" <<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>wrote:=
<BR><BR>>Rick,<BR>>Are=20
you using the M-audio 8x8 with XP?<BR>>I am reading about just as =
many=20
unhappy customers<BR>>using this box as the =
Motu.<BR>><BR>>I'd hate=20
to return one problem for another...<BR>>Tom<BR>> "Tom =
Bruhl"=20
<<A href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in=20
message <A =
href=3D"news:4402008b@linux">news:4402008b@linux</A>...<BR>> =20
M-Audio is first on the list of two then...<BR>><BR>> =
Thanks you=20
guys.<BR>> Tom<BR>><BR>><BR>> =
"rick"=20
<<A =
href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A>> =
wrote=20
in message <A=20
=
href=3D"news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h597i=
7bptq7jeq5ca7h4j9o2j9r8@4ax.com</A>...<BR>> =20
"I want a stand alone box." they still have drivers but =
i've not=20
had<BR>> any problems with the m-audio=20
stuff.<BR>><BR>> On Sun, 26 Feb 2006 02:44:36 =
-0500,=20
"Tom Bruhl" <<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>><BR>>&n=
bsp; =20
wrote:<BR>><BR>> >I'm trying to avoid =
drivers at=20
all costs.<BR>> >Midi in/out sounds far more =
stable to=20
me.<BR>> >I want a stand alone=20
box.<BR>> ><BR>> =
>USB/MIDI=20
=3D Extra unknown sysex data<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Computer crashes<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Smoked hardware<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Midi Communication loss<BR>> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
7 days of lost revenue<BR>> =20
><BR>> >or is that just=20
Motu?<BR>> ><BR>> =20
><BR>> > "Chris Ludwig" <<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:44015426@linux">news:44015426@linux</A>...<BR>> &nbs=
p; =20
> Hi Tom,<BR>> > The would =
shoot for=20
the M-Audio or Edirol. The Emagic PC driver <BR>> =
> development/support is non =
existent.<BR>> =20
><BR>> ><BR>> =
> =20
Chris<BR>> ><BR>> =20
><BR>> > Tom Bruhl=20
wrote:<BR>> > >=20
Chris,<BR>> > > No midi on the Delta =
66 but=20
that's soon to be gone as<BR>> > > is =
the=20
whole computer during the summer. I =
plan<BR>> =20
> > to get an RME with ADAT and midi interfaces. I=20
will<BR>> > > still need the 8x8=20
though.<BR>> > > =20
<BR>> > > It's between emagic unitor =
8,=20
MidiSport 8x8 or<BR>> > > Edirol UM=20
880.<BR>> > > =20
<BR>> > > Anyone like=20
these?<BR>> > > =
Tom<BR>> =20
> > <BR>> > > =
<BR>> > > <BR>> =20
> > "Chris Ludwig" <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
> > <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;>=20
wrote in message <A=20
=
href=3D"news:44008766@linux">news:44008766@linux</A>...<BR>> &nbs=
p; =20
> > Hi =
Tom,<BR>> =20
> > Sadly a common MOTU =
experience. The=20
M-Audio stuff has always worked for<BR>> =
> =20
> me as well as the Edirol=20
stuff.<BR>> > =
> Does=20
your sound card have midi ports on it? I couldn't find a=20
mention<BR>> > =
> =20
which it is you have.<BR>> > =20
> Hopefully the MOTU didn't damage your on =
board=20
USB ports!!<BR>> > >=20
<BR>> > > =20
Chris<BR>> > > =
<BR>> =20
> > Tom Bruhl=20
wrote:<BR>> > > =
<BR>> =20
> > > This is after over =
a week=20
of Midi Hell. I am fairly well<BR>> =
> =20
> > versed with midi as a =
whole. =20
This has been far less pleasant<BR>> > =20
> > than my first day with =
multi-timberal=20
synths, controllers, editors,<BR>> > =20
> > computers, midi merging, SMPTE =
to Midi=20
Song Pointer and<BR>> > =20
> > no information to start=20
with.<BR>> > =
> =2 0
> <BR>> > =
> =2 0
> Problem #1:<BR>> > =20
> > After not being able to =
transmit sysex=20
from my Amiga<BR>> > =20
> > to my TX7s without it 'taking =
out' the=20
Motu 8x8 patch bay<BR>> > =20
> > and crashing Windows into an =
auto=20
restart from black screen<BR>> > =20
> > I loaded FM Alive. This =
allows=20
the PC (instead of Amiga)<BR>> > =20
> > to send this sysex data. =
Well=20
the problems didn't go away,they<BR>> > =20
> > just changed. FM Alive =
was=20
getting long sysex messages that made<BR>> =
> =20
> > no sense. It would work =
at=20
editing the synths but irrelevant data<BR>> =
> =20
> > was constantly being seen to =
the=20
program. I disconnected all midi<BR>> =
> =20
> > connections from the Motu 8x8 =
and=20
STILL USB-MIDI data was being<BR>> > =20
> seen.<BR>> =
> =20
> > Cubase wasn't=20
=
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I have not been beaten.<BR>> > =20
> > <BR>> =
> =20
> > I decided to try my original =
concept=20
of using this Motu 8x8<BR>> > =20
> > as a stand alone and program a =
few=20
presets, disconnect<BR>> > =20
> > the USB, reinstall my Fastlane =
2x2 and=20
hook it up the<BR>> > =20
> > old fashioned way. Midi =
in/out=20
of Cubase through<BR>> > =20
> > Fastlane to one input/output =
of Motu=20
8x8 then routed<BR>> > =20
> > to all ins/outs of hardware=20
synths. Piece of cake so I thought.<BR>> =
> =20
> > <BR>> =
> =20
> > Now to dig up the =
drivers for=20
the FastLane again... I loaded what<BR>> =
> =20
> > I thought were the right ones =
but they=20
weren't. They were for<BR>> > =20
> the com port.<BR>> =20
> > > Okay, so I download =
the=20
newest ones from Motu's site. I bring<BR>> =20
> > > them into the =
computer to=20
realize minus Clockworks they are<BR>> > =
> > the exact same drivers that =
were=20
already in there for the 8x8. Well<BR>> =
> =20
> > the 8x8 wasn't working =
flawlessly so I=20
thought I'd 'remove'<BR>> > =20
> > then 'reinstall' them just to =
be=20
safe. After the reinstall, the<BR>> =
> =20
> > directions are to plug in the =
device=20
(USB cable) and Windows should<BR>> > =20
> > recognize the new =
hardware. The=20
only thing that was recognized<BR>> > =20
> was the<BR>> =
> =20
> > smell of burning =
components. I=20
quickly shut down two computers to<BR>> =
> =20
> > find out that the green =
FastLane=20
smoked!<BR>> > =20
> > This is the final=20
straw.<BR>> > =
> =2 0
> <BR>> > =
> =2 0
> Drivers from Motu are flakey as hell.<BR>> =20
> > > I swear they sent a =
higher=20
than normal voltage down the USB<BR>> > =20
> > line=20
somehow.<BR>> > =20
> > <BR>> =
> =20
> > I now need a new small in/out =
box=20
(2x2) and a stand alone 8x8<BR>> > =20
> > that works and merges without =
Fn=20
drivers.<BR>> > =20
> > What is=20
there?<BR>> > =
> =2 0
> <BR>> > =
> =2 0
> The "sick of it all" guy,<BR>> > =20
> > Tom<BR>> =20
> > > =
<BR>> =20
> > > PS Midi is still=20
cool. Motu is not.<BR>> > =20
> > <BR>> =
> =20
> <BR>> > =
> --=20
<BR>> > > =
Chris=20
Ludwig<BR>> > =
> =20
ADK<BR>> > > =
<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > <A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
> > <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> > (859)=20
635-5762<BR>> ><BR>> =
> =20
-- <BR>> > Chris=20
Ludwig<BR>> > =
ADK<BR>> =20
> <A =
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> <A =
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> (859) 635-5762<BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_00F3_01C63B67.91BA8C30--
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #65012 is a reply to message #64990] |
Tue, 28 February 2006 01:41 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
it works fine and i can play the soft synths from both at the same
time. i have more of a problem running 2 things (controller wise) on
the mac than this way. if i have the M24 and the keystation pro both
set up for logic (even though they're for different operations) the
mac freaks. maybe the new mac and 7.2 will be different. i'm still
into testing the new one to see what makes it happy and what pisses me
off.
On Mon, 27 Feb 2006 06:32:23 -0500, "Tom Bruhl" <arpegio@comcast.net>
wrote:
>Rick,
>As Mr. Davis (not Sammy) would say:
>"You're freakin' me out..."
>
>Two comps both connected via USB? Hubs are great huh?
>I'm spooked but it's good that you got that happening.
>
>I think the Motu Clockworks software is the problem
>at this end. Now that it's programmed I won't let it see
>the software. I know many are happy with Motu products.
>I am so disgusted with drivers, incompatibility and bugs
>that I am less patient than I used to be. Most hardware that
>is software driven (internally) is usually very stable if not
>missing a few features. I'd prefer stability anytime.
>T.
>
>
>
>
> "rick" <parnell68@hotmail.com> wrote in message news:p4j502po6jf055k5ue2gv7fqhfbh5pj3kr@4ax.com...
> no, i'm using the 4x4 for the m24 controller (3 I/O's) and one for the
> keystation. actually it's connected to both the mac and a pc via usb
> to allow sharing of hardware.
>
> On Sun, 26 Feb 2006 17:02:13 -0500, "Tom Bruhl" <arpegio@comcast.net>
> wrote:
>
> >Rick,
> >Are you using the M-audio 8x8 with XP?
> >I am reading about just as many unhappy customers
> >using this box as the Motu.
> >
> >I'd hate to return one problem for another...
> >Tom
> > "Tom Bruhl" <arpegio@comcast.net> wrote in message news:4402008b@linux...
> > M-Audio is first on the list of two then...
> >
> > Thanks you guys.
> > Tom
> >
> >
> > "rick" <parnell68@hotmail.com> wrote in message news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
> > "I want a stand alone box." they still have drivers but i've not had
> > any problems with the m-audio stuff.
> >
> > On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl" <arpegio@comcast.net>
> > wrote:
> >
> > >I'm trying to avoid drivers at all costs.
> > >Midi in/out sounds far more stable to me.
> > >I want a stand alone box.
> > >
> > >USB/MIDI = Extra unknown sysex data
> > > Computer crashes
> > > Smoked hardware
> > > Midi Communication loss
> > > 7 days of lost revenue
> > >
> > >or is that just Motu?
> > >
> > >
> > > "Chris Ludwig" <chrisl@adkproaudio.com> wrote in message news:44015426@linux...
> > > Hi Tom,
> > > The would shoot for the M-Audio or Edirol. The Emagic PC driver
> > > development/support is non existent.
> > >
> > >
> > > Chris
> > >
> > >
> > > Tom Bruhl wrote:
> > > > Chris,
> > > > No midi on the Delta 66 but that's soon to be gone as
> > > > is the whole computer during the summer. I plan
> > > > to get an RME with ADAT and midi interfaces. I will
> > > > still need the 8x8 though.
> > > >
> > > > It's between emagic unitor 8, MidiSport 8x8 or
> > > > Edirol UM 880.
> > > >
> > > > Anyone like these?
> > > > Tom
> > > >
> > > >
> > > >
> > > > "Chris Ludwig" <chrisl@adkproaudio.com
> > > > <mailto:chrisl@adkproaudio.com>> wrote in message news:44008766@linux...
> > > > Hi Tom,
> > > > Sadly a common MOTU experience. The M-Audio stuff has always worked for
> > > > me as well as the Edirol stuff.
> > > > Does your sound card have midi ports on it? I couldn't find a mention
> > > > which it is you have.
> > > > Hopefully the MOTU didn't damage your on board USB ports!!
> > > >
> > > > Chris
> > > >
> > > > Tom Bruhl wrote:
> > > >
> > > > > This is after over a week of Midi Hell. I am fairly well
> > > > > versed with midi as a whole. This has been far less pleasant
> > > > > than my first day with multi-timberal synths, controllers, editors,
> > > > > computers, midi merging, SMPTE to Midi Song Pointer and
> > > > > no information to start with.
> > > > >
> > > > > Problem #1:
> > > > > After not being able to transmit sysex from my Amiga
> > > > > to my TX7s without it 'taking out' the Motu 8x8 patch bay
> > > > > and crashing Windows into an auto restart from black screen
> > > > > I loaded FM Alive. This allows the PC (instead of Amiga)
> > > > > to send this sysex data. Well the problems didn't go away,they
> > > > > just changed. FM Alive was getting long sysex messages that made
> > > > > no sense. It would work at editing the synths but irrelevant data
> > > > > was constantly being seen to the program. I disconnected all midi
> > > > > connections from the Motu 8x8 and STILL USB-MIDI data was being
> > > > seen.
> > > > > Cubase wasn't open. I have not been beaten.
> > > > >
> > > > > I decided to try my original concept of using this Motu 8x8
> > > > > as a stand alone and program a few presets, disconnect
> > > > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > > > old fashioned way. Midi in/out of Cubase through
> > > > > Fastlane to one input/output of Motu 8x8 then routed
> > > > > to all ins/outs of hardware synths. Piece of cake so I thought.
> > > > >
> > > > > Now to dig up the drivers for the FastLane again... I loaded what
> > > > > I thought were the right ones but they weren't. They were for
> > > > the com port.
> > > > > Okay, so I download the newest ones from Motu's site. I bring
> > > > > them into the computer to realize minus Clockworks they are
> > > > > the exact same drivers that were already in there for the 8x8. Well
> > > > > the 8x8 wasn't working flawlessly so I thought I'd 'remove'
> > > > > then 'reinstall' them just to be safe. After the reinstall, the
> > > > > directions are to plug in the device (USB cable) and Windows should
> > > > > recognize the new hardware. The only thing that was recognized
> > > > was the
> > > > > smell of burning components. I quickly shut down two computers to
> > > > > find out that the green FastLane smoked!
> > > > > This is the final straw.
> > > > >
> > > > > Drivers from Motu are flakey as hell.
> > > > > I swear they sent a higher than normal voltage down the USB
> > > > > line somehow.
> > > > >
> > > > > I now need a new small in/out box (2x2) and a stand alone 8x8
> > > > > that works and merges without Fn drivers.
> > > > > What is there?
> > > > >
> > > > > The "sick of it all" guy,
> > > > > Tom
> > > > >
> > > > > PS Midi is still cool. Motu is not.
> > > > >
> > > >
> > > > --
> > > > Chris Ludwig
> > > > ADK
> > > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > > > <mailto:chrisl@adkproaudio.com>
> > > > www.adkproaudio.com <http://www.adkproaudio.com>
> > > > <http://www.adkproaudio.com/>
> > > > (859) 635-5762
> > >
> > > --
> > > Chris Ludwig
> > > ADK
> > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> > > www.adkproaudio.com <http://www.adkproaudio.com/>
> > > (859) 635-5762
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #65025 is a reply to message #64990] |
Tue, 28 February 2006 09:05 |
jef knight[1]
Messages: 201
Registered: October 2005
|
Senior Member |
|
|
i had a motu for a year or so and had nothing but trouble with the sysex
end of. apparently there are known issues with how it handles some types
of sysex. i switched to a unitor8 and my troubles dissappeared.
jef
Tom Bruhl wrote:
> Rick,
> As Mr. Davis (not Sammy) would say:
> "You're freakin' me out..."
>
> Two comps both connected via USB? Hubs are great huh?
> I'm spooked but it's good that you got that happening.
>
> I think the Motu Clockworks software is the problem
> at this end. Now that it's programmed I won't let it see
> the software. I know many are happy with Motu products.
> I am so disgusted with drivers, incompatibility and bugs
> that I am less patient than I used to be. Most hardware that
> is software driven (internally) is usually very stable if not
> missing a few features. I'd prefer stability anytime.
> T.
>
>
>
>
>
> "rick" <parnell68@hotmail.com <mailto:parnell68@hotmail.com>>
> wrote in message news:p4j502po6jf055k5ue2gv7fqhfbh5pj3kr@4ax.com...
> no, i'm using the 4x4 for the m24 controller (3 I/O's) and one for the
> keystation. actually it's connected to both the mac and a pc via usb
> to allow sharing of hardware.
>
> On Sun, 26 Feb 2006 17:02:13 -0500, "Tom Bruhl"
> <arpegio@comcast.net <mailto:arpegio@comcast.net>>
> wrote:
>
> >Rick,
> >Are you using the M-audio 8x8 with XP?
> >I am reading about just as many unhappy customers
> >using this box as the Motu.
> >
> >I'd hate to return one problem for another...
> >Tom
> > "Tom Bruhl" <arpegio@comcast.net <mailto:arpegio@comcast.net>>
> wrote in message news:4402008b@linux...
> > M-Audio is first on the list of two then...
> >
> > Thanks you guys.
> > Tom
> >
> >
> > "rick" <parnell68@hotmail.com <mailto:parnell68@hotmail.com>>
> wrote in message news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
> > "I want a stand alone box." they still have drivers but
> i've not had
> > any problems with the m-audio stuff.
> >
> > On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl"
> <arpegio@comcast.net <mailto:arpegio@comcast.net>>
> > wrote:
> >
> > >I'm trying to avoid drivers at all costs.
> > >Midi in/out sounds far more stable to me.
> > >I want a stand alone box.
> > >
> > >USB/MIDI = Extra unknown sysex data
> > > Computer crashes
> > > Smoked hardware
> > > Midi Communication loss
> > > 7 days of lost revenue
> > >
> > >or is that just Motu?
> > >
> > >
> > > "Chris Ludwig" <chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com>> wrote in message
> news:44015426@linux...
> > > Hi Tom,
> > > The would shoot for the M-Audio or Edirol. The Emagic PC
> driver
> > > development/support is non existent.
> > >
> > >
> > > Chris
> > >
> > >
> > > Tom Bruhl wrote:
> > > > Chris,
> > > > No midi on the Delta 66 but that's soon to be gone as
> > > > is the whole computer during the summer. I plan
> > > > to get an RME with ADAT and midi interfaces. I will
> > > > still need the 8x8 though.
> > > >
> > > > It's between emagic unitor 8, MidiSport 8x8 or
> > > > Edirol UM 880.
> > > >
> > > > Anyone like these?
> > > > Tom
> > > >
> > > >
> > > >
> > > > "Chris Ludwig" <chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com>
> > > > <mailto:chrisl@adkproaudio.com>> wrote in message
> news:44008766@linux...
> > > > Hi Tom,
> > > > Sadly a common MOTU experience. The M-Audio stuff
> has always worked for
> > > > me as well as the Edirol stuff.
> > > > Does your sound card have midi ports on it? I
> couldn't find a mention
> > > > which it is you have.
> > > > Hopefully the MOTU didn't damage your on board USB
> ports!!
> > > >
> > > > Chris
> > > >
> > > > Tom Bruhl wrote:
> > > >
> > > > > This is after over a week of Midi Hell. I am
> fairly well
> > > > > versed with midi as a whole. This has been far
> less pleasant
> > > > > than my first day with multi-timberal synths,
> controllers, editors,
> > > > > computers, midi merging, SMPTE to Midi Song
> Pointer and
> > > > > no information to start with.
> > > > >
> > > > > Problem #1:
> > > > > After not being able to transmit sysex from my Amiga
> > > > > to my TX7s without it 'taking out' the Motu 8x8
> patch bay
> > > > > and crashing Windows into an auto restart from
> black screen
> > > > > I loaded FM Alive. This allows the PC (instead
> of Amiga)
> > > > > to send this sysex data. Well the problems
> didn't go away,they
> > > > > just changed. FM Alive was getting long sysex
> messages that made
> > > > > no sense. It would work at editing the synths
> but irrelevant data
> > > > > was constantly being seen to the program. I
> disconnected all midi
> > > > > connections from the Motu 8x8 and STILL USB-MIDI
> data was being
> > > > seen.
> > > > > Cubase wasn't open. I
> have not been beaten.
> > > > >
> > > > > I decided to try my original concept of using
> this Motu 8x8
> > > > > as a stand alone and program a few presets,
> disconnect
> > > > > the USB, reinstall my Fastlane 2x2 and hook it up the
> > > > > old fashioned way. Midi in/out of Cubase through
> > > > > Fastlane to one input/output of Motu 8x8 then routed
> > > > > to all ins/outs of hardware synths. Piece of
> cake so I thought.
> > > > >
> > > > > Now to dig up the drivers for the FastLane
> again... I loaded what
> > > > > I thought were the right ones but they weren't.
> They were for
> > > > the com port.
> > > > > Okay, so I download the newest ones from Motu's
> site. I bring
> > > > > them into the computer to realize minus
> Clockworks they are
> > > > > the exact same drivers that were already in there
> for the 8x8. Well
> > > > > the 8x8 wasn't working flawlessly so I thought
> I'd 'remove'
> > > > > then 'reinstall' them just to be safe. After the
> reinstall, the
> > > > > directions are to plug in the device (USB cable)
> and Windows should
> > > > > recognize the new hardware. The only thing that
> was recognized
> > > > was the
> > > > > smell of burning components. I quickly shut down
> two computers to
> > > > > find out that the green FastLane smoked!
> > > > > This is the final straw.
> > > > >
> > > > > Drivers from Motu are flakey as hell.
> > > > > I swear they sent a higher than normal voltage
> down the USB
> > > > > line somehow.
> > > > >
> > > > > I now need a new small in/out box (2x2) and a
> stand alone 8x8
> > > > > that works and merges without Fn drivers.
> > > > > What is there?
> > > > >
> > > > > The "sick of it all" guy,
> > > > > Tom
> > > > >
> > > > > PS Midi is still cool. Motu is not.
> > > > >
> > > >
> > > > --
> > > > Chris Ludwig
> > > > ADK
> > > > chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com> <mailto:chrisl@adkproaudio.com>
> > > > <mailto:chrisl@adkproaudio.com>
> > > > www.adkproaudio.com <http://www.adkproaudio.com>
> <http://www.adkproaudio.com>
> > > > <http://www.adkproaudio.com/>
> > > > (859) 635-5762
> > >
> > > --
> > > Chris Ludwig
> > > ADK
> > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> <mailto:chrisl@adkproaudio.com>
> > > www.adkproaudio.com <http://www.adkproaudio.com>
> <http://www.adkproaudio.com/>
> > > (859) 635-5762
>
|
|
|
|
| Re: OT MIDI HELL or MOTU IS USELESS [message #65026 is a reply to message #65025] |
Tue, 28 February 2006 09:08 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0055_01C63C5F.AE386910
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
So I'm not the only one! Back it goes. I'm going for the M-Audio 8x8.
Thanks for confirming my tests Jef.
Tom
"jef knight" <thestudio@allknightmusic.com> wrote in message =
news:4404843c@linux...
i had a motu for a year or so and had nothing but trouble with the =
sysex=20
end of. apparently there are known issues with how it handles some =
types=20
of sysex. i switched to a unitor8 and my troubles dissappeared.
jef
Tom Bruhl wrote:
> Rick,
> As Mr. Davis (not Sammy) would say:
> "You're freakin' me out..."
> =20
> Two comps both connected via USB? Hubs are great huh?
> I'm spooked but it's good that you got that happening.
> =20
> I think the Motu Clockworks software is the problem
> at this end. Now that it's programmed I won't let it see
> the software. I know many are happy with Motu products.
> I am so disgusted with drivers, incompatibility and bugs
> that I am less patient than I used to be. Most hardware that
> is software driven (internally) is usually very stable if not
> missing a few features. I'd prefer stability anytime.
> T.
> =20
> =20
> =20
> =20
>
> "rick" <parnell68@hotmail.com <mailto:parnell68@hotmail.com>>
> wrote in message =
news:p4j502po6jf055k5ue2gv7fqhfbh5pj3kr@4ax.com...
> no, i'm using the 4x4 for the m24 controller (3 I/O's) and one =
for the
> keystation. actually it's connected to both the mac and a pc =
via usb
> to allow sharing of hardware.
>
> On Sun, 26 Feb 2006 17:02:13 -0500, "Tom Bruhl"
> <arpegio@comcast.net <mailto:arpegio@comcast.net>>
> wrote:
>
> >Rick,
> >Are you using the M-audio 8x8 with XP?
> >I am reading about just as many unhappy customers
> >using this box as the Motu.
> >
> >I'd hate to return one problem for another...
> >Tom
> > "Tom Bruhl" <arpegio@comcast.net =
<mailto:arpegio@comcast.net>>
> wrote in message news:4402008b@linux...
> > M-Audio is first on the list of two then...
> >
> > Thanks you guys.
> > Tom
> >
> >
> > "rick" <parnell68@hotmail.com =
<mailto:parnell68@hotmail.com>>
> wrote in message =
news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com...
> > "I want a stand alone box." they still have drivers but
> i've not had
> > any problems with the m-audio stuff.
> >
> > On Sun, 26 Feb 2006 02:44:36 -0500, "Tom Bruhl"
> <arpegio@comcast.net <mailto:arpegio@comcast.net>>
> > wrote:
> >
> > >I'm trying to avoid drivers at all costs.
> > >Midi in/out sounds far more stable to me.
> > >I want a stand alone box.
> > >
> > >USB/MIDI =3D Extra unknown sysex data
> > > Computer crashes
> > > Smoked hardware
> > > Midi Communication loss
> > > 7 days of lost revenue
> > >
> > >or is that just Motu?
> > >
> > >
> > > "Chris Ludwig" <chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com>> wrote in message
> news:44015426@linux...
> > > Hi Tom,
> > > The would shoot for the M-Audio or Edirol. The Emagic PC
> driver
> > > development/support is non existent.
> > >
> > >
> > > Chris
> > >
> > >
> > > Tom Bruhl wrote:
> > > > Chris,
> > > > No midi on the Delta 66 but that's soon to be gone as
> > > > is the whole computer during the summer. I plan
> > > > to get an RME with ADAT and midi interfaces. I will
> > > > still need the 8x8 though.
> > > >=20
> > > > It's between emagic unitor 8, MidiSport 8x8 or
> > > > Edirol UM 880.
> > > >=20
> > > > Anyone like these?
> > > > Tom
> > > >=20
> > > >=20
> > > >
> > > > "Chris Ludwig" <chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com>
> > > > <mailto:chrisl@adkproaudio.com>> wrote in message
> news:44008766@linux...
> > > > Hi Tom,
> > > > Sadly a common MOTU experience. The M-Audio stuff
> has always worked for
> > > > me as well as the Edirol stuff.
> > > > Does your sound card have midi ports on it? I
> couldn't find a mention
> > > > which it is you have.
> > > > Hopefully the MOTU didn't damage your on board USB
> ports!!
> > > >
> > > > Chris
> > > >
> > > > Tom Bruhl wrote:
> > > >
> > > > > This is after over a week of Midi Hell. I am
> fairly well
> > > > > versed with midi as a whole. This has been far
> less pleasant
> > > > > than my first day with multi-timberal synths,
> controllers, editors,
> > > > > computers, midi merging, SMPTE to Midi Song
> Pointer and
> > > > > no information to start with.
> > > > >
> > > > > Problem #1:
> > > > > After not being able to transmit sysex from my =
Amiga
> > > > > to my TX7s without it 'taking out' the Motu 8x8
> patch bay
> > > > > and crashing Windows into an auto restart from
> black screen
> > > > > I loaded FM Alive. This allows the PC (instead
> of Amiga)
> > > > > to send this sysex data. Well the problems
> didn't go away,they
> > > > > just changed. FM Alive was getting long sysex
> messages that made
> > > > > no sense. It would work at editing the synths
> but irrelevant data
> > > > > was constantly being seen to the program. I
> disconnected all midi
> > > > > connections from the Motu 8x8 and STILL =
USB-MIDI
> data was being
> > > > seen.
> > > > > Cubase wasn't open. I
> have not been beaten.
> > > > >
> > > > > I decided to try my original concept of using
> this Motu 8x8
> > > > > as a stand alone and program a few presets,
> disconnect
> > > > > the USB, reinstall my Fastlane 2x2 and hook it =
up the
> > > > > old fashioned way. Midi in/out of Cubase =
through
> > > > > Fastlane to one input/output of Motu 8x8 then =
routed
> > > > > to all ins/outs of hardware synths. Piece of
> cake so I thought.
> > > > >
> > > > > Now to dig up the drivers for the FastLane
> again... I loaded what
> > > > > I thought were the right ones but they weren't. =
> They were for
> > > > the com port.
> > > > > Okay, so I download the newest ones from Motu's
> site. I bring
> > > > > them into the computer to realize minus
> Clockworks they are
> > > > > the exact same drivers that were already in =
there
> for the 8x8. Well
> > > > > the 8x8 wasn't working flawlessly so I thought
> I'd 'remove'
> > > > > then 'reinstall' them just to be safe. After =
the
> reinstall, the
> > > > > directions are to plug in the device (USB =
cable)
> and Windows should
> > > > > recognize the new hardware. The only thing =
that
> was recognized
> > > > was the
> > > > > smell of burning components. I quickly shut =
down
> two computers to
> > > > > find out that the green FastLane smoked!
> > > > > This is the final straw.
> > > > >
> > > > > Drivers from Motu are flakey as hell.
> > > > > I swear they sent a higher than normal voltage
> down the USB
> > > > > line somehow.
> > > > >
> > > > > I now need a new small in/out box (2x2) and a
> stand alone 8x8
> > > > > that works and merges without Fn drivers.
> > > > > What is there?
> > > > >
> > > > > The "sick of it all" guy,
> > > > > Tom
> > > > >
> > > > > PS Midi is still cool. Motu is not.
> > > > >
> > > >
> > > > --
> > > > Chris Ludwig
> > > > ADK
> > > > chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com> <mailto:chrisl@adkproaudio.com>
> > > > <mailto:chrisl@adkproaudio.com>
> > > > www.adkproaudio.com <http://www.adkproaudio.com>
> <http://www.adkproaudio.com>
> > > > <http://www.adkproaudio.com/>
> > > > (859) 635-5762
> > >
> > > --
> > > Chris Ludwig
> > > ADK
> > > chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> <mailto:chrisl@adkproaudio.com>
> > > www.adkproaudio.com <http://www.adkproaudio.com>
> <http://www.adkproaudio.com/>
> > > (859) 635-5762
>
------=_NextPart_000_0055_01C63C5F.AE386910
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>So I'm not the only one! Back it =
goes. =20
I'm going for the M-Audio 8x8.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for confirming my tests =
Jef.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"jef knight" <<A=20
=
href=3D"mailto:thestudio@allknightmusic.com">thestudio@allknightmusic.com=
</A>>=20
wrote in message <A=20
href=3D"news:4404843c@linux">news:4404843c@linux</A>...</DIV>i had a =
motu for a=20
year or so and had nothing but trouble with the sysex <BR>end of. =
apparently=20
there are known issues with how it handles some types <BR>of sysex. i =
switched=20
to a unitor8 and my troubles dissappeared.<BR>jef<BR><BR>Tom Bruhl=20
wrote:<BR><BR>> Rick,<BR>> As Mr. Davis (not Sammy) would =
say:<BR>>=20
"You're freakin' me out..."<BR>> <BR>> Two comps both =
connected=20
via USB? Hubs are great huh?<BR>> I'm spooked but it's good =
that you=20
got that happening.<BR>> <BR>> I think the Motu Clockworks =
software is the problem<BR>> at this end. Now that it's =
programmed I=20
won't let it see<BR>> the software. I know many are happy =
with Motu=20
products.<BR>> I am so disgusted with drivers, incompatibility and=20
bugs<BR>> that I am less patient than I used to be. Most =
hardware=20
that<BR>> is software driven (internally) is usually very stable if =
not<BR>> missing a few features. I'd prefer stability=20
anytime.<BR>> T.<BR>> <BR>> <BR>> =
<BR>> =20
<BR>><BR>> "rick" <<A=20
href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A> <<A =
=
href=3D"mailto:parnell68@hotmail.com">mailto:parnell68@hotmail.com</A>>=
;><BR>> =20
wrote in message <A=20
=
href=3D"news:p4j502po6jf055k5ue2gv7fqhfbh5pj3kr@4ax.com">news:p4j502po6jf=
055k5ue2gv7fqhfbh5pj3kr@4ax.com</A>...<BR>> =20
no, i'm using the 4x4 for the m24 controller (3 I/O's) and one for=20
the<BR>> keystation. actually it's =
connected=20
to both the mac and a pc via usb<BR>> to =
allow=20
sharing of hardware.<BR>><BR>> On Sun, =
26 Feb=20
2006 17:02:13 -0500, "Tom Bruhl"<BR>> =
<<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A> <<A=20
=
href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net</A>>>=
;<BR>> =20
wrote:<BR>><BR>> =20
>Rick,<BR>> >Are you using the =
M-audio 8x8=20
with XP?<BR>> >I am reading about just =
as many=20
unhappy customers<BR>> >using this box =
as the=20
Motu.<BR>> =
><BR>> =20
>I'd hate to return one problem for=20
another...<BR>> =20
>Tom<BR>> > "Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A> <<A=20
=
href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net</A>>>=
;<BR>> =20
wrote in message <A=20
=
href=3D"news:4402008b@linux">news:4402008b@linux</A>...<BR>> &nbs=
p; =20
> M-Audio is first on the list of two=20
then...<BR>> =
><BR>> =20
> Thanks you guys.<BR>> > =
Tom<BR>> =
><BR>> =20
><BR>> > "rick" =
<<A=20
href=3D"mailto:parnell68@hotmail.com">parnell68@hotmail.com</A> <<A =
=
href=3D"mailto:parnell68@hotmail.com">mailto:parnell68@hotmail.com</A>>=
;><BR>> =20
wrote in message <A=20
=
href=3D"news:nc0302h597i7bptq7jeq5ca7h4j9o2j9r8@4ax.com">news:nc0302h597i=
7bptq7jeq5ca7h4j9o2j9r8@4ax.com</A>...<BR>> =20
> "I want a stand alone box." they =
still have=20
drivers but<BR>> i've not=20
had<BR>> > any =
problems with=20
the m-audio stuff.<BR>> =20
><BR>> > On Sun, 26 =
Feb=20
2006 02:44:36 -0500, "Tom Bruhl"<BR>> =
<<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A> <<A=20
=
href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net</A>>>=
;<BR>> =20
> wrote:<BR>> =20
><BR>> > >I'm =
trying to=20
avoid drivers at all costs.<BR>> =20
> >Midi in/out sounds far more stable to=20
me.<BR>> > >I want =
a stand=20
alone box.<BR>> > =20
><BR>> > =
>USB/MIDI=20
=3D Extra unknown sysex data<BR>> =20
> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Computer crashes<BR>> =
> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Smoked hardware<BR>> > =
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
Midi Communication loss<BR>> =
> =20
=
> &a mp;nbsp; &a mp;nb=
sp; &nb sp;=20
7 days of lost revenue<BR>> =
> =20
><BR>> > >or is =
that=20
just Motu?<BR>> > =20
><BR>> > =20
><BR>> > > =
"Chris=20
Ludwig" <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;>=20
wrote in message<BR>> <A=20
=
href=3D"news:44015426@linux">news:44015426@linux</A>...<BR>> &nbs=
p; =20
> > Hi =
Tom,<BR>> =20
> > The would shoot for the M-Audio or =
Edirol.=20
The Emagic PC<BR>> =20
driver<BR>> > =
> =20
development/support is non existent.<BR>> =20
> ><BR>> =20
> ><BR>> =20
> > =
Chris<BR>> =20
> ><BR>> =20
> ><BR>> =20
> > Tom Bruhl=20
wrote:<BR>> > =
> >=20
Chris,<BR>> > =
> >=20
No midi on the Delta 66 but that's soon to be gone=20
as<BR>> > > =
> is=20
the whole computer during the summer. I=20
plan<BR>> > > =
> to=20
get an RME with ADAT and midi interfaces. I=20
will<BR>> > > =
>=20
still need the 8x8 though.<BR>> =20
> > > =
<BR>> =20
> > > It's between emagic unitor 8, =
MidiSport=20
8x8 or<BR>> > =
> >=20
Edirol UM 880.<BR>> > =20
> > <BR>> =
> =20
> > Anyone like these?<BR>> =20
> > > =
Tom<BR>> =20
> > > =
<BR>> =20
> > > =
<BR>> =20
> > ><BR>> =
> > > "Chris =
Ludwig"=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > > <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;>=20
wrote in message<BR>> <A=20
=
href=3D"news:44008766@linux">news:44008766@linux</A>...<BR>> &nbs=
p; =20
> > > Hi=20
Tom,<BR>> > > =
> Sadly a common MOTU experience. The =
M-Audio=20
stuff<BR>> has always worked=20
for<BR>> > > =20
> me as well as the Edirol=20
stuff.<BR>> > =
> =20
> Does your sound card have midi ports on =
it?=20
I<BR>> couldn't find a=20
mention<BR>> > =
> =20
> which it is you=20
have.<BR>> > =
> =20
> Hopefully the MOTU didn't damage your on =
board=20
USB<BR>> =
ports!!<BR>> =20
> > ><BR>> =
> > > =20
Chris<BR>> > =
> =20
><BR>> > > =
> Tom Bruhl =
wrote:<BR>> =20
> > ><BR>> =
> > > =
> This=20
is after over a week of Midi Hell. I =
am<BR>> =20
fairly well<BR>> > =
> =20
> > versed with midi as a =
whole. =20
This has been far<BR>> less=20
pleasant<BR>> > =
> =20
> > than my first day with =
multi-timberal=20
synths,<BR>> controllers,=20
editors,<BR>> > =
> =20
> > computers, midi merging, SMPTE =
to Midi=20
Song<BR>> Pointer=20
and<BR>> > > =20
> > no information to start=20
with.<BR>> > =
> =20
> =
><BR>> =20
> > > =
>=20
Problem #1:<BR>> > =
> =20
> > After not being able to =
transmit sysex=20
from my Amiga<BR>> > =20
> > > to my TX7s without =
it=20
'taking out' the Motu 8x8<BR>> patch=20
bay<BR>> > > =20
> > and crashing Windows into an =
auto=20
restart from<BR>> black=20
screen<BR>> > =
> =20
> > I loaded FM Alive. This =
allows=20
the PC (instead<BR>> of=20
Amiga)<BR>> > =
> =20
> > to send this sysex data. =
Well=20
the problems<BR>> didn't go=20
away,they<BR>> > =
> =20
> > just changed. FM Alive =
was=20
getting long sysex<BR>> messages that=20
made<BR>> > > =
> > no sense. It would work =
at=20
editing the synths<BR>> but irrelevant=20
data<BR>> > > =
> > was constantly being seen to =
the=20
program. I<BR>> disconnected all=20
midi<BR>> > > =
> > connections from the Motu 8x8 =
and=20
STILL USB-MIDI<BR>> data was=20
being<BR>> > =
> =20
> seen.<BR>> =20
> > > =
>=20
Cubase wasn't=20
=
open. & nbsp; & n=
bsp; &n bsp; &n b=
sp; =20
I<BR>> have not been=20
beaten.<BR>> > =
> =20
> =
><BR>> =20
> > > =
> I=20
decided to try my original concept of =
using<BR>> =20
this Motu 8x8<BR>> > =20
> > > as a stand alone =
and=20
program a few presets,<BR>> =20
disconnect<BR>> > =
> =20
> > the USB, reinstall my Fastlane =
2x2 and=20
hook it up the<BR>> > =20
> > > old fashioned =
way. =20
Midi in/out of Cubase through<BR>> =20
> > > =
>=20
Fastlane to one input/output of Motu 8x8 then=20
routed<BR>> > =
> =20
> > to all ins/outs of hardware=20
synths. Piece of<BR>> cake so I=20
thought.<BR>> > =
> =20
> =
><BR>> =20
> > > =2 0
> Now to dig up the drivers for the=20
FastLane<BR>> again... I loaded=20
what<BR>> > > =
> > I thought were the right ones =
but they=20
weren't. <BR>> They were=20
for<BR>> > > =20
> the com =
port.<BR>> =20
> > > =
>=20
Okay, so I download the newest ones from=20
Motu's<BR>> site. I=20
bring<BR>> > =
> =20
> > them into the computer to =
realize=20
minus<BR>> Clockworks they=20
are<BR>> > > =20
> > the exact same drivers that =
were=20
already in there<BR>> for the 8x8. =20
Well<BR>> > > =
> > the 8x8 wasn't working =
flawlessly so I=20
thought<BR>> I'd=20
'remove'<BR>> > =
> =20
> > then 'reinstall' them just to =
be=20
safe. After the<BR>> reinstall,=20
the<BR>> > > =20
> > directions are to plug in the =
device=20
(USB cable)<BR>> and Windows=20
should<BR>> > =
> =20
> > recognize the new =
hardware. The=20
only thing that<BR>> was=20
recognized<BR>> > =
> =20
> was the<BR>> =20
> > > =
>=20
smell of burning components. I quickly shut=20
down<BR>> two computers=20
to<BR>> > > =20
> > find out that the green =
FastLane=20
smoked!<BR>> > =
> =20
> > This is the final=20
straw.<BR>> > =
> =20
> =
><BR>> =20
> > > =
>=20
Drivers from Motu are flakey as hell.<BR>> =20
> > > =
> I=20
swear they sent a higher than normal =
voltage<BR>> =20
down the USB<BR>> > =
> =20
> > line=20
somehow.<BR>> > =
> =20
> =
><BR>> =20
> > > =
> I=20
now need a new small in/out box (2x2) and =
a<BR>> =20
stand alone 8x8<BR>> > =
> > > that works and =
merges=20
without Fn drivers.<BR>> =
> =20
> > > What is=20
there?<BR>> > =
> =20
> =
><BR>> =20
> > > =
> The=20
"sick of it all" guy,<BR>> =
> =20
> > >=20
Tom<BR>> > > =20
> =
><BR>> =20
> > > =
> PS=20
Midi is still cool. Motu is not.<BR>> =
> > > =2 0
><BR>> > > =
><BR>> > > =
> --<BR>> =20
> > > Chris=20
Ludwig<BR>> > =
> =20
> ADK<BR>> =20
> > > <A=20
=
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A><BR>>=
=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;=20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > > <<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > > <A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
<<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
> > > <<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> > > (859)=20
635-5762<BR>> > =20
><BR>> > > =
--<BR>> > > =
Chris=20
Ludwig<BR>> > =
> =20
ADK<BR>> > > =
<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A> =
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
<<A=20
=
href=3D"mailto:chrisl@adkproaudio.com">mailto:chrisl@adkproaudio.com</A>&=
gt;<BR>> =20
> > <A=20
href=3D"http://www.adkproaudio.com">www.adkproaudio.com</A> <<A=20
=
href=3D"http://www.adkproaudio.com">http://www.adkproaudio.com</A>><BR=
>> =20
<<A=20
=
href=3D"http://www.adkproaudio.com/">http://www.adkproaudio.com/</A>><=
BR>> =20
> > (859)=20
635-5762<BR>></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0055_01C63C5F.AE386910--
|
|
|
|
Goto Forum:
Current Time: Tue Sep 24 13:02:12 PDT 2024
Total time taken to generate the page: 0.06072 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
