hello,
using pix_write, pix_writer, or pix_buffer to save a jpeg image, i always got the same result whatever quality asked.
using quality 1 or 100 gives the same image : a good quality, but not perfect.
This is a regression, i think it use to work. Iohannes : is this related to the huge work you did recently?
also, will you also add plugins support for image export? (png export would be nice).
thanks Cyrille
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-20 18:15, cyrille henry wrote:
hello,
using pix_write, pix_writer, or pix_buffer to save a jpeg image, i always got the same result whatever quality asked.
using quality 1 or 100 gives the same image : a good quality, but not perfect.
This is a regression, i think it use to work. Iohannes : is this related to the huge work you did recently?
yes, it definitely is.
also, will you also add plugins support for image export? (png export would be nice).
yes, theoretically it's there already :-) (but see the PS)
both your questions are tightly related (for me), as they involve a more generic way to select and parameterize the image saving plugins.
the framework is basically there, but it's currently unused :-(
the main idea is to have the same "properties" system as we already have for pix_video and pix_record. i guess, the easiest way to specify image formats explicitely, would be using mimetypes (a pre-defined property "mimetype", which you could set to "image/vogel" to save images in vgl-format) for compatibility (and usability) reasons, there should be an auto-mode to automatically select the mime-type based on the filename.
and then of course, plugins would need to specify "how good" they could saving of a certain filename/property combination e.g. the imageTIFF plugin is very good at exporting "TIFF" files, but less so at exporting JPEGs (which it cannot do at all, but at least it would save the image to disk in some format, which might be better than nothing); nevertheless imageMAGICK might be even better at exporting TIFFs, as it could support adding some special tags to the image, the user might want to have included in the image.
fmgasdr IOhannes
PS: though i'm not entirely sure what you mean by "image export" in contrast to what pix_buffer and friends already do.
hello, thanks for the explanation,
it look like you have planed everything, and i can't really help. (can I?)
so for now, i just get a bigger hard drive and export in tiff in order to have better quality images...
cheers, Cyrille
Le 21/06/2011 09:53, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-20 18:15, cyrille henry wrote:
hello,
using pix_write, pix_writer, or pix_buffer to save a jpeg image, i always got the same result whatever quality asked.
using quality 1 or 100 gives the same image : a good quality, but not perfect.
This is a regression, i think it use to work. Iohannes : is this related to the huge work you did recently?
yes, it definitely is.
also, will you also add plugins support for image export? (png export would be nice).
yes, theoretically it's there already :-) (but see the PS)
both your questions are tightly related (for me), as they involve a more generic way to select and parameterize the image saving plugins.
the framework is basically there, but it's currently unused :-(
the main idea is to have the same "properties" system as we already have for pix_video and pix_record. i guess, the easiest way to specify image formats explicitely, would be using mimetypes (a pre-defined property "mimetype", which you could set to "image/vogel" to save images in vgl-format) for compatibility (and usability) reasons, there should be an auto-mode to automatically select the mime-type based on the filename.
and then of course, plugins would need to specify "how good" they could saving of a certain filename/property combination e.g. the imageTIFF plugin is very good at exporting "TIFF" files, but less so at exporting JPEGs (which it cannot do at all, but at least it would save the image to disk in some format, which might be better than nothing); nevertheless imageMAGICK might be even better at exporting TIFFs, as it could support adding some special tags to the image, the user might want to have included in the image.
fmgasdr IOhannes
PS: though i'm not entirely sure what you mean by "image export" in contrast to what pix_buffer and friends already do. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4ATewACgkQkX2Xpv6ydvRU/QCcCpuGHoW5FXl0sMiKIgZsrjiv jTkAnjUAhpWGqA3W2oR0HDqXgUud2LE3 =lMMs -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-21 15:07, cyrille henry wrote:
hello, thanks for the explanation,
it look like you have planed everything, and i can't really help. (can I?)
so for now, i just get a bigger hard drive and export in tiff in order to have better quality images...
quality settings should work again with imageJPEG and imageMAGICK.
fgamsdr IOhannes
Le 21/06/2011 18:40, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-21 15:07, cyrille henry wrote:
hello, thanks for the explanation,
it look like you have planed everything, and i can't really help. (can I?)
so for now, i just get a bigger hard drive and export in tiff in order to have better quality images...
quality settings should work again with imageJPEG and imageMAGICK.
thanks! but to late : i've got more than 100Go of tif file that i'm curently converting to jpg... c
fgamsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4AyZQACgkQkX2Xpv6ydvRkvQCgjjveyD5mhCK7tNqHOwcBevN6 l+wAoOsOlA1UO5GrkIDSS9TbFs45zvfX =1Kvm -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
hello,
i now have an error compiling the svn (rev 4078)
nusmuk@chnry:~/pd/Gem/src$ make Making all in Base make[1]: entrant dans le répertoire « /home/nusmuk/pd/Gem/src/Base » make all-am make[2]: entrant dans le répertoire « /home/nusmuk/pd/Gem/src/Base » /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -DHAVE_VERSION_H -DPD -I/usr/include/FTGL -I/usr/include/freetype2 -g -O2 -fPIC -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -mmmx -MT libBase_la-GemPixUtil.lo -MD -MP -MF .deps/libBase_la-GemPixUtil.Tpo -c -o libBase_la-GemPixUtil.lo `test -f 'GemPixUtil.cpp' || echo './'`GemPixUtil.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DHAVE_VERSION_H -DPD -I/usr/include/FTGL -I/usr/include/freetype2 -g -O2 -fPIC -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -mmmx -MT libBase_la-GemPixUtil.lo -MD -MP -MF .deps/libBase_la-GemPixUtil.Tpo -c GemPixUtil.cpp -fPIC -DPIC -o .libs/libBase_la-GemPixUtil.o GemPixUtil.cpp: In member function ‘virtual void imageStruct::fromRGBA(const unsigned char*)’: GemPixUtil.cpp:621: error: invalid conversion from ‘const unsigned char*’ to ‘unsigned char*’ GemPixUtil.cpp:621: error: initializing argument 1 of ‘void RGBA_to_UYVY_SSE2(unsigned char*, size_t, unsigned char*)’ GemPixUtil.cpp: In member function ‘virtual void imageStruct::fromUYVY(const unsigned char*)’: GemPixUtil.cpp:1459: error: invalid conversion from ‘const unsigned char*’ to ‘unsigned char*’ GemPixUtil.cpp:1459: error: initializing argument 1 of ‘void UYVY_to_RGB_SSE2(unsigned char*, size_t, unsigned char*)’ GemPixUtil.cpp:1503: error: invalid conversion from ‘const unsigned char*’ to ‘unsigned char*’ GemPixUtil.cpp:1503: error: initializing argument 1 of ‘void UYVY_to_RGBA_SSE2(unsigned char*, size_t, unsigned char*)’ make[2]: *** [libBase_la-GemPixUtil.lo] Erreur 1 make[2]: quittant le répertoire « /home/nusmuk/pd/Gem/src/Base » make[1]: *** [all] Erreur 2 make[1]: quittant le répertoire « /home/nusmuk/pd/Gem/src/Base » make: *** [all-recursive] Erreur 1
cheers,
Cyrille
Le 21/06/2011 18:40, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-21 15:07, cyrille henry wrote:
hello, thanks for the explanation,
it look like you have planed everything, and i can't really help. (can I?)
so for now, i just get a bigger hard drive and export in tiff in order to have better quality images...
quality settings should work again with imageJPEG and imageMAGICK.
fgamsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4AyZQACgkQkX2Xpv6ydvRkvQCgjjveyD5mhCK7tNqHOwcBevN6 l+wAoOsOlA1UO5GrkIDSS9TbFs45zvfX =1Kvm -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-21 20:07, cyrille henry wrote:
hello,
i now have an error compiling the svn (rev 4078)
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DHAVE_VERSION_H -DPD -I/usr/include/FTGL -I/usr/include/freetype2 -g -O2 -fPIC -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -mmmx -MT libBase_la-GemPixUtil.lo -MD -MP -MF .deps/libBase_la-GemPixUtil.Tpo -c GemPixUtil.cpp -fPIC -DPIC -o .libs/libBase_la-GemPixUtil.o GemPixUtil.cpp: In member function ‘virtual void imageStruct::fromRGBA(const unsigned char*)’:
ok, i understand the reason for the problem (me suddenly starting to flag constant parameters as "const", which makes some problems with legacy code that did not do so)
i had fixed all issues visible in my compilation, but it turns out i had compiled without sse2 support (and without Altivec support as well), and there were some functions hidden in the optimized routines that slipped my attention.
the problems should be fixed now (rev.4080)
what i don't understand is, why your system builds SSE2 code at all. you probably want that anyhow, so you don't care so much; but there is no indication in your compiler-flags telling it to enable sse (should be "-msse2" somewhere) which compiler are you using? here it says $ g++ --version g++ (Debian 4.6.0-10) 4.6.1 20110526 (prerelease)
mfgasdr IOhannes
hello,
i'm still using ubuntu 10.04 (and i'll probably use it until 12.04) so, i've got an older gcc than you
g++ --version g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3
and yes, everything compile. (have no time to test everything now)
thanks c
Le 22/06/2011 10:29, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-21 20:07, cyrille henry wrote:
hello,
i now have an error compiling the svn (rev 4078)
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DHAVE_VERSION_H -DPD -I/usr/include/FTGL -I/usr/include/freetype2 -g -O2 -fPIC -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -mmmx -MT libBase_la-GemPixUtil.lo -MD -MP -MF .deps/libBase_la-GemPixUtil.Tpo -c GemPixUtil.cpp -fPIC -DPIC -o .libs/libBase_la-GemPixUtil.o GemPixUtil.cpp: In member function ‘virtual void imageStruct::fromRGBA(const unsigned char*)’:
ok, i understand the reason for the problem (me suddenly starting to flag constant parameters as "const", which makes some problems with legacy code that did not do so)
i had fixed all issues visible in my compilation, but it turns out i had compiled without sse2 support (and without Altivec support as well), and there were some functions hidden in the optimized routines that slipped my attention.
the problems should be fixed now (rev.4080)
what i don't understand is, why your system builds SSE2 code at all. you probably want that anyhow, so you don't care so much; but there is no indication in your compiler-flags telling it to enable sse (should be "-msse2" somewhere) which compiler are you using? here it says $ g++ --version g++ (Debian 4.6.0-10) 4.6.1 20110526 (prerelease)
mfgasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4Bp80ACgkQkX2Xpv6ydvTPDwCgv5riC/WuCnWwRaNiWHu48Cr1 BrQAoMvWpdtLQhnTTyxSWvjdHNtDbEyD =J9J/ -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-
cyrille henry -
IOhannes m zmoelnig