The PARIS Forums


Home » The PARIS Forums » PARIS: Main » MIDI Brain Power Needed!
MIDI Brain Power Needed! [message #67324] Mon, 24 April 2006 23:44 Go to next 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_0021_01C66812.1CA986D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I exchanged the Motu 8x8 for the MidiMan MidiSport 8x8.
I will install the drivers tomorrow. This is round two.

I wonder if it would be any faster regarding MIDI latency to
install a MIDI card into my Cubase rig and use the MidiSport as
a stand-alone (no USB connection)? I could then run MTC to Cubase=20
via a MIDI cable. I know I would forfeit 128 Midi channels for 16 by =
doing this. =20
Most of my work I think will be softsynths anyway though.

I know MIDI is slower than USB 2 but something tells me that
there may be something more stable if not even quicker to use
the MIDI line sending MTC into Cubase? I know it would usually be=20
combined with note and controller data from a controller which seems =
like=20
a log jam waiting to happen. =20

I am jaded by my experience with the Motu piece and it's inability to =
deal=20
with sysex and it's flakey software. =20

Wadaya think?
Tom



------=_NextPart_000_0021_01C66812.1CA986D0
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 exchanged the Motu 8x8 for the =
MidiMan MidiSport=20
8x8.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I will install the drivers =
tomorrow.&nbsp; This is=20
round two.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I wonder if it would be any faster =
regarding MIDI=20
latency to</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>install a MIDI card into my Cubase rig =
and=20
use&nbsp;the MidiSport as</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a&nbsp;stand-alone (no USB=20
connection)?&nbsp;&nbsp;I could&nbsp;then&nbsp;run MTC </FONT><FONT =
face=3DArial=20
size=3D2>to Cubase </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>via a MIDI cable.&nbsp; </FONT><FONT =
face=3DArial=20
size=3D2>I know I would forfeit 128 Midi channels for 16 by doing =
this.&nbsp;=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Most </FONT><FONT face=3DArial =
size=3D2>of </FONT><FONT=20
face=3DArial size=3D2>my work I think will be softsynths anyway =
though.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I know MIDI is slower than USB 2 but =
something=20
tells me that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>there may be something more stable if =
not even=20
quicker to use</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the MIDI line sending MTC into =
Cubase?&nbsp;=20
I&nbsp;know it would&nbsp;usually be </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>combined </FONT><FONT face=3DArial =
size=3D2>with note=20
and controller data from a controller which seems like </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a log jam </FONT><FONT face=3DArial=20
size=3D2>waiting&nbsp;</FONT><FONT face=3DArial size=3D2>to =
happen.&nbsp;=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am jaded&nbsp;by my experience with =
the Motu=20
piece and it's </FONT><FONT face=3DArial size=3D2>inability to deal =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>with sysex and it's flakey =
software.&nbsp;=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Wadaya think?</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>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0021_01C66812.1CA986D0--
Re: MIDI Brain Power Needed! [message #67326 is a reply to message #67324] Tue, 25 April 2006 00:09 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_0048_01C66815.B57BA8E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

PS I had around 7-8ms latency with rock solid timing with the Amiga, =
MIDI Clock=20
and SMPTE all hardwired. Never any variance. Is this asking too much =
with the
new USB MIDI world? I was expecting better with these newfangled toys. =


But No-o-o-o-o-o-o-o!,
T.

PPS Maybe I should install the drivers first huh?



"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:444dc443$1@linux...
I exchanged the Motu 8x8 for the MidiMan MidiSport 8x8.
I will install the drivers tomorrow. This is round two.

I wonder if it would be any faster regarding MIDI latency to
install a MIDI card into my Cubase rig and use the MidiSport as
a stand-alone (no USB connection)? I could then run MTC to Cubase=20
via a MIDI cable. I know I would forfeit 128 Midi channels for 16 by =
doing this. =20
Most of my work I think will be softsynths anyway though.

I know MIDI is slower than USB 2 but something tells me that
there may be something more stable if not even quicker to use
the MIDI line sending MTC into Cubase? I know it would usually be=20
combined with note and controller data from a controller which seems =
like=20
a log jam waiting to happen. =20

I am jaded by my experience with the Motu piece and it's inability to =
deal=20
with sysex and it's flakey software. =20

Wadaya think?
Tom



------=_NextPart_000_0048_01C66815.B57BA8E0
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>PS&nbsp; I had around 7-8ms latency =
with rock solid=20
timing with the Amiga, MIDI Clock </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and SMPTE </FONT><FONT face=3DArial =
size=3D2>all=20
hardwired.&nbsp; Never any variance.&nbsp; Is this asking too much with=20
the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>new USB MIDI world?&nbsp; I was =
expecting better=20
with these newfangled toys.&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>But No-o-o-o-o-o-o-o!,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>T.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>PPS Maybe I should install the drivers =
first=20
huh?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</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" &lt;<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>&gt; wrote =
in message=20
<A href=3D"news:444dc443$1@linux">news:444dc443$1@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I exchanged the Motu 8x8 for the =
MidiMan=20
MidiSport 8x8.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I will install the drivers =
tomorrow.&nbsp; This=20
is round two.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I wonder if it would be any faster =
regarding MIDI=20
latency to</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>install a MIDI card into my Cubase =
rig and=20
use&nbsp;the MidiSport as</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a&nbsp;stand-alone (no USB=20
connection)?&nbsp;&nbsp;I could&nbsp;then&nbsp;run MTC </FONT><FONT =
face=3DArial=20
size=3D2>to Cubase </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>via a MIDI cable.&nbsp; </FONT><FONT =
face=3DArial=20
size=3D2>I know I would forfeit 128 Midi channels for 16 by doing =
this.&nbsp;=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Most </FONT><FONT face=3DArial =
size=3D2>of=20
</FONT><FONT face=3DArial size=3D2>my work I think will be softsynths =
anyway=20
though.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I know MIDI is slower than USB 2 but =
something=20
tells me that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>there may be something more stable if =
not even=20
quicker to use</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the MIDI line sending MTC into =
Cubase?&nbsp;=20
I&nbsp;know it would&nbsp;usually be </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>combined </FONT><FONT face=3DArial =
size=3D2>with note=20
and controller data from a controller which seems like </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a log jam </FONT><FONT face=3DArial=20
size=3D2>waiting&nbsp;</FONT><FONT face=3DArial size=3D2>to =
happen.&nbsp;=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am jaded&nbsp;by my experience with =
the Motu=20
piece and it's </FONT><FONT face=3DArial size=3D2>inability to deal =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>with sysex and it's flakey =
software.&nbsp;=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Wadaya think?</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>
<DIV><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML >

------=_NextPart_000_0048_01C66815.B57BA8E0--
Previous Topic: Apples
Next Topic: What to do . . . what to do . . .
Goto Forum:
  


Current Time: Sun Jun 23 23:49:46 PDT 2024

Total time taken to generate the page: 0.15642 seconds