- Cin - Cinelerra-GG Mailing Lists

Testing Cingg RPM built with OneVPL, qsv and vaapi presets
by Terje J. Hanssen 05 Jan '25

05 Jan '25

Installed Andrey's recent cinelerra-5.1-20250104.suse15.x86_64.rpm package on Leap 15.6 on two different Intel based hw, and tested qsv and vaapi presets without issues 1) Intel Arc Alchemist w/ A750 dGPU (2023) av1_qsv_8b420.mp4, qsv_10b420.mp4 hevc_qsv_8b420.mp4, hevc_qsv_10b420.mp4, hevc_qsv_10b422.mp4 av1_vaapi_8b420.mp4, vaapi_10b420.mp4 hevc_vaapi_8b420.mp4, hevc_vaapi_10b420.mp4, hevc_vaapi_10b422.mp4 2) Intel KabyLake w/ UHD 620 iGPU (2017) hevc_qsv_8b420.mp4, hevc_qsv_10b420.mp4 hevc_vaapi_8b420.mp4, hevc_vaapi_10b420.mp4 The last line here is of special interest hevc_vaapi_8b420.mp4, hevc_vaapi_10b420.mp4 because Cingg deb on UB24.04 on this machine didn't render hevc_vaapi. It seems that OneVPL (libvpl) extends the codec capability also for vaapi. This has to be verified by dual-testing once more..

2 4

Issues to prepare a test on UB 24.04
by Terje J. Hanssen 03 Jan '25

03 Jan '25

Well, I admit I have never been a real UB user. But as UB16 initally was fabric installed on my Dell XPS 13-9370 (KBL), I have kept and upgraded UB as part of multiboot with openSUSE Leap and Slowroll on this machine. So I upgraded to the available UB 24.04.1LTS to prepare a new Cingg test on it. Actually my old installed Cinelerra Infinity - built: Jun 30 2020 09:37:43 still startup on UB24.04. 1) I tried first to install the latest cin_5.1.20241009.ubuntu2204_amd64.deb package without success. sudo apt install <package url> didn't work (like corresponding "zypper in" on Leap does) So I downloaded the package and tried sudo apt install cin_5.1.20241009.ubuntu2204_amd64.deb Reading package lists ... Finished Create overview over dependices --- Finished Reading state information ... Finished E: Cannot find the package cin_5.1.20241009.ubuntu2204_amd64.deb What is the issue, when the deb package is in the local directory? 2) So I tried the AppImage ./CinGG-20241120-x86_64-IntelHW.AppImage dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information Before this I had installed FUSE according to the wiki sudo add-apt-repository universe sudo apt install libfuse2t64 I had a look back into the AppImage (Fuse) mail thread, and ask here if a Fix was found that can be used here? Terje

3 6

Testing Nvidia Nvenc encoding
by Terje J. Hanssen 29 Dec '24

29 Dec '24

Continued and extracted from [Cin] Video accelerators support, builds and use https://lists.cinelerra-gg.org/pipermail/cin/2024-December/009226.html Den 12.12.2024 00:54, skrev Terje J. Hanssen: > > Den 11.12.2024 23:56, skrev Andrew Randrianasulu: >> >> чт, 12 дек. 2024 г., 00:43 Terje J. Hanssen via Cin >> <cin(a)lists.cinelerra-gg.org>: >> >> To clarify some pieces once again, I put up some basic statements >> or questions: >> ..........snip >> >> >> So what happened when adding oneVPL (qsv) support to the >> build system; dynamic linked to system or static added >> embedded into the build? >> >> >> dynamic >> >> .....snip >> >> Could in principle similar methods be extended to include >> broader video acceleration support for AMD/amf and NVIDIA/nvenc? >> >> >> nvenc already supported, I think? At some point I tried it with >> GF710 on livedvd and it was working for me. try to test it if you >> have proprietary nvidia drivers. >> Apparently Cingg then should supports NVENC via some dynamic linked external Nvidia lib, equivalent to what we did for for QSV via oneVPL support. While h264_nvenc.mp4 rendering works, h265_nvenc.mp4 fails with the following errors, see detail below: [hevc_nvenc @ 0x7ff79c015640] No capable devices found FFMPEG::open_encoder err: Generic error in an external library > > Yes, seemingly: > Cin/bin/ffmpeg/video> ls *nvenc* > h264_nvenc.mp4 h264_nvenc.qt h265_nvenc.mp4 NVENC Presets cat h264_nvenc.mp4 mp4 h264_nvenc # encode for nvidia graphics hw only preset medium profile main cat h265_nvenc.mp4 mp4 hevc_nvenc # encode for nvidia graphics hw only preset medium profile main > > Maybe I can do an attempt later, if I get life in the old GeForce GTX > 960 in my Skylake workstation. > Setup ---------- Booted BIOS and checked that the integrated Intel gpu and multimonitor setup were enabled. Installed the suse-prime package for nvidia/intel gpu selection (for NVIDIA optimus laptops with bbswitch support) and could then run the command prime-select on-demand and verified that both the Intel and Nvidia drivers were available inxi -G Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel Device-2: NVIDIA GM206 [GeForce GTX 960] driver: nvidia v: 550.135 Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4 compositor: gnome-shell v: 47.2 driver: X: loaded: modesetting,nvidia unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 vendor: intel mesa v: 24.3.1 renderer: Mesa Intel HD Graphics 530 (SKL GT2) API: EGL Message: EGL data requires eglinfo. Check --recommends. ============== Test h264_nvenc.mp4 ------------------- OK ./CinGG-20241120-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:06:05 Loads hdv09_04.m27 Shift-R mp4 h264_nvenc (video preset) pixels: yuv420p (default) ** rendered 5972 frames in 27.391 secs, 218.028 fps ffprobe -hide_banner hdv09_04_h264_nvenc_yuv420p.mp4 Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuvj420p(pc, smpte170m/unknown/unknown), 1440x1080 [SAR 4:3 DAR 16:9], 2156 kb/s, 25 fps, 25 tbr, 12800 tbn (default) ------- Tried also h264_nvenc with pixels: nv12 which for slowed down to 45% speed !? Render::render_single: Session finished. ** rendered 5972 frames in 60.368 secs, 98.927 fps ffprobe -hide_banner hdv09_04_h264_nvenc_nv12.mp4 Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuvj420p(pc, smpte170m/unknown/unknown), 1440x1080 [SAR 4:3 DAR 16:9], 2154 kb/s, 25 fps, 25 tbr, 12800 tbn (default) =================== Test h265_nvenc.mp4 ------------------- Did not render, neither with pixels yuv420p nor nv12: FFMPEG::open_encoder err: Generic error in an external library [hevc_nvenc @ 0x7ff79c015640] No capable devices found FFMPEG::open_encoder err: Generic error in an external library int FFMPEG::open_encoder(const char*, const char*): open failed hevc_nvenc:/run/media/terje/video/hdv09_04_h265_nvenc_yuv420p.mp4 Render::render_single: Session finished. =================== GeForce GTX 960 (GM206) should be capable to manage NVENC h265/hevc YUV 420 encoding https://en.wikipedia.org/wiki/Nvidia_NVENC#Third_generation,_Maxwell_GM20x https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new Tested hevc_nvenc full transcoding with FFmpeg 7.1 ffmpeg -hide_banner -hwaccel cuda -hwaccel_output_format cuda -i hdv09_04.m2t -c:v hevc_nvenc hdv09_04_ff_hevc_nvenc.mp4 frame= 5963 fps=270 q=34.0 Lsize= 64316KiB time=00:03:58.77 bitrate=2206.6kbits/s speed=10.8x [aac @ 0x55a38d4c4d40] Qavg: 488.890 ------------------ ffprobe -hide_banner hdv09_04_ff_hevc_nvenc.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuv420p(tv, bt709, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 2074 kb/s, 24.99 fps, 25 tbr, 12800 tbn (default)

4 32

Testing Appimage with OneVPL and QSV presets on legacy Intel hardware
by Terje J. Hanssen 20 Dec '24

20 Dec '24

After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware. Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_… * The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration, * The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration, 1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A) ~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0 Loaded hdv09_04.m2t (tff interlaced) Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished. 2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel ~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0 Loaded hdv09_04.m2t (tff interlaced) Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished. Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.

3 24

Two patches hopefully fixing build on NetBSD 10.0/amd64
by Andrew Randrianasulu 18 Dec '24

18 Dec '24

Currently from that system I still need to set export LD_LIBRARY_PATH="/usr/pkg/lib/ffmpeg6" and set audio output to oss - > /dev/audio but it seems to work. Can you check them by building on Linux? :)

2 22

Problem with X11-OpenGL
by Andrea paz 17 Dec '24

17 Dec '24

I continue from another post: >> After startup I have the following message: >> >> BC_DisplayInfo::gl_fb_config failed >> >> Do you know what it could be? >> > something between mesa and X server? > I fixed my mesa3d version to 22.1.7 due to breakage on nouveau with my > specific low end card (gt710) so I am not following latest mesa changes ... >> Another problem, if I load one or more media, when I set the >> X11-OpenGL driver, I get the following warning: >> >> void AWindowGUI::update_asset_list(): >> Warning: /home/paz/test/sad_woman.mxf >> dimensions 1920x1080 exceed OpenGL texture limit 0 >> void AWindowGUI::update_asset_list(): >> Warning: /home/paz/test/Unusual_Habitat.wav >> dimensions 0x0 exceed OpenGL texture limit 0 >> void AWindowGUI::update_asset_list(): >> Warning: /home/paz/test/video (2160p)HDR_01.mp4 >> dimensions 3840x2160 exceed OpenGL texture limit 0 >> void AWindowGUI::update_asset_list(): >> Warning: /home/paz/test/vp.webm >> dimensions 512x288 exceed OpenGL texture limit 0 >> Decoder dnxhd does not support device type vaapi. >> HW device init failed, using SW decode. >> file:/home/paz/test/sad_woman.mxf >> err: Operation not permitted >> FFMPEG::open_decoder: some stream times estimated: /home/paz/test/vp.webm >> >> editing on the timeline more or less works, but I often have freezes >> that force me to reboot. >> >> If I use the X11 driver everything works fine and I don't have the freezes. I've tried several tests, but I can't get to the bottom of the problem. On my system I have the following packages involving OpenGL: freeglut 3.6 glu 9.0.3 glslang 14.3 libepoxy 1.5.10 libglvnd 1.7 qt6-shadertools 6.7 and mesa 24.2.3 xf86-video-amdgpu 23.0.0 (for the 2D and opengl) I also have the same errors in Wayland (which, I imagine, uses xwayland) however I have better performance in timeline and no crashes. I too think it is some mesa update or, even more likely, amd drivers. However the problem is not only in the latest CinGG release but also in the previous one and also in a different distro (however always rolling and Arch based).

2 15

tried to add ubuntu24 specifically to bld_prepare.sh
by Andrew Randrianasulu 16 Dec '24

16 Dec '24

I have Ubuntu Studio 24.04.x on slow usb drive. I tried to get cingg sources there and compile her. It seems few packages changed their name (fftw3) or disappeared (python2) so I edited new case for our bld_prepare.sh script. git am patch attached, but it will be nice if anyone tested that on another ubuntu 24.04.x system

3 5

Multicam video output?
by Stefan de Konink 16 Dec '24

16 Dec '24

Given all the performane issues involved with multi track editing in Cinelerra, where every track is effectively rendered anyway. Is there any existing option to get a video track output into a separate viewer / compositor? Read: give me a window that only shows what is on this track. I am aware that <https://cinelerra-gg.org/download/CinelerraGG_Manual/Multi_Camera_Mixer.html> exists, but I am actually looking for just 'the track output' and not resource based interaction involved with mixers. Furthermore it might be a nice addition to get the multiview mode that OBS has to direct the program or multiview to a separate screen. -- Stefan

4 3

Some ideas how to speed up cingg
by Andrew Randrianasulu 16 Dec '24

16 Dec '24

Well, I only tested 1) 1) add fast lowres=3 skiploopfilter=all to your decode.opts file lowres really only work for dv/mpe2/mjpeg. 3 is really aggressive, try 1 or 2 if it works at all. 2) Set scaling method to simplest, nearest. Obviously only work if you do not do scaling, or plan to redo it anyway at higher quality. 3) Look if replacing -Ofast with " -mach=yourcpu, -mtune=yourcpu" works better (grep Makefiles to see where it set) 4) Add same march/mtune cflags to individual plugins Makefiles and see if it really speed ups them. 5) Hard - look into openmp parallel/simd directives and see if they apply to any for loops in slow plugins. 6) As I said - proxies ... It seems that in worst case scenario (g=250 frames, fps=25) for fast (less than 1 second) seeking to any point in stream you need nearly 10x more power that was needed for mere playback! It goes better for smaller g and bigger fps, but still. H265/4/2 was not designed as editing format, and you only can brute force your way so far .... 7) Look if mesa3d tracker has any issue with vaapi decoding crashing cingg. I added one case but it probably was just incomplete implementation in nouveau. I avoided some crashes by disabling those filmstrip icons as fast as I can after loading media. ymmv. I suspect way cingg drives ffmpeg and ffmpeg in turn drives vaapi driver is quite different from usual player/streaming case, but you probably need some thread debugging flags added everywhere and knowledge about how to interpret their output.

1 0

Mesa 24.3 and Vulkan
by Terje J. Hanssen 14 Dec '24

14 Dec '24

In August this year we had a thread "h264 vulkan encoding" initiated by Andrea https://lists.cinelerra-gg.org/pipermail/cin/2024-August/008517.html Mesa 24.3 is released with many Vulkan Driver Improvement, and implementations are expected around the corner in rolling distributions. Some articles about this in Phoronix https://www.phoronix.com/news/Mesa-24.3-Released https://www.phoronix.com/news/Mesa-24.3-rc2 https://www.phoronix.com/news/Mesa-24.3-rc1-Released https://www.phoronix.com/news/Intel-Vulkan-Video-H264-H265 With ffmpeg (7.1) h264/5 vulkan encoder support, I wonder if Cingg is ready to put them into use? ffmpeg -hide_banner -encoders | grep vulkan V....D h264_vulkan H.264/AVC (Vulkan) (codec h264) V....D hevc_vulkan H.265/HEVC (Vulkan) (codec hevc)

3 10