-
Proxy files missing after relinking
-
[Jeremy Garchow] “It’s simply not true,”
It is actually. “Most likely” being the key. Not always (no idea why), but why risk it.
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Robin S. Kurz] “It is actually. “Most likely” being the key. Not always (no idea why), but why risk it.”
I guess I live on the edge and dupe Libraries in the Finder all the time, haven’t seen any problems.
Mileage may vary.
-
Library files are largely just project files. You should be able to duplicate them without any issues. Footage and any managed files are a different story.
-
[Jiri Fiala] “Library files are largely just project files.”
Exactly. And those projects etc. are assigned unique IDs by FCP for the underlying database. Basic sql protocol if you will. Within the old >10.1 system it was definitely not possible, with the new one things seem to have gotten more lenient.
The general point merely being, why risk a potential ID conflict when the functionality is there within FCP to avoid it (and is easier/faster to boot). Just a friendly heads-up.
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Have you honestly seen this conflict? I have never seen or heard of it since the advent of Libraires. Events and Projects, yes, but not Libraries.
Google shows zero instances of this error for libraries.
I’d like to know if this is actually a problem as we dupe libraries constantly to share back and forth. Never had one conflict, and have even had two Libraires of the same name open in FCPX withiut one issue.
We have even duped open Libraires, renamed the dupe, and opened that library All with X open (this is all part of stress testing in a shared environment) and have literally had zero issues.
So, when exactly do you see this issue pop up with Libraries?
-
[Jeremy Garchow] “Have you honestly seen this conflict? “
Of course. Several times. Just not recently, since I know about it and don’t do it anymore, otherwise I’d post a screenshot for you.
But feel free to also read about it here or here. The first two of many I get when googling.
[Jeremy Garchow] “I’d like to know if this is actually a problem as we dupe libraries constantly to share back and forth.”
Like I said, it would appear to have become much less of an issue with 10.1 and above, maybe even completely resolved. I don’t know, but I don’t care to find out the hard way. 😀 Whereby I’m not talking about copying to another disk for the sake of passing it on or using elsewhere. And you’re obviously still free to do whatever works best for you. I just prefer to avoid potential problems and use the FCP own tools.
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Robin S. Kurz] “But feel free to also read about it here or here. The first two of many I get when googling.”
This is wholly different than duping libraries. These guys are talking about Events and Projects before Libraries, and in that case, yes Dupe IDs caused major conflicts. This is not the case with Libraries.
The first post is from Decmeber 12 2013, and the second post is from 2012. 10.1 was released on 19 December, 2013.
If you see any conflicts with Finder duping a Library, I would love to know about it, but as of right now, I think we are trouble shooting different problems for Jiri.
Jeremy
-
[Jeremy Garchow] “10.1 was released on 19 December, 2013.”
Hence what I wrote, yes.
No idea what I can say other than what I already have: do whatever is best for you, I’ll do it differently. I don’t even know why we’re still debating it. There’s nothing false about what I wrote.
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Robin S. Kurz] “There’s nothing false about what I wrote.”
I am actually looking to find conflicts. I have never seen a conflict with Libraries. You say there are, and pointed to a few examples that don’t apply to the 10.1 update. Not that the information is false, but the information doesn’t pertain to anything in this post, unless Jiri is using 10.0.9.
I’m trying to find experience in conflicts with 10.1 as it effects our work. Sometimes, it’s not feasible to use FCPX to make a new library with multiple users, and it is much easier to simply dupe in the Finder. IF X allowed mounting of read only Libraries, then yes, we could use FCPX for everything, but right now, we can’t.
-
To be sure, I asked Apple. And yes, there “should be no more problems with the unique ID’s as with pre-10.1 versions.” So you’re right, that part wouldn’t play into this.
But again, I personally still wouldn’t do the managing via the Finder, only through FCP itself to avoid exactly these kinds of problems. That was ultimately my only and actual point. To each his own.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!
Reply to this Discussion! Login or Sign Up