The first cause can be too much info on the MIDI bus for the DAW to properly process with allotted resources. Often fixed by increasing the input midi buffer, so the DAW can buffer messages & "catch up". This is a much bigger issue with PCs with slower CPUs or less memory. I'm a little surprised there is no buffer setting in HH, I think HH assumes you won't give it too much to handle.
The second possible source is that HH1 had a bug a while back. With all the changes, a possible reintroduction may have occurred. HH's Midi processing used to get easily overloaded causing hung notes & erratic midi behavior. Workaround for this is to NOT send input to 'Midi to Usine', use MIDI buses instead. I do not see this behavior in HH2, but it's worth a shot to try if you're really stuck.
Things to try:
- Reduce midi input... There are some very high volume messages that sometimes need to be disabled - e.g., midi clock and active sensing. If they are being generated by the controller, turn them off.
- Reduce midi input... Disconnect any other midi input devices for the time being, if you have any
- Don't run ANYTHING on that pc but HH for diagnostic purposes - ESPECIALLY anything audio related. Close all other windows, browsers, music players, etc.
- If the controller is sending midi clock, and you want to use it, make sure the device is configured as the source of the clock in HH
- Another thing to try - In the input midi device patchlet, you'll see a connection from the "from midi device" module to the "midi to usine" module. Disconnect that. Instead send the midi traffic from the "from midi device" to a MIDI bus. Use that MIDI bus in your patches. If this fixes your problem, file a bug report for HH.Statistics: Posted by shawnb — 08 May 2015, 19:22
]]>