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.
Thanks!
And with that I think I've identified the actual bug here. I still
can't override that framerate by changing the option in the codec
On 12/30/2012 15:16, Antonio Roberts wrote:
And with that I think I've identified the actual bug here. I still
can't override that framerate by changing the option in the codec
setting
yes, indeed you found a bug here.
it seems that currently there is no real way to set any property
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)
-
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
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
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
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.
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
I've noticed that [pix_record] will continue to record frames even if
the [gemhead] object attached to it is switched off. Is this a bug?
I've attached a sample patch, where I'm attempting to take a snapshot
from a camera and save it to a video
#N canvas 1660 101 564 374 10;
#X obj 281 40
On 12/26/2012 15:08, Antonio Roberts wrote:
I've noticed that [pix_record] will continue to record frames even if
the [gemhead] object attached to it is switched off. Is this a bug?
the way to turn off recording is by sending a record 0 message to
[pix_record], or - if you want to add single
the way to turn off recording is by sending a record 0 message to
[pix_record], or - if you want to add single frames to a movie, to not use
auto 0 mode and manually bang the frames you want to record.
Try out the example patch that's included in the last message. After
record is started it
11 matches
Mail list logo
