proxy linking issues in shared production

[J_Boy]

I'm working in a shared production. The production folder is stored on a Lucid Link files space. My AE and I have mirrores copies of all media on seperate drives at our respective remote offices. We have proxies for all footage also stored on the mirrored drives. After setting up the Production, anytime either of us open a project after the other has worked in it, we have to relink or re-attach the proxy to the file paths on our respective drives.

Premiere does not have the same issue with the camera original media, just the proxies. Is this an annomoly? Can it be avoided? Our respective drives are identical aside from the volume names, one of which has an A in the name, while the other has a B.

[R Neil Haugen]

Fascinating. I've not run into this, but we work our Productions with the entire Productions and media assets on our LucidLink servers.

Will be interesting to see an explanation.

[PaulMurphy]

If you’re having trouble with proxy linking in shared Productions, this great article on Productions workflows by @Jarle Leirpoll might be just what you need.

It covers a lot of useful tips, including a section on the "Constant need for relinking." One of the key takeaways is:

"To avoid trouble, it’s a good idea to give the shared storage the same drive letter on all Windows systems."

[J_Boy · Accepted solution]

Thanks @PaulMurphy. That is a super helpful article. I'm not sure that suggestion applies exactly to my situation since we are all on mac systems over here. But the same concept DOES seem to apply. We took off the 'A' and 'B' from the respective drive names, so each volume is now identical in name and path. After an initial test that seems to have solved the proxy relinking issue. Still worth noting that this is not neccessary for source clips, only the proxies. Premiere has no problem remembering different volumes and even different folder paths for different users when it comes to source clips. It appears the same is not true for proxies - unless our experience is an anomoly.

[atxspencer]

I have all my footage on a lucidlink workspace, and every time I open it I have to "attach proxies". Only proxies are on lucidlink, we only need proxies to edit for now, why is this happening? 

[PaulMurphy]

Does the project that's prompting you to attach proxies also have the media in it, or are you just adding the media to a timeline in this project?

[atxspencer]

The project has media in it. the project was made initially with raw media that was then transcoded. We moved the project and all transcoded proxies to lucid link, so everything should be pointing to the same folders. But it keeps asking to link every time me or another editing accesses the lucidlink project that is pulling from proxies to view footage.

[R Neil Haugen]

There are some intriguing things that you wouldn't think would affect linking in folder structures that have been posted by staffers over the years, mostly in regard to stand-alone projects.

I'm wondering if the structure of the production was changed during the transfer to a LucidLink filespace ... ?

[atxspencer]

It's possible it's still hung up on the transcodes original destination. We have so much footage they have been organized into managable transcode folders. Not sure how to reset that metadata.