Snow Leopard 10.6.3 - Colour Management Fix ?

MacFixit has posted an article about the beta release of Snow Leopard 10.6.3.
http://reviews.cnet.com/8301-13727_7-10456820-263.html?tag=mostDis;di
Intriguingly, the article lists one "focus areas from this build" as:
•   Improves printing reliability and compatibility with 3rd party printers.
Could this be the fix for printing non-colour managed files we are all hoping for ?

Hi Doyle.
You have but a short memory !
Can I suggest you go back and read all the posts on this and the Luminous Landscape sites.  This will disabuse you of the notion that the issue only effects "some Epson drivers".  At the present time I can categorically include Canon in this, there is some evidence (on web postings) to suggest that HP printers are effected, it clearly effects colour profiling software from Colorvison and X-Rite – and, I would suggest, (from what I have read) that most if not all Epson drivers are thus effected.
We all know that you say that your Canon printers can do no wrong but sadly this is not the same story for the rest of us unlucky users.
It is unclear whose problem it is (as no one has yet owned up) but the evidence would seem to suggest that it is common to all printers and profiling software that are using untagged files (files with no profiles) and need no colour management in the printing path.  Adobe have stated that Apple changed the printing APIs and that the new printing path "will not permit" files without a profile attached.  From here on in it appears that ColorSync (part of the Mac OS) starts introducing errors by attempting to colour manage the un-tagged file in some undiscovered way.  Thereafter the whole thing becomes a mystery – and no one really knows what the printer makes of it all !  My observation is that the results always seem to be the same, a file which is printed too dark - once again suggesting a common denominator.
Will 10.6.3 fix this ?  We will have to wait and see.

Similar Messages

  • I have a macbook os x snow leopard, but by accident I managed to Loaded os x lion. Is it depends to undo?

    I have a macbook os x snow leopard, but by accident I managed to Loaded os x lion. Is it possible to undo?
    I got the Mac in August 2010 and is 10.7software original.
    Thank you in advance!

    Check out this previous message thread.

  • Snow Leopard Strange behavior, best stategy for fixing?

    I have noticed recently a series of issues. It started when one of my computers starting getting Mobile Me sync errors. These seem to have gone away, but the computer that was having these errors now has several odd, but not, at this point critical problems.
    Whenever I open iTunes I get the license agreement, I click Agree and the next time I get the same agreement. If I remove or move anything in my Dock, the next time I launch it is returned to it's previous state with Icons back where they were. Sometimes I try to move a file and get the admin Log In requirement. Other times, no problem. It doesn't seem like much, but it appears like there might be something brewing. I have Run Techtools 6.0.3 and disk utility and it comes up clean. I have run disk permission, I have upgraded SL to 10.6.8 v 1.1. I have reinstalled SL from the disc and upgraded. I have upgraded iTunes.
    Still have the same problem. Is there any permissions fixes, such as changing a folder permission I can do without a clear wipe of my boot drive and a full install of all my apps and settings?
    If I do have to upgrade, is there any ideas as to the most efficient way to get all the apps and settings restored.
    Message was edited by: Mark Wheaton

    Since not getting a response I used disk Utility several times to repair permissions, Used TechTools 6.0.3 and found nothing wrong, used Diskwarrior 4.3 found numerous .plist corrupted files. No real way to tell it to just move these to a temp folder and see what happens, but I think there are corrupt hidden root level files that are causing my issues, so unless I hear suggestions, I am moving to a fresh install on another drive. I am keeping this drive until I knwo everything works right and then erase and use it for file storage.
    If any quicker fixes are out there I would love to hear them.

  • Colour Management Issue with PS CS3 and Leopard 10.5.2

    Hi Everyone,
    Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
    My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
    Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
    Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
    Any ideas?
    Thanks.

    >It was working perfectly in Tiger with the monitor profile.
    You were lucky.
    the monitor profile is so Photoshop can display your images correctly.
    the working space is Adobe RGB, sRGB, BruceRGB, ect... these are all known color spaces so when the file goes to another computer there is a consistent color space for reference. If you use your monitor profile as a working space then nobody else knows what is going on with your file.
    when you print you need to use the printer profile for the type of paper you are printing on this is supplied by the printer manufacturer. you can also have custom profiles made.
    you need to read up on color management:
    http://www.gballard.net/psd.html
    http://digitaldog.net/

  • Colour Management issue With Leopard and PS CS3

    Hi Everyone,
    Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
    My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
    Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
    Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
    Any ideas?
    Thanks.

    You need to use the correct printer profile for the paper you're using. If the printer didn't come with any pre-built profiles, check Canon's web site to see if they have any profiles available for your printer that you can download.
    Printer profiles are very specific. You can't take take a profile for glossy Epson paper and expect it to work very well for Canon glossy paper.

  • Colour Management Issues with Leopard and Photoshop CS3

    Hi Everyone,
    Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
    My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
    Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
    Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
    Any ideas?
    Thanks.

    I'm having exactly the same problem, only my printer is a Canon Pixma iX4000. The colour is all bleached out, it looks exactly like when you've accidentally printed an RGB file on a CMYK printer, and at first I thought that was what I had done, but it isn't. This is very frustrating, I've spent all day going through the manuals, recalibrating etc, but no luck. This is a brand new Mac Pro and printer, but if its not going to print what I see on screen it's just expensive junk.
    I wasn't sure if the problem was Leopard or the printer or CS3...

  • Possible fix for Adobe PDF plug ins (Safari & Print) on Snow Leopard

    I think I just discovered a "fix" for the Adobe PDF problem, as well as for some other miscelanious problems with Snow Leopard applications. I found the fix for the plug in from PDF on Adobe's website. http://kb2.adobe.com/cps/509/cpsid_50983.html
    Following these directions (changing the option from 64-bit, to 32-bit when the application loads), seems to have cured the plug-in for PDF from Adobe and loads the plug in properly.
    There is a link, http://kb2.adobe.com/cps/512/cpsid_51248.html for changing the settings similarly for Automator to fix the "save as PDF" in Print.
    I've also applied this "suggested fix" to Mail and Address Book, to see if it remedies some of the continued glitching and crashes on my iMac, even after the latest update (10.6.1). No problems with my PBG4, as it's not Snow Leopard nor Intel.
    Hope this solution is useful.

    I am having the same problem from CS4 Illustrator
    cups/error_log shows:
    D [10/May/2010:10:53:31 -0700] [Job 87] Opening Distiller
    D [10/May/2010:10:53:31 -0700] [Job 87] Starting Distiller job
    D [10/May/2010:10:53:31 -0700] [Job 87] Distiller child 26366, exited with status 0
    D [10/May/2010:10:53:31 -0700] [Job 87] End of messages
    D [10/May/2010:10:53:31 -0700] [Job 87] printer-state=3(idle)
    D [10/May/2010:10:53:31 -0700] [Job 87] printer-state-message="/usr/libexec/cups/filter/pstops failed"
    D [10/May/2010:10:53:31 -0700] [Job 87] printer-state-reasons=none

  • Snow Leopard 10.6.2 recommended for Adobe Fireworks CS4

    The release of update version for Snow leopard by Apple is expected to fix some random crashes which have been encountered while working with Adobe Fireworks CS4.
    Once the Snow Leopard machine has been updated, the version should read 10.6.2
    Please go ahead and update your boxes to this update.
    ..Sarthak
    http://blogs.adobe.com/sarthak

    My experience is that there are certain .ttf fonts that are great in Windows but not at all compatible with Mac, and they can cause issues with software that uses fonts.
    Case in point:
    I have two PCs and a MacBook. I have virtually Identical software suites on them all (Office, CS4, PSElements, Full sets of browsers). I also have a font library of around 5,000 fonts.
    Until last month, I just ran them all from the system fonts folder.  On the PCs, this lead to slooooooooooooowwwwwwwww running in all of CS4 and Word in Office especially when I had to change a font.
    On the Mac, it kept Fireworks from launching altogether. It would just crash at the splash screen.
    Since I work from Time Machine and ghost backups, reformatting a hard drive and reloading everything is just an afternoon for me. I reloaded all three systems, this time with Suitcase Fusion to manage my fonts. It comes with FontDoctor to ID any bad fonts before setting up a library from the full set.
    On the PCs it ID'd about 35 bad fonts and I chose to eliminate them. On the Mac, it ID'd about 135. Again, I did away with them.
    End result: Office 2007 and the 2010 Beta are lightning fast now by comparison, and on the Mac, Fireworks is fully functional.
    Since the only thing I changed, was the fonts (removing bad ones from each system and using a manager to activate them) I can safely say that fonts will have an impact on your software.
    If FontBook ID'd them as bad, dump them. They'll likely cause more trouble than they're worth if you don't.

  • Time Machine to Snow Leopard not working

    Ok, so this issue appears to be multi-faceted so please bear with me as I try to fully explain what's happening.
    I have a mid-2009 Macbook Pro with OSX 10.6.8, and I decided to give Yosemite a try since it was free. Before upgrading, I did a Time Machine backup on an external 500GB WD drive in case I wanted to switch back to Snow Leopard.
    I did the upgrade, but wasn't very pleased with the results. Seeing as how the computer was older I figured it would slow down a touch, but what broke the deal was when I tried to run After Effects and had plugins - that never gave me trouble before - crashing. I decided to restore from Time Machine and rebooted into Recovery Mode. However, by accident I selected the External Drive with the backups as my boot disk. I quickly rebooted AGAIN and selected the Recovery drive, but the TM drive wasn't showing up when I tried to access it for the backup.
    I rebooted back to Yosemite and found that the drive was not mounting despite lighting up and making spinny sounds. Disk Utility could see it but was unable to repair, so I used DiskWarrior instead. Everything seemed to work out ok and the drive was reading on my desktop as a TM backup. I rebooted AGAIN to recovery mode, selected the appropriate backup, and let the computer do it's work overnight.
    When I woke up in the morning and checked in on it, I got an error message saying that the restoration had FAILED at some point along the way. I tried to reboot normally, but the grey screen of death would appear after a few seconds and I'd have to shut down.
    I went back to Recovery mode, tried to access the TM drive, but once again it was not showing up! So I reinstalled Yosemite and was able to login to my desktop. The TM drive was still showing up, and according to a reinstalled DiskWarrior the drive was fine. I rebooted in Recovery, selected the TM backup, and it only took about 20 minutes before the restoration failed! This time the computer appeared to be wiped clean, with no OS.
    Fortunately I still had my Snow Leopard install DVD, so I managed to reinstall it from there. However, now I CANNOT login. My username shows up but the password I've used for FOUR YEARS is constantly rejected. I can't even login to the GUEST account!
    If you've made it this far, PLEASE HELP!!!!

    Pondini - I have an issue too. And so I went to the troubleshooting tips you listed here and was not able to find a solution. Specifically, I don't get a message. I plain ole don't get nothing. After I installed Snow my first backup failed. Funny thing is the backup on my wifes computer also failed. She does not have an Intel Mac. It's a PowerBook G4. Hence no Snow Leopard there. I have a iMac 24 Aluminum. My Time Capsule backup worked fine until Snow. My TC is wired via ethernet. There is no latest date. When Time Machine backup starts the TM preference pane says it's "Making disk available" Something to that effect. And that's where it stays. If I then try to do anything with the preference panel - like close it - I find out the Preferences are not responding. So I force quit. I try to stop Time Machine backups and it's no good. The TM indicator - that little backwards running clock - in the menu bar just keeps on it's merry little way. The only way to stop it - shutdown. Strange thing is shutdown then refuses to - well, shutdown. I end up having to hold the power button for 5 seconds. I don't get error messages. I get nothing indicating what may be causing this problem. I have been searching these and other forums looking for an answer. I had hoped the user tips you listed would have a solution, but, alas, no. I deleted the timemachine plist in the "higher" library. No luck. I have powered down everything. No luck. Those were two ideas I saw that said they worked. So where do I go from here? Where do I look for error messages that will point me in the right direction? I'd appreciate any help from anybody.

  • Problems syncing iCal btwn iPod Touch and Mac running Snow Leopard (10.6.8)

    Last fall I purchased an iPod Touch 32 GB, now running 6.1.2 iOS. I have an iMac 2007 running Snow Leopard (10.6.8).  I was looking forward to being able to sync my many iCal calendars and take it on the road with me, so that I could make appointments and have them then be available to me on my Mac. I have synced using usb cable, and can get contacts, music, apps synced just fine: but the Calendar has been rather choosy about what it will sync. Sometimes it will give transfer to the iPod all the appts on one calendar (for example, Medical, which lists all my medical appts) and sometimes it will only give me some of those, with no apparent pattern as to why some are transferring and some are not. Other calendars never sync at all. In the beginning I was able to make an appt on the iPod and have it transfer to the Mac,but it stopped doing that within the first month of purchase.
    I have spoken with Apple Care twice on this topic, and both times the conversation ended with the saying they would have to send this up to someone more knowledgeable, who would assuredly get back to me. I have not received any contact from their supervisors/other departments to work on this. The first Apple Tech Support person thought it was due to the new iOS, and assured me they were working out bugs on that, but further updates have not addressed the issue.
    Most folks seem to think the best solution is upgrading to Lion/Mountain Lion and syncing through the Cloud. But I *like* Snow Leopard, and what I've heard/seen about the newer operating systems isn't making me want to jump on that bandwagon unless there's really no other way around it. I've even seen some problems syncing calendars through the Cloud.
    Has anyone found a solution for this that allows me to continue to run Snow Leopard?
    Many thanks.
    A

    Problem fixed. I have 3 wireless mice connected to my Mac Mini through a USB bus, and started to get conflicts, disconnected all of them, re-connected my Apple bluetooth mouse and it all snapped back in to place, also didn't help that earlier, my wife caught the cat walking across my keyboard. That problem solved by closing off the office when I'm not there, and cat expelled from the area.
    Everything working as normal.

  • Isight is not working anymore after updating to snow leopard

    it used to work very well. i updated snow leopard 5 days ago. i try to use skype and photo booth, it is never working again. do people have the same problem?
    thank you for your information

    lightwright wrote:
    Thanks for the info - however surely this has something to do with the snow leopard software update - not a hardware failure or is that just a coincidence?
    My iSight was working fine before I upgraded to snow leopard? Is there a software fix coming?
    Welcome to Discussions, lightwright
    ... this has something to do with the snow leopard software update ...
    You may be correct that the problem has something to do with your SL update, but, as previously explained, many of us successfully use iSight every day after upgrading to Snow Leopard, so the problem is not SL itself. If you believe that your problem is with your update, you should consider reapplying the update using the method suggested above.
    If you continue to have iSight problems after properly applying the SL update, consider all relevant troubleshooting suggestions in http://support.apple.com/kb/HT2090
    However, if your iSight problem continues, and if iSight now does NOT show as a USB device in your Mac's System Profiler, yours is most likely a hardware problem. In that case, contact Apple or an Apple-Authorized Service Provider for service.
    If, after properly applying the SL update and using the Troubleshooting suggestions, iSight IS recognized in System Profiler but still does NOT work with any of your video-enabled Apple software, your disk may contain some pre-SL software that is causing problems. Either erase the disk and apply only Apple software to see if that fixes your problem, or seek help from your Apple-Authorized Service Provider.
    ... Is there a software fix coming?
    ¶2.1.1 of Terms of Use for Apple Discussions prohibit us from speculating on unannounced products, including updates.
    EZ Jim
    MacBook Pro (13 inch, Mid 2009) 2.26GHz w/Mac OS X (10.6.1)  G5 DP 1.8GHz w/Mac OS X (10.5.8) 
    G4 PowerBook 1.67GHz (10.4.11)  iBookSE 366MHz (10.3.9)  LED Cinema Display  External iSight

  • Help needed with Emagic AMT8/Unitor8 and Logic 9.01 Snow Leopard

    Hello
    I have a strange problem here... I have an AMT8 connected via USB to my Mac Pro (directly, not via an USB-Hub) and 2 Unitor8s (one connected to the AMT8 and one to the first Unitor8).
    I can see that the units communicate with each other, but when I open Logic Pro 9.0.1 there are only the first 8 Ports of the AMT8 available, the other 16 ports are greyed out). This happens using Snow Leopard. In Audio/Midi-Manager I can only see the AMT8 as well, although the unit name is AMT8/Unitor8).
    When I go back to my other OS (10.5.8 with Logic Pro 8 latest version) all three units are working and I can see them in the Audio/Midi-Manager.
    I reinstalled the AMT8-Drivers from the DVD (when I open the driver file it says V 2.2) but with no luck. So I know the units are working under 10.5.8 and Logic 8 but not under 10.6.1 with Logic 9.0.1.
    I tried what was described in another topic (http://discussions.apple.com/thread.jspa?messageID=10142376&#10142376) but it didn't change anything.
    Any ideas?
    Thank you for your help!

    Hi
    Thanks for the link. I tried it but with no luck.
    But at the moment it seems to work. I copied the EmagicUSBMIDIDriver.plugin from my previous 10.5.8 system to my new system and now it works which is strange because both drivers had the same file-size and date. Well, I'll see how stable it is...
    Thanks for your help!

  • How do i reinstall my mac laptop with the mac os x snow leopard disc

    Ok when i cut my laptop on something about mac os x utilities pops up and i ordered mac os x snow leopard so i need help to fix this problem.

    Installing or updating Snow Leopard:
    http://manuals.info.apple.com/en_US/Snow_Leopard_Installation_Instructions.pdf

  • Dreamweaver and Snow Leopard

    i recently did a fresh install of snow leopard and everytime i open Dreamweaver CS4 the dock icon bounces and then it quits. No error message from either Dreaweaver or Snow Leopard. Any ideas for a fix?

    Good sir (excuse me if I guessed incorrectly!),
    Many thanks for taking the trouble to reply to - er - my troubles. I 
    really must cease posting these things after dinner...
    I am a beginner (at a ridiculously advanced age) in the world of 
    htmling, so forgive me if some of my answers are based on ignorance of 
    how things work.
    Code: Near the top of the page is the inscription:
    ... and before various bits of text are things like: I can cause the right (for me) things to happen if I manually change 'Links' to 'Redsub' or similar, but I can't make changes by clicking on the relevant bit in the CSS box. And, as I indicated, if I select the text, then use Text > CSS styles, 'None' is ticked and the options 
    are greyed out. I can't seem to un-tick the 'None'.
    If you can suggest something, I'd be most grateful; if you're as 
    puzzled as I am, I wouldn't be terribly surprised.
    Happy days,
    Ol.

  • Snow Leopard 10.6.3 and Appleworks 6.2.9

    Until yesterday, I had only upgraded my laptop to 10.6.3. Unfortunately, I didn't think to CHECK how AppleWorks behaved after I did that
    Yesterday I loaded Snow Leopard (10.6.3) onto my wife's iMac and my MacPro. It was after that that she noticed a nasty problem: Every time she opened a formatted AppleWorks document and then performed a Page Setup the left and right margins were set to 0. I did the same test with a number of different AppleWorks documents on my MacBook Pro and MacPro and the same thing happens EVERY time: The left and right margins are set to zero.
    I have cleaned out all the AppleWorks preferences files and folders but the problem persists.
    Yes, we are migrating everything to Pages but that takes time. In the mean time I need a solution to this problem. (No, I cannot find the original AppleWorks discs, only the 6.2.9 upgrade.) Any ideas?
    Thanks.

    This appears to be an incompatibility between AppleWorks & Snow Leopard & is never likely to be fixed. AppleWorks was last updated in January, 2004, & was declared end-of-life (i.e. no further updates or official support) in August, 2007.
    Your options, as I see them, are to revert to an earlier version of OS X when you want to use AppleWorks or move your files to newer programs. I rarely use AppleWorks any more, but I do keep a Mac capable of running Tiger & Classic & of running Leopard for programs I occasionally need that do not work in a newer version.

Maybe you are looking for

  • SUBST_GET_FILE_LIST

    I am using the function module SUBST_GET_FILE_LIST to get the list of files in the directory.In that there are two import parameters dirname and filenm.I wanted to know what do I enter for the above two parameters?I have with me the physical file nam

  • Macbook Pro i5 won't connect to my wifi says connection timed out when I type in password.

    When trying to connect to wifi type in password and then says connection timeout. Can connect using ethenet cable no problems. Adam

  • !Beware: BWA 7.20 Rev 10 Issues!

    We are having problems with index creation, just like we did in BWA 7.20 Rev 6. I would suggest lots of index creation testing prior to upgrading your production environment. I'm just about to open an OSS Message for the issue. This is simply a heads

  • CTS+: Automate Imports into Quality system

    Hi, We have recently configured CTS+ in our lanscape and we have been successfully moving the non-abap objects. In a demo on CTS+ which was posted in sdn, i had seen that as soon as transport is released from Transport organizer Web UI, it triggers t

  • MMON TERMINATED

    Dear All, I am getting MMON terminated unexpectedly with errorcode 448 when trying to run a procedure which will send an e-mail to my users with an attachment. My server is scheduled to shutdown everyday 5.00 AM for backing up, somehow this day the s