January 2025 - 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

10bit VAAPI encoding test thread
by Andrew Randrianasulu 06 May '25

06 May '25

We branching! I looked at gpu-screen-recorder https://git.dec05eba.com/gpu-screen-recorder/tree/src/encoder/video/vaapi.c it sets AVHWFramesContext *hw_frame_context = (AVHWFramesContext*)frame_context->data; hw_frame_context->width = video_codec_context->width; hw_frame_context->height = video_codec_context->height; hw_frame_context->sw_format = self->params.color_depth == GSR_COLOR_DEPTH_10_BITS ? AV_PIX_FMT_P010LE : AV_PIX_FMT_NV12; hw_frame_context->format = video_codec_context->pix_fmt; hw_frame_context->device_ctx = (AVHWDeviceContext*)self->device_ctx->data; so may be we need to set AV_PIX_FMT_P010LE and not just P010?

2 21

Tested vaapi hwaccel presets
by Terje J. Hanssen 20 Feb '25

20 Feb '25

Attached tested vaapi hwaccel presets as gzip'd tar file av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm

4 25

I tried to make Appimage out of cinHV!
by Andrew Randrianasulu 28 Jan '25

28 Jan '25

https://cloud.mail.ru/public/mX4A/DSuGSMfUZ sha256sum /dev/shm/cinelerraHV-x86_64.AppImage 7621b7e99734717c4c6847de85f8d8e25c0bf9aa7722d7fc3cf4694cadbd8971 /dev/shm/cinelerraHV-x86_64.AppImage using new static appimage runtime ... and ROSA linux 2016 rootfs (gcc 5.5 and other tools of similar vintage ..roughly Ubuntu 16.04 ?) makeappimage need setting CXXFLAGS=-std=gnu++11, and adding liboost_filesystem for boost 1.61, and minor editing in appdir.C (constexpr t lines 33 and 35 to just const) but it seems to work, after I added desktop entry and (as hack) cingg svg icon ... Is anyone brave enough to test it? :) commit a30bb38bcdb6fe1fabdb534611bc2b9123f70514 (origin/master, origin/HEAD) Author: heroineworshiper <broadcast(a)earthling.net> Date: Thu Oct 10 21:56:45 2024 -0700 + some of my patches (can resend separately)

2 3

In theory there might be some help ....
by Andrew Randrianasulu 17 Jan '25

17 Jan '25

https://www.osnews.com/story/141556/offer-volunteer-labor-for-your-open-sou… ==== OSNews Sponsor OS-SCi <https://os-sci.com> is educating the next generation FOSS engineers, and as part of their coursework, they’re looking for worthy open source projects to which they can contribute their time and effort. In addition to the work they provide during their studies, these volunteers will be encouraged to continue to be involved after they finish their courses and proceed into the workforce. If you are involved in an open source project and would like some help, please register here <https://os-sci.com/partner-organisations>. ==== end of quotation ======

2 1

OT: Switcheroo-Control for Multi-GPU switching
by Terje J. Hanssen 11 Jan '25

11 Jan '25

Extracted info from referenced documents: The Switcheroo-Control is a D-Bus service to check the availability of hybrid GPU configurations and integrate with the desktop environment. This tool is the recommended solution to manage GPU switching on systems with multiple GPUs. Users are encouraged to move away from legacy tools like prime, bbswitch, and bumblebee, as they can cause more harm than good on modern systems. switcherooctl integrates well with Wayland and Xorg, is a lightweight userspace utility and its functionality extends across both Intel + NVIDIA and AMD + NVIDIA setups. By using switcherooctl, users can easily select which GPU to use for specific applications and eliminate the need for complex scripts or environment variables. ------------ https://negativo17.org/prime-optimus-laptops-and-multi-gpu-systems/ https://news.opensuse.org/2024/12/09/gpu-switching-game-changing/ For openSUSE on SkyLake with Nvidia dGPU + integrated Intel iGPU I followed this installation and setup guide SDB:NVIDIA Switcheroo Control https://en.opensuse.org/SDB:NVIDIA_Switcheroo_Control After installing the switcheroo-control package, it had to be enabled as a service and then reboot: systemctl enable switcheroo-control.service ------- According to its online help info switcherooctl version 2.6 switcherooctl help list Usage: switcherooctl list List the known GPUs. switcherooctl help launch Usage: switcherooctl launch [COMMAND…] Launch a command on a specific GPU. Options: -g, --gpu=GPU-ID The GPU to launch on The default GPU to launch on will be the first discrete GPU, or the default GPU if there’s only one. Identifiers can be found using the list command. ------------ Example: switcherooctl list Device: 0 Name: Intel® HD Graphics 530 Default: yes Environment: DRI_PRIME=pci-0000_00_02_0 Device: 1 Name: NVIDIA Corporation GM206 [GeForce GTX 960] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only ----------- I have not so far any example command(s) to launch(?)

2 2

QSV render tests 20% faster with RPM vs AppImage
by Terje J. Hanssen 07 Jan '25

07 Jan '25

I did a few hevc and av1 OSV render tests using the latest RPM w/oneVPL on Leap, to compare it with my own AppImage. To get the AppImage from Slowroll to run om Leap, I had to add-install a newer version libFLAC12. The machine is AlderLake w/Arc A750 gpu The OS root drive is on a std SATA disc, while the video files are read/written to a fast M.2 disc. Results: hevc_qsv_8b420.mp4 ** rendered 5972 frames in 19.255 secs, 310.153 fps (RPM) ** rendered 5972 frames in 23.798 secs, 250.945 fps (AppImage) av1_qsv_8b420.mp4 ** rendered 5972 frames in 18.612 secs, 320.868 fps (RPM) ** rendered 5972 frames in 21.470 secs, 278.156 fps (AppImage) In average rendering is ca. 20% faster with the RPM. I did also additional test with the AppImage on Slowroll and got a bit faster rendering, but not so fast as with RPM on Leap.

2 4

Release for 12/2024 + question for Andrey
by Phyllis Smith 07 Jan '25

07 Jan '25

AppImages available for the December 2024 release at: https://cinelerra-gg.org/download/images/ + https://cinelerra-gg.org/download/images/CinGG-20241120-x86_64-IntelHW.AppI… Packages available for the newer operating systems at: https://github.com/einhander/cin-gg-packages/releases/tag/20241229 See latest release notes below the *****. Question for *Andrey*: Would it be possible to easily add --with-onevpl to the configure line in your build script for Leap 15.5 RPM package? It would require the added package of "oneVPL-devel" to be installed on that O/S (that is the package name for Fedora). If you use the same build script on all of your package builds, they would have to have "oneVPL-devel" installed also. I have tested the build on Fedora 40 after installing that package and had no problem. I have none of the new Intel hardware to test but Terje would like to be able to use these new Intel hardware/software features on his computer. It should not impact normal usage (hopefully). ********* GIT for Cinelerra-GG has the following changes from 11/01/2024-12/31/2024 ********* *SVT_AV1* has been upgraded to 2.3.0 from 2.2.1 with no known problems. *Nvidia encode headers* updated from 10.0.26.0 to 12.2.72.0 which corresponds to Video Codec SDK version 12.0.16. The required driver version for Linux is 550.54.14 or newer. You can check to see if your Nvidia graphics board is supported at this website at the time of this release: https::// developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new There may be user impact since the previous required driver for Linux was 445.87. Minor addition to add non-working ffmpeg filters to plugin.opts; these are blacklisted items. *Andrew-R contributions* The build for *NetBSD* 10.0/amd64 is now working with 3 patches applied and checked in. New *Termux* (Android) encoding render formats have been added: h264_mediacodec.mp4, hevc_mediacodec.mp4, and mpeg2_hdv.mpeg. The 2 mediacodec formats will only work on Android (mediacodec is part of the Android low-level multimedia support infrastructure). A mod to mjpegtools disables compilation of y4mdenoise to prevent compiler errors in *clang*. *Terje testing/building and Andrew-R diagnosing contributions* 12 *new render formats* for qsv, which can be used only if you have that particular Intel hardware and software, have been added as developed/tested by Andrew and Terje. (QSV is Intel’s Quick Sync Video for its dedicated video encoding/decoding hardware core.) 12 *new or replaced vaapi hardware encoding *render formats are now available. Run the vainfo program to determine what formats your hardware/software recognizes. There are some patches to ffmpeg.C and ffmpeg.h to support the above. Additions for building with *oneVPL* (Intel’s oneAPI Video Processing Library) is now an option to be enabled if desired - not enabled by default - on the autogen line by adding “--with-onevpl”. Note in reference to the previous paragraph: There should be no impact to standard usage of CinGG but users need to be especially aware of the fact that using a render encoding format that requires specific hardware/software implementation will give an error. In addition, the standard AppImage releases will not provide the availability to use specific hardware features. This is the same as the inability to use vdpau/vaapi from those same appimages since they are created on a computer without the end users specific hardware. An *AppImage* has been graciously created for users who do have the Intel hardware that supports these newly tested/implemented features *of oneVPL, av1, qsv, and vaapi* for download at: https://cinelerra-gg.org/download/images/CinGG-20241120-x86_64-IntelHW.AppI…

5 8

No rendering - error message
by Terje J. Hanssen 06 Jan '25

06 Jan '25

I guess this may be a stupid error I have not encountered before. Suddenly the AppImages don't render and output the following Cinelerra messages: virtual void Render::handle_close_event(int): Create new file at labels checked, but no labels Any idea how to solve it?

2 2