Big library upgrades checked in -- hoping someone can build as a check
This was a weird month's work for gg. If someone who ordinarily builds themselves has a chance to build, that would be awesome. Then just do some generic stuff. Libraries upgraded are: giflib, libjpeg, twolame, tiff, x264, x265, dav1d, opus, nv-codec-headers, libwebp, openjpeg, and for LV2 – jalv, suil, sratom, lilvsord, and serd Some other stuff that just got checked in: - new option when do a Render with mp4 when you click on Video wrench, there is a new button "format" which provides some more ffmpeg available options (some are available to use and others not depending on whether ffmpeg has a hook up Cin can use). - pulse audio is going to be added to the builds so it should be a choice in Preferences, PlaybackA , but I have not tested that yet on my laptop because it does not show up for me. (We are still testing and will be all day today). - other messages and minor tweaks in like h264/h265_nvenc.mp4 quality changed from medium to high as Andrea suggested. We will try to get a Mint 19.3 static tar built for testing too. Thanks, gg/Phyllis
"preset high" doesn't seem to be a legal parameter (sorry for suggesting it); it always gives me rendering error. Maybe it is better to use the quality parameter instead (qp=24, it should be good). Many rendering options give errors or a video without images comes out. It is a normal thing to have to calibrate every single render according to the parameters we need and they work for us. I'll try to do more tests because it would be good to start with default parameters that always work. Otherwise I didn't see any other problems, but I'm not a good tester. The first time I started CinGG I had problems with resizing the windows, the content remained fixed and the edges cut off the window. But after a reboot the problem never came up again. OpenEDL keeps crashing, but in the Arch forum they told me that it depends on CPU microcode (AMD Ryzen 3700x). As for Cuda, I still can't compile it out. I've seen that --enable-cuda-sdk is deprecated in favor of --enable-cuda-nvcc. But it still doesn't work for me.
Andrea, We finally booted cuda/nvida but will have to upgrade out nvidia drivers before we can find a fix for h264/5_nvenc.mp4. GG changed the Bitrate and that seemed get past the High problem but the driver was outdated. I don't think it is critical but a solution will have to be figured out. Still have not reproduced the OpenEDL crash either and have this on the "to do" list yet. As for Cuda, I still can't compile it out. I've seen that --enable-cuda-sdk is deprecated in favor of --enable-cuda-nvcc. Good find. He tried the --enable-cuda-nvcc in compiling ffmpeg. It gett added in the configure script as something like this (I will have to verify that it is exactly like this): FFMPEG_EXTRA_CFG= "enable-cuda-nvcc enable-nonfree" then the F_scale_cuda and F_yadif_cuda ffmpeg video plugins do show up. But neither worked for us and not sure if it was due to the out of date nvidia driver so more work is needed here. On Fri, Feb 28, 2020 at 12:46 PM Andrea paz <[email protected]> wrote:
"preset high" doesn't seem to be a legal parameter (sorry for suggesting it); it always gives me rendering error. Maybe it is better to use the quality parameter instead (qp=24, it should be good). Many rendering options give errors or a video without images comes out. It is a normal thing to have to calibrate every single render according to the parameters we need and they work for us. I'll try to do more tests because it would be good to start with default parameters that always work. Otherwise I didn't see any other problems, but I'm not a good tester. The first time I started CinGG I had problems with resizing the windows, the content remained fixed and the edges cut off the window. But after a reboot the problem never came up again. OpenEDL keeps crashing, but in the Arch forum they told me that it depends on CPU microcode (AMD Ryzen 3700x). As for Cuda, I still can't compile it out. I've seen that --enable-cuda-sdk is deprecated in favor of --enable-cuda-nvcc. But it still doesn't work for me. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
1- Mandelbrot plugin: thanks, it works well. I put your five points in the manual, see if you like it. I append Plugin.tex and Tips.tex I don't think it's a good idea to waste time on Cuda either; after all, it's only for two secondary plugins. Out of curiosity, I noticed that among the pixel_formats that one can choose in the rendering window, in particular for h264/5-nvenc.mp4 codecs, besides the various 420p, ... there is also a "cuda". What does that mean? How does it work? (it gave me a rendering error!) 2- I don't know the new "Format" parameters of the rendering/Wrench window. Where can I learn more about them? Are they metadata?
Andrea: Thanks for the manual updates - I was secretly hoping you would do this ! I certainly was unaware that "cuda" was a pixel format but when doing "ffmpeg -pix_fmts" it shows up. No idea what it does. When we get back to cuda/driver upgrade, I will have gg try it. That could be fun. The new "Format" button of the Render window as seen under the Video wrench shows "private" options that can be passed to an underlying muxer. When you click on the Format button, you also have to click on the subsequent "view" button that popups to see them and like the view option in the Preset menu, when you highlight one of them, a yellow tooltip shows up in the lower right hand corner with 1 line of information if available. I believe most can be used on the ffmpeg command line if you ran from a window. For example, one of these for mp4 is "moov_size" and that is effective. If you look at section 21.18.1 in http://ffmpeg.org/ffmpeg-all.html these are the ones you will see for mp4. Or for mp3 of that url in section 5.3 as: "For example to write an ID3v2.3 header instead of a default ID3v2.4 to an MP3 file, use the id3v2_version private option of the MP3 muxer" In other words, these muxer/private options are all over the place to try and learn about them. This should be documented in the manual (so I don't have to try to figure it out when I forget!) On Sat, Feb 29, 2020 at 6:49 AM Andrea paz <[email protected]> wrote:
1- Mandelbrot plugin: thanks, it works well. I put your five points in the manual, see if you like it. I append Plugin.tex and Tips.tex I don't think it's a good idea to waste time on Cuda either; after all, it's only for two secondary plugins. Out of curiosity, I noticed that among the pixel_formats that one can choose in the rendering window, in particular for h264/5-nvenc.mp4 codecs, besides the various 420p, ... there is also a "cuda". What does that mean? How does it work? (it gave me a rendering error!)
2- I don't know the new "Format" parameters of the rendering/Wrench window. Where can I learn more about them? Are they metadata? -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Added the section on ffmpeg Private Options in the chapter on rendering. See if it's okay.
Andrea, again thanks for the Rendering.tex update. I checked in those + Tips.tex + Plugins.tex from the other day. Feedback on Cuda. GG upgraded his cuda system today and the nvidia drivers. 1) The "cuda" pixel format does not work because Cinelerra is not that sophisticated; i.e. when using "cuda" pixel format certain things have to be set up and they are not. 2) I removed the 2 ffmpeg plugins, F_scale_cuda and F_yadif_cuda from the manual and in the plugin.opts file. GG tried them again and they do show up as plugins when you enable cuda nvcc and enable nonfree. So you can drag them to the timeline but when you try to actually use them, it reports an error of "not implemented". In plugin.opts, hwupload_cuda and thumbnail_cuda were already commented out as unusable. I think that that was the last of the cuda unknown, but if not please let me know as I want to keep the manual correct. On Sun, Mar 1, 2020 at 2:49 AM Andrea paz <[email protected]> wrote:
Added the section on ffmpeg Private Options in the chapter on rendering. See if it's okay. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Yes, Cuda is a closed chapter. I took the two plugins out of the manual. Wow! You did a great job with Windows.tex; both as text and as images. My compliments! I've added some very small touches to better display the images; see if they are okay with you.
And Tips.tex Il giorno lun 2 mar 2020 alle ore 10:24 Andrea paz <[email protected]> ha scritto:
Yes, Cuda is a closed chapter. I took the two plugins out of the manual. Wow! You did a great job with Windows.tex; both as text and as images. My compliments! I've added some very small touches to better display the images; see if they are okay with you.
В сообщении от Friday 28 February 2020 19:34:22 Phyllis Smith написал(а):
This was a weird month's work for gg. If someone who ordinarily builds themselves has a chance to build, that would be awesome. Then just do some generic stuff. Libraries upgraded are:
giflib, libjpeg, twolame, tiff, x264, x265, dav1d, opus, nv-codec-headers, libwebp, openjpeg,
and for LV2 – jalv, suil, sratom, lilvsord, and serd
Some other stuff that just got checked in:
- new option when do a Render with mp4 when you click on Video wrench, there is a new button "format" which provides some more ffmpeg available options (some are available to use and others not depending on whether ffmpeg has a hook up Cin can use).
- pulse audio is going to be added to the builds so it should be a choice in Preferences, PlaybackA , but I have not tested that yet on my laptop because it does not show up for me. (We are still testing and will be all day today).
- other messages and minor tweaks in like h264/h265_nvenc.mp4 quality changed from medium to high as Andrea suggested.
We will try to get a Mint 19.3 static tar built for testing too. Thanks, gg/Phyllis
Hm, for some reason I can't make video track fade work outside of '1/0' positions. Try to load any video+audio file, and while audio fade should work as usual (nice slopes between keyframes), on video track you can only toggle fade to '1' or '0', very steep Also, clicking on video track for some reason autoselect both video and audio tracks now?? (they all become inverted visually) If I click on empty space *below* tracks in main window - I can select region as usual.
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith