Use plugin map on any instance of that plugin?
I'm enjoying CS control, but I'm finding the map I create for a plugin only works on that instance of the plugin.
If I create a map for a plugin (bx SSL9000 channel strip in this case), should any new instances of the plugin be mapped automatically, including installing the plugin in a new Pro Tools session? Or do I have to make a map for every instance I place on a session?
Thanks,
JS
- Chris Shaw @Chris_Shaw2025-04-05 14:12:12.844Z2025-04-07 23:31:08.425Z
hmm, you shouldn't have to do that.
Could you run the "Collect User Logs" script, which will put a zip file on your desktop, put it up on your preferred file sharing service and post a link to it here?Also which versions of CS Control and SF are you running?
- JJustin Smith @Justin_Smith
Sorry for the late reply. Haven't had time to dig into this this week! I am on Soundflow5.10.1, and CS Control 1.0.15. A user log is here:
https://www.dropbox.com/scl/fi/wn2n30u29s3k5wiz3ejs3/Justin-Smith-CS-Control-User-Files-2025-04-10-19-01.zip?rlkey=ljdz8s6h293qzidut77rtehq8&dl=0Just before I ran the user log script I installed an instance of BX Console 9000 J channel strip and tried to control it with the Twister, but got no repsponse. Under Bank Name it says it is an unnamed plugin. But it is able to control the same plugin on a different track in the session. That's the instance I originally mapped.
This is in Pro Tools 2024.10 on a Mac Mini running Sequioa
thanks,
JustinChris Shaw @Chris_Shaw2025-04-12 19:13:04.451Z
Hmm, everything seems to be in order but for some reason your plugin map isn't being saved.
Could you check under System Settings > Privacy and Security > Full Disk Access and verify that SoundFlow is checked?Chris Shaw @Chris_Shaw2025-04-12 20:25:56.231Z
I've also updated the package (1.0.16) but these were small updates not related (or at least shouldn't be) to your issue.
Once it' approve by the SF team it should be in the store (it may take a day)
Let me know if this resolves the issue- In reply toChris_Shaw⬆:JJustin Smith @Justin_Smith
Turns out, full disk access for Soundflow was off. I changed that and updated. It did not work at first, but when I re-mapped the plugin I have been trying to control it did begin working correctly, on any instance I open up. Great!
I'm not sure how full disk access got switched off. I'm pretty sure I went through all the optimizations need for Soundflow. Thanks for your help.Chris Shaw @Chris_Shaw2025-04-16 04:31:53.097Z
There have been some problems with some MacOS versions not retaining disk permissions.
Thanks for reporting back
Glad we got it sorted!