On 2010-03-21 18:22, Matteo Sisti Sette 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]
fgmasdr
IOhannes
smime.p7s
Description: S/MIME Cryptographic Signature
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
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,
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
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
Hi,
I've found a thread about this issue in the archives but no solution.
When you use [pix_video] followed by [pix_movement], you get either a
white frame or a black frame every once in a while.
In Windows I see black-frame flickering, while in Mac I have seesn
frame-identity flickering.
