Page 1 of 1

Incomplete "export for nconvert"

Posted: Sun Dec 01, 2019 11:04 am
by AnyOne
In order to automate my workflow I wanted to use the button "export for nconvert".
My workflow includes crop, resize, watermark, converting png to jpg.
Unfortunately, the exported batch for nconvert is missing important parameters to be equivalent to the treatment using XnConvert.
Parameters for crop and resize are all exported, but for watermark and jpg, some are missing.

Here's an extract of the config file (*.xbs) that show which parameters are not exported to batch file:

Code: Select all

    <Watermark ... no_alpha="false" delta_x="0" delta_y="-5" perc="80" size="3" ... />
    <JPEG ... optimizeHuffman="true" DCTMethod="2" subSampling="2" smoothFactor="0" .... />
When I tried to manually add these parameters to the batch file, I noticed that there is even no parameter offered by nconvert for stretching a watermark to a given percentage!

Could you please confirm my observations and tell me if this will be fixed in future versions?

(Merci en avance pour toutes les réponses)

Re: Incomplete "export for nconvert"

Posted: Fri Dec 06, 2019 12:08 pm
by xnview
AnyOne wrote: Sun Dec 01, 2019 11:04 am When I tried to manually add these parameters to the batch file, I noticed that there is even no parameter offered by nconvert for stretching a watermark to a given percentage!
currently no way, other settings are missing?

Re: Incomplete "export for nconvert"

Posted: Sat Dec 14, 2019 9:09 am
by AnyOne
I pointed out 9 parameters that don't get exported to batch by xnconvert.
And there is at least one of them missing for nconvert.

May I ask: what is the problem to add a parameter to nconvert for a function xnconvert offers?
Are they not based on the same core function code?

Re: Incomplete "export for nconvert"

Posted: Mon Dec 16, 2019 1:14 pm
by xnview
AnyOne wrote: Sat Dec 14, 2019 9:09 am I pointed out 9 parameters that don't get exported to batch by xnconvert.
And there is at least one of them missing for nconvert.
which ones?
May I ask: what is the problem to add a parameter to nconvert for a function xnconvert offers?
Are they not based on the same core function code?
not the same code, it's why i think to do that