1.94.2: last used settings of batch processing not stored

[Guest]

often i'm editing (resampling) and converting many images... i'm using batch processing. in previous versions, when i set output (e.g. JPEG 80%, progressive ... etc etc) these values were stored and when i run batch processing dialog again, there were last used values. now, there are "default" values from main app settings... this is little bit anoying - when i want to process many different files, i have to change it many times...

also i have discovered, that "saving script" did not affect transformations or some specific settings. also when i set "output directory" e.g. to "foo/" images are not processed to "./foo/" directory (active directory with processed files), but to "/directory/where/is/script/stored/foo/" ... this is little bit confusing...

... so i can not use scripting (( now i have to change settings all the time, over and over :'(

[oops66]

often i'm editing (resampling) and converting many images... i'm using batch processing. in previous versions, when i set output (e.g. JPEG 80%, progressive ... etc etc) these values were stored and when i run batch processing dialog again, there were last used values. now, there are "default" values from main app settings... this is little bit anoying - when i want to process many different files, i have to change it many times...
also i have discovered, that "saving script" did not affect transformations or some specific settings. also when i set "output directory" e.g. to "foo/" images are not processed to "./foo/" directory (active directory with processed files), but to "/directory/where/is/script/stored/foo/" ... this is little bit confusing...
... so i can not use scripting (( now i have to change settings all the time, over and over :'(

It's the normal behavior for this function, if you often use the same setting for batch processing, you have to store a .xbs file to save your batch settings sample (with "Save" not "Export"), then call this .xbs for your next bach processing.
(This doesn't affect the normal use of Xnview settings and it's normal)

[wdolek]

oops66: i know, there is such function - saving .xbs but as i wrote - this storing of batch did not store all settings for resample (resize) for me...

i have simple web gallery... when i have photos from digicam, i resize it to 800x600px, matching width and height, JPEG 90%, Progressive, ... and then i'm making thubs which has height 80px and JPEG 70% ...
when i save batch, there is no info about resizing stored (first i set everything and than save batch).

and thing i mentioned - when i set "output directory" to "./foo/", i want to output resapmpled files to "active/dir/foo" and not to "dir/where/script/stored/foo" ... and i don't want to use fullpaths...
(directory with source photos "2008-01-01_FooEvent" - i want to make small images to "2008-01-01_FooEvent/gallery/" and thumbs to "2008-01-01_FooEvent/gallery/thumbs" - and of course, that there are many more "event" directories )

[oops66]

I also sometimes use this function too, and I do not have your problems (no info about resizing stored, ...) :


So, I do not know why your xbs data are not all stored.

[wdolek]

oops66: well, but there is still "issue" with output path... now, i have to use full paths (which i can't - in this case i would have to edit script for every directory !) ... or copy script file to every proccessing directory (and it is little bit... uhm... lame)

[oops66]

oops66: well, but there is still "issue" with output path... now, i have to use full paths (which i can't - in this case i would have to edit script for every directory !) ... or copy script file to every proccessing directory (and it is little bit... uhm... lame)

Like my example above, I do not have to use the full path, just "4-emails" and that works on my system.

Well, if you want to have more chances to see your problems resolved, the best solution is to describe with more accuracy your customized settings and the way to reproduce these bugs, maybe like my topic above (with screen captures).
Because I can not reproduce them.
Which OS and XnView version ?

[wdolek]

oops66: well then... there are some screenshots (but i thinks it is not neccessary):

now, i have directory with images located on "D:\_foobar"... and i want to make some transformations and store result into "D:\_foobar\test"...


i start xnview, locate files, select them, press Ctrl-U... load script, which is located on "D:\myscript.xbs"


after processing, i can see, where is new "test" directory placed - it is placed to "D:\test" not to "D:\_foobar\test"


there is source of xbs


of course, this is simple example, this does not work with "./test/" neather does not work with complicated paths ("D:\foo\bar\my_photos" -> "D:\foo\bar\my_photos\transformed"; with script stored on "C:\omni\data\script.xbs")... everytime are processed files stored relatively to script, not to source data...

btw: running on Windows XP Pro, SP3...

[helmut]

Not sure whether this helps:
$ stands for the current browser directory, so if you want to store your output files in a subfolder 'test' of the current folder, you specify '$/test' as ouput directory.

[oops66]

OK, I have not these 2 bugs on my system, and here my .xbs file like this:

Code: Select all

resize( 1 lanczos 700 0 0 1 0 )
autocontrast( )
autolevels( )
clean( 86 )
settings( 3 0 1 1 0 0 )
output_path( 4-emails )
output( jpeg 80 1 1 2 2 0 1 )

...when i save batch, there is no info about resizing stored Sad (first i set everything and than save batch)...

Yes, strange you do not have any info into your xbs file about the resize function.

...now, i have directory with images located on "D:\_foobar"... and i want to make some transformations and store result into "D:\_foobar\test"...

Your output path line is like mine but i don't have this bug too....
So I don't know and I can't help you!

Is someone can confirm these Bugs into XP ?
Pierre, has you ever heard about a such problem ?

[wdolek]

oops66: i did not set any transformation on this "test"... i was trying to set it and now in latest version it is ok... i had problems with some of previous version - and storing all properties to xbs file... now i have just problem with that path...

i will try to put $ to path as helmut wrote...

PS: how do you use xnview under linux? i was trying it and gui was horrible :s and whole application was little bit unstable ... but... it was long time ago...

[oops66]

oops66: i did not set any transformation on this "test"... i was trying to set it and now in latest version it is ok... i had problems with some of previous version - and storing all properties to xbs file... now i have just problem with that path...

i will try to put $ to path as helmut wrote...

PS: how do you use xnview under linux? i was trying it and gui was horrible :s and whole application was little bit unstable ... but... it was long time ago...

FYI:The behavior is a little bit different, but XnView 1.9X (as Windows MP version) works almost perfectly under Linux and Wine (only few minor bugs for the moment for me, the GUI is ~like in Windows and the stability is fine), the Wine project is under development, a new version comes out every couple weeks, then it should be better and better.

[helmut]

... PS: how do you use xnview under linux? i was trying it and gui was horrible :s and whole application was little bit unstable ... but... it was long time ago...

I guess you have tried the final version on Linux which uses OSF Motif. As oops66 has pointed out there's a Multiplatform version of XnView under development which looks and feels pretty much like the Windows version, see forum XnView MP for more details.