Hey Chris,
I've been demoing CS Control and trying to get it functioning for the last couple days to no avail. Maybe you can help.
I had the same issue as another user here where CS Control would only detect the first knob of the Midi Fighter Twister. As a means of troubleshooting, I tried different firmwares from the MFT Utility. Once I did that, then the first knob also stopped working. So I did a factory reset (I've done a few more resets since). I went back into the CS Control script and, since the MFT changed the name to "Midi Fighter Twister 2," I selected it accordingly.
It's since been changed to Midi Fighter Twister 3 (as is shown in the screens below). Here is the list of steps I'm going through, including screenshots of my settings:
First, I'm going to the CS Control Midi Input script and following the directions. Here's my settings:
Once this information is set, I close that window, then I go to the "Start" tab in SoundFlow, then I click on the CS Control app to launch it. Once it loads, I go to the "Configure" tab, double click on Knob1's CC#0, turn the knob and nothing happens.
If I try to reset the number of controller knobs and buttons to 4 each, this is the error that comes up once clicking the save button:
Here are my other screenshot settings, which are set for all 4 pages on the MFT:
I tried going through by hand, clicking every single knob and making every single knob and button the same MIDI Channel 1 and it didn't do anything to resolve the issue. It was tedious and painful, and I regret having to jump through all of those hoops if I'm being honest. All that, to end up resetting the MFT to factory settings once again, and I still appear to be in the same situation as before.
I'm at a loss and I really want this to work. :-)
- 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 toStephen_Sechler⬆:Chris Shaw @Chris_Shaw2024-02-10 04:47:57.513ZHey @Stephen_Sechler,
Sorry that you're having problems with the app.
IT isn't necessary to set every knob and button (all 64 of each) on the MF to the smae channel, just the ones you are using (usually 16 of each).I'd like to get more info if possible. I need to know which version you're using at the moment so I can check the code for any issues.
Also, I need to get the logs from the app. Try running CS Control again and when it fails, run the "Collect User Logs" script in the package. This will place a ZIP file on your desktop. Upload to your file sharing service of choice (DropBox etc) and post the link here.
I'll have a look sometime tomorrow.- SStephen Sechler @Stephen_Sechler
Thank you Chris for the reply and the willingness to assist.
I have narrowed it down to where any knob works, as long as it's assigned to MIDI #0. If I then change the knob back to another MIDI number in the MFT Utility, such as CC# 121, for example, it will no longer detect in CS Control. I change the CC# back to 0, and it detects again.
I don't know how the code works, but it seems like maybe anything less than 1 is valid, and anything above 1 is invalid.
Chris Shaw @Chris_Shaw2024-02-10 22:02:10.315ZHmm, that seems really weird.
Could you send me a copy of your MFT settings? Open the MF Utility app and use "File > Export" to export you settings, post them to a file sharing service and post the link here.
That way I can load it into my MFT to try to reproduce your issue.
Post your User Logs when you have the chance too.- SStephen Sechler @Stephen_Sechler
Chris! I got it working! I didn't see in the instructions to hit the "record" button at the bottom of the MIDI Input trigger script, but I saw in one of your videos you hitting the button, so I tried that. It didn't resolve the issue the first time and I think it's because there's this popup box that says something about how this program needs to open, then it has a launch button. The thing is, the MIDI CC # needs to be switched back to "All CC" prior to clicking the launch button, since it changed itself after pressing record and turning the knob.
Inside the MF Utility, the "multiple" button doesn't appear to have MIDI Channel as one of the options to change several knobs at once. Therefore, I went ahead and did it manually (midi channel 1) for all 64 knobs and buttons, and wanted to share it, in case you or anybody ever wanted to use all 4 pages of knobs (0-63) and then 4 pages of buttons (64-127) without having to manually go through and set each one by hand again:
The key takeaway here (to anybody in the future reading this and having this issue) is that if the knobs aren't working, definitely click the record button and move the knob, even if everything is entered manually on the script and looks correct. Then change the MIDI CC # back to "All CC" prior to pressing the "launch" button.
- Chris Shaw @Chris_Shaw2024-02-11 05:13:55.055Z
Glad you worked it out!
Thanks for detailing the solution.