Let's discuss host based color management before you single out anyone as a troll ok?
I'm totally mystified by your hostility. If you'd like to discuss host based color management, or anything else that is not a part of OP's topic, start your own thread. I'm happy to participate (as long as you make some crumb of sense with your writing).
If you're just getting started and cash is short, maybe hold off a bit. But don't just look at the cost, balance this against the return. For a busy shop, they'd recoup these few thousand dollars in weeks or months.
If you'd like to get serious about color, hire a consultant to train you for a couple of days.
Are we still discussing things that don't make any sense?
I had a gold fish when I was growing up and I stabbed my hippidy hop with a knife.
Are we still discussing things that don't make any sense?
Second, make sure your design applications have the Working Space profiles setup to sRGB and US Web Coated SWOP. Then have your RIP's input profiles setup to match. This should take care of 99% input problems.
Why not AdobeRGB 1998 for RGB? It has a slightly wider gamut that sRGB (towards greens and blues, but its still wider than sRGB).
I use ISOcoated_v2_eci instead of US Web Coated SWOP. As you can see, it has a wider gamut.
Just my 2 cents...
Thing is, they only really work when you have influence over the design process and can choose to create and mainatain files in these spaces. Otherwise, taking in random customer files that are sRGB and (in the US) US Web Coated SWOP, then converting them into Adobe RGB or some other larger gamut working space does nothing but complicate your workflow and give you one more thing that can go wrong.
I'm also a big fan of converting most files to Adobe RGB for consistency. Our RIP is set to default to that space for an untagged image, and by manually converting (or assigning, then converting), incidents of having the RIP assign the wrong color space are avoided.
olor management is a system of inter-dependant parts, and the results you get are reflected from the relation between those parts.
I'm also a big fan of converting most files to Adobe RGB for consistency. Our RIP is set to default to that space for an untagged image, and by manually converting (or assigning, then converting), incidents of having the RIP assign the wrong color space are avoided.
That said, a good monitor that is well calibrated, and a work environment with controlled lighting and a proper viewing setup is very important.
Nothing at all wrong with wider gamut working spaces. Thanks goodness we have them available for us to use. I take full advantage of them when I'm working with my fine art clients.
Thing is, they only really work when you have influence over the design process and can choose to create and mainatain files in these spaces. Otherwise, taking in random customer files that are sRGB and (in the US) US Web Coated SWOP, then converting them into Adobe RGB or some other larger gamut working space does nothing but complicate your workflow and give you one more thing that can go wrong.
I generally say that if you're the one creating the files, go for the large gamut working spaces. Just be aware that you'll have to still juggle files from the unwashed masses as sRGB and SWOP.
As I've said here recently a couple of times, the end product differences between these working spaces is often pretty small. Yes, you can see a difference, but it's not usually as big as the gamut maps might lead you to believe.
I use AdobeRGB and since the version of wastach rip I use doesn't have the black point compensation feature (another reason I miss colorburst).