The PARIS Forums


Home » The PARIS Forums » PARIS: Main » OT Motu Midi Express XT (USB) If you have experience please chime in.
OT Motu Midi Express XT (USB) If you have experience please chime in. [message #64605] Thu, 16 February 2006 15:44 Go to previous message
Tom Bruhl is currently offline  Tom Bruhl   UNITED STATES
Messages: 1368
Registered: June 2007
Senior Member
This is a multi-part message in MIME format.

------=_NextPart_000_01D6_01C63329.04E54D90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I purchased this (knowing there are driver issues) by
someone's suggestion to buy it. I have spent four days
now and have come to find the USB signal gets lost
very easily and the unit is rendered undetected. This means all
hardware synths stop. If I do a sysex dump it loses
connectivity. It also crashes hard and fast to a black screen
if I touch any buttons on the "Mute" screen in Clockworks.
Clockworks is the software that controls programmability.
CW also loses touch with the hardware during these activities.
A quick fix seems to be an Off/On button push. That's a little
extreme 3 or 4 times in a song...

Motu drivers are v2.51 on Win XP Pro with Cubase 2.0?. I am using
an AMD 1700+ with a PCI to USB 2.0 card installed.

I haven't bothered syncing with Paris yet. That's not an
option the way things have been going. =20

I tried to have Cubase filter sysex data but whenever I do a sysex send
to a hardware synth the "Computer" light on the Motu lights up.
I think if I could filter sysex from not only Cubase but the 'Motu
trying to send to Cubase' I'd be better off. As I understand it the=20
Motu is always sending/returning all 8 ports to and from Cubase.
Tom


------=_NextPart_000_01D6_01C63329.04E54D90
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 purchased this (knowing there are =
driver issues)=20
by</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>someone's suggestion to buy it.&nbsp; I =
have=20
spent&nbsp;four days</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>now and have come to find the USB =
signal gets=20
lost</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>very easily and the unit is rendered=20
undetected.&nbsp; This means all</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>hardware synths stop.&nbsp; If I do a =
sysex dump it=20
loses</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>connectivity.&nbsp; It also crashes =
hard and fast=20
to a black screen</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>if I touch any buttons on the "Mute" =
screen in=20
Clockworks.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Clockworks is the software that =
controls=20
programmability.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>CW&nbsp;also loses touch with the =
hardware during=20
these activities.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>A quick fix seems to be an Off/On =
button=20
push.&nbsp; That's a little</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>extreme 3 or 4 times in a =
song...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Motu drivers are v2.51 on Win XP Pro =
with Cubase=20
2.0?.&nbsp;I am using</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>an </FONT><FONT face=3DArial =
size=3D2>AMD 1700+ with a=20
PCI to USB 2.0 card installed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I haven't bothered =
syncing</FONT>&nbsp;<FONT=20
face=3DArial size=3D2>with Paris yet.&nbsp; That's not an</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>option the way things have been =
going.&nbsp;=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I tried to have Cubase filter sysex =
data but=20
whenever I do a sysex send</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to a hardware synth the "Computer" =
light on the=20
Motu lights up.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think if I could filter sysex from =
not only=20
Cubase but the 'Motu</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>trying to send to Cubase' I'd be better =
off.&nbsp;=20
As I </FONT><FONT face=3DArial size=3D2>understand it the </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Motu is always sending/returning all 8 =
ports=20
</FONT><FONT face=3DArial size=3D2>to and from Cubase.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_01D6_01C63329.04E54D90--
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: PARIS Recorded Sample
Next Topic: Soooo.....is this stress?
Goto Forum:
  


Current Time: Tue Nov 26 11:10:11 PST 2024

Total time taken to generate the page: 0.00944 seconds