
Recherche avancée
Médias (1)
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (52)
-
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
-
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...) -
Le plugin : Gestion de la mutualisation
2 mars 2010, parLe plugin de Gestion de mutualisation permet de gérer les différents canaux de mediaspip depuis un site maître. Il a pour but de fournir une solution pure SPIP afin de remplacer cette ancienne solution.
Installation basique
On installe les fichiers de SPIP sur le serveur.
On ajoute ensuite le plugin "mutualisation" à la racine du site comme décrit ici.
On customise le fichier mes_options.php central comme on le souhaite. Voilà pour l’exemple celui de la plateforme mediaspip.net :
< ?php (...)
Sur d’autres sites (5537)
-
Java execute command doesn't work in code
27 août 2017, par ArianaI am calling java.lang.Runtime.exec(...) in my Java program to run a command (some
FFMPEG
commands) simply passed to my function :private static void RunCommand(String command) throws InterruptedException {
try {
// Execute command
Process proc = Runtime.getRuntime().exec(command);
}
}It runs OK for simple FFMPEG cases such as
ffmpeg -i input.avi -c copy output.avi
.But for one of the commands, apparently it doesn’t run. When I copy/paste the exact String in command line, I am able to run it and see the output file.
ffmpeg -i "concat:/home/temp10.avi|/home/p2.avi|/home/temp15.avi" -c copy -y /home/output.avi
Which is the following in code :
String c4="ffmpeg -i \"concat:"+dir+temp1+"|"+dir+ad+"|"+dir+temp3+"\" -c copy -y "+dir+output;
What is going on ? Any guesses why it doesn’t run in code ? If the
"
is causing the problem, why the corresponding string looks good ?! -
"no archive symbol table (run ranlib)" issue with static linking FFmpeg for android
9 octobre 2017, par ProgramistI am trying to build FFmpeg for android as static libraries on a MacOS Sierra machine.
Following is my
buildscript.sh
which is very much based upon the one in here#!/bin/bash
cd ffmpeg-3.3.4
NDK=/path/to/android/ndk/android-ndk-r15c
SYSROOT=$NDK/platforms/android-21/arch-arm64/
TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64
AR=$TOOLCHAIN/bin/arm-linux-androideabi-ar
CPREFIX=$TOOLCHAIN/bin/arm-linux-androideabi-
CC=$TOOLCHAIN/bin/arm-linux-androideabi-gcc
CXX=$TOOLCHAIN/bin/arm-linux-androideabi-g++
LD=$TOOLCHAIN/bin/arm-linux-androideabi-ld
RANLIB=$TOOLCHAIN/bin/arm-linux-androideabi-ranlib
STRIP=$TOOLCHAIN/bin/arm-linux-androideabi-strip
X264LIB=$X264/android/arm/lib/
X264INC=$X264/android/arm/include/
function build_ffmpeg_android {
./configure \
--prefix=$PREFIX \
--disable-stripping
--arch=arm \
--cpu=cortex-a8 \
--target-os=linux \
--enable-cross-compile \
--enable-pic \
--disable-programs \
--enable-static \
--disable-shared \
--cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
--disable-doc \
--enable-postproc \
--enable-swscale \
--enable-avfilter \
--enable-avresample \
--disable-opencl \
--disable-securetransport \
--enable-gpl \
--sysroot=$SYSROOT \
--extra-cflags="-Os -fpic $ADDI_CFLAGS -I$X264INC" \
--extra-ldflags="$ADDI_LDFLAGS -s -L$X264LIB -lx264" \
--enable-gpl \
--enable-decoders \
--enable-encoders \
--enable-muxers \
--enable-demuxers \
--enable-parsers \
--enable-protocols \
--enable-filters \
--enable-avresample \
--enable-libfreetype \
--disable-indevs \
--enable-indev=lavfi \
--disable-outdevs \
--enable-hwaccels \
--enable-ffmpeg \
--disable-ffplay \
--disable-ffprobe \
--disable-ffserver \
--disable-network \
--enable-libx264 \
--enable-zlib \
--enable-muxer=md5
make clean
make -j9
make install
}
CPU=arm
PREFIX=$(pwd)/android/$CPU
ADDI_CFLAGS="-marm"
build_ffmpeg_androidThe output of above script is placed inside
ffmpeg-3.3.4/android/arm
.Problem :
When trying to link to these.a
libraries from my app using-lavformat -lavcodec -lswscale -lavutil -lavfilter -lswresample -lavdevice
,
I get the following linker error for each of them:-1: error: error: avformat: no archive symbol table (run ranlib)
:-1: error: error: avcodec: no archive symbol table (run ranlib)
:-1: error: error: swscale: no archive symbol table (run ranlib)
:-1: error: error: avutil: no archive symbol table (run ranlib)
:-1: error: error: avfilter: no archive symbol table (run ranlib)
:-1: error: error: swresample: no archive symbol table (run ranlib)
:-1: error: error: avdevice: no archive symbol table (run ranlib)Looking at this discussion here, I am doing it correct by selecting
arm-linux-androideabi-ar
inCPREFIX
.Trying to solve the error, I’ve also added the following configure flag for
ranlib
to be picked up specifically for android but doesn’t seem to help.RANLIB=$TOOLCHAIN/bin/arm-linux-androideabi-ranlib
Question :
What else am I missing here ?
What is needed in mybuildscript.sh
to pick the correct ranlib & stop complaining about archive symbol table when linking from my app ? -
Error : failed to run custom build command for `ffmpeg-sys-next v6.0.1`
5 décembre 2023, par moxI am trying to make a program that converts a MP4 into a gif and vice versa by decoding its packets and encoding them into a MP4 (or gif), I am using ffmpeg-next package (which uses ffmpeg rust behind it) to do this, my operating system is Linux 22.04 Ubuntu LTS (ARM64). When i try to build the program using
cargo build
i am met with a very long error message.

error: failed to run custom build command for `ffmpeg-sys-next v6.0.1`

Caused by:
 process didn't exit successfully: `/home/parallels/Downloads/file-conversion-rs/target/debug/build/ffmpeg-sys-next-1aa9b27d2be5c242/build-script-build` (exit status: 101)
 --- stdout
 cargo:rerun-if-env-changed=LIBAVUTIL_NO_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=SYSROOT
 cargo:rustc-link-search=native=/usr/lib/aarch64-linux-gnu
 cargo:rustc-link-lib=avutil
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=LIBAVFORMAT_NO_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=SYSROOT
 cargo:rustc-link-search=native=/usr/lib/aarch64-linux-gnu
 cargo:rustc-link-lib=avformat
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=LIBAVFILTER_NO_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=SYSROOT
 cargo:rustc-link-search=native=/usr/lib/aarch64-linux-gnu
 cargo:rustc-link-lib=avfilter
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=LIBAVDEVICE_NO_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_PATH
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
 cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
 cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

 --- stderr
 thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" PKG_CONFIG_ALLOW_SYSTEM_LIBS="1" "pkg-config" "--libs" "--cflags" "libavdevice"` did not exit successfully: exit status: 1
 error: could not find system library 'libavdevice' required by the 'ffmpeg-sys-next' crate

 --- stderr
 Package libavdevice was not found in the pkg-config search path.
 Perhaps you should add the directory containing `libavdevice.pc'
 to the PKG_CONFIG_PATH environment variable
 No package 'libavdevice' found
 ', /home/parallels/.cargo/registry/src/github.com-1ecc6299db9ec823/ffmpeg-sys-next-6.0.1/build.rs:733:22
 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace



I am aware of the problem, it cannot find the libavdevice in the PKG_CONFIG.


I have tried installing the libavdevice package using
sudo apt install libavdevice
but Ubuntu cannot find it, i also tried installing the ffmpeg package directly, i had also searched the same error message, someone else had the same error issue but after running the solution provided by someone it still does not build/work.