On Thu, Jul 16, 2009 at 08:39:33PM -0400, drew Roberts wrote: > On Thursday 16 July 2009 13:51:00 Paul Davis wrote: > > On Thu, Jul 16, 2009 at 1:44 PM, Ken Restivo<ken@xxxxxxxxxxx> wrote: > > > Any ideas how to get JACK-RACK instances to start up more quickly? > > > > > > I've now got 4 of the things going for my standard live keyboard setup, > > > and it takes forever for each instance to process the entire list of > > > LADSPA plugins present... it's kind of like waiting for GIMP start up.... > > > > cd /usr/lib/ladspa > > mkdir /tmp/ladspa > > cp {comma_separated_list_of_plugins_i_want}.so $! > > export LADSPA_PATH /tmp/ladspa > > > > how well this works depends on whether a host considers LADSPA_PATH as > > a replacement for or supplement to the default search path. > > You could always do it the other way around couldn't you? > > Move the ones to don't want to a temporary location out of the normal path. > > Paul's thing worked perfectly. JACK-RACK apparently considers LADSPA_PATH to be a complete path and uses it exclusively. So I was able to move just the couple things I need for my live work over to a directory, and set my scripts to set LADSPA_PATH to just that directory before starting jack-rack. Since it's all in a script, my shell's LADSPA_PATH isn't mangled, and everything else still works fine. Cuts about 3 minutes off of the time it takes to set up for a gig; always a helpful thing. -ken _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user