Re: [FFmpeg-devel] duplicate symbol '_dec_init' in: fftools/ffmpeg_dec.o
I fixed it on my dev machine by renaming the function in libbluray and creating a new lib. I still think that this is a temporary hack and should be fixed properly. I've opened an issue with libbluray, so I hope that I'll get a reply at one point. I'm still not entirely sure who actually has to fix this. But I guess it will be determined in due time. Cheers, K. C. OpenPGP_signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] duplicate symbol '_dec_init' in: fftools/ffmpeg_dec.o
On 2024-03-17 08:10, Timo Rothenpieler wrote It only breaks when statically linking. The symbol is not exported by libbr. In this case the only fix is to use a prefix in libbr, and who knows whether they will do that. I opened an issue with them but haven't received a reply yet. Just rename it with a define in CPPFLAGS and call it a day until they fix it in libbr. What is "it" and where? in the ffmpeg code or libbr? Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ OpenPGP_signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] duplicate symbol '_dec_init' in: fftools/ffmpeg_dec.o
Hi, On 2024-03-16 10:26, Christopher Degawa wrote: Seems the conflict comes from https://code.videolan.org/videolan/libbluray/-/blob/master/src/libbluray/disc/dec.c?ref_type=heads#L287 and https://github.com/FFmpeg/FFmpeg/commit/c4de5778bceab3c15f1239f1f16816749a7fd3b6 Perhaps you could also try asking libbluray if they could use an internal prefix. Otherwise you might need to do a rename of that function on ffmpeg's side. Hmm, this commit in ffmpeg broke the possibility to link ffmpeg with libbluray. Just to make this perfectly clear, before that commit it worked without issues. This means that nobody is able to use libbluray and ffmpeg from this point forward. I am sorry, but this commit should be reverted. The commit message reads: Rename dec_open to dec_init(), as it is more descriptive of its new purpose. Who cares about how descriptive it is as long as it works. Now it doesn't. This was not a change to implement a feature or fix a bug, but a simple refactor, because somebody didn't like the name. In reality I agree with you that it might be better for libbluray to use a prefix/namespace or whatever. But until then, ffmpeg should still be able to be linked with libbluray. Is my standpoint unreasonable? If so, why? Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ OpenPGP_signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] duplicate symbol '_dec_init' in: fftools/ffmpeg_dec.o
Hello, On 2024-03-16 10:07, Gnattu OC via ffmpeg-devel wrote: If you are using Xcode >= 15 then you will need to add `-Wl,-ld_classic` to LDFLAGS. I've already been using it since I switched to Xcode 15. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ OpenPGP_signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] duplicate symbol '_dec_init' in: fftools/ffmpeg_dec.o
Hello, It's me again - the dude who compiles ffmpeg for macOS... ;-) I haven't updated the referenced libbluray, but only compiled ffmpeg the way I always do. The last time was about 3 days ago and all was good. This is the git hash of ffmpeg I tried to compile: b47abd5737 duplicate symbol '_dec_init' in: fftools/ffmpeg_dec.o /Users/Shared/ffmpeg/sw/lib/libbluray.a(libbluray_la-dec.o) ld: 1 duplicate symbol for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) The only code that changed was ffmpeg and libx265, thus I suspect it was a change to ffmpeg. I can't really do a git bisect, because this error only happens after ffmpeg is compiled at the linker stage, so that would take me forever However, the dev who did a change related to this would probably know right away. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ OpenPGP_signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] linker error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2022-10-20 02:48, Nicolas George wrote: > Possibly. But between a library and a final program, the one who is at > fault when a non-namespaced symbol conflicts is the library. In theory I agree with you. However, libass has been using the same non-static read_file function for many, many years. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmNQ+OsACgkQvgmFNJ1E 3QAOLQ/9F8d7myiHryjRti5U2+29vx8ExZM79JLM8wuz8U2Ba+EcszHec5FNFFAL Fs7r9zqTy4CcOO6/mTmnZGXOrCNQDSnCD/Z7mDpTCGyPfjcJ+SVvwvugvazuduig 7PQ7pAj1rOGzcaRvRrY5gvS5WP/g58uxZNtxNp6t2sGfHmdx9RCSz3rDgp01jDzj 5KJSbP8JAz7/jQnlhRMP3ol3nf0AQpbdZKQ9FfBJLKpCEd4C7qLNI9wQ77c5f4F6 uJiZKFcg8KY4IWTYVVggH7eLqTOeoFCwuCfvut0v5izBFFvY0JILHWqe8HofwHwq IcffmHA5lI/18w9zG0jgzToA90WiCrAYQbii0RHfm0yqXvpyDlqOvugfN08fMqUd R9j7s4FR3GZy6DhLvSeI+z9/1sk8XbtKGEZ06riD22NaXIdZkb40hcCeKoUH1iqK M8ADf90Zt8iVmw56uStVW33j30TsE8CHlTORo1Fjzl7pViyqwuue31Ty5ipHFY7l JchFRTRIpvPS9rE62LWnE9sDORL4oYZKfPDjgTR7byc8OL2q1Jh/S5wFhW23g+g7 1yV2/1KIIHtB315sRm9Tk4nLJxsmlGjKC/TIt0l/QNyXIeWC/dRnwQoRqnTVaIk1 NUtXLIjAZX/xDyyd0nIX4Spx3lIWU6+9u9WngIsXLzObYhOv82g= =JFAH -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] linker error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I compile the static ffmpeg binaries for macOS and I have noticed just now the following error: duplicate symbol '_read_file' in: fftools/ffmpeg_opt.o /Users/Shared/ffmpeg/sw/lib/libass.a(ass.o) ld: 1 duplicate symbol for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation ) make: *** [ffmpeg_g] Error 1 I believe it has something to do with commit 18d6c07267994398f99b2241f577f8e7118af099 fftools/ffmpeg_opt: move opening output files into a new file Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmNQz30ACgkQvgmFNJ1E 3QBXaQ//cihF3S1R5ruPOgOr7eR+sCdo1uoJEncezKJmoF/3IrsEgB05YHiU4nSz H9Qwm1eE8QNDBoYZNZ9gc/bRB7S4u+kUPKAQiE3ZyfYteK2Ez/zy9v/OCXX639pv cuCinQGmIcBAMnHo9Ue3v+E2T89x/fzGyew+3jbfkiG9Gl2aTV/u1k+x/IRzfRCE HuooGGaZUpQhQ0us46CfEHUjHte3QWCDUxKy9tkowVVFgHSyBZMcWfJb7VyN9rSJ CDh0uImRkJ6tR5NtpcpDEG+AJ5HK+olMEaZHEZ8WrlJOrC6AGK1d5N/tGaRfIxiO 7h9K9Disu/HEoGPcA0ULGlkN1axCLPJL0mEKRJVQBEe9Nh7OGFceA3uf/2a0TaBU bevCijy0gNHJi9BNPjK8+vvIgMhsfbkCqmnOKqnntHhUEyEfgm5CT7oBwC8DNZFO aXempSZAqUnCECv/Ry8GU66C/x97FQgvHTYFMrb5gfdAk7mSMu5vge0hkzqM IC7b3MNzSkjEOj4/cZCpzayZjqf2PJ3OIzaZ2na8jT7x7gm4neY9GvIzyF72xoka 4woquOWq3n4F2KpFK4Y5wBxlJYVd1slf7jf5A+r5MVNl+pfiJ2UfVGbgcBdUgH/J JnHAjO+nCQ8NAJGZ/jgRL3vy6BoG03u3WmfdjVqzUMBFuwvxEHE= =CZog -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2022-02-16 19:55, Stephen Hutchinson wrote: > FFmpeg dlopens AviSynth, it only needs the headers and doesn't try to > link it. It has never linked to AviSynth. This I find strange. dlopen is rather useless when you create static binaries unless you want to ship X diffreent dylibs or SOs with the binary. There's also no static version of frei0r. Very annoying. > If 3.5.1 is working (and by that I assume you mean you're opening a > Version() script in FFplay and it's showing you the video clip with the > version and copyright information), then libavisynth.dylib is somewhere > on your DYLD_LIBRARY_PATH, and you could just as easily set > DYLD_LIBRARY_PATH to the /usr/lib directory in the -filesonly package and > that Version() script will start reporting 3.7.1 instead. It's definitely not working, since I don't ship any dylibs. I always thought 3.5.1 li9nked a static lib, but I checked. It does not. Even if I wanted to I couldn't ship any dylibs, since I can't build AviSynthPlus on macOS 10.14. > At this point, just use latest git, since that's where the HEADERS_ONLY > fix resides: And HEADERS_ONLY is exactly what it says on the tin: it only > sets CMake to install the headers, and stops it from building the > library, which wouldn't get linked to anyway. Ok, this worked. I was able to compile ffmpeg again. At least now I know that avisynth won't work with static banaries unless people install dylibs themselves. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmIOyeMACgkQvgmFNJ1E 3QDS7g//VMqsrxTK7uC/N65ydY4MvEOhqZJcAJqTtmyDStqWrgLOr1zeTutu359I G3ah7M9/BYnZVwiVDypLgvRBNLR9F7bgv4CdG+VaV2M5Ljuv8yqiLG4ohbY6BcC3 6Da+CV2X7ylDunnGuI+jFQ2+E/DrP6lJRvMweotsLZvluTU3PCGNIpOHxt6SLq1S eN9V9UluOZT/+YYk4XOWiWpYucDBvZbRUCfcZtckKESRwpRrZCMRO9ExJXdRvNRr gyy0EIIDqAHhoEyP7RkadFuHOco4Beppalru4+UEvSwWae2B2pr8pwfFh8RUvXk6 75SNWOzfQoyndvEQR4jDv3PLFswWMv8upeGoGJHsb0NcOY31Uk0Y58kMzbzDC/eT uK8Jp5+5Gx+uOG8k/dvKQK5TllnelApSFaVbyeuzrcRnphVi6ad6OtdSPBaWKjdD BljKMkAr/plpCsfuJ9THdXIo3Q0qwoXC4l/fL8Q35uiqYcOOa8Ax/FePe/srMDnp vxtDBBzo+8nA2305OUtErEAq0XhgCnSvOyfzoXx4fWxF39N15tU2VKTDoPAkjx9A 5dx/753wos5HewC5WeESzKCALXWu5l9r/sV/Jih8rf+8YXzJweMjso+Ca2B8e7bv 2nWvPMAcqtByklBnsVpkV3QTGDaxb2c1E4XhEoTchKjVKeFzrQo= =5yaK -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2022-02-16 18:04, hydra3...@gmail.com wrote: > This probably will not help you, since I cross-compile under Ubuntu for > target Win10. However, for the record I did this, not quite according to > the git instructions, and it did not abort: > > # Changed dir from > /home/u/Desktop/_working/workdir/x86_64/AviSynthPlus_git to subfolder > avisynth-build > > cmake .. > -DCMAKE_TOOLCHAIN_FILE="/home/u/Desktop/_working/workdir/mingw_toolchain.cma ke" > -G"Ninja" > -DCMAKE_INSTALL_PREFIX=/home/u/Desktop/_working/workdir/toolchain/x86_64-w64 - -mingw32/x86_64-w64-mingw32 > -DHEADERS_ONLY:bool=on > > ninja VersionGen -j 6 > > ninja install -j 6 The file you are referencing is not even in the AviSynthPlus source tree. Also a mingw cmake file would not be very useful on macOS. But thanks anyway. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmINhS4ACgkQvgmFNJ1E 3QDtrBAAr+DFCh6UXswzSlJ7lE6J8GX7FxofZgq7H97L5SgCOBS7azjuF9isM6d1 OrY2WqGPsBiK6NnTvlDUtaPmtxJkZQ8OEc2YwfsX1K0lSdjWmtBlbjIoWNZTiwja H1xydX+XueWeb6Gm5c4NEXNyxsIquFW8nGTX2q8mZ8w54K3nFZhNhbPTtskzS0k6 GUyFYf8RxMICyXO1EcJhsHLu1zWTXDV72yVEIiHcyg4SNjggkJv9f4lnJSTZ9Igd FzZAWT+Z7tLg8laAftFUDeEWj1vjbUF007ldvBUl6lbg5aWfLdvsau3eEn4EKeSQ Sspl5mieo/XKljdqOugfaPRNdaK4BNv9Q/oX6gxXJ9jYacU5HhHwo8FekKXP+wbn VNvB9sYdzp/NaAlPjQE71e/jdQHMA74ETb3duV3fjaWCPehnxX0iOWhBPfhPzM0O RerC+6rCoYEJoD30jHuYDPB029Z/jdU0Y6BUCWt03MSG2M1bknsKxTcrYjRJFJ+V Rzrnh34iRwTU5sBwoevG6oI6aojHSjXY9aY4sfHmttVbkpPbVpEVpyO8/QRaysBI 0r908qY3Q1GjTBX8iNKiGyp4E0DUbtVBb7oki/7X7ZR7klSuM2jyRt+Fj7OlQCsA 4NMB3iXwMODo/OwAQ1AYVdF0j6vl+auwxo9gDMcrlHstNRehOGI= =hF9U -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2022-02-16 02:37, Stephen Hutchinson wrote:
> There is another option, basically what Gyan suggested earlier: grab the
> release build of 3.7.1, fetch the extra headers from the Github repo,
> then copy either all the contents of the tarball's /usr directory into
> the system /usr directory (or wherever your working ${prefix} is), or
> just the 'avisynth' directory into ${prefix}/include. Then try FFmpeg
> again.
This does not work. I compile static binaries. The filesonly tarball only
has dylibs.
As I mentioned nefore:. 3 days ago everything worked fine. Now the ffmpeg
builds are broken and I can no longer compile ffmpeg.
Is there any chancf you can add something to make it work again with 3.5.1
which compiled withtout issues on macOS 10.14 and which I've been using
since it was released.
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmINQXwACgkQvgmFNJ1E
3QAphA//aAu21aLcSYXTtFdb2DlW/lAdN3y7MhIftRXuy3zqTy7BnPOpiWwm6jtw
lq7Ck4IJMtFSbtH2Xh7RHqYKk1UVNZiwjIiPHhx/mBDxr+40wRdV44u00NPuQaGl
3ZHHqVSlODr0TSR9HjsW1ywM5BcxX4+FiilFHyM0JVlxTpEp6kqyisN8pRsL3Zyk
o00DVvTvTQD2GDd/eN+TRVl39d+8HD0DU16PzKF6ptuQs7Xyehoh/gt89fIhv5om
7/JWhJY9ritGQYyjzZq8J7vUrQ4dB7dLQMHbULnDaRC+7XQLdeTw5IU5NuNxqw4C
IUh4PbuYiiVLK0cE5HpvlPs6LwbkVvbw6Er9QtOUAtWEIys+d0sQxS5STm4NqUrB
92MXmkPqwDE8MgW5QJGo2n+vT1N4zDT49ot9aIa5NGb7PJ3WLRmqcx6RUbUKPPXn
JxtM1JYaVGHQIkqzxXh1Y8nWaMX5ynkXXj/TqIL8qjOuGgpaaqX9+mo6Uj7ZU3Vp
94AvAofrTXL6t7ZvnQGR53GNwroXsmy9/ffxZLhQSRQZj7oUasIeXRgDWkuJFaPd
CDvda7MXBw2A3v1Z60GhIYwZe2rbpsCL61lHFX0SmcIjy8eLk0ZbucwapnpCit0Y
IVtRbJCoDDrSCEwXgmXGkrlQ/KXGlCAX35C4Rw8T5hJLKqShE58=
=oTu0
-END PGP SIGNATURE-
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2022-02-15 22:50, Stephen Hutchinson wrote:
> Those errors would indicate you're not on the 3.7 branch, because if the
> filesystem submodule isn't present, it doesn't emit those errors, it
> stops dead because of the missing header. If the
> submodule is there, it compiles as it should. Is the filesystem
> subdirectory empty?
Nope, I used the git command you posted. I also checked the filesystem dir:
[tessus@epsilon3 0 ~/data/ext/ffmpeg/compile/AviSynthPlus/filesystem
:3f1c185|✔]$ ll
total 76
drwxr-xr-x 18 tessus wheel 576 2022-02-15 20:23 .
drwxr-xr-x 16 tessus wheel 512 2022-02-15 20:31 ..
- -rw-r--r-- 1 tessus wheel 2842 2022-02-15 20:23 .appveyor.yml
drwxr-xr-x 4 tessus wheel 128 2022-02-15 20:23 .ci
- -rw-r--r-- 1 tessus wheel 313 2022-02-15 20:23 .cirrus.yml
- -rw-r--r-- 1 tessus wheel 576 2022-02-15 20:23 .clang-format
- -rw-r--r-- 1 tessus wheel 795 2022-02-15 20:23 .drone.yml
- -rw-r--r-- 1 tessus wheel35 2022-02-15 20:23 .git
drwxr-xr-x 3 tessus wheel96 2022-02-15 20:23 .github
- -rw-r--r-- 1 tessus wheel32 2022-02-15 20:23 .gitignore
- -rw-r--r-- 1 tessus wheel 4141 2022-02-15 20:23 .travis.yml
- -rw-r--r-- 1 tessus wheel 1937 2022-02-15 20:23 CMakeLists.txt
- -rw-r--r-- 1 tessus wheel 1086 2022-02-15 20:23 LICENSE
- -rw-r--r-- 1 tessus wheel 35982 2022-02-15 20:23 README.md
drwxr-xr-x 4 tessus wheel 128 2022-02-15 20:23 cmake
drwxr-xr-x 5 tessus wheel 160 2022-02-15 20:23 examples
drwxr-xr-x 3 tessus wheel96 2022-02-15 20:23 include
drwxr-xr-x 11 tessus wheel 352 2022-02-15 20:23 test
I'm building AviSynth like this:
[tessus@epsilon3 0 ~/data/ext/ffmpeg/compile/AviSynthPlus]
mkdir avisynth-build && cd avisynth-build
cmake -DCMAKE_INSTALL_PREFIX:PATH=${TARGET} -DBUILD_SHARED_LIBS=OFF ..
make VersionGen install
-
Until 2 days ago I could compile ffmpeg with AviSynth 3.5.1 just fine. So
something must have made my configure to fail.
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmIMhzEACgkQvgmFNJ1E
3QDprg/+NckvpYpfWeq6jPKKjGmJQazTxFpE0PyyZAngEx9Du6UP49iitT4UefJH
5hOnm7Ps6gkmdNK5WZaeUHL87Vyarya6WIzdNAymzwERsapRfxdsc4YyEbh26bK6
eMf7Qz+4kZ2tfqSGvdTfCDqoYybr/nmR4W/T06jEbeV4v2OmZZieNrDPsel+BUjU
2pSSSCmglJ5qDXcDKfaqCXUtXI5TGJGKm0299yHcZq6Y+OOQGGTCz6f2JbMo0QL/
9X9CNUXxGkCuMgJ4fsOfSq1GkhFQt0eVAIBY9/vIcXKdAPnw+qHgi/Y6OVh6FUc2
S8Y5BEcE73jkjuakimje4DV5h/TfAe6vlavM1MCuHhMblQKYstsrYaRoEkYidb2E
sPp87KadqxCveYW7sTuNs0TxBuUJjWef/7NeShoBAsJTlgGgqM7Iel7ctEZz9gD7
TMOAwSqGy+B2OVXeQvQA5oLJf7I4a4WoVCUgSySKTRNh8Dq52X9wfmJPMD5iGz6K
eAR0Z4jlZ3ihZ9NgrjHBqVaSNwbGsrvOlpdrNptxKwFV3ob2VFGuIw5rSJy53y++
e+WI+beujsNc1KX/oU+2CEDX5M1jua6+xBMW08gOpawB4YRxMyx3NfcJjgNwdNZq
PWix846IxGDfd9O0pP7KAEmzX00Cld6b9k417ql/0m5zF1LMYw0=
=NM4f
-END PGP SIGNATURE-
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2022-02-15 18:55, Stephen Hutchinson wrote:
>
> git clone --recursive -b 3.7 https://github.com/AviSynth/AviSynthPlus
> [build/install as usual]
>
> -b 3.7 is equal to the tarball for 3.7.1a (which has the fix for the case
> of building the entire library), --recursive pulls in the submodule
> needed for the default AppleClang on 10.13 & 10.14. Unfortunately,
> Github doesn't put submodules in the tarballs.
>
> The fix on latest git was specifically for those that want to use the
> HEADERS_ONLY option when configuring.
Unfortunately this didn't work.
Building the new AviSynthPlus results in the following errors:
[ 10%] Building CXX object
avs_core/CMakeFiles/AvsCore.dir/core/FilterGraph.cpp.o
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:27
:
error: 'path' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:739:24:
note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
^
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:23
:
error: 'path' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:773:3:
note: 'path' has been explicitly marked unavailable here
path(const _Source& __src, format = format::auto_format) {
^
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:23
:
error: '~path' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:791:3:
note: '~path' has been explicitly marked unavailable here
~path() = default;
^
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:35
:
error: 'lexically_normal' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:1110:8:
note: 'lexically_normal' has been explicitly marked unavailable here
path lexically_normal() const;
^
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:35
:
error: '~path' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:791:3:
note: '~path' has been explicitly marked unavailable here
~path() = default;
^
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:14
:
error: 'absolute' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:1477:39:
note: 'absolute' has been explicitly marked unavailable here
inline _LIBCPP_INLINE_VISIBILITY path absolute(const path& __p) {
^
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:10
:
error: '~path' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:791:3:
note: '~path' has been explicitly marked unavailable here
~path() = default;
^
/Users/Shared/ffmpeg/compile/AviSynthPlus/avs_core/core/FilterGraph.cpp:510:55
:
error: 'generic_string' is unavailable: introduced in macOS 10.15
return fs::absolute(fs::path(f).lexically_normal()).generic_string();
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
/usr/bin/../include/c++/v1/filesystem:1019:15:
note: 'generic_string' has been explicitly marked unavailable here
std::string generic_string() const { return __pn_; }
^
8 errors generated.
make[2]: *** [avs_core/CMakeFiles/AvsCore.dir/core/FilterGraph.cpp.o] Error 1
make[1]: *** [avs_core/CMakeFiles/AvsCore.dir/all] Error 2
make: *** [all] Error 2
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow th
Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2022-02-14 17:03, Stephen Hutchinson wrote: > Should be fixed in > https://github.com/AviSynth/AviSynthPlus/commit/0e583378116c857372232e9886c5 99df2fb8da85 > > with the caveat (noted in AviSynth+'s README.md) that the `make install` step > now needs to explicitly invoke the VersionGen target, `make VersionGen > install`. I fiddled with it for a while, but I couldn't get the install > process to invoke it automatically. > > Related, the older GNUmakefile method is not set up to generate version.h > and arch.h (especially considering both of those use *.cmake scripts), so > it's now pretty clearly deprecated. What is the solution? I am compiling ffmpeg with AviSynthPlus-3.5.1 and my configure just errored out with ERROR: avisynth/avisynth_c.h avisynth/avs/version.h not found Which makes sense because I don't have a version.h Do I have to use the latest git version of AviSynthPlus. Is there a fix coming for configure so that I can compile it as I did 2 days ago? Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmIMIu0ACgkQvgmFNJ1E 3QCIRBAAt2kUYvy3+rMfskOBLISsDQm0epV4/RYWROqfUfzdn7ZWyUbshEGzEfSP EuxYSgAXcvHhNYKhdgCLPFPTD5dqmxHR/9xYagelCEoEDY898DSOw0LFWyrBpak4 qvBtZP7Xt7bzFTvtoDAr+J4yrQCZN4M8gmQLhNqsh4nOawvmYlhONjXZ1eHX49Ki 9R3XFvm8jbdUqrvsil5+SNHtrf0734HYcZ5wcXNgulcfzdGDxvuGw1wS+XI9USQv lyyom9AjgQaKZK/Kv68pVY4wLpkpVyO0KPYrfv3isNctwP69bNupRMc1BKKAPnhT 48FfSwZpU5d3CETdIXve/oX7VyWtYvNxbhqDCexlQICQgZEoWWgmUncxhVrQkMbF e5N0mYhKTd2kJ3/31qaV/OfHqCznh2/BFzz3yeM+sH1NLj/bkAQQtCQ0I4jlW2jc 3sDxhtGmLtLXen1hnvAQLsEreT+jnlilhs1kTV8j4zZZ0rZexn7q6MFGMCR8Bmsb 7YZv0gY/1evuIvcjeviuPU9eYtbKqIeWqhIg+cRvmAJkqu1f2As0jl34Uuvw2agX JdpfQ+x4R16wXlOYKTVu8hiX9l4pNvmeeNxUFLQSFs+Vz+bPVW9me4VCbVzbV+Dc MwjxnhEOnarIcozsslvJLrQIwXnN+98RSpZJFmwRAM56w6QvZ1A= =mifW -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] configure error: pkg not found even though it is available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2022-01-26 03:00, Gyan Doshi wrote: > Might there be a stale header in an cflags path with earlier precedence? Argh, why haven't I thought of that. It was way too late for me yesterday and apparently I couldn't think straight anymore. Sorry for the noise. Yes, there was an old header file in the folder above. Sometimes I wish that "make install" would take care of such things. Once again, I am sorry. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHxsSoACgkQvgmFNJ1E 3QDc/Q/+KeXHbDzKEJGPvjSZvKmsnZWHdPYcNdD5N54E79SOeR98memswXTdUYuZ f1jXNGaJ9BR2RJXahOcOW9XOfOdAZcI+f79RvIuI9lnOpfmt5y6popPMBZuovgzh 3D+h7X6oTFj6J8VtdSGgnc4MQ1Po0KPeqUYwUCsv3/Nef6DDSi3hW5sQIF/K0dyv gAVwyrcGLW9VQqNxiPLT5CUcqElXMJnBDsRBoY8+BUt/l9CCjRMkdsIxXmP+gjvd t5COmf7UlYeMyOy5EdFltdl/rBX22320NTLrcK3pbIY9kc16b7yVJiVVviaKQxnT 6zGmQiaxm9e88wH35/DJbI9UK9KNRneG+FOVeLByYIhF9HAltPKdGNNstSAABiIS 9ljQ6W2sz1GWXj6W7FGxt6kEEnoWQ6gQ92B4h6Y4oN/4cY4bSBEX2PHRMPTP2Xto +FN5pPl2goFjznvZlcyJT0+MHdCSL3YoDqMP6EyiUD/JstqQL7gxWBKckkMoTs+7 PA0jfkGkyE5JZF9oGZi9ghqVfofws0K+mh3uIMulqrQv2thQ4OowyU8alF+yAI98 PKYPQmtb+o3k+iRpySlA/l8Pf5Sz+S03mrrskoPermOCPjagHSJhRjMHLrCFNWy5 pti6Whtx1TqbJQYlBTVV3nvoxtHc5dNCPs4bI9S9rk5bwxdmCUs= =a5F4 -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] configure error: pkg not found even though it is available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2022-01-26 02:36, Gyan Doshi wrote: > Confirm that /Users/Shared/ffmpeg/sw/include/libvmaf has current header > which declares vmaf_init() Yes, the header file exists in the directory and the function vmaf_init() is declared. The vmaf version commit hash is aa1dd0b3. I compiled this version right before ffmpeg and all libvmaf files have the correct timestamp (todays). I can only say that the compile run worked a few days ago. Cheers, K. C. P.S.: Heading to bed. Will be up in 5-6 hours. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHw/wUACgkQvgmFNJ1E 3QAJ+g/+KD2+s5BMjr3UkZL+qkBqt7wV5DpZ84U3q9DvO1UnBlUnTKh5FT+3Zu6t CY13bcQimYtRB9TPGvJ95mTUSMlNIOK4wTCEqumlfwuy5Me7fTZfnv34gNLDSucd izJL6CG/G6om9prROgVQFMsEizunEFBJnWmSxq+GZsj0VOm0HKHYLmMik0VZmt4N tnVF5uX2NXZGG9he028KUgw3bIj0+v70lewzSPYwcbn+NVK5V3dV4pGK8l76HwMR 1VOOnB9qUdEbZ3+1kEESJ0X9YqbF26Yv/8xb2L/2NW6v4adQUAr97ARuPuMFglMF jdBLJR3jOgOJ+HNezQy0ml0L/Xc7sHxCVhbgmg0CoLIsNQIFmjyt7Nv2zHhK/USy Kxp7iddH3K62emQbLx68CLthBJMYJJqcPPZ7ujA5JS3Yuaatqq4JehcBI6mxwlzm 7moE8XzG6M8HQJsQCDAIt/a7IvguiAp/Gm7P9u6n9idgUlUmZxn2Sr7HejCn5unY ZB5sx/uVnyyIAEHVNFgDUNKHv6aWzov02s87PjHGdM3THLJpyZZ9zJumvzXw5Xsn USLQ/4FTZumNBWbDmHzyFjwaTC/yXjWNCtUmKJyQOMD2m0lJUHOfvlWMWR++yfTp 1SNfEeoApW5ZSkxLdCm55BzQ0uGtpbP1QfeA9tyQTRPZBxXbrxI= =s28/ -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] configure error: pkg not found even though it is available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
I compile the static binaries for macOS and just got a configure error:
ERROR: libvmaf >= 2.0.0 not found using pkg-config
The file looks as follows:
$ cat libvmaf.pc
prefix=/Users/Shared/ffmpeg/sw
libdir=${prefix}/lib
includedir=${prefix}/include
Name: libvmaf
Description: VMAF, Video Multimethod Assessment Fusion
Version: 2.3.0
Libs: -L${libdir} -lvmaf -lm
Cflags: -I${includedir} -I${includedir}/libvmaf
And the library also exists in the lib directory.
The full config.log is here: https://evermeet.cx/pub/tmp/config.log
This commit broke it: 3d29724c00
Cheers,
K. C.
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHw94cACgkQvgmFNJ1E
3QBHOxAAsb5hqhnHZb9pGAaln+DywL/YgnCUsvpgMGIqHPdi6aa2/ivcuuuXtVjv
Bi0+JevJ8FkDcNGjhjy0bz1zeV1iVqkRTk+rpGgHI1v9XlTCVE/Jxtx9//F8J8cj
fpVFSp13Dy2LCDGLC5CNHhAMKJ8hamFskF0D0W47E1ICW8nGa/1F4Dm8RHKnvMiz
OodBHuWl3aejojQSrNDh1jYDi11pFIscSCQviiZWghYFjswPnRCIy93PfWUcKOZD
06GhLJv2QXCXJmKbrc2i/fupdw0jUF0bdAYLWBxR29pBd+ug0Ler0StZslp2Jnc2
kwmqcioO8HCokC4p1CjhWrPVKjpgXmJ1ZHhHcNJFTnOFQKmNeVgOGU2jLaaaTrIb
+KWXUsgF9c1HR4IX2Uy/BWbDDpsGHvbdDkmq0ZOTE80h1IiQNttN7Z3fL4wj26ys
RqPT69DlvIC/Z6F9vt5uTIg+Y5hLWDOShVVZ44ZEJ/1DPfOBvWHZMzPROeSSKWXd
eG3TkWpQ5TcZD80Pdh/IM0GtHCUFWJMbW/aZXpZ3enrmcxlOl4+hfJ7kFnDXGyuT
be7sTmx+BnrvxDha6xrsU+Ami0NI9B/UfBDMM9Diqn9tmtusPu3SqTRc94ln5O6F
zuTeEd8gYtvZ5XYkiFGIcum/kN3WxLGUWxIdybPWQCnp6qRzBvo=
=eINl
-END PGP SIGNATURE-
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2021-12-20 20:39, Ridley Combs wrote: > Try this (replacing all previous patches): > https://gist.github.com/2b1ea91330a748740d608680b0f8abd2 This worked splendidly. All good with this patch. If you want to test the binary on 10.9 or 10.10, here you go: https://evermeet.cx/pub/tmp/ffmpeg.zip I will most likely delete this zip file in a week or so. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHBPHMACgkQvgmFNJ1E 3QDJzg//YtZzziC8XmQT+kn5XF+q7ql58p84QO0kc61m3s2uqZiS0PZzfCdbmGI2 lfgbzXVHD44TZ29puuUnKlqZTRNRp6HieV1jAGhPSWRSSpDZEDaWiefQHVYSmSAg +UR9n81btjWV/7EZdvoLVcBGeowUnM2U4/XAQ33OuiBwgY4aRtAFRI2wM3UFt+JF 04CXeemQMoTI0UsgMFN5NJZ4ygob92cKaj0e4Q5t+vfvfD7ArJswi8yLfIGq/j28 Ap+I1a2xK6k6baoPSNT60W0T87g6oHjndESzp7wurYd1xbjlRmKgVBnvkEZcW3JR cs4e76v+WmiQLh/fw0qmcpy0ALBs4WeqwjtlBhfYxKk7QwRPQZ0mhYAGkHV8ScgI 6gbZY+FZEJhGGR/PH+kmZJspuvpLtviMAMX913nExDXdqQzrKidpWIY4bX2zpVg1 GgKAsug6kFTI5pTLYKub3iTQnWcRiXoazAlmXJn/ZksiGRJHfJqpMf6e9+vVqyYb tKi4E6vjoxSIqttAngaDskqrw58yzuDcg+TUsZMBCHJK4cIhVWvaIZ/C6ZqAnTvw QeiknYH7LLMe6JRN+zonemg6qk/lOzvVYlYXb9FN9+GhXpYafJAunqKZUwUiHdt6 OAby2YEu3APXlkmCJnLujuJuzPku6hWukk7OXAKjd50YjGIi1Pw= =tKI6 -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2021-12-20 20:20, Aman Karmani wrote:
> Once we figure out why some computers are using the wrong metal binary,
> then we can fix it and commit the fix to master as well.
With the 2 patches from Ridley and your configure patch I run into the
following error now:
OBJCC libavfilter/metal/utils.o
HOSTLD ffbuild/bin2c
xcrun --sdk macosx metal libavfilter/metal/vf_yadif_videotoolbox.metal -o
libavfilter/metal/vf_yadif_videotoolbox.metal.air
CC libavfilter/motion_estimation.o
CC libavfilter/pthread.o
CC libavfilter/qp_table.o
CC libavfilter/scale_eval.o
CC libavfilter/scene_sad.o
CC libavfilter/setpts.o
CC libavfilter/settb.o
CC libavfilter/split.o
CC libavfilter/src_movie.o
CC libavfilter/transform.o
CC libavfilter/trim.o
CC libavfilter/vaf_spectrumsynth.o
libavfilter/metal/utils.m:33:21: warning: instance method '-supportsFamily:'
not found (return type defaults to 'id') [-Wobjc-method-access]
if ([device supportsFamily:MTLGPUFamilyCommon3]) {
^~
libavfilter/metal/utils.m:33:36: error: use of undeclared identifier
'MTLGPUFamilyCommon3'
if ([device supportsFamily:MTLGPUFamilyCommon3]) {
^
1 warning and 1 error generated.
CC libavfilter/vf_addroi.o
make: *** [libavfilter/metal/utils.o] Error 1
make: *** Waiting for unfinished jobs
rm libavfilter/metal/vf_yadif_videotoolbox.metal.air
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHBL3wACgkQvgmFNJ1E
3QBZ5BAApVGHkKD8ZtnnvqOFY9vPAHUdTtSOPPRu/U7bb/16k+rhz9gW7gPyzVbw
eObR2D5z66I7h2ePmNWbHP+i4cIqRfFlcOS+9eWHy0E5G8y0Lx55xncGFZV5wkhI
7OEe0EOo4GE6D6Ro/XwtOnnsy7cuHIt4oX0xT7rlTiITYYdoe+M2zF9nAVJtjUit
hKX3YHBBfryLRjUvQGQAwWR+EjKRT/LPNwhwf2WgxtSP1BGFH5+oROkq2CAdLUO1
7zFb2GkyS7atVYjysQ8QT0aW7ohTlxBpEaak69GhSEkvarZGWplsC8Z3BVZ58qXP
K0VH/fIF7lDMQqTmHkPw0lEz1bMBoqzEUevKVC7h3nFl+GhXPhM9lS3sR/SeBj0U
YBmeHTdcYJPoh9bD4PiU4X4AmMUaAn4+J2nUn6TmmqI952yZVWv9ZKWVPLhyjiTH
qHqtvc3gK4hYo7JhhIP8sJpNiW2OPSUBLEboXQ67YTI6cp30uJI0c0KdRCvkBhNS
zs19mdfaSOseG4vFSgsD0rOGUWprgU8SRf/9EM88WLF8cBEs/bUxRBcalq41RrwB
bB1D2orQoLLYlcdc1B40Wl+X38GcU4Jv3mFbpF5XhnjrwCg6QMx5BS8p8Zt77jov
IzZHnlqaqLrB66iN17UK5nGiBb1st19xyGEwSXctkzOIcOFOjhc=
=4Pni
-END PGP SIGNATURE-
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2021-12-20 19:11, Christopher Degawa wrote: > So I've exported "LIBRARY_PATH" to I'm sorry to say, this is a workaround but hardly a solution. Before these 2 commits all worked perfectly. Now it doesn't. Tweaking the build env is not a solution. Next time someone commits something, are we supposed to tweak it again? Where does it end? - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHBJ/EACgkQvgmFNJ1E 3QDsJg//WzTdNngpbNhCihB0foMLjtL687/1FWqZKPfsCx5pvvLZq/Xj8cd1G2G5 XJOehG1YYkjKXE+I1oWBrRxxQ/1mkW49DjX6jyzGUFPvEV+e0yf6f6TUPrE9IYDw nFkIq25rjJMo/+IPxklHw1bIuZxoqo4ohgYHfmcyYJWOPDBXRWCd93GJkbWJy3Cv fRRp4/gIeQJJzlld1ISqGLP6GDIwrevtW7oUwUZbwIWvnJyl25UdnHLAMl82fQPu QnCEuWgRODXI1eaYNXf15MwD6gGy39n7njon4AJ5C63678Yc2H0FfVh6wI9lIv1e LR6WY942ziQx8uqr3y/2IV5wGDSvLZqyEvCMSh199xTcJdfL4WNEZlNS8hlWxN51 TfLHBLpjJHqEq2i6+hyaYF4Y3M9ctRa/JVjv1EjciXFWzMx2Ddhehxv0TPu1tY0A UxiQ0By0hJhZDDzOPxez9DgCs/ecmIcUxq4mKuk6KXLIBfJqFrNIN/Mzsn7hBOI7 EPLui0+Jo+cWB3AsDRIGNO9UwN+gZAGKxGHt9U9//Af5rzzY0TQ09Z+To14BxD0V lTqDp69JlsutJIpQfOywkPb5ExaFgX7vYZmXEb1f05zlIScIeBRdPxKJ9Sip2Cyo AVzTsQIDTGkNM3KUJE8m3EgrX8V+gJOXKtfK+phUr5YvyhP5IpE= =maKQ -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2021-12-20 19:38, Aman Karmani wrote: > Could you share the output of `xcrun metal -v` $ xcrun metal -v Apple LLVM version 902.9 (metalfe-902.9.61) Target: air64-apple-darwin18.7.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain /usr/metal/ios/bin - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHBJUsACgkQvgmFNJ1E 3QC1ABAAmoeEXNt0/GKbKI2dc6VXiRugw7B6HoCf13BD3cemZ3FYZSeOwBGEOOi3 FfPWivhvbY1KvDl2nFX/hTrNWHuKUX1XEF7W4cmTyIcDxqwP7jKMShCWzo8wgEpE DUj7ExdQbQlIYEL+1OitRinuuxR2bLkk5tOIHnDAqlTSq3Qp+WyBwNzuDTyJtPHH uHBZV8dFpIwpUBfyEA5zZzOWIZpDoEzZZ1HWijktME/AVV0EaYVwTB8LiYELCL5w zMcHfGt6Ujy1MglTnjJnzeoi9LciHw6+AFd+jsWwvYdGxe47XbN+EBN/XK/A5VAm Gxw9NVNt+CIyoFN2Mk4nDxwpFzlerM9oZy1LpFOQ9teQB9xpdlhrQRvB72B1+IMM j1Yot1qGY53CFeEi4k4Q/ng8rDPilxcYA4MYk85I3r27hr7l1V7+4mh6WWdklPEj GZmQZwkjzlFHgehz3XkJfKvjQ8uMI8IA/hWSMsiSav8S1UUafwvpSPIx1qce6yc4 SLFkb52C0QobesSH0PlR2UclyuapTp9+vBOnznNmW0oIWrD2nLG38ijQBMhp3E5C 2DuXUhhTpgM4GmphaVptwG5U2VNbqE1/zh6shXV15TAfSJCYp5O9ediUbgCDM8RA MshlAoAZE3T42pnh28DQpuxoXTDrvWtXOEsTZOHvopdRFEQO/y4= =ZwX1 -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2021-12-20 19:06, Ridley Combs wrote:
> Try with this as well:
> https://gist.github.com/499380d8ea03a86fc89eb48803ff7b2e
Getting closer...
CC libavfilter/generate_wave_table.o
CC libavfilter/graphdump.o
CC libavfilter/graphparser.o
CC libavfilter/lavfutils.o
CC libavfilter/lswsutils.o
OBJCC libavfilter/metal/utils.o
HOSTLD ffbuild/bin2c
xcrun metal libavfilter/metal/vf_yadif_videotoolbox.metal -o
libavfilter/metal/vf_yadif_videotoolbox.metal.air
CC libavfilter/motion_estimation.o
CC libavfilter/pthread.o
CC libavfilter/qp_table.o
CC libavfilter/scale_eval.o
CC libavfilter/scene_sad.o
LLVM ERROR: Error opening
'/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchai
n/usr/metal/ios/bin/../lib/clang/902.9/lib/darwin/libmetal_rt_osx_air1.8.a':
No such file or directory!
metal: error: metallib command failed with exit code 1 (use -v to see
invocation)
make: *** [libavfilter/metal/vf_yadif_videotoolbox.metal.air] Error 1
make: *** Waiting for unfinished jobs
libavfilter/metal/utils.m:33:21: warning: instance method '-supportsFamily:'
not found (return type defaults to 'id') [-Wobjc-method-access]
if ([device supportsFamily:MTLGPUFamilyCommon3]) {
^~
libavfilter/metal/utils.m:33:36: error: use of undeclared identifier
'MTLGPUFamilyCommon3'
if ([device supportsFamily:MTLGPUFamilyCommon3]) {
^
1 warning and 1 error generated.
make: *** [libavfilter/metal/utils.o] Error 1
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHBHDAACgkQvgmFNJ1E
3QB1JA//bYQtbCqvB7/o0+W6VoUMiXi3XAV5OdP1sFwZg0ILSh+ARBfzPGhoFgPe
CLwKQ93+K0bmzICFgFaXjVRoVOvHyDR07/nMNc0nnXWjrIL59hRioJbx/AKFXMzs
EjXKwTfXiySI3L+8s2z/m3UQAaNbzdGcWBZgWsFVKeD/Lwl8W8ziGQvY3VeyNd2j
FXjCG9X3hN5rw8uXUFHx/xMDu6gNQa+0FMQaTdsWw5AmHmvVW/Xmg5p+h155PTHJ
UoYFtZ/RF36/i0HrA9IomppJj6Mpgy27z8YdAGn3AupWABxb+uraMHIODgq0OJVL
zgZFYCDtNT9ujxe4EF8s7MKQMCUUK8kP4NVka0miE4keCp8TjdLZzpP+HHcEqh1P
xENKjaF0D3RhrRdfu53miE4NCj0KyaWTALwC3mg7R+yPhqVaxqTm0ADYGmUruP2d
+8qzkhctRpmnoFvy+Ar07924py0kcLX4retDiw+qel5H3KjLi5HtNkycgpDx1KGN
cHtxqUm8xC6NA6vVw0xNmfz0aSWe/ANJ5HepqBbdqzr4YH5ykKGWr65ynVxRh/gP
muc/EG77T+UoXN9cRmXVqSLRNh0I+IxtqvSZFFDHTWSLJPGpq9MjlKGj7gTLOZpU
Qp0X5Q+E9zU0URXaLOktN+QPbTL7uUHTOddGkzjwyl+rg5Qkp9Q=
=Wsah
-END PGP SIGNATURE-
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks for the rwply.
On 2021-12-20 18:25, Ridley Combs wrote:
> Could you try with this patch and let me know if it works for you then?
> https://gist.github.com/7362df8a689c41b9174ac50fdeda3e43
I've applied your patch and get the following now:
CC libavfilter/scale_eval.o
CC libavfilter/scene_sad.o
libavfilter/metal/vf_yadif_videotoolbox.metal:47:1: error: constant sampler
must be declared constexpr
const sampler s(coord::pixel);
^
constexpr
libavfilter/metal/vf_yadif_videotoolbox.metal:122:14: error: use of
undeclared identifier 'max3'
T diff = max3(tdiff0, tdiff1, tdiff2);
^
libavfilter/metal/vf_yadif_videotoolbox.metal:152:9: note: in instantiation
of function template specialization 'temporal_predictor' requested here
temporal_predictor(A.x, B.x, C.x, D.x, E.x, F.x,
^
libavfilter/metal/vf_yadif_videotoolbox.metal:125:18: error: use of
undeclared identifier 'max3'
T maxi = max3(p2 - p3, p2 - p1, min(p0 - p1, p4 - p3));
^
libavfilter/metal/vf_yadif_videotoolbox.metal:126:18: error: use of
undeclared identifier 'min3'
T mini = min3(p2 - p3, p2 - p1, max(p0 - p1, p4 - p3));
^
libavfilter/metal/vf_yadif_videotoolbox.metal:217:12: error: no matching
function for call to 'temporal_predictor'
return temporal_predictor(A, B, C, D, E, F, G, H, I, J, K, L,
^~
libavfilter/metal/vf_yadif_videotoolbox.metal:233:16: note: in instantiation
of function template specialization 'yadif_compute_temporal'
requested here
return yadif_compute_temporal(cur, prev, cur, next, next,
spatial_pred, params.skip_spatial_check, pos);
^
libavfilter/metal/vf_yadif_videotoolbox.metal:265:23: note: in instantiation
of function template specialization 'yadif' requested here
pred = float2(yadif(dst, prev, cur, next, params, pos));
^
libavfilter/metal/vf_yadif_videotoolbox.metal:108:3: note: candidate
template ignored: substitution failure [with T = float]
T temporal_predictor(T A, T B, T C, T D, T E, T F,
^
5 errors generated.
make: *** [libavfilter/metal/vf_yadif_videotoolbox.metal.air] Error 1
make: *** Waiting for unfinished jobs
libavfilter/metal/utils.m:33:21: warning: instance method '-supportsFamily:'
not found (return type defaults to 'id') [-Wobjc-method-access]
if ([device supportsFamily:MTLGPUFamilyCommon3]) {
^~
libavfilter/metal/utils.m:33:36: error: use of undeclared identifier
'MTLGPUFamilyCommon3'
if ([device supportsFamily:MTLGPUFamilyCommon3]) {
^
1 warning and 1 error generated.
make: *** [libavfilter/metal/utils.o] Error 1
Error compiling ffmpeg...
> If you can test actual deployment on a 10.9 or 10.10 system that'd be
> great.
Unfortunately I don't have a 10.9 or 10.10 system. I compile on macOS 1.14
with export MACOSX_DEPLOYMENT_TARGET=10.9
Cheers,
K. C.
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHBFpsACgkQvgmFNJ1E
3QDapA//WmxnoAqIGCqliaSIUpRkL/KxhSpj9ULJzL1h9yw6Ls0DIYT39Pa66hTk
IABKgLiTNxe1hNTC9kbXf6HdNqJw7KGGUlCGu777RHhh7wySq355g7b89f1wrSJa
1RwCkb9EoyC/DzeSnayDk6oOO7duJxCibkdTXEsYW9VgA9QGSriTHIRSG666UgXO
NC6EyjiOfGqlVkTr9Ott+r2t30H/0faihttbIhLwV6y/Dd/vx4mdG4y61B0PXLX1
rAQwDP9GYkAa302XLeLSTTJ/IHzsV7xD1eE+I3QcB63gbzKlujfbSBiOf9Czv6Vs
M1xoRbcqYkTi7zK45t7w+FuAMn/her/P5cCjmXbEQIHBZEfX3r2MKtkdIAhHsUPl
vDvR7Zmi90gRorQnyQ1fy/LaIcZt6E6CFPKQrIVkBsOnIuXvnrx4fxsvo4rYO32p
goyhtmBMyg9zIZy4eSUn/3M5NKMifgSQrYdUIIKrJZr4ENesKTGB/EZXS30v5VF4
7GrObWDT1oR+VoUiMSYrGPSBlF8R/NHJGU/BL7iVFtF7CfFRnHmfgzyII8RlS6G+
V5stD8eKNr/8fzI3sjQfiROEMtLFKJz4Zkf6qmBT7zeDizNJp/xaGc2egsC7LMzX
or7vCtN6YKPXhQimhsrxDvIXLdvt2ZsCwcbNpq5ZzEMi8mDgwCs=
=DJOy
-END PGP SIGNATURE-
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, The following 2 commits break the build with a deployment target of 10.9 on macOS. I agree that 10.9 is quite old, but the rest of the code worked perfectly fine, so were those 2 commits really necessary? * 4ac869ca2a | 2021-12-18 11:57:31 -0800 | avfilter: add vf_yadif_videotoolbox (Aman Karmani) * ecee6af8bd | 2021-12-18 11:55:47 -0800 | avfilter: add metal utilities (Aman Karmani) Can you make that code conditional? The error messages I get during the compile run are: In file included from libavfilter/metal/utils.m:20: ./libavfilter/metal/utils.h:25:43: error: 'MTLDevice' is only available on macOS 10.11 or newer [-Werror,-Wunguarded-availability] void ff_metal_compute_encoder_dispatch(id device, ^ /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/ Metal.framework/Headers/MTLCaptureScope.h:14:11: note: 'MTLDevice' has been marked as being introduced in macOS 10.11 here, but the deployment target is macOS 10.9.0 @protocol MTLDevice; ^ ./libavfilter/metal/utils.h:25:6: note: annotate 'ff_metal_compute_encoder_dispatch' with an availability attribute to silence this warning void ff_metal_compute_encoder_dispatch(id device, ^ ./libavfilter/metal/utils.h:26:43: error: 'MTLComputePipelineState' is only available on macOS 10.11 or newer [-Werror,-Wunguarded-availability] id pipeline, ^ /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/ Metal.framework/Headers/MTLArgumentEncoder.h:17:11: note: 'MTLComputePipelineState' has been marked as being introduced in macOS 10.11 here, but the deployment target is macOS 10.9. 0 @protocol MTLComputePipelineState; ^ [snip - way too many messages to paste them all] Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHA9hIACgkQvgmFNJ1E 3QB0aw//Wsns6KOrT2vlw3RWIyAS1dIrVHO3bBM7NAwl0lYbHkKM6wQpE5sVsSdq tjAxWH+XikERU2jnHCCZqUormA40iei+WFXKAbZOgrobvrKMeXe/uuQaAmOL3Gkn o5jvf1+v/Oh3Wd9rSYqdPu+b7VWyz0qj5y8jgBxPtrapfIBh35HBt/41JbVln/PY d3+h+siAHuBUk1jLHTVep0qe5o3q+mB6m0As9bpGBoQD8oPhQvJxBMqzzzos3mOx bgVA36NowZEiH8YpEXBMaHk8Ek6k1/37kexinvlRBCmk59mfACShfBJc8J0EC+ii BVMF6OQvoQ3mHXT79fcd5xV7dueXzLGNAbaK+FQ7ZvAjQ2aEh7xVghH5I8hgRUKT 8JS1RS6e817+IsSlxFA0UvZ6waF/HINfUXpL0Ca4hFirFKSHRxaMIF/49EPgLk4g mK/NSvNVIbEN6tpz0Kt0t3cvVEp0O5AoKPAwEuCTWa8io13hgHxlOX0TFMS+3d2A CRuqROxEpAcOjYo92wWa/S1VFl4lDNBcxHnszA9sLRai7QTdxKmojoU+ti8PqTJa iDoMVIiH4psyzMMqod7kas06w+KSnr7IyW3bKE50atUBY0P9BCqH1e7/mZ+gn0JM ZSb61Lo9k0aYbHG7rTtXR4Wvtiao9NFCbD8NbHWPfrSRgs9jqP4= =/fRX -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] compile errors ffmpeg git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey James, On 2021-04-25 16:32, James Almer wrote: > Does the attached patch fix this for you? Yes, thanks. The patch works! Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmCF17oACgkQvgmFNJ1E 3QDbtQ/+PO0LUeMWQm5y8qXQjyO2pILRW2/pkkj6J1/gYLE4XZfWr+NDXMT4GiT8 Bkt8w9IXaPjWM+wD+ZDjGEczpeBsI1T02L5jgVgq1opDjhhWNs3ZhOD7mt6RwDmO LlCKyQVnPVBtQH+BaHo9wNaQhAnhHN2JGrPz20xMJxmhAvrzHI6YHTXH0AhVqmuW Jx8KuYUyG8QKAfE9S+Jo301vC7M2LAPQclHTeplkZq2WJgX4Ujh5x5FZVjBo41A/ jTfkWiyYYEQNdh+k+FjmTuTbjHSIDKYxMcOHw+gdxk3aY1LTXLG5ANo4nj/eFsRX HpoFgrQspvKs+HVBhj3qWlzV7x+cC/G9Cc2GxPskCiFXKxB05Jd1uFBxRioJWBmm GsAbz0Vq2GbN/kjMH4KBAp9lbgNj4jBH10ZjwJ1pcaIK8uvPliSFqYhDJpJyxl65 TQQOEJaey5JJRPBsB4tlSb4GM1zyFAcYILIIvFbbxSk7stDH0fO+0rKypVHvGxF1 m9Vo3sLQEZ2sGR9gH4mNsCq86JYf1W0TgMihKL105k2wAvoV9CUgpqXGkaMtkhg2 A9A48p05OsiWBHi+VSDTthST3D3TB9kFDl//AykyIXmvoitgFOkL3Wl2krlvBHxb VcTGLkmkDoRVtbk00j0xBO/d25MCgLqZsG5+s73z8JJuMm9B2Nk= =jkL1 -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] compile errors ffmpeg git
`FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_512_float' not defined libavutil/x86/tx_float.asm:1047: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_512_float' not defined libavutil/x86/tx_float.asm:1048: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_1024_float' not defined libavutil/x86/tx_float.asm:1082: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_1024_float' not defined libavutil/x86/tx_float.asm:1083: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_2048_float' not defined libavutil/x86/tx_float.asm:1103: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:861: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_2048_float' not defined libavutil/x86/tx_float.asm:1103: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:862: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_4096_float' not defined libavutil/x86/tx_float.asm:1104: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:861: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_4096_float' not defined libavutil/x86/tx_float.asm:1104: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:862: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_8192_float' not defined libavutil/x86/tx_float.asm:1105: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:861: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_8192_float' not defined libavutil/x86/tx_float.asm:1105: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:862: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_16384_float' not defined libavutil/x86/tx_float.asm:1106: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:861: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_16384_float' not defined libavutil/x86/tx_float.asm:1106: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:862: ... from macro `FFT_SPLIT_RADIX_DEF' defined here MAN doc/ffmpeg-protocols.1 libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_32768_float' not defined libavutil/x86/tx_float.asm:1107: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:861: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_32768_float' not defined libavutil/x86/tx_float.asm:1107: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:862: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_65536_float' not defined libavutil/x86/tx_float.asm:1108: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:861: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_65536_float' not defined libavutil/x86/tx_float.asm:1108: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:862: ... from macro `FFT_SPLIT_RADIX_DEF' defined here MAN doc/ffmpeg-devices.1 libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_131072_float' not defined libavutil/x86/tx_float.asm:1109: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:861: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_131072_float' not defined libavutil/x86/tx_float.asm:1109: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/tx_float.asm:862: ... from macro `FFT_SPLIT_RADIX_DEF' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_64_float' not defined libavutil/x86/tx_float.asm:1163: ... from macro `FFT_SPLIT_RADIX_FN' defined here libavutil/x86/x86util.asm:1341: ... from macro `movaps' defined here libavutil/x86/x86util.asm:1325: ... from macro `RUN_AVX_INSTR' defined here libavutil/x86/tx_float.asm:1212: error: symbol `ff_cos_64_float' not defined libavutil/x86/tx_float.asm:1164: ... from macro `FFT_SPLIT_RADIX_FN' defined here make: *** [libavutil/x86/tx_float.o] Error 1 make: *** Waiting for unfinished jobs STRIP libavcodec/x86/vp9itxfm.o - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE
[FFmpeg-devel] git server issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just got the following error, even though I can ping source.ffmpeg.org: Unexpected error: fatal: unable to connect to source.ffmpeg.org: source.ffmpeg.org[0: 213.36.253.5]: errno=Network is unreachable error: Could not fetch origin Any ideas? Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmBU9loACgkQvgmFNJ1E 3QBZaw/8DaTtxUiaBbJKL18i4bcmwTTOhHxDmawUbgnssHXAloDrhKbvWr+g5+yn zc7ZFcqWVJlSSpoPPIrbLn6AhKCvKSPIdreYRyMY5ST0PounQAQmH90mn+VQTpxT zLCsiaplWDMMrnZUCNOHu1GMiFW624aIAy7ynBoiwvC+d2lFlr+dYgPeYn4SUHAC /AecBFOFYR5jmpBLpN7Up75GYfBI+IYD4O5VnxwYT2cz43o/0SMM4ypIuv/BQDAw x3fQCvn9/OkQsFmH89NS8N4B02mgZ62/KIN+I55mt0lSYGFkabQi1KOG4PNoqFjn z2mpkGG0IGialA0kCe4m03soyF1i8zFgB3GHTB4daYlQnTa+hZXS7u+3D7rAMDBY my86F+t5y0dLjpRFyDQ38Pl4zwB/bUfnZa6OmYj/kgVXP183cbF3QLvOEFrV9tLN gWUEkTjUzcpEdjC7EF4XYr3AqaQVy8AOUrQvYr40+I92X69jdW5FqZTnObBiSTBP 0EjyJ9bOPh3IM7S+TYspnZffOik//xj+Z14ljJabiRRtqPxfHWWZAND4sdD52wsQ B33zgrI+ZOPb1P53kM5BPXYjHPp9a0XUwN/dsHFN1z46SI4vz2gWuHYB71ULGAyb kmka61OZseS9V4gv0MMwpgDNaggkfOBmY5JsKyjfAJupmxAWT9E= =Jjr0 -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] ERROR: avisynth/avisynth_c.h not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2020-04-05 20:02, Marton Balint wrote: > The headers got removed because the ffmpeg source tree is no place for > third party library headers. I get that and it makes sense. > Yes, avisynth was an exception, not anymore. I also get that, but the commit message should have mentioned that. > Actually with the change it got documented that you need to install the > headers. > > https://www.ffmpeg.org/general.html#AviSynth Thanks for the info. Yet again, I would have expected something in the commit message. I ususally don't care, but this commit broke the build process. > Sometimes you have to follow up on your compile scripts to be able to > build the newest ffmpeg. Considering that how easy avisynth upstream made > it to install the headers, I am sure this is only a small nuisance. I can't tell you how often I had to change the script to compile ffmpeg. It's not a problem, but when I run into a compile issue, I check what the problem was. "header missing" pointed me to commit 0c75acb4ce (compat/avisynth: remove avisynth headers), yet there was nothing in the commit message. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAl6LsEgACgkQvgmFNJ1E 3QDCig//Q5lesp0lIsZShjH6p72V9D/cgY9v9bg+wS0Io7N5xORkeLpnXd981xyF 2E09MYt/GGyzoOcn6IQoHhCkB/5nY7/Ly+Lz4iEbhCiOel5FApnts9rswLI5mQKX l0OOA6Y/mxu1oJ0QIAZSWneOVsPQ/1zy7aFjnWOTNoGBmE/jd4OrDkisiY75zChX yX19mARcvMJFXGXxCtUcLj3PX95P9/CUDV3wQgWgF+H7nVA60uFw1DTirUeOdPRm llUU1wDFRp1oxaCDNxjwPwlQUCp041HMNFtpIQzfXpcKmli5f6FmmIceHyIl0WER ELKM/3N1YNCOEvjWp2MTWvaeWA/RdDswSBUJCJEc1evoTXcUUd8naTkyPbwBnpd5 lbu1lziq6uLHMQ+NF9mjf//yYQJA+z64++Xt/Gd9DFm0nLsqxdZIEemINrhYtxDQ qnXE5urS7FyhDj7CL5S+DSTaLcEKW6K7Jmny3PEVhfg8iiYJDMZAClfJOzMIh+Iq p6mFgGYSbk1JOq71utduqsKy7sPqny63T5vSCDbF9oNAqAIjGIfwJChxpqg9JuTB 4uCnhud/iLQ94V94tYQVHBx2sJpSvcT4U7G4ZSYX+FpK4afbm0pZz0+qGJALpbCl K8ZJaha0lPgj7Rc86W4oKI/HKyWSB5e9vUuH+h3CadN5ExA6G4M= =LCWn -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] ERROR: avisynth/avisynth_c.h not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2020-04-05 18:57, Marton Balint wrote: > Well, do you have the headers installed? No, because they were always part of ffmpeg. You can't just remove stuff without proper documentation. I have been compiing the macOS binaries for 8 years now and this is a joke. Someone breaks ffmpeg from one compile run to the next and you want to put the blame on me? Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAl6KafoACgkQvgmFNJ1E 3QCF+A/+Nj2Qd2ywBzJ0HFZhF6tW/YZK0rw5T+9jne9++LrBE3ZZzIHKu3WU2uuf 3wWR8iXFrpzsvjAvEanAt9MEZIDUf0L4dOLV+0yOMqxw0dWOBrU+p0osKPliuTqV rEHb+lsm2NyrXyxQBJyinsU3woW7hbwZ02Ja4VaQLBiEBfQmfzZcI+LfhDsmozTf v3zo5Lslcd4LCDvkn6AtJ11BWjKAZs2Y8zIa+3tcw723nL9jwr0CtddB/O/zg3do SNuKl3oALfwUJ8SJCcjf9ORvHsVhaMPK390IKAEsAGC1FBfT1uGWvAGgHK2ncHjA CmVSF/rjiO6JAMSXKyZZ/Nh8XowAHnHb/YUJFJUHwu4RHph4SNi/8jPHPgFnLzBt j1btyazGyT2qo+51Fmjc7sVscARbZhnWXuQBpOH5xYMkbrflJpnaCQyX1EkMifA/ IrRMfDYL9udQSwxo5MAitKNliUh+6v3vW8vQmP0FK5LCMs4nU4QLoAbcTRTGCYUe Ih+NhGNBYMhT/W2L6A/mSiAWNggNEm1S7SbnHlAwXat6HmP4fluIMBShpAvKcC3n 7To2dmHUC/UWZyp2IXhb39reHQ3IurGYfVCaBMccj5C1WQhZMyY5jeityrTftDsg /iJcgpp+9Yy9vX9Q/fUJ/eCIspg/UdHb8heboGnRd5dZlNTsAIc= =rFtl -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] ERROR: avisynth/avisynth_c.h not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ffmpeg now throws an error during configure: ERROR: avisynth/avisynth_c.h not found I'm pretty sure it has something to do with removing the headers in commit 0c75acb4ce. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAl6KUjIACgkQvgmFNJ1E 3QCixg//Z7WbwQDPPliNJDehY3OxdQkeePHVtZ4R/FbBgwu3la36GdOMZ8cbnw/g 2NoKYZy0fcVeM0GTsSVKNV/DSm8DD5hSmKbY6K8h2xpRfvg9UjRHGfKvPPpXgHvb FgvJqsEaKGOs5YVgya8qyfeNGnXa0dxc80oTCoNbUkNCkdLOTnwqVC6FSUbcWhqy zzt4zIHlW5oS/5UBO68o4SHTBpmnCXQjOEbkEDiLwwNKTP/NlDeYgYbnf5AXvsBx +7DEUgapdPGwCossA7mgqy+mUWOXBBrShIpfh5C180822zQd1GehIsOAExKpIVwS M7VPH+HMGL9upe8Nnf8+FI5k2EDjTnRfWumEczd3PGVSVeloMUrf7kuvQZ+mVTe1 /adqHdJp/6le0q4KYcthTBpaFHtNP3ifKLsLvC9Xp/qaWldnKQugVY5+MWjCe2uN LsWHmHSqIO2nAF2WXX6FT3UqZj9875cQu7qBn5CmxWpSV4TrESZ3eRFSxJjX9KuR ctQ6091pB4pMOTQ33D/WEDrSHudTQ/soMPg14CazwHIqQ/I/BUXQK2AtUW62lTIM SFWnX5Gp/3xEZDWeEZxlzSdj7J+WZaHTFfyFargFDBh8Phf/PrvDASCy2EqxowYF KQvH5CngQl2RisqthrM6gafnMC+iKwqeEZd+6QZ6LF8i0vlMnnE= =OVJd -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] ffmpeg dylibs for OSX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2019-02-27 08:12, Patrick Cusack wrote: > Does anyone have any experience building ffmpeg dylibs for Xcode? I > want to include ffmpeg shared libraries in my macOS binary bundle > for easy distribution. I think you have to be a bit more specific. What dylibs? Are you talking about the ffmpeg internal ones? libavcodec libavutil libpostproc libswresample libswscale libavformat libavdevice libavfilter What about 3rd party libs? Also, it might not be that easy to use dynamic libs in a bundle, since you might have to change the rpath after the fact. But vlc and/or Handbrake use ffmpeg libs in their products. I suggest you ask them how they do it. IMO, it's rather a PAIN. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlx22f4ACgkQvgmFNJ1E 3QA9wBAAl7SbD0HcNuOXP7QZkLHxeP+KVb0ABRUkPAkudfa7EHr4jC2rNlK3NziB XIvrtXs0FKPgqbI9EttfvMJvSBJTywzELGlORpUTy2mxAPPCMImiwZ9D8Ei31HdQ ri3SWxfooKlSJe9OHK2vnx3bb9opRasDVn+EL+UJCiHWG8gMGPkQsSPH/NEGfszr ubOkGo7D5fCLKBpNI8+zI+SoW8zqY2c2qtBlRFiTmQ8/f/7dDigzP3zByAZj8me6 WfIB3ZqCoZrHx+eV54QfWL3nCdjIuEewi7y311/W7+ctR6wB2YA8eaCDMu62Rfyf 0aGj72Bp63n9Uoyg9Nogahlq/KBRZrjbvVNV4R6EJH/ScSLN1rlPAViEB7eVPlwQ uJ78g4+NIfyBK5cR5rPjLK0d+U1qWn0JiTWTlQWU6Qf7gT8Z0g4jeudHVIinDnT+ 5VddAnsYaiYxI5k3iqBmv46u2boVWgmKbRi4mFmIcaC6Z4HmQ4cHJdQxcXPiiWHD Rj8WMHLJ4zEpFcm7QgPMNRLcI6EKyeS0rRIAsQC3CJTCu0z4aORbnzXEo9i9SBbU T8lWK+eleorg7IeUkIW7R2UT7MzOfYmJ61m49fgGDgcPajoL8abTkb6upjXDp8rw Pvn+IGqDkKT/wrCsPICKq50FHmoRI4R16XU8TWKT9tZ/BiIfTqU= =hoxw -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2019-02-06 21:41, Werner Robitza wrote: > Please let me know your thoughts. I'd like to know why people always think that brew is the best way to get ports. Have you looked into MacPorts? No issues with ffmpeg there. If something should be missing, ping the maintainer, and/or create a PR. Done. Anyhow, I don't think that adding a formula to the ffmpeg src tree is the right approach. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlxbVN8ACgkQvgmFNJ1E 3QCBBQ//WERtTLEDSAgTOdTWC5Xcx77hmbD4BaFiabhbQklxN+CIHnLpuk5NP1vo GWEod9s7kxv8+iZyAySpsHf70iVeH8vJNGT13KZvIwk3C3QSS9z9w6RgVRr84oog Ox9l7EqUu1FWlG1HNiWmjTm2p+zzLSzp7lEk69L7g8itJ+8AXDd0xtLryXhRDMWB zFzqtrrYNVOOrt8TasJXMSTvpzwiYfZqB4lTxjyJWdfe08ip06SLOxJx4Lx3275J KeLnWHdeaUAyp7tOYjB71xBcZgVqZf1GDYMX9Hm4Ll04QNbOYWf0C/MHeEa2g2jV y8ZOams44UQRhoiJLp7dfw7XotSt3AsU4AHQ+FozpuoUxk0QW3WPbwir542cN/11 IxV/AqzI3BkekZ+vp7SZYUG3feTBQW2jlAq9GxrC2LxTNw7cnao67VSZIbm+ihWN pU2J7aZyyKEmRuIviP8Wb3Zf9JtRyUF67jrtMrX3lSGZYoSve7B5tvpnrCfyjzzK yFI462X+xTYYB2yiruHCY5UOVkGTO85Wq3+GGmj9UZcoymRnE5DC19P7vUUcenCk AONCJiaeVSbpiFHw8QGmJSewUUJ9Cwj0CeKVUlvs0vyScVdKTOG2645fw/W+mwyR FhYFGckxyv7a1N2lUqaQz6vSTm87VBUsHc5qDMsyE99iMGF6+nE= =rdZu -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] delogo filter: new "uglarm" interpolation mode added
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-12-30 08:02, Nicolas George wrote: >> +double d = pow(sqrt(x * x * aspect * aspect + y >> * y), exponent); > pow(sqrt(x * x * aspect2 + y * y), exponent / 2); > There seems to be a mistake. You are taking the square root twice. Or am I missing something here? Cheers, K. C. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlwozUAACgkQvgmFNJ1E 3QBvzw/+I6NXL7R+ugiDAmqUxUPwzvv/yJ+Vkbbp7Pl/XGApTol1Odee1P6QYs2t e0Rs93w66+GjPZIMk7dWzl7EdX2GfUl+xPkdGzFOjLvw12nenEf8EoSXuld2Ggx8 b7algcvHeUp1orG3/c98TAjUe2zLwN2oEfHq59v5lShwK9KeThtNOsxQjz08iKfx 41SNqHKYtuz5wo2Ez7BKHZ0iBPrRr4EBJ2BPINbvAUPsELfhblUtGFFX0pumRAaJ skLoPpaJuW3W1uK1/j0DpCNvHQzqrU0rM4hecBT8FaC0jQk6Kbi5RfS3u7xs8Gbq snvPrRUF3UEpp1BILWWPOfG+pnytvOoKdK3j0cv74ImTYBpO7mniUKl9IZbmN1rK 2AbDI/1EH0Vgt44koqOL1hn9/zEZRbnfNrLO4rp9J/SH8+AX1a17Ts7XP/K/G88M +pVq0u11B0/DnwrmnP11W+h6PT2ab6MNm+f57isu047j3ug9f56XvxZh56MDRzBg RXuFqj/qu8p7tymdXfcQOzFQfQQp6pJearzd/pKImfyI/ay1cyT8XjnGKr+VC3NV olT9lEQ13Qb7XBG/ASg6VlDuxyJqY4VRGNVx89/P3ApE406lNRpzgnK8G6XWvTQV swN8f1qxwARqiimhN2iSPCCYDu0svt0DOwymSVUPXhDZNDGqYOQ= =HEMW -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Install from Source on CentOS 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-12-28 19:21, Moritz Barsnick wrote: > x265 messed it up, with a commit created 15 days ago: > http://ffmpeg.org/pipermail/ffmpeg-user/2018-December/042609.html Hmm, ok. It must have been authored 15 days ago, but commited after Dec 24th. Anyway, thanks for the info. I believe to remember that x265 broke pretty much the same thing several months ago. > AFAIU, fate doesn't use external libraries. (Not even just build > tests, apparently.) I see. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlwnYpwACgkQvgmFNJ1E 3QCOHg/9GXfeSGOND0f4xg45yP9jrn8MLWEKqCK68i4mAtvtLbJyXFY7xSV08L8Y A6+xDJSPvAoRLX/fHGGNQ24DQwLJogpHPAg2ktlMvcGaJP1qh5sHD5aOw/eSsWi4 H5QBmCkCQ1ZTVCBxVfvEWbzQCLF6cpx0OoAX+zl0i9yUcgbV+4JwNmu4C5Pa4rwt E3QkFmQ8J8cizvWdPUyNjjUN7k5oV8mOssOfledzHTGbZtMrQ+KaaNLrBP72If73 u1c75piDggxn7/sJLMzLsrspwyqkTl5wj9fBbV7iQtToBfI3CxGec8CktSj/8P+2 2S1o/AlA1xbnFkmYujNTd3/Tk0WtJ/f+PQ615YlJZtQAfDt3FvbPdHfGZF2cMtOm 7gTjCbyoEkk2CFXxkq/iFoYSQ/3FphiHiC4AjuOwVWPaET+BmHweQmU9Vu2F2TIm jnaJBjnuCzxmNGMTrhhiCJvT7UPbFgo84sGtwhwoPED/0CMVfa06fr2CrHakYqAm g6MqcxPzev0C1940aLBgk7+sVzsCIkjYe1PHge9jEjtanGzRMQOeyjXhWGaVccQD hR/QniittRkIMnJmISM0+na6ap6E7qJ31waMN80ATb5t46U9QvzQ/6gXIzVhDJCB +7xQVdYsNxxy980qBQruQjeFwj0pyKEsM31NAQTfQ1ZZQn4Ux4Y= =7Ohr -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Install from Source on CentOS 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > You'd need to post your whole config.log (pastebin) likely. > > However, this list is for development of FFmpeg itself, and this > question should be on the user mailing list, or #ffmpeg on > FreeNode, where you'll likely get better answers. I'd usually agree, but I'm building the binaries for macOS and I'm running into the same issue. Either the latest x265 broke something or a change in ffmpeg's configure messed things up. What I don't understand is that you didn't run into the same problem with fate. The last successful build I had was Dec 24th: ffmpeg 92795-gcdbf8847ea x265 20181217-1f44f1f1623d 2.9+16-1f44f1f1623d So something between then and now screwed things up. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlwmtxUACgkQvgmFNJ1E 3QDHLQ/7BK1EDTPotGqn+7LQODL2TSmDGq8mQf7emx5ckG42R5Kpb0G84eZ5Ns6a Mii8oQ/tovX/kRtFjd4+H17xIUA2u7e+kXc/yNSHC51jFhE5F8QxfuU/3T2wfSIt nLbPx68t5LARPqUdaldWUJ3r7kL/wyctNaeqYfZrMuhhzRm5BCRnKJC1mLgNCB+e 8628iMdCCeucZwj1Eb3bK+Y4YgoxalEHHjnqSnrAxlxuWO2WdlIbD1z5gfTMJ8s7 bDsKVmKKdgy27lI4JU0vRZ5Q1d2GaPqicVRij7L3XjYr0OC6Yn2Oe9h9mYZCBLfp Z3f/wxUMOSQI4CwA2yd97ZV1fcs82B28StAvdaixTDWxecWyjF89dMC2mYqmpIFu SFqrtzEZdrWnFgNljSkvkd4t2evLCIS+A5l9b01sXVxN7RyqFv0kThs+bHll/cH9 jYXm/bVYn1hUuAp73xsKlHlNWjRcCgTQQSqVAKxAU6NP2PeIRogf/NpU8M7hACuo mds/OIFPNUMTnul58pvT59xTnrQV96aULDvbm+lTvskP93T/x4VDjs2yrYJ3q4tH 45J0a2x6eCmU2yVKLK/6wf2NwciBCDxItBIwqRPZ5m/8creDlfF46dHspE/q2wqd mR0YmeWr5ouOigFSnXi0EZk/eZwbqMPrUc+87LGm9Gt3gdHCHAs= =G6TL -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH V5 0/2] Add libsvt HEVC encoder wrapper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-12-22 23:35, Carl Eugen Hoyos wrote: >> API will be stable, from my understandings, but not soon. > > If this is correct - I have no idea - the patch should be sent > again once the api is believed to be stable. In that case I'm wondering why libaom has a wrapper in ffmpeg. Just a few days ago they broke the wrapper. What about dav1d? Yes, developers said it shouldn't be used yet, but ffmpeg still has a wrapper that had to be changed several times already. I don't have a proplem that this has happened, but telling someone that an API has to be stable while there are clearly 3rd party libs, which APIs are not stable, in ffmpeg is rather a joke - not to say slightly inconsistent. Cheers, K. C. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlwfmKsACgkQvgmFNJ1E 3QD7axAAuE1BN6AD205taTQE81wDbxiAVZwewQcPf/45TU/FnlUHKcU/CUnEgM0H wcyvbMSXjjJfVEHrUzHUohOKlQTwVwGyKDvSwaGTU4cjkPFjO4/ZTzlYHPU6QlvN vFgv70SG1kVNQ7UwxZD5Jd2jbnUCmxwiKRq7jkjf3RpK9/yC4i0X1SF51n7JwliI BFHuTSYSEQ/XY66bdnQEJq6McA75wY4Z8s+zWTF+69qN5vrDfZt5/fhZG6L0ttpR ViCiNGB9CG/aPBS2s2C6oOHBx7bfSCdj5QPrIB80YeifUvTXXJpGJ0gHBosljisW yoDR259FcEh/c4ApN0DV7bwptOuILyJI5wTntbT2b8YZxdjyoX3shUTeixtRHnhA fRemFIcOXa5pU0aaTJUxtaBsAcmla58qowmU+mujPYakg/XAVoxDVG3lqIt9/Dkj d8Q+sheuH3z9HemRAG6ddnDhneqQmarcUEma/vVzZKTcWBfW4MXzdR2UWoLS+XhP 6u4C0/uCSOUlqI8dN+FAD9JZODN/Bm/+ybI7A8eLTuzlb6U1Mqwy44pzkgn70YrZ vZ6aEzfyKE9NPpYCkKwHkitRrQtM0jqgN6Ew/tT2xOpqiq0Y8vXV8cbiYxvsMVks PCme8HEZ8X0/j/pP5KeapXotbSfK+nQpe7gOOVCbH6d/H83ooCo= =66Eo -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] libavcodec/libaomenc: fix breakage from upstream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-12-19 17:28, James Almer wrote: > This will break compilation with libaom 1.0.0 because it wasn't > typedefed before this change. You will need to use an #ifdef > UENUM1BYTE check or similar to choose one line or the other. Yep, an ifdef on UENUM1BYTE should work. > Sigh, they keep making breaking changes like it's all internal > headers. Hmm, one would assume that Google understood the concept of semantic versioning. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlwafGAACgkQvgmFNJ1E 3QCW2xAAjmlVUjfOWxfpeFPzkng8CInnFwESB09o7ujiBRMSsDuA+zCiRvuJYdau bjXnrLP7PTFmhrTym4p8Lr29KqfQnLBHi1utj7+JyANr6x7xr907C6r0caMY2+K7 OBGhdUib6XCaTt+o2sqEASJ9k3nzVLQJrMc/wizCkQjjTk7iWeXdJdbnjII2YPpC y1lz5YDA5ViY0tm1gJTzKjbS8/4XX+WjSpsCzKQAxvGCpGvK4BoPLVrHvihigjWV 0HOqPEHP+efaLxhADyvoK/VcOCUL0LWUicmQTKgn5n1bqb3M6JYFPCDx5Ukpc1fd +5L9mcvOWaVv/vFAd5FcolOu/kvs7a0oUedNvhY1BxdpRIcGhXgeG2OLJWojny3l QFMcoBW1E+m7McAdhRnFD6ziMWXBjO5/vO2SALM+dpll861S4PmbpakosNPPspgy CibAeoMFgmziA5qDvdTfNhy8fYBA5sF7GEg6PZ+LcVEOlxTZu4xqCfZf3AQeVhpw 9eq3xFOqszysxjVAOrVQ8IzOMvFdswB98dyiE4mmD3eo5GDQaYPNbu+iUYKCm4DA nIAFJFU5/Zgjf1wREzt0yz6DPUuaOct9uvRzwG/xbW37Zk09R3qXrPhCbXe9rV3C YuZHohVhUuUWvbnw6mEsH7PsWJzEDNhduSk7AZlopAJQ9hLSMuk= =OYCw -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH] libavcodec/libaomenc: fix breakage from upstream
commit
https://aomedia.googlesource.com/aom/+/4667aa1a373566e9c124afcd58c71731ab0d7377
changed parts of the code that broke compilation of libavcodec/libaomenc.c
---
libavcodec/libaomenc.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/libavcodec/libaomenc.c b/libavcodec/libaomenc.c
index 09ef423ce1..faec61cacd 100644
--- a/libavcodec/libaomenc.c
+++ b/libavcodec/libaomenc.c
@@ -195,7 +195,12 @@ static av_cold void free_frame_list(struct FrameListData
*list)
}
static av_cold int codecctl_int(AVCodecContext *avctx,
-enum aome_enc_control_id id, int val)
+#ifdef UENUM1BYTE
+aome_enc_control_id id,
+#else
+enum aome_enc_control_id id,
+#endif
+int val)
{
AOMContext *ctx = avctx->priv_data;
char buf[80];
@@ -291,7 +296,7 @@ static int set_pix_fmt(AVCodecContext *avctx,
aom_codec_caps_t codec_caps,
static void set_color_range(AVCodecContext *avctx)
{
-enum aom_color_range aom_cr;
+aom_color_range_t aom_cr;
switch (avctx->color_range) {
case AVCOL_RANGE_UNSPECIFIED:
case AVCOL_RANGE_MPEG: aom_cr = AOM_CR_STUDIO_RANGE; break;
--
2.20.0
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH] libavcodec/libaomenc: fix breakage from upstream
commit
https://aomedia.googlesource.com/aom/+/4667aa1a373566e9c124afcd58c71731ab0d7377
changed parts of the code that broke compilation of libavcodec/libaomenc.c
---
libavcodec/libaomenc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/libaomenc.c b/libavcodec/libaomenc.c
index 09ef423ce1..6d1955f9cc 100644
--- a/libavcodec/libaomenc.c
+++ b/libavcodec/libaomenc.c
@@ -195,7 +195,7 @@ static av_cold void free_frame_list(struct FrameListData
*list)
}
static av_cold int codecctl_int(AVCodecContext *avctx,
-enum aome_enc_control_id id, int val)
+aome_enc_control_id id, int val)
{
AOMContext *ctx = avctx->priv_data;
char buf[80];
@@ -291,7 +291,7 @@ static int set_pix_fmt(AVCodecContext *avctx,
aom_codec_caps_t codec_caps,
static void set_color_range(AVCodecContext *avctx)
{
-enum aom_color_range aom_cr;
+aom_color_range_t aom_cr;
switch (avctx->color_range) {
case AVCOL_RANGE_UNSPECIFIED:
case AVCOL_RANGE_MPEG: aom_cr = AOM_CR_STUDIO_RANGE; break;
--
2.20.0
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] build inconsitencies on macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-11-22 23:37, James Almer wrote: > when checking for Apple frameworks like AudioToolbox, > AVFoundation, VideoToolbox and more, so configure is evidently not > enabling them. > > What these errors mean or if they are consequence of a configure > change or some system/environment update in your Mac, i can't say. Hmm, this is really weird. Not quite sure why this is happening all of a sudden. But you gave me a great pointer. I was only looking for "toolbox" in the log file, thus I haven't seen these errors. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlv3pykACgkQvgmFNJ1E 3QCK4A/8C36KfnhtyDDdp9TyWfc0GPjg/6F+NL609rgA1Kz7ZpcPKKH9Bm4y6bBU xmCTxAnDoqyNoBOjzVxGZlUX4UhqXfTFlVzriftks+UktevAGRAh1/rBlNpYUj5t JJRdKQfWZg9tMiavOki961PelWitG1MrRfuphUyitpf2bmF/x7fyURmXQ1aB344h cA9nluN2f5QdqyzP8nJMJ6FYxlQg/IT9UZWbxmTcR3KdRWJ5XXFkR3fdHv0kWNPx zqNJLCxHb205hekyhnBYOejFTWo3J7PPL/12F/KUj8Hd7iBaF3hMbhNRgogKXljr AEtpS6cdGMk15bzwDiGQVfDx6IUVRFuJXFyttntCSG4JM44Q2B+MyOHvtO0mJjR3 LO70wh7TQHVMduYEiz5EztW/oqIgzJ46TS+Me5IHN3HoIHSzio5J7x6AnCtM0C1W E28NO/ZBAkM07x60/XlcncxA24UgHPYTUw3L1JzOfvC66IEW4OQ3L7A3D+IbyQ05 Z5mPaVtx1yBe73BO9XbRZS2vvf3+TZP42vNO4EZcQ9qAglCXS9GKe4WX/hF09Bem 3H6y+Nq6re5YqDaz9ghWkPMBpZvfSnt93yp3Kjrzr6ZJ6O4O/oUD6XotL8ONa+Es LZNIYCs1RHBd+RCBJtnxAepbXqntuRefYFKLKiNVWC8KjInqEQg= =fBZQ -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] build inconsitencies on macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I'm doing the ffmpeg binaries for macOS, but I've noticed something very strange today after my build: Several libraries (AVFoundation, CoreVideo, CoreGraphics, QuartzCore, AudioToolbox, VideoToolbox) are no longer linked (even though videotoolbox and audiotoolbox are found during configure). my config.log is here: https://evermeet.cx/pub/tmp/config.log ./ffmpeg: /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate (compatibility version 1.0.0, current version 4.0.0) /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1454.93.0) /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 58286.70.9) My last binary 92486-g8f875a90c4 looked like this : ./ffmpeg: /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.0) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1454.93.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4) /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation (compatibility version 1.0.0, current version 2.0.0) /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo (compatibility version 1.2.0, current version 1.5.0) /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics (compatibility version 64.0.0, current version 1161.21.0) /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate (compatibility version 1.0.0, current version 4.0.0) /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.0.1, current version 5.0.0) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1561.60.100) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1454.93.0) /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 58286.70.9) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox (compatibility version 1.0.0, current version 492.0.0) /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 822.37.0) /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0) I'm really puzzled as to why this is happening. Did someone change the configure script? Also, all of a sudden /usr/lib/libobjc is no longer linked either. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlv3gj8ACgkQvgmFNJ1E 3QBuARAAgqZAYG0G+qU6NDVwns0Cn2QWERAtEzVkcaZTWaIzSyW45y30zw3wou/g XuOLcHiDwe5U+7Ju1sltjqAWAMBZb0/5dyUWAXN/auK1daJvBsQdRrtyBMrddCBw d2b2R+JXgypcGheCQL1U2wwj+Ew0p88pYD7Xog8XNeuIILq14eH95ymYsBXF35fq EWrpYjLkGEmt5MudjxSNbtQNZ60wNtIQrlKAT2fbPFzgRcZRedqmAIAWG7hudq96 DpWCbDoTG8oMyZ4c+ef1yP+rCYqwh+d62Vl76xrWTnB3I70W74C7WDTGEVkEQEA0 Ucaa9ZxgPYptteLCog4rqi7nr+kniHzTXe0FR5ECczYFfwBB5ksMNi95wU+VXn43 BzuB5jSDA7R3Raf5L6prnfVou2niLOUZUB88J8Vivv+q/2yIL/CUKReEK5pMD9ga y00VjSW+S/W/Ezkz9qQn+2036qioHAPK8K6vFbx9u0M/GNy12/qpPLrd9tW93x/M kb+SbjI4PZPDJJe3l2ioUEaHT5aQZ90k4klwJy6fjk9zZKP5YF9nTsdFTBF6v5/B o5CZXgKqM5tX4PNwbYgCquY3Q8wO+G7wt7z4mW4ZyS9KyscsdqKwr2X8CNQ3wo1q jC5MuXe2QmKlfmwjWIiGCtGVdjKPEZwwxupI9SPkp5EH5fPodQ8= =q50f -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] FFmpeg 4.0.3 fails to compile
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-11-02 23:23, James Almer wrote: > Since libaom still hasn't tagged a release with that define > removed, it's not reason enough to rush a new point release for the > 4.0 branch. That's fine. I just wanted to mention it. I guess in the days to come a few people will be running into this issue. At least they will find this thread... Cheers. K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlvdG0wACgkQvgmFNJ1E 3QCpqRAAnlfJh46iTGqig4DNoSP6X6JyzgC0mmFyiHxmyO/OaSaCjF5Ji1cc0pE8 ryTk3cdlYOI201my8Duh3KVXBcNc1ABZfo08FxzwilUV+w3vvS5+ffqbqQ3JO/wd jSswFehA1jclacs9Y0LmD8VXJdjHiONdD1+a5Uz0OjNRX33yZakCbJiNyRXPWgsX FepLPrUHpIFmEddRU5BHXMPPVUj1XtAHus3eODIcWdS3g202/BDHSGqTsXBqU0dS UAytYS5hTYVXj1djJEMdBOal0UaTkaXoXYCOiMJLFWp5cAhj6xK4PdNQncLwgzDE 0EIsD2177+yrSLeAxv090omzR0vONI2XxZObns4agTHAGcULRKQ+2YrqHya6iRsN WVHyMwdUNZWA4rTGM38hY5RJHePNF7SwbBsQG7EdeQtNvS7tH4xfB0+EwOvEXm8j +gHASItYceqxf9y4jb3iCV135sDv75sHfucqPDXZLVGGt5BiGzQfC4IHAbA97PTm T1bNLKi75eaET3fcygFGvyfRvNLWp2bm2id8C1CW3Hcah/zCGo9SBsadBzyTjNC4 H+eOnfSjBn2buNywLAQK9Gske1MCeApsTBTEccVxUo7485ZXWzX4Vi44Zp2KJDx8 KKMr5AZIgIbxY3Ad5cZeY8DCiUR74z009clY12n4HnapHtGzP7c= =QR4d -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] FFmpeg 4.0.3 fails to compile
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Unfortunately FFmpeg 4.0.3 does not compile with libaom. error: use of undeclared identifier 'AOM_ERROR_RESILIENT_PARTITIONS' It seems that http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=b69ea742ab23ad74b2ae2772764743642212a139 has not been applied. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlvdEnEACgkQvgmFNJ1E 3QDsNQ//YzVYy/eYUuZy54OBzba6RaSIdoR6MZcTxVX4t31SUz4e6NoN7BHsCyOc VZzcf5QnLf4aCp+mPds7Rus3Ni6n6KiJ3WzYEMrY/XF0qoTyFI6qFWpovKYTBt+7 KpBYLUwFu1+pD0b19VkqC/cp2lOi4xvtTzC4tK2uiPhjspq9OFPgkAo4CcZxDPYH hWqyvB4LfTyNzUJCEeolsE2tXaKJh+yQ+7A1LhVECCTmfHQBkO/WwdLuHrmiXvr6 q5ZLxeb79/XvbqI6JUltSr8srDlrP/qI4j20QFxzOe1VYMZPJs+bgeLHsp8VbZvQ ga8Baq3PaVMxKUvJqzsL8lT43mWTiyzzl2vYAJLuM0lUYU6dclPcmP6X7iNOafVy uflF65LKWkXj0HKEgmheajqmRwjM2Q1LyetcQUjXHYHAjazAQBYFp8b6TQ3dUAex s37NSmiD4+Fiubq5SxMpthvOxf8l4rIqSD85cuKvXBNINQlqD1fUmpObjxmdXZw9 gjlBEAYLyleFyTBA0mdj1IzIylIdC1PtZCBuuFw6x/85a31Q4HtEU8XmOjV+Mf5n E0auv+ltbqbAuHd699FlOOo+sONWVCNqMo2vtRVYdqpa+BnPW+JIOVDM7KMJmCtF 9nuytQksRSbVbLTYigTG9vqImWLuddVbMJ8ZaOIs4V5lTDrAfHQ= =iMwf -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] download: change OS X to macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've changed the commit message as James suggested. Do I have to do anything else to get someone to commit it? Cheers, K. C. On 2018-10-15 22:11, Helmut K. C. Tessarek wrote: > --- src/download | 2 +- 1 file changed, 1 insertion(+), 1 > deletion(-) - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlvGg04ACgkQvgmFNJ1E 3QAZiQ/8CdPcEvLDvFyns8cY0mkDZ6Wfy7HzfSHsXoBNnuyT/yAkoabfagDMl/Eh 6z99/m0/+QQlYcYNyHRFf7ONT1mEQINcjl3GVtmybDX6AYBhh6RREVkC9poZ+npB lsTp76fVDqfjENylvUw++QUdck3a3PTCwDqYEFabibMd5aFh87sCKCiRqwvD7YOK 6AQ3TCYMgpWXU1HkaQEWVsAo4BFOvLK7jDdKTO2DAcqnEEdOlb6Q9gisPmjDyH1p g3DvYmsk2MEb88vjEh7DNbrvMxWTTCCx6V9JFGPbWbRwgsfX6cqJFkywMGJ4Gylt /7qWeg+YMEe/f1oHR789JSeuGYS/Rbf0gYxA4BVzEM8KDqyoDNB1L7zgX+VcuYIT /vjgdqy0xVqG77AAVIIK8Ok6Gxd89i1j3e7fKEklBgvC0ez8Y7vXmBXRY/7ybLcp nzXSehvLBAq+lR3gn5p+ANMD+JKCWndsQREX6LEWinyd6GvCt6jGFgCuzwPV8HlM uGoI4l0px8f0aEl6Jf5B/B2vobTQoUr86R9UoexURSjnbLd1X+9viy9W6eQLrAqS gxc/wCGGv+L2y2hy89TWN413rygGR4B+FI+FizOQuRlwv1BDF224BsRhHusNRqIw QrrwmXPDJOPRSy0rcdgZ+ri9KPX2tdzUs/iItH28L4P8OlNBAgE= =06v5 -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] doc: change OS X to macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-10-15 14:27, James Almer wrote: > It's fine, but maybe instead of "doc" use "download" for the > commit message since that's the page you're updating. Thanks for the reply. Shall I send the patch again with a different commit message? The reason why I chose 'doc' was because it was a change to the documentation. I figured that's more than enough. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlvE3wMACgkQvgmFNJ1E 3QC4rQ/9EfKyod+UmK76IMAvf+l4yqGQ9fcUsinUNprBjZYZu2N3jFwFHnhDL6ak 1rfbvyP3VZ06lH7lwY4FH5aYkmLkdbrnJYGmiNM1CjjIqtlf6viHLspO9nv3XkI7 PHAZY1McTH1pFsQA/UNvEev9OYV0JhykJhUKCtAVTO7xDPnqKBtNRTGdtKXrNZMF zkNQk1TZSR8/DvqYqRbeMneoEnhCIz11wmGp0NcOlAR+EwCaOUs3xEDSbXAauqf5 Bt27D9oGJXD4tzXYKjGl5GfQ8HmJ2KihtGhyYoBKoGFMtrG0dH7XBxBsA1GDo2mn XaVja8r2uqOJMcLRdiOoX3A345m+9kX+ZiEkNNun8cDkvGP6pBKtw9ho1y4Of+wj J9iMFYww1vdjYNE7j1sf4QPWgO44mrMtb1lVKvxaPG59WCA4lFkL8dQj21myZF3Y /ShKOODCqlWx6ZKa2++8gH4faWg1Q5hqDbcL3vizQejPG81SjRU5+uan2ryphUjz hHp5skdbW3MLlOW8TQCgoBz4BbAFoAraeqC/KwQZ+W7pHpr9lPAAAc8o1bletRno deDRqMGAiS7iA4RZrvgOLWxdr3HAkup029/kqkOPaOtJBuo5ZUv3ydzRNlsN1FPf uWqkGqc9q5qM3SglnJwWIL87iRPAJxge+/6eIhrOhpKyTDxrFa0= =LkEN -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] doc: change OS X to macOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just a quick question. Did I do everything right with the patch submission? I haven't subitted anything for a very long time here, so I hope the procedure hasn't changed. Cheers, K. C. On 2018-10-15 00:49, Helmut K. C. Tessarek wrote: > --- src/download | 2 +- 1 file changed, 1 insertion(+), 1 > deletion(-) - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlvEwU0ACgkQvgmFNJ1E 3QAuSw//cuCYPdE2GaVTEMObtDlRG6F2f0o2iox/vV2X42bXNy/4mIwchO8neSMb Nb9rS8zyr1ahpeObSVRzqmZ6pD7coDITWWm0MZlJKJbOFB4XrwrtqW1zWOtVFxRu MWH13Gkt3K1cUHWT0O9yQWkmd03K24NmA4vsuAuqC2Tm89DuZimvMRc6nAiwmIGE /+EaruEC6+16YOR6Sujl84WnCWa1ET6D9ZOszPN6noURmmiKLJA7xY9w/0A+PI3W jfeEza6qIhRTBQOyCOlrn9RNTgYQCyaBRFaVtpNVd890l0w3vPUHW9eYx/h4gNVz 2YvwUpg3sL7Itcxa4S1GvihU/7/0DNq8M497FqLYoBcKeyhQwzTGzsmII0tdUuta 0ayBVkDHw6VQudP/h9cuRW4PRPSRQwo4Mff/1VRhXNIbpMyIJt8kQtmaAk3eVDa/ j/0Vo6c+AzExujmKa+olSXr1G+HwbKJUhoSP/khRbBVFR368OfP15kFodEpIvSSU 6T6v9IaV6W2kCXa2J7gMAmVMtvH1B6Bp+nU6URhLzb1qwv13og0yyq1YKZq09BSj Ggn5LLND3Nmu0zhrB4pJaifAg719JHADCRkr7unZ7Nfv8NXPBRFJl+Ri1ngRqu4F UA0ARANfZlhKsQqy8CgMedl5/9OUeVnkAlPQdcCBbFB2m4l+/Gg= =jDTi -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH] doc: change OS X to macOS
--- src/download | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/download b/src/download index 0bda5a0..40f4706 100644 --- a/src/download +++ b/src/download @@ -95,7 +95,7 @@ https://evermeet.cx/ffmpeg/;> -Static builds for OS X Intel 64-bit +Static builds for macOS 64-bit https://ffmpeg.zeranoe.com/builds/;> Static and shared builds for macOS 64-bit -- 2.19.0 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 3/3] configure: speedup x2-x8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-08-25 17:15, Michael Niedermayer wrote: > patches 1-3 work here fine on linux x86-64 / 32, arm, mips, > wine+mingw32/64 Any chance you (or anyone who's commit access to the repo) could commit these 3 patches asap? Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAluDKzIACgkQvgmFNJ1E 3QDy3w//Xy2DQFyT5aQvFhadc+bmnuxMqYMIQy625rPbttPIid1q+oxUGTJPmtTu tNA8vP+mf11wUMbY4RFH94Te1ClRtYTiCoZgWSGm3gcHemiM2VfCE2SYuj1pAW/M BxJPmVK7pIy58dvX5DsyiRqLNA89OeV1eHsGfdJ+hpZ90OgvQtsatfj91SJO/Yfe DoStKl6LrvfcgAR2Y3mSCbWfBpnU8SwmMGra4YuN0OZH9TZDX1vtI1Ok+D1JgtHC H/64ha08C+56dwil55Zawugii8sAX24cwtxCLQ0CLgIdSFxHbIOiGZCBZFS0gIBL 8zV5GOONZEt0wXzFH1BWZvRra/mr828TEs3I/IbmFuXkAVpLLZpGcB9TTU6noScu ZKtn005CM2CynjZvm+4cQrLxzzex9XhL5miD8pY9EigKnMixeGP7PftmoCFV8maq uVlLfF1YEGAXLxW/br4PF6lA/QsSOkosqI8SxSBt/KzE12sgcE5cIWlqxUEBDsBd P57XAM6qCWFQec2lzcczS6BWL9qtrgQsT4A0Rs+FTGRppnjY3MKFRDKF/5d8ml3W R7jPfWlmPfR3XKPldivo3GTfNfny3u1HPidrDFjA5QW+0gheuVgyoSrVGjouj1H2 v0JKbDLp95Gg+GmolAyeXfHAqG2vK51/KwVwzUKEauDnxcPuDvE= =5wNw -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 3/3] configure: speedup x2-x8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-08-25 14:11, avih wrote: > For overview see: > http://ffmpeg.org/pipermail/ffmpeg-devel/2018-August/233665.html > > Attached is patch 3/3 which was at "main.patch" of that message. > > After the previous speedups, configure spent 20-60% of its runtime > at check_deps(). It's particularly slow with bash. After some > local optimizations - mainly avoid pushvar/popvar and abort early > in one notable case (empty deps), it's now x4-x25 faster. Patch 1-3 work fine on macOS. The configure time decreased by 75% on my machine. Awesome patch. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAluDAdwACgkQvgmFNJ1E 3QAYLg//T1ftuIcO9t5jLRKYYSi9mHQau0y0LlsNqvPyGk0ht+Wu04WumtsS/K0z aLAWTSX+vWShkwn/ncGCxZlrgUdXDfmc/y8jIGKXuHV/39ZhN5Y7CO11vNn/efdE XjWlXsdpadtyqnwtWdrmOmvufiVNhVxXbLAHETnT6afFNRDVxKWl4JboiU3kNVUX K7WTqvBBMqeSRIHhgRX/n40mNItp4vxk9WQGz8E+rcoipR5DIpokYb987aLzl0Y2 6gTFXY7HqCtY3oWJe70XuHY+/a/6z3Y6YD6i5o7QpYfyXJcbBz3PvzKJxdg/5W8S Q92780We9H61wXxf5cpoobJJcEIZ3/HTXE7O5zEWKrLrmNbGwV4wecBoWWaoHa9V 5lMkmC5yrx2b2WKoLG6sYTgq9h1UYSi3bNHTvuGKZ36mmgGz2Tx89ctr5hteakEB dreAmeLZGgI4g+PFjastnWGl9C+JmgUQwe0sTHNsKNqOyio0zQXgk+cpjuRNOx+X USD6hYp9sn6A0d8vh1Pgw3FnbWp2yc5NDmkwRIl/39icH19WJUtgHZKd1x40SHyV fPhLJKPaNmbdR4kSM/AMUUlVmthAD3nZyvPOdR/b94i/SsivRhWiiuk0L2lODOx0 mtNU8vJG1rcqLbNTQo0tkorH31CalzXnekInUrX5soeDZg8ywe8= =6p2H -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [GSoC] FFserver further development direction
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'm not an ffmpeg developer, but I do have experience in software engineering and ddesign. On 2018-04-24 17:33, Stephan Holljes wrote: > This arose partly out of the discussion that there is no way to get > a connected peer's address through the public API (as the > filedescriptor is hidden in private structs). How about adding this to the public API then? > Most people (including my mentor) spoke out in favor of utilizing > nginx. This makes no sense at all. So now people who are using Apache are supposed to use nginx to get a working ffserver implementation? - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlrfysgACgkQvgmFNJ1E 3QD99w//QVEGlbMgYPoFEkno/Qxcc3tgem4lAzBE6N7bp9SXZBGan1zbsQRA8FN9 0RSHVoiA99M5INIMsagXKym+evWqMFtKpJdQtiV7U30pY+s3WNZBFcYZMFej9fjz pcyiD34AjkZCLxCY4QjucW7GxKLVyY0QrWfdE5D9T7go21+CfuqWIn4U7aswojVo Ram7TYLAUb7ZngsgGIUM6Sm6fFyGUISdltaCd9Od2m0sPUH3d488ZN21xZ+nO6Xo VCiWzYAhEX87AgeYRkNKz5SbYGkGj+TQXupVqmYdvUrJ6BMxC/5bo+PTVaC1hkZa bGN50cosNUO85Es7eZQraqIY5u19UzHMJJfMkBDnUxmJ21EaF3Xd0dj5xXEJ9Etb qZiqfvzxbphbvny1yczqTbxyC5noHprXI4UKUfN4w8MfYggBbb5GSbAHyE+G6yUU dfrV17z3bxGOCH4mxJAQUzNwDTW2LMV1eyA2TuopsCDkHkL6WAbgLepfb4ixtdpK JA1pDyP2pfWsDSqR1tJ4bpW/72WoMT3ZL8M++947SuBlg9Wyit5y0m9klAnp9cPC M7415FcCgG3Zl/fVx/SqDsliWCcipqxGnmCMboAKkpAh4WPJG8OEqTohE7uK4EiZ ac28TsjJ2GT+B1t2IZVk0mtgtPcksOpXW3/bQHjZiI/Bid+a2y8= =3val -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/dashdec: Do not use memcpy() to copy a struct
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-04-21 17:23, wm4 wrote: > Just by the way, some have lamented that they think of it as > "doxing" when you post my real name on this list. I don't really care, if somebody is using a pseudonym or their real name. However, I have to say that if sombody is using not their real name, especially when their tone is often agressive and unfiltered, it rather begs the question why that is. Is that person afraid that an employer might come across some of this crap when doing research on a potential candidate? Is that person not confident enough to stand by their opinion. Seriously, what is it? Btw, I myself often use blunt comments, which are mostly seen and read as harsh, undiplomatic, and rude. I hate poltical correctness and love sarcasm. Non of these traits are a plus in public. People love sugar coating and talking around a problem, all in the name of diplomacy. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlrbs4MACgkQvgmFNJ1E 3QDEMA//SZNScbz+ngk0UU040cWdT6Tek83Dh5RhKwfTRzY7VlvTnsQTYG/ktJn8 2yiLUvMQWh+ENr+Kxe9MosFR7kDOkD4s/P199IkmQSC0Vdh0YwLNsaVamziAFjHP ZXbpn0v+PasU5raGbpJfQE0QXNAdDbRUORzEv4cz+8oZ3syTfGvSArkbVKsULrrX haOLbb/lb/qt2igduLBEa2Ir/3WYpMw5Ead11FH57828QKzCywtdS3ZYKf4PuBRT 3T1N1NI1P+9oMQC860TPa7xzFVBIl3kvsUh6J7QurG5UnuGR0AznAMRiDC+YoW9m 588ZX/Z5nlYFiW3VIDvwoErWWf/3EvcZrGAbqvOoAVFEnlQ2eKdSFEHrwkkhF8Zg St/O3ZEP+IzBzlr8stxVLxXSN81URHHlB4f3SLUtVZ45HHwR4WlMDk960SYwRzym 2mst91cS5fyEeCPkTvBkbhPQaVnYUBmYVqq1VN3v/9Y7W5DpKIxhIYBa4wXGSJ1I 2jaYXhxskNvbiiPogfRBWFZUvnx2oAMTUa0+3IXp05MlPh/1r1swv30KRyzRscjE pLQVJo6s97pM1sTvd2fBWJnWCPYm3/dZSqNHPZt8BjmRvotXOhD29zb6FPaYJCs9 nyKR78VZVC9vPycFdWiUQYG2dG7GMcxL5ruDvEyqkU5YL8zAYZ8= =WBwZ -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Building FFmpeg dylibs for OSX
On 2018-02-24 01:22, livinginlosange...@mac.com wrote: > I can successfully compile ffmpeg info lgpl compliant dylibs which I can link > to from /usr/local. I specify /usr/local during my ./configure phase. All OK. > I want to be able to include them as dylibs in my OSX app package. The app > wants to see dylibs which are built using @rpath like @rpath/libavutil.dylib > when inspecting the dylib using otool. Would anyone have any recommendations > on how to accomplish this? I must include ffmpeg dylibs in my app. You can have a look at how the VLC project does it. All of their libs are dynamic libs which are located in one sub directory of the app. So you have to set the rpath relative to your binary that makes the calls. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] configure: ERROR: x265 not found using pkg-config
On 2017-11-12 15:10, James Almer wrote: > Does this fix it for you? Unfortunately it did not. As requested, here the ticket: https://trac.ffmpeg.org/ticket/6830 Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] configure: ERROR: x265 not found using pkg-config
I get the following error during configure: ERROR: x265 not found using pkg-config My last compile run (3 days ago) worked perfectly. Somebody must have changed the configure script. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] compile errors on current master - libavcodec/audiotoolboxdec.c
On 2017-10-27 18:42, James Almer wrote: > Should be fixed, sorry about that. No worries, thanks for the fix. -- regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] compile errors on current master - libavcodec/audiotoolboxdec.c
Getting the following compile errors. I got this just now with current
master when I tried to compile today's snapshot...
2 days ago, all was good.
libavcodec/audiotoolboxdec.c:353:9: error: use of undeclared identifier
'AC3HeaderInfo'
AC3HeaderInfo hdr;
^
libavcodec/audiotoolboxdec.c:354:9: error: unknown type name
'GetBitContext'; did you mean 'GetByteContext'?
GetBitContext gbc;
^
GetByteContext
libavcodec/bytestream.h:35:3: note: 'GetByteContext' declared here
} GetByteContext;
^
libavcodec/audiotoolboxdec.c:355:9: error: implicit declaration of
function 'init_get_bits' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
init_get_bits(, pkt->data, pkt->size);
^
libavcodec/audiotoolboxdec.c:356:13: error: implicit declaration of
function 'ff_ac3_parse_header' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if (ff_ac3_parse_header(, ) < 0)
^
libavcodec/audiotoolboxdec.c:356:13: note: did you mean
'av_ac3_parse_header'?
libavcodec/ac3_parser.h:32:5: note: 'av_ac3_parse_header' declared here
int av_ac3_parse_header(const uint8_t *buf, size_t size,
^
libavcodec/audiotoolboxdec.c:356:40: error: use of undeclared identifier
'hdr'
if (ff_ac3_parse_header(, ) < 0)
^
libavcodec/audiotoolboxdec.c:358:33: error: use of undeclared identifier
'hdr'
in_format.mSampleRate = hdr.sample_rate;
^
libavcodec/audiotoolboxdec.c:359:39: error: use of undeclared identifier
'hdr'
in_format.mChannelsPerFrame = hdr.channels;
^
libavcodec/audiotoolboxdec.c:360:29: error: use of undeclared identifier
'hdr'
avctx->frame_size = hdr.num_blocks * 256;
^
libavcodec/audiotoolboxdec.c:361:27: error: use of undeclared identifier
'hdr'
avctx->bit_rate = hdr.bit_rate;
^
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] FFmpeg 3.4
On 2017-10-06 10:53, Michael Niedermayer wrote: > If people prefer a specific name, suggest one now, otherwise i will > pick a random one from past suggestions What about Cantor? Has this name already been used? -- regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Supporting DirecTV captioning.
On 2017-09-22 16:34, Joseph Van Riper wrote: > I would prefer not to sprinkle changes throughout something > if I can avoid it. Have you thought about a third party library then? This library can be maintained by the DirecTV folks and you can work on the glue between ffmpeg and the lib. The library can still use calls to existing functions... Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] FFmpeg 3.2
On 2016-10-26 15:29, Michael Niedermayer wrote: > release/3.2 branched > > ill make the 3.2 release tomorrow from release/3.2 > so if anyone wants to backport something, you have till then ffserver is still in that branch. I thought it would be removed from the repo and the configure script. Or am I missing something? Cheers, K. C. -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] FFmpeg 3.2
On 2016-09-27 09:30, Michael Niedermayer wrote: > Its long since FFmpeg 3.1, so its time to make 3.2 > ill branch release/3.2 off master and make 3.2 in maybe about a week or > 2 unless something delays it What happened to 3.2? Cheers, K. C. -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] FFmpeg 3.2
binp92P_YWvzj.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] FFmpeg 2.7
On 06.06.15 8:19 , Michael Niedermayer wrote: also if someone wants a specific name for it say/suggest it now, if theres no name suggested or no consensus then ill pick a random scientists/mathematicans name that was suggested previously To honor the beautiful mind who made game theory a whole different area, what about: John F. Nash Cheers, K. C. -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] remove the www. from the URL - http://evermeet.cx/ffmpeg/
Hmm, I believe my mail client screwed it up. I had to use git imap-send and then the mail client to actually send the patch, because git send-email gives me the following error on all my machines: perl5.16(58025,0x7fff776c2310) malloc: *** error for object 0x7fff90af47dd: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug error: git-send-email died of signal 6 Unfortunately I haven't been able to find anything on how to fix this. Cheers, K. C. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH] remove the www. from the URL - http://evermeet.cx/ffmpeg/
--- src/download | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/download b/src/download index a9d5cc2..7d50786 100644 --- a/src/download +++ b/src/download @@ -89,7 +89,7 @@ h3OS X Packages/h3 div class=list-group - a class=list-group-item href=http://www.evermeet.cx/ffmpeg/; + a class=list-group-item href=http://evermeet.cx/ffmpeg/; Static builds for strongOS X Intel 64-bit/strong /a a class=list-group-item href=http://ffmpegmac.net/; -- 2.3.1 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] remove the www. from the URL - http://evermeet.cx/ffmpeg/
Hi Timothy, On 2015-04-16 20:33, Timothy Gu wrote: Applying: remove the www. from the URL - http://evermeet.cx/ffmpeg/ fatal: corrupt patch at line 18 Thanks for fixing the patch. What was the problem with the patch, so that this won't happen again. Cheers, K. C. -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
