-
Notifications
You must be signed in to change notification settings - Fork 173
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
Midi problems (parameters, outgoing midi messages and modified Drumkit reopen) on Windows #1557
Comments
Thanks for reporting! I'll look into it |
Hey @philbee4 , Could you check whether the problem you had with version 1.2.0 still occurs in this patch? |
Hey GreatWhiteShark, |
…ut-channel Fix #1557 midi out channel
That's indeed a known issue for quite some time (see #63). It's one of those things that definitely deserve to be fixed no one had the time to do so. Unfortunately, it won't make it into the next release either because we are almost done and laid the focus on other things. But hopefully it's covered in the next next one. |
Hydrogen version * : 1.1.1 c845af2 (dec 5 2021) and 1.2.0-debug (march 6 2022)
Operating system + version : Windows 64 bits 8.1
Audio driver + version :
Midi issues :
Version 1.1.1 : no midi out messages from Hydrogen sequencer (or individual clic on an instrument inside a drumkit) (of course, Midi out device was set, instrument channel set to >0
Version 1.2.0 : with same midi configuration, midi out messages ok (see my comments on #1234) BUT :
**** I save a drumkit (from standard GMRockKit with a new name, and after check that things are normal with pattern scheduling and midi out messages as expected) after having set new channels and notes number, everything seems ok until I reload the same drumkit : channel numbers "randomly" transformed (as if instrument parameters had become corrupted), and Hydrogen crashes without any message, just after 1 or 2 instrument played.
Joined : Debug file and .conf
Thanks for any help.
hydrogen.log
hydrogen.zip
The text was updated successfully, but these errors were encountered: