search

surge-synthesizer / surge

Synthesizer plug-in (previously released as Vember Audio Surge)
https://surge-synthesizer.github.io/
GNU General Public License v3.0
3.09k stars 395 forks source link

Remote wavetable selection #759

Open michaelohagan912 opened 5 years ago

michaelohagan912 commented 5 years ago

Please make wavetables selectable by both midi and automation for use with devices like push or automap enabled controllers.

baconpaul commented 5 years ago

Oh that's a good idea, but it is a bit painful for a couple of reasons, including wavetables aren't really parameters (the file gets loaded as binary onto the patch) so aren't exposed in a normal way.

We're really trying hard to not add parameters for 1.6.0 so I'm going to tag this as a 1.6.n at least thing.

Thanks for the suggestion!

mkruselj commented 5 years ago

Yeah this is not really that easy to do because as soon as you add new wavetables, the list order gets messed up and any MIDI messages you used to select your wavetable is suddenly in great risk of choosing all the wrong wavetables.

I vote not to do this.

michaelohagan912 commented 5 years ago

It's up to the end user to create folders and categorize their wavetables according to their own liking, I would actually update this feature request that I think it should be 2 midi cc #'s, one to select banks/catagories/folders of wavetables and a second midi CC to select wavetables from within that bank.

mkruselj commented 2 years ago

@baconpaul My proposed solution for this issue:

  1. Make prev-next wavetable buttons MIDI learnable. Guess they will need to be proper parameters for that.
  2. Make right-click on prev-next wavetable buttons jump to prev-next folder. Add a separate MIDI learn for that (I guess another option in the context menu - MIDI learn file jog vs MIDI learn folder jog).
  3. Close this issue?
mkruselj commented 1 year ago

Another option to solve this issue is to expose wavetable selection to OSC (#2355).