- Cin - Cinelerra-GG Mailing Lists

Upd: SVG source files in themes
by Andrew Randrianasulu 04 Apr '20

04 Apr '20

Actually I used this command in svg source dir in theme: gzip -9 -S z *.svg (compresses and gives suffix z to any svg file in current dir) and resulted files correctly show up in inkscape (0.92.4) Now all themes weight 14891K on disk and still editable without additional effort ---------- Пересланное сообщение ---------- Тема: SVG source files in themes Дата: Суббота 04 апреля 2020 Отправитель: Andrew Randrianasulu <randrianasulu(a)gmail.com> Получатель: "Cinelerra.GG" <cin(a)lists.cinelerra-gg.org> They not eat space if you install binary package, but I found out you can easily compress them with gzip :} So, whole themes subfolder will weight on disk (after git unpacked it) 16545K as opposed 67,968,745 bytes right now. Not sure if space-saving for unpacked git tree actually worth additional effort to unpack them if anyone want to make changes In theory there is supportfor SVG compression, but not sure if Inkscape and co actually support it well (never tried)? https://www.moxio.com/blog/6/serving-compressed-svg-files -- The SVG standard reserves the .svgz-extension for gzip-compressed SVG files, which can typically achieve about 20-50% of the original file size. When not actively editing them, saving SVG files as svgz makes sense: it saves disk space, the compression is lossless and it spares the time needed for on-the-fly compression when serving them over the web. -- hm .... This inspired by latest git commit, adding jpeg-compressed shapes :} I also tried optipng on existing shapes, but result was slightly more than 1Mb of savings: 8412866 bytes optimized vs 9786K by default -------------------------------------------------------

1 0

Some suggestions and questions about rpm packaging
by Andrew Randrianasulu 03 Apr '20

03 Apr '20

Sorry, I was unclear when I posted link to Rosa's rootfs, I used specifically this archive, and untarred it in pre-created subdirectory: rootfs-std-rosa2016.1_x86_64_2020-04-02.tar.xz http://file-store.rosalinux.ru/api/v1/file_stores/3f1cb1e4069d183ade5379c0d… I actually copied it to btrfs-formatted file in tmpfs, mounted with compression option (-ocompress) From there I mount -obind /dev, /sys, /proc/ /dev/pts from host system into chroot and chroot'ed there. "urpmi package" will install package. You can add many of them as args. rpmbuild may complain initially about not created directory, so create it manually. At the end of binary package creation I saw: cinelerra.x86_64: W: no-documentation cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/de/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/el/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/es/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/eu/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/fr/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/hi/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/it/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/ja/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/ko/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/nb/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/pt/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/ru/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/sl/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/uk/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/vi/LC_MESSAGES/cin.mo cinelerra.x86_64: W: file-not-in-%lang /usr/share/locale/zh/LC_MESSAGES/cin.mo cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_hulk.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_bright.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_blond_cv.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_cakewalk.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_suv.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_blue.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_neophyte.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_blue_dot.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_pinklady.plugin cinelerra.x86_64: W: executable-stack /usr/bin/cin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_unflat.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/themes/theme_blond.plugin cinelerra.x86_64: W: executable-stack /usr/lib64/cin/plugins/video/chromakeyhsv.plugin 2 packages and 0 specfiles checked; 0 errors, 30 warnings. Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.90675 + umask 022 + cd /root/rpmbuild/BUILD + cd cinelerra-5.1 + /bin/rm -rf /root/rpmbuild/BUILDROOT/cinelerra-5.1-20200331-rosa2016.1.x86_64-buildroot It seems at least file-not-in-%lang can be easily cured: https://en.opensuse.org/openSUSE:Packaging_checks file-not-in-%lang W: file-not-in-%lang /usr/share/sarg/sarg-php/locale/en_EN/LC_MESSAGES/messages.mo A gettext translation file (those ending in .mo) is not properly tagged by language. This information might be useful in the future to be able to leave out certain languages during installation. The %find_lang macro can be used to automatically tag files. https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#.25find_l… %find_lang This macro helps to mark locale-dependent files with the respective %lang tag in the file list. Synopsis %find_lang name [filelist] The %find_lang macro searches the directories /usr/share/locale and locale/*/LC_MESSAGES for name.mo files. It also searches gnome/help/name and kde*/share/doc/HTML/*/name directories for a localized documentation. Then it creates the file filelist where the files are marked with the respective %lang(locale) and %doc tags. Such a file list can be then passed to the %files tag via the -f option. See below for an example. It is recommended to use this macro only if the BuildRoot tag is defined as otherwise the entire system will be searched. %find_lang should be used in %install section. Example usage %install # installation %find_lang %{name} %files -f %{name}.lang --- But I haven't tried this trick for .spec file yet .... For executable-stack there is solution given at first link, too: Solutions: A comprehensive article about this problem can be found at http://www.gentoo.org/proj/en/hardened/gnu-stack.xml Probably the easiest solution is to pass -Wl,-z,noexecstack to the linker. Hm, in our case this line probably can be added in plugin_config (in Cinelerra-5.1 src root)? Or better to add this to main configure.ac ? I see line if test "x$CYGWIN" != "x" ; then echo 'FF_PATH ?= /usr/local' echo 'LDFLAGS += -L$(FF_PATH)/lib' echo 'CFLAGS += -I$(FF_PATH)/include' echo "" echo "CFLAGS += -DNO_BTRACE" echo "CFLAGS += -DNO_GDB" echo "CFLAGS += -DNO_CTX" echo "CFLAGS += -DNO_PRCTL" echo "CFLAGS += -DNO_TID" echo "CFLAGS += -DNO_XSELECT" echo "" else LDFLAGS+=" -z noexecstack" but it is "z noexecstack", not "-z,noexecstack" (space, not comma) At least gentoo page referenced also says "# This line goes before LDFLAGS is used (either by the ebuild or by econf/emake) append-ldflags -Wl,-z,noexecstack" so, probably add "," after z in this statement. But I'm not sure why only some binaries show this warning .... as --version GNU assembler (GNU Binutils) 2.26.1 (in Rosa 2016.1 chroot) I have 2.29.1 binutils on my host machine. Also, what exactly can be marked as documentation, in our case? {with %doc line in spec} Only README ? and probably %license COPYING ??

1 0

Boxblur compilation error on 32-bit
by Andrew Randrianasulu 31 Mar '20

31 Mar '20

--skip a lot--- make[3]: вход в каталог «/dev/shm/tmp/cinelerra-goodguy-20200331/cinelerra-5.1/plugins/boxblur» g++ `cat i686/c_flags` -DMSGQUAL=boxblur -c boxblur.C -o i686/boxblur.o opencv-20180401.tgz 50%[======================================================> ] 124,12M 8,92MB/s ост 15s g++ `cat i686/c_flags` -DMSGQUAL=bluebananaengine -c bluebananaengine.C -o i686/bluebananaengine.o boxblur.C:125:6: ошибка: прототип для «void BoxBlurConfig::interpolate(BoxBlurConfig&, BoxBlurConfig&, int64_t, int64_t, int64_t)» не имеет соответствия в классе «BoxBlurConfig» void BoxBlurConfig::interpolate(BoxBlurConfig &prev, BoxBlurConfig &next, ^ boxblur.C:45:7: ошибка: претендент: void BoxBlurConfig::interpolate(BoxBlurConfig&, BoxBlurConfig&, long int, long int, long int) void interpolate(BoxBlurConfig &prev, BoxBlurConfig &next, ^ opencv-20180401.tgz 50%[=======================================================> ] 126,09M 8,89MB/s ост 15s cc1plus: предупреждение: unrecognized command line option «-Wno-stringop-truncation» cc1plus: предупреждение: unrecognized command line option «-Wno-format-overflow» cc1plus: предупреждение: unrecognized command line option «-Wno-format-truncation» cc1plus: предупреждение: unrecognized command line option «-Wno-stringop-overflow» cc1plus: предупреждение: unrecognized command line option «-Wno-unknown-warning-option» make[3]: *** [../../plugin_config:51: i686/boxblur.o] Ошибка 1 ---- I'll re-run with LANG set to English next time ....

2 2

Patches again - filepng, opencv config
by Andrew Randrianasulu 30 Mar '20

30 Mar '20

Sorry for insisting on this filepng part - but it was my work, and I dislike to ship broken feature! I actually tested Cinelerra git on Ubuntu Live DVD, and _16 bit_ pngs were broken there without it. It was as simple as 1) opening the video 2) setting project to rgba-float color format. 3) trying to save png (from non-black area of timeline) and set options to "with alpha, 16 bits". By default Cin adds encoded results into resources and on new tracks - you clearly can see it will be black/broken. 8-bits PNGs are OK. Ubuntu image I used: http://mirror.yandex.ru/ubuntu-cdimage/xubuntu/releases/18.04/release/ xubuntu-18.04.4-desktop-amd64.iso - 1.4 Gb Then I created 4 Gb file in tmpfs, formatted it with btrfs with compression, and booted Live image: guest@slax:/dev/shm$ wget http://mirror.yandex.ru/ubuntu-cdimage/xubuntu/releases/18.04/release/xubun… --2020-03-25 13:55:42-- http://mirror.yandex.ru/ubuntu-cdimage/xubuntu/releases/18.04/release/xubun… Распознаётся mirror.yandex.ru… 213.180.204.183, 2a02:6b8::183 Подключение к mirror.yandex.ru|213.180.204.183|:80... соединение установлено. HTTP-запрос отправлен. Ожидание ответа… 200 OK Длина: 1534459904 (1,4G) [application/octet-stream] Сохранение в: «xubuntu-18.04.4-desktop-amd64.iso» xubuntu-18.04.4-desktop-amd64.iso 100%[==============================================================================================================>] 1,43G 8,26MB/s за 6m 40s 2020-03-25 14:02:28 (3,66 MB/s) - «xubuntu-18.04.4-desktop-amd64.iso» сохранён [1534459904/1534459904] guest@slax:/dev/shm$ qemu-sy qemu-system-aarch64 qemu-system-i386 qemu-system-mips qemu-system-nios2 qemu-system-riscv64 qemu-system-sparc64 qemu-system-xtensaeb qemu-system-alpha qemu-system-lm32 qemu-system-mips64 qemu-system-or1k qemu-system-s390x qemu-system-tricore qemu-system-arm qemu-system-m68k qemu-system-mips64el qemu-system-ppc qemu-system-sh4 qemu-system-unicore32 qemu-system-cris qemu-system-microblaze qemu-system-mipsel qemu-system-ppc64 qemu-system-sh4eb qemu-system-x86_64 qemu-system-hppa qemu-system-microblazeel qemu-system-moxie qemu-system-riscv32 qemu-system-sparc qemu-system-xtensa guest@slax:/dev/shm$ qemu-system-x86_64 -m 2000 -display sdl,gl=on -soundhw es1370 -usb -cdrom xubuntu-18.04.4-desktop-amd64.iso qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory guest@slax:/dev/shm$ qemu-system-x86_64 -m 2000 -display sdl,gl=on -soundhw es1370 -usb -cdrom xubuntu-18.04.4-desktop-amd64.iso guest@slax:/dev/shm$ qemu-system-x86_64 -m 2000 -display sdl,gl=on -soundhw es1370 -usb -cdrom xubuntu-18.04.4-desktop-amd64.iso -enable-kvm -smp 3 guest@slax:/dev/shm$ qemu-system-x86_64 -m 2000 -display sdl,gl=on -soundhw es1370 -usb -cdrom xubuntu-18.04.4-desktop-amd64.iso -enable-kvm -smp 3 guest@slax:/dev/shm$ dd if=/dev/zero of=4Gb bs=1k count=4M 4194304+0 записей получено 4194304+0 записей отправлено 4294967296 байт (4,3 GB, 4,0 GiB) скопирован, 20,7155 s, 207 MB/s guest@slax:/dev/shm$ qemu-system-x86_64 -m 2000 -display sdl,gl=on -soundhw es1370 -usb -cdrom xubuntu-18.04.4-desktop-amd64.iso -enable-kvm -smp 4 -hda 4Gb WARNING: Image format was not specified for '4Gb' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. in just a hour I had compiled Cinelerra (by copying git tree from host BEFORE launching qemu) Note, in such mem-restricted VM you want to use zram (not default in this ubuntu flavor): as root modprobe zram echo 1000000000 > /sys/block/zram0/disksize mkswap /dev/zram0 swapon /dev/zram0 this will create 1Gb sized compressed swap in ram I even send email from this virtual setup, but it apparently was stuck in moderation due to size (over 750 kb). NOW, I found something really weird! Patch as attached worked on 64-bit Ubuntu, but for my system I *must* place this call to png_set_swap(png_ptr); differently, not before png_write_info(png_ptr, info_ptr); but AFTER! I actually left both there .... Still, this is something strange, I'll try to contact libpng author about this..... Also, I attach my current OpenCV tweaks - trim out unneeded stuff, fixing two typos, adding -stdc++11 line for my odd system. I still use opencv-20180401.tgz I also have two lame (mp3lame) patches, but will send them separately.

3 8

greycstoration plugin was disabled in may, 2016 ....
by Andrew Randrianasulu 30 Mar '20

30 Mar '20

https://git.cinelerra-gg.org/git/?p=goodguy/history.git;a=blobdiff;f=cinele… as "too costly" I wonder if 'too costly' was refering to CPU usage ? On next (local) rebuild I'll try to re-enable it and see how it work or break :}

2 3

[patch] More fully disable test and debug in thirdparty components
by Andrew Randrianasulu 29 Mar '20

29 Mar '20

I think something like this patch can be applied to automated builds, where you generally don't look into directories for debug, just want you binary package fast. I was trying to build CinelerraGG from source in just ~700 Mb compressed btrfs image on Live DVD from Linux Mint 18, 32-bit (from ~early 2016). With total 2Gb of memory for my virtual machine. It worked after I disabled ffmpeg's debug symbols, programs, and few other things in Cinelerra itself. Feel free to adapt to your needs. after applying this and opencv trim patch full 32-bit build eats around 2913M instead of 3650M or so. (uncompressed) PS: what exactly this file in thirdparty/src does, I can't find reference to it? -rw-r--r-- 32600440 cimg-source.txz ? --- diff --git a/cinelerra-5.1/thirdparty/Makefile b/cinelerra-5.1/thirdparty/Makefile index e343f39a..c4c6c4ad 100644 --- a/cinelerra-5.1/thirdparty/Makefile +++ b/cinelerra-5.1/thirdparty/Makefile @@ -131,6 +131,7 @@ esound.ldflags=" -lm -lstdc++" fftw.cfg_params= --disable-fortran --enable-shared=no ffmpeg.cfg_params= \ --enable-pthreads --enable-gpl --disable-ffplay \ + --disable-debug --disable-programs --disable-doc \ $(call if_want,VAAPI,--enable-vaapi,--disable-vaapi) \ $(call if_want,VDPAU,--enable-vdpau,--disable-vdpau) \ $(call if_want,NV, --enable-nvenc --enable-nvdec --enable-ffnvcodec) \ @@ -199,7 +200,7 @@ lame.cfg_vars?= CFLAGS+=" -O" lame.cfg_params?=--enable-shared=no lame.mak_params?= ; cd $(call bld_path,lame,include); ln -sf . lame libaom.cfg_vars?=$(call cmake_config,aom-master) -libaom.cfg_params?= -DENABLE_SHARED=no -DCMAKE_INSTALL_LIBDIR=lib \ +libaom.cfg_params?= -DENABLE_SHARED=no -DENABLE_TESTS=OFF -DENABLE_EXAMPLES=OFF -DENABLE_TOOLS=OFF -DCMAKE_INSTALL_LIBDIR=lib \ -DCMAKE_INSTALL_PREFIX=$(call bld_path,libaom)/usr/local libaom.mak_params?= ; $(MAKE) -C libaom* install dav1d.cfg_vars?=echo "echo dav1d custom make" >> configure; chmod +x ./configure; @@ -242,6 +243,7 @@ opencv.cfg_vars?=$(call cmake_config,.) opencv.cfg_params?= -DBUILD_SHARED_LIBS:BOOL=OFF openexr.cfg_vars?=true; \# openexr.mak_vars?=true; \# +opus.cfg_params?= --disable-doc --disable-extra-programs speech_tools.mak_params?=-j1 tiff.cfg_vars+=LIBS+=" -lpthread" tiff.cfg_params+= --enable-shared=no --disable-zstd $(call if_pkg,libwebp,\ @@ -251,7 +253,8 @@ twolame.cfg_params?=--enable-shared=no x264.cfg_params?= --enable-static --enable-pic x265.cfg_vars?=$(call cmake_config,source) x265.cfg_params?= -DENABLE_SHARED=no -libvpx.cfg_params?= --enable-pic +libvpx.cfg_params?= --enable-pic --disable-unit-tests --disable-examples --disable-tools + DS:=$$$$$$$$ pkg_cfg=$(call bld_path,$(1),usr/local/lib/pkgconfig):

2 2

[patch] Disable more things in thirdparty/Makefile
by Andrew Randrianasulu 28 Mar '20

28 Mar '20

1) it disables building examples and tools in libaom - can disable tests too, but they might be useful for regression hunting in tree? 2) disable some programs and docs building in opus. 3) disables unit testing/standalone enc/dec, examples and tools building in libvpx (vp9 encoding and decoding of resulted file still works in Cin, tested) applicable on top of commit e1e5dee5935f9f416a31014906a7e0dfacb10c02 diff --git a/cinelerra-5.1/thirdparty/Makefile b/cinelerra-5.1/thirdparty/Makefile index e343f39a..bf8c73d2 100644 --- a/cinelerra-5.1/thirdparty/Makefile +++ b/cinelerra-5.1/thirdparty/Makefile @@ -199,7 +199,7 @@ lame.cfg_vars?= CFLAGS+=" -O" lame.cfg_params?=--enable-shared=no lame.mak_params?= ; cd $(call bld_path,lame,include); ln -sf . lame libaom.cfg_vars?=$(call cmake_config,aom-master) -libaom.cfg_params?= -DENABLE_SHARED=no -DCMAKE_INSTALL_LIBDIR=lib \ +libaom.cfg_params?= -DENABLE_SHARED=no -DENABLE_EXAMPLES=OFF -DENABLE_TOOLS=OFF -DCMAKE_INSTALL_LIBDIR=lib \ -DCMAKE_INSTALL_PREFIX=$(call bld_path,libaom)/usr/local libaom.mak_params?= ; $(MAKE) -C libaom* install dav1d.cfg_vars?=echo "echo dav1d custom make" >> configure; chmod +x ./configure; @@ -242,6 +242,7 @@ opencv.cfg_vars?=$(call cmake_config,.) opencv.cfg_params?= -DBUILD_SHARED_LIBS:BOOL=OFF openexr.cfg_vars?=true; \# openexr.mak_vars?=true; \# +opus.cfg_params?= --disable-doc --disable-extra-programs speech_tools.mak_params?=-j1 tiff.cfg_vars+=LIBS+=" -lpthread" tiff.cfg_params+= --enable-shared=no --disable-zstd $(call if_pkg,libwebp,\ @@ -251,7 +252,8 @@ twolame.cfg_params?=--enable-shared=no x264.cfg_params?= --enable-static --enable-pic x265.cfg_vars?=$(call cmake_config,source) x265.cfg_params?= -DENABLE_SHARED=no -libvpx.cfg_params?= --enable-pic +libvpx.cfg_params?= --enable-pic --disable-unit-tests --disable-examples --disable-tools + DS:=$$$$$$$$ pkg_cfg=$(call bld_path,$(1),usr/local/lib/pkgconfig):

1 0

Tried to add PKG_CHECK_MODULES to configure.ac
by Andrew Randrianasulu 27 Mar '20

27 Mar '20

well, it "works" by now, as in - it detects my non-std X11 installation prefix. documentation I was reading: https://autotools.io/pkgconfig/pkg_check_modules.html Problem is - for making it work that far I was forced to rename some PKG_* names from configure.ac into PKG1_* .... otherwise autoconf was complaining loudly about undefined macro: configure:6226: error: possibly undefined macro: PKG_FREETYPE configure:6288: error: possibly undefined macro: PKG_LZMA configure:6350: error: possibly undefined macro: PKG_PNG configure:6412: error: possibly undefined macro: PKG_PTHREAD configure:6474: error: possibly undefined macro: PKG_Z configure:6721: error: possibly undefined macro: PKG_LINUX_CDROM configure:6747: error: possibly undefined macro: PKG_LINUX_SYS configure:8780: error: possibly undefined macro: PKG_VDPAU configure:8846: error: possibly undefined macro: PKG_VAAPI configure:9101: error: possibly undefined macro: PKG_GL configure:9358: error: possibly undefined macro: PKG_XV configure:9395: error: possibly undefined macro: PKG_OSS configure:9423: error: possibly undefined macro: PKG_XFT configure:9530: error: possibly undefined macro: PKG_ALSA configure:9973: error: possibly undefined macro: PKG_OGG configure:10331: error: possibly undefined macro: PKG_FIREWIRE configure:10446: error: possibly undefined macro: PKG_DV configure:10484: error: possibly undefined macro: PKG_DVB configure:10772: error: possibly undefined macro: PKG_ESOUND configure:10969: error: possibly undefined macro: PKG_PULSE configure:11013: error: possibly undefined macro: PKG_ISOFS configure:11058: error: possibly undefined macro: PKG_LADSPA configure:11105: error: possibly undefined macro: PKG_SHUTTLE configure:11213: error: possibly undefined macro: PKG_SHUTTLE_USB configure:11646: error: possibly undefined macro: PKG_CUDA configure:11674: error: possibly undefined macro: PKG_DL configure:11760: error: possibly undefined macro: PKG_OPENCV configure:11781: error: possibly undefined macro: PKG_NUMA configure:11980: error: possibly undefined macro: PKG_OPENEXR yes, even from just trying ./autogen.sh I wonder how this problem must be solved, correctly?

1 0

lame-3.100 patches - only one tested
by Andrew Randrianasulu 27 Mar '20

27 Mar '20

Well, this is mostly for information on what i tried. One patch is applicable and doesn't result in compilation failure lame-3.100-fastcrc.diff # lame patches cp $CWD/lame-3.100-fastcrc.diff thirdparty/src/lame-3.100.patch1 #cp $CWD/lame-3.100-sse-20171014.diff thirdparty/src/lame-3.100.patch2 git apply -v $CWD/lame-make-opt.diff but second patch actually require -msse2 on x86-32, so I disabled it for now. You can tweak it a bit more, for example leaving only x86_64 part in those statements: +#if defined(__GNUC__) && (defined(__i386__) || defined(__x86_64__)) but this is just some kind of distraction. in opt patch I changed defaults to more aggressive: +lame.cfg_vars?= CFLAGS+=" -O3 -DUSE_FAST_LOG=1 -ffast-math" +lame.cfg_params?=--enable-shared=no --enable-nasm --enable-expopt=norm from this page: https://shenki.github.io/LameMP3-on-Power9/ actually I saw described there configure bug, but just added CFLAGS instead of patching autoconf stuff. Oh, this libpng strangeness makes me unhappy :/

1 0

Videoscopes on Compositor/viewer
by Andrea paz 26 Mar '20

26 Mar '20

Videoscopes button is wonderfull! Thank you very much. I'm proposing to "Time" that they make a cover of "Man of the Year" for GG.

3 2