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

Midi problems (parameters, outgoing midi messages and modified Drumkit reopen) on Windows #1557

Closed
philbee4 opened this issue Apr 4, 2022 · 4 comments
Assignees

Comments

@philbee4
Copy link

philbee4 commented Apr 4, 2022

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 :

  1. internal : Realtek Audio 6.0.8746.1
  2. external audio + midi : Motu ultralite mk3 4.0.6.6814

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

@theGreatWhiteShark
Copy link
Contributor

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.

Thanks for reporting! I'll look into it

@theGreatWhiteShark theGreatWhiteShark self-assigned this Apr 5, 2022
@theGreatWhiteShark
Copy link
Contributor

Hey @philbee4 ,

Could you check whether the problem you had with version 1.2.0 still occurs in this patch?

Hydrogen-1.1.1-win64.exe or Hydrogen-1.1.1-win32.exe

@philbee4
Copy link
Author

philbee4 commented Apr 8, 2022

Hey GreatWhiteShark,
Tried it and seems ** OK ** with this version : no channel jam nor crash, here joined an audio result (Addictive Drums 2 driven by Hydrogen midi output via LoopBe1) to thank you for your test and mid/mod-ification.
One thing remains as a minor point, which could be intentional from Hydrogen conceptors : I noticed that when an instrument is part of a drumkit but not present as an audio file (examples: the 2 last instruments of GMRockKit : "hat semi open" and "bell"), no midi output occurs. Not a real issue, of course, but could be differently thought if small re-writing price.
Big thanks, best regards.
Phil
Hydrogen111'a38e1640'-tst.zip

@philbee4 philbee4 closed this as completed Apr 8, 2022
theGreatWhiteShark added a commit that referenced this issue Apr 8, 2022
@theGreatWhiteShark
Copy link
Contributor

One thing remains as a minor point, which could be intentional from Hydrogen conceptors : I noticed that when an instrument is part of a drumkit but not present as an audio file (examples: the 2 last instruments of GMRockKit : "hat semi open" and "bell"), no midi output occurs. Not a real issue, of course, but could be differently thought if small re-writing price.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants