QuickTime gamma shifts with H.264 HD files

Hi,
I experience some odd gamma shifts while playing full 1080p full HD content. During playback the video suddenly gets lighter and after a few moments switches back to normal / darker light.
This happens while playing videos in Lion QuickTime 10.1 (dunno about earlier versions) and also Lions iTunes 10.4 64bit. The videos play fine in other players like VLC and even on Apple TV 2.
I will provide any additional info to this bug if required. As of now I don't have any solution on how to avoid this bug.
The bug happens on 13 different well known systems (tried in 3 different households and an apple store).

Hi:
I've been experiencing all sorts of issues with compressor, somewhat like this. I think my quicktime plug-ins are the culprit. Example, I have been exporting directly out of Motion with no problems lately, but when I export to Compressor I see my "Flip4Mac" import window several times, then Compressor either fails to export, or crashes.
I would suggest trying a direct export from FCP or Motion, or whatever your source is. See if that works. Just bypass Compressor and choose your HD DVD option from the export window. It does the trick with Motion.

Similar Messages

  • Quicktime error -50 with "H.264 for DSP"

    Hello.
    When compressing for HD DVD with the profile "H.264 for DVD Studio Pro" (on macosx 10.5.5, QuickTime 7.5.5) I systematically get a QuickTime error -50, about which I am finding no information at all. More, precisely this is what the logs report
    (in com.apple.stomp.transcoder.stomp.log)
    ... msg="Processing service request error: QuickTime Error: -50"
    (in com.apple.compressor.cluster.admin.log)
    <log ... msg="Handling exception: ... fatal exception = QuickTime error: -50, fail count = 1." />
    <log ... msg="Stopping the failed request." />
    This happens with all kind of sources, but only when the setting is "H.264 for DVD Studio Pro". All other settings work as expected. I don't know what to think, possibly an upgrade problem, possibly one of the QuickTime plugins installed on my system might be interfering (but then perhaps the error should occur given a source for all output settings, rather than vice versa, fixed the DSP setting for sources of all kinds). Google doesn't seem to know about this, searching this mailing list hasn't helped, nor grep-ing my system for more expressive error reports.
    In way of help, can please anybody:
    (1) confirm that they are able with Compressor 3.0.4 to produce H.264 for DSP
    (2) shed some light on what this QuickTime Error: -50 might be, perhaps by pointing me to log files where some more information is given? (fatal exception -50 is not very helpful, really...)
    My interest is of course to learn how to bypass the problem, or alternatively to convince DSP to accept H.264 in HD DVD projects generated by encoders others than Compressor with "H.264 for DSP" profile, or alternatively to understand how to make DSP accept H.264 generated by a third-party encoder (eg x264). Does anybody know?
    thanks

    Hi:
    I've been experiencing all sorts of issues with compressor, somewhat like this. I think my quicktime plug-ins are the culprit. Example, I have been exporting directly out of Motion with no problems lately, but when I export to Compressor I see my "Flip4Mac" import window several times, then Compressor either fails to export, or crashes.
    I would suggest trying a direct export from FCP or Motion, or whatever your source is. See if that works. Just bypass Compressor and choose your HD DVD option from the export window. It does the trick with Motion.

  • Gamma shift with LStar-RGB profile

    Hi everybody
    I have a problem with gamma shift when I import a picture which has the LStar-RGB profile embedded. Anybody else with this problem? Any solutions?
    If I open the same image in Preview or Safari everything is fine.
    Thank you
    Marc

    Hi Marc,
    I have had a similar problem using the eciRGBv2 profile which I believe is the same as LStar-RGB. In my case when I exported images to an external editor they would open up dark in the editor. After work on the images they would return to Aperture and open up too light. I have also noticed that existing images that use this profile display too light in Aperture; the preview is fine but when the image finishes loading it is light. I thought this was some exposure issue as there seemed no effect on colour (although all of my images are black and white conversions) but gamma shift would sound right.
    I noticed this problem after simultaneously upgrading to Mac OS 10.6.7 and Aperture 3.1.2 so I am not sure which is the source of the problem. Apple engineers are currently working on the matter but I wonder myself whether this is an ICC version 4 profile problem. All the images I have had problems with use the version 4 profile. I have tried using the ICC version 2 profile and this works okay. You will know (or can look up in ColorSync Utility) if LStar-RGB is a version 2 or version 4 profile, and depending on the answer to that you could try to use the eciRGBv2 profile in its ICC version 2 guise.
    I hope you find an answer soon as I realise how frustrating this is.
    Phil

  • 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!

  • FCP 7 on Snow Leopard - Quicktime gamma shift!

    i am running Snow Leopard 6.0.2 and Final Cut Studio 3 in a 2008 2.8GHz Mac Pro Quad Core. My monitors are two 23" Apple Cinema Displays, both calibrated to a gamma value of 2.2.
    Since upgrading to Snow Leopard i have noticed, that when exporting a Quicktime movie, color corrected using the canvas, the output file, opened with Quicktime X or 7 looks washed out. When i compare the output file with the picture in the canvas there is a big shift.
    i currently do not have the budget for a professional Broadcast monitor, so i need to rely, to a certain extent on my Apple Cinema Display.
    i have searched far and wide for a solution, but have been frustrated immensely.

    However, when I try to download Quicktime 7 for Snow Leopard, it tells me I cant install because Quicktime X is already present.
    When you say "Quicktime 7 for Snow Leopard" are you referring to the normal QT 7 download page or the special "QuickTime Player 7.6.6 for Mac OS X v10.6.3" download page? Snow Leopard requires a special version of the QT 7 Player that gets installed in the "Applications > Utilities" folder.

  • 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!

  • Quicktime 7 pro export h.264 better than iMovie quicktime setting?

    Hi, wondering if anybody knows if Quicktime 7 pro will export h.264 files (mp4) with better quality than going thru iMovie 11 and using the Quicktime plugin? The results are ok with iMovie but wondering if Quicktime 7 Pro would export better as a standalone unit? Looking to make super small files from chopped up dvd's that will play on all mobile devices..Been using baseline profile setting in iMovie Quicktime plugin so it plays on iPhone 3g as well..  Thanks everyone!

    I am trying to create very small files from a DVD , just simple chopping the DVD up into sections...when I use Handbrake to rip the DVD to a small h.264 (mp4) file the quality is surprisingly good...if I rip a higher quality mp4 to use in iMovie the export to smaller h.264 files don't look nearly as good when trying to get files sizes equivalent to Handbrake...I have tried ripping the highest quality video from DVD to use in iMovie '11 but when trying to export using QuickTime plugin to get h.264 (mp4) files they don't look that good...basically if Handbrake had editing capabilities the chopped up files would look better from there...
    You are experiencing a process of diminishing returns by continuously re-compressing the video from less efficient codecs to more efficient/same efficiency codecs at the same or lower data rates which tends to degrade quality with each re-compression. My recommendation would be to purchase the Apple QT MPEG-2 Playback component ($20) and use it with MPEG Streamclip for your work flow. (Note: If you are using Lion, the component installer won't work correctly and you will either have the use the Squared-5 beta utility to install the package or install the codec manually.)
    A better work flow would be to load the DVD titles (VOB file data) to MPEG Streamclip and edit the content there in its native MPEG-2/AC3 or MPEG-2/PCM compression format. You can set in/out points the same as using QT 7 Pro and save the segments as separate files using an alpha-numeric filename convention denoting the order in which you later want to merge the segments. Once all segments are saved, just drop all of them simultaneously back to the MPEG Streamclip work window and they will be merged in the proper alpha-numeric order. You can then fix "timecode breaks" and export the final product to your targeted compression format. Since you only re-compress the project once, depending on the codec/settings you use, your final file should approach the quality achieved in HandBrake. I.e., this is the main benefit of editing in the original "native" codec used in the DVD content.

  • Setting hinting for H.264 MP4 files? Possible?

    I want to stream H.264 MP4 files for my online media class. Before with QT files, I set the hinting so the video loads and plays immediately. With H.264 MP4 files, end users have to download the entire file before it plays back in the browser.
    I searched under the various H.264 settings but have failed to discover where I can set the hinting/progressive download option.
    Can anyone help me with this?

    FAQ:Why has my question not been answered?
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • 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?!

  • H.264 Gamma Problems with Firefox & Opera?

    I've encoded some video (from a ProRes 4x4 source in compressor) using the x.264 codec.
    When I view the x.264 file in Quicktime X, Quicktime 7, or VLC it looks fine.
    When I view the x.264 file online using Safari and Google Chrome (also Firefox and IE on a PC) it looks fine.
    BUT... when I view the file using Firefox or Opera for Mac, the file looks much darker.
    Is there a reason the file looks darker in Firefox on the Mac then elsewhere? (Something that quicktime within that browser is reading wrong) And is there a fix?
    (FYI - I'm running Snow Leopard 10.6.4)
    Thanks

    Harm Millaard wrote:
    Calibrating your displays with an Elite Spyder3 or similar is very worthwhile,
    Of course. And mine is calibrated.
    I was just trying to take an extreme example to illustrate the fact that even though Jim Simon is only describing a reality, it does not mean that a good and consistent result (not necessary ideal) cannot be achieved otherwise, with less equipment. 
    Harm Millaard wrote:
    but can't match an external monitor.
    That part I don't understand though.
    Is it not in contradiction with the first part of your sentence ? Why ?
    Harm Millaard wrote:
    Everything played with QuiRcktime on a PC shows a gamma shift. They have earned this name.  VLC does not and shows the same picture as PR.
    How does one grade his colors on FCPX then if it displays exactly what QTX displays (which is brighter and less saturated than VLC) ?
    Yeah I know, we're going in circles here ... but I would really love to find some kind of solution to this.

  • 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.

  • Quicktime player gamma shift

    I'm playing back a ProRes file I rendered on my iMac.  Using the new default QuickTime Player, I noticed what seemed like a gamma shift; the colors are more pale.  When I play the same clip in the old QuickTime 7 Player, the colors are more accurate.
    I thought the new QuickTime technology was supposed to do away with gamma shift issues.  Am I wrong?

    My work in AE is the final video and it is intended for the web.
    I tried a lossless export and the result of that is that I have a gamma shift directly.
    Also, I ran into this thread
    http://forums.creativecow.net/thread/2/994565
    Where Todd Kopriva says that :
    "The QuickTime format can now contain an embedded ICC color profile. But After Effects doesn't know that. There's a feature record in our database to make it so that After Effects does know about this and can embed an ICC color profile into a QuickTime container; I just called the person responsible for that feature and suggested that I thought that it should be a higher priority for future development. So, there's no need for you to file the feature request."
    And my video is kinda like it has a profile in it that only Quicktime sees. Not the others players.
    well I am confused ...

  • Quicktime on Windows clients can't open files in folders with long names!!

    Hi,
    we've got a really strange problem. We have an Intel Xserve with Leopard Server 10.5.4 which is sharing files over SMB. Everything works fine, except Quicktime on Windows clients (XP Pro and Vista). It looks like the length of the folder names is the problem. If a single folder in the path to the mov has a name that's longer than 8 characters, Quicktime fails with "Error -43: A file could not be found."
    x:\test1234\test.mov works
    x:\test12345\test.mov doesn't work
    Same for UNC paths. VLC on Win and Quicktime on OS X work without problems over SMB. Also the problem doesn't exist on other Samba based fileservers.
    Any ideas? Perhaps some smb.conf tweaks to fix this?
    Best regards

    Just found this post
    http://discussions.apple.com/thread.jspa?threadID=1360461&tstart=0
    Seems like a well known problem

  • Creating H.264 FLV file as per Spec, does not play with Adobe Flash Player 10

    1] We have developed an application to encapsulate H.264 video inside FLV container, following the "Adobe Video File Format Specifications 9". According to the specification the H.264 video data is embedded in FLV tags, as follows
    FLV Headers: Meta Tag: Sequence of Video Tag.
    But in spite of following the specifications, Adobe Flash Player (version 10) could not play this FLV file. However, some players were able to play this FLV file. The fact that Adobe did not play it was very surprising.
    2] We searched and finally found one FLV file, which contained H.264 video (unlike others which usually contained Sorenson's H.263). This file was played fine by Adobe Flash Player. So it led us to investigate further and we found that
         [A] the video tag was preceded with 2 byte length of the every "contained" H.264 NALU. This applied to all the NALUs / I-slices/P-slices and so on.        This is not documented.
         [B] Only the first video tag (containing video sequence params), is preceded by the sequence "01 4D 00 15 FD E1" followed by 2 byte length and then      the video data (sequence parameters in this case). What are these additional bytes ? where are they documented ?
    Could you pls share your views about the above and point us to the documents, if any, which are in agreement with the above observations.We think there is a discrepency in the document related with authoring FLV file with H.264 content.
    Thanks,
    Abhijeet Wakle
    Sigro Systems

    You could push it out to one or two users and test.  Moving up to the latest version of Flash Player is USUALLY a good idea, however, if you happen to be on Captivate 4, be aware that there was an issue reported some time ago that once you upgraded your development machine to Flash Player 11 it interfered with publishing out courses.  I cannot remember seeing a bugfix issued to Cp4 users for this (someone correct me if I'm wrong).  If you're on Cp5 or 5.5 this shouldn't be an issue.

Maybe you are looking for