Page 1 of 1

Bandicam 4.5.3.1608, capturing speed bottleneck in "Screen Recording Mode"

Posted: Sat Jan 04, 2020 11:19 am
by gdgsdg123
Follow-Up of the original post.


In "Screen Recording Mode", the capturing speed (how fast Bandicam can grab input frames from the Windows GDI) seems to be capped to around 30 FPS for most of the time, disregard of the target recording rate. (low CPU utilization during the event)

Unsure if the problem is from the GDI itself (inability per se to feed frames fast enough?), or Bandicam's handling.


May be related with "Use enhanced capture method"?.. Check the original post.





Testing Details

Environment:

Method:
  • DX9 application (moving scene) of constant frame rate (┬▒ 3.5% cumulative in 1 s) as the input source, recording duration of 30 s.

Test:
  1. Input (1920x1080 @ 60 FPS), video codec: MagicYUV (RGB); target recording rate: 60 FPS, "Screen Recording Mode", most frames in the output (both the raw and the mpdecimate'd version *) are of 30 FPS, and there are periodic (random?) frame rate fluctuations (usually within 15-60/20-120 FPS range) among the frames *.
  2. Input (1920x1080 @ 120 FPS), video codec: MagicYUV (RGB); target recording rate: 60 FPS, "Screen Recording Mode", similar to 1.
  3. Input (800x600 @ 60 FPS), video codec: MagicYUV (RGB); target recording rate: 120 FPS, "Screen Recording Mode", similar to 1.
  4. Input (800x600 @ 60 FPS), video codec: MagicYUV (RGB); target recording rate: 60 FPS, "Screen Recording Mode", similar to 1.
  5. Input (800x600 @ 60 FPS), video codec: RGB24; target recording rate: 60 FPS, "Screen Recording Mode", similar to 1.
  6. Input (800x600 @ 60 FPS), video codec: RGB24; target recording rate: 60 FPS, "Game Recording Mode", the raw output is almost 60 FPS CFR.
  7. Input (800x600 @ 60 FPS), video codec: MagicYUV (RGB); target recording rate: 60 FPS, "Game Recording Mode", the raw output is 60 FPS CFR.
  8. Input (1920x1080 @ 120 FPS), video codec: MagicYUV (RGB); target recording rate: 120 FPS, "Game Recording Mode", the raw output is almost 120 FPS CFR.
  9. A portion (800x600) of the static desktop as the input source (all frames are of identical content), video codec: MagicYUV (RGB); target recording rate: 60 FPS, "Screen Recording Mode", most frames in the raw output are of 60 FPS. (not reliably reproducible, sometimes severe frame rate fluctuations (avg. 30 FPS) among all frames *)
* There's actually not much difference between the raw and the mpdecimate'd ("mpdecimate=0:0:0") in general, except the first few frames at the start of the recording.
* Caused by the intrinsic frame rate fluctuations of the input source and the interference from other applications (other update requests)?..
* The behavior is related with the frequency of the update requests sent to the screen.



Off-Topic

I actually wanted to try 240 FPS at first but...
bdcam.png
bdcam.png (30.95 KiB) Viewed 603 times


The post also reveals valuable information on the choice of the recording mode.

Re: Bandicam 4.5.3.1608, capturing speed bottleneck in "Screen Recording Mode"

Posted: Tue Jan 07, 2020 7:24 pm
by Bandicam Company
Hello gdgsdg123,

Thank you for your reports.
We've confirmed the issue where some videos recorded with MagicYUV codec have lower frame rates than the original ones and forwarded it to our development team.
Also, we've found that there is no problem with H.264(NVIDIA NVENC) codec.

Thank you.

Re: Bandicam 4.5.3.1608, capturing speed bottleneck in "Screen Recording Mode"

Posted: Tue Jan 07, 2020 10:21 pm
by gdgsdg123
Bandicam Company wrote:We've confirmed the issue where some videos recorded with MagicYUV codec have lower frame rates than the original ones and forwarded it to our development team.

According to Test 8 and Test 5,6 it doesn't look like a codec issue...


Bandicam Company wrote:Also, we've found that there is no problem with H.264(NVIDIA NVENC) codec.

What's the testing detail?

Also reproduced with H264 (NVIDIA® NVENC). (Test 1 with similar settings here, tried both available GPU as "GPU device")

Sitrep on Bandicam 4.5.5.1632

Posted: Wed Feb 19, 2020 1:24 am
by gdgsdg123
After upgrading to Bandicam 4.5.5.1632, the problem seemed to be fixed (Test 1 failed to reproduce) for Windows 10 (not fixed for Windows 7).

Note: I also upgraded Nvidia Display Driver to 442.19, but I doubt it's related. (as the testing results with Bandicam 4.5.5.1632 on Windows 7 before/after the driver update are almost identical)