Hello Avid Community! First time poster here
I've recently encountered the above error when trying to render a Timewarp effect (FluidMotion).
I am currently running Avid 2022.4.0.56108 on macOS Monterey (12.1) on a Macbook Pro.
I've attempted to look up this issue before but have run in to the same Avid KB article about checking permissions. All permissions for Avid MediaFiles and Avid MediaComposer itself are set to Read & Write for: Myself, everyone and wheel.
I only have one drive on this machine and it is my Macintosh HD. Transcoding works, as well as AMA Linking.
It is strange that I can use Avid properly (minus this effect issue), yet it's spitting this permission error!
System specs are below
Thank you
Nick
Update:
This was fixed by creating a new APFS volume/partition in DiskUtil, then migrating my Avid MediaFiles to the root of that drive.
Thanks
Hi Nick
Randy Rike, One of our forum moderators explains it nicely in this post.
https://community.avid.com/forums/p/36514/203145.aspx#203145
If the read write is correct then this is what will fix it.
Marianna
marianna.montague@avid.com
Unfortunately, the CREATE APFS VOLUME option in the Disk Utility menu is grayed out. If you have another suggestion for creating one I would love to try this idea.
Thank you.
Stephen Les
Hi Stephen,
See this link for more info:
Add, delete or erase APFS volumes in Disk Utility on Mac
You should be able to:
Go to Diskutil > (with the top volume selected) Create new APFS volume > Migrate Avid MediaFiles
Is there any reason you can't create the new APFS volume?
Hi Marianna,Thanks for your reply.
Looking at this further, it looks like this is causing issues when Avid MediaFiles is nested inside folders (as opposed to the root of a drive), even when permissions are set correctly
The original file folder structure for Avid MediaFiles (upon install) on macOS is:/Volumes/Macintosh HD/Users/Shared/Avid MediaFiles
When said folder is in this location, certain things can't be performed (i.e. rendering effects).
Once Avid MediaFiles is moved onto it's own drive and the folder on the root of the drive, the issue resolves itself.Is this something that can be passed on to the developers? Or is this a more Apple-centric problem...?
Thanks!Nick
I had this same error message when trying to mixdown a sequence to OP1a on a Mac M1 Pro running Monterey 12.5. I ran first aid on my Macintosh HD using Disk Utility, relaunched avid and that fixed the issue.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller