Recherche avancée

Médias (91)

Autres articles (27)

  • D’autres logiciels intéressants

    12 avril 2011, par

    On ne revendique pas d’être les seuls à faire ce que l’on fait ... et on ne revendique surtout pas d’être les meilleurs non plus ... Ce que l’on fait, on essaie juste de le faire bien, et de mieux en mieux...
    La liste suivante correspond à des logiciels qui tendent peu ou prou à faire comme MediaSPIP ou que MediaSPIP tente peu ou prou à faire pareil, peu importe ...
    On ne les connais pas, on ne les a pas essayé, mais vous pouvez peut être y jeter un coup d’oeil.
    Videopress
    Site Internet : (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (4502)

  • Is there any way to concatinate multiple video and audio streams with offset ?

    17 avril 2019, par Demchenko Oleg

    I am sory for my english, it is not my mother language. My issue related to ffmpeg concatenation of audio and video streams. There are multiple audio and video streams which were recorded by online chat. All of them have start and end time points. If user turned off a micro or camera then audio and video streams wouldn’t be matched. How can I align all streams in one time series ? Can I add some white noise to separate the two videos ? Similar with audio.

  • converting mp3 to ts with ffmpeg [closed]

    29 janvier, par tamirg

    i have an mp3 of about 50 kb.
if i use ffmpeg to convert to ts :

    


    ffmpeg -i sample.mp3 sample.ts


    


    i end up getting a file of almost 200kb.

    


    while if i use some online software which converts mp3 to ts (https://clideo.com/editor/?convertTo=TS for example), i get a file with similar size to the original mp3.

    


    why does the ffmpeg conversion creates such a large file ? is it possible to reduce that ?

    


  • FFmpeg -> JSMpeg Websocket Closes Repeatedly

    13 mars 2018, par Kyle Martin

    I’m trying to create a fairly simple streaming server/site. Here’s the current flow :

    • OBS streams to an RTMP URL
    • Nginx accepts the RTMP stream and uses exec-push to have FFmpeg pick up the stream and transcode it
    • FFmpeg transcodes the stream and outputs it to a JSMpeg application, which displays the stream on a webpage.

    When I have my exec_push statement as follows, everything seems to work perfectly, except the browser says Possible garbage data. Skipping. on every frame it receives :

    exec_push /usr/bin/ffmpeg -re -i rtmp://127.0.0.1:1935/$app/$name -f mpeg1video  http://localhost:8080/supersecret;

    This behavior is understandable, because JSMpeg must receive MPEG-TS data, not MPEG1 data. It sees the MPEG1 frames and thinks they’re garbage.

    So through some online research, I found this :

    exec_push /usr/bin/ffmpeg -re -i rtmp://127.0.0.1:1935/$app/$name -c:v copy -c:a copy -f mpegts http://localhost:8080/supersecret;

    Supposedly, this is supposed to transcode my RTMP stream into an MPEG-TS format, which should be compatible with JSMpeg.

    However, with the second version of the command, my FFmpeg -> JSMpeg stream keeps connecting and disconnecting, connecting and disconnecting, and so on. This behavior is observed in terminal :

    Stream Connected: ::1:40208
    
close
    
Stream Connected: ::1:40212
    
close
    
Stream Connected: ::1:40216
    
close
    
Stream Connected: ::1:40220
    
close
    
Stream Connected: ::1:40224
    
close
    
...

    What would cause this ? I am pretty certain the issue is in my exec_push command. OBS is perfectly content, which tells me that the stream is making it to the server, and if I do a push, I can do a test push to Ustream just fine, which tells me that Nginx is at least processing the stream with some reasonable degree of success.

    Disclaimer : I have no idea what I’m talking about. Everything I know about FFmpeg and JSMpeg/Node is from snippets of code that I found online.

Navigation