On Sat, 4 Jan 2025 12:40:06 +0100 Kristian Amlie <krist...@amlie.name> wrote:
>On 04.01.2025 12:14, Will Godfrey wrote: >> Overall I'd be quite happy with this. However, I still have questions. >> >> How would it relate to MIDI-Learn? >> >> What effect would it have on Vector control - or indeed, any of 32 or 64 >> parts? >> >> These come before any of the normal routing. Indeed, MIDI-learn has the >> ability >> to block any further access to a CC/CH pair. > >For MIDI learn, it's simple: It's unaffected. It already has its own >MIDI selector, which already includes an "All" option. Everything that >has to do with the part level Omni mode is handled only by MIDI messages >that make it through MIDI learn first, without being blocked. > >Vector is a feature I've never used personally, so I'm much less >familiar with it [1]. However, given that it controls more than one >part, it probably has to act the same as MIDI learn, IOW it does not >respect Omni mode, but respects its own base channel instead. Sometimes I forget what I implemented myself! >[1] However, I like it! Maybe I'll us it more now that I took the time >to figure out how it works. If you check the HTML user guide MIDI CCS and NRPNs you'll see that via an NRPN you can change the actual CC that is used for all features except 'Volume'. The only reason that this isn't also available to the GUI or CLI is that I never got round to doing it! Volume is a special case as it tries to maintain a consistent apparent level as you sweep across. It actually dips about 6dB in the middle depending on instrument types. I wish I could get it better. -- Will J Godfrey _______________________________________________ Yoshimi-devel mailing list Yoshimi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
