Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (104)

  • Les vidéos

    21 avril 2011, par

    Comme 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 (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (7423)

  • Yes or no, will ffmpeg api do hardware decoding on iOS ?

    15 janvier 2019, par Fattie

    There seems to be conflicting information on this.

    https://trac.ffmpeg.org/wiki/HWAccelIntro

    notice the first diagram, it firmly marks iOS as “Y” on VideoToolbox

    enter image description here

    however in the comments down the bottom it says

    VideoToolbox. ​VideoToolbox, only supported on macOS. H.264 decoding is available in FFmpeg/libavcodec.

    And in the confusing second diagram it says "Standalone" is not done for VideoToolbox.

    We have found that using ffmpeg compiled in to iOS .... it seems to not use hardware decoding, which is really a pain.

    1. With avcodec_get_hw_config() we get AV_PIX_FMT_VIDEOTOOLBOX, AV_HWDEVICE_TYPE_VIDEOTOOLBOX which is seemingly correct.

    2. But usage and framerates clearly shows everything is being done in CPU. The code is in ff_hevc_hls_residual_coding all the time. (That’s fffmpeg’s software decoder.)

    3. This very diff very long git.videolan.org URL here seems to suggest again it should all be working.

    4. Have tried every iPhone etc. of course

  • mp4 video on Android

    9 février 2016, par matthewbaskey

    I wanted to convert some old Flash videos to 1 video format so the content will show on a mobile phone. I got some mp4 and it doesn’t work on Android, specifically Chrome 32 running on Android 4.3.

    Click this link to a fiddle

    It is loading the mp4 file on Chrome 32 on Android 4.3, but I thought there is no support for H.256

    Then I went to a this site http://techslides.com/sample-webm-ogg-and-mp4-video-files-for-html5/

    and the mp4 video there works on Android/Chrome.

    I used VLC to check the codecs and they look the same

    H264 - MPEG-4 AVC (part 10) (avc1)
    Resolution: is different (working one is 560x320
    Resolution: mp4 not working is 640x480
    Framerate: working is 30, not working is 12
    Decoded format: Planar4:2:0 YUV

    I then searched the codec then with ffmpeg and I see that
    there is a property called
    compatible_brands : mp42icomavc1

    which is different than the non-working mp4 which has this property set to
    compatible : mp42mp41

    The file sizes are quite different as well. Could this be an issue.

    When I load http://html5test.com the Chrome on Android browser says MPEG-4 is not supported by H.264 is. it doesn’t say anything about the container.

    ok here is some source code, I thought chrome on android doesn’t support mp4 files, but when I load the following on Chrome 32 running on Sony Xperia Tablet running Android 4.3. I had an mp4 file that I converted to webm, but chrome still could not run it. It is 8 MB so perhaps the size is an issue....this mp4 has a different size and frameframe. Other than that I only see compatible version different as mentioned above.

       


       <h4>This is mp4 video</h4>
       <video controls="controls" autoplay="autoplay" preload="auto">
           <source src="http://techslides.com/demos/sample-videos/small.mp4" type="video/mp4">
       </source></video>

  • Video recorded using Kurento is corrupted

    10 avril 2023, par Pranjal Lamba

    We are using Kurento media server v6.6.1 to record a video conference. The web app client which runs on Chrome(Windows, OSX, Android) is using a modified version of one-to-one-call-advanced Kurento sample and the second client is an Android native application which is using Nubomedia webrtcpeer v1.1.1. Nubomedia webrtcpeer uses LibJingle built by io.pristine v11139(released on December 2015). The video and audio is recorded in two separate recorder endpoints by Kurento.

    &#xA;

    Video conference recordings generated using web app client/s are working properly. But sometimes the video generated using native application contains all the frames within initial few seconds. Please find below download link for the problematic video generated by our Android native application,

    &#xA;

    https://drive.google.com/file/d/1vOVk8hPuP_iOlQfsmMoqZLhICy-Jpcee/view?usp=sharing

    &#xA;

    We are testing this feature on a range of Android devices, Nexus 5(Android 6.0.1), Nexus 6(Android 7.1.1), Sony Xperia Z Tablet(Android 6.0.1), Samsung Galaxy Tab A(Android 5.0), OnePlus 3(Android 7.1.1), Xiaomi A1(Android 7.1.1). The issue randomly starts occurring on a bunch of these devices while the others work properly and vice-versa.

    &#xA;

    We are recording the videos with the following constraints,

    &#xA;

    Web app client

    &#xA;

    Minimum video width : 32
    &#xA;Minimum video height : 32
    &#xA;Maximum video width : 320
    &#xA;Maximum video height : 320
    &#xA;Minimum framerate : 1
    &#xA;Maximum framerate : 15
    &#xA;Video container format : MP4
    &#xA;Video codec : H.264
    &#xA;Audio codec : AAC

    &#xA;

    Android native client

    &#xA;

    Minimum video width : 32
    &#xA;Minimum video height : 32
    &#xA;Maximum video width : 480
    &#xA;Maximum video height : 640
    &#xA;Minimum framerate : 1
    &#xA;Maximum framerate : 25
    &#xA;Video container format : MP4
    &#xA;Video codec : H.264
    &#xA;Audio codec : Opus

    &#xA;