The PARIS Forums: PARIS: Main » OT Motu Midi Express XT (USB) If you have experience please chime in.

Home » The PARIS Forums » PARIS: Main » OT Motu Midi Express XT (USB) If you have experience please chime in.

Show: Today's Messages :: Polls :: Message Navigator

OT Motu Midi Express XT (USB) If you have experience please chime in. [message #64605]

Thu, 16 February 2006 15:44

Tom Bruhl

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.  I =
have=20
spent 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.  This means all</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>hardware synths stop.  If I do a =
sysex dump it=20
loses</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>connectivity.  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 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.  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> </DIV>
<DIV><FONT face=3DArial size=3D2>Motu drivers are v2.51 on Win XP Pro =
with Cubase=20
2.0?. 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> </DIV>
<DIV><FONT face=3DArial size=3D2>I haven't bothered =
syncing</FONT> <FONT=20
face=3DArial size=3D2>with Paris yet.  That's not an</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>option the way things have been =
going. =20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </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. =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> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML>

------=_NextPart_000_01D6_01C63329.04E54D90--

Report message to a moderator

Re: OT Motu Midi Express XT (USB) If you have experience pleasechime in. [message #64606 is a reply to message #64605]

Thu, 16 February 2006 15:59

EK Sound

Messages: 939
Registered: June 2005

Senior Member

Do you have the PC or MAC rom chip installed?? It comes with both 8
pin DIP's.

David.

Tom Bruhl wrote:
> 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.
>
> 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
> Motu is always sending/returning all 8 ports to and from Cubase.
> Tom
>
>

Report message to a moderator

Re: OT Motu Midi Express XT (USB) If you have experience please chime in. [message #64609 is a reply to message #64606]

Thu, 16 February 2006 16:48

Tom Bruhl

Messages: 1368
Registered: June 2007

Senior Member

This is a multi-part message in MIME format.

------=_NextPart_000_020B_01C63331.FE357C50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

David,
I read that it wasn't needed with the XT. Maybe that's wrong.
I didn't see any chips floating around in the box.
Tom
"EK Sound" <askme@nospam.com> wrote in message =
news:43f512f0$1@linux...
Do you have the PC or MAC rom chip installed?? It comes with both 8=20
pin DIP's.

David.

Tom Bruhl wrote:
> 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...
> =20
> 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.
> =20
> I haven't bothered syncing with Paris yet. That's not an
> option the way things have been going.=20
> =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
> Motu is always sending/returning all 8 ports to and from Cubase.
> Tom
> =20
>
------=_NextPart_000_020B_01C63331.FE357C50
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>David,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I read that it wasn't =
needed with the=20
XT.  Maybe that's wrong.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I didn't see any chips floating around =
in the=20
box.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"EK Sound" <<A =
href=3D"mailto:askme@nospam.com">askme@nospam.com</A>>=20
wrote in message <A=20
href=3D"news:43f512f0$1@linux">news:43f512f0$1@linux</A>...</DIV>Do =
you have the=20
PC or MAC rom chip installed??  It comes with both 8 <BR>pin=20
DIP's.<BR><BR>David.<BR><BR>Tom Bruhl wrote:<BR>> I purchased this =
(knowing=20
there are driver issues) by<BR>> someone's suggestion to buy =
it.  I=20
have spent four days<BR>> now and have come to find the USB signal =
gets=20
lost<BR>> very easily and the unit is rendered undetected.  =
This means=20
all<BR>> hardware synths stop.  If I do a sysex dump it =
loses<BR>>=20
connectivity.  It also crashes hard and fast to a black =
screen<BR>> if=20
I touch any buttons on the "Mute" screen in Clockworks.<BR>> =
Clockworks is=20
the software that controls programmability.<BR>> CW also loses =
touch with=20
the hardware during these activities.<BR>> A quick fix seems to be =
an=20
Off/On button push.  That's a little<BR>> extreme 3 or 4 times =
in a=20
song...<BR>>  <BR>> Motu drivers are v2.51 on Win XP Pro =
with=20
Cubase 2.0?. I am using<BR>> an AMD 1700+ with a PCI to USB 2.0 =
card=20
installed.<BR>>  <BR>> I haven't bothered syncing with =
Paris=20
yet.  That's not an<BR>> option the way things have been =
going.=20
<BR>>  <BR>> I tried to have Cubase filter sysex data but =
whenever=20
I do a sysex send<BR>> to a hardware synth the "Computer" light on =
the Motu=20
lights up.<BR>> I think if I could filter sysex from not only =
Cubase but=20
the 'Motu<BR>> trying to send to Cubase' I'd be better off.  =
As I=20
understand it the<BR>> Motu is always sending/returning all 8 ports =
to and=20
from Cubase.<BR>> Tom<BR>>  =
<BR>></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_020B_01C63331.FE357C50--

Report message to a moderator

Re: OT Motu Midi Express XT (USB) If you have experience pleasechime in. [message #64615 is a reply to message #64609]

Thu, 16 February 2006 18:44

Chris Ludwig

Messages: 868
Registered: May 2006

Senior Member

HI Tom,
Have you tried it on the motherboards built in USB?
It is not a USB 2.0 device so you might be getting some misbehaving from
that.
What motherboard are you using?

Chris

Tom Bruhl wrote:

> David,
> I read that it wasn't needed with the XT. Maybe that's wrong.
> I didn't see any chips floating around in the box.
> Tom
>
> "EK Sound" <askme@nospam.com <mailto:askme@nospam.com>> wrote in
> message news:43f512f0$1@linux...
> Do you have the PC or MAC rom chip installed?? It comes with both 8
> pin DIP's.
>
> David.
>
> Tom Bruhl wrote:
> > 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.
> >
> > 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
> > Motu is always sending/returning all 8 ports to and from Cubase.
> > Tom
> >
> >

--
Chris Ludwig
ADK
chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
www.adkproaudio.com <http://www.adkproaudio.com/>
(859) 635-5762

Report message to a moderator

Re: OT Motu Midi Express XT (USB) If you have experience please chime in. [message #64616 is a reply to message #64615]

Thu, 16 February 2006 18:51

Tom Bruhl

Messages: 1368
Registered: June 2007

Senior Member

This is a multi-part message in MIME format.

------=_NextPart_000_0228_01C63343.24A3FC70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hey Chris,
It's an old KG7 with USB 1 so I invested in a=20
USB2 PCI card to bring it up to USB 2. Was that
wrong?
Tom

"Chris Ludwig" <chrisl@adkproaudio.com> wrote in message =
news:43f539d7$1@linux...
HI Tom,
Have you tried it on the motherboards built in USB?
It is not a USB 2.0 device so you might be getting some misbehaving =
from=20
that.
What motherboard are you using?

Chris

Tom Bruhl wrote:

> David,
> I read that it wasn't needed with the XT. Maybe that's wrong.
> I didn't see any chips floating around in the box.
> Tom
>=20
> "EK Sound" <askme@nospam.com <mailto:askme@nospam.com>> wrote in
> message news:43f512f0$1@linux...
> Do you have the PC or MAC rom chip installed?? It comes with =
both 8
> pin DIP's.
>=20
> David.
>=20
> Tom Bruhl wrote:
> > 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...
> >=20
> > 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.
> >=20
> > 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
> > Motu is always sending/returning all 8 ports to and from =
Cubase.
> > Tom
> >=20
> >

--=20
Chris Ludwig
ADK
chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
www.adkproaudio.com <http://www.adkproaudio.com/>
(859) 635-5762
------=_NextPart_000_0228_01C63343.24A3FC70
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>Hey Chris,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It's an old KG7 with USB 1 so I =
invested in a=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>USB2 PCI card to bring it up to USB =
2.  Was=20
that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>wrong?</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>"Chris Ludwig" <<A=20
href=3D"mailto:chrisl@adkproaudio.com">chrisl@adkproaudio.com</A>> =
wrote in=20
message <A =
href=3D"news:43f539d7$1@linux">news:43f539d7$1@linux</A>...</DIV>HI=20
Tom,<BR>  Have you tried it on the motherboards built in =
USB?<BR>It is=20
not a USB 2.0 device so you might be getting some misbehaving from=20
<BR>that.<BR>What motherboard are you =
using?<BR><BR><BR>Chris<BR><BR><BR>Tom=20
Bruhl wrote:<BR><BR>> David,<BR>> I read that it wasn't needed =
with the=20
XT.  Maybe that's wrong.<BR>> I didn't see any chips floating =
around=20
in the box.<BR>> Tom<BR>> <BR>>     "EK =
Sound"=20
<<A href=3D"mailto:askme@nospam.com">askme@nospam.com</A> <<A=20
href=3D"mailto:askme@nospam.com">mailto:askme@nospam.com</A>>> =
wrote=20
in<BR>>     message <A=20
=
href=3D"news:43f512f0$1@linux">news:43f512f0$1@linux</A>...<BR>> =
   =20
Do you have the PC or MAC rom chip installed??  It comes with =
both=20
8<BR>>     pin DIP's.<BR>>=20
<BR>>     David.<BR>>=20
<BR>>     Tom Bruhl=20
wrote:<BR>>      > I purchased this =
(knowing=20
there are driver issues) by<BR>>      > =

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

Report message to a moderator

Re: OT Motu Midi Express XT (USB) If you have experience pleasechime in. [message #64636 is a reply to message #64609]

Fri, 17 February 2006 07:57

EK Sound

Messages: 939
Registered: June 2005

Senior Member

We have that exact unit here and had to swap out the rom chip for it
to work with the PC. Pop the top and look for an 8 pin dip that has a
sticker on the top, it will clearly be labeled MAC or PC. It is
possible that they have developed a generic rom negating the need for
different chips, but it wouldn't hurt to check.

David.

Tom Bruhl wrote:

> David,
> I read that it wasn't needed with the XT. Maybe that's wrong.
> I didn't see any chips floating around in the box.
> Tom
>
> "EK Sound" <askme@nospam.com <mailto:askme@nospam.com>> wrote in
> message news:43f512f0$1@linux...
> Do you have the PC or MAC rom chip installed?? It comes with both 8
> pin DIP's.
>
> David.
>
> Tom Bruhl wrote:
> > 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.
> >
> > 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
> > Motu is always sending/returning all 8 ports to and from Cubase.
> > Tom
> >
> >

Report message to a moderator

Re: OT Motu Midi Express XT (USB) If you have experience please chime in. [message #64651 is a reply to message #64636]

Fri, 17 February 2006 16:25

Tom Bruhl

Messages: 1368
Registered: June 2007

Senior Member

This is a multi-part message in MIME format.

------=_NextPart_000_0024_01C633F7.F0CBE1F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

David,
I looked inside and there are no 8 pin chips that say PC or MAC.
I also didn't see any dip switches. =20

I did talk to Eric at Motu. His take is to eliminate the variables. I =
removed
the USB 2 PCI card and am now using it with the onboard USB 1. So far
so good. I also reinitialized it just to start from ground zero again. =
I may try another
USB cable too. The one I'm using came from Motu.

I haven't reinstalled the software or tried the mute switches because I =
have to much
work to catch up on before I can continue to trouble shoot. I suspect =
there may
be an AMD or mobo issue I'm dealing with here that isn't compatible with
this Motu piece. Who knows.

Thanks for the tips and I'll keep you informed as to my progress.
Tom

"EK Sound" <askme@nospam.com> wrote in message news:43f5f36e@linux...
We have that exact unit here and had to swap out the rom chip for it=20
to work with the PC. Pop the top and look for an 8 pin dip that has a =

sticker on the top, it will clearly be labeled MAC or PC. It is=20
possible that they have developed a generic rom negating the need for=20
different chips, but it wouldn't hurt to check.

David.

Tom Bruhl wrote:

> David,
> I read that it wasn't needed with the XT. Maybe that's wrong.
> I didn't see any chips floating around in the box.
> Tom
>=20
> "EK Sound" <askme@nospam.com <mailto:askme@nospam.com>> wrote in
> message news:43f512f0$1@linux...
> Do you have the PC or MAC rom chip installed?? It comes with =
both 8
> pin DIP's.
>=20
> David.
>=20
> Tom Bruhl wrote:
> > 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...
> >=20
> > 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.
> >=20
> > 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
> > Motu is always sending/returning all 8 ports to and from =
Cubase.
> > Tom
> >=20
> >
------=_NextPart_000_0024_01C633F7.F0CBE1F0
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>David,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I looked inside and there are no 8 pin =
chips that=20
say PC or MAC.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I also didn't see any dip =
switches. =20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I did talk to Eric at Motu.  His =
take is to=20
eliminate the variables.  I removed</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the USB 2 PCI card and am now using it =
with the=20
onboard USB 1.  So far</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>so good.  I also reinitialized it =
just to=20
start from ground zero again.  I may try another</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>USB cable too.  The one I'm using =
came from=20
Motu.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I haven't reinstalled the software or =
tried the=20
mute switches because I have to much</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>work to catch up on before I can =
continue to=20
trouble shoot.  I suspect there may</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>be an AMD or mobo issue I'm dealing =
with here that=20
isn't compatible with</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>this Motu piece.  Who =
knows.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for the tips and I'll keep you =
informed as=20
to my progress.</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>"EK Sound" <<A =
href=3D"mailto:askme@nospam.com">askme@nospam.com</A>>=20
wrote in message <A=20
href=3D"news:43f5f36e@linux">news:43f5f36e@linux</A>...</DIV>We have =
that exact=20
unit here and had to swap out the rom chip for it <BR>to work with the =

PC.  Pop the top and look for an 8 pin dip that has a <BR>sticker =
on the=20
top, it will clearly be labeled MAC or PC.  It is <BR>possible =
that they=20
have developed a generic rom negating the need for <BR>different =
chips, but it=20
wouldn't hurt to check.<BR><BR>David.<BR><BR>Tom Bruhl =
wrote:<BR><BR>>=20
David,<BR>> I read that it wasn't needed with the XT.  Maybe =
that's=20
wrong.<BR>> I didn't see any chips floating around in the =
box.<BR>>=20
Tom<BR>> <BR>>     "EK Sound" <<A=20
href=3D"mailto:askme@nospam.com">askme@nospam.com</A> <<A=20
href=3D"mailto:askme@nospam.com">mailto:askme@nospam.com</A>>> =
wrote=20
in<BR>>     message <A=20
=
href=3D"news:43f512f0$1@linux">news:43f512f0$1@linux</A>...<BR>> =
   =20
Do you have the PC or MAC rom chip installed??  It comes with =
both=20
8<BR>>     pin DIP's.<BR>>=20
<BR>>     David.<BR>>=20
<BR>>     Tom Bruhl=20
wrote:<BR>>      > I purchased this =
(knowing=20
there are driver issues) by<BR>>      > =

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

------=_NextPart_000_0024_01C633F7.F0CBE1F0--

Report message to a moderator

Previous Topic:	PARIS Recorded Sample
Next Topic:	Soooo.....is this stress?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Apr 07 03:45:47 PDT 2025

Total time taken to generate the page: 1.58898 seconds