Hi, I don’t use NW drives, just a couple of internal and USB drives (which I have all disconnected at the moment). I have just now also disconnected the Internet, rebooted and started Audacity => No change as far as startup time is concerned.
alfred
That’s good. The developer has made a change that should prevent that error from appearing in future versions of Audacity.
So that error was clearly not the cause of the delay.
Having ruled out other possibilities, I think it’s most likely what is happening is that Audacity is picking up a dll in the plug-ins path that is incompatible with Audacity. Have you installed many plug-ins on this machine? Do you use other audio production software on this computer?
I will try another clean install without any plugins installed.
Yes, I am using a couple of other audio software: Spectralayers Pro, Acoustica, RavenPro, Seawave and few more, mainly Bat stuff. I will check, which ones are not on my Laptop, where Audacity starts very fast. I have recently installed SASLab Lite, which ist not on my other machine. Will check whether I can find any incompatibilities related to this.
alfred
Please do keep us informed. If we are able to provide the Audacity developers with step to reproduce the issue, then they may be able to do something about it.
Hi there,
since nothing has worked for me to overcome the problem of Audacity’s long start-up time, I have tried a sledge-hammer approach: Gone back to an image from mid last year where Audacity started like a rocket (less than 2 seconds). All I have done from there is updating to the latest Win10 and bang - it takes 10 seconds for Audacity to start. Still better than the about 20 seconds from before, but all I can think of now is giving up, I am running out of ideas. I had considered a complete new-install, but I am not sure anymore that this would really help.
Alfred
One thing that came to my mind: I am running an English version of Win10 on my machine from our time in Australia. This is set to German in the meantime, but that was already the case for the version that worked for me in 2019. Maybe it triggers any thoughts out there?
Hi guys, some real progress to report on this topic:
The start time got worse and worse and by chance I had the task manager open at one instance and noticed the following: As soon as I started Audacity the “Diensthost:Lokaler Dienst (Netzwerkeinschränkung)” subline: Windows-Audio popped up and used a very high CPU load. Sorry, for quoting the German text, it should translate to something like: Servicehost: Local Service (Netwerk restrictions) // Windows Audio. The load was very high until Audacity finally opened 30 seconds later.
I have then gone to the Device Manager and opened the Audio Devices Tab (making sure that also “Show inactive Devices” was ticked). I have then radically de-installed every single Audio Device, which was shown there. There were some dubious Microsoft devices visible, which I had no idea what they were good for.
I have then de-installed Audacity and finally restarted the computer. After the computer came up, I have gone back to the Device Manager und checked the found Audio Devices. All the dubious Microsft ones were still gone.
Re-installed and started Audacity and yes: Up and running in a second or so.
Happy.
Cheers Alfred