Re: [Qtractor-devel] More serious Pgm Change bug

[Rui N. C. <rn...@rn...>]

On 04/03/2015 01:37 PM, Ralf Mardorf wrote:
> PS:
>
> And what, if the MIDI interface at start position is on heavy traffic
> and data for some channels could be send at later positions to avoid
> unneeded traffic? Most of the times it's possible to add an empty bar at
> the beginning, but that can't be done always. If it can't be done, it's
> important to move program changes and similar stuff to later positions
> in the timeline when ever possible.
>

MIDI traffic is NOT the problem per se.

whet you are probably thinking of is that (some old, the older the 
worse) MIDI instruments, as actual sound generators, synths, samplers, 
whatever, due to their sole electronic/mechanical/digital 
implementation, might react in a non negligible extent of time for such 
MIDI setup messages, like bank_select, program_change, (N)RPN, sysex, 
etc., and the effects of which might not be immediately available or 
evident--that's why all performance events are/were usually delayed a 
bar or so after the instrument setup data.

of course this has nothing to do with the MIDI spec "tout couer" but it 
is/was a pragmatic convention, good practice and/or recommendations for 
GS/XG sequencing from which qtractor followed suit and enforced in its 
design model as a MIDI sequencer.

again, as said earlier, you can have program_change events interleaved 
in the sequence whenever you like, provided the imported MIDI file was 
assembled elsewhere but on qtractor. the issue arises when qtractor deos 
re-create/re-write the MIDI file seguence, where it always inserts the 
MIDI track instrument parameters (bank_select, program_change) at the 
beginning (at BBT=1.1.0000) of the corresponding channel sequence.

again, this is NOT a BUG. rather it's WAD, working as (long ago) designed.

byee
-- 
rncbc aka. Rui Nuno Capela