I am very new to freeway. We are photographers building a revised website of photos where colour is critical. I prep the images up in photoshop, everthing is perfect. As soon as I pull them into freeway they become very pasty looking. A lot of the info looks lost. What’s the solution where maintaining colour between the two applications is critical, or am I just being dumb and being new to freeway I am missing something.
I’d make sure that you check “Ignore Resolution” or set them as “Pass Through” and see if that helps on import. You won’t be able to slide the items around, but you won’t have Freeway handle the output either.
Tried ‘Ignore Resolution’ and set them as ‘Pass Through’, still the same. Tried prepping them to the exact size and dpi from Photoshop before pass through still the same. They look fab in photoshop!
I am very new to freeway. We are photographers building a revised
website of photos where colour is critical. I prep the images up in
photoshop, everthing is perfect. As soon as I pull them into
freeway they become very pasty looking. A lot of the info looks
lost. What’s the solution where maintaining colour between the two
applications is critical, or am I just being dumb and being new to
freeway I am missing something.
When you prep them in Photoshop, do you convert to sRGB?
Yep, sRGB. It seams to be lightening the images. And it’s doing it as soon as you import the image, even when set as pass through. Is there a Freeway display option? That said it retains that look when you preview in browser. It’s very strange.
Also, another thing to bear in mind is that everyone’s monitor will
be set differently so you can’t be assured of how they will look
globally.
I viewed my site on my wife’s pc (which I tend to veer away from) and
it was unbelievably pale. I then went on a mission to look at it
through as many different setups as possible. Some were very dark and
some very pale, but most seemed to view in a reasonable colour space…
Maybe it was laziness, but I decided to leave it as it was!!!
Good luck anyway.
Trev
On 11 May 2008, at 09:04, Paul Bradforth wrote:
On 11 May 2008, at 07:46, mandy gray wrote:
We are photographers building a revised
website of photos where colour is critical. I prep the images up in
photoshop, everthing is perfect.
Thanks, Trev. I know everyones’ monitors will be different, and maybe different OS and browsers will alter stuff too. But I see the problem side by side on my monitor with a PS window and a FW window. It’s weird. I can’t see why FW would display the colour differently. Even if I make the same hex colour in each program and display them side by side they’re completely different. Even if they’re websafe colours. Is it that one app is using my display profile and the other isn’t???
Sometime around 11/5/08 (at 04:29 -0400) mandy gray said:
I can’t see why FW would display the colour differently. Even if I
make the same hex colour in each program and display them side by
side they’re completely different. Even if they’re websafe colours.
Is it that one app is using my display profile and the other isn’t???
You’re getting close to the issue. The big problem with colour and
web design is the lack of proper colour control. The vast majority of
browsers completely ignore embedded profiles, and most preparation
processes don’t include profiles anyway.
For colour to reproduce as best it can, you must end up with it in
sRGB and tuned to look acceptable in that space. I absolutely would
not recommend that you switch to working in sRGB for normal photo
manipulation and retouching work; that space is painfully limited
when it comes to critical work. BUT it is the ‘lowest common
denominator’ space that is assumed for web work; it is what most
machines default to, and what most budget monitor manufacturers set
as the default in the hardware controls.
I’m assuming that your display is correctly profiled. With that as
part of a proper ColorSync workflow and an end-to-end colour
configuration set up in CS3, you should have reasonable confidence in
what you see on screen. BUT (again) when working for web things do
simply unravel to an extent - especially if you don’t adjust your CS3
colour settings.
I have two different sets of custom CS3 colour settings that I can
apply from Bridge CS3. One is tailored for print:
Working Spaces -
RGB: Adobe RGB
CMYK: Coated FOGRA27
Gray and Spot: Dot Gain 15%
Color Management Policies -
Preserve all embedded profiles
and one is tailored for web:
Working Spaces -
RGB: sRGB
CMYK: Coated FOGRA27 (although not relevant to web use)
Gray: Gray Gamma 2.2
Spot: Dot Gain 15%
Color Management Policies -
Convert RGB to Working RGB (others set to preserve)
This works for me, although you may well have other settings in place
and good reasons for that.
If your photos look less than ideal on a certain monitor, just think how truly awful everyone else’s must appear
On Sun, May 11, 2008 at 1:29 AM, mandy gray wrote:
Thanks, Trev. I know everyones’ monitors will be different, and maybe different OS and browsers will alter stuff too. But I see the problem side by side on my monitor with a PS window and a FW window. It’s weird. I can’t see why FW would display the colour differently. Even if I make the same hex colour in each program and display them side by side they’re completely different. Even if they’re websafe colours. Is it that one app is using my display profile and the other isn’t???
I see the problem side by side on my monitor with a PS window and a FW window
And how do they compare with the browser window side by side with the PS window?
Surely this is the the more important view. You, of course, are going to be the greatest critic being party 1st hand to what the originals are like - the rest of the viewing world wont know any better - or care - as long as they are pleasing to the eye.
I think that we all know that if you want colour matching as a priority then the web is not our friend and the only true method of showing the real thing is through printed medium, whether 4 or 6 colours at that.
But to stop Freeway making a difference in the whole scheme of things then use the ‘pass through’ setting. That then takes one factor out of the equation.
Take a look in the View menu in Photoshop. Proof Setup and Proof
Colors are the culprits here, I am guessing. I try to leave mine at
Monitor RGB when working on Web graphics.
Walter
On May 11, 2008, at 4:29 AM, mandy gray wrote:
Thanks, Trev. I know everyones’ monitors will be different, and
maybe different OS and browsers will alter stuff too. But I see the
problem side by side on my monitor with a PS window and a FW
window. It’s weird. I can’t see why FW would display the colour
differently. Even if I make the same hex colour in each program and
display them side by side they’re completely different. Even if
they’re websafe colours. Is it that one app is using my display
profile and the other isn’t???
Sometime around 11/5/08 (at 21:22 -0400) Walter Lee Davis said:
Take a look in the View menu in Photoshop. Proof Setup and Proof
Colors are the culprits here, I am guessing. I try to leave mine at
Monitor RGB when working on Web graphics.
Doh! When I nattered on about colour settings I completely forgot to
mention that. Thanks Walter, that’s probably the actual cause of the
discrepancy.
Guys thats fantastic, THANKYOU. Proof Setup in photshop was the culprit, it was set to CMYK on both the laptop and the mac. Stupid mistake on my part! Another question, should I pick monitor RGB or Windows RGB assuming most people use Windows.
Sometime around 12/5/08 (at 09:02 -0400) mandy gray said:
Another question, should I pick monitor RGB or Windows RGB assuming
most people use Windows.
Personally, I would set up a web-oriented, sRGB-based CS3-wide colour
settings preset, use that, and don’t force any ‘foreign’ display
method for your main work process.
