I’ve just installed Unity to version 2022.3.17 on MacOS 14.2.1 in a Mac mini 16 Gigabytes 1 tera with an M2 processor. Lots of free space and memory available. I import a project from version 2022.3.16 and tried 3 times, and I always get this error you can see below in 5 files.Example:
Errors during import of AudioClip Assets/Music/myfile.mp3:
FSBTool ERROR: Internal error from FMOD sub-system.
FSBTool ERROR: Internal error from FMOD sub-system.
This 5 audiclips where working perfectly in the last 2022.3.16 and below, they are old mp3 files that have no problem. Any ideas? Thank you.
Edit: I can confirm this does not happen with 2022.3.16, just imported with no problems.
I have same issue on Windows 11.
2022.3.16 and before: No error
2022.3.17: Some mp3 files have same error, these files are made by GarageBand on macOS.
I guess this update:
Editor: Updating fsbtool to match the current FMOD version. (UUM-32863)
Well it’s nice to see I’m not alone with this. I work with Mac and my mp3 were created with Audacity. Maybe it’s related to the way Mac generates mp3 files or the updated fsbtool might be responsible of the error. I tend to think of the second option.
I have tried, delete the library folder, remove the mp3 file, regenerate the library folder, copy the mp3 file back. It can play the mp3 file without crash. ?? What the problem is?
It only happens with some mp3 files when upgrading the project to 2022.3.17/18. I have many mp3 but some of them were working fine until these versions. Don’t know why, they are old mp3 files I have used in other projects with no problems, and until 2022.3.16 they were working fine.
I’ve been able to solve it by regenerating a new mp3 file from the original with Audacity. I can regenerate the 5 mp3 that give me problems and go to 2022.3.18, but as I said those mp3 are files that worked perfectly until 2022.3.16.
This issue continues in 2022.3.19f1. A workaround is, as ScottyDSB mentioned, importing it to Audacity, then exporting from Audacity to the location where it was again in the project. Overriding the original file worked for me.
I am using the same version mentioned 2022.3.19f1. Audacity has been my solution so far. At first, I was fixing only a few files manually. Recently though, I imported a new batch of 40-50 files (new language addition to project) with over half of them hosed. Imagine the mental screeching thinking I had to manually fix them.
So, I decided to investigate if Audacity had batch processing. Turns out pre-version 2.3 it was called “Chains”, post v2.3 it’s called “Macros”. I am using v3.4.2 and I was able to successfully create a macro to batch fix every audio file with an error.
Go to: Tools/MacroManager
Click [New], name your Macro “Fix Mp3 Files” or whatever.
Add [Insert] these commands before the "- END - " Command
Macro_FixMP3Files ← Isn’t this convenient?
Export as MP3
END -
Click the [save] button.
Click on the files button at the bottom (make sure your macro is select on the left nav window)
When file window opens navigate to the folder with your hosed audio and select all or the messed of files individually using [CTRL] click select method.
After selection click the [Open] button and Audacity will convert the files.
Be aware that Audacity puts the new files in places you may not expect. For me, and I assume, it was a default folder: \Documents\Audacity\macro-output. Not sure if there’s a path setting somewhere in preferences.
