Wotja 22 VST3 - MIDI events

[jules]

Surely Kott's post above is the clue you need to look at?

If your plugin is spitting out messages whose timestamps are beyond the end of the current block, then obviously hosts are going to deal with that in random ways.. They may throw the messages away, or clamp their times to the block length, or just reset their timestamp to 0, or maybe some hosts try to be clever and downscale all the times so they fit inside the block.

IIRC we clamp the times if they're not too far off the end, but if the timestamp is really nuts then we'll throw it away. Maybe that's not the best policy, but at least it meant that you spotted this mistake - because if you're testing with a small enough buffer size, you could easily have never spotted that the times are all wrong.

@drow
This definitely sounds like something that PluginVal should check for (if it doesn't already...?)

[impete]

Surely Kott's post above is the clue you need to look at?

If your plugin is spitting out messages whose timestamps are beyond the end of the current block, then obviously hosts are going to deal with that in random ways.. They may throw the messages away, or clamp their times to the block length, or just reset their timestamp to 0, or maybe some hosts try to be clever and downscale all the times so they fit inside the block.

IIRC we clamp the times if they're not too far off the end, but if the timestamp is really nuts then we'll throw it away. Maybe that's not the best policy, but at least it meant that you spotted this mistake - because if you're testing with a small enough buffer size, you could easily have never spotted that the times are all wrong.

@drow
This definitely sounds like something that PluginVal should check for (if it doesn't already...?)

Hi Jules - hope you're well BTW!

Thank you very much for your comment.

I'll dig-in to the question of timestamps. I guess I'm puzzled that we're not seeing any events come through at all on Tracktion - but DAWs are horrendously complicated to write, and that is just the way of the world!

Best wishes, Pete

[JamminFool]

nvm

[impete]

I guess I'm puzzled that we're not seeing any events come through at all on Tracktion - but DAWs are horrendously complicated to write, and that is just the way of the world!

Best wishes, Pete

he's suggesting that Waveform throws the MIDI messages away under certain circumstances, perhaps like this one.

Yep - that would appear to be what is happening

Pete

[Kott]

BTW it works fine in JUCE's extra's AudioPluginHost

[JamminFool]

BTW it works fine in JUCE's extra's AudioPluginHost

thanks for your help in this. hopefully it leads to a fix.

[impete]

BTW it works fine in JUCE's extra's AudioPluginHost

thanks for your help in this. hopefully it leads to a fix.

All now working on my development machine!



NB: I had the Waveform Pro Experimental audio engine enabled for some reason - and that did NOT route MIDI.

We'll try to push this update soon, but we must first test internally - and extensively!

Best wishes, Pete

[impete]

Hi again folks.

Just to report that while Wotja 22.1.0 MIDI routing works fine in Tracktion, this is *not* the case if the Tracktion Waveform "Experimental" audio engine is enabled.

Best to all, Pete