View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000575||Cinelerra-GG||[All Projects] Feature||public||2021-06-10 06:42||2021-06-11 07:12|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0000575: How to optimize the rendering speed of Cinelerra GG ?|
|Description||In accordance with @Andrea_Paz's last post on BT574 I have decided to continue the discussion by opening this new BT.|
The objective is to allow all potential users to benefit from the particular interest of this process that I use permanently.
You will find attached the following documents:
- The procedure
- The Bash script
|Tags||No tags attached.|
First of all, many thanks for your positive comments.
"The mknod command"
The mknod command does not create a file but a pipe. This pipe creates a link between ffmpeg and the cinelerra nodes. You can see that the size of the pipe in question does not increase.
"Is cin -r never used"
Yes, "cin -r" is never used. But I do use "cin -d" and I keep a Cinelerra as a master always open. I use it as a server to feed the Cinelerra nodes (cin -d). These nodes in turn feed the ffmpeg(s) via the pipes. I did try to use the "cin -r" command, which should improve performance.
But this command does not transfer the data correctly to ffmpeg. The system hangs at the pipe which is mistakenly considered as a file.
I don't know if this is a bug or if it was never implemented.
"Avidemux when is it used"
Indeed, avidemux is not in my script.
My script works in two steps
-First, it encodes the video alone in a file, using the render farm.
-Secondly, it encodes only the audio in a file, without using the render farm.
The mixing is then to be done manually with Avidemux because until now I still haven't found how to do an automatic mixing with ffmpeg. Indeed, I always have an audio/video lag in playback on a home cinema.
If anyone knows the answer? More work to do...
"There is probably a huge difference in power between Ryzen and Threadripper"
I don't know about your processor but this script greatly improves the rendering speed with the disadvantage of increasing the temperature of the said processor. Moreover, my movies are at least 60 minutes long (finished) and I often use a lot of plugins. These two elements together mean that my processor does not have time to breathe.
"So I will have to make several adaptations to your script, but I don't know if I will be able to"
Let me know if you need more information.
"This script could be the subject of an additional section of the manual, following yours already in the appendix."
I am not against the principle of sharing my method with all users.
Awesome work, my compliments!
It will take me a long time to study your script, given my ignorance. At first glance I don't really understand the mknod command, it creates a file of what type? Is "cin -r" never used? Avidemux when is it used?
There is probably a huge difference in power between Ryzen and Threadripper. Using the renderfarm with 16 threads active on 16 (at 100%) for about 20 min, the temperature always stays below 70°C with only a few spikes towards 73-74°C. I use stock air cooling, however I must say I have taken good care of the airflow inside the case.
So I will have to make several adaptations to your script, but I don't know if I will be able to. I will let you know. Anyway thank you and congratulations for the great solution you found.
PS: This script could be the subject of an additional section of the manual, following yours already in the appendix.
rendu_en_h264_via_pipes_parallélisés.sh (6,357 bytes)
Procedure.pdf (41,433 bytes)