Forum Replies Created

Page 221 of 258
  • Charlie Austin

    April 2, 2013 at 4:14 am in reply to: X to 7 and premiere weirdness/warning

    [Bret Williams] “And Digital Rebellion did the trick. Batch removed (5 clips at a time with the trial version) the XMP data from the afflicted files. Opened up FCP X and it’s all happy again. Thank you Jeremy and Charlie!”

    Nice!… sadly didn’t work for me… maybe another issue but I’ve got no clue what it could be. I know it was opened in AE with the Write XMP function turned on, so I really don’t have a clue. I’ll try the QT Edit again tomorrow. Anyway, glad you’re back up!

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

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

  • Charlie Austin

    April 2, 2013 at 4:11 am in reply to: X to 7 and premiere weirdness/warning

    [Jeremy Garchow] “Date should have nothing to do with it. Fcpx is picky about length, audio channel configuration, and type.

    What type of media is this?”

    Agreed, which is why this is so weird. As far as I can tell, and I looked pretty hard, the only discernable difference between the online and offline files, is the creation date. Invisible is whatever the XMP data was. This has happened to me twice. Once with a DV source clip, once with a Prores file. Both about 2 hours in length. In the first case, I had another copy of the original on my local drive. When I replaced the “modified” version with that one on the server, it relinked just fine. This recent time, I unfortunately had tossed the copy of the original that I had. Very odd. I’ve pinged Apple about it…

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

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

  • [Chris Harlan] “Choice–what a waste of time.”

    Winner! lol

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

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

  • [Chris Harlan] “hammertime! LOL. SUCH A DEAL.”

    My favorite paragraph:

    Because UAD Simplicity plug-ins feature no knobs, controls, buttons, or any other plausible way to adjust their sound, they’ve been designed with onboard MPUPâ„¢ (Most Popular User Preset) Technology. This technology removes hours of guesswork, giving users the single sound that best represents the complex, almost infinite possibilities of 50-year old classic analog recording equipment.

    It’s the perfect compliment to FCP X! 😉

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

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

  • [David Lawrence] “Nice! But I prefer something a bit more transparent sounding 😉

    https://www.fullscaleav.com/transparenator

    Cool! I plan to order both right away!

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

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

  • Charlie Austin

    April 2, 2013 at 1:56 am in reply to: X to 7 and premiere weirdness/warning

    [Bret Williams] “I have tried everything too. Reimport puts it right next to the other. My files are all local on the Pegasus. Some originals, some optimized, some AE renders that are linked, etc.

    Even more frustrating is the fact that the symlink/alias/whatever in the Finder, reveals the original just fine, so there really is something odd in the XMP data that X doesn’t like…

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

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

  • Charlie Austin

    April 2, 2013 at 1:29 am in reply to: X to 7 and premiere weirdness/warning

    [Jeremy Garchow] “[Charlie Austin] ” Also, the error message states that there’s not enough media or something, which is just plain wrong.”

    Yeah, that is wrong. I wonder what would be different (besides the obvious) from SAN and NAS XMP modified files.

    No clue. I guess the current “solution” is be certain that nobody opens a master file in any Adobe app with out first turning XMP write off…

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

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

  • Charlie Austin

    April 2, 2013 at 12:28 am in reply to: Failed share

    [Jeremy Garchow] “Or is the drive full or near full?”

    Nope… plenty of free space.

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

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

  • Charlie Austin

    April 2, 2013 at 12:27 am in reply to: X to 7 and premiere weirdness/warning

    [Jeremy Garchow] “[Charlie Austin] “The problem I run into, in a shared media environment, is that everyone didn’t know the havoc this could cause. ”

    Let’s back up a second.

    This is footage on a SAN?

    I assume your are using aliased links or is this media in the Event?

    XMP does not seem to trip up my files on the SAN here.

    Have you tried simply dragging a file back in to see if it reconnects? It should have the little “alias” arrow not a green plus sign.”

    Not a SAN, on NAS… central RAID served over gigabit ethernet. And yes, linked files, not in the event, which is local. tried dragging it in again, no change, the file I dragged in shows up right next to the offline “file” in the event browser. Nothing relinks…

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

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

  • Charlie Austin

    April 2, 2013 at 12:06 am in reply to: X to 7 and premiere weirdness/warning

    [Jeremy Garchow] “[Charlie Austin] “Just tried it on a file… didn’t seem to work. Fortunately it’s from a project that’s done, but if this had happened in mid job, I would be completely f*cked.”

    XMP file modification has been part of Adobe’s workflow for a long time so I usually shut off the XMP options (this has to be done in Ae as well).

    In FCP7, XMP injection simply knocks render files loose, which can be a pain, but not devastating.

    Reconnection in FCPX needs some retooling, absolutely.

    FWIW, I have mistakenly left the option on, and the files flash that they are disconnected in FCPX, but then they relink. I don’t seem to have an issue of XMP knocking the files completely offline.

    Stripping the XMP metadata works for me in Qt Edit.

    The problem I run into, in a shared media environment, is that everyone didn’t know the havoc this could cause. They do now… >:-| This has happened a couple of times, both times with projects that were done, but it’s a bit… disconcerting. In both cases the file was exactly the same, save for some sort of metadata being written to it, which was signaled by the files’ modification date changing. Same size, same format, same audio configuration… same file. No problem at all in FCP 7, but X just plain refuses to relink. Also, the error message states that there’s not enough media or something, which is just plain wrong. Again… disconcerting…

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

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

Page 221 of 258

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy