[PD] pix_record continues to record, even with rendering turned off

[Antonio Roberts]

> 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. 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.

Is this a problem/feature of Gem or the codec used?

> since i'm not tracking PdX versions (and even less snapshot versions of
> PdX!), it is usually helpful to provide the Gem-version as well. (something
> like "0.93.3"; it should be displayed at startup - when Gem is loaded -
> though you might have to raise the verbosity of the pd-console)

I'm using Gem 0.93.3

Thanks

Antonio

On 27 December 2012 18:57, IOhannes m zmölnig <zmoelnig at iem.at> wrote:
> On 12/27/2012 01:33, Antonio Roberts wrote:
>>
>> record is started it uses a bang to turn on the gemhead and to capture
>
>
> i'm talking abot [bang(ing [pix_record], which is something different than
> [bang(ing [gemhead].
>
>> one frame, and then turns it off again. However, the time between the
>> two frame captures is still recorded even if the gemhead is turned off
>> e.g. the 20 seconds between two bangs will still be recorded even if
>> rendering is stopped
>
>
> 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).
>
>>
>> Also, stopping recording writes the movie file, and restarting
>> recording will overwrite the previous file.
>
>
> yes.
> i was mainly pointing to the various ways to control [pix_record].
> please check "auto" mode and manual frame progression in the help-patch.
>
>>
>>> even more interesting would be the OS and Gem-version your are using.
>>> (but the above still is a valid answer)
>>
>>
>> I'm using pd-extended 0.43.4~cvs20121225-1 on Ubuntu 12.04
>>
>
> thanks.
> since i'm not tracking PdX versions (and even less snapshot versions of
> PdX!), it is usually helpful to provide the Gem-version as well. (something
> like "0.93.3"; it should be displayed at startup - when Gem is loaded -
> though you might have to raise the verbosity of the pd-console)
>
> fgmasdr
> IOhannes
>
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list



-- 
============================
antonio at hellocatfood.com
http://www.hellocatfood.com
============================