I've only been using cin for about 3 months. I could have sworn I tested the render speed vs others and was happy. This is just odd. I've tried the render farm idea as well. Sometimes tho, I get an empty file. Don't know why. So I'm gun shy to try it for this project where I have 3 hours estimated, it's only 15 minute video, ugh. There are no errors at all printed to the console if I launch cin from the terminal. The nvidia settings do show that about 5-8% load. I'm used to seeing that at 50-60% in other editors and also in OBS. I know my pc is not "new" and the "fastest" but it would be faster if I were to make the compositor borderless and record that with OBS. It's really odd, the compositor isn't dropping any frames whatsoever. All my effects look *awesome * in the compositor. The app is running awesome. I've not had a crash at all. On Thu, Jul 15, 2021 at 8:32 AM Andrea paz via Cin < [email protected]> wrote:
Lately many people are experiencing performance problems in encoding, I am one of them. I think the cause is the lack of multithreading in encoding (but also decoding in timeline). A rendering done with external ffmpeg from command line is much more efficient than the same rendering done in CinGG (always using ffmpeg). No fix has been found, only a workaround that makes use of the Render Farm:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Render_Farm_Usage.html
Lately the user fary54 has made available his script to automate the use of the render farm and external ffmpeg. Above all it is suitable for CPUs with many threads. You can find the script and explanations here:
https://www.cinelerra-gg.org/bugtracker/view.php?id=575 -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin