Hi all. I'm a debian user, but today I compiled ffmpeg (why?) with hardware acceleration (based on https://developer.nvidia.com/ffmpeg ) I want to use this ffmpeg version to encode (rendering) in CinGG. It's possible without --with-cuda option in CinGG compilation? I can use "ffmpg -hwaccel cuvid " in console to transcode, but those are input parameters, not just output options. Thaks all Sergio
GG writes: There are 3 classes of hw accel in cinelerra via ffmpeg. vaapi, vdpau, and cuda. The generic hw interface of ffmpeg is use to select hw decoding using the selected preference in the settings->preferences->performance->use hw device popup menu. The decode_activate operation attempts to decode the first hw frame, and if the initialization fails then the sw decoder is used as a fallback. The normal 3rd party build will configure and build a current version of ffmpeg with a few patches that provide improved operation. I would recommend using it. The standard cmdline versions of ffmpeg and ffprobe are built into the thirdparty build directory for ffmpeg with the normal static library builds. To use the hw for transcodes is not exactly straight forward from the command line. For example, vdpau is decode only. There are free and non-free versions, and the non-free versions are not in the 3rd party build. There is a vaapi transcode src code example in ffmpeg-4.2/doc/examples/vaapi_transcode.c. It probably only works with a limited set of codec formats. It is a good idea to load, vainfo, vdpauinfo. See "hardware acceleration" in the "Performance andTips" chapter 19 of CinelerraGG_Manual.pdf on the website. Various nvidia codecs require non free api library interfaces. The implementation may require at least a certain version of nvidia software or library baselines before it can work properly. I would have to study the exact problem you are trying to solve, and the code support before it can be determined if the library can do the problem you wish to solve. Please feel free to ask specific questions. gg On Thu, Apr 9, 2020 at 7:14 PM <[email protected]> wrote:
Hi all. I'm a debian user, but today I compiled ffmpeg (why?) with hardware acceleration (based on https://developer.nvidia.com/ffmpeg )
I want to use this ffmpeg version to encode (rendering) in CinGG. It's possible without --with-cuda option in CinGG compilation?
I can use "ffmpg -hwaccel cuvid " in console to transcode, but those are input parameters, not just output options.
Thaks all
Sergio -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Thanks for reply! I could compile CinGG with cuda, I used debian's package nvidia-cuda-sdk to compile ffmpeg and CinGG too, but cuda samples is needed too (basically, helper_cuda.h and few more). Debian use /usr/lib/cuda for libs and /usr/bin for nvcc, so I must to create a symbolic to /usr/lib/cuda/bin/nvcc (export variable path was not sufficient, compilation procces search nvcc un CUDA_PATH/bin/nvcc) that's all. My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me. Thanks a lot! Sincerelly. Sergio El 2020-04-10 01:21, Phyllis Smith escribió:
GG writes: There are 3 classes of hw accel in cinelerra via ffmpeg. vaapi, vdpau, and cuda. The generic hw interface of ffmpeg is use to select hw decoding using the selected preference in the settings->preferences->performance->use hw device popup menu. The decode_activate operation attempts to decode the first hw frame, and if the initialization fails then the sw decoder is used as a fallback. The normal 3rd party build will configure and build a current version of ffmpeg with a few patches that provide improved operation. I would recommend using it. The standard cmdline versions of ffmpeg and ffprobe are built into the thirdparty build directory for ffmpeg with the normal static library builds.
To use the hw for transcodes is not exactly straight forward from the command line. For example, vdpau is decode only. There are free and non-free versions, and the non-free versions are not in the 3rd party build. There is a vaapi transcode src code example in ffmpeg-4.2/doc/examples/vaapi_transcode.c. It probably only works with a limited set of codec formats. It is a good idea to load, vainfo, vdpauinfo. See "hardware acceleration" in the "Performance andTips" chapter 19 of CinelerraGG_Manual.pdf on the website.
Various nvidia codecs require non free api library interfaces. The implementation may require at least a certain version of nvidia software or library baselines before it can work properly. I would have to study the exact problem you are trying to solve, and the code support before it can be determined if the library can do the problem you wish to solve.
Please feel free to ask specific questions. gg
On Thu, Apr 9, 2020 at 7:14 PM <[email protected]> wrote:
Hi all. I'm a debian user, but today I compiled ffmpeg (why?) with hardware acceleration (based on https://developer.nvidia.com/ffmpeg )
I want to use this ffmpeg version to encode (rendering) in CinGG. It's possible without --with-cuda option in CinGG compilation?
I can use "ffmpeg -hwaccel cuvid " in console to transcode, but those are input parameters, not just output options.
Thaks all
Sergio -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me.
One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working. The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want. A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button". None of these are easy and you are a brave man to attempt them !! Phyllis
I also compile CinGG with Cuda, but the only result is the availability of the 2 cuda-plugins. From inside CinGG, to speed the encoding, try using h264-nvenc.mp4 and h265-nvenc.mp4
Hi Andrea. Thanks! Yes, with h264-nvenc.mp4, h265-nvenc.mp4 and changing hwaccel_flags to (0x00000002) allow_high_depth, works better, but I'm not sure why. Thanks for yout attention. Sergio El 2020-04-11 09:48, Andrea paz escribió:
I also compile CinGG with Cuda, but the only result is the availability of the 2 cuda-plugins. From inside CinGG, to speed the encoding, try using h264-nvenc.mp4 and h265-nvenc.mp4
Thanks a lot! Well... pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG Sergio El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me.
One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working.
The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want.
A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button".
None of these are easy and you are a brave man to attempt them !! Phyllis
Sergio, Thank you so much for sharing your results which are quite impressive. Am I understanding correctly that the only change you ended up making was the"*hwaccel_flags to (0x00000002) ?? *allow_high_depth" to the h264-nvenc.mp4 ffmpeg option file? I want to add that as a choice for others to see. Probably your newer/higher end graphics board was very beneficial -- a good way to justify upgrading if using h264/h265. GG/Phyllis On Sat, Apr 11, 2020 at 7:07 AM <[email protected]> wrote:
Thanks a lot! Well...
pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent
Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG
Sergio
El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me.
One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working.
The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want.
A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button".
None of these are easy and you are a brave man to attempt them !! Phyllis
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Phyllis, Yes! just this parameter, but if you want, give me a few day to more test. At this moment.. rendering 4minutes x 30 fps, full-hd, with masks, 11.685fps, rendering same time with constant zoom and chromakey, 9.04 fps. The detail is,before was rendering a 6 fps. I want to test little more to confirm stability, HW rendering I can confirm now. Sergio El 11/04/2020 a las 13:38, Phyllis Smith escribió:
Sergio, Thank you so much for sharing your results which are quite impressive. Am I understanding correctly that the only change you ended up making was the"*hwaccel_flags to (0x00000002) ?? *allow_high_depth" to the h264-nvenc.mp4 ffmpeg option file? I want to add that as a choice for others to see. Probably your newer/higher end graphics board was very beneficial -- a good way to justify upgrading if using h264/h265.
GG/Phyllis
On Sat, Apr 11, 2020 at 7:07 AM <[email protected] <mailto:[email protected]>> wrote:
Thanks a lot! Well...
pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent
Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG
Sergio
El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me.
One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working. The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want. A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button". None of these are easy and you are a brave man to attempt them !! Phyllis
-- Cin mailing list [email protected] <mailto:[email protected]> https://lists.cinelerra-gg.org/mailman/listinfo/cin
Great, I am in no hurry and also would like to include your statistics in the manual if possible. On Sat, Apr 11, 2020 at 3:30 PM Sergio Daniel Gomez < [email protected]> wrote:
Phyllis, Yes! just this parameter, but if you want, give me a few day to more test. At this moment.. rendering 4minutes x 30 fps, full-hd, with masks, 11.685fps, rendering same time with constant zoom and chromakey, 9.04 fps. The detail is,before was rendering a 6 fps.
I want to test little more to confirm stability, HW rendering I can confirm now.
Sergio El 11/04/2020 a las 13:38, Phyllis Smith escribió:
Sergio, Thank you so much for sharing your results which are quite impressive. Am I understanding correctly that the only change you ended up making was the"*hwaccel_flags to (0x00000002) ?? *allow_high_depth" to the h264-nvenc.mp4 ffmpeg option file? I want to add that as a choice for others to see. Probably your newer/higher end graphics board was very beneficial -- a good way to justify upgrading if using h264/h265.
GG/Phyllis
On Sat, Apr 11, 2020 at 7:07 AM <[email protected]> wrote:
Thanks a lot! Well...
pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent
Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG
Sergio
El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me.
One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working.
The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want.
A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button".
None of these are easy and you are a brave man to attempt them !! Phyllis
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
It's not a problem to me. I just want to offer a true information, tested... Additionally, and another topic... I was trying a lot of possibiliies to get the best performance possible... One was transcode option to replace media in video. One of them, was a movil (cellphone) video ( 720x1440) , it was transcoded adding black bands to complete 16:9 aspect, 1920x1080. El 2020-04-11 19:29, Phyllis Smith escribió:
Great, I am in no hurry and also would like to include your statistics in the manual if possible.
On Sat, Apr 11, 2020 at 3:30 PM Sergio Daniel Gomez <[email protected]> wrote:
Phyllis, Yes! just this parameter, but if you want, give me a few day to more test. At this moment.. rendering 4minutes x 30 fps, full-hd, with masks, 11.685fps, rendering same time with constant zoom and chromakey, 9.04 fps. The detail is,before was rendering a 6 fps.
I want to test little more to confirm stability, HW rendering I can confirm now.
Sergio
El 11/04/2020 a las 13:38, Phyllis Smith escribió:
Sergio, Thank you so much for sharing your results which are quite impressive. Am I understanding correctly that the only change you ended up making was the"HWACCEL_FLAGS TO (0X00000002) ?? allow_high_depth" to the h264-nvenc.mp4 ffmpeg option file? I want to add that as a choice for others to see. Probably your newer/higher end graphics board was very beneficial -- a good way to justify upgrading if using h264/h265.
GG/Phyllis
On Sat, Apr 11, 2020 at 7:07 AM <[email protected]> wrote:
Thanks a lot! Well...
pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent
Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG
Sergio
El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me. One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working.
The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want.
A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button".
None of these are easy and you are a brave man to attempt them !! Phyllis
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi Sergio, excuse me for getting me into the conversation. When this happens to you from the black bands you can solve it with the mask tool. I made a tutorial about it, you can see it at: https://multimediagnulinux.wordpress.com/2020/03/27/cinelerra-gg-5-mascaras-... I do not exactly deal with the question you are raising, but I am taking note to make a tutorial on the subject of inserting a video recorded horizontally and removing these black bands with a mask. Regards. El dom., 12 abr. 2020 a las 0:45, <[email protected]> escribió:
It's not a problem to me. I just want to offer a true information, tested... Additionally, and another topic... I was trying a lot of possibiliies to get the best performance possible... One was transcode option to replace media in video. One of them, was a movil (cellphone) video ( 720x1440) , it was transcoded adding black bands to complete 16:9 aspect, 1920x1080.
El 2020-04-11 19:29, Phyllis Smith escribió:
Great, I am in no hurry and also would like to include your statistics in the manual if possible.
On Sat, Apr 11, 2020 at 3:30 PM Sergio Daniel Gomez < [email protected]> wrote:
Phyllis, Yes! just this parameter, but if you want, give me a few day to more test. At this moment.. rendering 4minutes x 30 fps, full-hd, with masks, 11.685fps, rendering same time with constant zoom and chromakey, 9.04 fps. The detail is,before was rendering a 6 fps.
I want to test little more to confirm stability, HW rendering I can confirm now.
Sergio El 11/04/2020 a las 13:38, Phyllis Smith escribió:
Sergio, Thank you so much for sharing your results which are quite impressive. Am I understanding correctly that the only change you ended up making was the"*hwaccel_flags to (0x00000002) ?? *allow_high_depth" to the h264-nvenc.mp4 ffmpeg option file? I want to add that as a choice for others to see. Probably your newer/higher end graphics board was very beneficial -- a good way to justify upgrading if using h264/h265.
GG/Phyllis
On Sat, Apr 11, 2020 at 7:07 AM <[email protected]> wrote:
Thanks a lot! Well...
pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent
Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG
Sergio
El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me.
One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working.
The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want.
A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button".
None of these are easy and you are a brave man to attempt them !! Phyllis
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi Rafa, thanks. This is because the horizontal video well be masking to hide information on a tutorial and in this case well be a mask over a mask and a mask in the difuminated botton video. Maybe a better way is transcode to a yuva video (like you teach me in your las video) if the project have an alfa channel Thanks again El 2020-04-12 03:22, Rafa Mar Multimedia en Gnu\Linux escribió:
Hi Sergio, excuse me for getting me into the conversation. When this happens to you from the black bands you can solve it with the mask tool. I made a tutorial about it, you can see it at: https://multimediagnulinux.wordpress.com/2020/03/27/cinelerra-gg-5-mascaras-... I do not exactly deal with the question you are raising, but I am taking note to make a tutorial on the subject of inserting a video recorded horizontally and removing these black bands with a mask. Regards.
El dom., 12 abr. 2020 a las 0:45, <[email protected]> escribió:
It's not a problem to me. I just want to offer a true information, tested... Additionally, and another topic... I was trying a lot of possibiliies to get the best performance possible... One was transcode option to replace media in video. One of them, was a movil (cellphone) video ( 720x1440) , it was transcoded adding black bands to complete 16:9 aspect, 1920x1080.
El 2020-04-11 19:29, Phyllis Smith escribió:
Great, I am in no hurry and also would like to include your statistics in the manual if possible.
On Sat, Apr 11, 2020 at 3:30 PM Sergio Daniel Gomez <[email protected]> wrote:
Phyllis, Yes! just this parameter, but if you want, give me a few day to more test. At this moment.. rendering 4minutes x 30 fps, full-hd, with masks, 11.685fps, rendering same time with constant zoom and chromakey, 9.04 fps. The detail is,before was rendering a 6 fps.
I want to test little more to confirm stability, HW rendering I can confirm now.
Sergio
El 11/04/2020 a las 13:38, Phyllis Smith escribió:
Sergio, Thank you so much for sharing your results which are quite impressive. Am I understanding correctly that the only change you ended up making was the"HWACCEL_FLAGS TO (0X00000002) ?? allow_high_depth" to the h264-nvenc.mp4 ffmpeg option file? I want to add that as a choice for others to see. Probably your newer/higher end graphics board was very beneficial -- a good way to justify upgrading if using h264/h265.
GG/Phyllis
On Sat, Apr 11, 2020 at 7:07 AM <[email protected]> wrote:
Thanks a lot! Well...
pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent
Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG
Sergio
El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me. One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working.
The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want.
A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button".
None of these are easy and you are a brave man to attempt them !! Phyllis
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi all. Hi Phill. Thanks for waiting. Look... At this time I'm making a lot of tutorials about new laws and decress, all related with covid-19, for help people in Argentina. I have not many time to test, but... Check this: Today I did a special (to me) format video, 1080x2160, 120 seconds, 30 FPS. I always use png with transparency, alpha channel, and masks and blur plugin... So, there are some unsuported formats by HW decoding (cuda or vdpau) Decoder png does not support device type cuda. (using png not supported by HW rendering) Decoder huffyuv does not support device type cuda.(using another not supported by HW rendering) In this case, a mixed CPU-GPU sistem is used, GPU for supported formats, CPU for the rest, and need hwupload_cuda as a filter, somthing like "vf=hwupload_cuda" in video config preset box, but my CPU is too small to proccess all needed and allways is 100% (I'm working on it) and GPU just a little Render::render_single: Session finished. ** rendered 3623 frames in 982.980 secs, 3.686 fps Without tracks with png files: I add hwaccell in the video config preset box and this is the result (in this case a lot of CPU is used too) Render::render_single: Session finished. ** rendered 3623 frames in 698.243 secs, 5.189 fps Conclusion: I need a new CPU. Sorry. HW encoding works and is possible to take adventage of that in CinGG Thanks for all. I'll do more test, but maybe the information is usefull to another people Sergio El 2020-04-11 19:29, Phyllis Smith escribió:
Great, I am in no hurry and also would like to include your statistics in the manual if possible.
On Sat, Apr 11, 2020 at 3:30 PM Sergio Daniel Gomez <[email protected]> wrote:
Phyllis, Yes! just this parameter, but if you want, give me a few day to more test. At this moment.. rendering 4minutes x 30 fps, full-hd, with masks, 11.685fps, rendering same time with constant zoom and chromakey, 9.04 fps. The detail is,before was rendering a 6 fps.
I want to test little more to confirm stability, HW rendering I can confirm now.
Sergio
El 11/04/2020 a las 13:38, Phyllis Smith escribió:
Sergio, Thank you so much for sharing your results which are quite impressive. Am I understanding correctly that the only change you ended up making was the"HWACCEL_FLAGS TO (0X00000002) ?? allow_high_depth" to the h264-nvenc.mp4 ffmpeg option file? I want to add that as a choice for others to see. Probably your newer/higher end graphics board was very beneficial -- a good way to justify upgrading if using h264/h265.
GG/Phyllis
On Sat, Apr 11, 2020 at 7:07 AM <[email protected]> wrote:
Thanks a lot! Well...
pipe option isn't better in this case (I did some test). Changing parameters to pass in the "view" button, ffmpeg option, not codec, is better. Attached images show some information to think it's using HW Acceleration. It's using 2 of 6 cores when before used all cores to reender. And use dedicate memory of graphic card and more GPU and video engine. Render time reduce about 25% and that's excelent
Oh! The more important topic ! Manual is amazing. I'm trying to translate to spanish (slowly) to read the whole book and colaborate with CinGG
Sergio
El 2020-04-10 15:13, Phyllis Smith escribió:
Sorry, I (Phyllis) did not quite understand the question and it was late at night so my brain was tired.
My original question was: Can I pass some imput parameters to ffmpeg in render process? And I ask this again. Why? Becase ffmpeg -hwaccel cuvid can enconder x264 at 13,7x and without this parameter, just 2.5x. And at the moment, x264 is sufficient for me. One way to get parameters passed to ffmpeg while rendering is using the "Piping Video to a Command Line" (this was adapted from CV) and is documented in Rendering chapter 6 of the manual (6.5.6 section). I have not re-tested that in awhile but there is no reason that it should not be working.
The second way which might only work for certain parameters, is to click on the Video wrench in the Render Menu and try to see if the parameter you want to pass is available in either the "view" button which brings up another menu and on the top right hand side is the button "Kind" which defaults to "codec" but can be set to "ffmpeg". And/Or click on the "format" button which provides additional parameters -- these only sort of work and probably not what you want.
A third way is just to write a Shell Command and use that via the "shell cmds" button in the upper right hand corner of the timeline by the "Ffmpeg use first/last button".
None of these are easy and you are a brave man to attempt them !! Phyllis
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
participants (5)
-
Andrea paz -
Phyllis Smith -
Rafa Mar Multimedia en Gnu\Linux -
Sergio Daniel Gomez -
sergiogomez＠tostado.com.ar