here is the same thing with pix_multiimage instead. it will crash pd a little bit later than the version with pix_image.
timelapse_multiimage.pd
Description: Binary data
Am 30.03.2009 um 18:50 schrieb mark edward grimm:
hey thats pretty nice!! much nicer than my poor gem attempt last month...and the patch: put this to / because of the bug in pix_write to make it work. put a folder called "frames" beside it.yeah this is weird huh? --- On Sat, 3/28/09, Max <abonneme...@revolwear.com> wrote:From: Max <abonneme...@revolwear.com> Subject: [PD] GEM pix_write bugs (timelapse) To: pd-list@iem.at Date: Saturday, March 28, 2009, 12:52 PM hi list, i've thrown together this tiny gem patch which makes a timelapse slideshow. i have encountered a few issues with it. configuration: Pd version 0.41.4-extended-20090223 GEM: ver: 0.91.3 'tigital' GEM: compiled: Feb 23 2009 OS X 10.5.6 the issues: 1. pix_write doesn't interpret the file path correctly. it seems it can't understand relative paths at all. 2. pix_write accepts a message [file <file> [<type>](. it creates files with a .jpg ending if the type is >0. But in reality it still is a TIFF. no matter what value you write. 3. pix_write creates files with an acending number 0...9999 this conflicts with how other objects like pix_multiimage do it (00000...99999) just submitted that to the gem bugtracker. and the patch: put this to / because of the bug in pix_write to make it work. put a folder called "frames" beside it. beware: this patch will also eat up all the memory and will crash pd. this isn't pix_writes problem though - i'll try to find out why this is now. max -----Inline Attachment Follows----- _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PGP.sig
Description: Signierter Teil der Nachricht
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
