Home › Forums › Products › Stompboxes › H90 consecutive midi messages behavior
- This topic has 4 replies, 3 voices, and was last updated 1 year, 6 months ago by joecozziEventide Staff.
-
AuthorPosts
-
-
June 1, 2023 at 10:14 pm #171686MarcoRParticipant
Something seems to have changed somewhere around 1.3.0 and 1.5.2. Previously, I could send multiple CC messages and they would all process. Now they do not. In my controller I have the capability to delay the next midi message in milliseconds. I used to have to do this with a Source Audio Collider as it also couldn’t process consecutive midi messages. Putting 15ms delay between each message did the trick to overcome this. Now with the H90, I need to put about 400ms delay between each CC message to process. Has anyone else noticed this?
-
June 1, 2023 at 10:26 pm #171687
They only thing that changed MIDI-wise is the addition of a PC offset. Nothing else. I test often sending CC messages from a DAW to control parameters in Programs and have never run into any issue. Can you describe a scenario that’s causing you problems, perhaps something testable by us?
-
June 2, 2023 at 2:22 pm #171695brockParticipant
400 mS is way too much. Something is out of whack here. As Joe implied, do you have a lot of devices daisy-chained in front of the H90? Multiple MIDI Channels or Omni, a number of PCs transmitting? Trying to diagnose … I’ve had to delay MIDI for several legacy devices, but never as long as that.
For comparison, I regularly pound the H90 with CC LFOs, envelopes, sequencers, etc. from a Reflex, Beebo, MPX, 8 Step Program … Often modulating the modulation on its way in, and I’m not getting any hiccups. That same scenario to an H9 or ‘Factor pedal would freak out the display – at a minimum – or melt it down completely.
-
June 3, 2023 at 12:55 am #171713MarcoRParticipant
Thanks for replying! I have mostly resolved the problem… it was me.
There where some crossed up midi commands in my controller where a PC was sent to load an H90 program, followed by CC messages. Then something was unintentionally sending the PC again; reloading the program and resetting the parameters; giving the perception that the CCs weren’t being processed.
The difference compared to when it was initially worked was sending the PC before the CCs… which should be fine but there was an instant access switch on my controller also triggering the PC that was hidden. It took me a minute to track it down… Now I just need to clean up my programming and should be good.
-
June 3, 2023 at 6:44 am #171716
Glad you figured it out. Thank you for reporting back.
-
-
AuthorPosts
- You must be logged in to reply to this topic.