
Recherche avancée
Autres articles (40)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
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 -
Soumettre améliorations et plugins supplémentaires
10 avril 2011Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)
Sur d’autres sites (9023)
-
HTML5 Video Compatibility (MP4, WEBM, OGG) in 2021
19 juillet 2021, par WilliamThe support of HTML5 video has evolved a lot over the years. I am trying to understand whether the
<video></video>
element still needs to have three sources : MP4, WEBM, and OGG.

There are a lot of answers throughout StackOverflow with deeply conflicting information - some of which say that you just need MP4 now, others say, MP4 and WEBM are enough, and then finally many say that you need all three (although many of those article are 10 years old).


W3 suggests that either MP4 or WEBM alone would have universal support (Even though I found a 2011 article from Google saying that they would be removing support for MP4/H.264). Wikipedia paints a more complicated picture (as well as listing that Google Chrome does indeed support MP4/H.264). Azure Media services ONLY seems to allow output in MP4, which would suggest to me that MP4 must have widespread compatibility.


Also see Example 1, Example 2, Example 3.


Is there any definitive information on what video types to include in an HTML5 video player to achieve widespread compatibility ?


Background : I am building a Content Management Platform that allows uploading videos. When a new video is uploaded, a conversion process kicks off to convert the video into the required formats. This takes time and CPU/Memory, so if it is possible I would like to convert uploaded videos into as few formats as possible.


p.s. This question HAS been asked before, however, the fundamentals of playing video on the web continually evolve and most of the answers out there have become irrelevant.


-
Android NDK Build FFMPEG in 2021
19 janvier 2023, par KyrosI'm working on an android app, and I have to convert
webm
files tomp3
.
I really want to make a custom ffmpeg build, because it reduces the ffmpeg executable size to only 2MB.

My library works absolutely fine when running on my PC, but i'm struggling to build it for android... It seems like NDK architecture has changed and tutorials are outdated, and I can't find a proper and recent guide for android compiling...


I also would like to target all architectures (
aarch64
,armv7
,i686
, andx86_64
)...

I've been on this for hours, fixed many errors, but still nothing has worked ><.
Please help me ! :


PS. I'm compiling on Linux, here is my configuration script :


#!/bin/bash

API=31 # target android api

OUTPUT=/home/romain/dev/android/ffmpeg_build

NDK=/home/romain/android-sdk/ndk/23.0.7599858
TOOLCHAIN=$NDK/toolchains/llvm/prebuilt/linux-x86_64
SYSROOT=$TOOLCHAIN/sysroot

TOOL_PREFIX="$TOOLCHAIN/bin/aarch64-linux-android"

CC="$TOOL_PREFIX$API-clang"
CXX="$TOOL_PREFIX$API-clang++"

./configure \
 --prefix=$OUTPUT \
 --target-os=android \
 --arch=$ARCH \
 --cpu=$CPU \
 --disable-everything \
 --disable-everything \
 --disable-network \
 --disable-autodetect \
 --enable-small \
 --enable-decoder=opus,vorbis \
 --enable-demuxer=matroska \
 --enable-muxer=mp3 \
 --enable-protocol=file \
 --enable-filter=aresample \
 --enable-libshine \
 --enable-encoder=libshine \
 --cc=$CC \
 --cxx=$CXX \
 --sysroot=$SYSROOT \
 --extra-cflags="-0s -fpic"

make
make install



-
Revision 26fead7ecf : Renaming in MB_MODE_INFO The macro block mode info context originally contained
13 août 2013, par Paul WilkinsChanged Paths :
Modify /vp9/common/vp9_alloccommon.c
Modify /vp9/common/vp9_blockd.h
Modify /vp9/common/vp9_debugmodes.c
Modify /vp9/common/vp9_loopfilter.c
Modify /vp9/common/vp9_mvref_common.c
Modify /vp9/common/vp9_postproc.c
Modify /vp9/common/vp9_pred_common.c
Modify /vp9/common/vp9_pred_common.h
Modify /vp9/decoder/vp9_decodemv.c
Modify /vp9/decoder/vp9_decodframe.c
Modify /vp9/encoder/vp9_bitstream.c
Modify /vp9/encoder/vp9_encodeframe.c
Modify /vp9/encoder/vp9_rdopt.c
Modify /vp9/encoder/vp9_tokenize.c
Renaming in MB_MODE_INFOThe macro block mode info context originally contained an
entry for each 16x16 macroblock. In VP9 each entry refers
to an 8x8 region not a macro block, so the naming is misleading.This first stage clean up changes the names of 3 entries in the
structure to remove the mb_ prefix.TODO clean up the nomenclature more widely in respect of
mbmi and bmi.Change-Id : Ia7305c6d0cb805dfe8cdc98dad21338f502e49c6