Your help has been invaluable. Thank you.
I ended up loading Windows 7 onto an old HP Pavilion dv5000 with 4GB RAM. This allowed me to see some of the potential problems with the WriteBuffer Procedure, especially on slower systems.
Please try the new version.
1. When XML Builder opens, change the Video FPS value to zero.
- this will enter the program into Test FPS mode
2. Save the XML files, the Bullseye window will open.
3. Press CTRL + Y to start the test.
- the test will auto-end after 45 seconds
- note the various FPS values, close the message box, XML Builder will open
4. Set Video FPS to the maximum value reported from Test FPS
There are two FPS settings, one you can change and the other is limited by a computers resources, how the program processes images, and the video codec.BasicallyPure wrote:I am confused about what the FPS setting actually does.
I had assumed that if I recorded for 1 minute in real time the resulting video would be 1 minute long and a FPS setting of 1 would result in the video image changing once every second.
Obviously there is something I am not understanding. Where does the 30 FPS come from and is it always 30? How do I make the captured video run at the same speed (length) as real time events?
The Video FPS setting you can change determines how many frames per second your video displays during playback.
The other FPS setting is the maximum number of images the program can capture per second.
If the program can only capture 10 FPS, but you set Video FPS to 30, then a 5 minute video will take 15 minutes to record.
Setting Video FPS to the maximum (+5 / -5) reported from Test FPS should create a video with smooth playback.
- the maximum FPS your system can capture might change for different sized windows
- increase / decrease the Video FPS setting until the desired result is achieved