it appears to be video h/w + driver related, not ardour related. but hard to say.
On Fri, May 3, 2013 at 5:31 PM, Fons Adriaensen <[email protected]> wrote: > On Fri, May 03, 2013 at 05:18:03PM -0400, Paul Davis wrote: > > On Fri, May 3, 2013 at 5:14 PM, Fons Adriaensen <[email protected]> > wrote: > > > > > > > > The second one is an Ardour2 session that worked perfectly > > > on another similar PC, but becomes completely unresponsive > > > on the one to be used. It has four mono tracks and three > > > 10-channel ones, and little else. DSP load is not the problem, > > > it's less than 15%. Things look like it's the graphics. > > > > > > > This follows reports we've seen on IRC many/several times, with no > > particular combination of video h/w and drivers identified. > > Could this be related to reading peak files (which I assume will > happen when the editor display is updated) ? > > Ciao, > > -- > FA > > A world of exhaustive, reliable metadata would be an utopia. > It's also a pipe-dream, founded on self-delusion, nerd hubris > and hysterically inflated market opportunities. (Cory Doctorow) > >
_______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
