
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (40)
-
Selection of projects using MediaSPIP
2 mai 2011, parThe examples below are representative elements of MediaSPIP specific uses for specific projects.
MediaSPIP farm @ Infini
The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...) -
Sélection de projets utilisant MediaSPIP
29 avril 2011, parLes exemples cités ci-dessous sont des éléments représentatifs d’usages spécifiques de MediaSPIP pour certains projets.
Vous pensez avoir un site "remarquable" réalisé avec MediaSPIP ? Faites le nous savoir ici.
Ferme MediaSPIP @ Infini
L’Association Infini développe des activités d’accueil, de point d’accès internet, de formation, de conduite de projets innovants dans le domaine des Technologies de l’Information et de la Communication, et l’hébergement de sites. Elle joue en la matière un rôle unique (...) -
Automated installation script of MediaSPIP
25 avril 2011, parTo overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
The documentation of the use of this installation script is available here.
The code of this (...)
Sur d’autres sites (5037)
-
avutil/opt : only skip evaluation for rational options
18 avril 2020, par Marton Balintavutil/opt : only skip evaluation for rational options
Fixes problems when non-rational options were set using rational expressions,
causing rounding errors and the option range limits not to be enforced
properly.ffmpeg -f lavfi -i "sine=r=96000/2"
This caused an assertion failure with assert level 2.
Signed-off-by : Marton Balint <cus@passwd.hu>
-
Problems with muxing fmp4 stream with libav
20 juillet 2020, par Elias Wagnerbergercurrently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.


i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.


my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264rgb to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that the problem lies in the
moov
box that is one of the two initialization boxes of a fmp4 stream.

chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.


my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?


-
Problems with muxing fmp4 stream with libav
20 juillet 2020, par Elias Wagnerbergercurrently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.


i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.


my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264rgb to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that the problem lies in the
moov
box that is one of the two initialization boxes of a fmp4 stream.

chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.


my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?