well the greater the bandwidth the less likely it is that the computer will need to send a timing byte down the wire whilst it is also sending note data, so the less likely it is that any messages will be sent late because they had to wait for previous messages. i am just making this up as i go along, but the midi standard runs at 31,250 bps according to Wikipedia which means that if a note on message is being transmitted which iirc is 3 bytes then we'll have to wait 30 bits (the midi spec adds two extra bits per byte i think) of data before we can send the midi clock message which is 30/31250 = 0.00096s which is almost a millisecond. i think that's right :S On 10/3/06, Tony Scharf <tony@...> wrote: > > Which begs another question. How will it effect timing issues? I mean, > if Cubase is still putting out MIDI clock at the same rate, using > standard midi format, how is the driver for the turbo-midi device going > to somehow improve that? > > something about this just doesnt add up in my head. > > Tony > > Edward George wrote: > > > > > > well the midi specification bit may be a bit misleading? though there > will > > be a completely different protocol (no status bit maybe) surely any > changes > > to the data layer aren't going to need a new piece of hardware, it must > be a > > change at the physical level. Somebody mentioned something once about > using > > all the pins, maybe they're running their own parallel data stream over > a > > connection that is normally just serial or something? i dunno! I'll > > definately be having a peek at the stream when mine arrives :) > > > > > -- --------------------------------------------------- No Software Patents No Digital Rights Management [Non-text portions of this message have been removed]
Message
Re: [elektron] Turbo midi : so what ?
2006-10-03 by Edward George
Attachments
- No local attachments were found for this message.