-
Keyflow Pro or Not…
-
[Craig Seeman] “I think an archival feature should be accessible to other software.”
How is it not? I hate repeating myself, but again: it is nothing more than a folder containing a 1:1 copy of whatever medium. There is zero special sauce involved i.e. anything keeping anyone from accessing it. They’re not .DMGs or the likes. Not even close!
[Craig Seeman] “So it’s my fault that I have four years of Camera Archives because Camera Archives seemed like a sensible way to back up Camera Master files ensuring their integrity?”
That’s of course rather jejune. Or should I ask if it’s Apple fault that you want to use a MAM that isn’t able to read completely open and non-proprietary data in return? In which case I guess, by that logic, it’s also their fault that e.g. PPro (still) can’t parse an FCPXML file? Yet another completely open format.
[Craig Seeman] “I’ll add that even FCPX can’t read any of my BMPCC camera archive masters predating about May 2014.”
But then you could always simply open the “folder” and import everything manually as any other media that you have copied from a camera to wherever, without any issues whatsoever. On the other hand I have no issues opening archives even from FCP 10.0 and there were no changes made to its “format”… which isn’t even one to begin with. Delete the .fcarch suffix and bingo… a folder like any other! I’d even venture to say, that that would be the first logical step to getting any MAM to read it, no? Unless of course it can’t read folders either.
[Craig Seeman] “Perhaps this is why MAMs don’t attempt this.”
Nope. It’s simply because they don’t recognize the suffix! Simply teach it that “.fcarch” means “folder”… BINGO.
[Craig Seeman] “Perhaps FPCX Camera Archives is a proprietary can of worms.”
That being where you’re sorely mistaken, as I’ve demonstrated above.
[Craig Seeman] “Is it my fault for Foolishly believe FCPX Camera Archives were an intended feature that would be useful?”
No. Just your fault that you don’t understand what a FCP X archive in fact IS and that you’re reading some evil magic into it that doesn’t exist. Then vehemently pointing fingers based on mere assumptions, speculation and conjecture.
Good thing I’m here to save you from your misconceptions! 😀
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
If there’s a MAM that can read Apple’s Camera Archives please do mention it.
FCPXML is widely supported even though there may be exceptions. On the other hand Camera Archives, as simple as the folder structure is, apparently isn’t.
[Robin S. Kurz] “But then you could always simply open the “folder” and import everything manually as any other media that you have copied from a camera to wherever, without any issues whatsoever”
Except the time it would take to do that for scores if not hundreds of Camera Archives. That FCPX can’t read its own Camera Archives from Blackmagic Camera preceding a certain date is a serous concern. If FCPX can have such issues then certainly that may be a problem MAMs don’t want to deal with.
[Robin S. Kurz] “Nope. It’s simply because they don’t recognize the suffix! Simply teach it that “.fcarch” means “folder”… BINGO.”
If it were that simple then why the issue with FCPX and the early BMPCC Camera Archives. The Archives contain a .plist file and apparently reading that isn’t so simple… short of ignoring it.
[Robin S. Kurz] “[Craig Seeman] “Perhaps FPCX Camera Archives is a proprietary can of worms.”
That being where you’re sorely mistaken, as I’ve demonstrated above.
“Non Proprietary then why can’t FCPX read its own archives under circumstances noted previously. The .plist in the archive is likely the issue and FCPX can have problems with it.
[Robin S. Kurz] “No. Just your fault that you don’t understand what a FCP X archive in fact IS “
What it IS is something that FCPX can have problems reading in some cases and MAMx may not read as well.
If it were so simple….
It isn’t unless you think MAM developers have motives -
Well, I’m not sure which part of “a camera archive is the exact same thing as if you were to simply drag the contents of a card to a random folder in the Finder, only with a suffix” you’re not getting your head around, but the conversation has clearly become nonsensically circular.
A folder is a folder is a folder. Suffix (and how it’s interpreted by any given app) or not. And the issue with the BMPCC was in fact an error that THE CAMERA was writing into the metadata file and how FCP was reading it. Fixed with a flash update for the camera… but never mind. It had absolutely nothing to do with a “changed format” of the archives… because there is no such thing. Unless of course you’re otherwise aware of different types of folders on your system that I’ve never heard of. But I’m sure it’s still somehow Apple’s fault. Easy target, I know.
So if for you saying “Apple needs to fix this” isn’t the exact same as saying “RED needs to fix that MAM xyz can’t ingest their material” (which is in fact the case with KFP btw), well, then I guess there’s little to talk about. Because I do and find it to be a rather ludicrous notion.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
And if in fact some archives are causing problems, then the only constructive thing to do is to report it to Apple and even send them one. The thing that I in fact did when the last problem with the PCC cropped up, and they worked with BMD to fix it.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Robin S. Kurz] “Well, I’m not sure which part of “a camera archive is the exact same thing as if you were to simply drag the contents of a card to a random folder in the Finder, only with a suffix” you’re not getting your head around, but the conversation has clearly become nonsensically circular. “
The Archive contains a .plist that is written by FCPX.
[Robin S. Kurz] “And the issue with the BMPCC was in fact an error that THE CAMERA was writing into the metadata file and how FCP was reading it. “
The fix was retroactive. There’s nothing in a BMPCC firmware update that would impact archives created the previous year. A change in approximately May 2015 suddenly made my Camera Archives going back to 2014 readable in FCPX.
You’re assume only the suffix of the folder is at issue. Given the issues FCPX had reading it’s own archives, one can’t assume the suffix will be the only problem. Of course the MAM can ignore the .plist file. FCPX certainly needs that info to read its own Archives properly so I wouldn’t make such assumption.
-
I reported it as well. I reported the extent of the fix too. It’s still not working for Archives created around June 2014 and earlier.
-
Is anybody using this?
What is the best practice to share out media, does the media stay on one location (Shared drive) and is just linked or does it copy the each Mac when being used?
I don’t see no value if you have to have it copied on each Mac.
-
[Thomas Frank] “I don’t see no value if you have to have it copied on each Mac.”
Simply watch the above demo (or any of the other various demos). All the answers are in there.
Spoiler: yes, you can copy, browse etc. between KFP clients. Be it local or even remote.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!
Reply to this Discussion! Login or Sign Up