Skip to content
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

Voltage Range on Vol and Dry/wet CV INs #33

Open
Beatalchemie opened this issue Dec 18, 2024 · 2 comments
Open

Voltage Range on Vol and Dry/wet CV INs #33

Beatalchemie opened this issue Dec 18, 2024 · 2 comments

Comments

@Beatalchemie
Copy link

Hi
The CV inputs for the sliders (for VCOs & DRY/WET) are designed for 10 volts. Most modulation sources (e.g. ADSR, uni LFOs etc.) are 5 volts. And so the modulation level is not enough to fully open the sliders and that is a problem.
Is it possible to make the CV inputs unipolar at 5 volts or -5 to +5 volts and declare the controller as an attenu value?
That would be really fantastic.

And I have already said that the [WT] VCO is always an octave higher than the SINE VCO or SS, which is really annoying!

Otherwise, thank you very much for the wonderful module. I always use it now, with every patch hehehe. Totally cool

@markcrosbie
Copy link

Yes I noticed this as well today when shooting a video - and even if an envelope gets to 10v the result isn't as loud as manually opening the slider

@Diegoterrores Diegoterrores changed the title CV Controll Voltage Range on Vol and Dry/wet CV INs Mar 5, 2025
@Diegoterrores
Copy link
Collaborator

The faders are designed to be "normalized" to the control voltage (CV) inputs, which means that bipolar control is not possible. Instead of adding an offset to the CV, the faders function as attenuators, meaning that negative voltage will have no effect.

One potential improvement could be to adjust the range to a smaller positive value, such as 5 volts.
While it is possible to change the range to 0 to 5 volts, doing so would require hardware modifications. If user demand warrants it, this change could be implemented in a future hardware revision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants