In this topic I'll try to list the currently known bugs.Images to Movie can't handle 100 000 files / 2.5 GB data
The function "Images to Movie" can't handle larger amount of data.
The prgress bar will stop when trying to finalize the movie file and the produced movie will be corrupt and not playable.Interval bug
If you set the upload/save interval to a value larger than 9999 seconds Yawcam will upload/save the images _every_ second instead.freeze bug (fixed in 0.3.0)
Some users have problems with that the video freezes aftar a while when using the stream output.
If you have this problem, get the latest beta version from here:viewforum.php?f=5
It will hopefully fix the problem for you...open-url-bug (fixed in 0.2.1)
This concerns users of windows95 or windows98. When trying to open the help file or visiting the yawcam webpage from the help menu, nothing happens.ftp-directory-bug (fixed in 0.2.3)
There will not be any warning if the upload directory on the ftp doesn't exists. Yawcam will continue to run like all worked, but the image will not be uploaded.Stream-startup-bug (fixed in 0.2.3)
If the stream output is set to start automatically when Yawcam starts, Yawcam will have a higher CPU usage when no user is watching.**
Temporary solution: Don't use the the startup function for the stream output. Start the stream output by clicking the button manually instead.**GifEncoder-bug (fixed in 0.2.3)
When you save an image as a GIF it sometimes is impossible to preview or delete the image until you have exited Yawcam.ftp-time-out-bug (fixed in 0.2.3)
If the ftp upload times out during a transfer, Yawcam will not give any warning. Instead it will stop the ftp output. Not good at all... (Thanks to Frans Faase who noticed this.)Hidden-startup-bug (fixed in 0.2.5)
Some users have problems to start Yawcam if the option "Hide to traybar at start" is selected. Yawcam then crash or freeze when showing the splash screen.**
Temporary solution: Don't use this option if you experience these problems.**