This is not a question about V/Oct tracking not working out of the box as someone might expect, but announcement that I’ve been working on automatic procedure for calibrating input/output. V/Oct scaling code relies on calibration settings and those that are shipped gave results that are way off (i.e. scaling multiplier that I need is about x1.5 bigger than default setting). Currently this code resides at GitHub - antisvin/OpenWare at magus-calibration and it actually works, but I’ll be making a few minor updates before opening PR.
Calibration procedure that I’ve made should be run like this:
- Enter system menu, scroll to V/Oct page, confirm you want to calibrate with encoder click
- Choose Input, confirm
- Connect 1V source to left input, confirm
- Connect 3V to left input confirm
- Choose Save
- Choose Output, confirm
- Connect left input to left output, confirm (twice, with a short pause)
- Choose Save
That’s it, now you can use code from here OwlProgram/VoltsPerOctave.h at master · pingdynasty/OwlProgram · GitHub and it would use stored calibration settings (don’t forget to use VoltsPerOctave(input=False) for output CV). Also, I’m using max volume to get full output CV range (it could be that not doing that would result with incorrect measurements, haven’t tested this yet).
I’m also finishing some code that would expose V/Oct tracking to Faust patches.