hi everyone
I recently switched from my imac 2012 to macbook air m1 and now i cant open any files in fmod wirh an external sample editor. Always attached message appears. Fmod and my external sample editor both have full disk access anad there is also nothing showing off in the privacy settings in fmod while recreating the problem. Has anyone encountered the same problem?
attached screenshot
Have you tried opening files in your external sample editor outside of FMOD Studio? As in, just launching the sample editor or double-clicking on a file in a format associated with that editor in Finder?
hi, thanks for the help. What i have tried:
Hmm… I tried reproducing this issue using a MacBook Air M1 here, and the external sample editor opened without problems. I must therefore be missing some crucial part of the puzzle.
Where exactly your have you installed FMOD Studio? Are the external sample editors you’re using installed on your machine’s local drive, or on an external or network drive? Which version of FMOD Studio are you running? Can you think of anything else about your set-up that’s unusual or non-standard in any way?
thanks for checking.
MAC OS Version
15.4.1 (24E263)
FMOD Version
2.03.07 64bit
both apps are on my ssd on my macbook air
The assets folder path is:
/Users/lucienmontandon/Henry/FMOD/Henry/Assets/
I am working on a audio branch with gitHub.
Got a new variant of a message while fideling around. This message i got after selecting ocenaudio app as external sample editor:
following message appears when i select a OGG file:
thanks for looking into it. None of us devs knows how to solve it atm. we are almost finish with the game. Still some time for polishing and it would so handy if i could use an external editor again for this.
Hmm… Nothing there stands out as being a potential cause of this issue.
You mention “none of us devs.” Does this mean that multiple different people/machines are experiencing the issue? Or it is only your machine? If it’s multiple different people, is there anything their machines have in common?
What was the exact process you used to upgrade to a new machine? Did you just unbox the new machine, create a profile, and install your apps? Or did you use some kind of automated process or tool to transfer your profile and apps from the old machine to the new one?
context: I bought the macbook m1 in 2022. Never used it in the studio as i had my imac there.
when i remember correctly i did a new setup. Later on i synced a lot with my icloud account on both cmoputers. I installed fmod on my macbook air m1 separately.
Right now i am only using my MacBook air m1.
Not sure if this is helping any further. Really appreciate the effort you are making.
no i am the only “audio person”. but one dev has also triwd to figure out the problem. but no success yet.
under privacy in mac os settings in the category files&folders i have following settings. I have no assets or anything related to fmod in the google drives. Neither in icloud.
also this might help:
if i leave the external sample editor path in fmod settings empty and open a fmod asset with right click “open in external sample editor”. fmod opens the asset in vlc player. maybe we could just tell fmod to open ocenaudio instead of vlc and we could leave the path empty therefore. just guessing. 
also reproduced the problem with an older version of fmod. 2.01.05.
After some more investigation, we’ve been able to reproduce this issue. (It looks like it was caused by a change in how we invoke external applications on MacOS, and that the bug has gone unnoticed and unreported ever since.) As you’ve discovered, it only occurs when the external sample editor path has been set to something other than the default.
I’ve added this issue to our bug tracker, so it will be fixed in an upcoming release of FMOD Studio.
In the mean time, I’m afraid I haven’t been able to find any workaround that you could use to avoid this issue.
Thank you again for letting us know about this bug, and for all the information you provided to help us identify it.
okai, glad we have found out the issue. thanks for the help.
