Closed ProtoBelisarius closed 4 months ago
It just uses ffmpeg for frame extraction, if it's set to webp this can take a while. In the pre-release, I have updated rife to be used without frame extraction, if you want to try that out. If you want to use frame extraction, jpg is recommended for speed.
Yea, jpg works much better but how much worse is the degradation with that? At what quality setting is the jpg compression set? I already have a 1080p source and don't want to upscale.
I have it set to the closest to lossless setting, but it will have compression, shouldn't be too noticeable in the output video, though.
Ok, thank you for the prompt answers!
Before submitting an issue, please confirm it meets all the criteria
Describe the bug As mentioned in the title, frame extraction takes ages. Is there a setting for multithreading? Because it only uses one of 24 threads.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Logs If the application generates a log, please upload it here. Logs folder on Flatpak:
/home/$USER/.var/app/io.github.tntwise.REAL-Video-Enhancer/logs/
Logs folder on AppImage:/home/$USER/.local/share/REAL-Video-Enhancer/logs/
Desktop (please complete the following information):
GPU RX 6800XT, ncnn
Additional context Add any other context about the problem here.