[Craig Rogers]

I found this info regarding quicktime gamma issues. This “fix” did make my videos play back properly (gammawise), but this can’t be the real issue, as 99.9% of quicktime users aren’t going to know about this “fix”.

How can the single most popular codec (h264) not work properly with the single most popular player (quicktime)? I’m baffled.

[Craig Rogers]

I worded that badly. I took my uncompressed render and ran THAT through AME. It looked like dookie…and in either scenerio the color of my h264 renders are washed out. ???

I’ve noticed a considerable difference in the look of a video depending on the player playing it as well. They look more washed out played back with Quicktime. VLC player not so much.

[Craig Rogers]

Hmmm…having same error message. I’m using CS5.5 though.

I suspected a pre-render might fix the problem, so I took my H.264 quicktime and pre-rendered it to an uncompressed quicktime. I replaced my original H.264 footage in my project with this new uncompressed file and tried rendering again. 31 frames in it’s frozen solid.

Any ideas?

[Craig Rogers]

I’m running CS5.5 and just started having the same problem. I’ve been working on a project all week without issue. I’ve rendered several short sections of my project without a hitch. I just finished up this afternoon and am trying to render the entire piece and I keep getting this error.

I’ve re-downloaded the source quicktime file from the client in case the copy I was using got corrupt. I’ve tried moving my source footage to a different drive. I’ve tried rendering to a different drive. Seems no matter what I do, it simply won’t render. It gets 25-28 frames into the render and then crashes.

The source footage I’m using now is an H.264 quicktime.

Just as the previous person said, the files themselves playback a-ok, and I’ve been working with this footage for a week without issue.

Suggestions?