Sorry, combined panner and multichannel panner are not supported, as no ‘simple’ parameters are offered in the MIDI Remote API.
When you use a combined panner, you can only proceed as follows: Adjust the left side with the Rotate Knob and then move the blue panning bar on the screen with the mouse.
Yes, this was a bug. Sorry.
[ Addendum: The zip-file above has been completely updated. The corrections are included there.
The current version date there is now May 2, 2024 ]
Thanks, tommyrack.
I had this idea as suddenly the cycle symbol on the FaderPort somehow reminded me
to a toy-Carrera-racetrack. 
Simply amazing! Loving the new Send feature and the threshold color coding, plus easy rotation from -infinity to 0 to old value. I could go on and on as this is the best controller for Cubase! Thank you so much!
Thanks for your dedication to make this an awsome usefull script !
Just currently downloaded and for now just tried the GTS function.
But I’ll sure welcome the other new features (Send Mode) and I’m always grateful for improvements (though these things never seem to be as attractive as new features).
Now… I got a question about the GTS function:
Would it be possible to temporarily disable the Master Fader as long as the Cycle Button is pressed, so the Fader does not get mad, if I’m not scrolling fast enough ? Of course the Fader then should pick up the Volume Value of the arrived channel, then the Cycle Button is released.
Does this sound useful; is this possible ?
BTW: I did vote for this topic - but what does this actually mean (sorry, if this is a dumb question) ?
Wish you well
Thanks for your feedback, losanF.
That’s exactly what I was thinking also at first. 
But in my case, however, when I turn the Rotate Knob at normal speed while performing GTS,
my Motorfader is not constantly updated. That’s why I thought it was okay.
Now it may be that your Motorfader is faster than mine,
perhaps even because you have a newer device…(?)
OK.
I have now programmed it into the script,
so that the motor is switched off as long as the Cycle Button is pressed.
Maybe you can try it out to see if it works better for you.
If it is also better for the others here, I can leave this change in the script permanently for everyone.
Here is a script version with the change in the zip-file:
[ Addendum: The zip-file above has been completely updated. The corrections are included there.
The current version date there is now May 2, 2024 ]
Works better for me also, I think is an improvement.
I have a suggestion, for the Pan mode, when in shift mode (maybe even without shift, that I see it toggles monitor state as other modes), pressing the knob could reset the Pan to center?
The Pan Mode is available on the Main Paige.
To set the pan value to center, you have to repress the Pan Button.
This is a general, consequent conceptual operation that you reset everywhere in the script to the default values (incl. center) via a button repress.
Really awesome upgrade! Was waiting for Send mode. It is a game changer as many new features.
Just want to confirm that there is no way of making channel fader active while being in Send mode. If it would have been possible - it might have become my default mode for FP.
Oops. It should not be like this. Sorry.
You’ll find another patch here tomorrow with that fixed.
Then the Fader will also work in the Send Mode and in the Cue Send Mode as usual.
Here’s the patch for it… 
[ Addendum: The zip-file above has been completely updated. The corrections are included there.
The current version date there is now May 2, 2024 ]
new update available - May 2, 2024
Hello friends,
the latest corrections are now all included in the zip-file above.
Best regards
CKB (Christian)
What I like best is that you never have to think about which knob to turn, as there is only one.
Hi there,
I really appreciate that you’re taking into account to suggestions !
Quite busy at the moment, so not much time to check everything else than the GTS function right now - as it is right now - to my taste this is an improvment.
But ( sorry to be such a pain in the ass…) - you wrote it should function regardless in which mode you’re in - it works as expected in pan mode, also in Master Mode, also when Click enabled - but not with Channel, Scroll, Section and Marker (these are the ones I checked in the Main page - maybe more affected which I currently have not thought of/tried (on the Shift Page ?)
On a side note - you left out the Link Button in your Documentation (overview and all) ?
Anyway, thanks for your work again - and I’d also like to take the opportunity to thank WEM to initially start this all !
Kind regards,
Frank
Hi Frank,
On a side note - you left out the Link Button in your Documentation (overview and all) ?
You find the description of the Link Button in the Overview now on the left in ‘landscape style’ in the Middle Section, because some space had to be created on the side.
Hi Frank,
I have now actually found a (Steinberg) bug.
If the ‘Markers Window’ is open and has the focus, the Mute function does not work within the GTS function when the Rotate Knob is pressed. If the focus is back on the Project Zone, it works again.
Maybe this was also your observation error?
With MIDI Remote, there are two ways to switch the Mute Status, either as a track property or as a command. I had used the command method within the GTS function, but there seems to be a system bug from Steinberg in there that I can’t change. Now I have reprogrammed it so that the GTS function changes the track property and - here it works.
If the cause in your case was something other than opening the ‘Markers Window’ with focus, the problem could also still be solved now.
Best regards
CKB
Here’s the patch for it…
[ Addendum: The zip-file above has been completely updated. The corrections are included there.
The current version date there is now May 2, 2024 ]
Correct me if I’m wrong, but I don’t believe this requires any particular implementation on the plugin side. Quick Controls in Cubase is just a mapping of exposed VST Parameters within Cubase. In other words, if a plugin has parameters you can automate, you can also map them to QCs.
You’re right.
A plugin can support - if the manufactorer programmed it - the VST 3 Interface like this:
And within Cubase this can be mapped to a Quick Control.
My tip to all if you are not happy if your plugin does not work as desired with Cubase:
It’s best to write a comment on a public page that the manufacturer of the plugin also reads, e.g.
“Too bad, I actually think this plugin is very good, but since it doesn’t support Cubase properly, I won’t buy it, but another one.”
Then the manufacturer is most likely to be motivated to improve the plugin for use with Cubase and make the AI functionality, etc. available.
Hi,
could not respond earlier - was at work.
Nice find, but I have not even tried the GTS Mute function 
I should have described my observation more precise…
Well, I didn’t mean, that you could not scroll through the channels.
This does work. Also the temporarily Disabling of the Master Fader works.
But what does not work in all modes is that the Fader picks up the Volume Value
of the arrived channel.
Of course most obvious if the channel faders are all set different.
It works in Pan Mode, Master Mode and EQ Mode,
but for whatever reason not in the other modes.