Skip to content

v/oct not behaving like the hardware #3

@jackregnart

Description

@jackregnart

Based on the manual for Acidus Versio when the tuning knob is full counter-clockwise and you send zero volts it is supposed to correspond to C2. The voltage is also locked to 0-5V.

https://github.com/abluenautilus/AcidusVersio/blob/main/docs/AcidusVersioManual.pdf

Right now, the VCV rack port in this scenario starts at C4 and accepts -10 to 10V.

Audio up at the high and low voltage ranges (before it becomes inaudible) seems to misbehave.

Suggest changing the code here:
https://github.com/jjbbllkk/Acidus-Versio-VCV-Rack-Port/blob/main/src/AcidusVersio.cpp#L167-L168

Adding the following would make the code behave as per the port:

volts = clamp(volts, 0.f, 5.f);
int midi_note = (int)std::round(volts * 12.0f + 48.0f);

The only problem is, you'd lose a lot of octave range. Looking at the caveats section of Blue Nautilus' manual I can see why it is like it is in the hardware version. Maybe a good compromise to open it up more would be to clamp the voltage at -5V to 5V so that you can get more range out of it?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions