Quicktime 7.1.5 Update Fixes Color Profile Bug

You'll be glad to know that the latest Quicktime update, 7.1.5, that was released yesterday fixes the bug that prevented iPhoto 6.0.5 from importing or using/editing image files that did not have a color profile embedded in them.
However, users using Photoshop or Photoshop Elements should still set those applications to manage and embed an RGB profile in files so that when printing prints or ordering books/prints/calendars/cards ordered thru Apple they will have an accurate color rendition of what you see on the screen.
Do you Twango?
G5 Dual Core 2GHz, 2G RAM, 250G HD; G4 Dual 1Ghz, 1.5G RAM, 80G HD, QT 7.1.3, Mac OS X (10.4.8) 22 LCD, 250G/200G/160G FW HDs, Canon: SD700IS/i850/LIDE 50, Epson R200, 30G iPod

Yes it is. I ran several files thru PS, removing the profile, and they imported into iPhoto OK. I just ran another test (no profile in the files, edited in PS and saved w/o profile, iPhoto set to not embed a profile) and it worked as advertised. The files were editable by iPhoto and viewable in the full screen mode.
Interesting in that the resulting modified file ended up with a profile embedded even though iPhoto was set not to. Haven't figured that one out yet.
The bottom line is that it works as advertised.

Similar Messages

Colorsync fail to fix color profiles under Adobe folder

Any suggestions how do I make it fixed?
Searching for profiles...
Checking 65 profiles...
/Library/Application Support/Adobe/Color/Profiles/RedBlueYelllow.icc
   Tag 'pseq': Required tag is not present. Could not be fixed.
/Library/Application Support/Adobe/Color/Profiles/Smokey.icc
   Tag 'pseq': Required tag is not present. Could not be fixed.
/Library/Application Support/Adobe/Color/Profiles/TealMagentaGold.icc
   Tag 'pseq': Required tag is not present. Could not be fixed.
/Library/Application Support/Adobe/Color/Profiles/TotalInkPreview.icc
   Tag 'pseq': Required tag is not present. Could not be fixed.
Repair done - 0 out of 4 profiles fixed.
Thanks,

I think I found the problem..
Colorsync somehow opened an image I downloaded from (123rf.com) and kept the application open in my application bar at the background.
I think that caused the hustle.
After quitting Colorsync - problem solved.
Thanks for your help!

Display color profile bug when using the fast account switch from a guest account to an admin account (and vice versa)

Hey,
I'm sometimes using a guest account on my MBP (unibody late 2008 2,4 GHz Core2Duo, 4GB DDR3 running OSX 10.9.4 on an OCZ 128GB SSD) for a more distraction-free working space and I noticed right away a disturbing bug:
Using the fast account switch (upper right hand corner of the screen) in Mavericks from an admin account to log into a guest account (or vice versa) produces, after the fancy rotating cube animation, some strange distortion of the desktop background happens (lasting approx. 2 sec.). After that the color profile of the display is changed into an usable but ugly one, which is disturbing while working with pictures. When checking the color profile in the pref pane, the standard "display" profile is said to be active (it's the one I use) but still the colors aren't the same. Selecting another profile and re-selcting the desired one doesn't fix the problem. Switching back to the other account with the fast switching leaves the colors altered. Logging out and deleting the guest account seems to the problem for the remaining admin account. Rebooting and logging in to either of the accounts (admin or guest) from the standard account selecting page at booting shows the normal color profile.
Is it a general bug or is their anything a can do to prevent this problem (other than never using the fast switching)?
Thanks for your advice.
Mael

I cannot agree more with your comments! What a way to frustrate your customers!
I have been having an issue with iCloud on Mac where it kept asking me for my password and sometimes would, sometimes would not continue to access my iCloud mail. Today it just refused to connect to iCloud mail.
I looked in the Mail, Contacts and Calendars in my MacBook Pro settings and discovered that 2 iCloud accounts were present. One with my original Apple ID (a gmail address) and a second with my new iCloud email ( an @me.com address). Having deleted the second account, using the new @me.com address everything is working fine.
So from my viewpoint when I moved over to iCloud I was asked to sign in with my Apple ID (the gmail address) then to create an @me.com address. However, as far as I can see all sign ins to the new @me.com account on Macbook, iPhone and iPad need to be done through the old Apple ID (the gmail address). Is that confusing and just plain crazy???
Further, after creating the new @me.com address I soon found out that this is apparently now forever bound to my old Apple ID and cannot be changed. I mean why can't I delete the iCloud account and start anew with a different @me.com address??? Also, as everybody using iCloud must create an @me.com address why on earth can I not get rid of my old gmail address and have my entire Apple ID accessed through the new @me.com address? Creating a whole new Apple ID will not solve this as we are unable to transfer purchases between accounts.
Apple products are great IMHO, but they do seem to not think things through in a very big way sometimes......

Aperture 3 embedded color profile bug still unsolved (worked in Ap 2)

RE: Aperture 3.x cannot display images with certain color profiles embedded. This bug was reported
on March 11, but is still unsolved and basically makes Aperture 3 unusable for my large collection
of scanned slides which have a special color profile embedded. Viewer and sometimes Browser turns
either black or go haywire.
What is it about:
When you scan slides with a scanner, you can generate a special color profile so that the image
looks good and you can then embed this profile in the scanned tiff and jpeg images. Most pro applications honor the embedded profile and display the image correctly. In our case, we
generated a special profile named Nikon-LS5000 (it was tested for correctness!):
1) It worked fine in Aperture 2.x
2) It never worked in Aperture 3.x
3) It does not depend on the Operating System (i.e, the bug manifests itself in 10.6.2, 10.6.3 and now in 10.6.4)
4) It is no question of a special Mac Model (the bug shows on iMacs, ibook profs, and iMacs 2010)
5) It is irrelevant whether you start Aperture 3 in 32-bit or 64-bit mode
6) It shows with jpegs or tiffs, no matter
7) Preview.app or Photoshop CS4 display the images correctly!
8) If one changes the embedded profile via PS CS4 to sRGB or ProPhoto, Aperture 3 works (but the
image then has radically different colors - so no solution!)
9) The conclusion is that something affecting the processing of (some?) embedded color profiles has radically changed from Aperture 2 to Aperture 3.
I put a few jpegs with embedded color profiles and screenshots of how Aperture 3 behaves on the Picasa web:
http://picasaweb.google.com/114939413495021552399/TestapertureBilder#
you are invited to download the jpeg- images and retry in your ownAperture 3 Library.
Maybe together we can find out what causes this bug which is very annoying for any
serious photographer.

I have put the test material on another server - you can download a
zipped folder (Aperture3profilebug.zip) of all test images AND the color profile from
https://depot.uni-konstanz.de/get/txau69
with any browser. (The problem was that the Picasa Software seems to strip the color profiles from
the test images, so I had to put them on another server. It will remain there until July 1).
Regards and thanks for helping

Quicktime 7.1.1 update fixes whine?

I have a Week 11 MacBook Pro (15.4" 1.83GHz) that had the CPU whine. I strayed away from the Keyboard & Mouse Update and used the Mirror.widget start-and-close trick to remove the whine. Once the whine was gone, it would not start up unless I ran the camera again, or until I rebooted.
After installing the Quicktime update (out since a couple of days ago), I haven't noticed any CPU whine.
Is this it? Is this the software update that repairs one of the most nagging problems of the MacBook Pro line?
I'm tempted to try installing the Keyboard & Mouse update now to see what'll happen.

I have a Week 11 MacBook Pro (15.4" 1.83GHz) that had
the CPU whine. I strayed away from the Keyboard &
Mouse Update and used the Mirror.widget
start-and-close trick to remove the whine. Once the
whine was gone, it would not start up unless I ran
the camera again, or until I rebooted.
After installing the Quicktime update (out since a
couple of days ago), I haven't noticed any CPU
whine.
Is this it? Is this the software update that repairs
one of the most nagging problems of the MacBook Pro
line?
I'm tempted to try installing the Keyboard & Mouse
update now to see what'll happen.
Though I don't think you're lying, you may be experiencing something that happens to many of us.
For SOME reason, I don't know what, after I receive Apple Updates computer noises diminish somewhat for a short period of time. I have lost my screen inverter whine and processor whine to many updates, for it to come back days later. Some other people have reported improvements after some updates too.
It may have to do with the updates requiring "restarts" you know when you restart and it takes an exceptionally long time to reboot? Maybe something is being reset that decreases our noise symptoms, but reappears after repeated use.
I don't know the answer, all I know is that I'm still happy with my MBP, I wouldn't trade it for any other computer, but when they have a permanent solution for all of the problems, I'll be right there in line with everyone else to get them fixed!

I know there is a bug with the new firefox 3.6.14 and how Java operates. I've un-installed 3.6.14 and re-installed 3.6.13 Does the Firefox Beta 4 have the prob that 3.6.14 has? When will firefox updates fix this Java bug?

Under tools options for the 3.6.14 there is no tab to enable java, only java scripts. There was an add- on for Java that automatically downloaded that may be part of the problem. I' also updated to Java 1.6.0.24,- is that may be part of problem. The Pogo.com website will not load certain games.
My biggest question is whether the Firefox beta 4 is safe(er) to use, and/or does it have other and perhaps worse bugs that have not been worked out.

Firefox 3.6.15 fixes that problem with Java.
Use Help > '''Check for Updates''' to get 3.6.15.

GT70 Monitor Color Profile (Chi Mei 173HGE)

In case some people one to fix color profile for their GT-70 Monitor (Chi Mei 173HGE)
Someone from different forum using same monitor had fixed that for us, and I like the 7500k version.
Just make sure you enable Use Windows display calibration in
Control panel > Color Management > Advanced > Change System Defaults > Advanced > Use Windows display calibration
The link is :
http://rog.asus.com/forum/showthread.php?36153-Personal-Color-Profile-for-the-Chi-Mei-173HGE
Make sure you have same monitor.

Editors' Choice Award. Good job MSI !!
http://www.computershopper.com/laptops/reviews/msi-gt70-dominator-893#review-body

Will QuickTime 7.1.5 (released TODAY) fix the ColorSync Bug?

I just read on the iDVD forum that QT 7.1.5 was released today. Sure enough, it showed up on my Software Update! Can anyone test iPhoto 6.0.5 with QT 7.1.5 on a PPC Mac to see if it corrects the color profile bug?
or am I only dreaming?

Ha ha ha.

Have i found another big bug? from 2nd monitor profile bug to Exp panel bug

Well 2.0.1 is out and i was hoping for a fix for the second monitor color profile bug ... but no, not yet.
But guess what .. i think i have found another little treat.
Ok here we go, click on the Exposure, Recovery or Black Point sliders (but don't move them), notice anything?
On my system as soon as you click, the shadows block up. Take your finger of the button and they shadows go back to normal.
Next .. click and slide, when the button is down... blocked shadows again, release the button and shadows open up.
This also happens in the White balance panel.
Also we still have the tint slider problem, click it and it jumps the tint.
The exposure and white balance problem only happens in full screen mode.
It happens on my second monitor when running in mirror or alternate (or any other of the settings)
If i press the F key and go full screen on my macbook pro, the same thing happens on the macbook's screen.
Press the Z key to zoom to 100% and the problem goes away on either screen.
But get this ..... click any of the sliders in the Enhance panel before going to the Exposure panel (you don't have to move them), then go back to the exposure panel and...EVERYTHING FINE.....whaaaaaaat.
So now i have a second monitor with dodgy colors and an exposure panel glitch.
Thought this was an update!!!
Anyone else got this problem?
Oh, just to add, i have deleted pref files, deleted aperture altogether, re-installed 2.0 and 2.0.1, rebuilt library, tried on another library...all with no joy.
Sigh
Mike
rebui

System is macbook pro 2.4 4gb ram, formac 2010 second monitor.
Leopard 10.5.2
pro app 4.5
Seems that i am not the only one with this problem, not many out there... just a few.
Couple of links
http://forums.dpreview.com/forums/readflat.asp?forum=1017&thread=27043649
http://www.flickr.com/groups/aperture_users/discuss/72157604042773520/
Mike

Quicktime/iTunes Full Screen Color Profile Issues?

I'm running Yosemite now, but this has been an issue long before I upgraded from Mavericks as well. The default color calibration in OSX is overly bright and blown out on my monitor, so I have a custom calibration set up and in use on my Mac Mini. The profile I created looks great for general viewing, movies or anything else I want to do.
However...there seems to be an issue with Quicktime in either the app itself or when playing a movie from my iTunes library. If I play a movie in a window there are no issues, but the problem comes when I play a video in full screen mode. The color calibration looks just fine UNTIL the play controls automatically disappear from the screen. That's when it seems to go back to the default color profile that's blown out and muddy looking. Move the mouse so the controls come back up, color profile goes right back to the one I have set....until they go off the screen again, when the default profile is back.
Anyone else experiencing this and maybe found a workaround or way to fix it? I've found a couple mentions of it on the web in forums, but no answers or even replies were ever given.

Me too and it's very annoying. Exactly the same symptoms of the colour changing when the fullscreen controls disappear.
I've used a colormunki to create a custom profile for my monitor for photoshop use. Has everyone else done something similar?
I created the profile before Mavericks & Yosemite updates so I might try deleting it and creating a new one to see if that helps.

IPhoto fix that worked for me (Coregraphics & Adobe Color Profiles issues)

Ok, I posted a few days back in reference to getting help with my iPhoto. I do apologize on the fact this is quite the long post but maybe it will be easy to understand for those who are like me and not all that computer literate. I searched all the discussions and used all the different advice from different people but had no luck. I was able to FINALLY get iPhoto up and running again last night after doing just a few simple things. Please note that this may not work for everyone. Also please note that I AM NOT an expert in dealing with computers and working with computers. It's just that my ADD kicks in when something needs fixing and I won't stop till its finished. Below are a few lines from the crash report that I was getting each time I attempted to open iPhoto from my Macbook Pro Late 2011 running 10.8.3.
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000024
VM Regions Near 0x24:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL /Applications/iPhoto.app/Contents/MacOS/iPhoto
    VM_ALLOCATE            0000000000001000-0000000000055000 [ 336K] ---/--- SM=NUL
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreGraphics                  0x9678ec6c color_space_create_adobe_rgb_1998 + 28
1   com.apple.CoreGraphics                  0x9666dd70 CGColorSpaceCreateAdobeRGB1998 + 32
2   com.apple.CoreGraphics                  0x9642b46b CGColorSpaceCreateWithName + 652
3   com.apple.geode                         0x01079d4a +[DGColorSpace initialize] + 1018
4   libobjc.A.dylib                         0x90267600 _class_initialize + 305
5   libobjc.A.dylib                         0x902674c8 prepareForMethodLookup + 78
6   libobjc.A.dylib                         0x90267337 lookUpMethod + 81
7   libobjc.A.dylib                         0x902672e1 _class_lookupMethodAndLoadCache3 + 47
8   libobjc.A.dylib                         0x90266ac1 objc_msgSend + 81
9   com.apple.geode                         0x010798a0 +[DGContextMgr newBitmapContextCached:accelerated:] + 61
10 com.apple.geode                         0x0107985e +[DGContextMgr newBitmapContextWithAcceleration:] + 49
11 com.apple.RedRock                       0x02647bf6 -[Godot loadGeode] + 1261
12 com.apple.RedRock                       0x026448a8 -[Godot init] + 1571
13 com.apple.RedRock                       0x026437d2 +[Godot initGodotApp] + 108
14 com.apple.iPhoto                        0x00083be8 0x55000 + 191464
15 com.apple.iPhoto                        0x0008236b 0x55000 + 185195
16 com.apple.Foundation                    0x9a3bc4cf __NSFireDelayedPerform + 413
17 com.apple.CoreFoundation                0x95ed1416 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22
18 com.apple.CoreFoundation                0x95ed0db5 __CFRunLoopDoTimer + 709
19 com.apple.CoreFoundation                0x95eb5bc2 __CFRunLoopRun + 1842
20 com.apple.CoreFoundation                0x95eb502a CFRunLoopRunSpecific + 378
21 com.apple.CoreFoundation                0x95eb4e9b CFRunLoopRunInMode + 123
22 com.apple.HIToolbox                     0x9052af5a RunCurrentEventLoopInMode + 242
23 com.apple.HIToolbox                     0x9052abf5 ReceiveNextEventCommon + 162
24 com.apple.HIToolbox                     0x9052ab44 BlockUntilNextEventMatchingListInMode + 88
25 com.apple.AppKit                        0x923c39aa _DPSNextEvent + 724
26 com.apple.AppKit                        0x923c31dc -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
27 com.apple.AppKit                        0x923b963c -[NSApplication run] + 855
28 com.apple.AppKit                        0x9235c666 NSApplicationMain + 1053
29 com.apple.iPhoto                        0x00064c99 0x55000 + 64665
30 com.apple.iPhoto                        0x000642e5 0x55000 + 62181
-Run and attempt to repair any Color Profiles that may need to be fixed. There were 4 that could not be fixed for me. Locate these profiles and move them to your desktop (Note: I was still able to open and use all applications in my Adobe CS6 Master Collection after moving these profiles but you may want to check just to be sure if you are using Adobe).
-Even though I had done this many times, run the Disk Utility App in your Utilities Profile and Verify and Repair any permission needed (For me, I had none at this time that needed to be repaired).
-Next, I did an Apple Hardware Test. For me and the model Macbook Pro I am using, I had to restart my computer and when the screen went black for me at restart about the time the start up sound is about to come on, I pressed ALT-D. On some models you just have to press D. I did disconnect everything prior to doing this except the power cord and the Internet. I did a full AHT test that took about an hour or so. If you get an error code, be sure and right it down whereas your issue may be something different than mine and this will not apply to you. There were no problems from the test and then restarted the computer.
-At restart I decided to get into the OS X Recovery by pressing Command-R to either start from scratch or find some other way to fix the issue because I was tired of racking my brain on this and was about to throw the computer in to the wall.
http://support.apple.com/kb/HT4718 For help or questions on the OS X Recovery Process
-Once in the OS X Recovery from the Mac OS X Utilities Pane, I selected reinstall and then I selected my current Hard Drive. Luckily by doing this (not that I was aware or anything, but none of my files or folders were deleted and it only reinstalled Mountain Lion and whatever else it needed)
-This process took about an hour and once finished, I restarted my computer
-I logged back in to my account but did not attempt iPhoto at this time. Instead I immediately checked to make sure that 10.8.3 was what was reinstalled back on my Mac. I then checked for Software Updates which I had a few and installed these updates.
-I then went back to the Disk Utilities App from my Utilities folder and Verified the Disk and Disk Permission. To my surprise, many of the files that were in the iPhoto crash thread (posted above) were now showing up as needing to be repaired. I repaired what needed to be repaired.
-I verified all my Color Profiles to make sure none were showing up again (which there were none that needed to be repaired)
-I did a check check of some Adobe CS6 Apps just to verify they were opening and working correctly
-I restarted my Mac (Once again) and logged back in. I opened up iPhoto and everything worked and is working PERFECTLY. I then re-connected my printers and my Time Machine and performed a back up before importing photos back in to iPhoto. I DO WISH NOW THOUGH THAT I HADN'T DELETED AND RE-INSTALLED IPHOTO but it is nice being able to start over and organize iPhoto a little better than before.
I am sorry this is such a long post but for people like me who are not professionals in the computer department, sometimes it's good to "dumb" things done so that us "average joes" can understand a little better. Hopefully this will work for those who are having issues like mine. Thanks for all the help from everyone from my previous posts.

Tom:
To help prevent loss like you experienced see the tip at the end of my signature.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto 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 written an Automator workflow application (requires Tiger), 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 08 libraries. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Print driver/color profile problems after 2.0 update

Since I updated to the latest version of aperture 2 I have had problems with printing on my canon 5200R printer. The coloring is way off, as if aperture does not seem to recognize the canon print drivers or color profiles. I have read about printing from another program but was so happy with color quality using aperture 1.5, is there a fix for the current problem?

Bump.

Weird color profile problem after SMC update

Although I've managed to resolve this particular problem, I wonder if anyone has suffered the same thing.
Software update says that I should do the firmware update, so I did that yesterday night. Also, at the same time, I went and removed MS Office 2004 Test Drive (it was taking up space for no good reason). Sometime after doing those things, it seems like OSX had lost the display color profile. The only ones I've got was the Adobe one, Generic RGB and sRGB. The generic RGB washes the screen with a blue tone, and clicking on Calibration would merely have the ColorSync utility complain about the profile isn't there.
Looking at the knowledge base, it says that after the 10.4.8 upgrade, the screen may look bluer than before. The curious thing was that my Macbook reported it running on 10.4.8 when I first got it. But anyways I downloaded 10.4.7's LCD profile, and put it at the location specified in that knowledge base. Display preference still didn't pick up on the profile, so I end up restarting the machine, and now it seems to be using a profile called "Color LCD".
I'm wondering if anyone else have experienced something like this, and going to document this here as a possible solution if someone is lost after a random deletion of a color profile....
Macbook 13" Mac OS X (10.4.8)

I had something similar happen when I upgraded to 10.4.8. In fixing the blue tint problem, I loaded a backup copy of the Color LCD profile. Subsequently, under exact circumstances I don't remember, the machine "lost" the profile. And the calibration option would just give an error.
So somehow, after further fiddling, I ended up with two copies of Color LCD profile, one the old 10.4.7 one, one the 10.4.8 one. I haven't had the problem of it losing the profile again.
But I might mention that there is a related problem which you may encounter. If I use fast user switching with another account and return to my (admin) account, the blue tint returns. The workaround is as described in this article:
http://www.macworld.com/weblogs/macosxhints/2006/02/fuscolor/index.php
I have created an alias to the DMProxy application as described in the above article, and have to run it after every time I use fast user switching.

Quicktime Color Profile wrong

I'm trying my best to understand what is happening with the gamma shifts in Quicktime, and any help is appreciated.
So far I've found: Exporting Quicktime content automatically assigns it the "HD" Color profile and does not use the gamma tag. The "HD" profile seems to be HD 709-A and appears to have a gamma of 1.96. Please allow us to tag the files with the colorspaces/gamma that were used to create the content. I'm working in a color space calibrated to 2.2. Macs these days also seem to come set to 2.2. Unfortunately this seems to cause a brightening after exporting content.
Furthermore, there seems to be inconsistencies between how QT and FCPX handle the "gama" flag. QT seems to follow it which is great when editing with a third party utility, where FCPX ignores it which is all the more frustrating.
I think it's wonderful that we are getting closer to fully color managed workflows for video, but it's incredibly confusing to be forced into assigning a color profile that has nothing to do with how it was created. Please help. If at the very least FCPX would honour the "gama" flag, that would be amazing.

To Apple Discussions!
I'm sort of confused by what you mean by:
"I get wrong color in Quicktime"
Are your movies & videos coming out in the wrong colors?
Which version of QT are you using?
See if repairing permission using your Tiger DVD helps.

Printer adds blue, how do I fix this? color profile? calibration?

I have an HP 3210 printer and iphoto 06.
When I make a copy of a picture with the printer in stand alone mode, the copy is almost an exact.
When I scan the photo into iphoto and print it, the printer seems to add blue.
How do I fix this?
Can I create a custom solor profile or something to get it right?

Patrick:
First, you did check your ink cartridges to make sure you're not out in any of them? Duh. Make sure your monitor is calibrated. I use sRGB as the profile and adjust the brightness to make up for the aging monitor. Setting the gamma at 2.2 will help with just darkness.
Do you have iPhoto's Advanced preferences set to Embed Color Profile? Not sure what would cause too much blue but in the Advanced printer settings under the Copies and Pages menu there are a couple of sections that you can use to adjust the print settings; Color Option and ColorSync. Create a new setting under the Presets menu and save those settings before each trial so that once you get what you want it will be easy to just select that preset and print.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto 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 written an Automator workflow application (requires Tiger), 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 08 libraries. 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.

Quicktime 7.1.5 Update Fixes Color Profile Bug

Similar Messages

Maybe you are looking for