
Recherche avancée
Autres articles (36)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...) -
Support de tous types de médias
10 avril 2011Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)
Sur d’autres sites (5388)
-
Android : mp4 file plays when downloaded but when choosing "Video" player gets "Cannot play video"
14 janvier 2014, 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. -
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 ?


-
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