Slow startup on new SSD based system

[Al Stu]

So now that the slow startup is solved. Back to the error.
Don't think it is so harmless. Nor should exist. It is not there in 2.3.0 and it appears (according to the log) to delay startup a couple seconds. Never satisfied. Those 2 seconds are a big percentage of the 3 second startup.

Code: Select all

05:11:56: Audacity 2.3.2
05:11:56: Error: Couldn't find symbol 'AudacityModule' in a dynamic library (error 127: The specified procedure could not be found.)
05:11:58: Trying to load FFmpeg libraries...
05:11:58: mLibAVFormatPath ('C:\Program Files (x86)\FFmpeg for Audacity\avformat-55.dll') is not empty. Loading from it.
05:11:58: Looking up PATH environment variable...
05:11:58: PATH = 'C:\Program Files\Broadcom\Broadcom 802.11 Network Adapter;C:\PROGRAM FILES (X86)\INTEL\ICLS CLIENT\;C:\PROGRAM FILES\INTEL\ICLS CLIENT\;C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\WINDOWS\SYSTEM32\WBEM;C:\WINDOWS\SYSTEM32\WINDOWSPOWERSHELL\V1.0\;C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL;C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT;C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL;C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT;C:\PROGRAM FILES\ACER\REMOTE FILES\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files\Git\cmd'
05:11:58: Checking that 'C:\Program Files (x86)\FFmpeg for Audacity' is in PATH...
05:11:58: Warning: FFmpeg directory 'C:\Program Files (x86)\FFmpeg for Audacity' is not in PATH.
05:11:58: Temporarily prepending ';C:\Program Files (x86)\FFmpeg for Audacity' to PATH...
05:11:58: Checking for monolithic avformat from 'C:\Program Files (x86)\FFmpeg for Audacity\avformat-55.dll'.
05:11:58: Error: Couldn't find symbol 'avutil_version' in a dynamic library (error 127: The specified procedure could not be found.)
05:11:58: Error: Couldn't find symbol 'avcodec_version' in a dynamic library (error 127: The specified procedure could not be found.)
05:11:58: avformat not monolithic
05:11:58: Loading avutil from 'avutil-52.dll'.
05:11:58: Loading avcodec from 'avcodec-55.dll'.
05:11:58: Loading avformat from 'C:\Program Files (x86)\FFmpeg for Audacity\avformat-55.dll'.
05:11:58: Returning PATH to previous setting...
05:11:58: Actual avutil path C:\Program Files (x86)\FFmpeg for Audacity\avutil-52.dll
05:11:58: Actual avcodec path C:\Program Files (x86)\FFmpeg for Audacity\avcodec-55.dll
05:11:58: Actual avformat path C:\Program Files (x86)\FFmpeg for Audacity\avformat-55.dll
05:11:58: Importing symbols...
05:11:58: All symbols loaded successfully. Initializing the library.
05:11:58: Retrieving FFmpeg library version numbers:
05:11:58:    AVCodec version 0x373466 - 55.52.102 (built against 0x373466 - 55.52.102)
05:11:58:    AVFormat version 0x372164 - 55.33.100 (built against 0x372164 - 55.33.100)
05:11:58:    AVUtil version 0x344264 - 52.66.100 (built against 0x344264 - 52.66.100)
05:11:58: FFmpeg libraries loaded successfully.

[steve]

Back to the error.

I don't know the cause of that error message, so I've written to the developers asking about it. I'll post back when/if I know more.

[steve]

it appears (according to the log) to delay startup a couple seconds.

I don't think that's the case.

One of the developers has replied, saying that he thinks the message probably comes from the operating system when executing a line in ModuleManager::LoadModule

Code: Select all

ModuleMain audacityMain = (ModuleMain) lib->GetSymbol(wxSTRINGIZE_T(MODULE_ENTRY),
                                                            &success);

Where the module manager found a dll that looked like an Audacity module, but was not a valid Audacity module, so stopped trying to load it.
The message would be returned at the time that the module manager decided the "module" could not be loaded, which was at 05:11:56 (the same second that Audacity 2.3.2 started loading). So the time taken by this error is less than a second.

The next logged event is at 05:11:58 when Audacity attempts to load FFmpeg. This occurs after Audacity has scanned the audio system. It is reasonable / normal for that scan to take a couple of seconds. Other initialisation stuff will also be occurring during that 2 second gap.