Testing fullscreen video capturing @ 60 FPS

[UEZ]

Can someone with a 2K+ monitor test whether screen recording works at 60 fps? The previous version used the GDI API to send frames to the codec, which is too slow at high screen resolutions. Windows build 18362+ required!

Link to: ScreenRecorder2_vfw

Please unzip the 7-Zip archive and run one of the executable files. Recording will begin on the main screen as soon as the CMD window appears and a yellow rectangle is displayed.

 

Please run “Configure_x264vfw.cmd” (default is the x64 DLL version), adjust the settings according to this screenshot, and then click “OK”:

Once the recording is complete, the “Actual Time” should be roughly equal to the “Target Time,” which is 15 seconds (900 frames).

 

Can you please post your screen size and the “actual time”?

My result:

1920x1200

Actual time  : 15.01514229999849 seconds

 

The closer the actual time is to the recorded time, the more accurate the recording was.

 

Thanks.

Edited April 14 by UEZ

[AndyG]

Hi,

2560x1440 @60FPS

  Frame 870 encoded.
Actual time  : 15.01036810000005 seconds
Closing...
File finalized. Frames: 900
File size : 18 mb
Done! -> output_wgc.avi

👍

 

Edited April 14 by AndyG

[UEZ]

@AndyG Were there any problems with the player? @Danyfirex reported problems with VLC Player playing AVI file.

Edited April 14 by UEZ

[UEZ]

7 hours ago, Danyfirex said:

It does work but before play with VLC it says this:

 

Saludos

Should be fixed now - you may try it again. x64 should work - x86 may have some issues and may crash!

 

Btw, I renamed the GraphicsCaptureWrapper DLLs and record time is now 20 seconds. You don't need Ultrafast, Superfast should be ok, too.

 

Edited April 14 by UEZ

[Danyfirex]

Hello. X64 works fine for me. But for x86 I just get this.
 

It just exits after one or two seconds.

Saludos

 

 

Edited April 15 by Danyfirex

[AndyG]

22 hours ago, UEZ said:

@AndyG Were there any problems with the player? @Danyfirex reported problems with VLC Player playing AVI file.

I had no trouble playing the .avi file with the windows media player, It doesn't matter whether it's x86 or x64 (Win11 pro 24H2)

No video problems with Cyberlink PowerDVD Player, IrfanView (x64) , MS Clipchamp, Winamp....

 

Edited April 15 by AndyG

[UEZ]

Thank you both for testing. 👍

@AndyG my previous version is ok for x86 because I didn't use threading. With lasted update I changed it to threading, ergo encoding is executed in a separate thread but for some reason it doesn't work for x86. Actually I cannot find the issue - maybe VfW‑Thread‑Affinity‑Problem under x86.

Edited April 15 by UEZ

[Danyfirex]

Both are working perfect to me already

 

Saludos

[wakillon]

Salut UEZ

With the desired settings ,

32 bit version return : 

WGC Recording: 3840x2160 @ 60 fps
Target time  : 15 seconds
Press 'P' to Pause, 'R' to Resume, 'ESC' to Stop
  Frame 0 encoded.
x264 [error]: malloc of size 26200384 failed
x264 [error]: malloc of size 26200384 failed
x264 [error]: malloc of size 26200384 failed
x264 [error]: malloc of size 26200384 failed
x264 [error]: malloc of size 26200384 failed
x264 [error]: malloc of size 26200384 failed
x264 [error]: malloc of size 26200384 failed
x264 [error]: malloc of size 26200384 failed
...

x64 return :

WGC Recording: 3840x2160 @ 60 fps
Target time  : 20 seconds
Press 'P' to Pause, 'R' to Resume, 'ESC' to Stop
Starting thread for recording...
  Frame 1140 encoded.
Waiting for background thread to finish...
Thread closed.
Actual time  : 29.63338000000113 seconds
FPS real : 40.49487436127618
File size : 3 mb
Done! -> output_wgc.avi

 

And no problem for read video with VLC, except the reading speed which is 2 times faster
I saw my desktop Clock changing second too fast

 

[UEZ]

@wakillon thanks for testing. vfw is now replaced with x264 dll.

 

@All:

Can you please test: ScreenRecorder.7z

 

It is now GUI driven. Limitations: 2GB AVI file and Windows10+.

Edited Friday at 07:33 PM by UEZ

[wakillon]

You're welcome 😉

 

First problem, your graphical interface is hard to read as if you were using transparency

Second problem, If there is no user activity the  duration of the video is almost the same as the real duration, but if i open and minimize several windows while recording, your display timer is late ( example 1m42 for 2 min recording)

 

[Gianni]

I recorded for about a minute just by pressing the Start button and without changing any settings, but when I open the file, the media player displays this message: "Cannot open Capture_..._... It's using unsupported encoding settings." (win11 x64)
Am I doing something wrong?

Edited Saturday at 08:27 AM by Gianni

[UEZ]

1 hour ago, wakillon said:

You're welcome 😉

 

First problem, your graphical interface is hard to read as if you were using transparency

Second problem, If there is no user activity the  duration of the video is almost the same as the real duration, but if i open and minimize several windows while recording, your display timer is late ( example 1m42 for 2 min recording)

 

Yes, I can reduce transparency. When the background is dark it looks nice but on brighter background it becomes harder to read. Let me check if it is possible to get the recording time rather than a parallel timer.

 

55 minutes ago, Gianni said:

I recorded for about a minute just by pressing the Start button and without changing any settings, but when I open the file, the media player displays this message: "Cannot open Capture_..._... It's using unsupported encoding settings." (win11 x64)
Am I doing something wrong?

Obviously Windows cannot play AVI file because of missing decoder for H264 - MPEG-4 AV (part 10) (h264) (same on my Win11). You can use VLC Player, MediaPlayer Classic or any other app which supports this codec.

 

Thanks for testing. 👍

 

Btw, defaults are 30 fps and Region doesn't work properly yet because of some unknown stride settings...

Edited Saturday at 09:21 AM by UEZ

[UEZ]

@wakillon I updated the code. Can you please download the new version and test it again? I uploaded the GraphicsCaptureWrapper64.dll v0.5.1 which works for Region capturing. There is a problem with new version...

Merci.

[wakillon]

No problem but your download link to: ScreenRecorder2_vfw do not work 

 

[UEZ]

1 hour ago, wakillon said:

No problem but your download link to: ScreenRecorder2_vfw do not work 

 

I meant ScreenRecorder.7z (GUI version).

vfw is no longer being developed (links are dead).

Edited Sunday at 09:45 AM by UEZ

[wakillon]

Oups !

Your graphical interface is now so tiny that I can't read the buttons

A DPI problem ?

Video quality is good but a record of 30 sec give me a video of 22 sec

[UEZ]

1 hour ago, wakillon said:

Oups !

Your graphical interface is now so tiny that I can't read the buttons

A DPI problem ?

Video quality is good but a record of 30 sec give me a video of 22 sec

Can you please give me following information

1. fullscreen capture? if yes, which resolution?
2. is DPI > 100%?
3. how did you measured the time difference?

I called SetProcessDPIAware() that might be the reason for the DPI scale. Tomorrow I can test in my office on 3 monitor environment.

[wakillon]

FullScreen Capture : 3840x2160 @ 60 fps

DPI Scale x3

I recorded for 30 seconds but the playback only took 22 seconds when looking at the clock

it's a bit like if I were watching a video in fast motion

Edited Sunday at 02:14 PM by wakillon

[UEZ]

I assume that sending frames to the encoder is taking too long, which prevents the target FPS from being reached, causing the video to play back faster (frame dropping due to hardware encoding bottlenecks at 4K @ 60 FPS.). It’s also possible that the encoder can’t process the volume of data at 60 FPS.

You may try the "ultrafast" setting, default is "veryfast" and set to 30 FPS.

 

Unfortunately, these are the limitations of this setup involving screen capture (CPU -> GraphicsCaptureWrapper DLL) and an x64 encoder (x264 DLL).

It is very likely that only code based on a hardware encoder (GPU) can handle this load without frame drops. At 4K resolution and 60 frames per second, the CPU has to process about 500 million pixels per second.

Edited Sunday at 03:03 PM by UEZ