[Ardour-Users] multiple ardour instances and event pool out of memory error
plutek at infinity.net
Tue Nov 16 18:55:08 PST 2010
Excerpts from Paul Davis's message of Tue Nov 16 21:20:04 -0500 2010:
> On Tue, Nov 16, 2010 at 8:30 PM, plutek <plutek at infinity.net> wrote:
> > 2. when i operate as above, the first session (the "source") often throws a "CRITICAL: event POOL OUT OF MEMORY - RECOMPILE WITH LARGER SIZE!!" error as soon as i start the second session (the "mix"). it's not predictable, and will happen or not happen at random with successive attempts two start the two sessions, even without changing the session files. i've tried all the stuff about disabling MMC, which has been referred to previously with respect to this issue, but it doesn't seem to provide a consistent solution. i'm using current SVN (build 8048). any clues??
> you should stop trying to solve the problem, and simply rebuild after
> applying this patch:
> Index: libs/ardour/session_events.cc
> --- libs/ardour/session_events.cc (revision 7909)
> +++ libs/ardour/session_events.cc (working copy)
> @@ -37,7 +37,7 @@
> using namespace PBD;
> using namespace std;
> -MultiAllocSingleReleasePool Session::Event::pool ("event", sizeof
> (Session::Event), 512);
> +MultiAllocSingleReleasePool Session::Event::pool ("event", sizeof
> (Session::Event), 1024);
> Session::add_event (nframes_t frame, Event::Type type, nframes_t target_frame)
thanks very much, paul!
i'm also not getting the occasional xruns that i used to get in this situation at transport start/stop.
More information about the Ardour-Users