Hi all,
I’m trying Ardour4, it seems to be a very good Daw !
I’m planning to use it as my main midi sequencer.
Unfortunately, I got some tempo dropout.
Here is my console history : drop flushed event on the floor, time 0 too early for 614 + 0 fa
drop flushed event on the floor, time 354 too early for 614 + 0 f8
drop flushed event on the floor, time 53 too early for 550 + 0 88 24 40
drop flushed event on the floor, time 0 too early for 614 + 0 fc
drop flushed event on the floor, time 0 too early for 614 + 0 fa
drop flushed event on the floor, time 354 too early for 614 + 0 f8
drop flushed event on the floor, time 53 too early for 550 + 0 88 24 40
drop flushed event on the floor, time 0 too early for 614 + 0 fc
drop flushed event on the floor, time 0 too early for 614 + 0 fa
I switched to Ubuntu (for another reason)
I got the same problem
when the tempo became random, I can see some JACK messages : drop flushed event on the floor, time 56 too early for 368 + 0 88 27 40
drop flushed event on the floor, time 56 too early for 368 + 0 88 24 40
drop flushed event on the floor, time 56 too early for 368 + 0 88 30 40
drop flushed event on the floor, time 56 too early for 368 + 0 88 2a 40
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
drop flushed event on the floor, time 56 too early for 368 + 0 88 27 40
drop flushed event on the floor, time 56 too early for 368 + 0 88 24 40
drop flushed event on the floor, time 56 too early for 368 + 0 88 30 40
drop flushed event on the floor, time 56 too early for 368 + 0 88 2a 40</ code>
I have the same tempo drops with Muse sequencer… Maybe it’s not a bug, but there is something with my RTC…