Wrong FPS recorded about bescreencapture HOT 5 OPEN

Hi,
When recording, BeScreenCapture uses the frame rate set in the application options (default 20FPS, if I remember correctly).
When encoding, it calculates the FPS bases on number of frames and time.
It's possible that something doesn't work correctly, maybe the calculation is screwed on very fast machines.
I'll have a look.
Capture and Encoding is one thread because it uses the Haiku API to capture and encode.
Capture is inherently one thread in the API, Encoding could be multithreaded but it depends on the used addon.

from bescreencapture.

Hi! I had another look. It is likely that my disk i/o was a bottleneck so that BeScreenCapture couldn't save all frames to /tmp while recording. I was using a USB flash drive.

I tested again in a VM on a HDD this time and I got up to about 22 FPS, when selecting to record at 30 FPS. CPU usage was not high during recording, so I am not sure what happened here. See the resulting capture.mkv (zipped).
capture.zip

from bescreencapture.

Hi! I had another look. It is likely that my disk i/o was a bottleneck so that BeScreenCapture couldn't save all frames to /tmp while recording. I was using a USB flash drive.

I tested again in a VM on a HDD this time and I got up to about 22 FPS, when selecting to record at 30 FPS. CPU usage was not high during recording, so I am not sure what happened here. See the resulting capture.mkv (zipped).
[capture.zip]

Sorry for the late reply.
I made some tests on my Haiku system (a VM): the produced clip always has a bit fewer frames per second than I chose.
if I choose 20, I get a 18/19 fps clip.
if I choose 30, I get 28.

I'll have to review the recording loop to tweak the timing.

from bescreencapture.

Could you try with 2.5.2 ? It will now hit the disk only after it has exhausted almost all the available memory, so disk shouldn't be a bottleneck anymore.

from bescreencapture.

Could you try again with release 2.6.2 ?

from bescreencapture.