August 2024 - Cin - Cinelerra-GG Mailing Lists

FranceBB's LUT collection
by Andrew Randrianasulu 16 May '25

16 May '25

forum https://forum.doom9.org/showthread.php?t=176091 it says those LUTs should be usable for ffmpeg's lut3d and therefore for CinGG? github (each *.cube can be several mb's big) https://github.com/FranceBB/LinearTransformation author says they were verified on professional equipment... list includes PAL and NTSC variants for rec. 601....

3 6

I tried to add AVC-Intra 100 output profiles
by Andrew Randrianasulu 08 May '25

08 May '25

But not sure if I did this correctly. https://en.wikipedia.org/wiki/AVC-Intra says for AVC-Intra 100: AVC-Intra 100: nominally 100 Mbit/s, size of each frame is fixed CAVLC entropy coding only. All formats are High 4:2:2 Intra Profile, Level 4.1 4:2:2 chrominance sampling frames are not scaled and yeah, this French-language pdf actually says the same: https://web.archive.org/web/20110720215759/http://www.ficam.fr/upload/docum… 50M 100M Standard MPEG-4 part10 AVC/H.264 Profile High 10 Intra High 4:2:2 Intra Level Level 3.2/4.0 Level 4.1 Resolution 1440x1080 / 960x720 1920x1080 / 1280x720 Sampling 4:2:0 4:2:2 Bit rate 54Mbps 111Mbps Block size Y: 8x8, C: 4x4 Intra Prediction Y: 9mode, C: 4mode MBAFF Yes De-block filter No Slice/frame 10 Entropy coding CABAC CAVLC so, I looked up ffmpeg cmd line https://trac.ffmpeg.org/ticket/3597 ffmpeg -v info -i /mnt-data/backup4/vol0/export/CUHK\ 2014-1/V017b.mov -vcodec libx264 -intra -pix_fmt yuv422p10le -vb 100M -x264opts avcintra-class=100 -x264opts colorprim=bt709 -x264opts transfer=bt709 -x264opts colormatrix=bt709 -threads 4 -acodec copy V017b-ffmpeg-git-avcintra100.mov Huh, said I and entered those params in opts file, actually in two files (mp4 and mov containers) mov libx264 cin_pix_fmt=yuv422p10le flags -global_header keyint_min=0 x264-params=keyint=0:colorprim=bt709:transfer=bt709:colormatrix=bt709 avcintra-class=100 bufsize=100000000 level=4.1 mp4 libx264 cin_pix_fmt=yuv422p10le flags -global_header keyint_min=0 x264-params=keyint=0:colorprim=bt709:transfer=bt709:colormatrix=bt709 avcintra-class=100 bufsize=100000000 level=4.1 both for progressive content, for interlace you must add some more flags: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-January/035049.html -flags +ildct+ilme -x264opts interlaced=1 Also, there is still lack of (GUI) user notification if file writing failed due to NO SPACE on device :} FFStream::write_packet: write packet failed. file:/dev/shm/avci_new.mp4 err: На устройстве не осталось свободного места FFStream::encode_frame: encode failed. file: /dev/shm/avci_new.mp4 err: На устройстве не осталось свободного места FFStream::flush failed :file:/dev/shm/avci_new.mp4 err: Операция не позволена Render::render_single: Session finished. ** rendered 273 frames in 85.585 secs, 3.190 fps Render::render_single: Session finished. ** rendered 273 frames in 85.485 secs, 3.194 fps Render::render_single: Session finished. ** rendered 273 frames in 82.176 secs, 3.322 fps Profile sort of assumes you set project to some supported resolution, framerate, etc, otherwise libx264 will fail with console error message..... I found some talk about AVC-Ultra, there even was patch for x264, but it was not merged: https://mailman.videolan.org/pipermail/x264-devel/2015-September/011412.html Also, I think sound must be uncompressed, but I'm not sure.

2 5

Multitrack performance issues
by Stefan de Konink 26 Sep '24

26 Sep '24

I think have a significant opportunity to improve the Cinerella performance, under normal editing conditions, by n_videotracks-fold. At this point in time I notice that the CPU usage (decoding) for a section where multiple tracks are stacked, but only the top one is actually on screen (read opacity 100%) could be improved. I observe the following: - for a disabled video effect, the CPU still runs - for stacked video, the CPU still runs for both videos - the effect must be detached and the video below must have play track disabled to prevent the CPU to go from 20% to 150% - this is independent of colourspace (RGB, RGBA, YUV or YUVA) -- Stefan

3 6

SVT-AV1 library upgraded to v2.2.1
by Phyllis Smith 18 Sep '24

18 Sep '24

The SVT-AV1 library was at version 1.8.0 and finally I got it upgraded and checked into GIT. At first I had to figure out what I was doing wrong in upgrading to 2.1.2, but by the time I figured that out, they released a new version on Aug. 24 (2.2.1). Encoding seems to be somewhat faster. Previously on Aug. 16, GIT checkin was for the latest version of dcraw dated 2018, giflib 5.2.2, and flac 1.4.3 which may not have been recent updates but were the latest available -- might as well use the latest even if no significant changes. I am still checking to make sure we have the latest libraries in use for the other ones so do not plan on creating a release on Aug. 31 -- especially since SVT-AV1 version is so new and I only did a cursory test. Hopefully, Terje can check using the SUSE package at: https://github.com/einhander/cin-gg-packages/releases/ when it has been newly built.

4 23

How to access a second Intel iGPU in a workstation with additional discrete Nvidia GPU?
by Terje J. Hanssen 10 Sep '24

10 Sep '24

I am stuck how to configure QSV access to an enabled iGPU onboard an Intel Core i7-6700K (Skylake). This is a legacy, rebuilt workstation with additional, discrete Nvidia GeForce GTX 960 GPU on a MSI-Z170-A Pro mobo. Any idea and code modification below? Details as follows: inxi -CGMSz System: Kernel: 6.10.5-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 46.3.1 Distro: openSUSE Tumbleweed-Slowroll 20240803 Machine: Type: Desktop Mobo: MSI model: Z170-A PRO (MS-7971) v: 1.0 serial: <superuser required> UEFI: American Megatrends v: 1.K0 date: 07/10/2018 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel Device-2: NVIDIA GM206 [GeForce GTX 960] driver: nvidia v: 550.100 Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.1 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz API: OpenGL v: 4.6.0 vendor: nvidia v: 550.100 renderer: NVIDIA GeForce GTX 960/PCIe/SSE2 API: Vulkan v: 1.3.290 drivers: N/A surfaces: xcb,xlib,wayland API: EGL Message: EGL data requires eglinfo. Check --recommends. lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 Display controller: Intel Corporation HD Graphics 530 (rev 06) DeviceName: Onboard IGD Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971 Kernel driver in use: i915 -- 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3201 Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia ===================================================================== Trying to test QSV via FFmpeg benchmark similar like this Vulkan code ffmpeg -init_hw_device "vulkan=vk:0" -hwaccel vulkan -hwaccel_output_format vulkan -i INPUT -f null - -benchmark https://trac.ffmpeg.org/wiki/HWAccelIntro#Vulkan cause an output error which reports: "device type qsv needed". Intel Skylake with HD 530 graphics gen 9, should be capable to decode and encode MPEG-2/H.264/H.265 according to https://trac.ffmpeg.org/wiki/Hardware/QuickSync#HardwareSupport ffmpeg -hide_banner -hwaccel qsv -hwaccel_output_format qsv -i h264_8bit_yuv420p.mp4 -f null - -benchmark [AVHWDeviceContext @ 0x557526873500] Error creating a MFX session: -9. Device creation failed: -1313558101. [vist#0:0/h264 @ 0x55752685c6c0] [dec:h264_qsv @ 0x55752685b300] No device available for decoder: device type qsv needed for codec h264_qsv. [vist#0:0/h264 @ 0x55752685c6c0] [dec:h264_qsv @ 0x55752685b300] Hardware device setup failed for decoder: Unknown error occurred [vost#0:0/wrapped_avframe @ 0x55752685a740] Error initializing a simple filtergraph Error opening output file -. Error opening output files: Unknown error occurred bench: maxrss=67452KiB I have tried to define and add a qsv device according to the last section here https://trac.ffmpeg.org/wiki/Hardware/QuickSync#Transcode |-qsv_device| is an qsv customized option can be used to specify a hardware device and avoid the default device initialization failure when multiple devices usable (eg: an Intel integrated GPU and an AMD/Nvidia discrete graphics card). One example on Linux (more details please see https://trac.ffmpeg.org/ticket/7649 <https://trac.ffmpeg.org/ticket/7649>) ffmpeg -hwaccel qsv -qsv_device /dev/dri/renderD128 -c:v h264_qsv -i input.mp4 -c:v h264_qsv output.mp4 and also had a look at this answer https://stackoverflow.com/questions/44747381/i-cant-use-hw-encoder-of-qsv-b… --------------------------------------------------- Other HWA verification info: vulkaninfo | egrep 'GPU|driver' VK_LUNARG_direct_driver_loading : extension revision 1 GPU id = 0 (Intel(R) HD Graphics 530 (SKL GT2)) GPU id = 1 (NVIDIA GeForce GTX 960) GPU id = 0 (Intel(R) HD Graphics 530 (SKL GT2)) GPU id = 1 (NVIDIA GeForce GTX 960) GPU id : 0 (Intel(R) HD Graphics 530 (SKL GT2)): GPU id : 1 (NVIDIA GeForce GTX 960): GPU id : 0 (Intel(R) HD Graphics 530 (SKL GT2)): GPU id : 1 (NVIDIA GeForce GTX 960): GPU0: driverVersion = 24.1.5 (100667397) deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU driverUUID = cc628f46-3d02-8624-0c8a-e98e0420c4f6 driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA driverName = Intel open-source Mesa driver driverInfo = Mesa 24.1.5 VK_KHR_driver_properties : extension revision 1 GPU1: driverVersion = 550.100.0.0 (2308505600) deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU driverUUID = 63390c76-60ef-5529-a6ac-99167eb42a9c driverID = DRIVER_ID_NVIDIA_PROPRIETARY driverName = NVIDIA driverInfo = 550.100 VK_KHR_driver_properties : extension revision 1 ----------- Verifying VA-API vainfo Trying display: wayland 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_21 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.22 (libva 2.22.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.5 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI ------- Verifying VDPAU vdpauinfo | egrep 'Driver|GPU' Information string: NVIDIA VDPAU Driver Shared Library 550.100 Thu Jun 27 18:11:42 UTC 2024 ===========================================

2 2

The best strategy to render yuv (mpeg, limited range) from yuvj (jpeg, full range)?
by Tarantas 08 Sep '24

08 Sep '24

So, my sources are in yuvj, and my target (youtube) is yuv. I want to find the best strategy to minimize color banding and maximize dynamic range available. My current settings for this are: - JPEG in "preferences"; - RGBA-float in "format" (color correction in YUV leads to a lot of color banding). The problem is: I couldn't render this RGBA-float into YUV. No matter what render settings I use, it renders in full range. Putting color_range=mpeg doesn't help, because it just flags the file to be in limited range, leading to increased contrast of image. So, I'm a little confused. What I am really supposed to do? Using ColorSpace filter is not convenient with filter like histogram, for example.

5 26

offtopic: Quantel boxes
by Andrew Randrianasulu 25 Aug '24

25 Aug '24

Because I monitor mame WIP thread I saw some news about Quantel Paintbox emulation in MAME (0) and then I randomly followed some links to other Quantel systems Like HAL (basically like hardware compositor) http://dexterslab2013.blogspot.com/2018/03/quantel-hal-video-compositing-sy… 99 layers of SD images or video, up to 15 min storage on 20 disk array! https://m.youtube.com/watch?v=4k15hpeGzBA if you have half of hour you can watch this demo from 1997. Biggest thing so far for me? We are free to use old-fashioned optical effects in front of real camera too :) (0) - https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=120292&page…

2 2

h264 vulkan encoding
by Andrea paz 23 Aug '24

23 Aug '24

A patch brings hardware encoding with vulkan into ffmpeg. In the future I will try to make a preset for h264, but if I understand correctly you have to use the ffmpeg from Lynne's repository and then compile it with the --enable-vulkan option. Do you think a simple replacement of our ffmpeg tar.gz with Lynne's tar.gz is enough? https://lynne.ee/vulkan-video-encoding.html

4 18

Stack smashing detected
by Stefan de Konink 16 Aug '24

16 Aug '24

If you are ever hit by "Stack smashing detected". Go to Settings > Performance and set "Use HW Device" to "none". Lets hope that Google indexes the Cinerella mailinglist. -- Stefan

2 1

AV1 yuv422p10le rendering with some output FFStream::seek I/O errors, seek fails
by Terje J. Hanssen 11 Aug '24

11 Aug '24

So far it seems like 10-bit color depth yuv422p10le is only available for AV1 via FFmpeg encoders libaom-av1 and librav1e. That is not yet with the from experience faster libsvtav1, which currently support pixel formats yuv420p and yuv420p10le. My AV1 (video only) test run procedure using CinGG loading a 10-bit input file, resulted in 12% smaller file size than with h265. Visually the AV1 output file seemingly is ok, but there are some CinGG output "FFStream::seek I/O errors, seek fails" I don't know what are !? CinGG (built: Jul 29 2024 01:18:06, rpm on Leap) Render: File Format: FFMPEG | webm Video wrench: Compression: av1.webm (libaom?) | pixels: yuv422p10le Defaults: # this codec codes less than one frame per sec # and so even a few seconds of video can take # a very long time to encode cpu-used 5 row-mt 1 tiles 2x2 strict -2 threads 8 15M av1_yuv422p10le_LP.webm ** rendered 1780 frames in 184.787 secs, 9.633 fps FFMPEG::open_decoder: some stream times estimated: /run/media/terje/Videoklipp/Cineform/av1_yuv422p10le_LP.webm FFMPEG::open_decoder: some stream times estimated: /run/media/terje/Videoklipp/Cineform/av1_yuv422p10le_LP.webm FFStream::seek: /run/media/terje/Videoklipp/Cineform/av1_yuv422p10le_LP.webm retry limit, pos=207 tstmp=8280, err: Input/output error ** seek fail 207, 8280 .....snip FFStream::seek: /run/media/terje/Videoklipp/Cineform/av1_yuv422p10le_LP.webm retry limit, pos=87 tstmp=3480, err: Input/output error ** seek fail 87, 3480 Verificated the output file with FFprobe: ffprobe -hide_banner av1_yuv422p10le_LP.webm Input #0, matroska,webm, from 'av1_yuv422p10le_LP.webm': Metadata: ENCODER : Lavf61.1.100 Duration: 00:01:11.16, start: 0.000000, bitrate: 1709 kb/s Stream #0:0: Video: av1 (libdav1d) (Professional), yuv422p10le(pc, bt709/unknown/unknown), 1920x1080, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 1k tbn Metadata: DURATION : 00:01:11.160000000

3 10