Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[WaltK]

When I run Multiview on same system as AHP
I can use very short scan periods when
scanning automatically between cams.  5
Seconds works great, even when AHP is up
and CM15A is supporting it and Multiview
traffic.  It seems that the shortest period
I can set in iWitness is 15 seconds per
snapshot.  How do I make it shorter?

[Helpful hints]

Do direct entry: Highlight the value entry
i.e. the 15 and key in 05

[tony]

It would be great to be able to take it down
to at least 03 seconds for both between
cameras and between still shots. in fact the
still shots should a time increment from the
switch time to each camera. i.e. upon switch
to or turn on the respective camera +2
seconds.

[X10 Pro]

We'll make it so the arrow buttons allow you
to enter the minimum value. I'll see if we
can make it less than 5 seconds, too.

[tony]

X10 Pro:  Thank you.

[WaltK]

Thanks for the comments, although I DID TRY
to direct enter the 5 seconds...  It
appeared to take it, but then upon
redisplaying the popup it was back at 15
seconds.  So I though maybe the issue was
just with the DISPLAY of the info, but by
timing the interval it WAS 15 seconds even
though I direct entered the 5.  I will
interested to see if anyone else has seen
the behavior I did.  Have WinXP/Pro, all
SPs, and AHP (with all three addins) as
well as Multiview, PanTiltPro and Webview
installed.  Any comments which verify the
response I saw?

[RVerkoey]

I pressed the enter key instead of "close"
then restarted Camera Scanning and it
worked.  My cameras now change every 5 secs.

[WaltK]

Thanks for the Enter vs. Close tip.
But maybe X10Pro should consider if it
REALLY should be necessary to hit enter.
Maybe an APPLY or something would be more
to the normal windows practice?  However
now that you pointed out the "trick" all is
well for me at the moment.

[X10 Pro]

You shouldn't have to hit enter -- if you
leave the entry box, it should remember what
you typed. It's a bug that it doesn't.