JPG export/resize from RAW is really bad

[dbarrow]

I have an output profile for web gallery images that resizes to fit within 800x600 at 72 DPI. I had the exact same profile in Bibble and it worked perfectly. In Aftershot, the results are complete crap. There is all kinds of pixelation and posterizing. Just to be sure, I went back to the last version of Bibble to confirm: it worked perfectly. Also, the Aftershot image file sizes are many times larger, thus taking much longer to load. Was it really important to degrade the quality of Bibble when selling it to Corel? What is the solution? I notice there haven't been ANY upgrades. Is Corel just planning to shelve Aftershot like Adobe did to the other RAW processing program I used to use? Corel: Please fix the crappy JPG export function or the program is unusable for me.

[afx]

I have an output profile for web gallery images that resizes to fit within 800x600 at 72 DPI.

Why that 72dpi nonsense?

I had the exact same profile in Bibble and it worked perfectly.

Are you absolutely sure?
Apart from the sharpening bug I can see no difference between Bibble and AS in this regard.

How about posting screen shots of both queue definitions and generated JPGs?

quote]I notice there haven't been ANY upgrades. Is Corel just planning to shelve Aftershot like Adobe did to the other RAW processing program I used to use? [/quote]
A bit premature after two months don't you think?

cheers
afx

[dbarrow]

The 72dpi is how the Bibble preset was configured. It is for web graphics (in a web photo gallery). I have seen that non 72dpi images may not display in some browsers. I thought 72dpi was web standard. I will post some side by side comparisons when I get the other computer (with Aftershot) fired up later.

What is the "sharpening bug"?

[dbarrow]

Here is a side by side comparison between Bibble and Aftershot, with identical jpg export profiles:

Bibble:

http://davidbarrow.com/bibble-aftershot ... bibble.jpg

Aftershot:

http://davidbarrow.com/bibble-aftershot ... ershot.jpg

As you can see, the difference is profound. What happened to the jpg conversion in Aftershot?

[dbarrow]

Bibble:



Aftershot:



As you can see, the difference is profound. What happened to the jpg conversion/export in Aftershot?

[darKing]

And now a side by side comparison of the output batch settings. Hard to belive that these are the same settings.. just look at the terrible jpg compression artefacts.
It also looks like you are not using the same Color Management settings in Bib / Asp. Are you sure your working space in Bibble was "Pro Photo RGB"?

/edit

Even the output spaces of those two pictures are different. The Color Space of the bibble image is "pro photo". Hard to belive that this is the default space for a web output batch in Bibble...
The After Shot Image has a "bibble linear RGB (D50)" whats that? oO

I also checked my output batches in Bib and ASP, none of those has 72dpi as a default setting (which is irrelevant anyway). And both have set sRGB as default color space. You're sure you use default batches? I doubt it.

[afx]

The 72dpi is how the Bibble preset was configured. It is for web graphics (in a web photo gallery). I have seen that non 72dpi images may not display in some browsers. I thought 72dpi was web standard.

72dpi is a historic Adobe nonsense. The only reason why Bibble/AS have a DPI setting in the output is to accommodate a certain broken image editor.
DPI is totally irrelevant for digital images unless you have a specific device that needs a specific DPI number.
Current screens are in the 95-120dpi range.

I will post some side by side comparisons when I get the other computer (with Aftershot) fired up later.

The AS output uses the bibble working space for the web gallery instead of sRGB (exiftools your friend)...
Set your queue to sRGB.

What is the "sharpening bug"?

AS can have some silly color artifacts due to the way they implemented sharpening in AS.
For anything critical, I suggest using Wavelet Sharpen instead.

cheers
afx

[dbarrow]

Thanks. Changing the color space to sRGB seems to have solved the problem. Also, where is "Wavelet Sharpening"?

[SteveCase]

Thanks. Changing the color space to sRGB seems to have solved the problem. Also, where is "Wavelet Sharpening"?

All sorts of plugins.

http://www.aftershotpro.com/plugins/

[Ianr]

JPG export/resize from RAW is really Good ... actually. The headline statement is very misleading to others ... you are having a problem with your settings, it's not that the program is bad.
The speed and flexibility with the output is nothing short of superb, as you will eventually come to see.

Link for you : http://aftershotpro.com/plugins/index.h ... etsharpen3

Ianr

[Tadjio]

Thanks. Changing the color space to sRGB seems to have solved the problem.

You could edit your original posting, change the title to something like "[SOLVED] JPG export/resize from RAW" and add a comment so people are not further misled.

[VIM]

...The headline statement is very misleading to others ... you are having a problem with your settings, it's not that the program is bad...

Webboards about software are FULL of such misleading titles!
Many users tend to blame the software and shout about it while it is often a question of "knowing how to...".

[Jeff Stephens]

I just want to point out that this thread and some other comments to us highlighted a bug in 1.0.0 that will be addressed in our next update. If you create a new output batch, the settings window shows 'sRGB' as the output color space. If you save the batch without changing that setting - it actually does NOT save that setting (bug #1); instead it leaves the setting blank, which reveals another bug (#2) in that an output batch without a color space set will leave the image in ASP's working space. That's never the right answer...

The quick work-around is to do exactly what was done above: open your batch, select 'sRGB' from the output color space dropdown (even if it looks to already be selected) and then save your batch. With this done, you won't see the effects of either of these bugs....

Cheers, Jeff

[bcelasun]

Jeff,
Thanks for visiting here, responding and; most of all, paying attention