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 <[email protected] <mailto:[email protected]>> 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 _______________________________________________ [email protected] <mailto:[email protected]> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list -- Richie www.glitchpop.com <http://www.glitchpop.com> _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
pix_writer-help.pd
Description: application/puredata
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
