
Recherche avancée
Autres articles (53)
-
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (11164)
-
Compiling FFMPEG with x265 has ERROR : x265 not found using pkg-config
23 mars 2023, par timweiliuAt first, I have a project with ffmpeg build support x264 for android in Mac OS.



Now, I want to add x265 support.



I have compiled the x265 with make & make install like this :



[ 81%] Built target x265-static
[100%] Built target cli
Install the project...
-- Install configuration: "Release"
-- Up-to-date: /usr/local/lib/libx265.a
-- Up-to-date: /usr/local/include/x265.h
-- Up-to-date: /usr/local/include/x265_config.h
-- Up-to-date: /usr/local/lib/pkgconfig/x265.pc
-- Up-to-date: /usr/local/bin/x265




and then, I run this shell script :



make distclean 

NDK_PATH=$NDK_HOME
NDK_ARM_PATH=${NDK_PATH}/platforms/android-9/arch-arm
NDK_ARM_BIN_PATH=${NDK_PATH}/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/bin

CC=${NDK_ARM_BIN_PATH}/arm-linux-androideabi-gcc

chmod +x configure
chmod +x version.sh

if [ $APP_ABI = "armeabi-v7a" ]; then
LOCAL_CFLAGS="-O3 -DANDROID -fpic -I/usr/local/include -march=armv7-a -mfloat-abi=softfp -mfpu=neon"
ABLES="--enable-asm --enable-thumb --enable-hwaccels --cpu=armv7-a --enable-neon"
elif [ $APP_ABI = "armeabi" ]; then
LOCAL_CFLAGS="-O3 -DANDROID -fpic -I/usr/local/include"
ABLES="--disable-neon"
fi
echo $LOCAL_CFLAGS
echo $ABLES
echo $PKG_CONFIG_PATH

echo "开始configure"
./configure \
--disable-yasm \
--disable-debug \
--disable-doc \
--disable-ffmpeg \
--disable-ffprobe \
--disable-ffplay \
--disable-ffserver \
--disable-stripping \
--disable-avdevice \
--disable-postproc \
--disable-network \
--enable-pthreads \
--enable-small \
--disable-encoders \
--enable-encoder=libx264 \
--enable-encoder=libfdk_aac \
--enable-libx265 \
--pkg-config-flags="--static" \
...

echo "开始make"
make -j4

echo "开始install"
sudo make install




It results in an error :



-O3 -DANDROID -fpic -I/usr/local/include -march=armv7-a -mfloat-abi=softfp -mfpu=neon
--enable-asm --enable-thumb --enable-hwaccels --cpu=armv7-a --enable-neon
/usr/local/lib/pkgconfig
开始configure
ERROR: x265 not found using pkg-config




I looked at the config.log :



use_pkg_config x265 x265.h x265_api_get
check_pkg_config x265 x265.h x265_api_get
false --exists --print-errors x265
ERROR: x265 not found using pkg-config




but, the file of x265.pc is existing on the path. Its content is :



prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include

Name: x265
Description: H.265/HEVC video encoder
Version: 0.0
Libs: -L${libdir} -lx265
Libs.private: -lstdc++ -lm -lgcc -ldl -lgcc -ldl
Cflags: -I${includedir}




and the x265.h is in include path too.



I run



pkg-config --list-all




It also finds x265 :



TIMWEILIU-MC0:libSrc timweiliu$ pkg-config --list-all
libecpg_compat libecpg_compat - PostgreSQL libecpg_compat library
fdk-aac Fraunhofer FDK AAC Codec Library - AAC codec library
apr-1 APR - The Apache Portable Runtime library
apr-util-1 APR Utils - Companion library for APR
libpq libpq - PostgreSQL libpq library
libpcre libpcre - PCRE - Perl compatible regular expressions C library with 8 bit character support
libpgtypes libpgtypes - PostgreSQL libpgtypes library
libecpg libecpg - PostgreSQL libecpg library
x264 x264 - H.264 (MPEG4 AVC) encoder library
x265 x265 - H.265/HEVC video encoder
libpcreposix libpcreposix - PCREPosix - Posix compatible interface to libpcre
libiodbc iODBC - iODBC Driver Manager




Now, I don’t know why it does not work.
Why does pkg-config still not find the x265 ?


-
avformat/matroskadec : Accept more unknown-length elements
17 mai 2019, par Andreas Rheinhardtavformat/matroskadec : Accept more unknown-length elements
The current Matroska specifications mandate that only two elements may
use an unknown-length length : Segments and clusters. But this was not
always so : For the greater part of Matroska's existence, all master
elements were allowed to make use of the unknown-length feature.And there were muxers creating such files : For several years
libavformat's Matroska muxer used unknown-length for all master
elements when the output wasn't seekable. This only stopped in March
2010 with 2529bb30. And even afterwards it was possible (albeit
unlikely) for libavformat to create unknown-length master elements
that are in violation of today's specifications, namely if the master
element was so big that the seek backwards to update the size could
no longer be performed inside the AVIOContext's write buffer. This
has only been fixed in October 2016 (with the patches that introduced
support for writing CRC-32 elements).Libavformat's Matroska demuxer meanwhile has never really supported
unknown-length elements besides segments and clusters. Support for the
latter was hardcoded. This commit changes this : Now all master elements
for which a syntax to parse them is available are supported. This
includes the files produced by old versions of libavformat's muxer.More precisely, master elements that have unknown length and are about
to be parsed (not skipped) are supported ; only a warning is emitted for
them. For normal files, this means that level 1 elements after the
clusters that are encountered after the clusters have been parsed (i.e.
not because they are referenced by the seekhead at the beginning of the
file) are still unsupported (they would be skipped at this point if
their length were known).Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
-
Compiling x265 with ffmpeg for Android and receiving errors
5 juillet 2019, par m33ts4k0zTrying to compile x265 for use with arm64-v8a. After successuful build of x265 itself, I receive the following error when ffmpeg is about to compile :
require_pkg_config libx265 x265 x265.h x265_api_get
check_pkg_config libx265 x265 x265.h x265_api_get
test_pkg_config libx265 x265 x265.h x265_api_get
/root/ffmpeg_android/ffmpeg-android-1.6.3/ffmpeg-pkg-config --exists --print-errors x265
check_func_headers x265.h x265_api_get -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/include/x265 -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib -lx265
test_ld cc -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/include/x265 -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib -lx265
test_cc -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/include/x265 -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib
BEGIN /tmp/ffconf.xKyjnplW/test.c
1 #include
2 #include
3 long check_x265_api_get(void) { return (long) x265_api_get; }
4 int main(void) { int ret = 0;
5 ret |= ((intptr_t)check_x265_api_get) & 0xFFFF;
6 return ret; }
END /tmp/ffconf.xKyjnplW/test.c
/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/bin/aarch64-linux-android-clang -DANDROID -fpic -fpie -march=armv8-a --sysroot=/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/sysroot -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Dstrtod=avpriv_strtod -DPIC -DANDROID -fpic -fpie -march=armv8-a -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/vpx/android/arm64-v8a/include -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x264/android/arm64-v8a/include/x264 -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/include/x265 -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/lame/android/arm64-v8a/include -DANDROID -fpic -fpie -march=armv8-a --static -mcpu=cortex-a57 -std=c11 -fPIE -fomit-frame-pointer -fPIC -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/include/x265 -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib -c -o /tmp/ffconf.xKyjnplW/test.o /tmp/ffconf.xKyjnplW/test.c
clang60: warning: argument unused during compilation: '-L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib' [-Wunused-command-line-argument]
/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/bin/aarch64-linux-android-clang -Wl,-z,defs -Wl,--unresolved-symbols=report-all -march=armv8-a -L/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/sysroot -Wl,-z,relro -Wl,-z,now -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/vpx/android/arm64-v8a/lib -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x264/android/arm64-v8a/lib -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/lame/android/arm64-v8a/lib -Wl,-z,defs -Wl,--unresolved-symbols=report-all -march=armv8-a -L/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/sysroot -Wl,-z,relro -Wl,-z,now --static --sysroot=/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/sysroot -mcpu=cortex-a57 -Wl,--as-needed -Wl,-z,noexecstack -fPIE -pie -I/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/include/x265 -L/root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib -o /tmp/ffconf.xKyjnplW/test /tmp/ffconf.xKyjnplW/test.o -lx265 -lgcc
clang60: warning: argument unused during compilation: '-pie' [-Wunused-command-line-argument]
/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/bin/../lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: skipping incompatible /root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib/libx265.a when searching for -lx265
/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/bin/../lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: skipping incompatible /root/ffmpeg_android/ffmpeg-android-1.6.3/jni/x265/android/arm64-v8a/lib/libx265.a when searching for -lx265
/root/ffmpeg_android/ffmpeg-android-1.6.3/toolchain-android/bin/../lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find -lx265
clang60: error: linker command failed with exit code 1 (use -v to see invocation)
ERROR: x265 not found using pkg-configI use ffmpeg 4.1.3 and the latest version of x265 sources. I use this project to compile and I have succeeded when building without x265. I compile on Debian Buster x64.