Advertisement

Another known problem:The information about "Actions taken" in the motion detection's "Motion Events" is not correctly updated.
The text will say that a given action has been blocked by flood control even when this is not the case.
The real action takes place but the information says different...

I just downloaded the software and all the update files to bring it up to 0.2.6>7. Depsite initial streaming frustrations (the CODEBASE needs to start with "http://" [not mentioned in any instructions that I have read]), it works great! My only problem is that every time I close the program, it loses all of my settings. Also, it does not detect my 3Com Home Connect USB webcam. I can live with that for now, but the main concern is the lost settings issue. Help!

malun wrote:What settings are lost? The settings you can access from the menu, "settings -> edit settings..." or settings made to a html page?

All of them.

malun wrote:Check that you have a yawcam_settings.xml in your yawcam directory. This is where alla settings should be saved.

The file exists, but its contents are much more now than what the were before. I looked at the file before I lost all of my previous settings and the XML file was much smaller than what it is now. It's as if the file was not updated after a setting change.

malun wrote:

(the CODEBASE needs to start with "http://" [not mentioned in any instructions that I have read])

Hmm... perhaps that's not mentioned... I'll have a look at that.

It's not. It just says to swap in the IP adress of the computer running the software.

malun wrote:Does the "3Com Home Connect USB webcam" support VFW?

I am not sure.

malun wrote:Does the webcam work together with the software supplied with the camera?

tzankoff wrote:The file exists, but its contents are much more now than what the were before. I looked at the file before I lost all of my previous settings and the XML file was much smaller than what it is now. It's as if the file was not updated after a setting change.

Only the settings that are different from the default values will be written to the settings file. I you use all values as default the file will be almost empty.

Open the settings window, "settings -> edit settings..." and then click the OK-button. Now, check in the console-tab in the main window. Does it say "settings saved"?

I think the program is aware that I am on to it. Now that I have recreated all of my settings and saved a copy of the resulting XML file, the setting are not being forgotten anymore.

When attempting to detect cameras, the light on the webcam does flash for several seconds which would indicate that the camera has been detected; but when the scanning process was finished, the camera was not found.

tzankoff wrote:I think the program is aware that I am on to it. Now that I have recreated all of my settings and saved a copy of the resulting XML file, the setting are not being forgotten anymore.

Haha... You never know what the software decides to do when it has a free will.

tzankoff wrote:When attempting to detect cameras, the light on the webcam does flash for several seconds which would indicate that the camera has been detected; but when the scanning process was finished, the camera was not found.

Apparently the software scans the camera for all the video size modes. This is a good sign.
My guess is that the software somehow gets confused by your tv capture card. Try to occupy your tv-card with some other software first, then start Yawcam at the same time. This could be a good test. If Yawcam finds your webcam now, at least we know that Yawcam is compatible with the camera, but gets confused by the tv-card.

I don't know if this is the FREEZE bug or not, but I do have a situation that might be similar.

I'm using the newest beta (0.2.6>7).

1. I set up File captures every second. In the scheduler I set this to run 24-7.
2. I set up http streaming. I also set this in the scheduler to run 24-7.
3. I set up motion detection, but only have it set in the scheduler M-F 9am-6pm.

Today was the first day that I ran the whole setup. It worked fine during the day... it created the files correctly, streaming worked, and motion detection worked great. When I got home, I looked through all of the image captures (the ones from the File, not Motion Detection) and I noticed that at 6pm, the same image was repeated over and over. So, basically I have discreet images from 12am to 6pm and then from 6pm on the image captures were the same image. It seems a coincidence that this occured exactly as motion detection was shutting off from the scheduler.

I'll run it the same way tomorrow and see if it happens again.

In the last few days I've tried a lot of webcam apps looking for the perfect one, and BY FAR Yawcam is the best. Thanks for your hard work on it. I think the motion detection stuff is really great.

One feature request... I love the "Images to Movie" option. How about putting that in the scheduler as well? I'd love to have a movie of the previous days images produced automatically at the end of the day, named with the date and then have the images deleted after the movie was created. I found a command-line tool that creates a movie out of images and it works great, but it might be nice to have it incorporated into Yawcam.

Thanks!

*** UPDATE! I ran it again today and it froze at the same point. 6pm exactly when the motion detection was turning off with the scheduler. And just to be clear, the duplicate images I'm seeing have the overlay correctly updated... the actual image is static, the time on the overlay keeps updating. I'll run it again tomorrow without the scheduler.

Background: I’ve been using Yawcam off and on for a while now using 0.2.6 then to 0.2.7 and now BETA 2006-05-17.

Issue 1: I did incremental upgrades as they came out. I had no problem with camera detection as this was an upgrade. I had to rebuild a PC and went straight to BETA 2006-05-17 but the camera did not work. So ultimately I ended up going back and install 2.6 and let it the detect camera. Extracted 2.7 and 05-17 overwriting existing files and started Yawcam . The camera came on working as it should. I know it shouldn’t work due to overwriting files. I can only surmise that Yawcam.exe is reading an old file that did not get replaced OR the .exe is reading/writing a data in a different way. I hope this helps.

Issue 2: As stated in the previous post on freezing frames, I too am having the same problem. (BTW, I only use the Stream function and have not tried to use any other function) The only difference is that when there is sudden change of light (from light to dark), that’s when the camera freezes. The streaming still works because I have the date/time stamp showing that keeps going. This did not happen in 2.7 so naturally I would attribute this to the motion detection feature. To go into more depth on trying to “fix” this, I have tried to narrow down a solution but could not. The only way to fix the freeze is a reboot. Exiting Yawcam does not work. On exiting and restarting Yawcam, Yawcam assumes it is still running and gives the Port 8081 already in use and tries to use 8888. There were 2 Yawcam.exe's running in task manager. (BTW, it correctly locates the camera on re-executing Yawcam) After being patient and closing normally, I checked the Task Manager and noticed a Yawcam.exe still running. I attempted to end the Yawcam.exe but could not. The CPU was at 0% but still could not end it. While Yawcam is running but there are no active viewers does not seem to be an issue. Only when there are active viewers it seems to freeze.

I hope this will guide you to a solution that will provide an even better product. I will definitely donate more money in the future.

Additinal information: Exiting the view seems to freeze the camera also. Even though the time is moving the picture is frozen, HOWEVER, I can watch the FPS counting using the right mouse click. I can change the protocol, packet size, everything as if it is a live picture to include the resolution. It would seem like the problem is the browser window but then the preview window on the server is black, soooo.

First, great software, I've been using v 0.2.6 for a week now and love it and ready to make a little paypal contribution to keep it up. Thanks!

Could some please clarify that this beta version zip file is the WHOLE program or is it similar to an upgrade where I'm supposed to replace v 0.2.6 files? When I use it as a standalone it doesn't recognize my logitech camera which worked fine in previous versions. Am I supposed to upgrade 0.2.5 to 0.2.6 to earlier beta, to this beta?

Also, regarding v 0.2.6: I have my FTP password saved and it will upload 1 or 2 images fine to my server then the FTP username/password dialog box will pop open and not upload anymore...When I enter my password and click "Save password" and Ok, the box repeatedly pops open again and the password field is blank. I can only get out of it by clicking cancel which disables the FTP upload.

Is this a known issue that is fixed in any of these beta versions? My corporate proxy blocks most ports so I'm unable to stream but hope to get the FTP up and running.

mikepfly2 wrote:Could someone please clarify that this beta version zip file is the WHOLE program or is it similar to an upgrade where I'm supposed to replace v 0.2.6 files? When I use it as a standalone it doesn't recognize my logitech camera which worked fine in previous versions. Am I supposed to upgrade 0.2.5 to 0.2.6 to earlier beta, to this beta?

I just finished trying to get the latest beta version installed and working (hoping that it would solve my problem with 0.2.6) BUT it keeps indicating that it does not detect a camera. When I go through the Detect Camera it shows that Camera Detection FAILED almost immediately after starting (where 0.2.6 takes quite some time with camera detection and does detect the camera - vfw:Microsoft WDM Image Capture (Win32):0 :vfw://0 - it is a logitech camera).
I saw where you had made a debug batch file so I tried running the debug for you

The following is from the debug_log.txt file. I started yawcam, got the error indicating did not find a camera, then the options dialog opened, I canceled it, then clicked on menu Detect Camera and went through the detection phase, had the options dialog open up and canceled it and closed it down (note that I did not click on edit settings and the settings/options dialog opened on its own):