Question about JPG use in ASP

[ashmoore]

It used to be the case with Bibble that if you output a file to jpeg and reread it back in that the file would be reprocessed with your defaults.
So the jpeg would be resharpened, or whatever default you have set.
Is this still the case with ASP?

I ask because others here are saying you can use Topaz filters (or other external app) as a plugin.
So the workflow would be:-
* import raw file and make your changes
* output the jpeg and use Topaz as the external editor
* Topaz processes file and outputs modified jpeg
* ASP rereads jpeg and processes the jpeg again with its defaults.

Does that sound about right?

My perception is that files should not be returning to ASP after they have been output.

[afx]

It used to be the case with Bibble that if you output a file to jpeg and reread it back in that the file would be reprocessed with your defaults.
So the jpeg would be resharpened, or whatever default you have set.
Is this still the case with ASP?

Well, if you have set up any stuff in rendered defaults, yes that would be applied, that's the purpose of the defaults after all.
But no sane person would put any drastic image adjustment in rendered defaults......

I ask because others here are saying you can use Topaz filters (or other external app) as a plugin.

Nope, that is a major misunderstanding. That is not a plugin!!!!!!

So the workflow would be:-
* import raw file and make your changes
* output the jpeg and use Topaz as the external editor

Yuck, why a JPG and not a TIFF?

* Topaz processes file and outputs modified jpeg
* ASP rereads jpeg and processes the jpeg again with its defaults.

Does that sound about right?

Yes.

My perception is that files should not be returning to ASP after they have been output.

Why???
99.99% of all user would want them to show up in the AS browser.

cheers
afx

[ChrisC]

May I chime in?:

Yes, I would like the new JPGs to show up in AS.
But the combination of defaults for JGPs and the fact that some of us shoot sometimes JPGs (instead of RAW) leads to a problem: I would assume that AS will not distinguish between JPGs from a camera and JPGs coming from an AS outbut batch. So any of these defaults would get applied twice - correct?
> this would limit the reasonable settings in the defaults for JPGs

[afx]

I would assume that AS will not distinguish between JPGs from a camera and JPGs coming from an AS outbut batch. So any of these defaults would get applied twice - correct?

Absolutely. That's why one should not set up any defaults for rendered files.
Use presets.

cheers
afx

[ashmoore]

I am completely sane and I use camera defaults which suit my particular cameras, it saves a couple of clicks per image, but those clicks mount up over thousands of images.
So - I don't reprocess jpegs in ASP - honestly cannot see the point, I have a pixel editor for that, It works on the 2-3% of my images that need it.
However, I do not return jpegs to the same directory as my raws. Mine are output to various folders depending on whether they need work or not.
I have no need of the vestigal DAM features of ASP, it is only a raw processor for me, so defaults work perfectly and save time.

To be honest - still using B5 until next ASP version ships

[ChrisC]

I have no need of the vestigal DAM features of ASP,...

I use the DAM features of AS since B5 and find them very useful. (I do admit that there is room for improvement ) So we are using AS in different ways what is one of its advantages.

[tigloo]

I would assume that AS will not distinguish between JPGs from a camera and JPGs coming from an AS outbut batch. So any of these defaults would get applied twice - correct?

Absolutely. That's why one should not set up any defaults for rendered files.
Use presets.

Could you explain a new user what you mean with this? I know what presets are, but don't understand the hint about "defaults for rendered files". In the manual I only found the settings for export batch jobs, but wasn't sure if that's what you were referring to.

Thanks,

Till

[ChrisC]

Could you explain a new user what you mean with this? I know what presets are, but don't understand the hint about "defaults for rendered files". In the manual I only found the settings for export batch jobs, but wasn't sure if that's what you were referring to.

Here you can read about using defaults (also for rendered files):
http://product.corel.com/help/AfterShot ... tings.html

[afx]

Could you explain a new user what you mean with this? I know what presets are, but don't understand the hint about "defaults for rendered files". In the manual I only found the settings for export batch jobs, but wasn't sure if that's what you were referring to.

AS can be set up to apply defaults for images when they are first visited. These are either RAW defaults that are applied to any RAW image, camera specific defaults that are applied to RAW files from specific cameras or rendered defaults that are applied to TIFF and JPEG files.
While they are quite useful for raw files, they are a bit problematic for rendered/processed files because depending on your setup you might have already plenty of perfectly finished rendered files that will not like to be processed again via your defaults.
So instead of applying defaults, a preset with camera specific adjustments for JPG files is much more sensible.
(If you import files you could create import queues per camera and apply the camera specific preset already there in the import queue)

cheers
afx

[tigloo]

Thanks for the link to the manual and the explanation. This also cleared up the difference between initial and default settings.

[gareth]

One might ask why one class of rendered files was thought to be a good idea.
I scan quite a few old slides and negatives to TIFF in order to process them in Bibble (now in ASP) producing a JPEG.
Having a TIFF default would be useful - but if I do that, my JPEGs are reprocessed?

[afx]

One might ask why one class of rendered files was thought to be a good idea.
I scan quite a few old slides and negatives to TIFF in order to process them in Bibble (now in ASP) producing a JPEG.
Having a TIFF default would be useful - but if I do that, my JPEGs are reprocessed?

Having two sets might be useful.
But, Your TIFF scenario is as broken as the JPEG scenario.

Everyone has his favorite scenario where the defaults might be useful for rendered files. But they all fall flat on their face face that file type shows up in a slightly different context.
And they will....

Best is to not have rendered defaults at all put use presets instead. Much safer...

cheers
afx

[gareth]

Forced to agree, afx ....
not least because scans of slides and scans of negatives result in very different requirements for a default