[LV2] LV2 vs. Ardour: unexpected time.Position events and time.frames values

Sven Jaehnichen sjaehn at jahnichen.de
Sat Oct 26 11:26:54 PDT 2019

Hi Robin,

tanks for your quick response, about

>> #3 [..] In contrast to all other events where time.frames <=
>> n_samples in run() [..]
> With jalv? If so that's likely a bug in jalv. GUI to DSP messages are
> timestamped at n_samples, out of bounds.

With jalv, all time.frames are in the limits (0 .. n_samples). 
time_Position (usually) == 0, GUI events == n_samples, and midi_Events 
in between. Everything fine there.

But Ardour produces the described high (> n_samples) down counting (in 
n_samples steps) time.frames values for time_Position (although they 
were not requested in the .ttl).

Best wishes

More information about the Devel mailing list