
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (64)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Installation en mode standalone
4 février 2011, parL’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
[mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...) -
Installation en mode ferme
4 février 2011, parLe mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
C’est la méthode que nous utilisons sur cette même plateforme.
L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)
Sur d’autres sites (8311)
-
FFMPEG failing in AWS Lambda
18 février 2019, par Zaid AmirI am trying to create a transcoding function for short videos. The function is hosted on AWS Lambda. The problem is that AWS lambda seems to be missing something that FFMPEG requires, at least according to Amazon.
I contacted Amazon earlier and this is their response to the issue :
We found that the FFMPEG operations require at least libx264 and an
acc library, both of which will have dependencies of their own. To
troubleshoot the issue it will involve diving deeper into the full
dependency chain. We can see that it works in the Amazon Linux
environment however, the environment is similar but not identical to
the lambda environment. There can be some dependencies that exist in
Amazon Linux but not in lambda environment as Lambda runs on the
container. Here, as FFmpeg is a third party software, diving deeper
into the dependency chain and verifying the version compatibilities is
very hard to do. Unfortunately going further, this is bound to go into
architecture and code support which is out of AWS Support scope 1. I
hope you understand our limitations. However should FFmpeg support
have any questions specific to the Lambda platform, please do let us
know and we will be happy to assist. We will be in better position to
investigate further once you receive an update from the FFmpeg support
suggesting an issue from Lambda end.Upon AWS suggestion, I contacted FFMPEG on the developers mailing list, my message was rejected with the reason being that its more suited to ffmpeg users mailing list than developers. I sent an email to ’ffmpeg-user@ffmpeg.org’ a week ago and did not get any response yet.
I then went and built a dynamically linked ffmpeg version making sure to package all libraries, checked ddl on each one, then made a small lambda function that looped over all binaries and ddled each one of them, compared that to the output I got from Amazon Linux and the same dependencies/versions exists on both lambda and the AWS Linux instance yet ffmpeg still fails on lambda.
You can find a detailed log file here : https://www.datafilehost.com/d/6e5e21bb
And this is a sample of the errors I’m getting, repeated across the entire log file :
2018-08-14T12:27:10.874Z [h264 @ 0x65c2fc0] concealing 2628 DC, 2628
AC, 2628 MV errors in P frame2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.11 is not
allocated2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
data found when processing input2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Invalid NAL unit size
(108085662 > 1649).2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Error splitting the input
into NAL units.2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.0 is not
allocated2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
data found when processing input2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Invalid NAL unit size
(71106974 > 1085).2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Error splitting the input
into NAL units.2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] Pulse tool not allowed in
eight short sequence.This log is generated when trying to perform an HLS transcoding on this file : https://www.datafilehost.com/d/999a4492
Note that the issue is not related to that file alone nor is it related to HLS, its general and happen on all videos and any ffmpeg command that tries to seek the stream, even tried extracting a single frame from a video using the simplest form possible for example :
ffmpeg -ss 00:00:02 -I file.mp4 -vframes 1 -y output.jpg
also fails with the same errors in the log file.Not sure how to debug this further. Tried enabling debug logs with ‘-loglevel debug’ but did not give me any extra info. Any help or suggestions
-
FFmpeg libraries on Windows - Undefined References
26 novembre 2018, par GomesI am trying to use FFmpeg libraries available from here under Windows 10 (64 bits). I downloaded version=20181126-90ac0e5, architecture=Windows-64, Linking=Dev. There are 3 folders inside that FFmpeg folder : examples, lib and include.
To use these libraries I copied the contents of the "include" folder to the "include" folder of my MinGW installation. I also copied the contents of the "lib" folder to the "lib" folder of MinGW.
I try to compile the decode_video.c example that comes inside the examples folder with the following way :gcc decode_video.c -o decode_video.exe -lavcodec -lavutil -lavformat -lm
The compiler gives me these undefined references :
undefined reference to `avcodec_send_packet'
undefined reference to `avcodec_receive_frame'
undefined reference to `av_packet_alloc'
undefined reference to `avcodec_find_decoder'
undefined reference to `av_parser_init'
undefined reference to `avcodec_alloc_context3'
undefined reference to `avcodec_open2'
undefined reference to `av_frame_alloc'
undefined reference to `av_parser_parse2'
undefined reference to `av_parser_close'
undefined reference to `avcodec_free_context'
undefined reference to `av_frame_free'
undefined reference to `av_packet_free'I would like to know what I am doing wrong here. Any guidance is very welcome.
-
Why do I get "error : invalid instruction mnemonic" when compiling FFmpeg for Android ?
20 octobre 2018, par donturnerI’m trying to compile FFmpeg 4.0 for Android using
clang
from the NDK (r18.1.5063045). My host architecture is Mac OS.Here’s my configure command :
./configure \
--target-os=android \
--arch=armv7-a \
--enable-cross-compile \
--cc=${ANDROID_NDK}/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang \
--enable-shared \
--disable-staticThis completes successfully. So I run
make -j8
and get the following error :In file included from libavfilter/vf_mestimate.c:22:
In file included from ./libavcodec/mathops.h:40:
./libavcodec/arm/mathops.h:90:26: error: invalid instruction mnemonic 'itt'
"cmp %1, %2 \n\t"
^
<inline asm="asm">:3:2: note: instantiated into assembly here
itt gt
^~~
</inline>Any idea what could be causing this ?