Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: 32BT on September 25, 2006, 03:58:52 am
-
Obviously I only had a short chance to test the new beta version and may well have some settings wrong, but it seems the new version is suffering from "ringing" artifacts. Small, 1 pixel wide copies of edges. It's less distinct in the preview, more distinct in a rendered file.
it happens with default settings, and no amount of denoise or reduced sharpening mitigates the problem.
PS. I am glad to see that the product naming hasn't yet trickled down to the application itself. Hope it stays that way...
-
OK, found it: it's a cropping bug. As soon as you adjust the cropping overlay, it messes up the rendering pretty bad...
-
OK, found it: it's a cropping bug. As soon as you adjust the cropping overlay, it messes up the rendering pretty bad...
[a href=\"index.php?act=findpost&pid=77556\"][{POST_SNAPBACK}][/a]
I have not been able to duplicate the problem you report when I'm using the Windows B4 version.
I just cropped a bunch of TIFs (100MB file size scans of 35mm Kodachrome slides) and exported them to JPGs to produce a slide show.
Bud James
North Wales, PA
-
I have not been able to duplicate the problem you report when I'm using the Windows B4 version.
I just cropped a bunch of TIFs (100MB file size scans of 35mm Kodachrome slides) and exported them to JPGs to produce a slide show.
Bud James
North Wales, PA
[a href=\"index.php?act=findpost&pid=77564\"][{POST_SNAPBACK}][/a]
Right, I'm on a Mac (intel), and it seems directly related to RAW development. Apparently TIFs that don't require debayering, don't suffer this problem.
Mind you, other than this, my first impressions are very positive. It's just that this particular problem may be potentially disastrous so thought it prudent to notify immediately.
-
OK, found it: it's a cropping bug. As soon as you adjust the cropping overlay, it messes up the rendering pretty bad...
[a href=\"index.php?act=findpost&pid=77556\"][{POST_SNAPBACK}][/a]
Not sure it is what you are referring to, but there is a known bug in the cropping tool described in the "readme" file that comes with the beta4 download. You might look at that to see if it is a known issue.
Tim
-
Not sure it is what you are referring to, but there is a known bug in the cropping tool described in the "readme" file that comes with the beta4 download. You might look at that to see if it is a known issue.
Tim
[a href=\"index.php?act=findpost&pid=77642\"][{POST_SNAPBACK}][/a]
i've read the document, but I'm not sure what you're referring to?
-
Is this the slowest bloatware ever devised? Answer: it might be on my admittedly ageing Windows machine. Silkypix, itself quite a memory hog, seems lighting fast in comparison.
Looks great, but on a 2 year old Athlon machine with 1.5gb ram, its unuseable.
Quentin
-
Funny, I'm running B4 on a 3 yr old 800 Megahertz iMac & it works just fine. Certainly faster than B3. No complaints--certainly not regarding speed.
-
B4 is not running as fast as fully sorted-out software, but it IS significantly faster than B3 was on my several years old 2.4 Ghz P4 PC.
It did grab a lot of system resources when rebuilding thumbs, though. I couldn't multi-task other software without running out of RAM.
Paul
-
Is this the slowest bloatware ever devised? Answer: it might be on my admittedly ageing Windows machine. Silkypix, itself quite a memory hog, seems lighting fast in comparison.
Looks great, but on a 2 year old Athlon machine with 1.5gb ram, its unuseable.
Quentin
[a href=\"index.php?act=findpost&pid=77683\"][{POST_SNAPBACK}][/a]
I think I'm coming around to Quentin's point of view. B4 keeps grabbing all of my PC system's resources. I also have B4 on my Powerbook and need to check if the same thing happens.
Paul
-
I have B4 installed on my 2 yr old Dell Precision workstaton with dual Xeon 2.8Ghz processors, WinXP Pro, 4GB of RAM and internal SATA disks in a RAID 0 configuration.
It is a little faster than B3, but still kind of pokey. However, it is pretty quick doing RAW conversions. One benefit I think most people aren't considering is that the greatly improved workflow through to printing, assuming that no dust spotting is required, saves a lot of time over the usual ACR+Photoshop workflow.
I'm definitely buying the retail release version and I'm only a amateur.
Bud James
North Wales, PA
-
Oscar,
I haven't noticed that issue (G5 mac). Perhaps you could post a screenshot?
Is this the slowest bloatware ever devised?
[a href=\"index.php?act=findpost&pid=77683\"][{POST_SNAPBACK}][/a]
Perhaps you are suffering from a rootkit or two...
It ain't finished folks, so lets hold the performance judgments 'till it is as complaining about it accomplishes nothing.
-
Is this the slowest bloatware ever devised? Answer: it might be on my admittedly ageing Windows machine. Silkypix, itself quite a memory hog, seems lighting fast in comparison.
Looks great, but on a 2 year old Athlon machine with 1.5gb ram, its unuseable.
Quentin
[a href=\"index.php?act=findpost&pid=77683\"][{POST_SNAPBACK}][/a]
It is worlds faster that the previous beta. Still slow.
-
Oscar,
I haven't noticed that issue (G5 mac). Perhaps you could post a screenshot?
Certainly can:
(http://www.theimagingfactory.com/examples/ringing.jpg)
During the creation of this example I noticed that the cropped image has its pixels shifted by half a pixel which may account for the problem. The problem is obviously exacerbated when output sharpening is applied. As a matter of fact, it makes it simply impossible. Incidently, I was testing several DAM utilities and thus also RAW processors. It turns out that Aperture has an interesting halo problem as well. The same kind of edges as in this example show a rather large desaturated halo, no matter what setting of denoise or chroma blur.
I really like the rendering in LR. The smooth slider seems to get rid of the maze problem formerly present in ACR renderings, yet it retains fine detail better than DPP. I'll see if I can create an example later.
On the less positive side: I believe there is an over abundunce of sliders in LR currently. That needs to be seriously reworked. There should be one way to get a result, and that should be the right way. Now there are several ways to reach a result, and I think that a lot of people will have a hard time explaining the subtle differences between all sliders (if there are differences).
Another example: the saturation sliders. We only need a single saturation slider and it should work as follows: when + it should be vibrance, when - it should be saturation. Additionally, if +, it should simply follow a curve shape, not a gamma shape, this will eliminate the need for some esoteric "skin" color preservation blah blah...
-
I really like the rendering in LR. The smooth slider seems to get rid of the maze problem formerly present in ACR renderings, yet it retains fine detail better than DPP. I'll see if I can create an example later.
Oops, should retract that statement. Forgot to turn on Noise Reduction in the DPP preferences. Setting this to Low produces the good old canon smoothness. Turning it off will result in maze patterns in fine detail. The LR rendition still shows maziness even at Smooth = 100%. The DPP conversion seems to create a strange Bokeh artifact.
(http://www.theimagingfactory.com/examples/dppvslr.jpg)
I suppose this simply remains the digital equivalent of selecting the best film (= raw converter) for the job at hand. There doesn't currently seem a one-size-fits-all converter.
The absolute, most powerful feature of ACR or LR over all other RAW converters is the chromatic aberration correction which seems to be processed in the source space, as opposed to Bibble for example which does so in the destination space which leaves faint remains of the problem. But not all pictures require ca-correction in which case a DPP buttersmooth conversion, even in smaller colorspaces, may be preferable.
-
It ain't finished folks, so lets hold the performance judgments 'till it is as complaining about it accomplishes nothing.
[a href=\"index.php?act=findpost&pid=77826\"][{POST_SNAPBACK}][/a]
How about they stop expecting people to give them feedback on a product that isn't totally useable to evaluate? I know it's a beta, but if someone mentions its slow, then, SUPRISE!, they are giving feedback saying that it needs to be faster. I find it funny that complaining about features denotes "Feedback", but complaining about a lack of speed is just complaining.
*Waits to be attacked*
-
It is worlds faster that the previous beta. Still slow.
[a href=\"index.php?act=findpost&pid=77827\"][{POST_SNAPBACK}][/a]
I found B3 a little faster, but still slow. Maybe there is too much processing going on with the thumbnails, as it just takes over the processor. Possibly its not optimised for older processors. My PC runs everything else reasonably well. I'd like to use it but I can't.
Quentin
-
I found B3 a little faster, but still slow. Maybe there is too much processing going on with the thumbnails, as it just takes over the processor. Possibly its not optimised for older processors. My PC runs everything else reasonably well. I'd like to use it but I can't.
Quentin
[a href=\"index.php?act=findpost&pid=77889\"][{POST_SNAPBACK}][/a]
Sigh...B3 was impressively trouble free. Perhaps in pushing to be ready for Photokina, the development team reached too far. Enough problems have surfaced to take a wait and see approach. When work-arounds are evident or Adobe releases changes, I'll be more inclined to try B4.
-
How about they stop expecting people to give them feedback on a product that isn't totally useable to evaluate? I know it's a beta, but if someone mentions its slow, then, SUPRISE!, they are giving feedback saying that it needs to be faster. I find it funny that complaining about features denotes "Feedback", but complaining about a lack of speed is just complaining.
*Waits to be attacked*
[a href=\"index.php?act=findpost&pid=77870\"][{POST_SNAPBACK}][/a]
Everyone knows it's slow, and they (Adobe and those deeply involved in the project) have stated several times that it is not finished nor optimized but it will be once it is released. Thus...
Complaining about its slowness = non-constructive feedback.
Stating X function doesn't behave correctly = constructive feedback.
Requesting a feature because ___ = constructive feedback.
Etc.
We all have a chance to use a very nice organizer/converter/etc program for free and we all have an equal opportunity for give constructive feedback to make it better. Why then, would anyone want to waste their time complaining about something that everyone knows will be taken care of? All that does is make the complainer look ungrateful of the opportunity they have as well as make it harder to take their other feedback seriously.
-
Everyone knows it's slow, and they (Adobe and those deeply involved in the project) have stated several times that it is not finished nor optimized but it will be once it is released. Thus...
Complaining about its slowness = non-constructive feedback.
Stating X function doesn't behave correctly = constructive feedback.
Requesting a feature because ___ = constructive feedback.
Etc.
We all have a chance to use a very nice organizer/converter/etc program for free and we all have an equal opportunity for give feedback to make it better. Why then, would anyone want to waste their time complaining about something that everyone knows will be taken care of? All that does is make the complainer look ungrateful of the opportunity they have as well as make it harder to take their other feedback seriously.
[a href=\"index.php?act=findpost&pid=77913\"][{POST_SNAPBACK}][/a]
Opportunity? What opportunity? The damn thing won't run on my otherwise healthy Windows system. I don't have a chance to use an unuseable program. My feedback is thus inevitably limited to "Its so slow I can't use it" and seeing as this was not the expected outcome of downloading and installing a reasonably advanced Adobe Beta product, I think I and others thus affected are entitled to say so.
Quentin
-
i've read the document, but I'm not sure what you're referring to?
[a href=\"index.php?act=findpost&pid=77671\"][{POST_SNAPBACK}][/a]
I was finally able to go back and look at the "readme" file again and found the reference I was talking about. Sounds like it does not relate to the issue you are having. "Currently, there is a bug where the Develop settings icon will always display when there is a crop, even if the adjustment settings in Develop have not been changed."
Tim
-
Quentin, I am running Win XP Home, AMD 3000+, 512MB Ram , NVidia 6600GT 128MB card and B4 runs miles quicker than B3 for me.
When I make changes I hardly have to wait at all, whereas with B3 it was like wading through treacle.
I am just hoping that the final product is not too expensive because I will buy this without a second thought.