

Check using e.g. top
for your CPU (nvidia-smi
or amd-smi
for your GPU) or System Monitor on KDE if any of your resource is being maxed out. If so then most likely you found the culprit.
Regarding what the actual codec is being used you can use ffprobe
but anyway what matters if resource bottleneck and thus if you can have hardware acceleration for it.
It’s probably worth investigating so that you don’t keep on getting video files too big for your computer to handle. I imagine it’s something very high resolution with very recent compression. If so, look for something less demanding, e.g. x265 720p and if that’s still leading to performance hiccups the older x264 720p or even 480p.
It’s rare that the media player itself, e.g. VLC or mpv, actually is the bottleneck.
Why? I have a hard time imagine a use case where restoring the OS itself would be appropriate.
I can imagine restoring data, obviously, and services running with their personalization … but the OS is something generic that should be discarded at whim IMHO. You probably chance few basic configuration of some services and most likely that’s stored in
/etc
but even then 99% is default.You can identify what you modified via shell history, e.g.
history | grep /etc
and potentially save them or you can also usefind /etc -type f -newerXY
with a date later than the OS installation and you should find what you modified. That’s probably just a few files.If you do back up anything beyond
/home
(which should be on another partition or even disk than the OS anyway) you’ll most likely save garbage like/dev
that might actually hinder your ability to restore.So… sure, image the OS if you actually have a good reason for it but unless you work on archiving and restoring legacy hardware for a museum then I doubt you do need that.