<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>This is my experience as well, I actually went back
to using a serial port midi interface because every USB one I tried had timing
glitches galore. I've seen better USB midi interfaces lately with
timestamping etc, but I still hear a lot of people complain about timing of
external midi modules when played with audio or VSTi on the computer, MAC and
PC, which may have something to do with all the internal delay compensation or
some other internal process to deliver the goods, so a lot of talk of shifting
midi notes in the sequencer app, and just bouncing to audio as soon as possible,
as Jason Proctor mentioned.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Perhaps it is something to do with MIDI being such
an old protocol, the older gear was developed or built when it was still fairly
related to the current technology, so the hardware integrated well with it, now
the new stuff has advanced in leaps and bounds yet midi is still back in the
80's, so it's more like legacy support on the part of hardware manufacturers, so
it's specialty markets and peripherals that handle it, but the timing is left up
to hardware designed for a multitude of tasks and the software does what it can
with it. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I don't know I'm just
wondering.</FONT></DIV></FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=rude66@gmail.com href="mailto:rude66@gmail.com">rude66</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=debus@cityweb.de
href="mailto:debus@cityweb.de">Ingo Debus</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=synth-diy@dropmix.xs4all.nl
href="mailto:synth-diy@dropmix.xs4all.nl">SynthDIY</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Saturday, May 06, 2006 1:08
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [sdiy] Atari latency,
was:Camel*ont* soft Da synth!</DIV>
<DIV><BR></DIV>the way i always understood it, is this: in the atari, midi is
built into the OS, it's all there right from the beginning. on a pc, midi is
not a native part of the os or the hardware, it always has to be translated
via usb/pci/ whatever. i have no idea about the technical or programming side
of things when it comes to this though.<BR><BR>however, i have to say that on
my atari (a mega ste) i never ever ever had timing problems. rock solid. on
every damn pc i had, even though both hardware and software were supposed to
be about 1000 x more superior to the st hardware/software, i've ran into all
kinds of crap. especially when syncing 3 drum machines and arpeggiators via
midi clock, it can be an absolute nightmare. my hardware is fine, because when
i use the good old alesis mmt8 as a clock master, everything is supertight.
<BR><BR>and i'm not the only one who experiences this: i know guys who have
super pro studios but still use the ST for midi sequencing.
<BR><BR>r./<BR><BR><BR><BR>
<DIV><SPAN class=gmail_quote>On 5/6/06, <B class=gmail_sendername>Ingo
Debus</B> <<A href="mailto:debus@cityweb.de">debus@cityweb.de</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><BR>Am
04.05.2006 um 19:00 schrieb elmacaco:<BR><BR>> Yes, the Atari Machines
are known for both their tight timing and<BR>> low midi<BR>> latency,
I rarely hear about the midi latency because it seems non<BR>> existent.
<BR>><BR><BR>Hm, what *is* latency here? How is it defined?<BR><BR>On a
(hardware or software) synth, latency is the time between the<BR>arrival of
the MIDI message and the actual starting of the sound. But<BR>we're talking
about the Atari ST, thus certainly not about a soft <BR>synth, correct? What
does latency mean for a MIDI sequencer? The<BR>difference between the time
stamp value recorded along with a MIDI<BR>event and the actual time when
this event occurred? As long as this<BR>'latency' is constant, it could
easily be compensated by the <BR>sequencer program.<BR>And even if it
couldn't, what's the difference between "tight timing"<BR>and "low MIDI
latency" then?<BR><BR>Ingo<BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>