Hi all,
No matter what I try I can't get [pix_write] to do much more than create corrupted .tiffs that won't open or just crash Pd. Looks like it's missing gem.conf?
open: /etc/pd/gem.conf: No such file or directory open: /home/research/.pd/gem.conf: No such file or directory open: ./gem.conf: No such file or directory pd: tif_dirwrite.c:2084: TIFFWriteDirectoryTagCheckedRational: Assertion `value>=0.0' failed. Pd: signal 6
Running Pd Extended 0.43.4 64 bit on Ubuntu 14.04. I know the 64 bit is buggy but according to my searching [pix_write] has had issues for a while?
Is this is known issue? Should I log it to the bug tracker?
cheers
On 06/18/2014 02:58 AM, Richie Cyngler via Pd-list wrote:
Hi all,
No matter what I try I can't get [pix_write] to do much more than create corrupted .tiffs that won't open or just crash Pd. Looks like it's missing gem.conf?
open: /etc/pd/gem.conf: No such file or directory open: /home/research/.pd/gem.conf: No such file or directory open: ./gem.conf: No such file or directory pd: tif_dirwrite.c:2084: TIFFWriteDirectoryTagCheckedRational: Assertion `value>=0.0' failed. Pd: signal 6
Running Pd Extended 0.43.4 64 bit on Ubuntu 14.04.
I know the 64 bit is buggy
why? what? what exactly are you referring to with "the 64th bit"? how is it buggy?
but according to my searching [pix_write] has had issues for a while?
if it does has issues with PdX-0.43.3 then it will have these issues forever. i don't think anybody will make a bugfix version of this PdX release ever...rather a new shiny PdX-0.45.6 might come out...
in any case:
- [pix_write] is deprecated in favour of [pix_writer] (which takes the
incoming PIX to write, rather than creating a snapshot of the current framebuffer). the deprecation happened because [pix_write] is flawed by design rather than any bugs.
- which imageplugins are you using? search for files called
"gem_image*.so" in your extra/Gem/ folder. if you have both gem_imageTIFF.so and gem_imageMAGICK.so try disabling one of them (just rename it to something not starting with "gem_" && not ending with ".so, e.g. gem_imageTIFF.so.disabled) and see if it helps; if not try disabling the other one. the MAGICK plugin should be the preferred one.
fgamsdr IOhannes
Hi IOhannes,
I was referring to the message that comes with this version of Pd-X.
From the console: *WARNING: 64-bit builds are still beta, some libraries
are known to have serious issues (cyclone, maxlib, moonlib, moocow, pdp, bsaylor, etc.) For more info, see the README.txt in '64-bit-warning-plugin' in the Help Browser*
Thanks for your help I followed your instructions and found that I have both gem_imageTIFF.so and gem_imageMAGICK.so so I disabled gem_imageTIFF.so and now Pd no longer crashes however "GEM: Unable to save image..." with [pix_write]. I tried [pix_writer] but it doesn't respond to a [file <name>( or a [bang( and there is no help that I can find. Would you mind explaining how to use [pix_writer] please. Then if I can get it working I'd be happy to write a help patch for it.
cheers
On Wed, Jun 18, 2014 at 5:06 PM, IOhannes m zmölnig pd-list@lists.iem.at wrote:
On 06/18/2014 02:58 AM, Richie Cyngler via Pd-list wrote:
Hi all,
No matter what I try I can't get [pix_write] to do much more than create corrupted .tiffs that won't open or just crash Pd. Looks like it's
missing
gem.conf?
open: /etc/pd/gem.conf: No such file or directory open: /home/research/.pd/gem.conf: No such file or directory open: ./gem.conf: No such file or directory pd: tif_dirwrite.c:2084: TIFFWriteDirectoryTagCheckedRational: Assertion `value>=0.0' failed. Pd: signal 6
Running Pd Extended 0.43.4 64 bit on Ubuntu 14.04.
I know the 64 bit is buggy
why? what? what exactly are you referring to with "the 64th bit"? how is it buggy?
but according to my searching [pix_write] has had issues for a while?
if it does has issues with PdX-0.43.3 then it will have these issues forever. i don't think anybody will make a bugfix version of this PdX release ever...rather a new shiny PdX-0.45.6 might come out...
in any case:
- [pix_write] is deprecated in favour of [pix_writer] (which takes the
incoming PIX to write, rather than creating a snapshot of the current framebuffer). the deprecation happened because [pix_write] is flawed by design rather than any bugs.
- which imageplugins are you using? search for files called
"gem_image*.so" in your extra/Gem/ folder. if you have both gem_imageTIFF.so and gem_imageMAGICK.so try disabling one of them (just rename it to something not starting with "gem_" && not ending with ".so, e.g. gem_imageTIFF.so.disabled) and see if it helps; if not try disabling the other one. the MAGICK plugin should be the preferred one.
fgamsdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
here is pix_writer help patch. cheers c
Le 23/06/2014 03:04, Richie Cyngler via Pd-list a écrit :
Hi IOhannes,
I was referring to the message that comes with this version of Pd-X. From the console: /WARNING: 64-bit builds are still beta, some libraries are known to have serious issues (cyclone, maxlib, moonlib, moocow, pdp, bsaylor, etc.) For more info, see the README.txt in '64-bit-warning-plugin' in the Help Browser/
Thanks for your help I followed your instructions and found that I have both gem_imageTIFF.so and gem_imageMAGICK.so so I disabled gem_imageTIFF.so and now Pd no longer crashes however "GEM: Unable to save image..." with [pix_write]. I tried [pix_writer] but it doesn't respond to a [file <name>( or a [bang( and there is no help that I can find. Would you mind explaining how to use [pix_writer] please. Then if I can get it working I'd be happy to write a help patch for it.
cheers
On Wed, Jun 18, 2014 at 5:06 PM, IOhannes m zmölnig <pd-list@lists.iem.at mailto:pd-list@lists.iem.at> wrote:
On 06/18/2014 02:58 AM, Richie Cyngler via Pd-list wrote: > Hi all, > > No matter what I try I can't get [pix_write] to do much more than create > corrupted .tiffs that won't open or just crash Pd. Looks like it's missing > gem.conf? > > open: /etc/pd/gem.conf: No such file or directory > open: /home/research/.pd/gem.conf: No such file or directory > open: ./gem.conf: No such file or directory > pd: tif_dirwrite.c:2084: TIFFWriteDirectoryTagCheckedRational: Assertion > `value>=0.0' failed. > Pd: signal 6 > > Running Pd Extended 0.43.4 64 bit on Ubuntu 14.04. > I know the 64 bit is buggy why? what? what exactly are you referring to with "the 64th bit"? how is it buggy? > but according to my searching [pix_write] has had issues for a while? if it does has issues with PdX-0.43.3 then it will have these issues forever. i don't think anybody will make a bugfix version of this PdX release ever...rather a new shiny PdX-0.45.6 might come out... in any case: - [pix_write] is deprecated in favour of [pix_writer] (which takes the incoming PIX to write, rather than creating a snapshot of the current framebuffer). the deprecation happened because [pix_write] is flawed by design rather than any bugs. - which imageplugins are you using? search for files called "gem_image*.so" in your extra/Gem/ folder. if you have both gem_imageTIFF.so and gem_imageMAGICK.so try disabling one of them (just rename it to something not starting with "gem_" && not ending with ".so, e.g. gem_imageTIFF.so.disabled) and see if it helps; if not try disabling the other one. the MAGICK plugin should be the preferred one. fgamsdr IOhannes _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list-- Richie
www.glitchpop.com http://www.glitchpop.com
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thanks very much for the help patch Cyrille, I'm still having trouble with it. No matter what path (or lack of path) I specify I get something like:
GEM: Unable to save image to 'blahblah/Home/Pd_files/test100000.jpg'
Is there a reason Pd might not be able to write to my HD (Ubuntu 14.04)?
Thanks again
On Mon, Jun 23, 2014 at 5:04 PM, Cyrille Henry ch@chnry.net wrote:
here is pix_writer help patch. cheers c
Le 23/06/2014 03:04, Richie Cyngler via Pd-list a écrit :
Hi IOhannes,
I was referring to the message that comes with this version of Pd-X. From the console: /WARNING: 64-bit builds are still beta, some libraries are known to have serious issues (cyclone, maxlib, moonlib, moocow, pdp, bsaylor, etc.) For more info, see the README.txt in '64-bit-warning-plugin' in the Help Browser/
Thanks for your help I followed your instructions and found that I have both gem_imageTIFF.so and gem_imageMAGICK.so so I disabled gem_imageTIFF.so and now Pd no longer crashes however "GEM: Unable to save image..." with [pix_write]. I tried [pix_writer] but it doesn't respond to a [file <name>( or a [bang( and there is no help that I can find. Would you mind explaining how to use [pix_writer] please. Then if I can get it working I'd be happy to write a help patch for it.
cheers
On Wed, Jun 18, 2014 at 5:06 PM, IOhannes m zmölnig <pd-list@lists.iem.at mailto:pd-list@lists.iem.at> wrote:
On 06/18/2014 02:58 AM, Richie Cyngler via Pd-list wrote: > Hi all, > > No matter what I try I can't get [pix_write] to do much more thancreate > corrupted .tiffs that won't open or just crash Pd. Looks like it's missing > gem.conf? > > open: /etc/pd/gem.conf: No such file or directory > open: /home/research/.pd/gem.conf: No such file or directory > open: ./gem.conf: No such file or directory > pd: tif_dirwrite.c:2084: TIFFWriteDirectoryTagCheckedRational: Assertion > `value>=0.0' failed. > Pd: signal 6 > > Running Pd Extended 0.43.4 64 bit on Ubuntu 14.04.
> I know the 64 bit is buggy why? what? what exactly are you referring to with "the 64th bit"? how is it buggy? > but according to my searching [pix_write] has had issues for awhile?
if it does has issues with PdX-0.43.3 then it will have these issues forever. i don't think anybody will make a bugfix version of this PdX release ever...rather a new shiny PdX-0.45.6 might come out... in any case: - [pix_write] is deprecated in favour of [pix_writer] (which takes the incoming PIX to write, rather than creating a snapshot of the current framebuffer). the deprecation happened because [pix_write] is flawedby design rather than any bugs.
- which imageplugins are you using? search for files called "gem_image*.so" in your extra/Gem/ folder. if you have both gem_imageTIFF.so and gem_imageMAGICK.so try disabling one of them (just rename it to something not starting with "gem_" &¬ ending with ".so, e.g. gem_imageTIFF.so.disabled) and see if it helps; if not try disabling the other one. the MAGICK plugin should be the preferred one.
fgamsdr IOhannes _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Richie
www.glitchpop.com http://www.glitchpop.com
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
On 06/23/2014 09:37 AM, Richie Cyngler via Pd-list wrote:
Thanks very much for the help patch Cyrille, I'm still having trouble with it. No matter what path (or lack of path) I specify I get something like:
GEM: Unable to save image to 'blahblah/Home/Pd_files/test100000.jpg'
Is there a reason Pd might not be able to write to my HD (Ubuntu 14.04)?
reason #1: Pd might disagree with you about your current working directory. *and* [pix_write*] will not create directories for you; if the path to the filename (excluding the file-portion) does not exist, then you won't be able to write the file.
so: imagine you have a directory "foo" in your home-directory (e.g. /home/glitchpop/foo/). since you want to write images into this file, you specify "foo/test.jpg" as the output filename) now you start Pd from the cmdline while you are in the /tmp directory: $ cd /tmp && pd sending the above message will really tell [pix_write*] to create a file "/tmp/foo/test.jpg". assuming there is no "/tmp/foo/" directory, this will fail.
if possible try using absolute paths. (e.g. prefixing your relative path with some (variable) root ("/home/glitchpop"))
gfmrdsa IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I have a little problem to understand how to manage the iMatrix interactor with [pmpd2d]. I don't understand how the matrix works here. Any help or a good exemple ? ++
Jack
Le 24/06/2014 15:56, Jack via Pd-list a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I have a little problem to understand how to manage the iMatrix interactor with [pmpd2d]. I don't understand how the matrix works here.
the matrix represent a force field. the "physical" size of the matrix is in the iMatrix message. there is 1 table for X interaction, one for Y. forces are bilinear interpolation of value from the matrix.
what's the problem? cheers c
Any help or a good exemple ? ++
Jack
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTqYNkAAoJEOuluecjw8GUQS8H/2akKm6IYwNUu5rLP7SQYF69 9o0lkYbhA4D1qitbcQOownJiEBYSn38T14tBpd+oXDHgzYfw39tqDYIwj6SB1MnL 2XD9y0BIGKczPDOR1VTsMxT3ibYl07Ztx036cbLki+LU6USoKelgQkhTWyEDX39n 9C1AyQOdIpDnLUTWglYSZqNfKZivA0kI6iC26KQ0FUb8UeMBSXlkmpWySMXg9B1x 7STjUMfWFHTBpcXI4hjKCHZ3tKYavrzBKE9AY8o4Eu+7em3o2yJ6lm6YRrqxo5N7 QsM7uCs/6OI9dc8whSfkRFxkMBMG6W6dfQ0kqptD8/YL25kBWu6nvZijwCwF6o4= =Estw -----END PGP SIGNATURE-----
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Cyrille Henry via Pd-list -
IOhannes m zmölnig via Pd-list
-
Jack via Pd-list
-
Richie Cyngler via Pd-list