Recherche avancée

Médias (91)

Autres articles (53)

  • Keeping control of your media in your hands

    13 avril 2011, par

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

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (8929)

  • VP9 Profile 2 VDPAU support

    8 octobre 2020, par ManojGuptaBonda
    VP9 Profile 2 VDPAU support
    

    Added VDPAU to list of supported formats for VP9 420 10 and 12 bit
    formats. Add VP9 10/12 Bit support for VDPAU

    Signed-off-by : Philip Langdale <philipl@overt.org>

    • [DH] Changelog
    • [DH] libavcodec/version.h
    • [DH] libavcodec/vp9.c
  • ffmpeg errors out with Error initializing output stream 0:0 for the setting `-profile:v main`

    17 octobre 2020, par Vishwasa Navada K

    We are using ffmpeg for generating HSL streaming files (.m3u8, .ts) from multiple type of input video and audio like avi, mp4, mp3, mkv, m4a etc. We are trying to encode everything into h264 streams to support modern browsers. But we are facing issues in converting few videos of type avi and mp4 (not all). Below is the ffmpeg command (it's using ffmpeg fluent on NodeJS).

    &#xA;

    ffmpeg(fileName)&#xA;  .outputOptions([&#xA;    &#x27;-c:v h264&#x27;,&#xA;    &#x27;-profile:v main&#x27;,&#xA;    `-vf scale=1280:-2`,&#xA;    &#x27;-hls_list_size 0&#x27;,&#xA;    &#x27;-start_number 0&#x27;,&#xA;    &#x27;-hls_time 10&#x27;,&#xA;    &#x27;-loglevel error&#x27;,&#xA;  ])&#xA;  .output(output_file_path)&#xA;

    &#xA;

    When we try to run this with some set of specific avi and mp4 samples, it errors out saying&#xA;Error: ffmpeg exited with code 1: Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height.

    &#xA;

    I tried changing few commands (like providing crf value) and tried to run them, The only time it successfully converted converted them was when I removed the output option -profile:v main. I am not sure about the reason behind it.

    &#xA;

    I ran ffprobe to get the information from the videos that were not able to generate streams. I have them uploaded to gist here : https://gist.github.com/vishwasnavadak/91b5c978e2a3cb7a7c7a2bb505487263

    &#xA;

    Is there something I am missing ? What is the reason for it to error out when -profile:v main option is present ?

    &#xA;

  • audio/mp4 ; codecs="mp4a.40.2" not playing in Chrome and Firefox

    19 octobre 2020, par Stefan Falk

    It seems I want to convert audios, which I want to stream on my website, to audio/mp4; codecs="mp4a.40.2".

    &#xA;

    Using ffmpeg-cli-wrapper, I am converting my uploaded audio files with this command here :

    &#xA;

    ffmpeg -i /tmp/input.any -acodec aac -b:a 256000 /tmp/output.aac&#xA;

    &#xA;

    On the client I am creating a SourceBuffer like this :

    &#xA;

    this.sourceBuffer = this.mediaSource.addSourceBuffer(&#x27;audio/mp4; codecs="mp4a.40.2"&#x27;);&#xA;

    &#xA;

    The errors are :

    &#xA;

    Chrome :

    &#xA;

    NotSupportedError: Failed to load because no supported source was found.&#xA;

    &#xA;

    Firefox :

    &#xA;

    NotSupportedError: The media resource indicated by the src attribute or assigned media provider object was not suitable.&#xA;

    &#xA;

    Here comes the fun part :

    &#xA;

    If I create the SourceBuffer using audio/aac as mime-type :

    &#xA;

    this.sourceBuffer = this.mediaSource.addSourceBuffer(&#x27;audio/aac&#x27;);&#xA;

    &#xA;

    the audio gets played correctly on Chrome but Firefox says :

    &#xA;

    MediaSource.addSourceBuffer: Type not supported in MediaSource&#xA;

    &#xA;


    &#xA;

    Update

    &#xA;

    After changing the command to

    &#xA;

    ffmpeg -i /tmp/input.any -acodec aac -b:a 256000 /tmp/output.mp4&#xA;                                                             ^^^ &#xA;

    &#xA;

    Chrome/Firefox do not give an error when using audio/mp4; codecs="mp4a.40.2", but the audio is not being played.

    &#xA;


    &#xA;

    See

    &#xA;

    &#xA;