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

Similar Messages

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.

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!

Colours wrong when RAW file with Adobe RGB profile printed from iPhoto '08

I've taken some photos on my Nikon D300 with the colourspace set to Adobe RGB. These import and display fine in iPhoto '08 but when printed it looks like the printer (Epson R2400 with the Epson 6.12 driver) is using the sRGB colourspace. The only option I can find relating to colour, is the Color matching dialogue which gives the option of Colorsync or Epson Color Controls. I've tried both with the same results. Preview shows the profile of the .nef file to be Adobe RGB (1998).
Has anyone any ideas of what I need to change?

AndyMn:
Welcome to the Apple Discussions. Most inkjet printers are geared for the sRGB profile. The Adobe profile is used by professional printers. Apple's services also recommend the sRGB profile. You need to reassign the sRGB or sRGBIEC1966-2.1 profile. I'm not sure about the raw file but you can use the ColorSync Utility to assign that profile to the file.
I have an Applescript that will apply the profile to files or folder of files dropped on it. I'm not sure if it will work on RAW files but it does on jpgs and tiffs. You can download it from Toad's Cellar. It takes about 6 seconds per file but does not apply any additional jpeg compression to jpg files.
Assigning the profile is considered better than the Applescript way but can only be done one at a time. You can test each method and see what gives you the best results.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.≤br>
Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Color Shift with ProPhot RGB in CS4

When I had CS3 I would be able to open a RAW image in Photoshop with the ProPhoto RGB color space. I would then change the color space as needed.
In CS4, I am using the 64-bit version, and there is a color shift when I open a RAW image in Photoshop with ProPhoto color space. The color is desaturated.
There is no color sift when I open the same image using Adobe RGB.
Why is this happening?
Lynnea

There is a color shift when the Photoshop color space is set as ProPhoto (Edit>Color Settings) and the RAW color space to open in Photoshop is set as ProPhoto.
There is no color shift if RAW color space is Adobe RGB and the Photoshop is set with ProPhoto (Edit>Color Settings).
But, when I save the image, the color space in file information as seen in Bridge is Adobe RGB.
Could this be connected to GPU and "Move Color Matching to the GPU?"
I have seen comments concerning GPU and color sifts, but I don't really understand them.
It is frustrating since I do calibrate my monitor and have seen some of the images in both CS3 and now CS4 and thus can see the difference.
LYnnea

Open with External Editor Profile sRGB instead of Adobe RGB

Hi,
I know in the export presets I can adjust what profile aperture will use. But what about when I open with External Editor. I like doing this because I can open my image in PhotoShop make my adjustments then save it and have aperture manage my files. But when I do this it opens the file with Adobe RGB, my lab and I sometimes want Adobe RGB. How can I change this without exporting the file and reimporting the file. Thanks.

Aperture uses a color space larger than AdobeRGB and sRGB. When an image is sent to Photoshop is converted to a 16bit AdobeRGB PSD file in order to get the largest color space to work with.
sRGB would be necessary when exporting to the web and/or send it to a printer that requieres that color profile, and that's why you have it in the export presets.

5.1.1: there's still gamma shift from AE with uncompressed codec

O.k. - this issue has annoyed me for years and has caused me to come up with all sorts of silly workarounds. I saw that with 5.1.1 and the pro app update we were promised a fix for this:
Uncompressed 422
Uncompressed 422 delivers a fix for changes in color-space and/or gamma when moving clips between Final Cut Pro and Adobe After Effects and addresses a codec issue leading to drawing errors in 16bpc After Effects projects....
However, i still get the identical gamma bump as before with this $49 update. . . is this update working for anybody yet?

Sorry, I don't use that specific codec. I export footage to AE in the format I am working with, and back in the same format, typically DVCPRO HD. And I see no gamma shift.
Try the Animation codec?
Shane

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!

Soft Proofing with Adobe RGB

I am experimenting with soft proofing various sunset images. The problem I'm seeing when I soft proof the images in Photoshop using the Adobe RGB profile is that the oranges and magentas in the sunset turn yellowish. Can someone please explain why this is happening. I admit that some of these images are coming from the internet and have no embedded profile. I have always thought that the Adobe RGB profile had a larger color space so I'm not sure why I'm getting the obvious changes in the sunset colors when switching between sRGB and Adobe RGB.

With a standard monitor everything you see on screen is already soft proofed to sRGB. That's all it can reproduce. So soft proofing to Adobe RGB makes no sense. It's beyond the monitor's capabilities.
Even if you have a wide gamut monitor soft proofing to Adobe RGB makes no sense. You'd need a monitor that reproduced considerably more than Adobe RGB (which doesn't exist), and a file in an even larger space such as ProPhoto.
If you see a difference, you have "Preserve RGB numbers" checked in Proof Setup (which you normally shouldn't). This is the proof equivalent of Assign Profile - IOW how it will look if you assign Adobe RGB as opposed to Convert to Profile, which is what you normally do and which will preserve color appearance.
The other possible explanation is a rather evasive bug in Photoshop, reported from time to time. Sometimes people see a color shift when converting to the very same profile as the file already is. I can't reproduce that, so I can't give any more details.

Targa gamma shift

Has anyone ever come across this: I've been using the same targa sequence output module and render settings in CS3 for the last 6 months without issue, and now all of the sudden my post house is telling me they're getting a gamma shift on my renders, that the blacks are lifted and everything is a little milky. I don't see any problem on my end--when I compare my render to the original sequence they gave me there is no apparent difference.
Even weirder is that I had a totally different post house on a different show with different targas tell me the same thing, and I was using CS4 for those shots. So it's gotta be something on my end, but what it is I have no idea.
Any ideas on this would be greatly appreciated.

I'm not sure, but this sounds like they are simply not importing them correctly. Maybe they misinterpet the Alpha and it makes the color fade and when whatever editing suite they use fills the transparency, colors wash out. Apart from that - Targas will always use whatever default Gamma your program has and directly encode the skewed color info, which in a computer environment is anything from 1.6 to 2.2 or in case of 3D programs, the Gamma you define in the render settings. Beyond that the format is completely agnostic of color profiles or additional calibration meta data. Maybe you simply mis-tweaked you monitor?
Mylenium

Gamma shift from After Effects

Hi,
We had to apply graphic work over a QuickTime Uncompressed 8 bit footage from Final Cut Pro.
The graphic work was done in After Effects.
The After Effect output was done using QuickTime Uncompressed 8 bit, the very same codec.
...but all the footage has a gamma shift ( upward ) and a slightly increased color saturation...
What's wrong ?
If we export Uncompressed 8 bit from FCP and reimport in FCP, there is NO gamma shift. ...so it seems to be an After Effect setting (or problem).
thanks !

Well I must specify that we haven't had any problems with gamma when working between After Effects and FCP in Mac OS X. It's just if you bring some material from PC to MAC you might notice that graphics are too bright, because FCP thinks all the RGB material is made with gamma 1.8. So FCP maps RGB colors to YUV (television colorspace used by DV, Uncompressed 8-bit etc.) with gamma 1.8.
BTW FCP doesn't collaborate with color management in OS X. So it doesn't make any difference how FCP handles RGB material if you change OS X gamma to 2.2.
FCP works in YUV and After Effects in RGB so that's why you don't see gamma problems when exporting material from FCP. I think you should first check from Apple Software Update you have the newest Pro Applications Update. I remember Uncompressed 8-bit codec had this kind of gamma problem with After Effecs couple updates before.
G5 DP2.5 (3.5GB RAM) Mac OS X (10.4.5) FCP 5.04, AJA Io, XSAN 1.2

Snow Leopard Prores 4444 Gamma Shift Nightmare

I've run into a nightmare with significant gamma shifts wrecking a lot of work we're trying to export using the Prores codec and After Effects CS3 (and CS4).
I found this supposed fix, but it has not solved my problems: http://blogs.adobe.com/toddkopriva/2009/12/prores-4444-colors-and-gamma-s.html
I appended suggested xml edit to the last line before </MediaCoreQT...> in both CS3 & CS4 files. Same infuriating darker gamma result after both edits.
Scenario: large targa sequence we've been working on for months, established pipeline of compiling the targas in AFXCS3 (OSX 10.5.8), Project Settings/Color Settings/Working Space = none, exporting sequence as Prores 4444, gamma set to automatic. Colour matched targas perfectly.
Now we're trying to use new Macpros we've bought specifically for this job that are run up as 10.6.2. Prores 4444 compiles are now coming out much darker! I've tried the XML edit (both CS3 & CS4), adjusting system gamma to 1.8 from new 10.6 default of 2.2, adjusting legacy gamma setting in project settings, etc... The colour is wrecked!! WTF?!?!?
Really don't want to have to revert to "Animation" settings. Deadline looms. Any help would be enormously appreciated!

I Think (but dont know) that I have found an explanation to this problem.
It has to do with colorsync on OS X (cant talk windows as I dont use that)
Scenario
1) Encode any non-ProRes 4444-source to ProRes 4444 using Compressor(Only encoder able to provide accurate result)
2) Be sure so DISABLE - Final Cut Studio color compatibility in the QT7 Player Preferences
3) Open source.MOV and new output.MOV in Quicktime7 -> Set view of both to half size (So you have overview) and place them next to each other
They should look/be identical
sometimes placing them next to each other will lead you to believe that they are different. If so, place them on top of each other and flip back and forth via the Window menu to make sure that both movies are indeed identical-looking.
4) Open OS X System Preferences
5) Click 'Displays' and select the color tab
Now, toggle through various color profiles. You SHOULD see the colors adapt on BOTH movies.
Create new AE Project and make sure that your Project is set to NOT color-manage your workflow
6) Create new AE composition and drag the Compressor-created ProRes 4444.MOV into it.
7) Add to render queue and select the ProRes 4444 as output.
8) Render out.
9) Open Compressor-created ProRes 4444.MOV and new AE-created ProRes 4444.MOV in Quicktime7 -> Set view of both to half size (So you have overview) and place them next to each other
10) They should look identical but they dont.
11) Open OS X System Preferences (in case you closed it)
12) Click 'Displays' and select the color tab
Now, toggle through various color profiles. You SHOULD see the colors adapt on BOTH movies.
They DONT. They ONLY adapt in the Compressor-created ProRes 4444.MOV not in the AE-created ProRes 4444.MOV
And that even though color-mangement has been turned off.
Turning color-managemen ON will have no different effect that leaving it off. The AE created movie(Color Management set to OFF) WILL not allow being color synced in OS X.
The Expected behavior IS:
1) when color management is set to OFF in the AE project settings and output module that the AE-Created movie would adapt to any color-profile change made within the OS X System Preference, COLOR Panel.
2) when color management is set to ON in the AE project settings and output module that the AE-Created movie would NOT adapt to any color-profile change made within the OS X System Preference, COLOR Panel.
As of NOW... There are no differences between above.
I hope this helps to solve this nuisance !!!
If I have missed something VERY obvious then please disregard my post and tell me what I seeing incorrectly !!!
PS - ON my computer - this last part of my post looks ridiculously small and that even though I have done NO font editing.
I find that posting and editing in this forum is as hard as getting Adobe products to encode 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 ...

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.

Color problem with ProPhoto RGB color space

Hi, everyone,
I have wery special problem I think. I use MacBook pro 15" with retina display, adobe Photoshop CC and when I export RAW (from Nikon D7000) from Lightroom 5 to Photoshop with settings: 16 bit TIF, color space: ProPhoto RGB I have a problem with displaying the correct colors. As you can see in this picture:
My problem are some "green" artefacts in absolutely black and white picture. I tried myself to solve this problem and found the following facts: when I convert picture into Adobe RGB or sRGB color space is everything OK - without green artefacts.
But here is one important fact: I have calibrated monitor by datacolor spyder4elite and problem with ProPhoto RGB incorrect color displaying is only when the color calibration configuration is loaded. When I change my display calibration to standard apple color LCD profile than is everything OK.
But using uncalibrated monitor and also Adobe RGB color space are no right solutions for me.
My question is why I have problem with displaying ProPhoto RGB color space in photoshop under calibrated monitor profile and can anybody help me please?
Thanks for answers.

That's a classic example of the basic problem with 16 bit color. There is no solution that I know of.

Gamma shift with LStar-RGB profile

Similar Messages

Maybe you are looking for