[Cin] How to identify if a running CinGG is the Regular or Multibit version?
Andrew Randrianasulu
randrianasulu at gmail.com
Tue Jul 16 17:23:56 CEST 2024
вт, 16 июл. 2024 г., 17:07 Terje J. Hanssen <terjejhanssen at gmail.com>:
>
>
> Den 16.07.2024 13:19, skrev Andrew Randrianasulu:
>
>
>
> вт, 16 июл. 2024 г., 13:30 Terje J. Hanssen <terjejhanssen at gmail.com>:
>
>>
>>
>> Den 16.07.2024 11:46, skrev Andrew Randrianasulu:
>>
>>
>> вт, 16 июл. 2024 г., 12:34 Terje J. Hanssen <terjejhanssen at gmail.com>:
>>
>>
>>> Does this also mean that it is not possible to make a "smart", common
>>> CinGG version that has multibit capability for all encoding, x264 and x265
>>> included?
>>>
>>
>>
>> this should be current *-multibit version, but as Andrea noticed it might
>> be slower at regular x265 8bit encodes.
>>
>>
>> I wonder why I didn't get the following encoding formats to work
>>>
>>>
>>> 0 av1_svt_yuv420p_cfhd01.webm
>>> 0 av1_vaapi_yuv420p_cfhd01.webm
>>> 0 av1_yuv422p10le_cfhd01.webm
>>>
>>>
>>>
>> There should also be more 10-bit pixel formats available as extracted
>> from my previous post:
>> https://lists.cinelerra-gg.org/pipermail/cin/2024-July/008407.html
>>
>> cfhd: yuv422p10le gbrp12le gbrap12le
>> libx265: yuv420p10le yuv422p10le yuv444p10le gbrp10le yuv420p12le
>> yuv422p12le yuv444p12le gbrp12le gray gray10le gray12le
>> libsvtav1: yuv420p10le
>> av1_qsv: nv12 p010le qsv
>>
>> you tried to set pixel format dropdown menu after choosing preset?
>
>
> Probably I missed that some preset steps (Compression?) on the Render menu.
> I found now 10bit more yuv422p10le for x265 and svt, but still not yet for
> av1_vaapi.
>
>
>> And won't it be possible to enable Intel qsv etc. hwaccel support with
>>> CinGG's "internal ffmpeg", when it is available for my system ffmpeg?
>>>
>>
>>
>> in theory yes, just figure out that switch you need to pass to ffmpeg for
>> that (ffmpeg should print it in its banner ) and add it
>> to FFMPEG_EXTRA_CFG=" --your-switch --your-second-switch" environmental
>> variable set via export command before you run autogen.sh/configure/make
>>
>>
>> I meant pre-build with CinGG.
>>
>
> well, problem is, if we compile cingg for whatever new libs for ffmpeg
> exist - running it on system where such libs are at wrong version may
> result in weird crashes etc? Appimage helps with some of them, but sadly
> not with hw-assisted de/encoding .....
>
> Why you are so reluctant to compiling cingg yourself? You have enough
> cou/memory/hdd space ....
>
>
> Well, actually I had begun to think about it, and might do a second
> attempt later on (winter work), so this was possibly a kick on the way ;)
> https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q1/003834.html
>
> In the meantime, is there differences between a "System Built" and a
> "Single User built" with regards to updated procedures and utilizing the
> system ffmpeg, libs and gpu performance?
>
"single user" means you can (and should) run it from directory 'bin' that
appear in your cinelerra-5.1 directory after successful build.
System (dynamic) build mean you disable thirdparty components (including
ffmpeg) and resulting binary and plugins should be installed system-wide
(for example in /usr/local )
You can make "single user build" with "system components" by adding both
switches:
./configure --with-single-user --without-thirdparty
but system-wide installed ffmpeg should be at compatible version (just in
case you install some either new or too old ffmpeg/libavcodec).
On systems where few ffmpegs installed you may need to figure out where
exactly relevant libav* libs installed, and then add some CFLAGS/LDFLAGS
before compilation. You can look at blds/bsd.bld and bld/netbsd.bld for
some examples.
not sure how suse handles this. you probably can look at ldd
/usr/bin/ffmpeg to see where libs installed. Or query rpm database about
specific packages
https://cinelerra-gg.org/download/CinelerraGG_Manual/How_Build_CINELERRA_GG_from.html
>
> I remember a fun anecdote from my first Unix (the) book, 1982 (translated
> 1985), in the chapter about 'ed' and 'vi'. They referred to inner circle
> Unix programmers who used to say: "Real hackers do it with ed" 😎
>
well, I do not think you can use vi with teletype :) but of course I never
tried ed ....
>
>
> Some 20+ years ago I was distrohopping a bit because nearly every single
> distro was compiling mplayer just slightly wrong. Then I just stopped
> worrying about distro versions and embrace gcc ....
>
> with whole set of deps being that long I think having source copy and poke
> it from time to time is reasonable?
>
> I can't stop whole world from doing this style of development, even if
> personally I dislike being in focal point of breaking changes from all
> sides!
>
>
>> A hwaccel listing from my system ffmpeg:
>>
>> ffmpeg -hide_banner -encoders | grep qsv
>> V..... av1_qsv AV1 (Intel Quick Sync Video acceleration)
>> (codec av1)
>> V..... h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
>> (Intel Quick Sync Video acceleration) (codec h264)
>> V..... hevc_qsv HEVC (Intel Quick Sync Video acceleration)
>> (codec hevc)
>> V..... mjpeg_qsv MJPEG (Intel Quick Sync Video acceleration)
>> (codec mjpeg)
>> V..... mpeg2_qsv MPEG-2 video (Intel Quick Sync Video
>> acceleration) (codec mpeg2video)
>> V..... vp9_qsv VP9 video (Intel Quick Sync Video
>> acceleration) (codec vp9)
>>
>> ffmpeg -hide_banner -encoders | grep amf
>> V....D av1_amf AMD AMF AV1 encoder (codec av1)
>> V....D h264_amf AMD AMF H.264 Encoder (codec h264)
>> V....D hevc_amf AMD AMF HEVC encoder (codec hevc)
>>
>> ffmpeg -hide_banner -encoders | grep nvenc
>> V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1)
>> V....D h264_nvenc NVIDIA NVENC H.264 encoder (codec h264)
>> V....D hevc_nvenc NVIDIA NVENC hevc encoder (codec hevc)
>>
>> And the ffmpeg banner:
>>
>> ffmpeg version 7.0 Copyright (c) 2000-2024 the FFmpeg developers
>> built with gcc 13 (SUSE Linux)
>> configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64
>> --incdir=/usr/include/ffmpeg --extra-cflags='-O2 -Wall -U_FORTIFY_SOURCE
>> -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
>> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type
>> -flto=auto -ffat-lto-objects -g' --optflags='-O2 -Wall -U_FORTIFY_SOURCE
>> -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
>> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type
>> -flto=auto -ffat-lto-objects -g' --disable-htmlpages --enable-pic
>> --disable-stripping --enable-shared --disable-static --enable-gpl
>> --enable-version3 --enable-libsmbclient --disable-openssl --enable-gnutls
>> --enable-ladspa --enable-libshaderc --enable-vulkan --enable-libplacebo
>> --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b
>> --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libdc1394
>> --enable-libdrm --enable-libfontconfig --enable-libfreetype
>> --enable-libfribidi --enable-libgsm --enable-libjack --enable-libjxl
>> --enable-librist --enable-libmp3lame --enable-libmysofa
>> --enable-libopenjpeg --enable-libopenmpt --enable-libopenh264-dlopen
>> --enable-libopus --enable-libpulse --enable-librav1e --enable-librubberband
>> --enable-libsvtav1 --enable-libsoxr --enable-libspeex --enable-libssh
>> --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvidstab
>> --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp
>> --enable-libxml2 --enable-libzimg --enable-libzmq --enable-libzvbi
>> --enable-lto --enable-lv2 --enable-libvpl --enable-vaapi --enable-vdpau
>> --enable-version3 --enable-libfdk-aac-dlopen --enable-nonfree
>> --enable-libopencore-amrnb --enable-libopencore-amrwb
>> --enable-libvo-amrwbenc --enable-libx264 --enable-libx265 --enable-libxvid
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20240716/8920ce53/attachment-0001.htm>
More information about the Cin
mailing list