Skip navigation
BrightlandCo
BrightlandCo
Currently Being Moderated

Slow playback of Canon 5D Mark III file

Mar 6, 2012 9:35 PM

I tried this new Canon 5D Mark III native .MOV in PPro CS5.5: https://vimeo.com/38055013

Available for download on Vimeo: https://vimeo.com/38055013/download?t=1331098396&v=87557753&s=60764fbb 7ca30180cd7cfb02022adc3c

 

In CS5.5, it plays OK for a few seconds, then slows way down. Sequence created from the clip format (matches). GTX 285, 12 Core 2.93 (MacPro running Win7x64), same issue GPU or CPU.

Plays fine in PPro CS5, Vegas 11, Windows Media Player, etc.

 

Can anyone verify this issue in PPro CS5.5?

2344 Views   10 Replies   Latest reply: BrightlandCo, Mar 21, 2012 9:02 AM
 
Replies
  • BrightlandCo
    Currently Being Moderated
    1. BrightlandCo,
    Mar 7, 2012 1:32 PM   in reply to BrightlandCo
    Report

    This is confirmed as a bug in CS5.5. Changing the filename from .mov to .mpg is a work-around, tricking the loader to use a native code path vs. Quicktime. This bug does not exist in CS5 (file plays in real-time). Adobe: wouldn't it make more sense for the native loader to try to load the file first, and if it cannot, set metadata to load it through Quicktime for subsequent loads? It appears the code currently is hard-coded with a template that if matched uses the native loader, and if not, uses Quicktime (otherwise there appears to be some other kind of bug).

     
    |
    Mark as:
  • Todd_Kopriva
    Currently Being Moderated
    2. Todd_Kopriva,
    Mar 10, 2012 2:34 AM   in reply to BrightlandCo
    Report

    Have you installed the latest updates? They include some improvements in decoding of such files.

     
    |
    Mark as:
  • BrightlandCo
    Currently Being Moderated
    3. BrightlandCo,
    Mar 10, 2012 9:34 AM   in reply to Todd_Kopriva
    Report

    Yes, I have been running 5.5.2 since it was released. CS5 (5.0.3) does not have the bug.

     
    |
    Mark as:
  • Dave Merchant
    Currently Being Moderated
    4. Dave Merchant,
    Mar 10, 2012 12:43 PM   in reply to BrightlandCo
    Report

    For info, the Vimeo content in question has been removed as it was infringing the Canon non-disclosure agreement (the footage was from a pre-release camera).

     
    |
    Mark as:
  • BrightlandCo
    Currently Being Moderated
    5. BrightlandCo,
    Mar 10, 2012 3:19 PM   in reply to Dave Merchant
    Report

    Another direct-from-camera MOV available here (search page for "untouched clip"): http://www.paulward.net/?p=1075

    One would think Adobe is working with Canon to ensure support when the 5D Mark III is released on March 22?

     
    |
    Mark as:
  • EricSanders_
    Currently Being Moderated
    6. EricSanders_,
    Mar 20, 2012 1:39 PM   in reply to BrightlandCo
    Report

    I would suggest going to your MediaCacheFiles directory (typcially this is C:\Users\<your_user_name>\AppData\Roaming\Adobe\Common\Media Cache Files), and delete the .qtindex files when Premiere is not running, relaunch, and try importing the files again.

     
    |
    Mark as:
  • BrightlandCo
    Currently Being Moderated
    7. BrightlandCo,
    Mar 20, 2012 3:45 PM   in reply to EricSanders_
    Report

    Thanks for the tip Eric. Tried it, didn't work. The 5D3 I-frame only works ok, however. Until Adobe fixes this bug, the workaround is to rename MOVs to MPG, or use CS5. 5D3 is available today in the US; suspect fix requests will start growing louder. Since the issue was first reported about 10 months ago(?), is this something that won't get fixed until CS6?

     
    |
    Mark as:
  • Jim Simon
    Currently Being Moderated
    8. Jim Simon,
    Mar 20, 2012 9:21 PM   in reply to BrightlandCo
    Report

    At this point, that's probably a safe bet.

     
    |
    Mark as:
  • Bob Dix Photographer
    Currently Being Moderated
    9. Bob Dix Photographer,
    Mar 21, 2012 2:31 AM   in reply to BrightlandCo
    Report

    Well, as soon as I saw the codec change I knew there would be a problem, CS5.5.2 could fix it , but , I canot fault CS5.5.2 in Premiere Pro for our updated Firmware Canon 5 D Mark II, editing the old Mark II is a breeze , the HD Video PAL at 1920 x 1080p is just stunning.

     

    All the best 

     
    |
    Mark as:
  • BrightlandCo
    Currently Being Moderated
    10. BrightlandCo,
    Mar 21, 2012 9:02 AM   in reply to Bob Dix Photographer
    Report

    Bob Dix Photographer wrote:

     

    Well, as soon as I saw the codec change I knew there would be a problem, CS5.5.2 could fix it , but , I canot fault CS5.5.2 in Premiere Pro for our updated Firmware Canon 5 D Mark II, editing the old Mark II is a breeze , the HD Video PAL at 1920 x 1080p is just stunning.

     

    All the best 

     

    Interestingly, CS5.x works; something in CS5.5.x broke it.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points