Can be also used in other compatible plugin hosts (The Gimp, Irfanview, Xnview, Photo paint ....)
Allow you to apply the algorithm to the selected portion of the image and not only to the full image.
Important: It reduces the number of colors in a image, but don't change a RGB image to indexed color. If you want to use it to change an image from RGB to index color, you should use your image tool to change the image mode, after running XImagic quantizer.
Besides its practical use, this plug-in is also a great learning tool.
Also by using it, you can get to color amounts that are less than 16 and those that aren't powers of 2.
Oh, and I've found a bug... I don't know if it's with the way XnView handles plugins or the actual plugin itself, but here's test.
Take this image and put the XnView zoom level at 100%. Now in the plugin, do a Scolorq conversion @ 16 colors | Filter: 3 | Dithering: 10
Ignore the message and wait a bit as your CPU crunches away. (we could really use some OpenCL support for that...)
Now open the original image again, but set XnView's zoom to 150%. Do the same Scolorq conversion as the last one with the same settings and all.
Notice that the blue background is of considerably lower quality in the 2nd one. But this was only a zoomed image, not resized. So why did the results come out so different?
Last edited by NM64 on Wed Feb 04, 2009 2:21 am, edited 1 time in total.
This plugin tries to be a learning as well as working tool and this is the reason it includes not only the best methods, but all those that could be of interest.
Let me try to help with the two questions I found
XnTriq - About getting the same results from two runs.
SColorQ uses random numbers to fill the initial palette, which is very important for the result. As a consecuence the results are diferent in each run. The random seed used is a second clock which means the results are similar when you make two runs very near in time.
In quantization methods, there is very common to start with an initial random palette. Older methods such as Octree, medians and olders ones don't need this approach.
nintendomaniac64 - Zoom in XNView.
By default XNView (at least mine) comes with high quality zoom selected only for reductions and apparently SColorQ produced images work badly with the low quality zoom, I've also surprised with that.
Go to Tools->Options->View->High Quality Zoom and check if Enlarge is marked.
------------------
I hope this helps.
It will an update of the plugin available today, with some code optimizations in the scolorq algorithm, which reduces the time 35% more or less.
If you know any other quantization o dithering algorithm which should be included, please let me know.
I suspect from the tests I made with your image, that the zoom is only a coincidence. As you say, there is no difference in the data and could not affect the image processing.
The initial palette problem is even more serious than I think, at least with your image. In one of the tests, I get an image with the windows logo in only one color.
I'll try to test the method with not random initial palettes and if it works I'll add a option to choose the initial palette generation method.
brodriguez wrote:This plugin tries to be a learning as well as working tool and this is the reason it includes not only the best methods, but all those that could be of interest.
Let me try to help with the two questions I found
XnTriq - About getting the same results from two runs.
SColorQ uses random numbers to fill the initial palette, which is very important for the result. As a consecuence the results are diferent in each run. The random seed used is a second clock which means the results are similar when you make two runs very near in time.
In quantization methods, there is very common to start with an initial random palette. Older methods such as Octree, medians and olders ones don't need this approach.
Thanks for your explanations. Playing with Ximagic Quantizer has already taught me a thing or two
One very frustrating thing with this plugin (especially when trying to test 7 compare different options) is that it refuses to remember any settings from one use to the next.
Most photoshop filters store the parameter values between runs using a service from the plugin host. Xnview, IrfanView or GIMP don't have this service.
Some photoshop plugins, f.i. Harry's filters, store the values apparently bypassing photoshop. I'll try to add this function in the future.
I thought it might just be an xnview thing at first, but I also tried it in paint shop pro before posting that last message. All other photoshop plugins I have remember their setting when I use them in psp, even though some of those same plugins don't remember when I use them in xnview.
I tested this plugin on a quad-core PC hoping to see some uber-speed processing and I was dissapointed at the lack of efficient multi-core scaling. I don't know exactly how long it took, but I'm pretty sure it was still over 30 seconds or so. (now we could REALLY use some OpenCL )
There is a new version of the plugin available (1.3) which reduces scolorq processing time around 50%-40%. Now the random palette changes more quickly and it is easier to find a good looking result.
Also a note was added in the main page about SColorQ random results.
nintendomaniac64: Yes the plugin don't speed up on multicore processors. The work needed to make it use multicore only make some sense on SColorQ since the other methods are quick enough, and SColorQ is not an easy candidate to multicore processing.