Question for Metadata Nerds!

[Noah Kadner]

Can you give a little more context?

Noah

FCPWORKS – FCPX Workflow
Call Box Training

[Charlie Austin]

[Noah Kadner] “Can you give a little more context?

Noah
“

Sure… Over the last couple weeks, we’ve had 2 or 3 master clips (shared on a NAS/OS-X server (10.7.x… don’t ask)/GB Enet) go offline. Files are there, but corrupted. It’s affected X (modified file can’t relink) as well as FCP 7, Pr and QT Player etc. Files are just hosed. Something is modifying the files (created date changes). No apparent rhyme or reason. We have backups, so we just replace with an original copy, but I’d like to know why it’s all of a sudden appearing. We updated most of our systems to 10.10, and a couple more folks have been playing with PrCC, but I turned off all the XMP crap on their systems. When I compared a good file with a corrupt file, the stuff above had been added to the corrupt file.

It reminds me of when you’d try to modify source TC from FCP 7 on an externally shared file, and the file just goes poof. Disconcerting. I’m 99% sure X doesn’t try to write anything/modify source files, so I don’t know what else to look at…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Dennis Radeke]

If you’re disabling XMP in Premiere Pro, make sure you’re unchecking all three of these:

Dang the retina for making such large graphics! 😉

[Charlie Austin]

[Dennis Radeke] “Dang the retina for making such large graphics! ;-)”

lol.. first world problems 🙂 I think I did, but I’ll double-check. I really don’t think it’s the actual metadata that’s the issue, the XMP issue with Pr and X was sorted out a while ago AFAIK. Also it’s not just X that’s affected. I’m inclined to think it’s something else. Some OS/NLE?Random App interaction.

Though I personally think source clips, particularly when shared among different apps, should never be modified. My experience since forever has been that modifying files that aren’t local has always seemed to make bad things happen.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Bret Williams]

[Charlie Austin] “the XMP issue with Pr and X was sorted out a while ago AFAIK”

Yeah, I think Adobe has it turned off by default. But 10.1.x might be more lenient now as well.

[John Heagy]

I’m guessing your working in 23.976.

24000/1001 is the fractional way of defining 23.976.

24000/1001=23.976

Probably Adobe’s way of defining that frame rate.

John

[Charlie Austin]

[John Heagy] “I’m guessing your working in 23.976.”

Yep

[John Heagy] “24000/1001 is the fractional way of defining 23.976.

24000/1001=23.976

Probably Adobe’s way of defining that frame rate.”

If their app modified the file, that makes sense. But nobody is taking responsibility. 😉 It probably wouldn’t be an issue on local files, but modifying file metadata on a server from a client seems to make bad things happen.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Dennis Radeke]

23.98 = 23.976.

23.976 is the actual frame rate that other NLEs display as 23.98

Aspect ratio is another thing. Wide screen DV is often considered 1.2:1 but in fact it is 1.2121:1.

HTH,
Dennis – Adobe guy