Bugs item #3445361, was opened at 2011-11-29 09:32 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3445361...

Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: osx Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Nicolas Montgermont (nimon) Assigned to: Nobody/Anonymous (nobody) Summary: pix_write quality not working - osx

Initial Comment: pix_write create exactly the same jpg file when specifying type = 1 or type = 99 see attached captured file (from pix_image help file) for the two quality. GEM: ver: 0.93.git 2687102 OSX 10.6.8 Image saving support: QT

----------------------------------------------------------------------

Comment By: Hans-Christoph Steiner (eighthave) Date: 2011-11-30 07:49

Message: time to build the gmerlin, etc. plugins for Mac OS X?

----------------------------------------------------------------------

Comment By: Nicolas Montgermont (nimon) Date: 2011-11-30 05:59

Message: right... a pity!

----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-11-30 05:54

Message: i checked again, and using an apple app like "Preview", and it behaves the same.

go thank apple that their strive for happy customers does not allow you to save a jpeg (using QuickTime) with "unacceptable" quality.

----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-11-30 03:52

Message: what is the expected behaviour?

[pix_write] will request the backend to write between lossless (quality=100) and "lowest possible quality" (0). the operating system defines what "lowest" quality means. on OSX this would be "codecMinQuality" (whatever that means).

[pix_write] currently does not really allow to set a quality=0 for jpeg images (since "0" automatically means: lossless TIFF), so quality=1 should be a "bit" better than "codecMinQuality".

----------------------------------------------------------------------

Comment By: Nicolas Montgermont (nimon) Date: 2011-11-30 00:45

Message: I can now see a difference between type=1 and type=99 but it is still very low. The image with quality = 1 is still very clean and has a certain weight. Writing the output of example/04.pix/01.image, it gives : type = 1 : 6771 bytes type = 99 : 12 928 bytes

The new result of pix_write for type = 1 is attached.

----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-11-29 10:39

Message: thanks. should be fixed in git with rev.981527f2

----------------------------------------------------------------------

You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3445361...