Quote:
Originally Posted by sp4ce_c0wb0y
Can you define what you mean by "freezing"? Do you have to hard shut off your computer? Is it just unresponsive for a few minutes or while the command is running? Additionally, what are the specs of your computer?
|
System specs:
Quote:
Device name *****
Processor Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz 1.80 GHz
Installed RAM 8.00 GB
Device ID 53D6784B-E04E-405E-90BC-FD5A73AE2EBE
Product ID 00325-80136-65388-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 10 Home
Version 21H1
Installed on 7/28/2020
OS build 19043.1165
Experience Windows Feature Experience Pack 120.2212.3530.0
|
It seemed to hang when I put it that command although some people told me that the command itself might be flawed. It might because I had kept it on without properly shutting it down for a long time as it seemed to work better when I restart it. When I put in that command, it seemed to "freeze" the computer in place although it might due to the command and not restarting the computer for a long time.
Quote:
Originally Posted by sp4ce_c0wb0y
For something you can test right now, download prime95 and run it for benchmarking. If your computer "freezes" in the same way it's probably a hardware issue, not a ffmpeg issue.
|
I will try that to see if what you suggested is true.