Audacity error - File open command

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Post Reply
mikemoorcroft
Posts: 1
Joined: Thu Feb 04, 2021 1:31 pm
Operating System: Windows 10

Audacity error - File open command

Post by mikemoorcroft » Thu Feb 04, 2021 1:52 pm

My Audacity is up to date, my system is windows 10 aspire es1.

So I had a project that was already saved. I made some changes, closed audacity and then forced a shut down my laptop. I get the message when reopening the project:

'Error Importing, xx is and Audacity Project File, Use the File-Command to open any audacity Projects.'

This doesn't work, I've gone into the autosaves - there aren't any. I've included the report below. Can someone please help me? (and also in a really easy to follow step-by-step way because I'm a total novice! :D


13:43:37: Audacity 2.3.3
13:43:37: Error: Couldn't find symbol 'AudacityModule' in a dynamic library (error 127: The specified procedure could not be found.)
13:43:42: Trying to load FFmpeg libraries...
13:43:42: Trying to load FFmpeg libraries from system paths. File name is 'avformat-55.dll'.
13:43:42: Looking up PATH environment variable...
13:43:42: PATH = 'C:\Program Files\Broadcom\Broadcom 802.11 Network Adapter;;C:\Program Files (x86)\Intel\TXE Components\TCS\;C:\Program Files\Intel\TXE Components\TCS\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\TXE Components\DAL\;C:\Program Files (x86)\Intel\TXE Components\DAL\;C:\Program Files\Intel\TXE Components\IPT\;C:\Program Files (x86)\Intel\TXE Components\IPT\;C:\WINDOWS\System32\OpenSSH\;C:\Users\mikem\AppData\Local\Microsoft\WindowsApps;C:\Users\mikem\AppData\Roaming\Dashlane\4.6.6.23032\bin\Firefox_Extension\{442718d9-475e-452a-b3e1-fb1ee16b8e9f}\components;%DASHLANE_DLL_DIR%;'
13:43:42: Checking that '' is in PATH...
13:43:42: FFmpeg directory is in PATH.
13:43:42: Checking for monolithic avformat from 'avformat-55.dll'.
13:43:42: Error: Failed to load shared library 'avformat-55.dll' (error 126: The specified module could not be found.)
13:43:42: Loading avutil from ''.
13:43:42: Error: Failed to load shared library '.dll' (error 126: The specified module could not be found.)
13:43:42: Loading avcodec from ''.
13:43:42: Error: Failed to load shared library '.dll' (error 126: The specified module could not be found.)
13:43:42: Loading avformat from 'avformat-55.dll'.
13:43:42: Error: Failed to load shared library 'avformat-55.dll' (error 126: The specified module could not be found.)
13:43:42: Error: Failed to load FFmpeg libraries.
13:43:42: Error: Failed to find compatible FFmpeg libraries.
13:43:42: File name is C:\Users\mikem\Desktop\Morpheus Invocation for Prophetic Dreaming.aup
13:43:42: Mime type is *
13:43:42: Opening with libsndfile
13:43:42: Opening with liboggvorbis
13:43:42: Opening with libflac
13:43:42: Opening with lof
13:43:42: Opening with libav
13:43:42: Error: Importer::Import: Opening failed.

steve
Site Admin
Posts: 80752
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Audacity error - File open command

Post by steve » Thu Feb 04, 2021 6:55 pm

I suspect that the project file is fatally damaged (unrecoverable).
If you would like us to check, attach the "Morpheus Invocation for Prophetic Dreaming.aup" file to your reply.
(See here for how to attach a file to your post: viewtopic.php?f=49&t=64936

I'd recommend updating Audacity to the current 2.4.2 version at your earliest convenience (See: https://www.audacityteam.org/download/windows/)
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

Post Reply