
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (95)
-
Mediabox : ouvrir les images dans l’espace maximal pour l’utilisateur
8 février 2011, parLa visualisation des images est restreinte par la largeur accordée par le design du site (dépendant du thème utilisé). Elles sont donc visibles sous un format réduit. Afin de profiter de l’ensemble de la place disponible sur l’écran de l’utilisateur, il est possible d’ajouter une fonctionnalité d’affichage de l’image dans une boite multimedia apparaissant au dessus du reste du contenu.
Pour ce faire il est nécessaire d’installer le plugin "Mediabox".
Configuration de la boite multimédia
Dès (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.
Sur d’autres sites (9675)
-
Android FFMPEG build for arm64 failed with error ?
26 août 2019, par bharat agheraI have made ffmpeg build with following build script.
https://github.com/Free-Syj/ffmpeg-build-script/blob/master/build-android-ffmpeg.shIt worked for armv7.
when I tried to make for arm64 architecture, it gave me following error.NDK/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64/bin/aarch64-linux-android-gcc is unable to create an executable file.
Edited : -
Following build script has been used to make the build.
NDK=/Users/tapansodha/Documents/Softwares/AndroidStudio/adt-bundle-mac-x86_64-20140702/android-ndk-r10e
function build_one
{
./configure --target-os=linux \
--prefix=$PREFIX \
--enable-cross-compile \
--extra-libs="-lgcc" \
--arch=arm \
--cc=$CC \
--cross-prefix=$PREBUILT/bin/aarch64-linux-android- \
--nm=$NM \
--sysroot=$PLATFORM \
--extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
--enable-shared \
--disable-static \
--extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \
--disable-everything \
--disable-debug \
--disable-programs \
--disable-doc \
--enable-decoder=h264 \
--enable-decoder=mjpeg \
--enable-decoder=mpeg4 \
--enable-decoder=mxpeg \
--enable-decoder=aac \
$ADDITIONAL_CONFIGURE_FLAG
make clean
make -j4 install
}
#arm arm64-v8a
PLATFORM=$NDK/platforms/android-21/arch-arm64/
PREBUILT=$NDK/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64
CC=$PREBUILT/bin/aarch64-linux-android-gcc
NM=$PREBUILT/bin/aarch64-linux-android-nm
CPU=arm64
PREFIX=./android_arm64n/$CPU
ADDITIONAL_CONFIGURE_FLAG=
build_one -
Android : mp4 file plays when downloaded but when choosing "Video" player gets "Cannot play video"
11 juillet 2019, par gviewI’ve converted the video to an mp4 with ffmpeg using the h264 codec and AAC, and used the baseline profile.
Videos are 540x360x250kbps
I then ran qt-faststart on the file to move the atoms into the right order.
I’ve stuck the file up on a wiki we use and created a link to it.
My test phone is a Samsung Galaxy S3.
When I browse to the page that has links to the mp4’s on it, and I click on them, I get a popup window with 2 options : Internet and Video.
If I download the videos using the "Internet" option, I can play them on the phone without issue.
I’ve done other encodings with the main profile as well, and these also play fine. I thought that a powerful phone like the s3 would be able to handle the more advanced compression schemes available in h264, however I’ve also browsed the Android docs in regards to supported video formats, and it seems to state that only the "baseline" compression profile is supported.
Regardless, what doesn’t work is trying to use the "Video" option which I assume tries to stream the video.
For the wiki in question, clicking on the link reveals that the content-type and content-length headers are being set :
Content-Length 6175996
Content-Type video/mp4;charset=UTF-8Clicking on the link with a browser invokes a player (Quicktime in most cases) that can play the mp4’s.
Is there more to having the file HTTP streamable beyond making a link to it ? Why won’t my Android 4 play these files ?
UPDATE :
I decided to make a quick HTML5 page using the video tag, and the videos do play on both my Galaxy S3 and the latest IOS. -
Android cannot play a video, but PC can [duplicate]
6 juin 2018, par CoXierThis question already has an answer here :
I use
ffmpeg
to convert gif to mp4 on Android. And part of configuration is :--disable-encoders \
--disable-decoders \
--enable-small \
--enable-encoder=libx264 \
--enable-encoder=flv \
--enable-encoder=opus \
--enable-encoder=gif \
--enable-decoder=h264 \
--enable-decoder=flv \
--enable-decoder=opus \
--enable-decoder=gif \However I can not play the output mp4 on Android. But pc can play it.
ffmpeg -i output.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'output.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.12.100
Duration: 00:00:09.73, start: 0.000000, bitrate: 330 kb/s
Stream #0:0(und): Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), yuv444p, 280x174, 328 kb/s, 11 fps, 11 tbr, 11264 tbn, 22 tbc (default)
Metadata:
handler_name : VideoHandlerIs there anything wrong ?