X10 Community Forum

🖥️ActiveHome Pro => Plug-ins => iWatchOut/iWitness => Topic started by: lare on December 06, 2005, 04:23:06 PM

Title: iWitness Recorded Video's cut short
Post by: lare on December 06, 2005, 04:23:06 PM
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?
Title: Re: iWitness Recorded Video's cut short
Post by: magij on December 22, 2005, 06:58:20 PM
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?  
Title: Re: iWitness Recorded Video's cut short
Post by: WinS on December 28, 2005, 07:21:40 PM
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?
Title: Re: iWitness Recorded Video's cut short
Post by: WinS on December 29, 2005, 12:46:01 PM
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.
Title: Re: iWitness Recorded Video's cut short
Post by: magij on December 31, 2005, 01:57:30 PM
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?  
Title: Re: iWitness Recorded Video's cut short
Post by: magij on December 31, 2005, 01:57:34 PM
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?  
Title: Re: iWitness Recorded Video's cut short
Post by: jim k on January 01, 2006, 09:46:13 AM
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.
Title: Re: iWitness Recorded Video's cut short
Post by: bronco on January 29, 2006, 07:54:18 PM
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.
Title: Re: iWitness Recorded Video's cut short
Post by: WinS on January 30, 2006, 01:35:59 PM
Bronco
Regarding the time stamp, Universal Time is
used which is 4 or 5 hours (Dayight Savings
or Standard) ahead of East Coast Time.
Title: Re: iWitness Recorded Video's cut short
Post by: magij on January 30, 2006, 09:02:17 PM
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?  
Title: Re: iWitness Recorded Video's cut short
Post by: bronco on January 31, 2006, 11:34:29 AM
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.
Title: Re: iWitness Recorded Video's cut short
Post by: Mystyx on February 26, 2006, 01:12:09 AM
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?
Title: Re: iWitness Recorded Video's cut short
Post by: X10 Pro on February 27, 2006, 12:07:24 PM
The next update will contain several fixes for iWitness video recording problems. All of the items mentioned here will be resolved.
Title: Re: iWitness Recorded Video's cut short
Post by: bronco on March 12, 2006, 07:51:40 PM
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.
Title: Re: iWitness Recorded Video's cut short
Post by: Mystyx on March 12, 2006, 09:18:25 PM
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 :)
Title: Re: iWitness Recorded Video's cut short
Post by: bronco on March 31, 2006, 02:47:16 PM
two wireless cameras.  Each with its own separate wireless receivers. K11 and K12.
Both Receivers are near each other (20ft) One pointed North and the other pointed south.
I have tried using one receiver with the two cameras set at the same code such as 'D' on the receivers but I cannot get good reception from both cameras.  ONe will be good and the other bad.
If I leave both receivers on and just kill one of the cameras (say k11) then the receiver for camera (k11) will trainsmit enough garbage to interfere with getting a good signal for camera K12.
The only way I can get it to work is to kill both a camera and its receiver.
But AHP does not allow that in their scanning.
Title: Re: iWitness Recorded Video's cut short
Post by: Mystyx on March 31, 2006, 08:54:16 PM
You could play with a single receiver to get it working on both cameras...  I use one for 4 cameras.
Try setting the receiver 90degrees to all cameras or strait up to the ceiling. place the receiver as far from any monitors ect that create interference. maybe on a shelf higher up.
I have one receiver inbetween 2 monitors, I get a great picture, But if i move the receiver any way 2mm I get interference.

ALSO, in your setup as is....   If you set both cameras to different frequencies (under the rubber gasket) they may not interfere as much when switching as they would having both setup on the same (A-D) settings.

Try one camera on code A (NOT HouseCode) and the other on Code D
Title: Re: iWitness Recorded Video's cut short
Post by: bronco on April 01, 2006, 03:48:11 PM
I already have one receiver set to A and the other to D.  This absolutely means you need two receivers.  I thought that AHP was supposed to turn off all but the called for Camera.  I don't see that happening with is the problem.  I have tried moving a single receiver to many,many locations but I end up getting interference.  I don't get the interference using two receivers set at ( A & D).  It works ok, its that I can not use the scanning to go between cameras because all the scanning does is turn on the next one in line and never turns off the other one.
Therefore, I get interference.
I use an motion detector now to trigger a macro to start recording (AHP is still cutting the recordings short).  I get it to work fairly good with "Still' shots but Video is still a problem.
The other problem I have is that if the motion detector is hit multiple times it screws things up.
I have the motion detector that trigger a macro(N1) to see if flag2 is off, if it is then I send N4 signal that is on my PC that inturn turns on the camera and records for a minute and turns off.
I kept the macro(N1) simple so that multiple hits would not bother the N4Macro.
After multiple hits of N1 the N4 macro gets screwed up, I am guessing that there is too many collisions on the line, so N1 then always sees flag2 set so it does trigger N4.
I have tried many combinations of clearing the flag from N4, the most successful was sending a macro O15 to my old cm-11a that in turn sent out a N16 macro that is on the AHP to clear the flag.
From what I can find out AHP as well as the cm-11a are not designed to send a macro command to another macro on the AHP.  I have tried using phantom modules as well, but is not as reliable as using
the cm-aa. 
I have noticed an option in the AHP to allow multiple modules to use the same address which I have not explored yet.  I am running v3.302 AHP.  Do you have any experience on same addresses?
Title: Re: iWitness Recorded Video's cut short
Post by: Mystyx on April 01, 2006, 04:47:44 PM
Quote
I thought that AHP was supposed to turn off all but the called for Camera.

Yea, in sets of 4 if i remember. I remember back that HC K had some problems, you tried different ones though :)

Could be Distance / Signal problems then (dirty power in home) no filters ect. things like that matter, so without specifics of size, age of home, equipment in home (TVs PCs) and their positions ect would take this all into account. you seem to know about this though? :) things like "Find other Computers" under "tools" shows your HCs clean?

Also there is a problem with video recording and such that could make troubleshooting troublesome ;)
Title: Re: iWitness Recorded Video's cut short
Post by: tom j on April 03, 2006, 02:34:28 AM
The next update will contain several fixes for iWitness video recording problems. All of the items mentioned here will be resolved.

Say thinking about  purchasing this software have these video problems been resolved yet and how about the pan functions and tilt don't want any nasty surprises. Thanks

Tcj
Title: Re: iWitness Recorded Video's cut short
Post by: bronco on April 07, 2006, 07:45:54 PM
The pan and tilt functions of the Ninja are severly limited because you have to send the commands over the air (RF).  They can't be sent down the power line (BAD design).  So if anybody has their cm15a more that about 30 feet from the Ninja (mine is about 200ft)  it won't work.  X10 tells me that if I use a SR-731 RF repeater that it will work to extend the distant.  I have purchased 3 for another purpose but wouldn't you know it that the models I have don't repeat the Ninja commands.  I would need a later model.
From an X10 Person " The date code of 03E22 on a SR731 indicates it will work with Ninjas and Vanguards.  Older codes do not retransmit those commands".
Title: Re: iWitness Recorded Video's cut short
Post by: bronco on April 25, 2006, 11:34:38 AM
AS of 4-29-03  AHP at 3.203   I can only get max video at 1m 3sec.
I have a delay on one camera of 3 min and another with 7 min delay.  Still restricted to short video.
I have a 2 second delay after video stop to allow the file to close.
 :-\