Request to be able to remap the current PWM in jack to be used for FM of each oscillator. Ideally this could be changed independently per oscillator (e.g. Castor could have PWM and Pollux could have FM) and could be enabled either through a button combination or through Gemini.

Hey @theacodes, Looks like you have a wonky link in the latest releases for C&P
https://github.com/wntrblm/Castor_and_Pollux/releases/tag/2021.06.10

Actual:
instead of directing to https://theacodes.github.io/Winterbloom_Castor_and_Pollux/#updating-the-firmware

Expected:
https://github.com/wntrblm/Castor_and_Pollux/blob/main/user_guide/docs/index.md#updating-the-firmware
OR
https://gemini.wntr.dev/#updating-the-firmware

Was writing a contact email but thought this was more immediate & wasn't quite sure about opening a pr on someone else's repo. Hoping you're having a great week!

In the open source hardware and software section of the Castor and Pollux user guide (Here), the links still point to files in the non-existent master branch. I think these should point to the main branch, as I can find the files there.

It would super nice to have a button in the settings editor page to reset Castor & Pollux, ideally right underneath the "upload settings" button

That way, the user doesn't have to use the physical reset button on the module, which may be difficult to get to depending on how their rack is arranged

For context: this is a DIY build based on hardware v2 9/26/2020, with fixed transistor ramp core.

I've noticed that with all volume pots at zero, there is a faint bleed of castor's ramp in pollux's mix out.
I've yet to calibrate the unit, but this seems like pure analog spookery at play, here.

Please note that in the following report, part numbering follows latest schematic (3beb279 as of today).
With preliminary probing, here's what I've tested:

• No bleed at pin 8 of U12
• Bleed after r47 (== net pollux_mix_out) -- this is the reference volume
• Bleed is fainter at pin 3 of U14a
• Bleed is equal at pin 1 of U14a

Setting Castor's ramp volume up, and playing with the crossfade knob can cancel out the bleed. This seems to indicate the bleed is 180° out of phase with the ramp output. Maybe netlist castor_ramp_pre is bleeding in ?

I'll tinker a bit further when I get the time.

Right now, the base CV offset is fixed so that 0V = C2. It should be possible to edit this with the settings editor.

When I try to connect to Castor & Pollux from the Settings Editor, I see the message "Couldn't connect, check connection and power and try again?" when the module is powered on and connected to the computer. This is on a Fedora 34 (Pipewire) system.

It looks like the cause is that the MIDI ports are getting assigned the name Gemini MIDI 1, while the settings editor is checking for a port with the exact name Gemini. Indeed, changing these comparisons from === to startsWith lets it connects fine, but this alone seems a bit loose to me. Maybe a more robust solution would also check the port manufacturer. Or maybe the real problem is the name assigned by Pipewire, and I should file a bug there?

This feature would allow configuring either (or both) pitch CV inputs to quantize to the nearest semitone.

Implementation checklist

• Basic feature implementation, mostly already done in aquaticsarah@9e2452c
• New settings fields to enable quantization for each oscillator. This requires a couple of changes in a few files- this commit shows what's involved.
• Update the settings editor to have the fields. This isn't too bad, this commit shows how it was done for the LFO feature, which was a lot more involved than this one.

Possible follow-up features

These are nice to have, but not required to get this feature deployed. They can be added on later.

• Ability to specify a scale other than the chromatic scale.

/cc @aquaticsarah