Firstly, I want to express my gratitude for the development of CS Control. I believe it will significantly enhance my workflow, work ethic, and overall morale!
I have been using Mulligan to leverage the hardware faders and non-endless knobs on my budget controllers for mixing, benefiting from its "Soft Takeover" mode. However, I find the modular design of your CS Control package to be much more practical, as Mulligan’s limitations can often be quite frustrating.
With that in mind, I would like to inquire whether there are any plans to introduce a similar "Soft Takeover" feature, or if there is currently a way to achieve this within Soundflow. Gaining clarity on this would greatly assist me in determining whether to invest in CS Control and continue my use of Soundflow.
Thank you for your time and consideration!
- SSoundFlow Bot @soundflowbot
Thanks for posting a question or an issue related to the 'CS Control' package.
This package is made by @Chris_Shaw. We're auto-tagging them here so that they will hopefully be able to help you.Please note, that the best way to get help with a script, macro or other content installed from the Store is to select the script you installed, then click the red Need help button, and then click "Get help with this script or macro".
By using this workflow, the developer of the package will get access to more information so they'll be able to help you quicker.
You can read more about how to best get help in this article: bit.ly/sfscripthelp 
In reply toJake_Morton⬆:Chris Shaw @Chris_Shaw2024-09-24 17:16:22.207ZHey @Jake_Morton.
By "soft takeover" I'm assuming you mean the ability to use standard CCs that send the values 0-127.
I tried to make using standard CCs work with CS Control but it severely limited its functionality. There's a detailed explanation in the documentation under "MIDI Controller Requirements".
The main issue is that CS Control does not communicate with a plugin directly to ascertain knob positions and button states. It converts CC movements to mouse scroll wheel events so it has no way of knowing when a knob has reached its minimum, maximum, or even what position it's in. I've experimented with using a QWERTY modifier key that would block CCs to CS Control so one could move a knob back or forward when it has reached it's upper or lower range but I'm using most modifier key combinations to implement fine control and other functions.
You might want to look at this thread from another user who manged to get CS Control working with a standard CC controller using a 3rd party MIDI translating app. YMMV:
Midi Knobs Direction #post-6- JJake Morton @Jake_Morton
Hey Chris,
I hope you’re doing well!
Thank you for sharing your thoughts and confirming my assumptions. I really appreciate you taking the time to point me toward some potential solutions.
Regarding the "soft-takeover" concept, you’re absolutely right. I’d like to use unmotorized MIDI faders and basic 0-127 potentiometers to control various elements. Sorry for not making that clearer earlier!
Thanks again for your help!
Cheers
- Jake