IOHannes wrote:
Hi,
How do you work this around? How can one "know" whether a new frame has been captured or not?
you can learn quite everything about a pix with [pix_info]
How can I use it to learn whether a new frame has been captured?
I tried [print]ing the output from the 7th outlet, whose function is not quite clear in the help patch: "list <newimage> <newfilm>". I guessed either <newimage> or <newfilm> _may_ be a boolean meaning whether the image is new (or the film, whatever it is), but even if I set the gemwin at 30 or 50 fps, I _always_ get "1 0", and I don't think my webcam captures 50 fps.......
thanks m.
On 2010-03-22 09:48, Matteo Sisti Sette wrote:
IOHannes wrote:
I tried [print]ing the output from the 7th outlet, whose function is not quite clear in the help patch: "list <newimage> <newfilm>". I guessed either <newimage> or <newfilm> _may_ be a boolean meaning whether the image is new (or the film, whatever it is), but even if I set the gemwin at 30 or 50 fps, I _always_ get "1 0", and I don't think my webcam captures 50 fps.......
that would have been the hint
there are two possibilities why this is happening:
- there is a bug in Gem that doesn't mark the images as "old" (was this
on w32 or osx?)
- there is a "bug" in the image acquisition backend (DirectShow,
QuickTime,...) that just serves the same image twice as if it were new.
in the former case, we can fix it. in the latter case we won't.
of course you can use the "black" image to detect whether the same image was captured twice.
fgasdr IOhannes
is it possible your camera is capturing at 29.996 fps instead of 30 and pix_video still is capturing them as 30 or something similar? is it a dv compressed camera? could you measure the frequency of the black/white frames?
J
On Mon, Mar 22, 2010 at 1:54 AM, IOhannes m zmoelnig zmoelnig@iem.atwrote:
On 2010-03-22 09:48, Matteo Sisti Sette wrote:
IOHannes wrote:
I tried [print]ing the output from the 7th outlet, whose function is not quite clear in the help patch: "list <newimage> <newfilm>". I guessed either <newimage> or <newfilm> _may_ be a boolean meaning whether the image is new (or the film, whatever it is), but even if I set the gemwin at 30 or 50 fps, I _always_ get "1 0", and I don't think my webcam captures 50 fps.......
that would have been the hint
there are two possibilities why this is happening:
- there is a bug in Gem that doesn't mark the images as "old" (was this
on w32 or osx?)
- there is a "bug" in the image acquisition backend (DirectShow,
QuickTime,...) that just serves the same image twice as if it were new.
in the former case, we can fix it. in the latter case we won't.
of course you can use the "black" image to detect whether the same image was captured twice.
fgasdr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
IOhannes m zmoelnig escribió:
there are two possibilities why this is happening:
- there is a bug in Gem that doesn't mark the images as "old" (was this
on w32 or osx?)
W32 (Windows Vista)
- there is a "bug" in the image acquisition backend (DirectShow,
QuickTime,...) that just serves the same image twice as if it were new.
What test may I do to tell which one of the two is true?
By the way, if the image were correctly marked as "old", would [pix_movement] use this information (i.e. avoid comparing tro frames that are actually the same frame)? Or do you have to handle this explicitly with pix_info?
-
IOhannes m zmoelnig -
Jaime Oliver -
Matteo Sisti Sette