I think the one instrument one track approach is much more organized.
For the limit of 16 instruments, Qtractor gives us the midi bus tool.
If we didn't have midi buses, we would say please implement them, it is chaos to have several instruments on a track.
(I think sometimes we don't even know what we want :) )
On the other hand, I don't understand Rui's answer either.
Because apparently Qtractor does support "Program Change".
But it is not done from the track properties, but from the midi editor, which is its place since it is a midi event.
@DavidJS I mention it in case you want to experiment with this.
I also tell you that I have never used it, and if Rui says that Qtractor ends up discarding that data, there has to be a reason.
But if so, it is logical that this option would not be available.
Someone could use it and find that their "Program" edits are lost afterwards.
I already told you, it was not clear to me.
If Rui can explain it better, just out of curiosity.
I think the one instrument one track approach is much more organized.
For the limit of 16 instruments, Qtractor gives us the midi bus tool.
If we didn't have midi buses, we would say please implement them, it is chaos to have several instruments on a track.
(I think sometimes we don't even know what we want :) )
On the other hand, I don't understand Rui's answer either.
Because apparently Qtractor does support "Program Change".
But it is not done from the track properties, but from the midi editor, which is its place since it is a midi event.
@DavidJS I mention it in case you want to experiment with this.
I also tell you that I have never used it, and if Rui says that Qtractor ends up discarding that data, there has to be a reason.
But if so, it is logical that this option would not be available.
Someone could use it and find that their "Program" edits are lost afterwards.
I already told you, it was not clear to me.
If Rui can explain it better, just out of curiosity.