T
Tripecac
New member
In Sonar 1.3.1, the PATCH (Pch) number was the second MIDI track parameter.
This let me make each track two rows high, and still be able to see the
patch associated with each MIDI track.
In Sonar 2, VOLUME (Vol) always comes first, and the PATCH (Pch) number is
8th on the ALL view, 5th on the I/O view. This forces me to increase the
height of each MIDI track, or the width of the track properties area in
order to be able to see the Patch for each MIDI track. It also makes it
hard to quickly see the patch parameter *and* is more error-prone (since
more parameters are visible and can therefore be accidentally adjusted).
The Sonar 2 manual shows "Pch" as still being second, after the Channel
number [see page 106]. This leads me to believe that maybe this re-ordering
of track parameters is a bug which will be fixed or is something we can adjust.
My questions are:
1) [How] can I get the MIDI patch number to be the second track parameter,
like it was in Sonar 1.3.1?
2) If I can't fix it now, do you think it will be fixed in the next Sonar
patch? [Is this a "known issue"?]
Thanks!
Travis
This let me make each track two rows high, and still be able to see the
patch associated with each MIDI track.
In Sonar 2, VOLUME (Vol) always comes first, and the PATCH (Pch) number is
8th on the ALL view, 5th on the I/O view. This forces me to increase the
height of each MIDI track, or the width of the track properties area in
order to be able to see the Patch for each MIDI track. It also makes it
hard to quickly see the patch parameter *and* is more error-prone (since
more parameters are visible and can therefore be accidentally adjusted).
The Sonar 2 manual shows "Pch" as still being second, after the Channel
number [see page 106]. This leads me to believe that maybe this re-ordering
of track parameters is a bug which will be fixed or is something we can adjust.
My questions are:
1) [How] can I get the MIDI patch number to be the second track parameter,
like it was in Sonar 1.3.1?
2) If I can't fix it now, do you think it will be fixed in the next Sonar
patch? [Is this a "known issue"?]
Thanks!
Travis