Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 2185 - Import2: Incorrect error message if file not found
Import2: Incorrect error message if file not found
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Other
2.3.3
Per OS Linux
: P3 RepeatableAll
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-02 07:15 UTC by Steve Daulton
Modified: 2019-09-01 14:25 UTC (History)
2 users (show)

See Also:
Steps To Reproduce:
1) Create a Macro containing: Import2:Filename="filename.wav" where "filename.wav" is the name of a file that does not exist. 2) Apply the the Macro to the current project. Note that the error message is misleading.
Release Note:
When using the scripting command "Import2:", if the specified file cannot be found, Audacity returns a misleading error message indicating that the file type is not recognized.
First Git SHA:
Group: ---
Workaround:
Closed: 2019-09-01 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Daulton 2019-08-02 07:15:32 UTC
Macro Scripting command Import2:

If the file specified in the Import2: command does not exist, the Macro returns the error:

Audacity did not recognize the type of the file "<filename>".
Try installing FFmpeg. For uncompressed files, also try File > Import > Raw Data.


A correct error message would be something like:

"<filename>" not found.
Comment 2 Peter Sampson 2019-09-01 14:25:30 UTC
Testing on W10 with audacity-2.3.3-alpha-341-72f36f8a82e9ed4a184b9029cb53780e62a9bea8

Message now says File <filename.wav> not found.

This is much clearer