Pages: 1 [2] 3 4 ... 10
 on: Today at 07:01:24 PM 
Started by john beardsworth - Last post by FranciscoDisilvestro
I would have preferred if they implemented a solution similar to FastRawViewer in the import module, which lets you check the images based on RAW data and very fast.

This Embedded & Sidecar workflow is useless (IMO) if you use ETTR, UniWB or "ISO less" mode during capture,

 on: Today at 06:48:50 PM 
Started by bcooter - Last post by bcooter
3 spreads from a recent 50 page e-book, print book promo.



P.S.  Man it's hard to do 50 pages.  Thank goodness I'm not a novelist.

 on: Today at 06:22:27 PM 
Started by Paul Wright - Last post by plugsnpixels
I work in higher-ed IT and love these computer discussions. I support and use Macs (iMacs and Mac Pros) but also run Windows 10 and Deepin Linux as either VMs or natively, depending on whether I am sitting at a Mac or at my Hackintosh.

Random thoughts:

-OP has very decent specs on the "slow" PC. I also vote for the fresh install. No need to spend a penny there. Sounds like Windows cruft.

-Thanks for the heads-up about the PCIe NVMe SSD option. I hadn't given them much thought as I'm not currently building a new machine as the Hack is running fine and I have others. But definitely something to consider.

-While I love Macs, the last one I bought new was in 1997 (PowerMac 7300), and a used G4 tower off ebay a few years later. That's it. I would not spend my own money again on a new Apple device (price/performance, as noted by other earlier). Of course I'm not still using those machines! I've used older iMacs over the years. At home I currently use a maxed-out 2013 or 14 MacBook Air which was given to me by a colleague (it was actually on the way to electronic recycling, something to do with a cat and a large drink...). The screen is all cloudy but I use it with an external monitor and kb, and it works great (and is actually clean inside). I was also given a 2007 Dell thinline desktop (Pentium, 4 gigs RAM) which I also put Deepin Linux on recently as a spare station.

-If you must buy a Mac, get a used/refurbed iMac (2010 or newer) and replace the HDD with SSD and max out the RAM. Avoid the Mini though.

-Building a computer is the best way to go, regardless of which OS you prefer. At this moment I am sitting at my triple-boot 2011 build Hackintosh in a G5 case (i7 2600, 16 gigs RAM, Gigabyte Z68 and a bunch of HDDs and one old SSD) which I bought from a friend cheap and made changes to, running Deepin Linux which I recently installed (please Google it and check it out). The Hackintosh also boots Windows 10 and OSX El Capitan. It's ugly and noisy but it's fast and efficient. It's my "play" machine" when I feel like tinkering. The video card limits the resolution in OSX and Linux but Windows looks normal.

 on: Today at 06:09:15 PM 
Started by john beardsworth - Last post by Rory
Thanks for the scoop John.  This is a real improvement but I feel LR is still missing the boat on an efficient workflow for photographers facing large imports and culling.  A workflow where you still have to import ALL the images into LR before culling is DUMB.  The initial cull should be made before importing in the import module by only selecting the winners or deselecting the losers.   In my wildlife shoots I typically only import 10-25% of the images on the card.  If LR sped up the browsing speed in the import module by prefetching previews this would solve this issue.  I won't be ditching photo mechanic yet.

 on: Today at 06:08:03 PM 
Started by ButchM - Last post by Rhossydd
I think the dpreview article sums up my position very well;

"Adobe is turning its back on a certain type of enthusiast photographers: those users who enjoy and care about their photography enough to buy Adobe's products, but don't need to edit 'in the field' or have clients to justify the ongoing cost of subscription software."

Their loss, I was happy to pay for upgrades.

 on: Today at 05:58:37 PM 
Started by davidgp - Last post by Rory
I'm seeing significant performance improvements in both library and develop.  No apparent performance improvement to image rendering in the import module.  Hope that's on the top of the list to fix.

I really like the range masking tool. 

 on: Today at 05:55:21 PM 
Started by madlantern - Last post by madlantern
Just got my 120mm Macro for the X1D, and I did a very quick and rough comparison with the Canon 100mm L f/2.8 Macro I had on hand.

The Hasselblad is obvious sharper in the corners wide open, but in the center and stepped down, the difference becomes much smaller.

 on: Today at 05:39:24 PM 
Started by Doug Gray - Last post by Doug Gray
I stopped keeping up but when the new Gracol 2013 standard came out, proofing was switched for Papers 'without' OBAs to Papers 'With' OBAs. Measuring Devices are needing to be replaced with devices that were capable of M! "AND" and new light standard was indroduced (new tubes). I don't know much about the new lights for viewing.

Since you have the M1 and OBA paper, maybe you need [to try] the new lighing

Not a lighting issue. The soft proofing failure is really a limitation of the colorspace RGB B values being clipped at 255. It's intrinsic and not something that can be fixed with profiles. A workaround is to set the monitor's whitepoint to match the luminance and chromaticity of the D50 (wiith uV) viewing booth. Then don't select show paper white.

If one can easily switch between monitor white points and associated profiles (such as with ColorNavigator inter alia) then the workaround fixes the problem. It's also particularly effective when the viewing station uses lighting that doesn't have the required levels of uV. That's most of them made in the last 20 years. Full D50 w uV booths are pricey. Andrew Rodney's videos on soft proofing follows that approach.

I see proofing paper is now specified at Lab(95,1,-4) from (95,0,-2) in 2006. It's a pretty small change and not really large amounts of fluorescent additives. In any case these small levels have a tiny effect on hard proofing in that industry but there should be no issue with soft proofing as one can simulate  95,1,-4 white points without clipping the monitor's blue channel. Really, the only place I see the effect is soft proofing high key images with a white border for papers with extremely large levels of OBA combined with a high L* white point.

 on: Today at 05:36:20 PM 
Started by ButchM - Last post by Alan Goldhammer
I don't think this thread is about LR vs. C1 in terms of speed, user friendlyness or results. Both are very capable programs which can achieve (similar) outstanding results if you know how to work them and both have their warts, strength and weaknesses.

It's more about pay once and know what you get or pay forever (not knowing how much) for a promise of "improved" functionality in the future without an easy way out.
It's more complicated than that.  C1 is $300 and you get free upgrades for life.  this does not include major releases which will cost more or you can do it just like LR and go the subscription route.  I assume the 'free upgrades' are support for new cameras. 

However I hoped Tom Hogarty would have kept good on his word to keep LR perpetual licences going for further updates and his dry "matter of fact" announcement today without any recognition of a change of direction vs. past statements doesn't in my mind bode well for future cost of the CC licence fees as well as the sunset option once you decide to stop the ongoing licence arrangement. I hope I'm wrong, but this move doesn't give me a comfortable feeling and certainly doesn't motivate me to step into the CC option quickly.
This was not surprising to me at all.

Btw, I thought Adobe would be OK with some critical remarks regarding this move on their blog, however my entry (essentially my first post in this thread) is still "awaiting moderation" and I wouldn't be surprised if it is deleted by tomorrow. Another reason for me not to start paying more money to this company when I have no idea when and how I can stop it without a serious impact on how I process my raw files.
To paraphrase what was said on the 'Coffee Corner', it's Adobe's Blog and they can moderate the way they want.  If you save all your processed work as TIFFs you can exit the subscription model any time you want without any issues.

 on: Today at 05:32:29 PM 
Started by Dave Rosser - Last post by Dave Rosser
In "Classic", open a backup of the old catalogue. It will then convert it and leave the old catalogue untouched.

I have found "Classic" and the new "LRCC" perfectly compatible on the same W10 computer. No stability problems.
I think my problems occured because I installed LRCC first and edited some files with it then installed the new classic which got in a total mess "synchronising"  at the same time as updating the old catalogue. It seemed to be continuously reading from the hard disk till all the 32 gig of memory was full then releasing the memory and starting again.  I would advise anyone to install and run classic,make sure all is ok before installing the new lightroom cc.

Pages: 1 [2] 3 4 ... 10