Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (53)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • 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

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (8103)

  • how to install FFMpeg in xampp and laravel 9 [migrated]

    19 août 2022, par Yash Bohra

    i have tried

    


    Install FFMPEG on XAMPP

    


    this method to install...

    


    i have no idea about FFMpeg.... please command me the steps from downloading the FFMpeg to install in xampp...

    


    and than to setup in laravel

    


  • Streaming different MP3 files using Ezstream and Icecast

    3 mai, par hh083

    I am trying to stream two MP3 files to Icecast using Ezstream and the stream should run in web browsers. The files I am testing with were downloaded as webm and converted to MP3 using ffmpeg. They have the same channels count, same bitrate and same sample rate but different duration.

    



    My setup : the Ezstream xml configuration file is set to stream MP3 and a program playlist is used to identify what is the next file to be streamed, and no encoders or decoders are used. When I start streaming I save the process ID of the Ezstream process (using the -p argument), and then I use the command kill -10 $(cat currentpid) with currentpid as the file containing the process ID so Ezstream executes the playlist program to get the next file name and skips the current file to play the next one. Basically I am just switching between 1.mp3 and 2.mp3.

    




    



    The problem is that on Chrome web browser, when I switch between the two files the player (default HTML5 player) will suddenly stop (sometimes I can switch multiple times before it happens and sometimes it happens quickly) and the error PIPELINE_ERROR_DECODE is what I find when I access player.error in JavaScript. Although Firefox handles the change and continues the stream normally, I am convinced that Firefox here is the exception, that it is not a bug in Chrome (in my case), and that there is something wrong with my setup that needs to be fixed to support other browsers.

    



    Doing the same using mpv player, I get the following errors but the audio keeps streaming normally (sometimes it takes multiple switches before it happens just like in Chrome) :

    



    [ffmpeg/audio] mp3float: big_values too big
[ffmpeg/audio] mp3float: Error while decoding MPEG audio frame.
Error decoding audio.


    



    I tried using MP3 encoder and decoder I copied from the Ezstream example files (lame and madplay) but the problem still existed.

    



    I am not sure if the problem is basic and I cannot see it or it is more complicated. Also I do not have a problem if I need to use other format than MP3 to fix that issue, as long as that format is supported by Ezstream and Icecast.

    



    Thanks.

    


  • Does Android 4.x support streaming RTSP over TCP ?

    9 décembre 2014, par Robert

    I’ve used VideoView in Android to play video on wowza successfully. Now I got to deal with my server which the UDP ports seems to be blocked. With the proof of openRTSP command :

    -> % openRTSP rtsp://61.218.52.250:554/live/ch00_0

    Opening connection to 61.218.52.250, port 554...
    ...remote connection opened
    Sending request: OPTIONS rtsp://61.218.52.250:554/live/ch00_0 RTSP/1.0
    CSeq: 2
    User-Agent: openRTSP (LIVE555 Streaming Media v2013.12.16)


    Received 105 new bytes of response data.
    Received a complete OPTIONS response:
    RTSP/1.0 200 OK
    CSeq: 2
    Server: UBNT Streaming Server v1.2
    Public: DESCRIBE, SETUP, TEARDOWN, PLAY


    Sending request: DESCRIBE rtsp://61.218.52.250:554/live/ch00_0 RTSP/1.0
    CSeq: 3
    User-Agent: openRTSP (LIVE555 Streaming Media v2013.12.16)
    Accept: application/sdp


    Received 562 new bytes of response data.
    Received a complete DESCRIBE response:
    RTSP/1.0 200 OK
    CSeq: 3
    Server: UBNT Streaming Server v1.2
    Content-Base: rtsp://61.218.52.250:554/live/ch00_0/
    Content-Type: application/sdp
    Content-Length: 393

    v=0
    o=- 1 1 IN IP4 127.0.0.1
    s=Ubiquiti Live
    i=UBNT Streaming Media
    c=IN IP4 0.0.0.0
    t=0 0
    m=video 0 RTP/AVP 99
    b=AS:50000
    a=framerate:25
    a=x-dimensions:1280,720
    a=x-vendor-id:ubnt,a521
    a=x-rtp-ts:4617405454576779984
    a=rtpmap:99 H264/90000
    a=fmtp:99 profile-level-id=42A01E;packetization-mode=1;sprop-parameter-sets=Z0IAKOkAoAt1xIAG3dAAzf5gDYgQlA==,aM4xUg==
    a=control:trackID=0

    Opened URL "rtsp://61.218.52.250:554/live/ch00_0", returning a SDP description:
    v=0
    o=- 1 1 IN IP4 127.0.0.1
    s=Ubiquiti Live
    i=UBNT Streaming Media
    c=IN IP4 0.0.0.0
    t=0 0
    m=video 0 RTP/AVP 99
    b=AS:50000
    a=framerate:25
    a=x-dimensions:1280,720
    a=x-vendor-id:ubnt,a521
    a=x-rtp-ts:4617405454576779984
    a=rtpmap:99 H264/90000
    a=fmtp:99 profile-level-id=42A01E;packetization-mode=1;sprop-parameter-sets=Z0IAKOkAoAt1xIAG3dAAzf5gDYgQlA==,aM4xUg==
    a=control:trackID=0

    Created receiver for "video/H264" subsession (client ports 63346-63347)
    Sending request: SETUP rtsp://61.218.52.250:554/live/ch00_0/trackID=0 RTSP/1.0
    CSeq: 4
    User-Agent: openRTSP (LIVE555 Streaming Media v2013.12.16)
    Transport: RTP/AVP;unicast;client_port=63346-63347


    Received 47 new bytes of response data.
    Received a complete SETUP response:
    RTSP/1.0 461 Unsupported Transport
    CSeq: 4


    Failed to setup "video/H264" subsession: 461 Unsupported Transport

    After searching around I found it seems Android still not support RTSP over TCP :

    When streaming to an Android device using RTSP/RTP, the RTP portion
    must flow over UDP. Android doesn’t support RTSP/RTP interleaved (RTP
    over TCP). This means that if UDP is unavailable for RTP playback, RTP
    over TCP won’t work as a failover and your stream won’t play.

    Considering it’s posted on 2010, does Android 4.x support RTSP over TCP now ? I’ve found lots of post asking for how to force transfer via TCP other than UDP. I guess it’s not.

    If not, could I achieve it by re-compiling and using ffmpeg library ?

    Basically I hope ffmpeg could help me to automatically switch to TCP while UDP not available.