ok, let me explain the pitfalls to this rule, in case you didn't understand already...
suppose you have a MIDI file that you grabbed from the intertubes somewhere and have these interleaved PC events on the same track or channel.
you may import this very file into qtractor alright, it's a perfect valid SMF no matter it breaks the aforementioned rule or convention though; it might even play well to MIDI instruments for which it was designed for, so those PC's will match their purpose as originally intended--no problem so far...
now imagine you want to edit the MIDI clip under qtractor's piano-roll, change anything to your liking in the original sequence; you're happy with the changes and duly save the clip or session--it is now that the said rule roars its ugly head: it might come to your surprise that all PC events have disappeared from the original sequence, which now resides on a brand new MIDI file that goes for the changed clip.
TL;DR when writing to a MIDI file, qtractor always discards bank_select or program_change's but the ones set up in track properties.
do you understand it now?
hth.
ps. as @GEN-es shows above, you can enter those PC events in the MIDI clip editor, but truth be told, they won't survive the next save operation; they just won't be there the next time you open the session.
ok, let me explain the pitfalls to this rule, in case you didn't understand already...
suppose you have a MIDI file that you grabbed from the intertubes somewhere and have these interleaved PC events on the same track or channel.
you may import this very file into qtractor alright, it's a perfect valid SMF no matter it breaks the aforementioned rule or convention though; it might even play well to MIDI instruments for which it was designed for, so those PC's will match their purpose as originally intended--no problem so far...
now imagine you want to edit the MIDI clip under qtractor's piano-roll, change anything to your liking in the original sequence; you're happy with the changes and duly save the clip or session--it is now that the said rule roars its ugly head: it might come to your surprise that all PC events have disappeared from the original sequence, which now resides on a brand new MIDI file that goes for the changed clip.
TL;DR when writing to a MIDI file, qtractor always discards bank_select or program_change's but the ones set up in track properties.
do you understand it now?
hth.
ps. as @GEN-es shows above, you can enter those PC events in the MIDI clip editor, but truth be told, they won't survive the next save operation; they just won't be there the next time you open the session.