Nick Dowell
Nick Dowell
I have been unable to reproduce this issue with either the current or old 1.9.0 version of amsynth that is included with Ubuntu 20.04. Tested with Rosegarden 19.12 and 22.06,...
Hi @ondinegreen can you provide any further information to help me reproduce the issue?
The issue appears to be that amsynth "remaps" the MIDI CC to its "preferred" representation - i.e. `0` or `127` for an on/off parameter - so that any other value...
Thanks for the feedback :+1: I was able to reproduce the unexpected output for normalized values; it was due to a missing call to `round()` - fixed in 1c8dea8fc59601f456a3427c9f4dd32f36c97cc1 I...
Thanks, I need to do a bit more investigation into these "ghost" values / jumpy UI. Are you using ALSA or JACK MIDI input to amsynth? > 1)Is it possible...
The "ghost" MIDI output turned out to be caused by an issue with how the GUI was being updated in response to MIDI input. This should now be fixed in...
>The ghosts in the midi out are fully gone. I'm still testing the code, but it looks veeeery good. Excellent 😅 >Filter Decay control CC (assigned by me to CC111)...
Thanks for the update! I'm just wondering whether it could be a subtle hardware difference between the encoders, because I can't see a reason that amsynth would respond differently to...
Closing as fixed - unexpected MIDI output was fixed in release [1.13.0](https://github.com/amsynth/amsynth/releases/tag/release-1.13.0)
Good suggestions, thanks! 👍