Lock symbol not showing in Production

[Sedef_iari]

Hey everyone,

I am a seasoned AE working on a feature doc in Production and I am encountering an issue I never met before.

The production folder is on Dropbox. I've been using Dropbox and production for years and never had this issue.

When the editor enters a project I can see the .prlock in the Dropbox folder and the consequent red lock symbol locking the project in Production. For some projects though - like the one in screenshot - no red lock symbol appears. We do have the .prlock appearing in production. So, although there is someone working in that project - the projects (see screenshot) appears to be 0KB and when I try to enter from Production panel the "Project appears to be damaged" warning pops up. If I try to open the project at Finder level folder Dropbox, the project opens and shows the symbol of only reading access - yet not red lock symbol. 

In addition,  when the editor try to save the project that she is in - writing and reading access - she reaceves this. And no one else is in that project...

Media cache goes locally (SSD or machine).

Production settings are correct on my side and editor side - all goes to dropbox.

Dropbox setting is online only.

We are working M1 and M1 Max from 2021.

No idea what's going on... Any ideas? Suggestions?

[mattchristensen · Accepted solution]

@Sedef_iari Adobe specifically recommends against working collaboratively in a production hosted in consumer file sysncing service like Dropbox, Google Drive, etc for reasons exactly like this. Productions assumes that all of the files inside (projects and the lock files) are fully there and existant. My best guess is that when you're seeing issues, Dropox has decided to host that file as only a stub on the local file system so its contents are not actually present on disk for Premiere Pro to use.

You could try setting Dropbox to make new files default to Available offline as that is what Premiere Pro is expecting.

[a_leven]

I am seeing this behavior in Premiere 24.5 (Beta) while using LucidLink to store both the Production and the Media.  Any insights into how we can fix this?  One editor is working on a laptop and their Project files appear to be closed on the Premiere end, but when I look on the finder level, they appear "stuck" on Lucid and are Zero Bytes.  If I try to open them I get the "Project Damaged" dialogue box.  If the editor re-enters the Production and does a full save, everything appears to go back to normal.  But there is no rhyme or reason why the files get stuck and Premiere cannot see them as locked.

From what I understand LucidLink and Premiere are fully compatable; Lucid is a recommended cloud storage solution for Premiere.

Thank you!

[mattchristensen]

@a_leven Please don't interepret this as me trying to move blame, but, what you describe sounds like an issue with LucidLink or your internet connection being unreliable.

Premiere Pro and LucidLink are fully compatible in the sense that, when working properly, LucidLink successfully abstracts away the cloud storage and to Premiere Pro it looks just like any other directly attached file system. Premiere Pro has no special code to detect or do anything different on LucidLink volumes; so because of that there's not much we (on the Premiere Pro side) can do here.

In the abstract, Premiere Pro tells the operating system "I would like to save this data (the project file) here (the folder)." It either works or doesn't, and if Premiere Pro displays an error saying it wasn't able to save it's really just showing you the error it got from the operating system in response to the request to save the data.