After I updated to Unity 2022.3.18, some mp3 files had errors.
The message is as follows
FSBTool ERROR: Internal error from FMOD sub-system.
FSBTool ERROR: Internal error from FMOD sub-system.
(Filename: ./Modules/AssetPipelineEditor/Public/AudioImporter.cpp Line: 1062)
@ - you keep breaking LTS versions, THIS.HAS.TO.STOP!
This issue for example, you say it should be fixed in the next version, but the next version is out and it is still present. For that matter your comment could be taken as for version 2022.3.19 or 2022.4.X or 2023.X.X please be more specific.
Do you have structured testing, both programmatic AND human? It does not seem that way from the issues I have been reading about.
The fix is currently on the bench, pending for QA. As you might be aware, the company is “going through a phase” right now, and this part of the machine is currently impacted.
The issue is that there was an accidentally incomplete backport on a complicated MPEG codec fix. I am sorry that it’s taking so long, but we should get there soon.
On a side note, it is super relevant that you voice your concerns, and it helps us build a case about what should be improved in our media stack. Codecs and media framework is one of our top priorities.
We do have a testing infrastructure, and while it’s not perfect it catches a lot of small errors! The human side for testing media quality over all platforms is a complicated one, and it’s practically impossible to do all manuals tests for all bugs for all platforms. In this case, we’re incrementally building a library of files known to have failed to test for regressions in the future.
Known issue with Unity 2022.3.18 and mp3s. Try re-encoding the mp3s with a different tool (like Audacity). Otherwise, wait for a Unity update or downgrade to a previous version (2022.3.17 might work). Good luck!
Hi there. Are people still seeing this error? Interestingly, I’m seeing it when building on Unity 6000.2.8f1 on Linux, but NOT when building on Unity 6000.2.8f1 on Windows. The downstream effect is that my builds work locally, but not in CI. Can anyone offer any suggestions or guidance, other than converting MP3 to WAV? Just wondering if that’s the only option I have.
I would check is if afconvert is available on your path, it might be leveraged in the MP3 processing flow; a valid return from afconvert --help in terminal should answer that.
Then, if that’s fine, I’d try the same with an OGG file. If the same error comes up, then we should probably file a bug.
$ afconvert --help
Command 'afconvert' not found, did you mean:
command 'affconvert' from deb afflib-tools (3.7.20-1)
command 'sfconvert' from deb audiofile-tools (0.3.6-6)
command 'auconvert' from deb nas-bin (1.9.4-7build1)
Did you happen to mean either affconvert or sfconvert? Either way, neither one is installed on my system. This is on Ubuntu 24.04.3 LTS, for what it’s worth.
Haha you’re right, afconvert is the lib that is used in a Mac context, not on Linux. The one I was actually thinking about is avconv which is used for some conversions, notably to AAC, the format used for serialized audio on WebGL.
The decoder used would be FMOD’s mpeg decoder for the MP3->WAV, and then avconv for WAV->AAC. Considering the error you’re seeing, I imagine the first half of this pipeline must be broken, but what’s strange is that the mpeg decoder should be the same on both Windows and Linux.
Does this error happen with any MP3 file or only specific ones? If you’re simply unable to import any file like this, you should definitely file a bug and provide one of the failing MP3.
Oh dear. This is the part where I sincerely apologize for wasting your time…
It turns out that the issue had nothing to do with MP3s specifically. Rather, it’s because my CI server didn’t have git lfs installed, so I only had references to any and all large files. When I was poking around in the logs, I happened to notice an .fbx import error, and then it dawned on me what might be happening. I checked the CI server, and sure enough… I hadn’t installed LFS. Doh.
After installing LFS and running git lfs fetch, I expected I’d be good to go, but I was still seeing issues for whatever reason. Rather than chasing that down, I just recloned the repo, everything worked like a charm.
Thank you for your time nonetheless. Much appreciated!