Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modulation Range Error #562

Open
Banana71 opened this issue Nov 17, 2023 · 12 comments
Open

Modulation Range Error #562

Banana71 opened this issue Nov 17, 2023 · 12 comments
Labels
bug Something isn't working

Comments

@Banana71
Copy link

Banana71 commented Nov 17, 2023

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)

@probonopd
Copy link
Owner

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

@probonopd probonopd added the bug Something isn't working label Nov 17, 2023
@Banana71
Copy link
Author

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

@probonopd
Copy link
Owner

@dcoredump can you reproduce this on MicroDexed?

@dcoredump
Copy link
Contributor

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 😁

@dcoredump
Copy link
Contributor

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

@Banana71
Copy link
Author

Hi Holger @dcoredump ,
Unfortunately the error is still there

@dcoredump
Copy link
Contributor

dcoredump commented Nov 20, 2023

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?

@probonopd
Copy link
Owner

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

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

@Banana71
Copy link
Author

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.

@dcoredump
Copy link
Contributor

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.

@dcoredump
Copy link
Contributor

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

@Banana71
Copy link
Author

Thank you Holger for your effort.

Merry Christmas to you all 🎄
Peter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants