CS3 Colour Management with Leopard

Hi, I have a Canon Pixma iP4200 (driver 4.8.3) Leopard 10.5.2 and Photoshop 10.0.1, Surprisingly I haven't printed anything since Tiger but I printed something out yesterday and it looked horrible, real muddy look to the picture with a magenta cast over it.
Why is this, anyone else have a problem getting the printer to print what's on the screen in PS3???
Its really bugging me because I spend so long colour correcting my images only yo print and see they look horrible.
ANY ideas on how to fix this would be much appreciated.
p.s. I'm not too brill on PS!

I have gone from PSE 2 to 3 to 4 successfully and used old photoshop and the original lightroom beta all worked successfully. there is obviously a reason why the same file looks different when printed with PSE4 and PSE6
whatever the books say when adobe changes a release they must not change the way colours come out if you use a previously created file. if they do then a lot of artists/photograpers/graphic designers will be wasting time modifying images
I have been in the DP business too many years to accept that...
note adobe did not say I had a problem or they had one they only said can you send us some samples of the printouts. I also included a CD with the files and suggested they print them with both versions of PSE if I was wrong I would have expected to be told. no answer implies they are still working on it.....
cheers elo

Similar Messages

Device Central CS3 NOT compatible with Leopard

I just upgraded to OS X Leopard and Device Central CS3 is no
longer usable. OS X says it is "not supported on this
architecture," as if the machine was PowerPC (it is an Intel
MacBook Pro). All the Adobe support docs says DC is compatible so I
don't know how to resolve this situation.

CS3 device central is fully compatible with Leopard ...for me its running fine

Contribute CS3 not working with Leopard

Hi,
Ever since I loaded Lopard onto my Mac - Contribute won't
connect to any of my websites.
Says it can't connect 'because the server is down or not
accepting connections.'
Is anyone else having this issue - and does anyone know the
cure?
I've re-installed - but still won't work.
Thanks,
- Greg

This issue has been reported couple of time in this thread, i
was able to get the site info twice from the users and for one site
it was not connecting from the Tiger itself because of the site
issue and for the next one it was working from the 3 leopard test
machines we tried.
We have tested Contribute CS3 on Leopard and it works fine.
In case if the user is hitting any issue then it is important to
reproduce it then only we nail it down.
I do understand that you may not like to give the information
and for that only the second option is:
1. One test folder inside the site
2. One test role and a test user under the same role
3. Provide the access to the user only to that folder by
administering the site -> Select the role->Edit Role
settings->Folder File Access->Only allow editing within these
folders -> Add the test folder in the list
In this case i will be having the access to only one
particular folder which you can very well delete later on.

Colour Management - who does what - Some thoughts now the smoke is clearing

First up, thanks very much to everyone who contributed their ideas and expertise to my recent query here, when I was seeking help for a problem with colour management issues when printing a magazine I edit. I have a ton of suggestions to work through and study but the smoke is slowly clearing and it raises some interesting points which I think are worth recounting.
First of all, I have been editing short run magazines now for 25 years, at first part time and later on a professional contract basis. I am not a trained graphic designer nor a trained printer. I did start out training as a graphic designer, many years ago but gave it up for a career in IT (as a networking specialist). That was full time until 10 years ago, although I did some freelance writing and editing in my spare time.
And yes, I did start originally with scissors and cut and paste, and moved on through black and white with spot colour and Pagemaker software to full colour and InDesign today. One thing which may be different about my experience to most of yours is that I am a PC user and always have been. All my editing and graphics work has always been done on a PC - Pagemaker was our DTP package of choice for a long time and we supplemented this with Corel-Draw (which has a range of graphics handling options). All my software is legal and I always register it and keep it up to date. I have used the same graphic designer for quite a few years now and whenever we upgrade our software he goes and gets trained on the latest release.
Around 10 years ago I was offered the chance to edit a specialist short run magazine (not the current one). This was a chance I took and gave up the day job and became a full time freelance. Editing is not my main or only source of income. I am also a freelance writer and photographer and heritage consultant and I have a specialist image library.   I sell my own sell my work - articles and pictures - to the national and local press. I also write books (non fiction) on commission. The magazine editing is really an extension of my interest in historic landscapes. I have never had any complaints, or problems, with the freelance work, photos and archived images I sell. Clients include national newspapers here in the UK, national magazine groups and my books are available in national bookstore chains. I supply my work digitally, naturally, and it includes photos I have taken myself and items which I have scanned into my library of historical images and store on line. No reported colour management issues there.
I have always enjoyed a good relationship with my publishers and printers because I seek to be as professional as possible, which means delivering my stuff on time, to the required standard so that minimum intervention is required from them. This does assume that I have a clear brief from them on what they need from me.
Recently this approach has not been enough to avoid colour management issues with the short run magazine I currently edit. I have been wondering when and where things went astray and date it back to the upgrade to InDesign two years ago. However it may have its roots in my earlier decision to use PCs not Macs for my work.
Until 4 years ago I had used the same printers for magazine editing for many years. They were a well respected firm specialising in short run magazines. They were not far from where I live and work and if there was a problem I would go over and discuss it with them. They were happy, and competent, to handle Pagemaker files generated on a PC and convert my rgb images to cmyk if there was any concern about the colour balance. On a few occasions I paid them to scan a photo for me. However 4 years ago the owner decided to retire and shut up shop. I needed to find a new printers and it had to be someone who specialised in short run magazines and could meet the budget of the charity I edit for. Also someone who could handle copy generated using Pagemaker running on a PC. I chose a printers I had used briefly in the past where I knew some of the staff and was promised PC based Pagemaker would not be a problem. I even got this in writing. I started to send them proofs generated using Pagemaker v7 on my PC.
I soon found that although they had agreed they could handle Pagemaker on a PC in fact they had only a few PC based clients and were using a single ageing PC running Pagemaker to proof their work. In fact nearly all their jobs were Quark based. I was also told we had to supply CMYK images although not given any further requirement so I now did the conversions from rgb to CMYK using my PhotoPaint software. (There are quite a few settings in Corel for the conversion but there was no guidance by the printer on which to use so to be honest it did not occur to me that it might be a problem).
Now of course I understand that the drive to get customers to supply CMYK images was a Quark driven requirement back in the late 1990s. I did not and do not use Quark so knew nothing for this. I did have some early colour problems and font incompatibilities with the new printers and was pressured by their senior Graphic Designer (who designed for their own contract clients) to upgrade to InDesign and provide them with a .pdf, which I was assured would solve all my problems. The .pdf would be the same as the final printed magazine because "it would not require any further intervention by the printers".
I expect you are collectively throwing up your hands in horror at this point, but I think he was speaking genuinely. The creation of a .pdf using InDesign, is widely promoted as the ultimate answer to all printing issues.   I have encountered it recently with a lot of printers' salesmen and my friend, who edits a learned journal, has just been told the same thing by her printers, to get her to upgrade to ID. Incidentally she also uses a PC.
So we upgraded our design process in house to InDesign and our graphic designer went on a course, two courses in fact. When we came to produce our first .pdf using ID, the printers' Senior Graphic designer came on the phone and talked our designer through the ID Export function. I think he may at that time have told him to create a preset profile with MPC and the defaults, but to be honest I don't recall. We were never sent anything in writing about what settings we needed to match theirs. I continued to have intermittant colour management problems but put this down to my photos. Things came to head with the most recent issue where the colours were badly out on the cover, supplied by a press agency and taken by a professional photographer. The printers seemed to have little or no idea about possible causes.
Initially I thought that part of the underlying cause must lie in some mismatch between what I was sending the printers and what they expected to receive so I asked them to specify what I should send. All they said was use Profile preset as MPC setting and accept the defaults which accompany it.
So I came on here looking for a solution. A lot of people were keen to offer their own experience which I really appreciate. However the messages could be conflicting. Some of you suggested it was the underlying cover photo which was at fault, some that it was my monitor which needed better calibration.
Many of you here said that part of the problem, if not the whole problem, was the way I was generating my CMYKs for the printer and I should use Photoshop to do this. You also mentioned a number of possible colour management settings which I should try.
At times the advice seemed to change tack. There were suggestions that the colour management issues I had were nothing to do with the printers, that it was up to me not them. Quite a lot of you said I needed to be better informed about Colour Management issues. I agree, but I had never had any previously (maybe good luck, maybe good support from my previous printer) so I was not even aware that I needed to be better informed. Some of you mildly chastised me for not finding out more and doing more to manage my own colour management with the switch to ID. To which I can only say if I had needed to train up, I would have done. I did not realise I needed to. Nor was my designer aware of the issues as colour management was not really covered on his ID courses which were about typesetting and design.
Some of you even seemed to hint that unless I was prepared to use an expensive high end printer or effectively retrain as a print specialist or get my graphic designer to do so, then I probably shouldn't be in the magazine editing game at all. OK maybe that is a bit harsh but you get the drift.
The fact is that printing is much more accessible these days to all sorts of people and in particular to people with PCs. My brother lives in a large village in an isolated area and produces a village magazine which has been a great success. It is in black and white with spot colour but he would like to move to an all colour issue. He is a bit nervous of the colour management issues as he has no experience of graphic design and is his own designer using a low end entry level design package. He too uses a PC. The printers reps all tell him the same thing they tell me, that all he needs to supply is a .pdf using InDesign.
Somewhere I feel a black hole has developed, maybe back in the 1990s with Quark 4.11. A lot of printers standardised on that, and set up a work flow and prepress dependent on CMYK images as provided by the clients. They assumed the the clients would doing their own colour management. This approach also assumes everyone is using Quark on a Mac with the full range of Adobe software. When it became possible to generate .pdfs using InDesign, this was held out to users as the Holy Grail of magazine printing, even though their workflows and prepress were still based on Quark 4.11 principles. Any underlying colour management issues the clients now have to tackle themselves.
So now we have the situation in which I find myself, having to learn from scratch a good deal about colour management issues so that I can tell the printers what is needed for my magazine. Meanwhile all the printing salesmen, the ones I encounter anyway, are still busy pushing the InDesign to .pdf as the "be all and end all" solution. Some re-education is needed for all parties I think.

I am glad to see that the sun is peeping through the clouds.
I apologise for my Aussie-style straight talk earlier, but as I said before it was not directed personally at you but in the direction of others whom you epitomize, repeating a conversation I have had many times over the last 10 years or so where respectable, well-meaning photographers, designers and other contributors refuse to accept that colour management is being thrust upon them.
It is a simple fact of life, there is this 'new' thing that has butted into the very root of our trades and changed the most basic principles of printing and photography. We expect that this kind of thing does not happen but the industry we now work in is not the same one we trained in twenty years ago.
Many printers are still struggling with the same conflict, so many tradespeople cannot accept this change.
This is exacerbated by the fact that colour management is so complicated to learn and implement and confounded by the fact that the default settings and a clumsy workflow often yield acceptable results with incorrect, generic settings, hence the old 'use InDesign and make a PDF and it will be ok' route.
When the chain of colour management includes the photographer, the photographer's client, the designer, the other designer maybe, the prepress person, and the platemaker, and a single incorrect click by any one of those can kill the CM it is not surprising that in the end when someone is looking back to see where it fell over they usually never find out.....   They will meet someone who says ' I never touched it, I simply opened the file and scaled it and closed it'. And that person will be a reputable photographer or designer (and CLIENT) who has no idea they just broke it. So what do we do? We go with the generic setting that seems to yield adequate results therefore avoiding the confrontation.
You need to understand the situation of the printer who took his business through the 'early' days of colour management, we had all kinds of very reputable sources supplying incorrect files, we did not have the expertise yet to be able to address the entire workflow, it would have meant training photographers and designers all through the best design houses and national institutions, because they blamed the printer. Only in the last few years have I seen these people coming around to the fact that they bear responsibility for implementing their own cm and maintaining it through their own work.
Sadly, many high end sources are still not there, and I mean HIGH end! Probably the ones that don't even visit this forum because they want to keep blaming the printer... They tend to live with the poor quality reproductions and just pull up the worst ones and fiddle with those and try to avoid the 'elephant in the room'.
I am sorry to say that it was not practical for a printer to reject mismanaged files for fear of losing clients who would happily accept less than perfect results in order to avoid the painful truth that was being told to them. The best thing we could do was to gently make those clients aware that their workflow was imperfect and hope to show them how we could help... Many print shops do not have someone knowledgeable enough or patient enough to do this, or the boss does not understand the issue either and tries to work around it to keep his jobs flowing in the expectation that all those experts in the chain will eventually tame the thing.
The many experts on this holy forum are waaaaayyyy ahead of the printing industry in general and photographers and designers in general in their understanding of colour management workflow. I have seen first hand how reputable local industry people and trainers alike are spreading misinformation and bad techniques, when I discovered these forums back in about 2002 I found that they opened up a whole new galaxy of knowledge and facts that actually worked and made sense, unlike what I had been told locally.... This forum taught me what the Adobe text books did not, the Tech' teachers did not, local 'experts' did not!
I tell all interested people to join these forums and learn to discriminate between the good and bad information.

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

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.

Anyone else having a Problem with Leopard and Photoshop CS3?

I'm using CS3 with Leopard 10.5.4 at work and there are some very aggravating anomalies, that I'd like to nail down to a cause. Most frequently, when switching from apps to P'Shop, the menu bar stays for the previous app, i.e. when going from Finder to P'shop, the menu bar still says Finder and has Finder options. Changing from Lightwave to P'Shop, the menu bar remains Lightwave.
Occasionally, an Adobe app - P'Shop or InDesign - will simply disappear and not come back. The icon in the dock shows it as active, but no amount of clicking, Command-Tabbing will reveal the app and I have to Force Quit, losing unsaved changes.
I have a feeling it's Leopard, since, I've used CS3 on Tiger and CS4 on Tiger and never had a problem.
I'm wondering if upgrading to the latest Leopard would make much of a difference.
Has anyone come across this and found any kind of answers?
Thanks for any suggestions.
-Vincent

> Just because it doesn't happen to Phil (who may not use all of the same features of the Suite that others do anyway) does NOT mean that these problems are not real and are not mere PEBCAK.
Right. If someone is having a problem associated with Tiger, it's PEBAK. If Leopard is involved, it's automatically because of Leopard. Apparently, with Apple's latest OS, trouble shooting problems are no longer necessary - just blame it on Leopard and call it a day.
b FUD
I find the dynamics here really interesting. This thread would have been very different if Vincent had posted with problems involving Tiger. Would have gone something like this:
After admonishing him for not providing more information about his setup by posting the obnoxious big blue link on how to ask questions (ahem - we know NOTHING about his machine or configuration, such as which machine, how much RAM, scratch disk or attached peripherals), there'd be all kinds of trouble shooting advice given - "try a new user", "repair permissions", "run DiskWarrior, and on and on ...
But no, since he mentions Leopard, none of that is apparently necessary and the completely, utterly
b irresponsible
advice is given ... "that's just the way Leopard is".
Those are some serious problems he's reporting that have nothing to do with Leopard. Something is obviously hosed!
As for discounting my experience because I don't use every app in the suite as extensively as I do Photoshop, I'm FAR more qualified to discuss Leopard and CS issues than Ann or Neil who do not use Leopard at all (and have never used it as far as I know.)
"Others have problems with it", is their battle cry but it's extremely weak. Do I really need to remind you all that these forum are ALWAYS filled with people who have problems, regardless of version or OS? You act as if this forum was a ghost town when Tiger and CS3 were current!
Gee, Ann ... people are STILL reporting problems with 10.5 and CS3? How shocking! Guess what - people are STILL reporting problems with 10.4 and CS3 too! Let me make a prediction - people will have problems with 10.8 and CS9!
Vincent-
> I don't really deal with fonts anyway ...
Yes. You do. Even if you never type a single line of text, every application uses fonts to create menus and other GUI items. If one of those fonts are bad, it can create all kinds of problems, including the very problems you mention.
The fact that you don't seem aware of this and you're still using 10.5.4 leads me to believe you're not familiar with the basic practices of maintaining a healthy system. Again, how did you install Leopard on that machine?
Look, if you're simply trying to justify using CS4, go right ahead. It's a worthwhile upgrade in it's own right. However, if you install it on that machine in it's current state, CS4 will NOT fix your problems because you do NOT have a healthy system.
You asked for experiences with Leopard - I can launch every application in both CS3 and CS4 suites
i simultaneously,
and STILL not have your issues. I haven't experienced anything like your CS3 problems in Leopard - on both a 2006 Mac Pro and a 2008 Macbook.
If you'd like help to try and figure out the real problem, I'm more than happy to help. If not, Adobe will gladly take your money ...
-phil

Draft Mode Printing with Colour Management

Hi
A simple change to the print module that would improve matters for me.
Draft Mode Printing disables all print enhancements, I can understand the reasoning behind this BUT for me the main advantage is the speed of generation using only the existing previews, I would still like to be able to print using the correct colours. Proofs don't have to be high quality or particularly sharp but if you present a client with proofs that have a colour cast or other colour fault they are going to think your final images are also suspect.
Please consider re-enabling Colour Management in Draft Mode.
Thanks
Mike

u are probably not getting much help on this unless you post screenshot of your process (starting with File> Print window)
remember, Photoshop can print a document correct regardless of how it looks on the monitor (and vice versa: Photoshop can display a document correct regardless of how it prints)
i recommend getting a known target like the WhackedRGB.jpg and see where the problem is occuring (in Photoshop color management settings, on the monitor, on the printer or both)...

Help diagnosing colour management problem - windows 7, CS3, Eye-one display 2

Hi,
I had my colour management all set up and working on my old laptop then I foolishly got a new laptop and am completely failing to get things straight.
The new laptop (Asus N56VM with Nvidia GT 630M) is running Windows 7.. I've calibrated the screen using my Pantone (X-Rite) eye-one display-two and straight away it looks much better to the eye. I calibrate to native white point which I always do with laptops.
I've used the following procedure to make Windows 7 load the profile at startup and removed the GretagMacbeth tool which attempts to do the same:
http://www.laszlopusztai.net/2009/08/23/stop-losing-display-calibration-with-windows-7/
Everything looks great except when I attempt to use anything with colour management.
Eg. All my old photos looked great in Adobe Bridge until I activated Color Management via it's settings and suddenly they look awful - sky blues turn turquoise.
If I open an sRGB tagged file in photoshop it looks the same - awful (using Preserve Embedded Profile and with a working space of Adobe 1998 in Color Settings)
Only way I can get images to look normal in Photoshop is to open them then ASSIGN the monitor profile to the image (I know this makes no sense to do and is in no way a workaround)... and it looks great.
Something's not right somewhere but not sure where to start looking since there are so many variables. Can anyone suggest a route to investigate based on what I've said so far? This is driving me nuts!

Ok, I use the same tool and software to calibrate my monitor. I disagree with Lazlo p about resetting Color Management. What you should have is under Devices>Display, click "Use my settings for this device". (You will have to go to the place you checked Windows display calibration and uncheck it first.)
When I first started using Win 7, I did not have either checked, (I didn't know about Windows Display Cal) and had fits. Then I checked "Use my settings..." and it ran fine.
The reason the Gregg MacBeth Calibration Loader tool is needed has to do with their reluctance in updating the software completely to run in 64 bit. The Calibration Loader has always been a part of their software and for at least, XP, has run seamlessly. I now have the icon for Cal Loader in my tray, and after reboot, I'll click it to be sure the profile has loaded. Most of the time it has.
I verified it with the support group who verified the need to use that tool in 64 bit. The workaround? An entirely new software package at a considerable sum!
So I did what Lazlo suggested, and when I had completed the changes, I clicked the cal loader icon in the Tray.
The display changed!
I trust the Cal Loader.
I do not grasp what MS implies in their discussion of WCS vs ICC, especially with respect that WCS is better.
Finally, I am doubtful that you should be using native white point. It's not simply a choice available to laptops, but to all LCD screens (AFAIK!). There is a huge difference between 6500K and native white point on the Dell u2412,so much so I dismissed it out of hand and tweak the colors in RGB during calibration. Your laptop may not offer that path.

Dreamweaver cs3 problem with leopard

Dreamweaver CS3 is much slower with Leopard. And I have trouble uploading pics to remote site. Anyone got a solution?

If there is a solution, you'd probably find it on the Adobe forums:
http://www.adobe.com/support/forums

When will CS3 be fully compatible with Leopard?

I haven't read any definitive answers to this question.
Adobe says when Acrobat 8.1.2 Pro is released in late Jan08: Leopard FAQ
But the 8.1.2 update this month didn't say anything about Leopard...
Does anyone know? We've been waiting to migrate to 10.5 for a couple of months now and CS3 is the last hold-up.

I understand CS3 came out before Leopard. But Leopard is a whole new operating system, they give core developers like Adobe months and months to make their software workable for the new OS. Third party developers always take alphas and betas from the OS builds, do they not? Is it the requirement that Apple make each and every software piece compatible with it's OS? So, they in essence have to do the third party's developer's work?
Further, if it's not compatible, then what grounds does Adobe have telling customers that it is. That would be a lie, then, wouldn't it? I'm just sayin. And I don't have Leopard OR CS3 yet, but I sure don't like the fact that Adobe is being pretty quiet about these issues--it takes someone some digging to figure this out, then they find engineers who are basically claiming it's not compatible, and to wait for likely 18 months until 10.6, and if I were Adobe's legal dept. I'd probably delete this post.
As far as *everyone* having issues, it doesn't seem to be the case--I am reading several threads where many have figured it out. Maybe I'll be lucky.
I can certainly see if Apple changed the specs (I'm not sure what this means, do they not provide seeds to you?), Adobe having a LOT to complain about. But I have not seen evidence of this other than an Adobe engineer calling the OS Buggy. Proof?
I think Apple being quiet about it is that they don't allow their staff to blame others in blanket statements on forums in direct contradiction to what they warrant in writing the software to be compatible with. Usually things like these come from press releases or a kb. Or Steve Jobs <g>
Buko, your blanket statement about CS3 being perfect in Tiger doesn't seem to wash. A quick look through the Apple forums and the forums here pretty much show that not to be the case. What seems to be clear is that Adobe's registration and auto update program are the problem. I won't go so far as to say they are poorly written and executed, but the scores of people who have had and continue to have numerous issues IN TIGER certainly point in that direction.
I suppose we could blame Apple for that, too?

Using colour profiles with Windows XP Pro SP2

Hi,
Freshly-installed WIndows XP Pro SP2 on the Unibody MBP.
I note that in the advanced display settings there is a tab for colour management. It offers the opportunity to add a .icc or .icx (I think) colour profile. I copied across my .icc-prefixed colour profile from my Leopard install, added it, and Windows reports it as invalid.
Can anyone tell me how (or whether it's possible) to make a Leopard-created .icc profile work with XP Pro SP2? If it's not possible, can someone suggest some free software for XP Pro SP2 that I can use to achieve a similar result?
Thanks.
SiR. G.

Got the error message 3256 after downloaded latest itunes version 8.xx.
After days of reading logs and bullentin boards, uninstalling, hard resets,firewalls experiments, etc, I found solution for me. Following firmware upgrade to airport express solved. When you go to Apple download center and search for airport revisions only the MAc version pops up. However they do have this one for windows. Give it a try. Good luck.
http://www.apple.com/downloads/macosx/apple/firmware_hardware/airportexpressfirm wareupdate63forwindows.html

Colour management warning for dual display users

For those of you who require a colour managed workflow and have more than one display, be very careful in Mountain Lion. It appears to have a bizarre bug where images loaded and shown on the primary display (e.g. in Preview) are initially rendered with the colour profile from the secondary display, or something along those lines. Dragging the display window to the secondary display and back again sorts things out. I've filed a bug report.
If your two (or more) monitors have the same colour profile, you won't have a problem. The only workaround I can see is to set your least important display(s) to all have the same profile as your (probably calibrated, if these things matter to you) primary display, at least until (if?) the bug gets fixed.
If you want to see it for yourself, set your two displays to differing profiles - e.g. NTSC (1953) on the primary and Wide Gamut RGB on the secondary. Then load an image into Preview - something with lots of shades of red "works" well for the colour profiles mentioned. Take a screenshot of the Preview window as a reference. Move the window to the secondary display; note the colour shift as it gets re-rendered. Now drag it back to the primary display. It'll look quite different compared to the screenshot you took earlier, despite the fact it's the same image being shown by the same application on the same display in the same window... All you did was drag the window between two monitors and back again.
It doesn't seem to matter if the image in question has a colour profile embedded in it or not. When comparing with your screenshot, feel free to drag the screenshot between the monitors too - after all, it'll be suffering the same rendering bug! You'll still see a different result; in fact it may even be magnified by the accumulated rendering errors.
Preview isn't the only application affected; I've seen identical issues under harder to replicate circumstances in Safari, for example.
Given this fault and others I've seen with colour rendering in Lion, plus several new bugs found in Mountain Lion, I'm afraid that if a colour managed workflow is important to you - well - Snow Leopard or Windows...?! Ugh, what a mess

I've encountered many of the same woes with color management being a graphic designer, but here's my issue:
Have a 15" (Early 2011) Macbook Pro. It is turned on with me hooked up to my Dell U2410 and display open for a dual display configuration. The Dell is my primary monitor.
I then unplug my MBP to use it around the house. I go to plug it back into the Dell for my dual monitor. I notice that the color on the Dell looks good, but now the MBP has a very blue color temperature. Like moving from the preconfigured 'Color LCD' profile to 'sRGB' which definitely shifts to a blue color on the MBP.
I check the color profiles in System Settings and the Color profiles are correct. 'Dell U2410' for my Dell and 'Color LCD' for my MBP. But as I said, it's much bluer than standard. I try to change the color profiles around on the MBP and no matter which I select it's always the same color with no shifts I would expect to see.
Only solution I have found is to restart my computer. Upon restarting all is well again in the world.
It's pretty annoying having to restart my computer everytime I plug it back into my workstation with Dell and keyboard.
Related note: USB does not work when I plug things back and again have to restart to fix this.

CS3 Colour Management with Leopard

Similar Messages

Maybe you are looking for