-
Incompatible file
Anyone noticed that sometimes files that are moved and then relinked to won’t actually relink? We keep getting the ‘The new file is not long enough to cover clip…” in project “….”.
Nothing has changed about these source files other than their location. Bug?
John Davidson | President / Creative Director | Magic Feather Inc.
-
11 Replies
-
[John Davidson] “Nothing has changed about these source files other than their location. Bug?”
Are you editing with symbolic links? Why does the location change?
-
We moved everything over from local machines to NAS. We tried turning off the projects blocking relinking in Event Manager X and then bringing the projects back in with EMX, but the relink still doesn’t show up correctly in the project. It’s not the end of the world, but it’s kind of weird nontheless. We’re just reediting the shots back in.
John Davidson | President / Creative Director | Magic Feather Inc.
-
I can sorta see that.
I don’t do NAS stuff, but “finder-fu” is an area where X is extremely persnickity.
It really wants assets to reside right where it expects them – and for the pathways and locations to be fixed and dependable. I imagine this is more delicate in a system where there more complex pathways between the software and asset locations and with NAS, you’d certainly have that.
Keep us up on what ‘s working and not, John. You’re on the frontier and I suspect the new territory is pretty interesting for everyone to read about.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
It’s a short term pain for now and since we’re moving to a single location for shared media it likely won’t happen again. Just something I was curious if others had encountered.
John Davidson | President / Creative Director | Magic Feather Inc.
-
So, are you using sparse images for this?
-
We are – and referenced media. It’s actually working pretty great. We mount them straight off the NAS and then FCPX ‘sees’ them. So far, so good.
John Davidson | President / Creative Director | Magic Feather Inc.
-
So, when does the reconnect come in to play?
Why not use FCPX ‘Move’ function to the sparse image?
-
We don’t keep the media inside the event. We have a media folder on the NAS that all DMG’s refer to and are separate from any specific event. Moving the media from within the event doesn’t work in the way we’re setting it up. Source footage is broken down inside based on media/network/show.
It should relink correctly, it just doens’t want to for some clips – especially if the media is inside a compound clip for some reason.
John Davidson | President / Creative Director | Magic Feather Inc.
-
Never mind, you’re reconnecting the symbolic links.
Duh.
-
I wish it did work that way. I see a world where DMG’s are gonna get filled up pretty quickly, even if setting sparse bundles with up to 100 gigs of room and referenced media. We have a 250gig event (using referenced media) of just render files for about 30 ten second spots. We were kind of surprised it got so bloated.
I think we are going to need a preference to select specific locations for render files one of these days. Also, importing audio from the media browser still copies to events, even if ‘copy to’ is unselected in preferences.
John Davidson | President / Creative Director | Magic Feather Inc.
Reply to this Discussion! Login or Sign Up