2.0.3 Really slow to launch

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
panjan
Posts: 14
Joined: Sun Dec 22, 2002 5:43 pm
Location: Leeds
Contact:

2.0.3 Really slow to launch

Post by panjan » Fri Mar 28, 2003 10:25 pm

Hi

I'm use XP Pro and never had the the really slow program launch with 2.0
It can take about 45 seconds to start and switching between the 2 views is slower - about 5 seconds. Also it just crashed on me for the first time ever.
Has any one else had this slowness.

Michael

Alex
Posts: 4006
Joined: Wed Apr 03, 2002 1:07 pm
Location: Ableton Headquarter

Post by Alex » Fri Mar 28, 2003 10:41 pm

Hi panjan,

we never heard of such slowness problems on the Windows side.
Do you mean with "swtching between the 2 views" the views inside Live or switching between Live and other applications?

The startup time could be related to some VST's in the VST folder. You could try to set the VST path to another empty folder and start again to see if the starting time is shorter.

regards,
Alex

panjan
Posts: 14
Joined: Sun Dec 22, 2002 5:43 pm
Location: Leeds
Contact:

Post by panjan » Fri Mar 28, 2003 11:28 pm

Hi

I changed the VST fx folder to an empty folder.

The 2 Live views now switch over quickly.
What should I now do about regaining the VST fx items?

The program launch time - I just timed it and it took 1 minute 10 seconds before the splash screen disappeared and the program came up.

Michael

Alex
Posts: 4006
Joined: Wed Apr 03, 2002 1:07 pm
Location: Ableton Headquarter

Post by Alex » Mon Mar 31, 2003 11:49 pm

Hi Michael,

the question now is how these VST plugs affect the starting time.
I could imagine 2 reasons:

1) There are a lot of VST plugs

or

2) It's just one VST plug that could be the reason for needing so much time.

What you could do is to copy some of your VST plugs (maybe the half) into this temporary folder start Live again a watch how much time it needs.

regards,
Alex

mm303

Post by mm303 » Tue Apr 01, 2003 11:26 am

I have similar problems ...

when I close live an the last folder I opened contains around 2000 wav files... live saves the last position of opened folders....

so at the next startup it takes a lot of time until live has recognized all the samples in the folder...


a short trick: renaming the folder before startup ... and live comes up quickly...


cheers,
matthias

panjan
Posts: 14
Joined: Sun Dec 22, 2002 5:43 pm
Location: Leeds
Contact:

Post by panjan » Tue Apr 01, 2003 6:21 pm

Thanks guys.

OK. I renamed my WAV samples folder and the program started in about 5 seconds.

In setup I re-pointed the VST folder to the Steinberg VSTPlugins folder and the program still only takes 5 seconds to start.

So it would appear that it is the samles folder that is at fault - it contains hundreds of wavs.

So its just the way that the program possibly builds some list of WAVS before appearing.

Regards

Michael

cr

Post by cr » Tue Apr 01, 2003 9:59 pm

install the leaked sp2 mem patch for XP, fixes long-launch problems for a lot of programs

Guest

Post by Guest » Sun Apr 06, 2003 1:29 am

cr wrote:install the leaked sp2 mem patch for XP, fixes long-launch problems for a lot of programs
Where can I get this patch?

I have a same kind of problem with live 2.0.3 but renaming .wav folders
or changin vst-paths won't help. Live starts in about 2-5 minutes and
behaves very slow. System is P4/2.4, Terratec ews88 with XP SP1.

Also the switch for the interface of vst-effect is not working anymore, can't see the vst-effects own interface.

Any ideas?

--lauri

panjan
Posts: 14
Joined: Sun Dec 22, 2002 5:43 pm
Location: Leeds
Contact:

Post by panjan » Sun Apr 06, 2003 12:57 pm

Me too - I'm an MSDN subscriber and still can't find that patch. Since I have my XP auto download windows updates I'm assuming I must have them all.

user

Post by user » Fri Apr 11, 2003 10:57 am

*bump*

lauri

Post by lauri » Thu May 01, 2003 12:54 pm

cr wrote:install the leaked sp2 mem patch for XP, fixes long-launch problems for a lot of programs
installed it but it did'nt fix the problem.

-l

Locked