A possibility to choose the compression-rate for lurawave-files is missing.
nconvert -out lwf -comp_ratio 94 -o C:\AMD\%%.lwf C:\AMD\*.png
converts png-files into lurawave-files, but without compression,
so that they have a greater size than the png-files
with a working switch like -comp_ratio or ...
Search found 20 matches
- Thu Dec 26, 2013 9:07 am
- Forum: NConvert
- Topic: option for the compression-rate of lurawave-files
- Replies: 0
- Views: 1006
- Wed Oct 24, 2012 4:18 pm
- Forum: NConvert
- Topic: small bug in nconvert x64
- Replies: 10
- Views: 2678
Re: small bug in nconvert x64
It's fixed now.

Thanks! (a lot)

Thanks! (a lot)
- Fri Oct 19, 2012 1:21 pm
- Forum: NConvert
- Topic: small bug in nconvert x64
- Replies: 10
- Views: 2678
Re: small bug in nconvert x64
the "Ignoring -p option from command line" message is not from nconvert
After a while I figured out how you ment it probably (without your new comment).
(Because I guessed than that you know your source code that well.)
So the mistake in the source code is not in the XnView-SourceCode,
instead of ...
After a while I figured out how you ment it probably (without your new comment).
(Because I guessed than that you know your source code that well.)
So the mistake in the source code is not in the XnView-SourceCode,
instead of ...
- Thu Oct 18, 2012 11:31 am
- Forum: NConvert
- Topic: small bug in nconvert x64
- Replies: 10
- Views: 2678
Re: small bug in nconvert x64
What?
Take a look at this:

Take a look at this:

- Thu Oct 18, 2012 5:24 am
- Forum: NConvert
- Topic: small bug in nconvert x64
- Replies: 10
- Views: 2678
Re: small bug in nconvert x64
this error message:
Ignoring -p option from command line
As you can see, I didn't use any -p option:
"C:\Program Files (x86)\XnView\nconvert_x64" -out jxr -o C:\Users\%%.jxr C:\AMD\*.png
Ignoring -p option from command line
As you can see, I didn't use any -p option:
"C:\Program Files (x86)\XnView\nconvert_x64" -out jxr -o C:\Users\%%.jxr C:\AMD\*.png
- Mon Oct 15, 2012 7:41 am
- Forum: NConvert
- Topic: small bug in nconvert x64
- Replies: 10
- Views: 2678
Re: small bug in nconvert x64
In Program Files (x86).
There is no 64-bit variant of XnView (yet).
And because it's related, I store the nconvert-executables in the XnView-folder.
(And I renamed them to avoid to confuse them (or to have to copy and delete them again and again).)
There is no 64-bit variant of XnView (yet).
And because it's related, I store the nconvert-executables in the XnView-folder.
(And I renamed them to avoid to confuse them (or to have to copy and delete them again and again).)
- Mon Oct 15, 2012 5:27 am
- Forum: NConvert
- Topic: small bug in nconvert x64
- Replies: 10
- Views: 2678
small bug in nconvert x64
The 32-bit variant of nconvert works without any problems with this command line:
"C:\Program Files (x86)\XnView\nconvert_x86" -out jxr -o C:\Users\%%.jxr C:\AMD\*.png
Do I the same with the 64-bit variant of nconvert that happens:
"C:\Program Files (x86)\XnView\nconvert_x64" -out jxr -o C:\Users ...
"C:\Program Files (x86)\XnView\nconvert_x86" -out jxr -o C:\Users\%%.jxr C:\AMD\*.png
Do I the same with the 64-bit variant of nconvert that happens:
"C:\Program Files (x86)\XnView\nconvert_x64" -out jxr -o C:\Users ...
- Mon Oct 08, 2012 10:07 pm
- Forum: Classic - Bug Reports
- Topic: HD Photo Format is somehow broken
- Replies: 2
- Views: 1130
HD Photo Format is somehow broken
I have a JPG-File with the dimensions 4320x3240(x24).
I store it with XnView 1.99.1 as WDP-File (which means HD Photo) with a quality of 82%.
That works all. But I can not open it with XnView again.
I can't open the new WDP-File with XnView (or with Corel Photo-Paint X6.1 for example).
But it's ...
I store it with XnView 1.99.1 as WDP-File (which means HD Photo) with a quality of 82%.
That works all. But I can not open it with XnView again.
I can't open the new WDP-File with XnView (or with Corel Photo-Paint X6.1 for example).
But it's ...
- Fri Aug 10, 2012 12:45 pm
- Forum: NConvert
- Topic: folder name with spaces
- Replies: 5
- Views: 4098
Re: folder name with spaces
Please try the following syntax:
nconvert commands -D " C:\This Is Just A Folder Name\*.tiff "
I didn't mention it, but I'd tried that already and it didn't work - if I remember me correctly.
Related topics for future reference:
...
The additional links seem... are... I don't know ...
- Tue Aug 07, 2012 4:50 am
- Forum: NConvert
- Topic: folder name with spaces
- Replies: 5
- Views: 4098
Re: folder name with spaces
That with dir /x worked. Thanks!
(That with the help-programs goes in a direction I'm not interested in.)
as an example:
instead of
-D C:\PICTURES\portable stuff\%image folder%\nightly\-77577-\
I now use
-D C:\PICTURES\PORTAB~1\%%IMAGE~2\nightly\-77577-\*.*
and that works.
But I'm still ...
(That with the help-programs goes in a direction I'm not interested in.)
as an example:
instead of
-D C:\PICTURES\portable stuff\%image folder%\nightly\-77577-\
I now use
-D C:\PICTURES\PORTAB~1\%%IMAGE~2\nightly\-77577-\*.*
and that works.
But I'm still ...
- Thu Aug 02, 2012 9:20 pm
- Forum: NConvert
- Topic: folder name with spaces
- Replies: 5
- Views: 4098
folder name with spaces
How do I open files which are located in a folder with spaces in the folder name like
C:\This Is Just A Folder Name\
nconvert commands -D C:\This Is Just A Folder Name\*.tiff doesn't work.
nconvert commands -D "C:\This Is Just A Folder Name\"*.tiff doesn't work either.
I use a batch file for this ...
C:\This Is Just A Folder Name\
nconvert commands -D C:\This Is Just A Folder Name\*.tiff doesn't work.
nconvert commands -D "C:\This Is Just A Folder Name\"*.tiff doesn't work either.
I use a batch file for this ...
- Wed Jul 18, 2012 2:39 am
- Forum: NConvert
- Topic: suggestion: multi-threaded nconvert!
- Replies: 0
- Views: 1539
suggestion: multi-threaded nconvert!
Hi!
I use NConvert now a little bit more often to modify the photos of my digital camera
during the development process of the RAW-files via a batch file.
That works good.
There could be some more effects be available like an intelligent unsharp mask
or a better noise suppressor which doesn't soft ...
I use NConvert now a little bit more often to modify the photos of my digital camera
during the development process of the RAW-files via a batch file.
That works good.
There could be some more effects be available like an intelligent unsharp mask
or a better noise suppressor which doesn't soft ...
- Wed May 02, 2012 3:39 am
- Forum: NConvert
- Topic: getting my batch file to work
- Replies: 7
- Views: 4450
Re: getting my batch file to work
I finally got it working! (This time really.)
value2 for -subsampling is wrong. It's a simple 2. (We have to understand how the documentation is meant.)
The last parameters I've used are:
"C:\Program Files (x86)\XnView\nconvert" -opthuff -q 97 -subsampling 2 -efocus -soften 52 -org_depth -out jpeg ...
value2 for -subsampling is wrong. It's a simple 2. (We have to understand how the documentation is meant.)
The last parameters I've used are:
"C:\Program Files (x86)\XnView\nconvert" -opthuff -q 97 -subsampling 2 -efocus -soften 52 -org_depth -out jpeg ...
- Wed May 02, 2012 2:09 am
- Forum: NConvert
- Topic: getting my batch file to work
- Replies: 7
- Views: 4450
Re: getting my batch file to work
At last I got it working. Here are the parameters:
"C:\Program Files (x86)\XnView\nconvert" -opthuff -q 97 -subsampling value2 -efocus -org_depth -o C:\AMD\sharpened\%% C:\AMD\developed\*.jpg
As you can see it was necessary to use %%. It's undocumented (not like $$) but it works. And the output ...
"C:\Program Files (x86)\XnView\nconvert" -opthuff -q 97 -subsampling value2 -efocus -org_depth -o C:\AMD\sharpened\%% C:\AMD\developed\*.jpg
As you can see it was necessary to use %%. It's undocumented (not like $$) but it works. And the output ...
- Tue May 01, 2012 9:22 pm
- Forum: NConvert
- Topic: getting my batch file to work
- Replies: 7
- Views: 4450
Re: getting my batch file to work
%%? - Did not hear of that, but could be possible.
The -i argument irritated myself. I've read the documentation too (before I read your post) and found the same out as you did.
-i seems not to be "input file" as -o is "output file".
VnView? What's this? Do you have a link for that or is this ...
The -i argument irritated myself. I've read the documentation too (before I read your post) and found the same out as you did.
-i seems not to be "input file" as -o is "output file".
VnView? What's this? Do you have a link for that or is this ...