- Home /
Unity3d Mac project freezes when importing ogg/mv4 files on external hard disk
Updated to Catalina on Mac Pro, since then if I try to open a project on an external hard disk it will freeze when it encounters mv4 or ogg files. The import will stop on the first file of this type that it encounters. Have to kill the Unity process, and sometimes even after the process is force quit the import dialog will remain up. This implies that Unity started a separate importer thread, possibly an external helper app, or something like that. Just guessing.
After updating to Catalina any time I open an application the OS goes through a "verification" step the first time that takes a long time. I am wondering if the process handling the import is something like this. Catalina won't let it run until it is verified, and because it's a helper app that Unity uses, it never gets verified. Unity waits forever for the import process to complete.
Can you please report this issue so that the $$anonymous$$m can try to reproduce it? https://support.unity3d.com/hc/en-us/articles/206336985-How-do-I-submit-a-bug-report-
hi @akeplinger - did you find a fix for this? I am encountering the same issue: I download and try to import an old project into Unity 2018.2.21f1 on my $$anonymous$$acBook Pro. As it builds the library it freezes on ogg files.
This is $$anonymous$$ac specific: I tried the same import on a PC and it worked fine.
Thanks much!
CC: @AskCarol
Answer by akeplinger · Jan 27, 2020 at 08:44 PM
I found the files, in one case, and resaved them. It was a punt, because I don't know what could have been different in the sound settings. I had the same issue with a different program that had way too many ogg files than I could resave, and in that case I found using Unity Hub that the problem only seemed to affect certain versions of Unity. In this case I updated to 2019.3 and I could import. I was trying to use 2018.x and that was freezing. Your milage may vary, because I also installed a new larger hard disk and migrated files from external USB drives to internal SSD so compiling could be faster (like x4 faster) and that might have had some impact. At one point I thought the problem was because Catalina handles external volumes differently than internal, but that theory didn't hold up. Sometimes you try everything you can think of and have no idea which thing did the trick.
Answer by dcolman · Jan 27, 2020 at 09:24 PM
Got it. Yeah, I am actually not importing from external drive; downloaded project from bitbucket to my SSD and tried to import and the freezing happened. I have a PC that I can use so I’m just using that for now as I’m working on Android build; I’ll have to keep tinkering so I can do future iOS builds. It’s a released game so I’m not thrilled with the risk of updating the engine. I’ll update if I find something.
Answer by Kargan · Mar 20, 2020 at 11:21 AM
Hi,
I have the same issue and can't find a solution, what do you mean by "resaving" them @akeplinger ?
Hi Kargan,
Could you provide some more information about your setup? For instance, which version of the Unity editor are you using, and which operating system are you running?
If you are on macOS Catalina (10.15), you may be running into an issue with older versions of the Unity editor. Catalina dropped support for 32-bit processes, which older versions of Unity were using to import audio files.
Here's the list of Unity versions that are supported on macOS Catalina: 2017.4.32+ LTS 2018.3+ LTS 2019.1+
Yes, I am on $$anonymous$$acOS Catalina and I'm using Unity 2018.1.9f2. This is a released project so I don't really want to update my editor, is there a workaround for this issue ?
If you don't want to update your editor, there are two workarounds, but neither seem ideal.
Downgrade to macOS $$anonymous$$ojave (10.14). This was the last version of macOS that supported 32-bit components.
Install Windows and move your Unity project to that OS. Windows 10 still supports 32-bit components.
Realistically, my suggestion would be this:
Backup your Unity project.
Install Unity 2018.3 (which is the $$anonymous$$imum version of 2018 that supports macOS Catalina).
Try opening your Unity project in 2018.3 to see if it still works as expected. If so, congratulations! The problem is solved! If not, then restore your backed up version of your Unity project and go with one of the other options (downgrade macOS or install Windows).
I'm guessing those aren't the suggestions you were hoping for, but unfortunately they are the best ones that I am aware of.
Answer by Pavenko1 · Dec 11, 2020 at 11:29 AM
Hi, I have same problem and fix it. You should replace two files in FSBTool folder in Unity package in unity folder, long story short: you should path your unity from 32bit to 64bit.
Programs folder/Unity/Hub/Editor/YOUR_EDITOR/Unity(Show content of package)/Contents/Tools/FSBTool/
Patch 64bit: https://drive.google.com/file/d/1hIRyJ5RrZU2yZYb83R5IZ5Su1Te9vuk2/view?usp=sharing
Your answer
Follow this Question
Related Questions
Help to solve freezes when web client start playing downloaded audioclip 0 Answers
Videos Play with Weird Shadow Artifact 0 Answers
Unity freezes when In try to import a package (890 MB) 1 Answer
Why import will work only with some .mov files? 0 Answers
Infinite video loop without crashing? 0 Answers