Re: [PD] pix_snap + pix_record = problem
Jaime Oliver escribió: I had a similar error in osx10.6. Did you find a workaround? Could you ever record a sequence of snapped pixes into a video file? thanks m. -- Matteo Sisti Sette matteosistise...@gmail.com http://www.matteosistisette.com ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_snap + pix_record = problem
Hello I am working with [pix_snap] and its running quite good. In the attachment you will find a test-patch i build out of help-files. While playing around with [pix_snap]i noticed, that its quite important, to have different gemheads for the parts where you do something to the source-signal and the part of the patch where you record the video. like having [gemhead 5] for the first, and [gemhead 55] for the snapping part. that way the first part gets handled before the image is snapped. hope that helps. Peter -Ursprüngliche Nachricht- Von: Matteo Sisti Sette Gesendet: 21.03.2010 13:23:16 An: Jaime Oliver Betreff: Re: [PD] pix_snap + pix_record = problem Jaime Oliver escribió: I had a similar error in osx10.6. Did you find a workaround? Could you ever record a sequence of snapped pixes into a video file? thanks m. -- Matteo Sisti Sette matteosistise...@gmail.com http://www.matteosistisette.com ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list pix_snap_test.pd Description: Binary data ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_snap + pix_record = problem
this one works on windose hope it helps der.brandt Zitat von Matteo Sisti Sette matteosistise...@gmail.com: Jaime Oliver escribió: I had a similar error in osx10.6. Did you find a workaround? Could you ever record a sequence of snapped pixes into a video file? thanks m. -- Matteo Sisti Sette matteosistise...@gmail.com http://www.matteosistisette.com ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list #N canvas 688 14 450 300 10; #X obj 8 271 pix_record; #X obj 27 240 cnv 15 145 25 empty empty empty 20 12 0 14 -225271 -66577 0; #X msg 37 244 bang; #X msg 109 244 auto \$1; #X obj 90 245 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1 ; #X obj 5 172 cnv 15 155 65 empty empty empty 20 12 0 14 -225271 -66577 0; #X obj 9 174 bng 15 250 50 0 empty empty empty 0 -6 0 8 -258699 -1 -1; #N canvas 0 0 450 300 savepanel 0; #X obj 114 62 inlet; #X obj 114 254 outlet; #X obj 114 199 t b a; #X obj 114 125 savepanel; #X msg 114 162 set file \$1; #X connect 0 0 3 0; #X connect 2 0 1 0; #X connect 2 1 1 0; #X connect 3 0 4 0; #X connect 4 0 2 0; #X restore 29 173 pd savepanel; #X msg 65 216 record \$1; #X obj 45 218 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1 ; #X obj 8 216 t a; #X floatatom 96 274 5 0 0 0 - - -; #X obj -3 109 pix_snap; #X msg 33 82 0 0; #X obj 39 32 loadbang; #X obj -1 79 t b a; #X obj -2 11 gemhead -99; #X msg 65 83 640 480; #X msg 9 197 file C:/Users/FSC/Desktop/newhypnoticdevice/nextUnivers4.mov ; #X connect 0 1 11 0; #X connect 2 0 0 0; #X connect 3 0 0 0; #X connect 4 0 3 0; #X connect 6 0 7 0; #X connect 7 0 18 0; #X connect 8 0 10 0; #X connect 9 0 8 0; #X connect 10 0 0 0; #X connect 12 0 0 0; #X connect 13 0 12 1; #X connect 14 0 13 0; #X connect 14 0 17 0; #X connect 15 0 12 0; #X connect 15 1 12 0; #X connect 16 0 15 0; #X connect 17 0 12 2; #X connect 18 0 10 0;#N canvas 688 14 450 300 10; #X obj 8 271 pix_record; #X obj 27 240 cnv 15 145 25 empty empty empty 20 12 0 14 -225271 -66577 0; #X msg 37 244 bang; #X msg 109 244 auto \$1; #X obj 90 245 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1 ; #X obj 5 172 cnv 15 155 65 empty empty empty 20 12 0 14 -225271 -66577 0; #X obj 9 174 bng 15 250 50 0 empty empty empty 0 -6 0 8 -258699 -1 -1; #N canvas 0 0 450 300 savepanel 0; #X obj 114 62 inlet; #X obj 114 254 outlet; #X obj 114 199 t b a; #X obj 114 125 savepanel; #X msg 114 162 set file \$1; #X connect 0 0 3 0; #X connect 2 0 1 0; #X connect 2 1 1 0; #X connect 3 0 4 0; #X connect 4 0 2 0; #X restore 29 173 pd savepanel; #X msg 65 216 record \$1; #X obj 45 218 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1 ; #X obj 8 216 t a; #X floatatom 96 274 5 0 0 0 - - -; #X obj -3 109 pix_snap; #X msg 33 82 0 0; #X obj 39 32 loadbang; #X obj -1 79 t b a; #X obj -2 11 gemhead -99; #X msg 65 83 640 480; #X msg 9 197 file C:/Users/FSC/Desktop/newhypnoticdevice/nextUnivers4.mov ; #X connect 0 1 11 0; #X connect 2 0 0 0; #X connect 3 0 0 0; #X connect 4 0 3 0; #X connect 6 0 7 0; #X connect 7 0 18 0; #X connect 8 0 10 0; #X connect 9 0 8 0; #X connect 10 0 0 0; #X connect 12 0 0 0; #X connect 13 0 12 1; #X connect 14 0 13 0; #X connect 14 0 17 0; #X connect 15 0 12 0; #X connect 15 1 12 0; #X connect 16 0 15 0; #X connect 17 0 12 2; #X connect 18 0 10 0;___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_snap + pix_record = problem
Thank you Peter and der.brandt for the patches. Your test patches work (and so do some variations of them that make them essentially similar to what I'm trying to do): I'm trying to find out what's different in my patch; at the moment I can't find any significant difference I'll let you know It would help (maybe) to know what the- those error messages mean... thanks m. n...@petervenus.de escribió: Hello I am working with [pix_snap] and its running quite good. In the attachment you will find a test-patch i build out of help-files. While playing around with [pix_snap]i noticed, that its quite important, to have different gemheads for the parts where you do something to the source-signal and the part of the patch where you record the video. like having [gemhead 5] for the first, and [gemhead 55] for the snapping part. that way the first part gets handled before the image is snapped. hope that helps. Peter -Ursprüngliche Nachricht- Von: Matteo Sisti Sette Gesendet: 21.03.2010 13:23:16 An: Jaime Oliver Betreff: Re: [PD] pix_snap + pix_record = problem Jaime Oliver escribió: I had a similar error in osx10.6. Did you find a workaround? Could you ever record a sequence of snapped pixes into a video file? thanks m. -- Matteo Sisti Sette matteosistise...@gmail.com http://www.matteosistisette.com ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_snap + pix_record = problem
Hi, I think I've found what triggers the problem (and avoiding it I can get things to work fine). It seems to happen when these things happen in this order: 1) The [gemhead] driving the [pix_snap] and [pix_record] is disabled (via a 0 message) _before_ the gemwin is created (for example, at loadbang) 2) After creating the gemwin, the gemhead is not enabled until _just before_ the record 1 and auto 1 messages are sent to [pix_record]. That is, the following sequence of actions, that should be perfectly legal, leads to malfunctioning: i) disabling the gemhead driving pix_snap and pix_record (some time passes) ii) creating the gemwin (some time passes) iii) filename is given to pix_record (some time passes) iv) the following is done in 0 logical time: iv.1) enabling the gemhead iv.2) record 1 message to pix_record iv.3) auto 1 message to pix_record This can lead to either of two malfunctioning and unrecoverable situations: A) immediate crash B) pix_record outputs some error messages and does not record; The pix_record will never recover. Even if you do a sequence of steps that would normally lead to good functioning (e.g.: destroy/recreate the gemwin, enabling the gemhead, repeating steps iii, iv.2 and iv.3 in non-zero time), it won't work any more. I wouldn't expect this to cause any problem; at the very least, pix_record should: - never crash - give a meaningful error message if the situation presented is actually illegal for some reason - recover and work correctly when normality is reestablished Well all this is basically a bug report so I will file it to the bug tracker. I just thoght I'd let you know that I had found the workaround; then while writing it came out as if i was filing a bug report... Also, if anybody can confirm the issue on other platforms beside windows and/or explain why this behaviour should be expected (except the crashes of course), that would be helpful. thanks m. n...@petervenus.de escribió: Hello I am working with [pix_snap] and its running quite good. In the attachment you will find a test-patch i build out of help-files. While playing around with [pix_snap]i noticed, that its quite important, to have different gemheads for the parts where you do something to the source-signal and the part of the patch where you record the video. like having [gemhead 5] for the first, and [gemhead 55] for the snapping part. that way the first part gets handled before the image is snapped. hope that helps. Peter -Ursprüngliche Nachricht- Von: Matteo Sisti Sette Gesendet: 21.03.2010 13:23:16 An: Jaime Oliver Betreff: Re: [PD] pix_snap + pix_record = problem Jaime Oliver escribió: I had a similar error in osx10.6. Did you find a workaround? Could you ever record a sequence of snapped pixes into a video file? thanks m. -- Matteo Sisti Sette matteosistise...@gmail.com http://www.matteosistisette.com #N canvas 355 9 994 775 10; #X msg 468 167 snap; #X obj 458 134 t a b; #X obj 458 112 gemhead 99; #X obj 458 86 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1; #X obj 553 224 cnv 15 167 200 empty empty empty 20 12 0 14 -24198 -66577 0; #X obj 553 404 pix_record; #X obj 572 373 cnv 15 145 25 empty empty empty 20 12 0 14 -225271 -66577 0; #X msg 582 377 bang; #X msg 654 377 auto \$1; #X obj 635 378 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1; #X obj 572 229 cnv 15 145 65 empty empty empty 20 12 0 14 -225271 -66577 0; #X msg 578 254 codeclist; #X msg 574 233 dialog; #X obj 574 274 t a; #X obj 562 301 cnv 15 155 65 empty empty empty 20 12 0 14 -225271 -66577 0; #X obj 776 275 bng 15 250 50 0 empty empty save_as 0 -6 0 15 -258699 -1 -1; #N canvas 0 22 450 300 savepanel 0; #X obj 114 62 inlet; #X obj 114 254 outlet; #X obj 114 199 t b a; #X obj 114 125 savepanel; #X msg 114 162 set file \$1; #X connect 0 0 3 0; #X connect 2 0 1 0; #X connect 2 1 1 0; #X connect 3 0 4 0; #X connect 4 0 2 0; #X restore 586 303 pd savepanel; #X msg 622 345 record \$1; #X obj 602 347 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1; #X obj 565 345 t a; #X floatatom 641 407 5 0 0 0 - - -; #X msg 634 274 codec mjpa; #X obj 773 325 tgl 15 0 empty empty rec_ONoff 17 7 0 10 -262144 -1 -1 0 1; #X obj 775 240 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1; #X msg 654 255 codec 4; #X obj 75 18 cnv 15 250 350 empty empty empty 20 12 0 14 -228992 -66577 0; #X obj 241 49 cnv 15 100 60 empty empty empty 20 12 0 14 -195568 -66577 0; #N canvas 0 0 450 300 gemwin 0; #X obj 132 136 gemwin; #X obj 67 89 outlet; #X obj 67 10 inlet; #X msg 67 70 set destroy; #X msg 132 112 create \, 1; #X msg 198 112 destroy; #X msg 156 71 set create; #X obj 67 41 route create; #X connect 2 0 7 0; #X connect 3 0 1 0; #X connect 4 0 0 0; #X connect 5 0 0 0; #X connect 6 0 1 0; #X connect 7 0 3 0; #X connect 7 0 4 0; #X connect 7 1 6 0; #X connect 7 1 5 0; #X restore 246 88 pd gemwin; #X msg 246 69 create; #X text 242 48 Create window:; #X obj 77 49 cnv 15 155 250
[PD] pix_snap + pix_record = problem
Hi, I'm trying to use a [pix_record] after a [pix_snap] but I get errors and it doesn't record. The help patch does work, and I could make my own working test patch with [pix_video] followed by [pix_record] and it does work. However, when I try with pix_snap (to capture what I'm rendering and record it), I get the following error as soon as the gemhead is connected to the chain: error: recordQT: EndMediaEdits failed with error -2008 Then, when I send it record 1, auto 1, I get these errors: error: recordQT: CreateMovieFile failed with error -47 error: recordQT: EndMediaEdits failed with error -2008 If I delete the pix_record and replace it by [pix_texture] | [cube 4] I see the snapped image (snapped every frame), so [pix_snap] is working correctly. Any idea? What are error -47 and error -2008? (btw do errors really have negative codes or is it some type error?) Thanks in advance m. -- Matteo Sisti Sette matteosistise...@gmail.com http://www.matteosistisette.com ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
