XnView Software

The next step would be to run several instances of guetzli in parallel as soon as more than 1 image file is available. However, the total number should be limited since guetzli uses lots of memory. I have to work for it, I am NOT a programmer.
If someone is interested I can provide the file. Use ...

In the meantime, I have programmed a small GUI for CUDA-guetzli with Visual Basic, where you can set the image quality and then automatically compress all jpg, png, tif or alternatively all image files which are located in the program folder. Since guetzli also removes all copyright notices, I also ...

No, please. By far too dark.

m.Th. wrote: Sun Nov 26, 2023 5:24 pm I opened a ticket with Windows' team.
Vote here!
https://aka.ms/AAnt6p4

Thanks. Done.

I have built guetzli with autodetection of best mode from the start.

You can download it from here https://github.com/doterax/guetzli-cuda-opencl/issues/11

If you experience some problems with it, you can write it in this issue.

Enjoy.


doterax, you are the hero of the day! Thank you, thank ...

Finally, I did it. I got a working „auto“ as well as a „CUDA“ exe which is dependent from 5 dll files (don’t know why visual studio does not merge, I have chosen static exe). However, it does not work with XNview since I get an error message. Obviously, XNview sends some additional parameters to the ...

The solution would be (citation from author):

if you can clone&rebuild the source, you can change the default parameter of g_mathMode which is in the file clguetzli.cpp, change it to MODE_CUDA and rebuild it. (End of citation).

Unfortunately, I did not manage to compile it after 2 days of hard ...

--c ist just the „optimised“ procedure which speeds up about 2x. Check the table here:
https://github.com/doterax/guetzli-cuda-opencl

I think --auto is the switch for autodetection. This does not help for the use in XNview, since it is not possible to use any switch.


no --auto mode in ...

--c ist just the „optimised“ procedure which speeds up about 2x. Check the table here:
https://github.com/doterax/guetzli-cuda-opencl

I think --auto is the switch for autodetection. This does not help for the use in XNview, since it is not possible to use any switch.

Some more info, also for the development team from XNView MP:
I just contacted one of the developers with the question how to introduce the CUDA-guetzli into XNView as a plugin instead of the normal (slow) guetzli. The issue is that CUDA-guetzli needs the extra command "--cuda" in order to activate ...

Just started to play around with guetzli a few days ago. The jpg files created by guetzli are quite small.
The normal version is by far too slow, see my previous post.
Currently, I use CUDA-guetzli the following way for batch-conversion of 1 or more than 1 files:

1) Download the cuda-version of ...

I think the CUDA version will NOT work with XN_View by simply exchanging the exe file in the plugin folder, since the CUDA version needs the parameter --CUDA in order to work 20x faster. I dont see any option how to set this parameter in XN_View. It simply calls the exe file from the plugin folder ...

But this should not work. However, if I chose quality below 84 and "progressive", I get an exported jpg anyway. Whats going on? Is guetzli bypassed in thess cases?

Hello,
the "save as guetzli jpg" option is extremely slow on almost each computer. 20 Mpix files need about 20 minutes. This is anything but practical in everyday use.

There is a cuda version of guetzli available with is way faster (25-40x acording to the developers) than the original one:
https ...

Hello,
when using the "save as" to save a guetzli-compressed jpg, I can choose quality between 0 and 100 as well as "progressive" jpg. However, Guetzli does not support that. Whats going on here and why is it possible without getting an error message that guetzli needs quality setting >= 84?
Thanks ...