MIDI Track Controls Issue

I have used the feature MIDI Track Controls feature to link the volume/pan controls to MIDI instead of the default audio. I noticed that the default for the slider fader is 127 (the max for midi velocity) and yet there is still room to move the slider to it's maximum position. Is there something I am missing or is the slider default value wrong and there is a bug? Many thanks in advance.

Sorry I wasn't clear. If you create a track in the TCP and right click on it, there is the menu option "MIDI Track controls". Within that menu option you can select "Link Volume/Pan to MIDI channel". When I do this, I notice the fader volume default is set at the max volume 127, but yet there is still headroom to move the fader up. I hope that makes sense. I have tried this for the first time and this is doesn't seem to be behaving like it should. Unless I am missing something?

I think that's just the way the devs implemented it. By default (if you use it as a volume fader) it also goes higher than 0db. Now if you change it to a Midi fader 0db=127 and as there's nothing above 127 in Midi, there's still room to the top doing nothing. That would be my explaination, could be wrong though. I think it should behave 'correctly' if you change the volume fader range in Preferences/VU Meters/Faders to a max of 0db, but haven't tested this myself.

I think the DudeMeister is talking about the options in main menu (or track context menu) Track -> MIDI track controls -> "Link volume/pan to MIDI...". with that you can use the track's volume and pan sliders to control MIDI CC7 and CC10. Yes, volume sliders in MIDI mode max out with value 127 at where zero dB normally is, so there is a range above that line lost for MIDI control. I faintly remember it had some reason... something to do with the fact that the sliders don't just send volume values (and slavishly move when CC7 passes through them), but can also offset existing CC7 values that pass through - which is really nifty. Basically the reasoning was they need to be at 127 when you reset the slider to unity or something like that. But it sure is awkward. Track sends in MIDI mode have the same oddness. The whole thing desperately needs users and discussion to be improved (imo mainly on the set-up side, but this issue -though minor - is itching me a bit as well). Although there were many people requesting this, it somehow doesn't get much attention now that it's there. But people should really put it on the test, it's worth to try it open minded, because it has that special twist in that you can eg have a pan CC10 automation on your items and still use the MIDI pan sliders on the track to shift that movement around. As if there were two layers of CC10 on the same MIDI channel ;). EDIT: Wow! Did it really take me almost half an hour to submit this post? How time flies :)

[OT] Gofer, I love that you're always here to "get up stand up, stand up for our Midi rights", seriously. :) [/OT]