[Ardour-Users] doctor, it hurts when i do that...
gg3137 at vegri.net
Mon Feb 13 07:47:25 PST 2012
Hi Joern et al.,
On 10/25/2011 08:26 PM, Jörn Nettingsmeier wrote:
> hi *!
> from the pathological usecases dept:
> i just created a shiny a3 session with 92 tracks, each has one region of
> roughly 15 minutes length.
> the master bus is 16ch (3rd order ambisonic), which makes for 16 outputs
> in each track, for a total of 1764 jack ports.
> when i try to load the session, ardour3 creates all the jack ports
> amazingly fast, but the connections don't show up, and the a3 process
> has been stuck at 100% cpu since i started it some 15 minutes ago.
> i'm going to give it another hour or so, since that's roughly how long
> the initial import and track creation took...
> i'd like to hear from other people with massive numbers of channels what
> your session load times are and whether i'll be likely to run into any
> hardcoded upper port limits or whatnot.
> for the record, --ports-per-application was upped to 4096 when i built
I think connecting ports takes significantly longer with jack2 than with
jack1. I quite frequently switch between jack1 and jack2, and
jack_connect command line tool as well as ardour or any other program
takes significantly longer for setting up its connections when using
jack2. Right now it took about 1-2 seconds to connect 16 ports. Which
would correspond to 30-60 minutes with your nearly 1800 port session.
More information about the Ardour-Users