Print

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

[lare]

Whenever I capture video with iWitness, the
AVI file is almost always only 16mb in
size, no matter how long I record. If I
record several minutes, then there are many
tiny clips besides the first 16mb avi file.
Anyone else have this problem and know what
the solution is?

[magij]

same problem here at times only records a
few seconds when I have it set to one minute
and can see it recording.  sometimes it does
not record at all sometimes it crashes
sometimes there is a file but I can not play
it.  Do I have the wrong video codecs?  

[WinS]

I am experiencing the same problem.  The
setup for my four cams is to turn on and
record video for 20 seconds when triggered by
a motion sensor. This worked quite well until
less than one month ago.  Now most of the
files are only one second long or not
useable, while a few are recorded correctly.
Could one of the most recent updates have
affected iWitness?  I'm on 3.199.  I save the
previous two versions when I update, so I
have 3.198 and 3.196.  When I run either of
those versions, I encounter no problem with
the video recording.  When I go back to 3.199
I do encounter the problem - video recording
is only fully successful about 10% of the
time.  Windows XPPro SP1 (has not changed).
X10 Pro - could you take a look?

[WinS]

Since my last post I have run version 3.198
and did the update to 3.199.  The new version
(3.199) will not record video properly - it
makes unuseable files or files that run only
a second or two, as reported here previously.
This needs to be fixed, pronto.

[magij]

I got my x10 to watch my home while on
vacation.  It shows a photo of me leaving
the house and then stopped working.  I have
updated, changed codecs, re-installed, even
set a task manager event so when the program
crashes it will restart.  I have made
certain the usb is seen as x10 not some
camera.  I gave up on recording video and
set the macro to record only a still.  I
have spent hours trying to make this work
and it faild me when I really needed it.
Thank god my home is safe.  Do you intend to
fix this problem or would I be better served
with another product?  

[magij]

I got my x10 to watch my home while on
vacation.  It shows a photo of me leaving
the house and then stopped working.  I have
updated, changed codecs, re-installed, even
set a task manager event so when the program
crashes it will restart.  I have made
certain the usb is seen as x10 not some
camera.  I gave up on recording video and
set the macro to record only a still.  I
have spent hours trying to make this work
and it faild me when I really needed it.
Thank god my home is safe.  Do you intend to
fix this problem or would I be better served
with another product?  

[jim k]

I have had every one of the problems listed
here.  It was somewhat useable before the
3.199 update.  It looks like part of the
problem might be that pro does not close
the video file properly when it is
running.  If I close pro right after the
recording sometimes the recording is longer
than one second (up to a minute).  Looking
forward to the resolution of these issues
so the program can be used.

[bronco]

I agree that it appears that the program is
not properly closing the video file.
Also, tonight it created a still directory
of 30Mon0023 and todays date is 1/29/06.
My system date is correct as well as the
configuration date of AHP.
It is still iffy whether I get a file saved
or not.  Probably 1 out of 5 tries I might
get a file.

[WinS]

Bronco
Regarding the time stamp, Universal Time is
used which is 4 or 5 hours (Dayight Savings
or Standard) ahead of East Coast Time.

[magij]

I don't think anyone from X10 reads this.
They must know that the software has been
sold to us not working.  Or maybe the could
tell us they know and are working on it?  

[bronco]

I know the Universal time better as
Greenwich Mean Time (GMT) which is 5 hours
before us in Great Britain.  Howerver, if
you set your Longitude and Latitude (or
choose a city) in the configuration option
it will use your local time.
My point was that my PC and AHP both showed
local time and it still created a file with
the wrong date.  Seems like a bug.  I'll
test some of the times when I get a chance.

[Mystyx]

I too have seen some problems with the PC video recording function, prior to the 3.199 there was a problem I was trying to figure out with X10 techs, but I have put it on hold for now as it could be a problem with other hardware on your PC.

Originally 3rd / 4th email, that a file may have become corrupt and I should reinstall. Since then have found a compatibility problem with ATI and X10 using the same X10 files and have asked for a change in the way AHP detects hardware.

ATI uses X10 remote controls for their video cards (All in Wonder) but I found even with the ATI remote NOT Installed, ATI software will still install (and reinstall) the X10 driver. I found that the ATI 9800 remote (UR84A) RF Receiver uses a thirdParty version of the CM19A. When I install AHP the program, it auto detects the ATI remote as VT37A + CM19A, neither were connected or installed. asking X10... VT37A is their new RF iPod package.

how many people here have a ATI video card? how many of you have other Video / RF input connections and software? Does AHP detect other hardware other then what you connected at the time of installation?

[X10 Pro]

The next update will contain several fixes for iWitness video recording problems. All of the items mentioned here will be resolved.

[bronco]

I have an ATI all in wonder card.  Have not had a problem with the Video except:

I have two cameras connected with a Y cable to the USB.  Both cameras using the wireless x10 send and receive unit.
AHP does not correctly.   I have one set up as K11 and the next one as K12.
when I switch from K11 to K12 using AHP ,  AHP does not turn off K11 snding unit and since K11 is closer to the USB connector, it interfers with the transmission of K12.  The only solution I have found is to put an appliance module on the send and receiving units and create a macro that insures that K11 is turned off before K12 is turned on.  and vice versa.

[Mystyx]

2 wired cameras? or 2 wireless cameras?
those are send and recieve units seperate of the cameras? to a Y cable at your PC?

there is an easier way i think