So according to the Pod gen~ patch, turning the encoder should change the saw/triangle waveform. This does not happen.
I also watched the encoder output with an oscilloscope. Both terminal A and B are giving pulses (negative pulses). So I am assuming the hardware is OK.
Give this patch a try to confirm that your encoder is working with the Daisy.
Twisting the encoder will increase (or decrease depending on the direction) the frequency of an oscillator. You can select “pod” as the board. Just FYI, it’s 1 hertz per twist in this patch so keep on twisting to hear the change
My apologies - zooming it makes it clearer. I’m really new to gen~ but when I open that template patch I can’t see that the encoder is actually connected to anything:
Apologies again for being so unhelpful! I just tried this dev patch on my pod, and the encoder only makes a change once I have pressed one of the buttons. Don’t have time to dig into the patch and learn why right now, but hopefully this is of some help at last?!
Haha, no worries!
Yup when pressing a button, it switches to triangle/saw which has a morphing waveform that is influenced by the encoder.
Maybe there’s a bug in the oopsy package from the dev branch that I got installed? I could try to reinstall the oopsy package with the one from the master branch, tomorrow.
Ah I see, I think I remember the encoder not working on the dev branch.
I’m currently using the current/public release and I can confirm that encoder does work.
Unfortunately when using the main branch I’m now getting a compilation error when using GateOut in the custom json file. However, GateOut does work in the dev branch.
Somewhere in the oopsy verbos output it says: oopsy-verbose: “error: ‘dsy_gpio’ in namespace ‘daisy’ does not name a type”
I can make a new forum post about the GateOut if that’s better.
Also, do you have any indication on when a new version of Oopsy is coming?