-
Notifications
You must be signed in to change notification settings - Fork 20
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
Optional CV control for levels (VCA)? #63
Comments
Can you provide a usage scenario? Am I right in concluding, that this would require an extra JACK input port for every CV signal? And if you wanted to control all channel levels individually, you'd need as many extra CV input ports as channels? And if you have less CV input ports than controllable levels, you'd need some internal mechanism/setting to route from a CV input to a controlled level? |
Use case would be to automate a sequence of volume changes for apps in a JACK graph. Prior art is Non Mixer. I see this as a 'turn on individually for each channel that needs it, and a CV port for that channel appears directly after it in port order'. On maybe one CV signal to serve for multiple channels - my take before was that those channels would probably be on a buss / group send anyway, so one CV could be enabled to control that group. |
Just transferring information from IRC ( You can use midimonster to create a JACK CV to MIDI client to control a Here's an example configuration for midimonster:
Connect your CV source to the Here's a short demonstration video: |
Related to #55
The text was updated successfully, but these errors were encountered: