Skip to main content

Staggering the event list to MIDI instruments

Posted

Thanx Andre - 

 

I see you did stagger the contrel set up events. Thanx

 

You should consider moving all CC events to measure 0 because you can't send a CC event on the same clock count as a note and expect it to work. (measure 1, clock 1) It might occassionally be correct.  I'm guessing, but I'd say the average kbd, can handle a dozen or so l of CC events on one clock, especially if the tempo is slow.  But multiplying that by 16 MIDI channels.  and some of the CC's will get lost. 

 

I included a 2nd control sequence I use for you to check out .  I have these set up in Logic already for each channel and just change the MSB/LSB/Prog.For it to work most effectively, Each event for each channel must be staggered to insure, the kbd gets everything right.  So MIDI channel 1 would be -  Measure 0 clock 1 (you put 2 clock counts to seperate events  - thats fine) but then MIDI channel 2 should start on something like measure 0 clock 20, MIDI 3 - measure 0 clock 40.  etc.

 

Note - The way SFP (build 1.6.3). exported MIDI files fine, Tyros 4 got MSB/LSB/PROG fine. But make the other controllers still be in measure 0 also. . I would probably add more parameters (reset channel, pitchbend 0, Attack,Delay, Release times, chorus, detune, etc)  to fine tune that particular instrument more.  

 

Often once I get 16  - 20 tracks coming out of Tyros,  the event times of CC's and program changes become critical. . Especially when there's modulations, pitchbend etc. Cause patch changes won't always be consistant.  or a note off gets lost, cause Logic was sendinig out a lot of CC's on other channels. And of course older kbds, with slower proccessors, will have more issues. 

 

But all CCs should be in measure 0.  If the song starts with a pick up I leave it in measure 0, so that it's easy to calculate verses, chorus's, bridges, Measure 1, 9, 17, 32, 65.  And a score will print out

 

Thanx 


Thu, 2012-10-18 - 09:58 Permalink

Program selection (MSB/LSB/PRG) is staggered in the lead-in now, yes.

Standard MIDI CC (Volume, Reverb, Pan, Sustain) come from parameters and these start with the actual song. This could not be changed. These CC are also constantly changing during playback, so they should not have a noticeable latency, unless the hardware is really flawed.

If your hardware needs these CC in advance, set the parameters in your root container and have music start one measure later. It is always good to keep the "default mix parameters" in the root container anyway.

We plan on adding a pre-roll to the arrangement, so measure couting can be offset by a lead-in bar. This will make an arrangement start at, for example, measure -1, where you can put all those things.

Thu, 2012-10-18 - 16:46 Permalink

OK.  Thanx - Yes, I've learnt from experience having 16 channels receive CC's on clock count one, and midi notes on clock count one, works intermittantly.  Some most notes make it, some will lose part of the CC data (like LSB).  The machine does not have a processing speed capable of handling (16 MIDI channels X 8 events) 128 events on one clock count and do whatever else it needs to do. I doubt there is any kbd that could do this with a moderate to fast tempo.