
Recherche avancée
Médias (16)
-
#7 Ambience
16 octobre 2011, par
Mis à jour : Juin 2015
Langue : English
Type : Audio
-
#6 Teaser Music
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#5 End Title
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#3 The Safest Place
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#4 Emo Creates
15 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#2 Typewriter Dance
15 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
Autres articles (12)
-
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 (...) -
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
Les vidéos
21 avril 2011, parComme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)
Sur d’autres sites (3005)
-
transcoding legacy MJPEG camera stream using ffmpeg to rstp stream
1er décembre 2013, par ArckoI am trying out this solution to transcoding legacy MJPEG camera stream using ffmpeg to rstp stream, which originally posted on http://www.wowza.com/forums/showthread.php?11218-Transcoding-Solution-For-Legacy-MJPEG-Cameras
As the post is a little old, so it seems not working well in ubuntu 12.04 with the latest ffmpeg source code from git ://source.ffmpeg.org/ffmpeg.git
Here's the steps :
- Compile and installed ffmpeg follwing guide https://trac.ffmpeg.org/wiki/UbuntuCompilationGuide
-
Created ffserver.conf and running ffserver successfully using server.sh
!/bin/bash
while [ 1 ]
do
ffserver -loglevel verbose
done -
created pull_stream_http.php following the guide
-
Created stream.sh and running :
!/bin/bash
while [ 1 ]
dophp -f pull_stream_http.php | ffmpeg -an -f mjpeg -maxrate 500 -b24k -r 6 -i - 6 http://[serverip]:8090/feed1.ffm
php -f pull_stream_http.php | ffmpeg -an -f mjpeg -r -i -vcodec libx264 -map 0 -vpre fastfirstpass -vpre baseline -b 24k -bt 32k -threads 0 http://[serverip]:8090/feed1.ffm
done
Now comes the error with stream.sh : "Invalid input file index : 0".
Any one who familiar with ffmpeg would give some advice ?
Thanks,
Arcko -
ffmpeg and libaom compilation failed "unable to open include file `third_party/x86inc/x86inc.asm"
7 octobre 2023, par samI'm trying to build ffmpeg using this guide :
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu


the problem is when i try to compile libaom using the following commands :


cd ~/ffmpeg_sources && \
git -C aom pull 2> /dev/null || git clone --depth 1 https://aomedia.googlesource.com/aom && \
mkdir -p aom_build && \
cd aom_build && \
PATH="$HOME/bin:$PATH" cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX="$HOME/ffmpeg_build" -DENABLE_TESTS=OFF -DENABLE_NASM=on ../aom && \
PATH="$HOME/bin:$PATH" make && \
make install



i get the following error :


/root/ffmpeg_sources/aom/aom_dsp/x86/sad4d_sse2.asm:14: fatal: unable to open include file `third_party/x86inc/x86inc.asm'
CMakeFiles/aom_dsp_encoder_sse2.dir/build.make:62: recipe for target 'CMakeFiles/aom_dsp_encoder_sse2.dir/aom_dsp/x86/sad4d_sse2.asm.o' failed
make[2]: *** [CMakeFiles/aom_dsp_encoder_sse2.dir/aom_dsp/x86/sad4d_sse2.asm.o] Error 1
CMakeFiles/Makefile2:842: recipe for target 'CMakeFiles/aom_dsp_encoder_sse2.dir/all' failed
make[1]: *** [CMakeFiles/aom_dsp_encoder_sse2.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2



Is there any fix for this issue ?


-
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.