June 2023 - Cin - Cinelerra-GG Mailing Lists

Awesome functions for Arch
by Andrew Randrianasulu 05 Jun '23

05 Jun '23

https://aur.archlinux.org/packages/vapoursynth-plugin-awsmfunc-git literally ... For that? For x265 HDR param calculations, of course! :)

1 2

AdobeRGB and editing
by Stefan de Konink 04 Jun '23

04 Jun '23

Hi, Given that AdobeRGB gives a wider colorrange, and therefore is likely to have the ability to do 'better' conversions. What is the best workflow to edit in Cinelerra in this extended mode? Or is Cinelerra by definition limited to RGB-8bit/RGBA-8bit/YUV-8bit/YUVA-8bit? -- Stefan

4 14

DV to DVD rendering - questions and issues
by Terje J. Hanssen 03 Jun '23

03 Jun '23

Lately I have experimented with PAL DV to DVD rendering, both using ffmpeg/DeVeDE, and now using CinGG mpeg2enc/FFMPEG I hope someone can help to clarify the following questions and debug possible issues regarding DVD Rendering with CinGG: 1. dvd.m2v and dvd.mpg Why are there two video files created, dvd.m2v w/o Audio and dvd.mpg w/Audio, and which one is used for what? tree -sh dvd_20230528-115747 dvd_20230528-115747 ├── [ 16M] dvd.ac3 ├── [3.4K] dvd.jobs ├── [562M] dvd.m2v ├── [588M] dvd.mpg ├── [ 733] dvd.sh ├── [6.5K] dvd.xml └── [4.0K] iso ├── [4.0K] AUDIO_TS └── [4.0K] VIDEO_TS ├── [6.0K] VIDEO_TS.BUP ├── [6.0K] VIDEO_TS.IFO ├── [ 18K] VTS_01_0.BUP ├── [ 18K] VTS_01_0.IFO └── [588M] VTS_01_1.VOB 2. Deinterlacing: The input PAL DV source file is Interlaced, Bottom Field First ffprobe: Stream #0:0: Video: dvvideo, none, 25000 kb/s, SAR 16:15 DAR 0:0, 25 fps, 25 tbr, 25 tbn Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s Unsupported codec with id 24 for input stream 0 mediainfo: Width : 720 pixels Height : 576 pixels Color space : YUV Scan type : Interlaced Scan order : Bottom Field First Why does deinterlacing with dvd default rendering (mpeg2enc) still come out as Interlaced, but Top Field first? ffprobe -hide_banner dvd.m2v Input #0, mpegvideo, from 'dvd.m2v': Duration: N/A, bitrate: N/A Stream #0:0: Video: mpeg2video (Main), yuv420p(tv, bt470bg, top first), 720x576 [SAR 64:45 DAR 16:9], 25 fps, 25 tbr, 1200k tbn Side data: cpb: bitrate max/min/avg: 8000000/0/0 buffer size: 1835008 vbv_delay: N/A ffprobe -hide_banner dvd.mpg [mpeg @ 0x55a756c7af00] start time for stream 0 is not set in estimate_timings_from_pts Input #0, mpeg, from 'dvd.mpg': Duration: 00:09:56.44, start: 0.160000, bitrate: 8305 kb/s Stream #0:0[0x1bf]: Data: dvd_nav_packet Stream #0:1[0x1e0]: Video: mpeg2video (Main), yuv420p(tv, bt470bg, top first), 720x576 [SAR 64:45 DAR 16:9], 25 fps, 25 tbr, 90k tbn Side data: cpb: bitrate max/min/avg: 8000000/0/0 buffer size: 1835008 vbv_delay: N/A Stream #0:2[0x80]: Audio: ac3, 48000 Hz, stereo, fltp, 224 kb/s Unsupported codec with id 98312 for input stream 0 mediainfo dvd.m2v | egrep "Color|pixels|Scan" Width : 720 pixels Height : 576 pixels Color space : YUV Scan type : Interlaced Scan order : Top Field First Color primaries : BT.601 PAL mediainfo dvd.mpg | egrep "Color|pixels|Scan" Width : 720 pixels Height : 576 pixels Color space : YUV Scan type : Interlaced Scan order : Top Field First Color primaries : BT.601 PAL While corresponding deinterlacing with the optional FFMPEG DVD Rendering comes out as Progressive? ffprobe -hide_banner dvd.m2v Input #0, mpegvideo, from 'dvd.m2v': Duration: N/A, bitrate: N/A Stream #0:0: Video: mpeg2video (Main), yuv420p(tv, bt470bg/unknown/unknown, progressive), 720x576 [SAR 64:45 DAR 16:9], 25 fps, 25 tbr, 1200k tbn Side data: cpb: bitrate max/min/avg: 9000000/0/0 buffer size: 1835008 vbv_delay: N/A ffprobe -hide_banner dvd.mpg [mpeg @ 0x561effba3f00] start time for stream 0 is not set in estimate_timings_from_pts Input #0, mpeg, from 'dvd.mpg': Duration: 00:09:56.42, start: 0.160000, bitrate: 8266 kb/s Stream #0:0[0x1bf]: Data: dvd_nav_packet Stream #0:1[0x1e0]: Video: mpeg2video (Main), yuv420p(tv, bt470bg/unknown/unknown, progressive), 720x576 [SAR 64:45 DAR 16:9], 25 fps, 25 tbr, 90k tbn Side data: cpb: bitrate max/min/avg: 9000000/0/0 buffer size: 1835008 vbv_delay: N/A Stream #0:2[0x80]: Audio: ac3, 48000 Hz, stereo, fltp, 224 kb/s mediainfo dvd.m2v | egrep "Color|pixels|Scan" Width : 720 pixels Height : 576 pixels Color space : YUV Scan type : Progressive mediainfo dvd.mpg | egrep "Color|pixels|Scan" Width : 720 pixels Height : 576 pixels Color space : YUV Scan type : Progressive 3. Dvd Interlaced Chroma With reference to the CinGG manual https://cinelerra-gg.org/download/CinelerraGG_Manual/Dvd_Interlaced_Chroma.… /Now you can use the YUV420P DVD Interlace Mode when rendering DV directly to mpeg2 through a yuv4mpeg stream and when using video effects on HDV video./ /With this option enabled, improved chroma results will be obtained from your DV or HDV source. Editing DV or HDV and rendering it back to the same format does not require any special handling. In order to perform colorspace conversions correctly in CINELERRA-GG and avoid Chroma errors for interlaced 4:2:0 video, check the box as follows:/ Settings → Performance → YUV420P DVD Interlace Mode I can't find this option and is it relevant for DVD rendering? 4. Missing FFMPEG output According to the manual: https://cinelerra-gg.org/download/CinelerraGG_Manual/DVD_Bluray_Creation.ht… I/t is also highly recommended to run the CINELERRA-GG startup from a terminal window, instead of the icon, in order to see informative messages of how to actually write the output (at prompt: keyin <install_directory_path/bin/cin). / For the default mpeg2enc DVD rendering there is output like mpeg2enc -v 0 -b 8000 -q 1 -a 3 -F 3 -H -I 1 -M 8 -z t -f 8 -g 15 -G 15 -R 0 -o '/home/terje/Videoklipp/DVD/dvd_mpeg2enc_20230527-184531/dvd.m2v' For the optional FFMEG DVD Rendering it would be nice to also get the actual "ffmpeg code line" as terminal output, both for learning, customizing and debugging. Is that possible ?

4 15

zimg 2.8
by Andrew Randrianasulu 03 Jun '23

03 Jun '23

Builds on gcc 11.2 (with patch) and seems to require only c++11 support as minimum ... https://bugs.gentoo.org/721676 just one liner (adding include) https://github.com/sekrit-twc/zimg/commit/9ae36d7d5f7420eaacd9644451933512f… wget https://github.com/sekrit-twc/zimg/archive/release-2.8.tar.gz not sure if ffmpeg 5.1 still supports this ...

4 32

KODI vs HDR
by Andrew Randrianasulu 03 Jun '23

03 Jun '23

https://forum.kodi.tv/showthread.php?tid=371952&page=2 ==== * <https://forum.kodi.tv/showthread.php?tid=371952&pid=3139871#pid3139871>* 2023-02-12, 07:24 Is our goal to get HDR passthrough to work to an HDR capable display, or to just get HDR videos to display without being washed out? If it's the latter, turn on tone mapping <https://kodi.wiki/view/Video_playback#:~:text=would%20disturb%20AR%29.-,Ton…> in the video settings for the HDR video. Kodi 20 has a few different tone mapping options. Hable is pretty good. If you want HDR passthrough, you'll need to use the GBM backend of Kodi with GLES. The GL backend does not have the code to turn on HDR passthrough, only GLES does. The Xorg and Wayland backends do not support HDR passthrough. Xorg has no HDR support, and Wayland's is in progress and incomplete (I'm not talking about Kodi, I'm talking about in general.) To get the GLES backend for kodi GBM, you'll have to compile it yourself <https://github.com/xbmc/xbmc/blob/Nexus/docs/README.Ubuntu.md> as the PPA version uses the GL backend. You will have to compile it with the -DGBM_RENDER_SYSTEM=gles option. Then you'll have to run Kodi from a regular text tty, and not X11. Switch to a tty with ctrl-alt-F2, log in, and run kodi --windowing=gbm. ==== I looked at Arch package and it uses gl, not gles! Also, bt2020 might be broken. Dolby vision not supported... https://github.com/xbmc/xbmc/pull/21845 merged in late april ...2023. Might not work on amd :( only on intel GPU. https://github.com/xbmc/xbmc/issues/22360 ==== I've noticed that in the current libreelec nightlies that if you start a HDR file with an AMD APU / GPU that it will start playing but not in the correct colourspace. It will play in SDR709. You then have to just return to the Kodi menu while playing and go back to Fullscreen and the output will then be correct at BT2020. I've confirmed this issue on the AMD 5600G and the Radeon 6400 series. This does not occur using my 12th gen Intel NUC. I believe it might have something to do with this. ==== end of quote ====

1 1

Rendering tests
by Andrea paz 02 Jun '23

02 Jun '23

Taking advantage of the fact that I compiled a version that uses system (external) ffmpeg, I did some comparative testing with CinGG appimage which uses an internal ffmpeg instead. I report the results: Source: blender movie "Tears of steel" 1080p, webm (Used an interval of the first 1440 frames via In/Out Points) mp4; preset h264.mp4 ffmpeg internal --> render at 117.4 fps (25.4MB) ffmpeg external --> render at 175.3 fps (22.8MB) mxf; preset DNxHR 444 ffmpeg internal --> render at 92.9 fps (1.8GB) ffmpeg external --> render at 120.5 fps (1.8GB) I had already noticed that ffmpeg from the command line (external) was faster than ffmpeg inside CinGG; but now we see that even external ffmpeg called up inside CinGG is still faster than internal ffmpeg. What could be the cause of this difference?

3 2

Weird world of WINDOW_CONFIG!
by Andrew Randrianasulu 02 Jun '23

02 Jun '23

so, I looked in mainsession.C while hunting about a_x11_host callsites see what I found: void MainSession::default_window_positions(int window_config) { // 0 - all windows on a, playback_config a // 1 - all windows on b, playback_config b // 2 - all windows on a, except composer on b, playback_config b but in reality this config set everything on A (Xephyr screen) A_X11_HOST :1.0 B_X11_HOST :0.0 WINDOW_CONFIG 2 this config set everything BUT compositor on A A_X11_HOST :1.0 B_X11_HOST :0.0 WINDOW_CONFIG 1 this config set only compositor on B: A_X11_HOST :0.0 B_X11_HOST :1.0 WINDOW_CONFIG 1 and this config se ALL on A A_X11_HOST :0.0 B_X11_HOST :1.0 WINDOW_CONFIG 0 so check your Cinelerra_rc for WINDOW_CONFIG value!

3 6

10bit display links
by Andrew Randrianasulu 01 Jun '23

01 Jun '23

https://github.com/CESNET/UltraGrid/discussions/203 10bit display with SDL/GL #203 has this hint (may be not needed on Display port) ==== it is also important to set the display to Full range and set the max bpc ACTIVEDISPLAY=`xrandr | grep " connected " | awk '{ print$1 }'` xrandr --output $ACTIVEDISPLAY --set "Broadcast RGB" "Full" --set "max bpc" 10 https://www.soi.pw/posts/10-bit-color-on-ubuntu-20.04-with-amdgpu-driver/ ==== https://github.com/CESNET/UltraGrid/commit/03b60c9931b1fc83ca91bee09dbe4266… referred pdf says this: https://www.amd.com/system/files/documents/10-bit-video-output.pdf "Figure 5: 10-bit display feature can be enabled by checking the “Enable 10-bit pixel format support” checkbox in the Catalyst Control Center. Note that this feature is only available in workstation (ATI FireGL™) cards. Once the 10-bit pixel format support is enabled the system will request a reboot and after that any 10- bit aware OpenGL application will be displayed in 10-bits without any clamping. In the following, we demonstrate how an application programmer can easily create a 10-bit aware OpenGL [skip] Creating a 10-bit Texture The previous section highlighted several methods to choose a 10-bit pixel format. It is important to note that once a 10-bit pixel format is chosen any smooth shading operation will immediately take advantage of the increased bit depth. In other words, the user does not need to explicitly provide 10-bit input data to benefit from the increased precision. This is due to the fact the internal processing of colors in the graphics card is in floating-point precision with 10-bit (or 8-bit) conversion occurring only at the output stage. However, it is also possible to explicitly create and work with 10-bit textures as will be explained in this section. 10-bit texture support is exposed to the user through a packed RGB10_A2 texture format, which contains 10 bits for each of the color channels and 2 bits for the alpha component. ==== original issues also should contain test images https://github.com/CESNET/UltraGrid/files/7525556/gradients.zip

2 5

Mpv's HDR signalling over drm subsystem
by Andrew Randrianasulu 01 Jun '23

01 Jun '23

https://github.com/mpv-player/mpv/pull/8648 not quite it, not on master branch yet (look for "hdr" branch for recent rebase) but for some Arch users it worked? ==== With the already noted exception that mpv needs to be run once and then ran again before the monitor enters HDR mode, this seems to be working for me with the following options: --no-config --target-trc=pq --target-peak=400 --video-output-levels=full --target-prim=dci-p3 --hdr-compute-peak=yes --gamut-clipping=no --tone-mapping=mobius --vo=gpu --gpu-api=opengl --gpu-context=drm --drm-send-hdr-meta=auto --drm-connector=HDMI-A-0 I'm on an arch based system. linux 5.10. AMDGPU. Connected over HDMI to an Acer XV272U =====

1 0

Mysterybox.us blog archive
by Andrew Randrianasulu 01 Jun '23

01 Jun '23

https://web.archive.org/web/20170822225433/http://www.mysterybox.us/blog/20… ==== As slightly more concerning consideration, however, is the availability of high quality 12+ bit codecs for use in intermediate files. Obviously any codec using 8 bits / channel only are out of the question for HDR masters or intermediates, since 10 bits are required by all HDR standards. 10 bit encoding is completely fine for mastering space, and codecs like ProRes 422, DNxHR HQX/444, 10 bit DPX, or any of the many proprietary ‘uncompressed’ 10 bit formats you’ll find with most NLEs and color correction softwares should all work effectively. However, if you’re considering which codecs to use as intermediates for HDR work, especially if you’re planning on an SDR down-grade from these intermediates, 12 bits per channel as a minimum is important. I don’t want to get sidetracked into the math behind it, but just a straight cross conversion from PQ HDR into SDR loses about ½ bit of precision in data scaling, and another ¼ - ½ bit precision in redistributing the values to the gamma 2.4 curve, leaving a little more 1 bit of precision available for readjusting the contrast curve (these are not uniform values). So, to end up with an error-free 10 bit master (say, for UHD broadcast) you need to encode 12 bits of precision into your HDR intermediate. ProRes 4444 / 4444 (XQ), DNxHR 444, 12 bit DPX, Cineform RGB 12 bit, 16 bit TIFFs, or OpenEXR (Half Precision) are all suitable intermediate codecs,** though it’s important to double check all of your downstream applications to make sure that whichever you pick will work later. Similarly, any of these codecs should be suitable for mastering, with the possibility of creating a cross converted grade from the master later. ==== hm, so even if swscale from rgba32f timeline to libavcodec still buggy we can just use cingg's built-in tiff/exr output, I guess? Strangely for now those blogs are not linked to site? I found link while looking inside HDR.zip provided at doom9 forums https://spaces.hightail.com/space/nEaXy 91 Mb!

1 0