Getting errors or found a bug when converting faces from a trained model? Post about them here
This forum is for reporting errors with the Convert process. If you want to get tips, or better understand the Convert process, then you should look in the Convert Discussion forum.
Please mark any answers that fixed your problems so others can find the solutions.
GTX Titan X ( maxwell )
AMD 1950x threadripper
08/01/2020 20:59:17 INFO Loading Writer from Ffmpeg plugin...
08/01/2020 20:59:17 WARNING No GPU detected. Switching to CPU mode
- Site Admin
- Posts: 634
- Joined: Fri Jul 12, 2019 12:49 am
- Location: San Francisco
- Has thanked: 3 times
- Been thanked: 161 times
That isn't ffmepg using the CPU, that's Faceswap using the CPU, which is of more concern.
Please post the output from within Faceswap's "Help > Output System Information"
My word is final
opencv: 8m 11s
ffmpeg: 8m 18s
This isn't as drastic because h264/720p is not that complex, however when I performed the process on a 4 minute 5k video, ffmpeg was adding an additional 30+ minutes to encode the results into h265. I ended up having it output the images in opencv and manually running ffmpeg to merge the images into an h265 video which drastically cut the overall time down as I used a hardware encoder.
I unfortunately do not have logs for this, the next time I do a conversion on a video of that resolution I'll come back and post the logs for comparisons sake and to validate the claim.
Thanks for your time.
Code: Select all
gpu_devices: gpu_devices_active: gpu_driver: No Nvidia driver found
First and foremost make sure that your nvidia drivers are up to date and everything is in order on that side of things.
Also, as an aside, it is not a great idea to have a system installed version of Cuda, unless you have a very good reason to do so. It can lead to conflicts with the version installed inside your Faceswap environment, so if you can, I would recommend that you uninstall system Cuda.
As to your other issue, yes, HEVC encoding is slow. We do it on CPU because video encoding on GPU whilst also using the GPU for ML tasks is not a great idea. The way you are doing it (output to images then stitch back to video yourself) is the best way to proceed.
My word is final
I had the latest driver 451.67, but I kept having CUDA errors, downgrading to 451.48 fixed the issue.
Thanks for the input, I'll remove the local machines cuda installation and see if that has any positive/negative impact. I'll see if removing cuda does anything positive or negative on the local machine. I dont mind doing ffmpeg manually if thats best use.