Midi events sent to LV2 plugins pontentially not being sorted

[captaincurrie]

Check out https://github.com/swesterfeld/liquidsfz/issues/47

Problem with the liquidsfz lv2 plugin, apparently it was crashing because reaper was not sending midi events in chronological order. Not sure if this is by design or not but just thought i would bring it to the attention of the devs

[Justin]

ah thanks, fixing this!

[mschnell]

Curious (as discussed in several issues):

AFAIU, Midi events (consisting of "data" and "offset") are handled as Blocks associated with Sample blocks.
At least with VST API.

Is the DAW required do sort their position in the block (according to "offset")?

is the lv2 API not using blocks ?

[sockmonkey72]

Originally Posted by mschnell

Curious (as discussed in several issues):

AFAIU, Midi events (consisting of "data" and "offset") are handled as Blocks associated with Sample blocks.
At least with VST API.

Is the DAW required do sort their position in the block (according to "offset")?

is the lv2 APUI not using blocks ?

He who reads documentation, knows things:



(the information you seek is in the warning box at the bottom)

[mschnell]

Interesting, but ???
captaincurrie was talking about Midi (CC, Notes, ...) (and sample blocks). Not automation (supposedly meaning parameter modulation).
I do know that VST3 does sample accurate parameter modulation (i.e. parameter changes somehow tied to a sample block offset), while VST2 does not provide this.
But this a different story.