[GH-ISSUE #405] 录制帧率问题 #1701

New issue

Open

opened 2026-03-01 18:47:35 +03:00 by kerem · 4 comments

kerem commented 2026-03-01 18:47:35 +03:00

Owner

Copy link

Originally created by @IEtheReaLKnifL on GitHub (Dec 15, 2018).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/405

Originally assigned to: @NickeManarin on GitHub.

软件最高只支持60FPS, 我是120HZ的显示器, 录制的时候特别卡, 而且在全屏录制的时候CPU占用几乎100%
但是最骚的是录制的GIF很丝滑, 没有录制时的卡顿

Originally created by @IEtheReaLKnifL on GitHub (Dec 15, 2018). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/405 Originally assigned to: @NickeManarin on GitHub. 软件最高只支持60FPS, 我是120HZ的显示器, 录制的时候特别卡, 而且在全屏录制的时候CPU占用几乎100% 但是最骚的是录制的GIF很丝滑, 没有录制时的卡顿

kerem added the

🔷Enhancement

future feature

⬜ Help Wanted 💪

labels 2026-03-01 18:47:35 +03:00

kerem commented 2026-03-01 18:47:36 +03:00

Author

Owner

Copy link

@vatterspun commented on GitHub (Dec 16, 2018):

Care of Google Translate: The software only supports 60FPS, I am a 120HZ monitor, special card when recording, and the CPU is almost 100% when recording in full screen.
But the most confusing thing is that the recorded GIF is very silky, there is no recording when it is stuck.

Do you need to record above 60FPS? Or are you concerned about the high CPU usage?

<!-- gh-comment-id:447613154 --> @vatterspun commented on GitHub (Dec 16, 2018): > Care of Google Translate: The software only supports 60FPS, I am a 120HZ monitor, special card when recording, and the CPU is almost 100% when recording in full screen. But the most confusing thing is that the recorded GIF is very silky, there is no recording when it is stuck. Do you need to record above 60FPS? Or are you concerned about the high CPU usage?

kerem commented 2026-03-01 18:47:36 +03:00

Author

Owner

Copy link

@IEtheReaLKnifL commented on GitHub (Dec 16, 2018):

No, I don't need to record a 120FPS GIF.
My issue is when I record 60FPS GIF in full screen, the mouse slide is very stuck, and the CPU usage is very high, my CPU is 7700

<!-- gh-comment-id:447642054 --> @IEtheReaLKnifL commented on GitHub (Dec 16, 2018): No, I don't need to record a 120FPS GIF. My issue is when I record 60FPS GIF in full screen, the mouse slide is very stuck, and the CPU usage is very high, my CPU is 7700 

kerem commented 2026-03-01 18:47:36 +03:00

Author

Owner

Copy link

@vatterspun commented on GitHub (Dec 23, 2018):

As I understand it, the primary goal of ScreenToGif is a basic for creating quick demonstrations and how-to guides. The program isn't really suited for creating high FPS GIF files. This might be out of scope for the developer.

You might look into ShareX or OBS tools. Those might be a little more robust.

<!-- gh-comment-id:449608947 --> @vatterspun commented on GitHub (Dec 23, 2018): As I understand it, the primary goal of ScreenToGif is a basic for creating quick demonstrations and how-to guides. The program isn't really suited for creating high FPS GIF files. This might be out of scope for the developer. You might look into ShareX or OBS tools. Those might be a little more robust.

kerem commented 2026-03-01 18:47:36 +03:00

Author

Owner

Copy link

@NickeManarin commented on GitHub (Jan 6, 2019):

My issue is when I record 60FPS GIF in full screen, the mouse slide is very stuck, and the CPU usage is very high, my CPU is 7700

Indeed, the recording is a heavy operation. In order to be less resource demanding, I'll need to use DirectX.

<!-- gh-comment-id:451774198 --> @NickeManarin commented on GitHub (Jan 6, 2019): > My issue is when I record 60FPS GIF in full screen, the mouse slide is very stuck, and the CPU usage is very high, my CPU is 7700 Indeed, the recording is a heavy operation. In order to be less resource demanding, I'll need to use DirectX.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dev

v2.40

2.43.1

2.43

2.42.1

2.42

2.41.5

2.41.4

2.41.3

2.41.2

2.41.1

2.41

2.40.1

2.40

2.39

2.38.1

2.38

2.37.2

2.37.1

2.37

2.36

2.35.4

2.35.3

2.35.2

2.35.1

2.35

2.34.1

2.34

2.33.1

2.33

2.32.1

2.32

2.31

2.30.1

2.30

2.29.1

2.29

2.28.2

2.28.1

2.28

2.27.3

2.27.2

2.27.1

2.27

2.26.1

2.26

2.25

2.24.2

2.24.1

2.24

2.23.2

2.23.1

2.23

2.22.1

2.22

2.21.2

2.21.1

2.21

2.20.4

2.20.3

2.20.2

2.20.1

2.20

2.19.3

2.19.2

2.19.1

2.19

2.18

2.17.1

2.17

2.16

2.15.2

2.15.1

2.15

2.14.1

2.14

2.13.3

2.13.2

2.13.1

2.13

2.12.1

2.12

2.11

2.10

2.9

2.8.1

2.8

2.7.3

2.7.2

2.7.1

2.7

2.6

2.5

2.4

2.3.2

2.3.1

2.3

2.2

2.1

Labels

Clear labels   

copy cats

  

duplicated

  

future feature

  

pull-request

Mirrored from GitHub Pull Request

  

⬜ Accepted

  

⬜ Completed

  

⬜ Help Wanted 💪

  

⬜ In Progress

  

⬜ Missing Details

  

⬜ Pending

  

⬜ Waiting For Answer ⏳

  

🆕 feature preview

  

🔷 Bug 🐛

  

🔷 Out Of Scope

  

🔷 Out Of Scope

  

🔷 Question

  

🔷Enhancement

  

🔷Enhancement

  

🔷Invalid / External

  

🔷Knowledge Base

  

🔷Won't Fix

  

🕑 High

  

🕑 High

  

🕑 High

  

🕕 Medium

  

🕙 Low

  

🕛 Critical

No labels

copy cats

duplicated

future feature

pull-request

⬜ Accepted

⬜ Completed

⬜ Help Wanted 💪

⬜ In Progress

⬜ Missing Details

⬜ Pending

⬜ Waiting For Answer ⏳

🆕 feature preview

🔷 Bug 🐛

🔷 Out Of Scope

🔷 Out Of Scope

🔷 Question

🔷Enhancement

🔷Enhancement

🔷Invalid / External

🔷Knowledge Base

🔷Won't Fix

🕑 High

🕑 High

🕑 High

🕕 Medium

🕙 Low

🕛 Critical

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ScreenToGif#1701

No description provided.