Recherche avancée

Médias (10)

Mot : - Tags -/wav

Autres articles (45)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Les notifications de la ferme

    1er décembre 2010, par

    Afin d’assurer une gestion correcte de la ferme, il est nécessaire de notifier plusieurs choses lors d’actions spécifiques à la fois à l’utilisateur mais également à l’ensemble des administrateurs de la ferme.
    Les notifications de changement de statut
    Lors d’un changement de statut d’une instance, l’ensemble des administrateurs de la ferme doivent être notifiés de cette modification ainsi que l’utilisateur administrateur de l’instance.
    À la demande d’un canal
    Passage au statut "publie"
    Passage au (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (6899)

  • ffmpeg and libaom compilation failed "unable to open include file `third_party/x86inc/x86inc.asm"

    7 octobre 2023, par sam

    I'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"

    14 janvier 2014, par gview

    I'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-8

    Clicking 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 : mp4 file plays when downloaded but when choosing "Video" player gets "Cannot play video"

    11 juillet 2019, par gview

    I’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-8

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