-
Notifications
You must be signed in to change notification settings - Fork 35
Will not import a newly recorded MP3 but will import other MP3s #98
Comments
I'm guessing the converter has a problem. What's the name of it? |
Blumway cassette tape to mp3 converter. And this is the first time Audacium / Audacity has had a problem importing the mp3s it creates - and only the mp3s it creates. It's handled them fine before. |
And suddenly, without my doing anything to cause it, Audacium can't find my recording and playback devices!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WHY???????????????????????????????? |
@JimFlasch Can you, when you launch Audacium, go to the Help menu on the top and show the logs? There should be a section called "Logs" and in there you should be able to show a Log window, where you basically get all the logs. Perhaps there'll be more information. |
Here's what the log is saying: 18:53:16: Audacium 1.0.0-beta-20211210 |
Right. You need to download a specific version of FFmpeg for Audacium (5.0 is too recent). Go there to see how to install it: https://manual.audacityteam.org/man/installing_ffmpeg_for_windows.html. Then, manually locate FFmpeg again (go to the settingts, then Libraries, then Find FFmpeg or something like that) |
Alright, now I can import the file I couldn't import before; however, my other, more recent problem - the sudden inability to find and recognize my recording and playback devices (as of 5 days ago) - persists. How do I fix that? |
@JimFlasch Could you send your logs now please? |
Here's my latest log: 23:01:44: Audacium 1.0.0-beta-20211210 Like I said in my last post, I can now import newly recorded mp3 files; it's the sudden inability of Audacium to find and recognize my recording and playback devices (as of 22 days ago, now) that's my current problem. |
Describe the bug
Will not import a newly recorded MP3 but will import other MP3s
To Reproduce
Expected behavior
BOTH mp3s should import without problems!
Additional information (please complete the following information):
The text was updated successfully, but these errors were encountered: