Timing for Sending of Program Change Messages?

I have a Boss VE500 and an Eventide H90. My VST Live project has two midi tracks that fire program changes to the two pedals. When I hit play on VST Live, the VE500 immediately jumps to the appropriate preset. But the H90 does not. Once I hit the space bar to stop it and once more to restart, the H90 jumps to its preset.

I feel like this is partially an H90 issue, but when I plug my Octatrack into the VE500 and the H90 and load a pattern, both pedals immediately jump to their presets. So i wonder what VST live does differently when it comes to sending out midi program changes when you RTZ the transport or hit play.

Thank you.

How are your devices connected? USB hub? Maybe the secret lies hidden here.

In both situations the units are fed through a usb to midi interface. I also tried it from VST Live through a second interface but it was the same. I also tried making changes so that the program changes would happen every second. But it would only snap to a program after I’d stopped playback and started again.

I’m afraid I haven’t yet fully understood your setup. Could you perhaps elaborate a little bit more on how your MIDI connections are actually realized, what interface(s) you use etc.?

And to narrow down the problem, please open the MIDI Monitor, set it to the MIDI port in question and check if VST Live actually sends out the Program Change in time - or only after you press space (stop the playback).

Here you can see that when I hit play the first time, it sends the Change out channel 16 to the VE500. Then I hit stop and it sends the All Notes Off message. Then I hit play again and it sends Change messages out to both pedals.

Both program changes are sent out at the same time stamp, it seems. The only difference being that data for your H90 is transmitted on channel 15 instead of channel 16.

Have you already tried to switch connections and channels for both devices? What happens, if only the H90 is connected?

And are you sure that the software supplied with the U6MIDI Pro is set up correctly? I don’t have that interface, so I don’t know which traps may linger there. :blush:

Yes, tried both connections. Switching both midi ports and channels. Interface firmware is up to date.

I take it that nobody has this issue? Everyone can fire off program change messages from every port?

I just did the following:

  • On Mac I activated an IAC port (a virtual MIDI cable) using the Audio-MIDI-Manager
  • In VST Live I created a new project with two MIDI tracks, both routed to that IAC port. One track sends on channel 15, one on channel 16. Both tracks send a program change at exactly 2.1.1.
  • In Cubase 15 I also created a new project. One MIDI track, receiving from the aforementioned IAC port on all channels. I also inserted the MIDI Monitor as an insert effect.

Result: both program changes are received absolutely simultaneously. I can also use two individual IAC ports, same result. So I assume your problem lies somewhere hidden in your MIDI signal chain. I suspect either the H90 or the U6MIDI Pro (wild guess, of course).

Another idea just struck me: have you ever tried to connect both, VE500 and H90, directly via USB, thus leaving the U6MIDI out of the equation?

Could this be due to the Microsoft Windows MIDI Services rollout? They’ll be rolling out fixes there until the end of May.

MIDI chase settings in preferences maybe?

I’ll have to try this on my studio computer (Mac Studio) since I’ve only attempted it on my live rig (Surface Studio)

Anything is possible, but I’m not aware of any Program Change message delays in the new MIDI stack.

The monthly rollouts and what they contain are documented on the MIDI Discord Server Windows MIDI / Audio . See the pinned #start-here post.

I also have a U6MIDI Pro and haven’t seen any issues there. What exactly should I be looking for? (Take Cubase out of the equation, please).

Pete
Microsoft

Well, I dug my MOTU M2 out and tried the Midi out on that and it went away. I’ll poke around a bit, but if it ain’t broke (anymore)…