https://www.rncbc.org/drupal/index.php/node/2829
"ALL internal processing (within qtractor premises that is), plugins and looping included, is frame/sample accurate; automation being the exception as it runs on a fixed 64frames resolution (or even less, if the period buffer-size is insanely shorter than that)."
If I increase the clip duration by just 23 frames (the minimum allowed), exceeding the range limit, the problem disappears.
It might be a rounding error, resulting in an empty sample space.
As I mentioned, it's not important, but... it doesn't hurt to point it out.
It might also be related to the desynchronization (although that disappeared with a generic kernel on my machine) of audio tracks in loops...
PS: Sorry, I misunderstood. Everything syncs to 1 frame, except for automations, which run at 64 frames.
It can't be a rounding error then.
https://www.rncbc.org/drupal/index.php/node/2829
"ALL internal processing (within qtractor premises that is), plugins and looping included, is frame/sample accurate; automation being the exception as it runs on a fixed 64frames resolution (or even less, if the period buffer-size is insanely shorter than that)."
If I increase the clip duration by just 23 frames (the minimum allowed), exceeding the range limit, the problem disappears.
It might be a rounding error, resulting in an empty sample space.
As I mentioned, it's not important, but... it doesn't hurt to point it out.
It might also be related to the desynchronization (although that disappeared with a generic kernel on my machine) of audio tracks in loops...
PS: Sorry, I misunderstood. Everything syncs to 1 frame, except for automations, which run at 64 frames.
It can't be a rounding error then.