Re: [PD] pix_snap
hello chr, so, if i understood you correctly, you just want to create a feedback? pix_snap is a bit cpu intensive. you should better do that with gemframebuffer. i just added this to your patch. cheers, marian Am 29.12.12 00:01, schrieb chr: hello list, i try to work with pix_snap and i dont get it, i do not come further. i made something like a typing machine the content is from a [coll] the attached patch demonstrates the principle of it. how i can make a snap after each line, and write afterwords over it?? i could do it with pix_write, i know, but i dont want to save always an image-file thank u very much greets chr ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list wolf.pd Description: application/puredata ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_record continues to record, even with rendering turned off
switching off the [gemhead] will not push new frames into your [pix_record], but it will not halt a local time (this is never what [gemhead] does). Ah, I see now! Although this is expected behaviour, I still think it'd be useful to be able to pause recording (at least in this scenario) - either manually force the framerate to a constant value when writing the file (it might well be (haven't checked yet) that you actually cannot force the framerate to a given value, which indeed could be considered a bug) I've checked the help file and options and of pix_record and there doesn't appear to be any options to set the frame rate. Please correct me if I'm wrong! I did a bit of further investigating and it appears that the framerate for the videos created by my patch/pix_record are craziliy high! Here's the sample video that I used http://dl.dropbox.com/u/350846/test.mov I ran the following command to get some information from the file mplayer -vo null -ao null -frames 0 -identify test.mov The important part of that information is that the fps is 100.000. Something isn't right there... On 28 December 2012 17:34, IOhannes m zmölnig zmoel...@iem.at wrote: On 12/28/2012 02:18, Antonio Roberts wrote: i cannot check your example right now, but this can totally be desired behaviour. e.g. if your container supports variable framerates and you record two frames that are 20 seconds appart, you might end up with a 20sec video containing of 2 frames. (afair, you might be able to override the framerate (depending on the backend/container you are using). This 20 seconds between frames is what I'm ending up with and I believe that it is a bug. hmm, with this is assume you mean that you really get a frame duration of 20 seconds (that is, your framerate is 0.05). if so, then the behaviour is definitely not a bug, as you record two frames and that are 20 seconds apart and you also get that. switching off the [gemhead] will not push new frames into your [pix_record], but it will not halt a local time (this is never what [gemhead] does). i understand that this behaviour is not what you want, but the way to fix it is: - either manually force the framerate to a constant value when writing the file (it might well be (haven't checked yet) that you actually cannot force the framerate to a given value, which indeed could be considered a bug) - or ignore the framerate when playing back the file - or fix the framerate once the file is written (but before you want to play it back). As far as I understand, pix objects need a [gemhead] in order to function. If it is not present or is turned off then it shouldn't operate. What I'm finding is that once recording is turned on and then afterwards the gemhead is turned off, when it is turned back on and a frame captured the time between the two bangs is still recorded. for the sake of completeness: there's a small chance of a problem with data caching. [pix_record] will not write new frames if it doesn't receive a render-trigger (usually originating from [gemhead]). but once you turn it on again it might write pixel data that originates from before turning on the [gemhead]. fadmsr IOhannes ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- anto...@hellocatfood.com http://www.hellocatfood.com ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] [PD-announce] Downloads for PuREST JSON have moved
Hello, as Github has deprecated the downloads section, I have moved the downloads to my own website: http://ix.residuum.org/pd/purest_json.html I have now uploaded a Windows package of the library as well, but [rest] and [oauth] do not work for some reason on Windows (see https://github.com/residuum/PuRestJson/issues/10). Help with that bug is very much appreciated. What is PuREST JSON? PuREST JSON is a library for connecting Puredata (Pd) to HTTP services and encoding and decoding JSON data. The library can issue GET, POST, PUT and DELETE statements, so consumation of RESTful services is possible, e.g. CouchDB. PuREST JSON also includes an object for OAUTH secured webservices, so you can also use it e.g. for building a Twitter client. Best regards, Thomas -- It seems to me, Golan, that the advance of civilization is nothing but an exercise in the limiting of privacy. (Janov Pelorat in: Isaac Asimov - Foundation's Edge) http://www.residuum.org/ ___ Pd-announce mailing list pd-annou...@iem.at http://lists.puredata.info/listinfo/pd-announce ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_record continues to record, even with rendering turned off
On 12/29/2012 16:20, Antonio Roberts wrote: switching off the [gemhead] will not push new frames into your [pix_record], but it will not halt a local time (this is never what [gemhead] does). Ah, I see now! Although this is expected behaviour, I still think it'd be useful to be able to pause recording (at least in this scenario) bien sur. - either manually force the framerate to a constant value when writing the file (it might well be (haven't checked yet) that you actually cannot force the framerate to a given value, which indeed could be considered a bug) I've checked the help file and options and of pix_record and there doesn't appear to be any options to set the frame rate. Please correct me if I'm wrong! aye, it's a bit undocumented :-( [*] like with [pix_video], you can set a number of properties specific to the used backend/codec. when selecting a specific codec, you should get a list of supported properties for the selected setting on the info-outlet of [pix_record] (that's the 3rd outlet). e.g. slecting [codec mjpa( gives me available properties framerate, jpeg_quality and jpeg_usefloat. you can then set these properties using a set message: [set framerate 20( should give create a film with a fixed framerate of 20fps, whereas [set jpeg_quality 15( will give you low quality jpeg compression. I did a bit of further investigating and it appears that the framerate for the videos created by my patch/pix_record are craziliy high! Here's the sample video that I used http://dl.dropbox.com/u/350846/test.mov I ran the following command to get some information from the file mplayer -vo null -ao null -frames 0 -identify test.mov The important part of that information is that the fps is 100.000. Something isn't right there... hmm, i get: $ qtinfo test.mov | grep rate rate 0.608175 [100:1644263] not constant which sounds plausible to me. might be, that mplayer doesn't report the correct framerate (only the numerator, not the denominator) mfgasdr IOhannes [*] patches contributing to the docs are welcome. ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_snap
hi marian yes, it was exatly this what i tried to do i have only my old acer netbook by the hand, which seems to be too slow, even in buffer 1 mode but tomorrow i will try it with an faster machine thank you very much for your help greets christian On 29.12.2012 14:21, Marian Weger wrote: hello chr, so, if i understood you correctly, you just want to create a feedback? pix_snap is a bit cpu intensive. you should better do that with gemframebuffer. i just added this to your patch. cheers, marian Am 29.12.12 00:01, schrieb chr: hello list, i try to work with pix_snap and i dont get it, i do not come further. i made something like a typing machine the content is from a [coll] the attached patch demonstrates the principle of it. how i can make a snap after each line, and write afterwords over it?? i could do it with pix_write, i know, but i dont want to save always an image-file thank u very much greets chr ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_record continues to record, even with rendering turned off
like with [pix_video], you can set a number of properties specific to the used backend/codec. when selecting a specific codec, you should get a list of supported properties for the selected setting on the info-outlet of [pix_record] (that's the 3rd outlet). And now it seems I've encountered an actual bug! I've tried several different codecs (25 and 1 exhaustively) and it appears that I can't change the settings of them. No matter what framerate I set I still get a framerate of 20 (or whatever the original video was (I think)). Before finally diagnosing this as a bug, is there a specific order to how the messages should be sent? This is my order, using the pix_record help file: 1 - create the gem window 2 - open the video file 3 - Choose the codec 4 - change the options of the codec (via set) 5 - open a location to save the file 6 - record 7 - set auto record [auto 1( Is this right? Thanks Antonio On 29 December 2012 19:41, IOhannes m zmölnig zmoel...@iem.at wrote: On 12/29/2012 16:20, Antonio Roberts wrote: switching off the [gemhead] will not push new frames into your [pix_record], but it will not halt a local time (this is never what [gemhead] does). Ah, I see now! Although this is expected behaviour, I still think it'd be useful to be able to pause recording (at least in this scenario) bien sur. - either manually force the framerate to a constant value when writing the file (it might well be (haven't checked yet) that you actually cannot force the framerate to a given value, which indeed could be considered a bug) I've checked the help file and options and of pix_record and there doesn't appear to be any options to set the frame rate. Please correct me if I'm wrong! aye, it's a bit undocumented :-( [*] like with [pix_video], you can set a number of properties specific to the used backend/codec. when selecting a specific codec, you should get a list of supported properties for the selected setting on the info-outlet of [pix_record] (that's the 3rd outlet). e.g. slecting [codec mjpa( gives me available properties framerate, jpeg_quality and jpeg_usefloat. you can then set these properties using a set message: [set framerate 20( should give create a film with a fixed framerate of 20fps, whereas [set jpeg_quality 15( will give you low quality jpeg compression. I did a bit of further investigating and it appears that the framerate for the videos created by my patch/pix_record are craziliy high! Here's the sample video that I used http://dl.dropbox.com/u/350846/test.mov I ran the following command to get some information from the file mplayer -vo null -ao null -frames 0 -identify test.mov The important part of that information is that the fps is 100.000. Something isn't right there... hmm, i get: $ qtinfo test.mov | grep rate rate 0.608175 [100:1644263] not constant which sounds plausible to me. might be, that mplayer doesn't report the correct framerate (only the numerator, not the denominator) mfgasdr IOhannes [*] patches contributing to the docs are welcome. ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- anto...@hellocatfood.com http://www.hellocatfood.com ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_record continues to record, even with rendering turned off
No matter what framerate I set I still get a framerate of 20 (or whatever the original video was (I think)). of course. you need to bang [pix_record] in the desired framerate. with auto 1, it will always record in your current gem framerate, which is 20fps. cheers, marian Before finally diagnosing this as a bug, is there a specific order to how the messages should be sent? This is my order, using the pix_record help file: 1 - create the gem window 2 - open the video file 3 - Choose the codec 4 - change the options of the codec (via set) 5 - open a location to save the file 6 - record 7 - set auto record [auto 1( Is this right? Thanks Antonio On 29 December 2012 19:41, IOhannes m zmölnig zmoel...@iem.at wrote: On 12/29/2012 16:20, Antonio Roberts wrote: switching off the [gemhead] will not push new frames into your [pix_record], but it will not halt a local time (this is never what [gemhead] does). Ah, I see now! Although this is expected behaviour, I still think it'd be useful to be able to pause recording (at least in this scenario) bien sur. - either manually force the framerate to a constant value when writing the file (it might well be (haven't checked yet) that you actually cannot force the framerate to a given value, which indeed could be considered a bug) I've checked the help file and options and of pix_record and there doesn't appear to be any options to set the frame rate. Please correct me if I'm wrong! aye, it's a bit undocumented :-( [*] like with [pix_video], you can set a number of properties specific to the used backend/codec. when selecting a specific codec, you should get a list of supported properties for the selected setting on the info-outlet of [pix_record] (that's the 3rd outlet). e.g. slecting [codec mjpa( gives me available properties framerate, jpeg_quality and jpeg_usefloat. you can then set these properties using a set message: [set framerate 20( should give create a film with a fixed framerate of 20fps, whereas [set jpeg_quality 15( will give you low quality jpeg compression. I did a bit of further investigating and it appears that the framerate for the videos created by my patch/pix_record are craziliy high! Here's the sample video that I used http://dl.dropbox.com/u/350846/test.mov I ran the following command to get some information from the file mplayer -vo null -ao null -frames 0 -identify test.mov The important part of that information is that the fps is 100.000. Something isn't right there... hmm, i get: $ qtinfo test.mov | grep rate rate 0.608175 [100:1644263] not constant which sounds plausible to me. might be, that mplayer doesn't report the correct framerate (only the numerator, not the denominator) mfgasdr IOhannes [*] patches contributing to the docs are welcome. ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-announce] pd 0.44-0 test 1 released
everytime i run audacity i can not get the audio to work again with anything without a cold start. ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-announce] pd 0.44-0 test 1 released
On 12/30/2012 01:31 AM, Billy Stiltner wrote: everytime i run audacity i can not get the audio to work again with anything without a cold start. ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list Did you try resuming pulse audio? It is possible that Audacity might be suspending it but is not necessarily resuming it once it is done. Please take this with a boulder of salt as I've not tested any of this... -- Ivica Ico Bukvic, D.M.A Composition, Music Technology Director, DISIS Interactive Sound Intermedia Studio Director, L2Ork Linux Laptop Orchestra Head, ICAT IMPACT Studio Virginia Tech Department of Music Blacksburg, VA 24061-0240 (540) 231-6139 (540) 231-5034 (fax) disis.music.vt.edu l2ork.music.vt.edu ico.bukvic.net ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
