[BUG] Noise Ninja : first pixel line bug

[binoyte]

When I use NN, the first pixel line (on the left or on the top, depending on the orientation) is weird.
On full size batch this not a problem, 1 pixel over 4000 or more, I can't see it. But for web publication, 1 pixel over 600 or 800, this is more annoying.

Whatever the NN value, but if I uncheck NN, no more weird first line.

Is this a known bug ? It is also the same, with bibble.


For instance,

With an Olympus E-3

Magnify :

With a Nikon D-300s

Magnify :

[gareth]

I believe this is a very old Bibble bug 1822
(no comment ! )
Oddly - I have not had this effect but several people have reported it.

[binoyte]

OK.
So I'll avoid using NN.

[guilc]

Is this really critical to crop ONE pixel line ?
ASP/Bibble give you usually more pixel than competitors that automatically do a crop in your back, exactly to hide such artifacts due to some algorithms that work not at pixel level but at pixel group level (and so create artifacts at image edge). Cropping one pixel will certainly not kill kittens ! And will not strip too much data

[KeithR]

Is this really critical to crop ONE pixel line ?

If you've got a few hundred converted files and need to check every last one of them first for this problem, then yes, it could easily be "critical". It's especially problematic for people who create stitched panoramas.

exactly to hide such artifacts

Nope, or it would happen with ever ASP/Bibble conversion, and it would happen when Noise Ninja wasn't activated.

It's because of people like you, who laugh off such problems as non-issues, that they exist for so long. This is a bug, it's probably older than you, and it should have been fixed years ago.

[gareth]

@binoyte :
Where you have the problem, try using wavelet denoise plugin instead ... it flattens the image less but may be suitable for you.....
That mushroom for instance -- might end up sharper ....

[spoilerhead]

funny enough: i can reproduce it here, but id disappears when i turn of sharpening.

[spoilerhead]

even funnier:
NN on, sharpening on -> 1-2 pixel bug
enabling Wavelet Denoise with all settings to 0 (i.e. do nothing) bug is gone :S

[gareth]

Perhaps that explains why I don't see it ... I haven't used internal sharpening since wavelet sharpening came out in Bibble.
I am still undecided as to which images work better in NN and WavDeNoise so I have some of each.

Sounds like a rounding error somewhere?

[klaxian]

I'm getting this problem too. When working with hundreds and thousands of images, cropping each one by 1 pixel is time consuming and shouldn't be necessary. I suppose I will look into WavDeNoise. Please fix this

[binoyte]

I just posted a report on the Monkey. But I don't except any change.

[KeithR]

I just posted a report on the Monkey. But I don't except any change.

Right enough - it's not as if the devs haven't been well aware of this bug for a long, long time...

Let's hope the Corel Way is actually to fix bugs, rather than ignoring them in favour of spending development time on gimmicks, bells and whistles like an "improved" plugin SDK, which was surely the Bibble way.

Ignoring Noise Ninja in favour of Wavelet Denoise is no solution: it's a decent enough plugin, but it's not NN; and more to the point, many of us paid extra over the cost of Bibble/ASP for a registered version of NN purely to use in Bibble/ASP, money which has been thrown away if we've got to turn it off in order to work around an ancient bug.

A completely unacceptable solution, no matter how well-intentioned.

As I suggest above, one of the reasons this bug still exists is undoubtedly because of the time the devs spent fannying around with improvements to the plugin SDK instead of bug-fixing, but this just means plugins become a crutch for the lack of proper fixes.

[wgo]

Same annoying first-line(s) here. Even in scaled down versions ... heavily visible.

I circumvented this by cropping output:
Jpeg-output: Postprocessing: open with jpeg-shave.sh

-----------8<------------------------
#!/bin/sh
convert -shave 2x2 "$1" "$1".tmp
mv "$1".tmp "$1"
----------->8------------------------


kind regards
W.

[klaxian]

If you use "mogrify" instead of "convert", you don't need the shell script wrapper. Mogrify is meant to work on a group of files and modify them instead of creating new files. Convert is the opposite. Both are part of the ImageMagick package. Cheers.

[spoilerhead]

try my above observation of just enabling wavelet denoise (with setting to 0)