Emu XL-7 & MP-7 User's Group

Output of the sequencer is bounded by the latency of the synthesiser. 
Tracks are processed in numeric order, from 1 to 16 for all events up
till the current tick.  Firing complex synth notes can take a while
(relatively speaking) as opposed to sending MIDI notes which takes
really no time at all (from the sequencer's point of view).

Moral of the story?  Put your external tracks first if you can, cause
they won't affect timing at all.  After that, put the most important
timing critical tracks next (like drums, especially since they're
usually simpler patches).  Next put important melodic stuff, and
finally put fluffy stuff like pads last.

-Aaron

PS.  tons of controller data can chew up MIDI bandwidth, but internally
takes very little processor power.

PPS.  arps unfortunately have a lower priority than ALL of the
sequencer, so those'll get sloppy first.  You can record them with a
loopback cable if you want...  (yeah, I know it's a kludge)

PPPS.  MIDI A vs B out makes no difference.  (bonus trivia: on a
Proteus2000, the A *input* has a higher priority than the B input.)

--- mike <curiousproductions@...> wrote:
> I think that in the xl the midi priority starts from track one and 
> moves down the line.  At least that is what i rember reading.  
> 
> Am i to take it the Midi B outs are way down the line then? or as 
> least come in sequence after the A outs?
> 
> Trying to keep midi timing as tight as possable is all.
> 
> Please give a shout if ya know the answer to this one.  And just a 
> general question, how do you all find the timing on this box?  I feel
> that at times it gets kinda sloppy when i have arps going and what 
> not.
> 
> Mike G.

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree