Thanks, I only wanted to confirm that it was true even with the last set of pitch bend range options, and you have now clarified that so I cant think of any other possibilities to explore.
1 Like
The moDllz author incorporated my MPE+ fix, and it looks like that updated version is now available in the VCV Rack library. Version 2.1.2 incorporates the fix, although I havent actually had time to try this library version of the plugin myself to make sure its working as expected. I shall do so shortly and will report back.
5 Likes
FWIW Iām currently working on adding polyphonic WXYZ outputs to #d CHEM.
Itās working at a basic level, but I need to make sure that it follows all the possible MIDI output configuration, and some other adjustments like match the number of output channels to the polyphony setting ā currently always 16, even though some get no output.
I also either have a bug, or I need to add smoothing to the Y output. Using a separate slew module works, of course, but I think it needs to work nicely on its own.
1 Like
Turned out the main issue was that I needed to recalibrate the surface on my Mini. But yeah, Y is still pretty noisy, especially on the Mini. So Iāve added tiny slew trim knobs for Y and Z that can add some basic light slew control. For more detailed or heavy-handed smoothing you can always use any one of several very good slew modules available in Rack.
Still thinking about how to support MIDI access for navigating preset lists. I think thereās a module that supports converting MIDI cc to computer keyboard events, and if that allows routing to a specific module, it would work because Preset supports keyboard access. But of course, something more integrated would require fewer modules and stands a better chance of being robust.
when I did Meta Morph for the Eigenharps, I also noticed that I could hear āzipperā noise in some casesā¦ (it was quite contextual in my case)
In the case of the Eigenharps, Iāve got a direct usb access to the hi-res data, and was sampling at sample rate - so could rule out āmidi odditiesā (e.g. core midi / vcv midi handling).
I think its simply that when you use āmidiā synth they all have a certain amount of slew to handle the midi steps, its primitive so never really exposed to the user -though, some allow control over this.
I found when writing my own āsynthsā (c++ dsp), I had to do the same to make it usable esp. with expressive controllers, as they are modulating x/y/z so quickly, to the point you could consider it ānoiseā (or chaos if you prefer ;))
and , vcv ( * ) and cv is like this, its often assumed to be continuous (at sample rate), with obvious exceptions ( v/oct , gates, trigs etc) , so few modules have slew (unlike midi), unless you add it yourself.
Itās an interesting area for expressive controllers, as when I added slew to the eigenharps I could instantly feel it (as ālagā) even when it was pretty subtle/fast, and if you do it too fast, it loses its effectiveness - so its a compromise/balance.
all that saidā¦ I also think its like pixel peeking (by photographers),
once you hear it, and start coding against it - I found I was became a bit hypersensitive to it. likely most/many users would not even notice it.
( * ) hmm, it be interesting to check the code of MIDI CC module, id not be surprised to see it have a slew?!
1 Like