Pages: [1] 2 3 ... 10
 1 
 on: Today at 04:02:28 AM 
Started by madshutter - Last post by Paulo Bizarro
Wonderful.

 2 
 on: Today at 04:01:07 AM 
Started by James Clark - Last post by Paulo Bizarro
Nice colours, pleasing smooth photo.

 3 
 on: Today at 03:41:52 AM 
Started by lowep - Last post by BartvanderWolf
Curious, this is the first time I have heard this one. Kind of makes sense in theory, but have you tried it in a practical application and noticed any real difference?

Hi,

I'm not particularly into B/W photography, but in an odd case (depending on the spectral content of the scene, it would help (a bit). Whether it's worth the risk of optical image deterioration (dirt / veiling glare / optical imperfections) remains to be seen on a case by case situation.

Cheers,
Bart

 4 
 on: Today at 03:34:34 AM 
Started by Dinarius - Last post by GWGill
The V4 reference sRGB profile is quite interesting.  In perceptual mode it maps RGB values into a much wider gamut in PCS.
It likely maps to the PRMG. The assumption is that the destination profile maps from the PRMG to the destination device space.

 5 
 on: Today at 03:22:33 AM 
Started by madshutter - Last post by stamper
An amazing image!

 6 
 on: Today at 03:15:27 AM 
Started by Rajan Parrikar - Last post by sdwilsonsct
#3: I like the form, the textures, and the attitude. I'd like you to get closer, safely.

 7 
 on: Today at 03:04:28 AM 
Started by torger - Last post by bcooter
Sometimes the non pros do not realize that a big part of our job is to cover for every possible eventuality so that there is that wonderful allowance for the serendipity that can give us those amazing visual glimpses that can make for an amazing image.

The difference between "making" an image and taking a photo.


Very Nice work Brent.

BC

 8 
 on: Today at 02:55:06 AM 
Started by madshutter - Last post by sdwilsonsct
Very nice!  I particularly like the cottonwoods and the silky, silvery water.

Fine stuff.

 9 
 on: Today at 02:53:52 AM 
Started by Paulo Bizarro - Last post by sdwilsonsct
1. #1

... +1.

The trees accentuate the claustrophobic feel of the cave. This complementarity isn't in the other photographs.

 10 
 on: Today at 02:20:25 AM 
Started by RikkFlohr - Last post by ButchM

Was it Apple's fault that an Adobe engineer screwed up the code? Nope, but it was a code change that was forced by Apple. So far, I have't seen Apple implicated in this problem much, only Adobe. Note, Windows users have been blissfully printing away without this issue.

You all can keep harping on the mistake and ignore that facts and fail to enjoy the bug fix Adobe rushed out the door...in the meantime, I'm pleased I can now print out of Lightroom again :~)

I've seen plugin developers use the same exact excuses explanations when Adobe makes changes in their API's. Sometimes, those changes seem to arrive for no good reason when the current method appears to be rock solid. Yet we all know, in order to advance, new foundations need to be built. The bottom line is, if any developer is going to support any partnering configuration ... they need to be prepared for updating and upgrading their code as technology advances. It's no secret that Apple has a history of making changes like this. It shouldn't come as a shock to anyone involved that they updated their printing API's.

Did Apple start the scenario that resulted in this issue occurring? Absolutely. However, it was Adobe that failed to fully test and recognize the issue before it reached we end users. And ... as I stated previously, for Lightroom, it has been the fourth such failure I have experienced in very recent history. It is fast becoming a pattern. A pattern that does not instill confidence.

Do I appreciate the quick response and correction of the issue? You betcha. Though, I would prefer that the good folks at Adobe would place that type of emphasis and productivity before they send me their updates. Then we end users, nor the engineers would have to be bothered with repairing such issues. Then I also wouldn't have to come here and share my dismay when my workflow is hampered or, at times completely broken resulting in rolling back to an earlier version.

If there are folks on this and other discussion forums who would prefer there to be less 'harping' and less failure to 'enjoy' the software Adobe produces ... all Adobe need do is scrutinize their work a bit more carefully before they send it our way. It's a rather simple solution.

Pages: [1] 2 3 ... 10