I used a TIGER 3rd party AVID server, which has worked great to 2021.12 , but now when I go into projects in my server they say PROJECT IS LOCKED FOR WRITE when I try to open them. I even tried removing the bay's folder from the project to see if it needed to regenerate it and that doesn't fix it. Then I put 2021.12 back and everything works fine the project goes straight in. I tried this on multiple projects and drives.
Thanks this might be a bug that has to be addressed quick because it could impact lots of users.
Hi,
Would you be able to create a support case? https://www.avid.com/learn-and-support/contact-support
The support reps there can report this to engineering.
Thanks
Editing Movie Magic.
My Equipment & System Specs
Media Composer Ultimate 2022.12.2 | Pro Tools Studio 2022.21 | Sibelius Artist 2022.12
Thanks this case is submitted.
Hello,
I have exactly the same issue with a Nexis E4 Client 19.2.2.13. iMac iOs 10.15.7
I created a new project but the problem persists. If the project is local, I can open it without any issue.
I have upgraded the client to 19.12.1 and then, I was able to open the projects in the Nexis.
Hope this helps.
Dalidá
Dalida: Hello, I have exactly the same issue with a Nexis E4 Client 19.2.2.13. iMac iOs 10.15.7 I created a new project but the problem persists. If the project is local, I can open it without any issue. I have upgraded the client to 19.12.1 and then, I was able to open the projects in the Nexis. Hope this helps. Dalidá
Fantastic thanks for sharing the solution
Yeah, I'm having the same issue on Facilis Terrablock, so I can't update any Nexis anything....
Does anyone else have a solution?
I'm having this issue too. For some reason i thought it was a windows smb permissions issue but I guess its not. This should be fixed.
For the first time in years, I created a case No. for this, too.
My MXF MediaFiles folder is inaccessible on third-party storage as well (yes, I made sure to check the 3rd-pary emulation feature).
Work around is, of course, to put the Avid project on a local drive -- as well as any MediaFiles -- but this is not an acceptable solution.
For those who care;
Facillis is reporting that other 3rd-party vendors are also experiencing the problem. I'm now in the waiting period of my case, but have decided to roll back to MC 2021.2. Until a fix has been issued, I suggest all do the same.
J
I created a support case and support came back to me saying "... we wish to help you but we are limited because we don't support 3rd party storage."I also wrote an email to Chris Bove, explaining the problem in detail but he did not come back to me so far.
The problem only occurs when the file system's (Volume) "ofstypename" is set to "AvidUnityISIS". When removing this parameter, MC 2022.4 will open the project just fine but the bin locking won't work.
sirpuls: I created a support case and support came back to me saying "... we wish to help you but we are limited because we don't support 3rd party storage."I also wrote an email to Chris Bove, explaining the problem in detail but he did not come back to me so far. The problem only occurs when the file system's (Volume) "ofstypename" is set to "AvidUnityISIS". When removing this parameter, MC 2022.4 will open the project just fine but the bin locking won't work.
Sorry to hear this.
Chris gets hundreds of emails. You could try following up with him or emailing Raff: raff.condalor@avid.com
sirpuls:I created a support case and support came back to me saying "... we wish to help you but we are limited because we don't support 3rd party storage.
Avid, I'm not affected by this issue but want to chime in here. Nobody asks you to support 3rd party storage. But when you put:
'Enable bin sharing on 3rd party storage emulating Avid NEXIS/ISIS'
as an optional setting in Media composer then you are responsible for that part of the code and its fuctionality.
Choose! Either leave this setting out or help your support paying customers when they use an alternative to Nexis succesfully for years. Or, if you decide to revoke support for 3rd party storage. please state that clearly.
Jeroen van Eekeres
Technical director, Broadcast support engineer, Avid ACSR.
Always have a backup of your projects....Always!!!! Yes Always!!!!
A.V.I.D....... Another Version In Development
www.mediaoffline.com
I presume Avids line is that if a 3rd party emulates Nexis then it will work (because it works with Nexis) if the 3rd party storage isn't emulating nexis completely or accuratley then it won't work as required. But thats not Avids fault. I'm not even sure how Avid could resolve that.
Broadcast & Post Production Consultant / Trainer Avid Certified Instructor VET (Retired Early 2022)
Still offering training and support for: QC/QAR Training - Understanding Digital Media - Advanced Files * Compression - Avid Ingest - PSE fixing courses and more.
Mainly delivered remotely via zoom but onsite possible.
T 07581 201248 | E pat@vet-training.co.uk
Uhm.... if Avid ends up taking this stance, they are going to lose a LOT of customers... me included.
I have to disagree. This specific method of emulation does not mess with Avid code, nor does it change how the underlying file system works. It simply adds a parameter (string) to the mount options of the file system. This has worked for many years and suddenly stopped working with MC 2022.4. Removing that "emulation" string makes Avid work again on the shared storage.. but of course bin locking is then no longer available. To me this smells like a MC bug but we will see.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller