Gamma Shift / Flash Frame when Transcoding to H264

Hi Everyone,
I'm having an issue with gamma shifting when I transcode my ProRes 422 HQ master clips to H.264 for web viewing.  The workflow is this:
Final Cut Pro 7.0.3 > Cut with ProRes 422 HQ 1080p 23.98 masters > Export to ProRes 422 HQ 1080p 23.98 self-contained QT
Compressor 3.5.3 > Bring in ProRes 422 HQ master clip > Apply H.264 custom setting > Transcode
Unfortunately the result is that what appeared in the ProRes master as a good looking clip, becomes a terrible looking clip with all sorts of gamma shifting.  The strangest thing is that you can see the gamma shifting problem in the PREVIEW window in Compressor on BOTH sides of the comparison divider.  So if you playback in Compressor you see it in the ProRes original!  But in QuickTime player the ProRes is fine.  In FCP it's fine.  Even as an MPEG-2 for Blu-Ray (made using Adobe Media Encoder) it's completely fine.
So there is something going on in Compressor, it seems.  I just can't quite figure this one out.  Has anyone experienced this?  I personally have found Compressor 3.5.3 to be very buggy.  I get a green band on the outside of the frame when I make MPEG-2 for DVD in this version of Compressor.  I never had that problem in the past with 3.0.5. 
If anyone has any ideas that would be great.  In the mean time, I'm uploading a comparison so that folks can actually see what I'm talking about.  I'll post the download link when it's up.
Thanks in advance.
-JD

I have compressor 3.5.3 without any of this sort of problem.    If you are doing any scaling or retiming, make sure that frame controls are enabled and all relevant options are set to best.
First, do your clips match your sequence settings (in particular frame rate and progressive/interlaced)? 
Do you want to send me a short clip exported from fcp with current settings and I'll see if I can reproduce the problem?
My email is [email protected]

Similar Messages

  • Flash frame when printing to tape?

    Ok, this has never happened to me before, I have an hour long show. The whole project is edited and rendered out in one quicktime movie.
    I'm using the final QT movie to edit to tape. At the end of a dissolve I am getting a Flash frame, the funny thing is its only happening on the tape. I have gone through the sequence frame-by-frame and there is no indication of an added frame or
    bad edit anywhere. Does anyone know why I would get a Flash frame only when I print to Tape?

    are you monitoring on a NTSC monitor or your computer. I've seen this when the flashframe is on a field the computer monitor isn't showing, but the ntsc mon will show it. The other thing is when your deck is brought out of record by hitting stop without rolling enough black prior to stopping this can happen but it sounds like you are seeing this in the sequence somewhere not at the end

  • Compressor3.53 genrating dulipcate frames when exporting from H264 to Apple Prores

    whn i was trying convert Animation playblast(H264 Codec) in compressor to appleprores422...genrating dulipcate frames..at 13th frame ....Orginally the animator will take playblast in NON-codec .OR Wraw codec formate ....later it will converts into H264 using Quicktime ..while the playblast playing like vedioShutters..wat i converted in Compressor
    i was using same preset from long bak...........this promble occuring for few days
    iam using compressor 3.5.3......QT.time 7.0 .. mac

    Not surprised the 10bit uncompressed won't play back on an iMac. Is 10-bit HD....? Yes, in fact in some opinions, 10 bit IS (the appropriate bit-depth for) HD.
    The other thing is that you must select your render codec and directory BEFORE you load the Render Queue. Otherwise everything goes out 'default',and to top it off, the XML export will reflect the changes you made AFTER -- which will then be, as they say, "wrong".... so yes, it matters.
    Internal Hard Drive is nowhere near what you'll need. Doing a compression from it shouldn't be a problem, though. Anything that doesn't need to run in real time should be okay. Heck, you could probably do 4K -- but not much of it, or very quickly.
    Seems like FCP really wants to work in bit depths in multiples of 8. Funny thing, that.
    I'm also mystified about the 'render in original codec' wrinkle in your fabric... I've never had an issue with DVCProHD like that. And the ProRes422HQ thing... I'm looking at a 5 minute project right now (just Media Managing the corrected version back to hard drive as I write this) that would duplicate your initial workflow and it looks, well, lovely. You may be simply overwhelming your hardware.
    jPo
    Message was edited by: JP Owens

  • Getting choppy footage when rendering plus "flash" frames

    Hi all,
    I've been using Final Cut Pro 7 for about two years for casual video editing. I use H.264 files with a framerate of 24fps and I always set sequences to fit the native format of the video files I use in them. Today, I noticed an odd "bug" when rendering video files. It's a bit hard to explain, but I'll try my best.
    Let's say I take a 5-second clip from an hour-long video file and place it in the timeline. I cut off a bit of the end and add some keyframes to adjust the opacity. I then render this small piece. However, upon playback, the footage appears to "stagger", and even the playhead appears to pause for a moment before continuing on. This is confusing to me, because the footage is rendered properly, so shouldn't it play normally, like the unedited segment of the clip?
    I've also had a problem with getting "flashes" of a frame that isn't meant to be in said clip. When I scroll over the clip using the playhead, this "flashing" frame is nowhere to be found.
    I'm using Mountain Lion (10.8.5).
    Can anyone lend a hand with this? Thanks in advance.

    David and Ian are absolutely correct in their posts about the problems with trying to work with h264 quicktimes in fcp.  But the issues you are having may also have something to do with your frame rate. 
    Do you mean 24 fps or 24P?  24p is actually 23.976 frames per second.  Most US video is 29.97 fps and 23.976 fps is a relatively easy conversion to 29.97 fps using "pulldown."  Early DSLR's sometimes shot exactly 24 or 30 frames per second.  New DSLR's now shoot 23.976 and 29.97.  Unfortunately, spec sheets don't always describe the frame rate accurately.   24 fps is not a standard video frame rate and there can be problems putting a 24 fps clip in a 24p sequence.
    Here's a user tip describing these frame rate issues in greater detail
    https://discussions.apple.com/docs/DOC-4731
    If any of this isn't clear, post back.  It's complicated.

  • Gamma shift when exporting MP4

    I know this is a known issue, but I have yet to see a viable solution.
    Working off PC and exporting via Adobe encoder.
    When exporting H.264 in an mp4 container, there are significant gamma shift issues that void several hours/days of color correction work. It really washes out the color.  I have viewed these exported mp4's in quicktime and VLC on multiple computers and the issue is still present.
    Quicktime MOV exports seem to be fine, it is only when exporting H.264 mp4.
    Some have mentioned changing the NVIDIA settings which seems to be an internal fix for that monitor, but I am exporting video's that will be going on the web for distribution.  I really need consistency across all media platforms.
    This is a very big deal that needs attention and hopefully a fix is in the works if it is not already out there.
    Thanks,
    Austin

    Gamma shift once clip starts
    Pure black before clip starts
    Thanks for the reply!
    The above demonstration is the same in VLC as well.
    We exported black for a few seconds and then faded into a jpg image using the generic fade in effect.
    All that was used in this clip was a jpg image at the end that we faded into. For this test we used no video.
    Running Premiere Pro 8.1 Caravan on a Dell Precision T5610 Intel(R) Xeon(R) CPU E5-2620 v2 @2.10 GHz 32gb RAM
    Working off a Synology diskstation ds1513 20TB 4GB RAM
    Only third party installed effects are film impact transitions, but they were not used in this clip.
    Let me know if any more info is needed.
    Thanks

  • Gamma Shift with Encore Transcoded Material

    Hello,
    I use Edius as my NLE and have always noticed that if I let Encore CS4/CS5encode my assets the gamma of the resulting DVD or BD is higher resulting in a grey, milky look to the footage.
    1)  Does anybody else see this?
    2)  What is causing this?  Color space issue?
    3)  Can it be avoided?
    This issue has baically stopped me from ever using Encore beyond a compiler of assets.  It has been there since CS 4 for me.
    Any ideas would help and might save my lowered opinion of this software.
    Thanks

    Hello,
    Thank you for the tip about using AME.  I thought Encore CS 5 used the media encoder in the background automatically.
    The gamma shift is gone and I am happy to be using Encore in a more prominent role going forward.
    One thing, it seems a bit odd regarding transcode settings.  I can not find a way to enter AME through Encore to make presets.
    Are the presets in Encore the same as AME?
    Any help about this proceedure would be appreciated!

  • Show a Flash animation frame when opening a Powerpoint presentation

    Hi all,
    I have a Powerpoint presentation that embeds a Flash
    animation (swf file). I use Powerpoint 2003 and a Flash 9
    animation.
    The problem is that when the presentation is opened, no image
    (in fact a frame of the Flash animation) appears on the slide that
    contains the Flash object. Instead, a blank rectangle is displayed.
    To make it appear, I must start the presentation in slide
    show mode (here the animation is playing) and then return to
    'Normal' view. The last animation image is then shown on the slide.
    From now, if I save the presentation, close it and then reopen it,
    no image is shown.
    I have tried with different Flash animation versions and
    noticed that an image is displayed for Flash animation when
    compiled in Flash 7. In a Flash 8 animation, no image appears too.
    It seems that a change since Flash version 8 avoids an image to be
    displayed when opening the Powerpoint presentation.
    Has anyone already met this ? Are there security or other
    changes that will prevent a frame to be displayed when opening the
    presentation ? Any ideas or Internet links will be appreciated.
    Thanks

    Hi Dave and thanks for the answer.
    My embedded movie is playing well when we start the slideshow
    mode for the presentation, because it uses the installed activeX
    component (version 9 installed) to render it.
    My problem is that no image (ie the last movie frame
    displayed before exiting the slide show) is displayed the next time
    the presentation opens, even if the file is saved.
    Did you mean that, because the activeX version is newer than
    the PowerPoint 2003 release date, the PowerPoint application is not
    able to get the image (frame) the next time the presentation opens
    (that is, the image to display is embedded into the activeX at a
    specific location, which has changed between Flash player version 7
    and 8) ?
    PS: 1) I have opened the Flash 8 presentation in PowerPoint
    2007 and an image is shown on the slide, which might confirm that
    PowerPoint 2003 is too old to find the frame to be displayed.
    2) I searched into the in-line/off-line documentation and I
    found no paragraph speaking of the Flash version limitation.
    Let me know if I am right.
    Thanks again for the time taken to answer me.
    Rico

  • Gamma shift

    hello -
    I'm wondering the best way to deal with the gamma shift problem in Premiere (Mac). Clips appear differently delending on where you're viewing them, for example in the Program viewer colours are more saturated then when you open up the title window with the clip preview underneath. Likewise if I match frame and open a clip in the Source viewer, the colours are more muted than the identical clip in the Program window. If I export h264 and upload to YouTube, I get the more muted colours but if I upload the same file to vimeo, I get the more saturated version. I know this is a QuickTime problem but I'm wondering why Premiere shows identical footage in different ways and also wondering if anyone has solved this problem? Any advice will be appreciated!
    thanks
    David

    It's unfortunate, but different players appear to interpret the same footage differently.  Even if you knew how the viewer's computer monitor was calibrated, you still couldn't predict how the footage will look, if the viewer has a choice of players.
    Other than correcting material on a properly calibrated HDTV, and ensuring that everyone who watches it also has an accurately calibrated HDTV, there's no way to get uniformity or predictability.  Don't despair, however:  makers of $100 million movies have exactly the same problem.  How many consumers of Hollywood DVDs and blurays have accurately calibrated TVs?

  • Momentary gamma shifts in PS-CS6 composed image h.264 video

    Before I finalize a bug report, wonder what others are seeing?
    Having discovered the problem in a more complex scenario, I've narrowed down to a simple set of jpg images placed sequentially in a video group, and exported as an h.264 video from Photoshop PS6. All is on Windows 7 Professional SP1, all software involved completely up-to-date.
    I first noticed the gamma shift using the 'High Quality' preset. It occurs with variations on Vimeo 29.97 and Youtube 29.97 presets. The gamma problem does not occur on HD 720p or 1080p 29.97 presets.
    When I view the resulting video through Quicktime, I see a gamma shift for a moment on the first image, making it look washed out. After another moment, the gamma goes back to normal. On other players such as Windows Media or VLC, no such shift is visible.
    Interestingly, the shift comes at 1 second when exporting to the Vimeo 29.97 preset, or 'High Quality', while at 3 seconds on Youtube 29.97. Similarly, the shift back occurs at 2 seconds, or 6 seconds for Youtube.
    What the gamma shift looks like sounds like the now age-old Apple Quicktime fault on h.264. -- except it occurs only for one or a few seconds, then reverts to proper gamma, instead of continuing..
    With the simple setup of single image (jpg) sequence, it occurs only on the first image. With a more complex scenario, some actual videos included, I've seen it occur on every jpg -- or on some -- in a sequence.
    This is very repeatable here - 100%. Anyone else who's noticed it? I'm on the CS6 trial, and still thinking whether to purchase, or go on the Creative Cloud.
    Regards,
    Clive

    We're seeing a worse issue when exporting in H.264 and playing in QuickTime 10.0 (Mac OS 10.6).  We are using a custom size video to fit a spot on our website (398x498).  When exported and played in QuickTime 10.0 the white inverts throughout the video (back and forth).  The same issue is not seen when viewed in VLC or QuickTime 10.1.
    This is how the video should look:
    And this is how they are appearing:
    But like I said, the issue is very specific to QuickTime 10.0 on Mac 10.6.  VLC, Flash, Chrome, FireFox all play it correctly.

  • Flash Frames On Incoming Video

    I have the strangest problem with flash frames I've ever seen. Whenever I make a cut at a scene change in my footage I get a flash frame on the incoming cut. I immediately assumed it was a field so I lopped off the first frame and... no luck. I actually have to tim off the first 3 to 4 frames! to rid the cut of the flash.
    My sequence of events: I ripped supplied footage from DVD using Handbrake & de-interlacing into an progressive, Mpeg4 file. Then, using Compressor, rendered it into a progressive, ProRes 422 HQ Quicktime. However, the ProRes 422 HQ Quicktime had this bizarre brightness change when I hit play in FCP6. It was annoying so I used compressor again to transcode the ProRes 422 files into progressive H.264 Quicktimes. They seem to play & edit fine... except for this issue. Unfortunately, this issue is a showstopper. There's no way I can continue to edit with this media doing this.
    I've searched the forum for similar posts but none of the problems ever seemed solved, and certainly none of the solutions suggested are working for me; I've trashed preferences, trashed rendered files & re-rendered them, etc. I have zoomed in to verify that there are no extraneous frames. Also, if I import the ProRes 422 Quicktimes and edit with them, they don't seem to have this flash frame issue.
    Anybody else seen or heard of this issue? Why would an errant field exist across 3-4 frames? Anybody have any suggestions? Any and all help would be greatly appreciated.

    Handbrake is the wrong tool for this...MPEG STREAMCLIP or DVDxDV Pro are the better options. I use DVDxDV...REALLY good with non-Hollywood movie type DVDs. Can extract to DV or Uncompressed...whatever you need. MPEG-4 like H.264 isn't meant to be used as an editing codec, it is designed for final delivery. That might be why you are getting the odd flash frames...the way it is compressed.
    As for ProRes brightening...that means that your system needs to reduce the quality of the image in order to play it back without dropping frames...that is one symptom. Another is really low quality playback. To see what you really working with it is good to have a capture card and external monitor connected so you can tell what things really look like...as the computer monitors are playing back a low res proxie.
    Shane

  • Export without "transcoding"? (h264 Eos .mov files)

    Hy!
    My question is: Is it possible to export from the original footage without transcoding bits that dont need to?
    I am using a Canon Eos 550d which produces h264 .mov files with 49mbit/sec. As I believe mercury-playback-engine acts as a frameserver to the editing program of CS5 and serves only I-frames to Premiere. Mercury decodes the files and plays them back, and btw it doesnt report the proper clip properties - My Canon Eos 550d .mov footage (sequence setting: preset: digital slr - dslr 1080p25) shows up as "Type: MPEG Movie" when I choose right-click-Properties. But I assume that internally the footage is not transcoded to mpeg but just decoded by mercury and played back, so Premiere only gets I-frames to handle.
    So the question at this point is: What is the source of footage that the export module uses? Does the export module rely on mercury and is feeded only i-frames (aka decoded footage), so that transcoding has to be done, as not to transcode at this point would mean to save uncompressed 25p-full-size-frames one after the other? Or is the export module taking the source file and re-encoding (I understand that there is no "transcoding" with h264, or at the time beeing not yet..) it (because then, as I understand, it would be possible to save parts of sequences withour re-rendering them)?
    So, if it is possible, how to tell the export module not to re-encode the bits that dont need re-rendering (all parts that are not near any cuts or effects)- which settings are to be taken, or is there an automatism?
    Thanks!

    You are looking for "Smart Rendering." PrPro does not offer that. Not sure which NLE program you will need, but I think that at least one version of Sony's Vegas offers that. Google/Bing "smart rendering," and you should get a list of NLE's, that support it.
    Now, there can be major issues, as one is going from a GOP format, to a GOP format. Might, or might not, come out right.
    Good luck,
    Hunt

  • H.264 gamma shift/washed out colours on export

    I know this has been discussed before but I've been researching this topic for the past two hours and still can't find a solution.
    I have .mov source files from a Canon 7D. Exporting them from PP CS5.5 (Mac OS X - Lion, 10.7.4) in h.264 or by 'matching sequence settings' results in a gamma shift/desaturated colours. Playing the resulting h.264 file in QuickTime Player, VLC, Elmedia all result in the same colour shift so this is not an issue with QT simply interpreting the gamma incorrectly.
    Uploading to Vimeo and Youtube results in the same gamma shift. The monitor I'm using is not calibrated but when puling up a VLC window of the exported file next to the Program Monitor (on the same monitor) shows that there is a definite difference. Below is a screenshot.
    Is there any way to produce an exported file for Vimeo use that reproduces the gamma as I see it in the Program Monitor?
    Any help would be massively appreciated.
    Thanks.

    Did you use Quicktime's H.264 export option? Or just standard h.264 using the .mp4 container? If you used the Quicktime h.264 the option itself is flawed. Here are some links regarding the issue.
    http://provideocoalition.com/index.php/cmg_blogs/story/brightness_issues_with_h264_quickti me_movies/
    http://www.videocopilot.net/blog/2008/06/fix-quicktime-gamma-shift/
    http://imnotbruce.blogspot.com/2011/07/fixing-quicktimes-gamma-export-problem.html
    https://discussions.apple.com/thread/1358418?start=0&tstart=0
    http://byteful.com/blog/2010/07/how-to-fix-the-h264-gamma-brightness-bug-in-quicktime/
    https://discussions.apple.com/message/8551140?messageID=8551140#8551140?messageID=8551140
    https://discussions.apple.com/thread/2292530?start=0&tstart=0
    If you read around the net a lot of people have had this issue with h264. A couple of the articles I posted are supposed to "fix" the problem although I haven't ever tried any of them myself. I've never experinced a gamma shift when using the standard h.264 format option in Premiere, however if you have already used that option and you're still having issues then I have no clue what is going on. However when I import ProRes files into Premiere they don't appear washed out, but when I play them in Quicktime or VLC they do appear washed out. I've always just assumed Premiere was somehow correcting it, because when I export my video to mpeg-2 for playback on our server it looks like it looked in Premiere.
    From what I have read though the reason the Quicktime format does this when using the h.264 codec looks and looks washed  out is because of a incorrect gamma tag. But Premiere isn't affected/fooled by this like most media players are. According from how they made it sound on provideo and the one other site I read it on anyways.

  • Quicktime X and After Effects CS4 - Unwanted Color / Gamma shift

    Hello,
    Upon the import of ANY video footage file into After Effects CS4, there is an immediate color (I am guessing a gamma shift) difference between how the video appears in Quicktime (both X and the older player) and how it appear in the After Effects composition window.
    Footage appears to be darker in AE and lighter in quicktime, both before and after export. The gamma/color then appears roughly the same when being compressed via h.264 and uploaded to the web (the same in Safari, much darker via Firefox).
    My main concern is simply getting AE's color to match Quicktime's so that I can have as close of a match between the color I think I have created in AE, and the actual color that appears in my final output to the web.
    I have tried using all of the fixes to be found relating to gamma shifts via .h264, prores, etc. but nobody seems to have this problem with every codec, even animation. I have tried assigning color profiles in AE, matching quicktime legacy formats, etc. All of the options available in AE to no avail.
    My monitor is calibrated fine, I am using Perian, All of the latest software updates. Any advice much appreciated!

    Hi, thanks for the link. While helpful I am still having problems!
    I tried using the method described with Automator to assign a color profile to a test Animation file, created from scratch in AE and rendered out as an Animation with no color management (previously it made no difference to the quicktime gamma shift as to if I had assigned a working color space or not within AE).
    Automator only gives three color profile options, HD, SD, or PAL. I tried using HD as this is the size of video I normally work in (although I am also working in PAL), and ran Automator. I also tried using PAL and got identical results. It took about 30 seconds to finish and the result indeed looked much better in QT, and opened up in AE looking identical to a copy of the same .mov file with no color correction.
    However, there is *still some change in the image quality as it appears in QT from how it (and the original) appears in AE*.
    Original created / displayed in AE: What I am trying to maintain
    Rendered out, Automator color profile HD assigned, and opened in QT: Gamma looks good but colors slightly more saturated than original in AE.
    Rendered out with no color profile: Original problem with large gamma shift making everything bleached/washed out.
    I have a screen shot I can show you to illustrate this here:
    http://www.yousendit.com/download/THE0ek9xa0RxRTNIRGc9PQ
    While the difference is subtle you can look at the RGB numbers and see the middle example is indeed more saturated.
    Perhaps I need to use another color profile when working with the animation codec for animations created from scratch in AE to avoid this saturation shift, other than HD or PAL? Would you know of how to do this?
    Also, would you know of how to change this, and perhaps a way of changing qucktime's interpretation rules for all animation files per se, so that I do not need to go through every .mov with the animation codec and assign profiles to them?
    Many thanks for your time and sorry for being so long winded!

  • Canon 5D h.264 files to Prores introduces gamma shifts

    I can convert these files with QuickTime Player fine. But using the Compressor 3.5 preset for Apple Prores 422HQ Introduces random gamma shifts in the file - when viewed with QuickTime Player or FCP.

    Why are you transcoding them in the first place? Doesn't FCP work with H.264 natively?!

  • Corruption when transcoding from DV to Mpeg to in FCP, QT and Compressor

    After transcoding some DV files (exported from FCP) with white 'flash frames' to m2v using Compressor, i noticed that these same frames are green with lots of corruption around them.
    Any clue as to why this might happen?
    http://www.zen67493.zen.co.uk/corruption.jpg
    Any help would be appreciated.
    Thanks
    J

    Thanks for the help and tips.
    Ok so when I turn on the chroma and luma range check I get an "!" in the window, so there is clearly too much of something!
    However when I lower the 'Max Luma' level on the filter I'm using (Too Much Too Soon Flashframe), I still get the same problem when converting to m2v.
    I am begining to think that it's filter itself is causing the problem rather that the compression. The DV codec seems to handle the out of range luma but as soon as I convert it to m2v, the problem is back.
    So....deep breath, can anyone recommend a filter that will give me similar results to the 'Too Much Too Soon - Flashframe' transition? It increases Luma whilst blurring either the out going or incoming clip and it looks great.
    Thanks again for all your help. Unfortunately I am in the UK Michael and unable to pop of to your edit suite. Thanks for the kind offer though.

Maybe you are looking for