MiniDexed

MiniDexed copied to clipboard

If any modulation range is changed, the modulation can no longer be heard; the modulation only works again after blindly saving and reloading the performance. You can easily try it out with the performance 000011_SeventyOne, for example. Simply turn the modulation wheel all the way up until the sound has a lot of vibrato, then change the modulation range for the modulation wheel from 99 to 98 in the settings of TG1 and TG2 and you can no longer hear vibrato. The problem occurs with all types of modulation. (ModWheel, Breath Controller, Foot Controller, Aftertouch)

Thanks for reporting this issue @Banana71. Do you happen to know whether this works correctly in Dexed on the PC?

In Dexed everything works as it should. Range changes are applied immediately, even when tones are pressed and held.

@dcoredump can you reproduce this on MicroDexed?

I have to check this, give me some time. I think I know what's going wrong...

Thanks @Banana71 for deep testing and finding problems I never thought they may exist 😁

I created a PR. Hope this fixes the problems. Cannot test - no keyboard right here.

Hi Holger @dcoredump , Unfortunately the error is still there

Hi Holger @dcoredump , Unfortunately the error is still there

Hmpf... I found that the (wrong?) calls to controllers.refresh() were additionally also inside Synth_Dexed :( Can you try this version of Synth_Dexed?

@Banana71 please try this build: MiniDexed_2023-11-20-8d1e592

It is built using the fixed version from the posting above.

The error has changed. I set the Mod.Wheel to MAX, the sound has full vibrato. After adjusting the Mod.Wheel range from e.g. 99 to 80, the vibrato remains at MAX and the vibrato stops completely when you move the Mod.Wheel. In other words: you can adjust the range but the modulation remains at the old value. After moving the Mod.Wheel the modulation goes off and can no longer be restored.

Thanks for testing!

Ok, I need to get my MIDI keyboard from the rehearsal room to my lab at home for deeper inspection. I hope I can try to dive in deeper at next weekend.

Hi Peter,

now I got some time for testing this with MicroDexed (see this video). On MicroDexed it works as expected. So the problem may be located inside MiniDexed?

Regards and merry xmas, Holger

Thank you Holger for your effort.

Merry Christmas to you all 🎄 Peter

Good things come to those who wait. For whatever reason, probably due to the Glissando Effect Fix https://github.com/probonopd/MiniDexed/issues/889 , the modulation range parameterization now works. Thanks

Or does anyone have an explanation for why this suddenly works?

Glad to hear it works now! 👍

I don't have a better explanation.

Or does anyone have an explanation for why this suddenly works?

Maybe I fixed it and forgot to tell this for upstream integration...

Maybe this one? https://codeberg.org/dcoredump/Synth_Dexed/commit/b9fd3010f28ba248049315dbd81c887bdc3f3a38