Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere CS5 Altered my XDCAM folder and now i get errors when I try to use XDCAM transfer

  • Premiere CS5 Altered my XDCAM folder and now i get errors when I try to use XDCAM transfer

    Posted by Richard Cooper on July 6, 2011 at 9:27 pm

    Hi All,
    Testing the waters with CS5.0 and have found something strange.
    I imported some XDCAM EX footage (from a RAW XDCAM BPAV foler) into a PPro project via the import command so I could review a lot of footage without the long “log and transfer” workflow in FCP…. and all went well. All the footage came into PPro swimmingly and plays natively on the time line with no issues. Exactly what I was hoping for… I was really stoked.
    Flash forward one day and this morning I went to do a “log and transfer” of this footage in FCP and bam… will not work.(it would yesterday “pre PPro import”) So I opened XDCAM transfer(2.5.1) and same thing, error. This is what I get in the XDCAM Transfer:

    So I take a look into the raw BPAV file structure and I see that the actual mp4 files have been altered somehow and saved with a “date modified” of yesterday! So somehow PPRo has made the mp4 file unreadable by XDCAM Transfer and FCP Log and Transfer. But strangely I can preview the folders in XDCAM Clip Browser (2.05.00)
    Has anyone else run across this? Have I done something incorrectly within PPro with the import?

    System is an 8 core Mac pro running OSX (10.6.3), CS5.0 Production Premium and FCP 7.0.3

    Thanks

    Richard Cooper
    FrostLine Productions, LLC
    Anchorage, Alaska
    http://www.frostlineproductions.com

    Tim Kolb replied 14 years, 10 months ago 4 Members · 4 Replies
  • 4 Replies
  • Todd Kopriva

    July 6, 2011 at 9:54 pm

    Do you have the Write XMP ID To Files On Import preference checked in the Media preferences?

    If so, that will write an XMP ID metadata value into assets on import. It may be that this is causing the assets to not behave properly in FCP.

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    Technical Support for professional video software
    After Effects Help & Support
    Premiere Pro Help & Support
    ———————————————————————————————————

  • Tim Kolb

    July 7, 2011 at 1:23 am

    My guess would be that there may be some files that PPro doesn’t use that didn’t get a new modification date, and now they disagree?

    Obviously if XDcamEX Clipbrowser can read the files, they aren’t “corrupted” so I wonder if you transfer them to another drive if that might bring all the mod dates into zen…?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Jeff Pulera

    July 7, 2011 at 1:42 pm

    Instead of using “Import”, you should be using the “Media Browser” in Premiere for importing that type of footage. I don’t know what’s going on with the current issue, but try Media Browser next time.

    Jeff Pulera
    Safe Harbor Computers

  • Tim Kolb

    July 7, 2011 at 1:59 pm

    If the write-back of the metadata is causing the issue, are you saying the media browser doesn’t write updated XMP data?

    While the media browser is a nice way to bring in media, I’m not sure it would change this situation if the write XMP preference is selected…

    It sounds like log and transfer may use the modified dates as a verification for data set association.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

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