Tests with beta 2006-05-17
Posted: Sun Sep 24, 2006 6:40 pm
Hi,
I used Yawcam some time ago and did not have it installed for some time due to some major system upgrades and OS reinstalls. I did get the current stable version 0.2.6 and attempted to run two instances with my Logitech QuickCam Web and Kodak DVC300. It failed.
I then gave the latest beta a try. I did install first only the files that come in the beta package and that made Yawcam crash right away. I then took the latest stable release and overwrote those files with the current beta files (quasi update) and that not only brought in some more stability, but I was able to run two instances at the same time having each use a different camera. I did come across some problems that may need to get addressed in a final version.
1.) Address conflicts for HTTP and Stream. If address is in use increase address by one and check again. The current workaround is to start one instance, change the settings, then start the other.
2.) Not surprising, the source selection is somewhat unstable (as it says, it is experimental). Nevertheless, after several tries it does work.
3.) Automatic opening of the settings form. Once it opened I did not have a chance to close it with either OK or Cancel or X. This problem occured only when two instances of Yawcam were running.
Besides that, it was as easy as ever. It for sure would be nice to be able to manage two (or more) cameras with the same Yawcam instance. That is maybe something for versions 0.3.x.
So, overall, stability seems to be the issue, everything else is right on.
Just one addition, it appears as that Yawcam always asks which device to use on startup when there is more than one available. It should connect to the one used last and only if that one is not available asks to select one. This way one can fire up Yawcam on boot and not worry about it.
Also, worthwhile to mention in the documentation is that one should connect USB webcams on different controllers. I had mine connected on the same and constantly got the bandwidth saturation message and nothing really worked (not even a single camera only). I do have two entirely independent USB controllers (one onboard, one PCI extension card) and using both fixed the problem. I can stream both cameras at the same time.
Finally, one praise, the idea to add a scheduler is absolutely fantastic!
I used Yawcam some time ago and did not have it installed for some time due to some major system upgrades and OS reinstalls. I did get the current stable version 0.2.6 and attempted to run two instances with my Logitech QuickCam Web and Kodak DVC300. It failed.
I then gave the latest beta a try. I did install first only the files that come in the beta package and that made Yawcam crash right away. I then took the latest stable release and overwrote those files with the current beta files (quasi update) and that not only brought in some more stability, but I was able to run two instances at the same time having each use a different camera. I did come across some problems that may need to get addressed in a final version.
1.) Address conflicts for HTTP and Stream. If address is in use increase address by one and check again. The current workaround is to start one instance, change the settings, then start the other.
2.) Not surprising, the source selection is somewhat unstable (as it says, it is experimental). Nevertheless, after several tries it does work.
3.) Automatic opening of the settings form. Once it opened I did not have a chance to close it with either OK or Cancel or X. This problem occured only when two instances of Yawcam were running.
Besides that, it was as easy as ever. It for sure would be nice to be able to manage two (or more) cameras with the same Yawcam instance. That is maybe something for versions 0.3.x.
So, overall, stability seems to be the issue, everything else is right on.
Just one addition, it appears as that Yawcam always asks which device to use on startup when there is more than one available. It should connect to the one used last and only if that one is not available asks to select one. This way one can fire up Yawcam on boot and not worry about it.
Also, worthwhile to mention in the documentation is that one should connect USB webcams on different controllers. I had mine connected on the same and constantly got the bandwidth saturation message and nothing really worked (not even a single camera only). I do have two entirely independent USB controllers (one onboard, one PCI extension card) and using both fixed the problem. I can stream both cameras at the same time.
Finally, one praise, the idea to add a scheduler is absolutely fantastic!