- Cin - Cinelerra-GG Mailing Lists

profile vs vprofile in 7.1?
by Andrew Randrianasulu 25 Oct '24

25 Oct '24

We tried to update cinelerra-gg to ffmpeg 7.1 and ran into two problems: First, vf_scale now declares dynamic input and was filtered out by code in cinelerra/pluginfclient.C int flag_mask = AVFILTER_FLAG_DYNAMIC_INPUTS | AVFILTER_FLAG_DYNAMIC_OUTPUTS; if( filter->flags & flag_mask ) return AVERROR(EPERM); ok, it was easy to workaround just by commenting this line out But then it turned out our vaapi/qsv profiles stopped working, anytime there was "profile=high" line. Oh, dang. Looked around and found this thread on Narkive https://ffmpeg-user.ffmpeg.narkive.com/FRd15m7B/ffmpeg-1-0-null-0xcb4700-ev… replaced "profile" with "vprofile", now it appear to work again. But this was a bit unexpected, I do not think both changes were mentioned as breaking in release notes? It sort of sad to see this "hidden" breakage every release. Ffmpeg is not only library that does so, and tracking them all is not fun anymore. If you can't avoid making breakage - put it up front in release notes, not hide it like in bad commercial advertisement. our source: git://git.cinelerra-gg.org/goodguy/cinelerra.git you can build ffmpeg 7.1 into /usr/local and then ./auto gen.sh + configure --without-thirdparty --with-single-user --without-libdpx + make + make install. if it does not work on your system - look around in blds directory for various scripts adding --disable-component switches to configure. binaries and profiles will be in $cin_src_root/bin

2 1

No audio when playing videos
by Bulhwi Cha 24 Oct '24

24 Oct '24

It's been two months since I ran Cinelerra-GG. I downloaded its newest version yesterday. At the moment, I can play and preview my video in the Compositor or Viewer window. However, I can't hear the audio. I tried and failed to build Cinelerra-GG. Here's the information about my desktop computer: chabulhwi(a)desktop.semmalgil.com ------------------------------- OS: Slackware 15.0 x86_64 (post 15.0 -current) x86_64 Host: Micro-Star International Co., Ltd. B360M MORTAR (MS-7B23) Kernel: 6.11.4 Uptime: 2 hours, 7 mins Packages: 2319 (pkgtool), 105 (nix-user) Shell: bash 5.2.37 Resolution: 1920x1080, 3840x2160 WM: sway Theme: Breeze [GTK2/3] Icons: breeze-dark [GTK2/3] Terminal: konsole Terminal Font: Victor Mono 16 CPU: Intel i7-9700 (8) @ 4.700GHz GPU: Intel CoffeeLake-S GT2 [UHD Graphics 630] GPU: NVIDIA GeForce GTX 1660 SUPER Memory: 7595MiB / 31959MiB

3 3

OT: cp -r vs cp -R recursive copy as backup
by Terje J. Hanssen 23 Oct '24

23 Oct '24

From my past Unix & alike experience with Cromix/SVR5/BSD and SunOS/Solaris, I seem to remember faintly that there was a difference between "cp -r" and "cp -R". Both copied recursively directories and files, while -R (possibly) also followed symlinks and copied their targets. On SUSE Linux (which first version 1993 is told to orginate from the most Unix like Slackware), the man pages for cp just say -R, -r, --recursive copy directories recursively A previous thread on Stack Exchange, "Difference between cp -r and cp -R (copy command)", mentions additionally POSIX defined and implementation dependency. https://unix.stackexchange.com/questions/18712/difference-between-cp-r-and-… So I am used with "cp -R" for complete directory backup purpose; else I use more effective "rsync" incremental backups to portable (USB) disks. . What do you use and think here about this?

2 1

Build Cingg-with-system-FFmpeg won't startup after upgrade to ffmpeg-7-7.1
by Terje J. Hanssen 23 Oct '24

23 Oct '24

Continued from another thread: Re: [Cin] another set of test profiles Den 18.10.2024 02:08, skrev Andrew Randrianasulu: > чт, 17 окт. 2024 г., 15:06 Terje J. Hanssen <terjejhanssen(a)gmail.com>: >> If we get available a packaged Cingg test build (rpm/Leap for me), it >> would be more useful to do this test. Then I have available three >> gen. Intel, legacy Skylake/Kabylake iGPUs and current DG2/Arc GPU. I >> also have/had a Nvidia GPU on Skylake, but it looks like it past away. > I think you can build rpm yourself, but for this we need to update > spec file, so it will point at new source and add openvpl as requirements. > > In meantime you can just make your own appimage from just build > cingg-with-system-ffmpeg, so it hopefully will not be lost after few > system updates. > Well, first: After my ffmpeg upgrade from v. 7.0.2 to the awaited v. 7.1 on Slowroll yesterday, my "just build " cingg-with-system-ffmpeg won't startup. Apparently Cingg also has to be rebuilt or upgraded to the new ffmpeg 7.1 family version, as it claims at startup attempt: /home/cinelerra/cinelerra-5.1 # # bin/cin bin/cin: /lib64/libswscale.so.8: version `LIBSWSCALE_8.1_SUSE' not found (required by bin/cin) bin/cin: /lib64/libswresample.so.5: version `LIBSWRESAMPLE_5.1_SUSE' not found (required by bin/cin) bin/cin: /lib64/libavfilter.so.10: version `LIBAVFILTER_10.1_SUSE' not found (required by bin/cin) bin/cin: /lib64/libavcodec.so.61: version `LIBAVCODEC_61.3_SUSE' not found (required by bin/cin) bin/cin: /lib64/libavformat.so.61: version `LIBAVFORMAT_61.1_SUSE' not found (required by bin/cin) bin/cin: /lib64/libavutil.so.59: version `LIBAVUTIL_59.8_SUSE' not found (required by bin/cin) Verify the installed packages that now provide the missing lib files # zypper se -f /lib64/libswscale.so.8 /lib64/libswresample.so.5 /lib64/libavfilter.so.10 /lib64/libavcodec.so.61 /lib64/libavformat.so.61 /lib64/libavutil.so.59 Loading repository data... Reading installed packages... S | Name | Summary | Type ---+----------------+--------------------------------------------------------------+-------- i+ | libavcodec61 | FFmpeg codec library | package i | libavfilter10 | FFmpeg audio and video filtering library | package i+ | libavformat61 | FFmpeg's stream format library | package i+ | libavutil59 | FFmpeg's utility library | package i+ | libswresample5 | FFmpeg software resampling library | package i | libswscale8 | FFmpeg image scaling and colorspace/pixel conversion library | package and to verify the new versions: # zypper se -is libavcodec61 libavfilter10 libavformat61 libavutil59 libswresample5 libswscale8 Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+----------------------+---------+-----------------+--------+----------- i+ | libavcodec61 | package | 7.1-1699.6.pm.1 | x86_64 | Packman i | libavcodec61-32bit | package | 7.1-1699.6.pm.1 | x86_64 | Packman i | libavfilter10 | package | 7.1-1699.6.pm.1 | x86_64 | Packman i+ | libavformat61 | package | 7.1-1699.6.pm.1 | x86_64 | Packman i+ | libavutil59 | package | 7.1-1699.6.pm.1 | x86_64 | Packman i | libavutil59-32bit | package | 7.1-1699.6.pm.1 | x86_64 | Packman i+ | libswresample5 | package | 7.1-1699.6.pm.1 | x86_64 | Packman i | libswresample5-32bit | package | 7.1-1699.6.pm.1 | x86_64 | Packman i | libswscale8 | package | 7.1-1699.6.pm.1 | x86_64 | Packman My question is which steps (back) to rebuild Cingg for the new ffmpeg 7.1 ?

3 18

0000541 probably done already?
by Andrew Randrianasulu 23 Oct '24

23 Oct '24

"Make "Show Viewer/Compositor/Resources" a toggle under Window pulldown" https://www.cinelerra-gg.org/bugtracker/view.php?id=541

2 1

Docker
by Andrew Randrianasulu 19 Oct '24

19 Oct '24

I found this page https://hub.docker.com/r/multiarch/qemu-user-static/ https://stackoverflow.com/questions/72444103/what-does-running-the-multiarc… seems to work after I 1) installed Docker itself (needs Go language from Google .. quite a beast! filled 1Gb for its own incremental rebuilds) 2) installed docker-cli from Slackbuilds 3) ran /etc/rc.d/rc docker start (different command on systemd distros) 4) ran mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc (may be already done by your startup scripts) 5) ran docker run --rm --privileged multiarch/qemu-user-static --reset -p yes -c yes 6) ran test line root@slax:~/src/appimagetool# docker run --rm -t --privileged arm64v8/ubuntu uname -m WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/386) and no specific platform was requested aarch64 root@slax:~/src/appimagetool# for some reason it was not working as root without "privileged"! But hopefully now I can.download few more linuxes for exotic arches and look what their objcopy output looks like! So, hopefully more arches in our strange image-embedding code soon ;) Appimagetool build also worked after I added "privileged" to its script! env ARCH=x86_64 ci/build-in-docker.sh file appimagetool-x86_64.AppImage* appimagetool-x86_64.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=9d7e67802fffc45391e9a993c33120227d1b7c78, stripped so,I am happy Slacker!

1 0

AppImage's new runtime
by Andrew Randrianasulu 19 Oct '24

19 Oct '24

https://github.com/AppImage/type2-runtime/issues/77 I think I fixed it, now it builds inside Alpine chroot and correctly copied out before chroot deleted (debuggin this was ... slow) I see it uses libfuse3 so hopefully there will be no need for libfuse2 workaround on new Debian 11, etc. But I have not tried to use this runtime part anywhere yet. Build takes around 400 mb in /tmp

1 1

Building AppImage as backup
by Andrew Randrianasulu 19 Oct '24

19 Oct '24

So, I was reading https://cinelerra-gg.org/download/CinelerraGG_Manual/Build_CinGG_AppImage_f… I already had pre-build static/opevpl cingg in /dev/shm/new-git/cinelerra/cinelerra-5.1 so I cd there cd tools wget https://github.com/AppImage/AppImageKit/releases/download/continuous/appima… (note, for x86_64 name will be different!) chmod +x appimagetool-i686.AppImage cd ../ guest@slax:/dev/shm/new-git/cinelerra/cinelerra-5.1$ setarch i686 ./bld_appimage.sh on x86_64 you obviously can skip setarch part it was a bit scary because it re-run configure with its own parameters, but at the end it just sailed past build phase and packaged resultin binaries in cinelerra-5.1/bin as cin-i386.AppImage so, in general procedure works, I think, just make sure you have makesquashfs installed ?

2 1

Re: [Cin] CinGG libraries updates
by Phyllis Smith 18 Oct '24

18 Oct '24

Yes! patching thirdparty/Makefile as shown immediately below, now builds. But I have no concept as to how you figured this out and why it works? On Wed, Oct 16, 2024 at 6:43 PM Andrew Randrianasulu < randrianasulu(a)gmail.com> wrote: > > > чт, 17 окт. 2024 г., 03:32 Phyllis Smith <phylsmith2017(a)gmail.com>: > >> Tested 3.0.4 - attached log with same error. >> > > thanks .. > > > can you check if patching thirdparty/Makefile like this > > diff --git a/cinelerra-5.1/thirdparty/Makefile > b/cinelerra-5.1/thirdparty/Makefile > index bb987b0a..04f7c2f4 100644 > > --- a/cinelerra-5.1/thirdparty/Makefile > > +++ b/cinelerra-5.1/thirdparty/Makefile > > @@ -265,9 +265,12 @@ openexr.mak_vars?=true; \# > > opus.cfg_params?= --disable-extra-programs > speech_tools.mak_params?=-j1 > > tiff.ldflags?="$(call ld_path,libjpeg,build)" > > -tiff.cflags?="$(call lnc_path,libjpeg)" > > +tiff.cflags?="$(call inc_path,libjpeg)" > > tiff.cfg_vars+=LIBS+=" -lpthread"; autoreconf -ifv -I m4 && automake -caf; > > i.e. change Inc_path (capital I) to inc_path (small i) > > improves buildability ? > > > >> On Wed, Oct 16, 2024 at 6:18 PM Andrew Randrianasulu < >> randrianasulu(a)gmail.com> wrote: >> >>> >>> >>> чт, 17 окт. 2024 г., 02:30 Andrew Randrianasulu <randrianasulu(a)gmail.com >>> >: >>> >>>> >>>> >>>> чт, 17 окт. 2024 г., 02:18 Phyllis Smith <phylsmith2017(a)gmail.com>: >>>> >>>>> Attached is the log from the build with libjpeg-turbo version 3.0.3 >>>>> BUT 3.0.1 had the same error. I have not tried 3.0.4 but will do so later >>>>> today yet (hopefully). >>>>> >>>> >>>> there also new libtiff 4.7.0, at >>>> >>>> http://www.simplesystems.org/libtiff/releases/v4.7.0.html >>>> >>>> but may be we just build against different libjpeg-turbo includes ? >>>> Need to check .... >>>> >>> >>> hm, may be it does not pick includes from correct place... >>> >>> can you also post config.log from thirdparty/tiff directory after build >>> fails? >>> >>> >>>> >>>> >>>>> On Wed, Oct 16, 2024 at 4:47 PM Andrew Randrianasulu < >>>>> randrianasulu(a)gmail.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> ср, 16 окт. 2024 г., 22:47 Phyllis Smith via Cin < >>>>>> cin(a)lists.cinelerra-gg.org>: >>>>>> >>>>>>> Library updates checked into GIT: >>>>>>> libvpx from 1.13.1 to 1.14.1 >>>>>>> libwebp from 1.3.2 to 1.4.0 >>>>>>> >>>>>>> That completes the library updates for a while except for >>>>>>> libjpeg-turbo which is currently at 2.1.5.1 and could be updated to 3.0.3 >>>>>>> but does not build. Maybe when Andrew has time he can look at this -- I >>>>>>> think the error is due to WITH_12BIT, but I do not know for sure or how to >>>>>>> fix that. >>>>>>> >>>>>> >>>>>> I tried with 3.0.4 and it builds for me on Termux (now with clang >>>>>> 19.1.2) BUT I see failure in mjpegtools/y4mdenoise, I do not think we need >>>>>> program itself so I disabled it (see attached patch). >>>>>> >>>>>> Can you post exact error text? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> It seems like the below url thinks it is in CMakeLists.txt. I did >>>>>>> compare it to the current version but there are a lot of differences. URL >>>>>>> is: https://github.com/libjpeg-turbo/libjpeg-turbo/issues/466 >>>>>>> >>>>>>> -- >>>>>>> Cin mailing list >>>>>>> Cin(a)lists.cinelerra-gg.org >>>>>>> https://lists.cinelerra-gg.org/mailman/listinfo/cin >>>>>>> >>>>>>

2 2

CinGG libraries updates
by Phyllis Smith 16 Oct '24

16 Oct '24

Library updates checked into GIT: libvpx from 1.13.1 to 1.14.1 libwebp from 1.3.2 to 1.4.0 That completes the library updates for a while except for libjpeg-turbo which is currently at 2.1.5.1 and could be updated to 3.0.3 but does not build. Maybe when Andrew has time he can look at this -- I think the error is due to WITH_12BIT, but I do not know for sure or how to fix that. It seems like the below url thinks it is in CMakeLists.txt. I did compare it to the current version but there are a lot of differences. URL is: https://github.com/libjpeg-turbo/libjpeg-turbo/issues/466

2 1