https://groups.google.com/a/aomedia.org/g/av1-discuss/c/2F_tQddyd0c ===== Release Notes: 2023-11-30 v3.8.0 This release includes new codec interfaces, compression efficiency and perceptual improvements, speedup and memory optimizations and many bug fixes. This release is ABI compatible with the last release. some reported speed gains are impressive: Speedup and Memory Optimizations * Good-quality, single-thread encoder speedups: o 15% improvement for speed 5. o 12% improvement for speed 6. but most of them for new Arm servers, it seems. I'll try to see if I can repackage it here....
git files for update, actual tarballs a bit big so I'll put them into cloud вс, 17 дек. 2023 г., 05:10 Andrew Randrianasulu <[email protected]>:
https://groups.google.com/a/aomedia.org/g/av1-discuss/c/2F_tQddyd0c
=====
Release Notes:
2023-11-30 v3.8.0 This release includes new codec interfaces, compression efficiency and perceptual improvements, speedup and memory optimizations and many bug fixes. This release is ABI compatible with the last release.
some reported speed gains are impressive:
Speedup and Memory Optimizations * Good-quality, single-thread encoder speedups: o 15% improvement for speed 5. o 12% improvement for speed 6.
but most of them for new Arm servers, it seems.
I'll try to see if I can repackage it here....
вс, 17 дек. 2023 г., 08:09 Andrew Randrianasulu <[email protected]>:
git files for update, actual tarballs a bit big so I'll put them into cloud
https://cloud.mail.ru/public/tFTC/PpkmydyYP hopefully here
вс, 17 дек. 2023 г., 05:10 Andrew Randrianasulu <[email protected]>:
https://groups.google.com/a/aomedia.org/g/av1-discuss/c/2F_tQddyd0c
=====
Release Notes:
2023-11-30 v3.8.0 This release includes new codec interfaces, compression efficiency and perceptual improvements, speedup and memory optimizations and many bug fixes. This release is ABI compatible with the last release.
some reported speed gains are impressive:
Speedup and Memory Optimizations * Good-quality, single-thread encoder speedups: o 15% improvement for speed 5. o 12% improvement for speed 6.
but most of them for new Arm servers, it seems.
I'll try to see if I can repackage it here....
@Andrew I wanted to try to compile CinGG with your new patches, but I didn't quite understand how to use "x265-17122023.tar.xz". Another question: to apply the "0001-Limit-number-of-opencv-modules-we-build.patch" patch, do I have to compile OpenCV as well (i.e from git)?
вс, 17 дек. 2023 г., 12:32 Andrea paz <[email protected]>:
@Andrew I wanted to try to compile CinGG with your new patches, but I didn't quite understand how to use "x265-17122023.tar.xz".
put it in thirdparty/src, move away x265_3.5.tar.xz temporarily, apply git patch, re-run autogen.sh , configure, make. It should pick up new x265 (you will see its new directory in thirdparty after build successfully unpack and compile it). Another question: to apply the
"0001-Limit-number-of-opencv-modules-we-build.patch" patch, do I have to compile OpenCV as well (i.e from git)?
I think *just* repacked opencv-2020 archive from cingg site should work, as long as you replace faulting module in its .cache from new version and cmake file searching for it. https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007382.html But you can also try to get opencv from git building inside cingg - I just found relying on daily changed git is not very reliable ? Try --with-opencv=sta,git argument to cingg's configure and see how it works (or not). You can also try --with-opencv=sys for attempt at linking to system's opencv, but it need to be compiled with contrib modules for this to work, not sure how Arch package it? options briefly explained in opencv_build file in root of our source directory.
I tried to compile CinGG with your patches. I had problems applying the opencv one and the x265 one however, by passing the paths manually, I think I was able to apply them (apologies, apparently my brain refuses to understand how patches work). The compilation however fails immediately, I think with an error about x265. I attach the cin5.log
вс, 17 дек. 2023 г., 16:13 Andrea paz <[email protected]>:
I tried to compile CinGG with your patches. I had problems applying the opencv one
Most likely because it already upstream in our git ? and the x265 one however, by passing the paths
manually, I think I was able to apply them (apologies, apparently my brain refuses to understand how patches work).
was "git am" failing for some reason? You always can inspect patches visually (say with "less patch.diff") and see if they from git or plain patches .... The compilation however
fails immediately, I think with an error about x265. I attach the cin5.log
/bin/bash: riga 1: cd: x265*: File o directory non esistente are you sure you have both x265-17122023.tar.xz in thirdparty/src and it also correctly named in configure.ac (in case patching failed) AND your run ./autogen.sh ?
вс, 17 дек. 2023 г., 16:46 Andrew Randrianasulu <[email protected]>:
вс, 17 дек. 2023 г., 16:13 Andrea paz <[email protected]>:
I tried to compile CinGG with your patches. I had problems applying the opencv one
Most likely because it already upstream in our git ?
and the x265 one however, by passing the paths
manually, I think I was able to apply them (apologies, apparently my brain refuses to understand how patches work).
was "git am" failing for some reason? You always can inspect patches visually (say with "less patch.diff") and see if they from git or plain patches ....
Ah, fired up ubuntu 16 VM, patch really fails to apply because I put my changes on top of another experimental patch (attached). So you can try to apply it first, and then two other patches from folder. Do not forgot to mv thirdparty/src/x265_3.5.tar.xz to another location and move both xz tarballs to thirdparty/src ! Sorry for inconvenience ....
The compilation however
fails immediately, I think with an error about x265. I attach the cin5.log
/bin/bash: riga 1: cd: x265*: File o directory non esistente
are you sure you have both x265-17122023.tar.xz in thirdparty/src and it also correctly named in configure.ac (in case patching failed) AND your run ./autogen.sh ?
Sadly, libaom 3.8.0 broken quite hard on cmake 3.5 not sure if I will able to fix it. вс, 17 дек. 2023 г., 17:10 Andrew Randrianasulu <[email protected]>:
вс, 17 дек. 2023 г., 16:46 Andrew Randrianasulu <[email protected]>:
вс, 17 дек. 2023 г., 16:13 Andrea paz <[email protected]>:
I tried to compile CinGG with your patches. I had problems applying the opencv one
Most likely because it already upstream in our git ?
and the x265 one however, by passing the paths
manually, I think I was able to apply them (apologies, apparently my brain refuses to understand how patches work).
was "git am" failing for some reason? You always can inspect patches visually (say with "less patch.diff") and see if they from git or plain patches ....
Ah, fired up ubuntu 16 VM, patch really fails to apply because I put my changes on top of another experimental patch (attached).
So you can try to apply it first, and then two other patches from folder.
Do not forgot to mv thirdparty/src/x265_3.5.tar.xz to another location and move both xz tarballs to thirdparty/src !
Sorry for inconvenience ....
The compilation however
fails immediately, I think with an error about x265. I attach the cin5.log
/bin/bash: riga 1: cd: x265*: File o directory non esistente
are you sure you have both x265-17122023.tar.xz in thirdparty/src and it also correctly named in configure.ac (in case patching failed) AND your run ./autogen.sh ?
вс, 17 дек. 2023 г., 18:13 Andrew Randrianasulu <[email protected]>:
Sadly, libaom 3.8.0 broken quite hard on cmake 3.5 not sure if I will able to fix it.
ah, this one https://aomedia.googlesource.com/aom/+/a250c26cade747ead5ff434ba4c69ca012115... may be I'll able to adapt code back to old way of building nasm objects ... it fails to find includes.
вс, 17 дек. 2023 г., 17:10 Andrew Randrianasulu <[email protected]>:
вс, 17 дек. 2023 г., 16:46 Andrew Randrianasulu <[email protected]
:
вс, 17 дек. 2023 г., 16:13 Andrea paz <[email protected]>:
I tried to compile CinGG with your patches. I had problems applying the opencv one
Most likely because it already upstream in our git ?
and the x265 one however, by passing the paths
manually, I think I was able to apply them (apologies, apparently my brain refuses to understand how patches work).
was "git am" failing for some reason? You always can inspect patches visually (say with "less patch.diff") and see if they from git or plain patches ....
Ah, fired up ubuntu 16 VM, patch really fails to apply because I put my changes on top of another experimental patch (attached).
So you can try to apply it first, and then two other patches from folder.
Do not forgot to mv thirdparty/src/x265_3.5.tar.xz to another location and move both xz tarballs to thirdparty/src !
Sorry for inconvenience ....
The compilation however
fails immediately, I think with an error about x265. I attach the cin5.log
/bin/bash: riga 1: cd: x265*: File o directory non esistente
are you sure you have both x265-17122023.tar.xz in thirdparty/src and it also correctly named in configure.ac (in case patching failed) AND your run ./autogen.sh ?
I believe I did the steps you indicated correctly. The patches did not give any problems (but I applied them manually). I seem to have the same crash as the first time, though. I attach the cin5_02.log
вс, 17 дек. 2023 г., 22:39 Andrea paz <[email protected]>:
I believe I did the steps you indicated correctly. The patches did not give any problems (but I applied them manually). I seem to have the same crash as the first time, though. I attach the cin5_02.log
hm, hold on then, I 'll try to remake clean series tomorrow ...
Built libaom 3.8 just on my default laptop now after downloading from https://cloud.mail.ru/public/tFTC/PpkmydyYP and did 1 minor test with no problems. Andrew, is libaom-v3.4.0.patch1 equivalent for 3.8 no longer needed? On Sat, Dec 16, 2023 at 10:17 PM Andrew Randrianasulu < [email protected]> wrote:
вс, 17 дек. 2023 г., 08:09 Andrew Randrianasulu <[email protected]>:
git files for update, actual tarballs a bit big so I'll put them into cloud
https://cloud.mail.ru/public/tFTC/PpkmydyYP
hopefully here
вс, 17 дек. 2023 г., 05:10 Andrew Randrianasulu <[email protected]
:
https://groups.google.com/a/aomedia.org/g/av1-discuss/c/2F_tQddyd0c
=====
Release Notes:
2023-11-30 v3.8.0 This release includes new codec interfaces, compression efficiency and perceptual improvements, speedup and memory optimizations and many bug fixes. This release is ABI compatible with the last release.
some reported speed gains are impressive:
Speedup and Memory Optimizations * Good-quality, single-thread encoder speedups: o 15% improvement for speed 5. o 12% improvement for speed 6.
but most of them for new Arm servers, it seems.
I'll try to see if I can repackage it here....
вс, 17 дек. 2023 г., 22:39 Phyllis Smith <[email protected]>:
Built libaom 3.8 just on my default laptop now after downloading from https://cloud.mail.ru/public/tFTC/PpkmydyYP and did 1 minor test with no problems. Andrew, is libaom-v3.4.0.patch1 equivalent for 3.8 no longer needed?
They reworked cpu detection so it does not apply anymore. Hopefully not needed, but for now I just trying to see if 3.6.1 can be compiled on old Ubuntu 16 without too much cmake hacking ...
On Sat, Dec 16, 2023 at 10:17 PM Andrew Randrianasulu < [email protected]> wrote:
вс, 17 дек. 2023 г., 08:09 Andrew Randrianasulu <[email protected]
:
git files for update, actual tarballs a bit big so I'll put them into cloud
https://cloud.mail.ru/public/tFTC/PpkmydyYP
hopefully here
вс, 17 дек. 2023 г., 05:10 Andrew Randrianasulu <[email protected]
:
https://groups.google.com/a/aomedia.org/g/av1-discuss/c/2F_tQddyd0c
=====
Release Notes:
2023-11-30 v3.8.0 This release includes new codec interfaces, compression efficiency and perceptual improvements, speedup and memory optimizations and many bug fixes. This release is ABI compatible with the last release.
some reported speed gains are impressive:
Speedup and Memory Optimizations * Good-quality, single-thread encoder speedups: o 15% improvement for speed 5. o 12% improvement for speed 6.
but most of them for new Arm servers, it seems.
I'll try to see if I can repackage it here....
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith