[ardour-dev] MMC News

Joe Hartley jh at brainiac.com
Sun Apr 3 09:59:22 PDT 2005

On Sun, 03 Apr 2005 10:46:51 -0400
Paul Davis <paul at linuxaudiosystems.com> wrote:
> >The freeze on FFwd is still there, though.  I'll just have to remember not
> >to do that!!
> i want you to do it, and preferably with a debuggable version of
> ardour in such as way as to get a backtrace :)

OK, I have entered this along with a trace as Mantis bug 947, but here's
a summary:

It looks like my session's just too large.  This was embedded in the trace,
which I think is supposed to be what's displayed in the popped-up window:
_S_empty_rep_storage = {0, 0, 3446, 0}}, msg=
        {static npos = 4294967295, _M_dataplus = {<allocator<char>> = {<No data fields>}, _M_p = 0x913e89c "The disk system on your computer\nwas not able to keep up with Ardour.\n\nSpecifically, it failed to read data from disk\nquickly enough to keep up with playback.\n"}, static

I loaded up a smaller session (2 stereo tracks) and couldn't freeze it
at all.

So it looks like it's just how it's handling this situation of the disk
not keeping up with the program.

       Joe Hartley - UNIX/network Consultant - jh at brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa

More information about the Ardour-Dev mailing list