dennishh wrote:
I looked all over for them in the Beta, finally found that the gradient and brush have CA removal now. I haven't upgraded still using 3.6 because there are so many problems with 4 with importing libraries and speed.
I don't think the grad and brush tools have CA removal. Can you point that out?
I didn't have any issues with speed or upgrading a catalog. If you download the the trial and try and it doesn't work for you, what do you lose? Nothing.
FlyPenFly wrote:
Ugh, CA removal is useless in the 2012 profile.
In the beta discussions they kept talking about the kind of CA LR could automatically fix and I guess I had the wrong kind. I really didn't understand.
It's not easy. None of the image adjustments will move and the two programs are so different you'll probably have a tough time at first. Then you'll wonder why you ever used Aperture. And this is coming from a Mac guy.
carstenw wrote:
Does anyone here have experience moving an Aperture library to Lightroom, with as much info intact as possible?
If you include develop settings in the word "info", I can imagine that it would probably turn out a nightmare. Tags and other data like that shouldn't be that hard to import into a LR database, but I can't imagine that different RAW developers have crosss-compatible develop settings.
tomrock wrote:
I don't think the grad and brush tools have CA removal. Can you point that out?
I guess he actually meant that the grad and adjustment brush tools have a WB option now?
AhamB wrote:
Does the CA auto-correction rely entirely on lens profiles, or does it measure CA in the image and correct it?
I was wondering how it works too.
Right now with 3.6 version I have to turn the vignetting slider to zero on the lens correction section panel for my adapted z* lenses because it uses the aperture reported from adapter which is fixed and not usually the aperture used. I am betting it is using canned lens CA profiles based on aperture to do CA removal.
corposant wrote:
In LR4, can you have WB adjusted in a grad filter?
More or less. The grad and brush tools have the same adjustments, which include a color temp and tint slider. It doesn't appear to list actual color temp, and instead adjusts it relative to the overall image WB setting. That's probably more intuitive for most things.
FlyPenFly wrote:
So it seems if you want to do purple defringe manually you have to bring it into photoshop and do a local adjustment of desaturating magenta/purple.
You still have the option of using the Defringe parameter in the manual lens corrections pane, in addition to any automatic lens profile corrections. That can sometimes help with purple fringing/longitudinal CA. It doesn't always work perfectly though, and using the "All Edges" option may desaturate some edges in a noticeable, non-desirable way. It just depends on the image and what your quality tolerances are.
Those who rely on Nik filters, stick with LR3 or 4 beta until they correct a bizarre bug that prevent LR4 to launch photos to Nik. Just does not work...holy crap Batman!
It's not easy. None of the image adjustments will move and the two programs are so different you'll probably have a tough time at first.
I was hoping to avoid a google search with a million hits, and I do respect the people on this forum a lot. Anyway, I suppose I will end up writing an Applescript to write a small text file for each image with all the settings intact, and then to read them in again and try to apply them in some sort of sensible manner, maybe skipping a few tough ones.
This will probably take me 6 months to get around to, if I know myself well
Then you'll wonder why you ever used Aperture. And this is coming from a Mac guy.
I doubt this very much. I used Lightroom from pre-version-1 (I was part of the beta program), and up to version 2, and wanted to use version 3, but Adobe mucked up my upgrade so badly I decided to try Aperture. I much prefer it in several ways, especially in colour, but Apple appears to be abandoning their pro programs, so this time around I decided to switch back. I am expecting trouble with colour, and will do a profile if this turns out to be true. I might also use other developers for important images, like RPP or Capture One.
vallejo wrote:
Those who rely on Nik filters, stick with LR3 or 4 beta until they correct a bizarre bug that prevent LR4 to launch photos to Nik. Just does not work...holy crap Batman!
I didn't have any problem with the NIK filters on a Mac. They all work fine.
Lightroom has a lot of good features, and the colours were better in 3 than 2, and I expect are also better in 4 than 3. Anyway, I am soon switching to the D800E, so it is a level playing field for me. The ability for me to make my own profile with equipment I already own is big, and Aperture doesn't offer than.
I like Aperture a lot, but have been frustrated with a few things, top of which is the incredibly slow pace of development, and the amazingly long life span of even obvious bugs. On top of that, no lens profiles, no proper sharpening, lame noise reduction, and so on. I will give Lightroom another shot, and if I don't like it that much, I will probably figure out some way to integrate either Capture One or RPP in a total workflow.
Since I had Lightroom 2, the upgrade was cheap, and anyway, I am sure I can find a friend to take it over if I want that.
I run a Windows 7 64-bit system. When using Nik filters (Viveza, Silver Efex or Dfine) in the Lightroom 4 environment I get a tiff copy of the file to work with. There everything works except for the banding control in Dfine.
The Nik filter issue is a known bug, but only applies in certain situations (typically if PS is not installed) and not only with the Nik plugins (they're simply the most popular of the afflicted plugins). One of the known workarounds is to simply install the PS 5.5 demo.
