Menu colors shift after build

OK, so my menus look good in DVDSP, and in the simulator. However, after building, when tested in the DVD Player, they look "washed out". Everything is lighter, less saturated...
I don't have any fancy broadcast standard video equipment here... but I'm watching DVD Player on the same monitor that I'm using to create the DVDSP project - I'm not that worried (yet) that the color is "accurate" in some way, I just want the DVD Player to look the same as the simulator - are there some settings I need to play with?
The video content itself does not seem to have a color shift from the simulator - only the menus. I did not make the menus (I mean the elements), I bought some Templates from a company that produces DVDSP Template Packs and loaded them into DVDSP.
I'm somewhat familiar with the whole issue of color spaces and gamuts etc., but I don't really see any settings in DVDSP to manage this.

I managed to fix this issue, here's what I did in case anyone else has this problem.
The issue was that the DVD template I purchased has a motion background, and when you apply the template to a menu (for example), it adds the a QuickTime movie for the background. The fact that DVDSP was rendering the .mov into a .m2v during the build is what caused the color shift.
I took the .mov background file, and ran it through Compressor to turn it into a .m2v file (with the same preset I used on all my other video), and then imported that asset and applied it to all the menus. After build, no more color shift.

Similar Messages

Menu color shift in DVD Studio Pro

THE PROBLEM: There is a color or gamma shift in DVD SP menu when you play the DVD on a regular monitor and also when you play the DVD image using Apple's DVD Player app.
The only thing that is effected is the menu. The footage, which was compressed in Compressor, is fine.
The menu looks correct in DVD SP and its simulator, but once encoded to a DVD, it's washed out.
This discussion held promise. Everything JeremyG says is what's happening with me. But at the bottom of this long thread, still no answer:
https://discussions.apple.com/thread/1559230?start=0&tstart=0
I know I am not alone in this, but I've spent hours looking through the discussions to find if a solution was finally found to this, and cannot. I hope someone can help, or if the gods prevail, maybe Apple will.
My specs:
OS: 10.6.4
DVD SP 4.2.1
Menu: PNG or PICT from PS CS4
If someone knows the solution to this, please help! Thanks. ~Kenny

I design in Photoshop. The colorspace is RBG 8-bit. I have all color management profiles turned off, but I usually use sRGB. I then export as either PICT or PNG. I also tried TIFF per your suggestion. Still the same issue.
Again, it looks fine in the menu composition window in DVD SP and fine in its simlulator. The problem is in the burned DVD, and is apparent whether viewed with the built in DVD Player, or on a set-top external DVD player.
BTW, I've been using this workflow for many years with no problem, but only recently did this start happening. The version of DVD SP hasn't changed. The OS went to Snow Leopard in 2011, but I think it was OK after that. Other changes would only have been regular Apple updates, so it's a mystery.

Chapter Markers shift after build in Encore when using PP dynamic lnk

When I create a sequence complete with perfectly placed chapter markers in Premiere Pro CS6 and send it to Encore via the dynamic link everything appears fine (it even simulates perfectly) until I build a DVD in Encore. After the build in Encore most of the chapter markers have shifted and are no longer perfectly placed. It's as if Encore encodes the video without regard to the chapter marker information and then adds them onto the already encoded video where they have limitations on which GOP frames they can appear. Shouldn't Encore take the chapter markers into account while encoding the video? The way around this I found is to export the sequence from PP and then import the video into Encore. All is well if I do it this way but I like the advantages of dynamic link. Encore just doesn't seem to respect the chapter marker information. Am I missing something or is this just a flaw in Encore?

Good questions.
Yes my source clips codec is motion jpeg at 29.97fps.
If I just focus on the second chapter marker in my test sequence (given the automatic first chapter marker is at 0 sec.) it is at 1:01 in the timeline which is off the GOP boundary of 15 frames. When I build the timeline this marker moves 1 frame back to 1 sec., a GOP boundary. Doesn't sound like a big deal but that puts the marker into the previous clip on my time line which causes the automatic thumbnail in my menu to be wrong and there's a little flicker when you jump to this chapter on DVD playback as it plays this one odd frame.
I guess I am transcoding during the build (am I not supposed to?) but I have since tried your idea of trying "transcode now" before the build. It sounded promising. While looking at my second chapter marker in the timeline I clicked transcode now and watched the marker jump back 1 frame. Cool, but I'd rather it didn't do that.
You are right I don't need a menu to examine this. It's just that the thumbnails changing in my menu after a build were the firts indication to me that something was going wrong. Again if I import a file that's already transcoded to En this isn't an issue.
It just looks like En doesn't respect chapter marker locations through the dynamic link to Pr and it should. It rather transcodes first and then adds in the chapter markers as close as it can to their original locations. It's possible I am missing something in my workflow but it at least sounds like you understand what I am experiencing.
Can you try modifying your test by creating a couple of 1-sec clips in Pr sequence with a chapter marker between them (so your first one is at 1:01) and then see if the same thing happens to your first chapter marker?

Color shift after upgrade to 7?

I just upgraded from FCP 6 to 7, and I could swear my footage (AVCHD converted to ProRes) looks just slightly bluer now. Is this possible? Is there something different about how FCP 7 handles the video that could cause this?
thanks!

Just on the computer screen, so I know the color is not accurate, but I just mean that it looks different now (bluer) after the upgrade to 7.0, than it did before. I know it could be my imagination, but I don't think so - it really jumped out at me right away.

Color shift after rendering

I have a 4x3 animation that I'm putting in a 16x9 frame. To fill the space I've added Color Solid Copy "wings" to each side and matched the colors. It all looks good until I render off the green preview line, and the color hue ends up shifting.
Any idea how to maintain the same hue?

It's your monitor, computer monitors can not be relied on for color accuracy.
Try setting RT to Unlimited.
Put all your animation on V2, put a Shape (Generators > Shapes > Square) on V1. Make the Square the size and color you want. Before editing it into the Sequence, in the Viewer window, top left, enter the duration you need. This will be more stable with coloring.

TIFF files color shift after import

I just imported a project of 1Ds MIII TIFF files first converted in Capture One then imported into Aperture. In the preview and when exported they are noticeably lighter and desaturated than the originals when both are compared side by side, to the point they can't be sent off for publication purposes, and I don't want to try to compensate for something like that. Proofing is off as far as I can tell.
My copy of Aperture and OSX are up to date...
Any ideas? Thanks!

I just imported a project of 1Ds MIII TIFF files first converted in Capture One then imported into Aperture. In the preview and when exported they are noticeably lighter and desaturated than the originals when both are compared side by side, to the point they can't be sent off for publication purposes, and I don't want to try to compensate for something like that. Proofing is off as far as I can tell.
My copy of Aperture and OSX are up to date...
Any ideas? Thanks!

How To Change Hyperlinks And Nav Menu Colors

I continue to see people stating that it's impossible to change hyperlink colors and navigation menu colors until after you publish your site. This is not true. It's quite easy to update your templates with the colors YOU want and when you update the template, you never have to mess with any post-processing. You make a new page? Your colors are already there.
I've gone over this before in this thread:
http://discussions.apple.com/thread.jspa?messageID=3288533&#3288533
But I'll go over the quick and dirty version here as well. Those who want more detail can post a question and I'll elaborate.
First, do you know how to get into iWeb's inner folders? You right click or control click on your iWeb icon and select Show Package Contents from the pop-up menu.
Step 2
Once you've done that, you'll see a new Finder window that shows a folder called Contents. Open that and then open the next folder Resources. Within Resources there's a folder named Shared. Open the Shared folder.
You're now looking at your collection of iWeb template files. You'll notice that each template has seven individual page files - each file defines the layout and styles for the page for which its named. This is actually one of the two places where you'll find the data/images that make up your iWeb pages. This location only contains the images. Now I'll show you were to find the data file.
So you're currently here:
/Applications/iWeb/Contents/Resources/Shared/
You want to go here:
/Applications/iWeb/Contents/Resources/English.lproj
Now if you speak another language and your Mac's system language is set to the language you speak, substitue English with that language. If your system is set to English regardless of the language you speak, and you use the English templates, then stick with the English folder.
When you're in the English.lproj folder, you will see seven sub-folders and one file named TemplatesInfo.plist. TemplatesInfo.plist is the file that registers the templates and tells iWeb what you've got in your collection. But we don't care about that file for now. We're after the template data files.
The seven sub-folders are aptly named for each of the seven page-types as you can see. Open the About Me folder.
Now you will see an "about me.webtemplate" file for every template you have in your collection. Good job. You've learned something new. Move on to Step 3.
Step 3
If you haven't decided yet, now's the time to decide which template you'd like to update. If you're just along for the ride to learn something new, no worries. We won't do anything you can't undo.
Pick a template file now. Perhaps you chose the White template, or:
White About Me.webtemplate
Right click or control click on this file and select Show Package Contents from the pop-up menu. This will launch a new Finder window that displays the contents of the White About Me.webtemplate file.
You will likely see a handful of different files, but the file you want is the one named Index.xml.gz.
Index.xml.gz is the brain behind the template. Within this file are all the settings for the page you chose and it's really not hard to find what you want and change it. So let's take a peek.
Step 4
Double-click the file Index.xml.gz. This will reveal a new file named Index.xml. You might have to scroll down in your Finder window to see it. Rename Index.xml.gz to Index.xml.gz.backup in case you screw things up, you have your original.
Now, open Index.xml with TextEdit. Do not open the file with a code editor unless you have already formatted the file.
When the file opens, you'll notice it's one gigantic jumbled mess of stuff. No worries, we'll straighten that out. All you need to do is a find/replace.
Find all instances of: ><
And replace with:
<
The line break is important so maybe just copy the lines right out of this post. When you replace all of those, the file will be far more easy to view.
Assuming you've completed that step. You're basically ready to make your change and test it out! Not hard ey?
So let's say you want to change your hyperlink color from grey to blue. Search for this string:
BLDefaultHyperlinkCharacterStyleIdentifier0
When you find that string, you will see a few lines below it, two lines that look similar to this:
<sf:fontColor>
<sf:color xsi:type="sfa:calibrated-rgb-color-type" sfa:r=".8" sfa:g="1" sfa:b="0.4" sfa:a="1"/>
This is how the template specifies color. It's RGB100. Your Mac came with a program called Art Director's Took Kit and that application can tell you the RGB100 values for any color you want. Tinker with that and you'll have a lot of fun with this.
So I picked out a nice royal blue for you. The RGB100 values for it are:
R:0 G:25 B:100
What you need to do is update the color line to match those values:
<sf:color xsi:type="sfa:calibrated-rgb-color-type" sfa:r="0" sfa:g=".25" sfa:b="1" sfa:a="1"/>
Notice that you specify these in terms of a percentage, where 25 became .25 and 100 became 1.
Step 5
Save your file. It's time to see your work in action. Open iWeb if it isn't open already and create a new page using the template you've just altered. If you altered the White About Me page, then select that and create the new page.
It there are hyperlinks already on this page, you should already see that they reflect your new color. If there aren't any hyperlinks, then type some text and create one. You should see your new link color right away!
Now if you don't see the new color, either you picked the wrong page or you neglected to rename the Index.xml.gz file a few steps back. If you did not rename that file, then it's still in control of your template. Rename it now and try again.
If you don't like that color, simply swap back to the TextEdit page and change it until you like it - switching back and forth between the file and iWeb to view your changes. Once you're happy, make note of the color you chose and make the change for the remaining six pages in the tempalte you selected. Just be sure to follow the steps for each page you edit. If you fail to see your change, again, check to see that you renamed Index.xml.gz.
Side Notes
For the more technical, rather than editing an existing template, you might want to duplicate and rename a template. This essentially creates a brand new one. If you're pretty good within Finder then go for it, just be sure that you duplicate the files in both locations:
/Applications/iWeb/Contents/Resources/Shared/
/Applications/iWeb/Contents/Resources/English.lproj/...
Choose a unique name for the duplicated template and change every single file so that the new name replaces the old one. You would have to register this new template in the TemplatesInfo.plist file as well, but I'm not going to get into that here.
The thread I referenced at the top has all kinds of search terms to find the other hyperlink styles (rollover and visited) and all the navigation menu styles plus a bunch of other fun stuff.
Now, it seems long, but that's because I wrote it well. The shortest version of this I've ever written was two sentences, but that was for a UNIX geek and he got it. It's just as easy for you, but I write it out so that anyone can do this, because anyone can. It's just not hard.
If you have questions about any of the steps, go ahead and ask.

Good. Okay here's how to apply a background color to your nav bar buttons. For example, my Aerolite template sets the selected page to a black background color. The rollover effect uses a gradient fill. I'll describe both of those here.
First, here are the navigation menu search terms:
navbaritem-style-normal-default
navbaritem-style-rollover-default
navbaritem-style-selected-default
navbar-pargraph
The first three set the button effects and text colors. The last one there sets the font, font size and other paragraph styles.
To change the selected page button background color, or gradient or image, first search for it using the search term above. Start from the top of the file because there are two instances of those terms, one where you can set the values, the other is only reference to the first and does not allow you to change settings.
When you find the search term, you might want to insert an empty line above it to help separate it from the rest of the code. You can also insert an empty line below the section. The end of this style ends with:
</sf:navbar-item-style>
Be careful not to mix that up with </sf:navbaritem-character-style>
Now, within this section, you'll find all kinds of settings... stroke, fill, character styles, etc. Notice you can change font color in there. But for this demo, you want to find the section that looks like this:
<sf:fill>
<sf:null/>
</sf:fill>
I'm assuming you're editing an Apple template that does not already have a fill effect. If it does have one, then your example might not look exactly like that.
To apply a color fill, change those three lines to these lines:
<sf:fill>
<sf:color xsi:type="sfa:calibrated-rgb-color-type" sfa:r="0" sfa:g="0" sfa:b="0" sfa:a="1"/>
</sf:fill>
You can see that we've inserted the line that specifies color - something you should be familiar with by now. Here you can specify the color that will become the background of your nav bar button. This example specifies black. Easy no?
If you would prefer a gradient fill, then replace those three lines with this:
<sf:fill>
<sf:angle-gradient sfa:ID="SFRAngleGradient-1111" sf:opacity="1" sf:type="linear" sf:angle="0">
<sf:stops sfa:ID="NSMutableArray-1111">
<sf:gradient-stop sfa:ID="SFRGradientStop-1111" sf:fraction="0">
<sf:color xsi:type="sfa:calibrated-rgb-color-type" sfa:r="0.40" sfa:g="0.40" sfa:b="0.30" sfa:a="1"/>
</sf:gradient-stop>
<sf:gradient-stop sfa:ID="SFRGradientStop-2222" sf:fraction="1">
<sf:color xsi:type="sfa:calibrated-rgb-color-type" sfa:r="0.64" sfa:g="0.66" sfa:b="0.54" sfa:a="1"/>
</sf:gradient-stop>
</sf:stops>
</sf:angle-gradient>
</sf:fill>
Now, don't panic Here's what this is. The first line allows you to specify the angle of your gradient. Play with the numbers from 0 to 359 until you have what makes sense for your design.
Then, you will see two familiar lines again - the lines that allow you to specify color! The first line is the first color of your gradient and the second color is the second color of your gradient. That's all there is to it!
SECRET: It might be possible to add additional colors, not just two. Do you see the part sf:fraction="0" and sf:fraction="1"? These are gradient stops. I'm willing to bet that if you inserted a thrid gradient stop with a fraction setting of .5, you'd have a three-color gradient!
<sf:gradient-stop sfa:ID="SFRGradientStop-3333" sf:fraction=".5">
<sf:color xsi:type="sfa:calibrated-rgb-color-type" sfa:r="0" sfa:g="0.25" sfa:b="4" sfa:a="1"/>
</sf:gradient-stop>
I have never tried this - it just occurred to me as I was looking at this code. Big prize for the first person to prove the theory
NOTE: You will notice that the number 1111 and 2222 are within this code. iWeb XML relies on identification tags here and there. It's nothing you really have to care about except if you insert gradient fills in more than one area. Those numbers need to be unique so if you paste that code in for your selected page button and then paste it again for your rollover buttons, you'll need to update the numbers for the second button. Any numbers are fine. Use 3333 and 4444 for the second set, 5555 and 6666 for the thrid and so on. I often just type 4345781476 - doesn't matter.
Next lesson will be images.

Pentax K-x RAW color shift problem with Aperture 3

I have seen a few posts similar to what my problem is but not exactly.I have two Pentax K-200D's and a new Pentax K-x. I shoot RAW with all of them and the K-200D's work great. The RAW files however from the K-x are doing something strange. Sometimes (more and more though) the files are being imported into Aperture and there is a radical color shift after they finish loading. ALL of the preview thumbnails look fine in the camera and the Aperture import window. However, after importing them and processing is complete, some of the shots have a magenta color shift, but most that have this problem shift radically to a green tint. Everybody looks like they are in "The Matrix."
I do not have any brightness correction on the camera turned on as other posts imply might be the problem. I have also remove the Aperture RAW 3.2 and tried 3.0 and 3.1 with no solution. 3.0 doesn't recognize the files at all and 3.1 does the same thing as 3.2. Here are two examples of UNEDITED RAW files:
Frame that looks fine in RAW
http://gallery.me.com/mattcline#100470/IMGP5982&bgcolor=black
The next frame taken with the same settings on the camera:
http://gallery.me.com/mattcline#100470/IMGP5983&bgcolor=black
I do have one possible pattern. I had the camera set on rapid fire capture. It appears to me that the first frame I take when the shutter button is depressed looks and translates fine. All the subsequent frames take in rapid fire under the same shutter release have the green shift when taking shots in relative shade. Things taken in bright sunlight have the magenta shift.
Any ideas on what is going on or how to fix this?
Thanks.

kb8wfh wrote:
I just downloaded Apple's RAW 3.3 and it still made no difference.
Going back over the files, I found that going back and forth between the two, see no difference in the RAW processing headings. I did see however that in the meta data that the two pictures I have in the example of those listed above have one difference. There is a setting on the Exposure Bias for the one that was fine was -0.3 ev and the one that has the green contrast blast has an Exposure Bias of 0.3 ev. So the one that looks right is slightly negative. Doesn't seem like that should be a big difference, but apparently it is.
I did take some pictures with the RAW+JPG setting and I had the same problem with the RAW files. Some were ok, some were green, others were magenta shifted. However, all the JPG files looked just fine.
Switching from Aperture isn;t really an option for me. I have been using it for a long time and it generally works very well...perfectly with my K-200D's. It's just some bug with the RAW decoder for the K-x.
It's a known bug and I have been in touch with Apple staff over it, including engineers. It's not just the K-x. Other brands (Canon) and models suffer from the RAW processor gone wrong.
Right now there is no fix. At the pace Apple works at, there may not be one for quite some time. Use JPEG, use iPhoto, or move to Lightroom.
Another suggestion is to phone customer service and complain that their "Pro" program is not working as expected. I spent hours with an engineer going over the issue including a screen share session, only to be told to use JPEG.
This was 4 months ago.

Divs are shifting after inserting spry menu bar

I have tried so much that it has driven me crazy. Initailly I created this site by APdivs and it came out perfect and worked great, except it was not fluid and looked bad on bigger browser and screen size. I decided to change it to fluid way. Now I am in bad shape as soon as I put a horizontal spry menu bar. it shifts the columns to the left and leaves a blank space next to the column 3. I am out of idea, how to fix it. As soon as I take the menu bar out, it works perfect. and columns are stretched to the end on both sides.
Here is the link of test page
www.hpbsurgery.net
This is what I have tried-nothing worked
put menu bar in container
put menu bar in header div
Put mebu bar in a horizontal div inside header div.
changed the size and dimension of menu bar
Any help would be greatly appreciated as I am running out of time.
Thanks much all....

Thanks very much for your help. I just wanted to mention one thing which I discovered this am by accident out of frustration. Originally, I was trying to control the size of the 3 columns with external CSS and it was messing up after inserting menu bar. I wrote directly in the code this am to exactly define the size besides in my CSS. AND............it fixed the problem and stretched the columns to the end on both side and sizes were appropriate, I am still not sure why did it happen.
I am not a professional and trying to build my own site as I have interest in web design, but this is first time with DW.
I really appreciate your help and suggestion about the code.
Thanks a lot,
Date: Wed, 26 Sep 2012 12:46:19 -0600
From: [email protected]
To: [email protected]
Subject: Divs are shifting after inserting spry menu bar
    Re: Divs are shifting after inserting spry menu bar
    created by Nancy O. in Dreamweaver General - View the full discussion
You appear confused about how to use CSS classes and IDs. Classes (.className) can be used multiple times in layouts as for re-usable styles. IDs (#IDName) can be used only one time per page -- as for layout regions or when JavaScript is needed to act upon it. Try copying and pasting this code into a new blank page. Hopefully it will make more sense than what you have now.
<!NEW LAYOUT>
body
#header
#horizontalmenu {
min-height: 43px;
width: 100%;
overflow: hidden;
margin: 0px;
#leftbar {
background-color: aqua;
float:left;
width: 18%; /*combined width and padding = 22%*/
padding:2%;
#middlebar {
background-color: white;
float:left;
width: 52%; /*combined width and padding = 56%*/
padding:2%;
#rightbar    {
background-color: green;
color:white;
float:right;
width: 18%; /*combined width and padding = 22%*/
padding:2%;
#credential
#footer {
background-color: maroon;
width: 100%;
color:white;
padding:2%;
#header
[Item 2 | #]
[Item 3 | #]
[Item 3.1 | #]
[Item 3.1.1 | #]
[Item 3.1.2 | #]
[Item 3.2 | #]
[Item 3.3 | #]
[Item 4 | #]
<!END #HEADER>
#leftbar
#middlebar
#rightbar
#credential
#footer
Nancy O.
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4729585#4729585
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4729585#4729585
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4729585#4729585. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Dreamweaver General by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

After Efftect to FCP color Shift

I am compositing video from FCP in After Effects out put back to FCP matching formats and get the RGB to YUV color shift. I understand why but not how to correct the problem. I have tried the sequence setting and selected render in RGB but the releative difference remains the same. I started a new sequence and selected render in RGB before puting any video in but the difference remains.
What am I missing?
Any help would be greatly appreciated.
M

Only thing I can think of is a work around... Process all the clips that are going to be part of the AE effect thru AE, so that the color is the same when you get to the effect. (hide the shift that way). It's a work around... you should report this to Apple too in FCP feedback.
Jerry

Color shift between viewer and browser after pro kit update

hi there,
i thought i be one of the lucky guys since updating and running 3.0.1 was easy on my system. but after yesterdays pro kit update i experience a weird color shift between the look of pictures in the browser and viewer.
there is a strong colorshift in orange parts of sundown pictures. they turn magenta in the viewer but stay orange in the browser. the difference can easily be seen in the split screen. even weirder if i export a picture from the vier/split screen the exported files show the magenta tint. if i export them from the browser, they have the "right" orange tint.
this happens with raw-files from both d200 and d70. also exportet the raw and processed it with ps cs3 and everything was ok. anyone got a clue?
thanx in advance

just found the explanation. after my prokit update, all raw-files needed to be reprocessed and then i needed to select the standard apple camera module for the d200. that was quite tricky and i don't understand why something like this happens. why do all files need to be reprocessed and than afterwards you would have to manually select the apple standard converter and why did the viewer look different than the browser and why is there no warning module that tell you all files will have to be reprocessed?

OS 10.4.6 is causing color shift in prints

Since I updated to 10.4.6 My prints have a severe red cast to them. All perameters used in printing are the same as previous and my Epson 2200 is working properly. I have color managment turned off in the driver and am using the correct prifiles fo the paper. I saw another post where others were having display problems but my images display fine but print badly.
Anyone else have this problem or a suggestion.
Thanks
Craig

Grrr!
I'm having the same issues as people above and as on some similar threads.
First, I've color managed for awhile. Beginning with calibrated monitors, Photoshop's "View" menu settings, my color space ...
I know not to double color manage, and I choose to manage through Photoshop. I've reinstalled everything and read these boards and other threads on the web.
Here are my problems.
I am getting severe color shift and cannot get an accurate print. I've spoken with Epson ($$) and Adobe. All fingers point to Apple. Going through the printing process, everything is fine until soft proofing before hitting the final print button. That preview ALWAYS shows a shift in color if any color management has been applied. (I just tested an image without any color management and there still is a shift.)
Today I trying to print blue hydrangeas for a town project; they are shifting toward magenta. Last week I worked on a town-wide Relay for Life (ACS fundraiser); night-time images with candles ... shifted green. (Again, my with calibrated monitors.)
Ironically, when I was on 10.3.7 I didn't have any trouble. After that it's been roulette. I have an Apple Care contract and called Apple. Understanding that not every rep knows the ins and outs of color management, I asked him to forward an email to someone who can help me.
Grrr. I was told that since Photoshop and Epson are not Apple products they can't help me. Surely, web searches show that this is known problem. (Some suggest trashing Apple's Generic RGB profile ...)
Can ANYONE at Apple help? Please? Isn't that what an Apple Care contract should do?
I have 20 (different) prints due to a family by tomorrow. I have an additional 150 prints due by Thursday. Am I expected to borrow someone's Windows PC and use it to send the image to my printer?
(Also, I've installed several icc profiles in the past, but can't install any currently. I'm trying to install Museo and Arches profiles.
What is happening? Newer profiles don't show up in the print driver's "Print Settings," "Media Type" pull down menu, no matter where I try to load the newer icc profiles.)
G4 - 1.5 GHz Power PC Laptop Mac OS X (10.4.7) OS 10.4.7; Epson 2200; Photoshop CS2; plus other peripherals not relevant to this issue.

Solution to Gamma/Color Shift Problems with Apple Codecs - Adobe BUG

Hi....
In AfterEffects when choosing an output module and that module be ProRes or 10 Bit Uncompressed,
when trying to color manage the file, there is a fine line called
'This Codec Does Not Support Output Profile'
You can find it int he Color Management Pane of the output module....
Funny thing is - That Profile Embedding IS support by:#
Apple's Compressor and THE CODEC 4444 AND UnCompressed
Episodes Encoder
See following Screen Shots:
First one from Apple's Compressor...
Look at that little beautiful Color Option... Adobe did you MISS that one, perhaps...
You must have - because your APPS are NOT including that when encoding or should I say
butchering movie files....
Here adobes famous but wrong dialog!!!!
And in this next screen shot you can easily see that adobe just strips the color profile out of the file...
AND THAT IS WHY THERE IS A COLOR SHIFT...........
left image = Apple's Compressor Encoding (Colors match of course) - Right Adobe's BRUTAL encoding (Colors WONT match...)
Now, in after effects you wont notice the shift. But ALL mac and PC users using quicktime to watch YOUR movies
are going to be looking at a movie with a different look than you thought it WOULD be... Courtesy of adobe ;-)
Jokes aside, Adobe.... It seems as if this one is on you to fix... Apple's Compressor has NO problems. And other encoders are also preserving those values.
Now... Let us assume that I encode in compressor... Looks are matching 100% that of the original source. All it takes to mess that up is ONE
roundtrip to after effects, premiere pro or Media Encoder. That is if I wanna maintain my initial choice of transcodec - in my case 4444 or 10bit Uncomp.
I could of course export to animation and then use compressor AGAIN to transcode to my format of choice... But in the long run I think that will become tedious.
Perhaps you could assign a few engineers on this one and in the future spend MORE time on living up to the name PRO(The most misused word in the software business) instead of wasting time generating new Application icons for your apps....
Thanks for reading and for a PROMPT and near-future BUG FIX

Mylenium wrote:
It's not really "embedding" anything, it merely sets the QT color space flags which have been there forever, but are mostly unused. Specific to ProRes it also toggles different internal optimizations in the encoding. That's also documented somewhere on the QT developer pages. I'm not sure I share your views otherwise. The point really is, that Apple developed ProRes just as much as a closed workflow within their products as Avid did with their CoDecs. Therefore the widespread use of the CoDecs is merely a byproduct of the use of the products, but not per se an intended workflow outside of those and, which is the more important part, also not explicable as a causal circumstance of the quality. If I may be so bold: What you are saying sounds like everyone would be using the Animation CoDec because it is so good, when the simple fact is that there are no decent free cross-platform alternatives and people are willing to accept limitations because of that. Don't get me wrong, ProRes is well designed and pretty robust, but the world doesn't come to an end without it and outside the Mac world it is difficult to deal with. Hell, it's even difficult to deal with between different versions of FCP occasionally...
Mylenium
I have been testing codecs for a long long looooooong time. My criterion(s) are:
1) Image Quality and that through multiple encoding generations and color grading
THEEEN
a looooong way down the road
2) Performance
BTW - I find that working with files less compressed and thus HUGE is much better. Hard drives are so cheap that one can build himself an 8 Disk RAID0 and that takes care of everything. In PPRO I can cut real time in FulRes with an uncompressed codec with the processors maxing at 3% while the H264 editing sequence will stutter like a drunken wasp and maxing the CPUs at 63%.... Go figure...
ProRes 4444's impeccable imageQuality:performance ratio, is unbeaten.
Especially on H264 material like that of the Canon5D. You might say if the source is 4:2:0 why bother upping it to 4444... Well in theory perhaps
it is overkill. But rather than reading in theoretical white papers I conduct my own tests. And the end results are (REALITY) and way different from what theory states. TO anyone reading this. DONT believe ANYTHING you read about codec nor what I am saying.... DO YOUR OWN TESTING and judge for yourself. Problem is that you have to do 100's and 100's of transcodings with ONE source to various destinations with lost of grading and transcoding generation. THEN you have to keep track of your tests and THEN compare them. It takes WEEKs. But it is well worth while it. In my case... I start with a Canon5DMKII H264 movies. Transcode it to PRORES4444 then I do LOTS of compositing and re-encoding then lots of color grading etc etc etc. Then I export back to H264 - and the end result is STUNNING has NO artifacts and is adorable to look at. Not so with at least 6 other codecs claiming to be top-notch....
Sure Mylenium, the world would NOT end with PR4444 not in it... BUT the WORLD has ALREADY decided that it WANTED ProRes4444 in it. It is growing and that every day..........
Had the codec not been so darn excellent - it would NOT have been used. Period.

Photoshop CS6 random color shifts

Here's the lowdown on my system/machine:
Photoshop CS6 (version 13.0.4)
Mac platform, OSX (version 10.8.4)
2 x 2.4 GHz Quad-Core Intel Xeon
I'm having problems with color shifts in a batch of images from a common Photoshop document.
I make 28 images from a single file, think of it like a picture frame where the frame doesn't change but the art depicted in it changes.
Since they come from the same Photoshop document they all have the same profiles and settings, they are all the same size and the frame should never change color—but it does.
Therein lies the problem.
A color shift in the art wouldn't really be noticable since the art is different every time. The frame is the same across all the images and the shift is obvious in the frame.
We use an Applescript to speed up the process; The script turns on a layer, flattens the image, then saves it out as an EPS for placement in InDesign, reverts to the layered version, then turns on the next layer and repeats the operation.
Of the 28 images, 3 of them have a noticable color shift.
It's never the same images that shift, it's just a random assortment that are effected (right now it happens to be 3, the next set of images may have more or it may have less).
Here's a screen shot of the color build in a specific location on sample 1:
Screenshot of the color build in exactly the same location on sample 2:
Here's a screenshot of the effected files in the directory (those highlighted in green are shifted):
Has anyone else seen this?
After some basic file analysis:
The shift occurs when the person working in the file creates a new document and copies the existing components from the master file into the new file.
I'm still confused since it's done on the same machine, with the same color settings/profiles, by the same person. It is still random.
BAD

Okay then. I mean when I use the Eyedropper Tool on the color that I had already put on a picture, the color becomes darker than what is shown when I use the Brush tool.
Like when I put light red as the foreground color, then switch it out for another color, then used the Eyedropper tool to copy the light red color to use it again, the light red color instead becomes a slight darker red when I use the brush or other related tools I use to color in my picture.
Hope this detail is clear enough.

Color "shifted" in CS4 RAW files

Hello everyone.
Ill try to explain my problem. Until last year I used ACR (combined with Bridge CS3) to color manage my images. Then I would convert them to DNG using the Adobe DNG Converter, and bring them into iMatch (www.photools.com), which is the program I use to manage my image database. I would work with a calibrated monitor, and a sRGB color profile.
The DNG images would look the same in Bridge and iMatch, and if I extracted the JPG preview from any DNG image it would also look the same.
This year I bought a new laptop and a CS4 license (previously I was doing the CS3 work using a license from the place I work at). Ive calibrated my laptop screen with a Pantone Huey Pro screen calibrator.
When I open my images in CS4 the color in all of them looks "shifted", as if the white balance was off. They look consistently greenish and somewhat washed out. This happens in Bridge, ACR and Photoshop.
However, if I open any of the JPG images (the ones that I created extracting the preview from the DNG files) they look the way they should. So from this I can infer that it can't be a screen calibration problem (otherwise both the JPG and its DNG counterpart would look wrong, instead of just the DNG).
So it seems like CS4 is rendering the DNG images differently than it should. But I havent been able to find out how to correct the problem.
Some other info: In the ACR flyout menu I have Image Settings selected, and under the Camera Calibration I have Embedded selected. Ive already tried (at the suggestion of Adobe support) to reset the Bridge preferences by holding CTRL+Shift when Bridge loads, but this hasnt corrected the problem.
Also, here are my system specs,:
- Precision M6400: Intel Core 2 Duo P8600(2.4GHz,1066MHz,3MB)
- Display : 17in Widescreen WUXGA (1920X1200)
- Memory : 4096MB (2x2048) 1067MHz DDR3 Dual Channel
- Graphics card: 1GB NVIDIA Quadro FX3700M (with 1GB dedicated memory)
- Hard Drive : 200GB Serial ATA (7200RPM)
- Operating System : WXP Pro SP3
I have already contacted Adobe support about this a few days ago, but so far no luck. So I thought Id try the forums as well and see if anyone here has any theories as to what the problem could be. Im stuck until Im able to solve this, so any help would be appreciated.
Thanks.

Hello,
I'm still having trouble with this same issue, wondering if anyone has further thoughts.
I've read some of the similar threads, like: http://forums.adobe.com/message/1203718 and http://forums.adobe.com/message/1203965
But I'm still confused.
I hadn't noticed the color shifts in Bridge being so pronounced until recently. So maybe something got inadvertently reset?
It would be a bad idea to change my computer's color profile to generic sRGB (as someone suggested), since I have a good calibrated color profile via the Gretag MacBeth (yeah, it's older) EyeOne Display. I've used that calibration device for years, updating every 6-12 months. Never been a problem.
It doesn't make any sense to me that Bridge should alter the colors of thumbnails/previews for RAW images (from the very good looking camera setting) before I even open Camera Raw to work on the RAW images. I don't work on every single RAW image, and doubt anyone does. But if I have 50 landscape shots, and the mere act of looking at their previews in Bridge turns all their skies unnaturally purple (which is currently happening), I lose any visual record of what the skies really looked like -- or at least a much closer approximation.
My Canon 40D's jpg previews for RAW images are quite good when they initially show up in Bridge. I'd really like to keep them until I work in Camera Raw, to give me a good visual memory starting point until I can get to work in ACR. Sometimes I don't start serious work on an image for many months after shooting.
Someone please correct me if I'm wrong, but it also doesn't make sense to me that a solution is to make a new Camera Raw default based on a photo I've worked on in ACR, because the color settings always depend on the lighting situation a photo was taken in, don't they? How could a daylight photo's settings be right for an indoor or sunset shot with totally different lighting and color temps?
Bottom line question: Is there any way to prevent Bridge from altering the color in thumbnails/previews of RAW images before you've worked on the images in Camera Raw? (Even if you click on a thumbnail to see the preview in Bridge, I mean.)
Thank you very much!!!
~Glenn
Message was edited by: glennooo - for clarity and to fix a link

Menu colors shift after build

Similar Messages

Maybe you are looking for