/tech/ - Tech


Mode: Reply

Max message length: 8192


Max file size: 20.00 MB

Max files: 3


(used to delete files and postings)


Remember to follow the rules

(79.24 KB 960x960 1565408584324.jpg)
Comrade 05/21/2020 (Thu) 10:44:39 No. 1887
I wanted to speed up a video with ffmpeg, did it the https://trac.ffmpeg.org/wiki/How%20to%20speed%20up%20/%20slow%20down%20a%20video way outlined here >ffmpeg -i input.mkv -filter_complex "[0:v]setpts=0.5*PTS[v];[0:a]atempo=2.0[a]" -map "[v]" -map "[a]" output.mkv but after 5 minutes of my graphics card sounding like it was going to explode, and being told it was doing 1000fps, i stopped it. it was only a 3 minute clip. Did something go wrong or did I pussy out?
i'm not aware of ffmpeg being gpu-accelerated, pretty sure it uses just your cpu, at 100% and that usually causes your cpu fan to run at full throttle download this and check the cpu temp and gpu temps while encoding with ffmpeg https://openhardwaremonitor.org/downloads/ as long as your cpu or gpu doesn't reach 70C you should be fine
also if the cpu temp goes past 70C you can limit ffmpeg to encode with just one cpu core with the "-threads 1" option assuming you have a multicore cpu which may reduce the temp at the cost of longer encoding times
>>1888 >'m not aware of ffmpeg being gpu-accelerated https://trac.ffmpeg.org/wiki/HWAccelIntro Did you even look?
>>1893 in your link it says you have to explicitly include a gpu option. it also says in your link that gpu acceleration is still shit quality-to-bitrate: >Hardware encoders typically generate output of significantly lower quality than good software encoders like x264, but are generally faster and do not use much CPU resource. (That is, they require a higher bitrate to make output with the same perceptual quality, or they make output with a lower perceptual quality at the same bitrate.) there's a reason it's disabled by default, retard. you should never use gpu-accelerated encoding unless you're a streamer using obs with a cpu too weak to handle it


no cookies?