-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to name Carla Patchbays #1568
Comments
why not simply use patchbay instances as plugins inside carla? |
I want to load/unload any patchbay at any time from scripts/hotkeys, so each patchbay would need its own Carla instance, which means I end up with two Carla windows per fx chain, which is kinda ugly and can lead to worse overview. Also, a command line option makes it more flexible by being able to set adaptive names when launching. |
Well I dont have that implemented now, but env var is. So this will work just the same:
|
I ran into a similar use case and noticed it only sometimes worked. I need predictable names for my inputs and outputs and would love the configuration ease of Carla. I stumbled upon the env var before and when setting Some further debugging got me to this: Poking around in code leads me to believe it is set here, but this code is not called when the GUI is not rendered. Carla/source/frontend/carla_host.py Line 212 in ecad526
Do you have any idea if there is a way to change the output names to be predictable when not using a GUI for Carla? My minimal example
|
Hi, I want to use Carla-Patchbay as a plugin chain host for multiple "chains", so multiple instances are needed.
But when I start new Carla-Patchbays, there is currently no option to set the name, so I end up with this:
Which is confusing, not really clear which is my mic processing chain here.
Some way to name the patchbay instances would help here, at least for console.
I start them with:
There could be a new command line option for example:
The text was updated successfully, but these errors were encountered: