Recherche avancée

Médias (91)

Autres articles (55)

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

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

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, 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 (...)

Sur d’autres sites (6406)

  • vp9 : drop support for real (non-emulated) edges

    20 décembre 2013, par Anton Khirnov
    vp9 : drop support for real (non-emulated) edges
    

    They are not measurably faster on x86, they might be somewhat faster on
    other platforms due to missing emu edge SIMD, but the gain is not large
    enough to justify the added complexity.

    • [DBH] libavcodec/vp9block.c
    • [DBH] tests/fate/vpx.mak
  • How to decode and display real-time H264 stream using ffmpeg in Python ?

    25 mars 2022, par yiiiiiiiran

    I would like to port the live stream to ffmpeg and display it in real time using Python.

    


    Anyone knows how to port the stream to PIPE ? And in the mean time to display it after decoding ?

    


    I managed to get real-time stream from my Raspberry Pi3 to Windows PC, using RS232 connection with Baud Rate 2M.

    


    The format of the stream is in H264. The data package I get for each frame is in .
In order for the program to know when does each package ends, I've add

    


    bytes([0xcc,0xdd,0xee,0xff])


    


    to the end of package. So that my serial port will read for a package until it sees those bytes.

    


    Lets assume the stream WIDTH, HEIGHT, NUM_FRAMES, FPS = 320, 240, 90, 30

    


    I have the command for decode the h264 stream :

    


    cmd = ["C:/XXXXXX/ffmpeg.exe",
    "-probesize", "32",
    "-flags", "low_delay",
    "-f", "h264",
    "-i", "pipe:",
    "-f", "rawvideo", "-pix_fmt", "rgb24", "-s", "384x216",
    "pipe:"]

decode_process = sp.Popen(cmd, stdin=sp.PIPE, stdout=sp.PIPE)


    


    The stream package I got is

    


    while datetime.now() &lt; end_time:&#xA;    pkg = ser.read_until(expected=bytes([0xcc,0xdd,0xee,0xff])) #output <class>&#xA;    frame_len = len(pkg)-4&#xA;    frame_inBytes = pkg[0:frame_len]&#xA;    decode_process.stdin.write(frame_inBytes)&#xA;</class>

    &#xA;

    I want to write the real time stream to PIPE however it shows error :

    &#xA;

    [h264 @ 0000017322a3e980] missing picture in access unit with size 48&#xA;[h264 @ 0000017322a3e980] no frame!&#xA;[h264 @ 0000017322a2d240] Stream #0: not enough frames to estimate rate; consider increasing probesize&#xA;[h264 @ 0000017322a2d240] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size&#xA;Consider increasing the value for the &#x27;analyzeduration&#x27; (0) and &#x27;probesize&#x27; (32) options        &#xA;Input #0, h264, from &#x27;pipe:&#x27;:&#xA;  Duration: N/A, bitrate: N/A&#xA;  Stream #0:0: Video: h264, none, 25 tbr, 1200k tbn&#xA;Stream mapping:&#xA;  Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native))&#xA;[h264 @ 0000017322a3f180] no frame!&#xA;Error while decoding stream #0:0: Invalid data found when processing input&#xA;Cannot determine format of input stream 0:0 after EOF&#xA;Error marking filters as finished&#xA;Conversion failed!&#xA;

    &#xA;

  • ffmpeg and 7160 HD Capture card error, already set rtbufsize 2000M, still real time buffer too full

    21 septembre 2015, par todaf

    The 7160 Capture card original video was shown fine in the Honestech HD DVR software that is included.

    However, when the card was captured using ffmpeg and publish out. This error occurred after a while running ffmpeg :

    real-time buffer [7160 HD Capture] video input too full or near too full ...

    I have already set -rtbufsize 2000M which is nearly the maximum that is allowed and can not be increased further.

    Please tell me how to resolve this bug or give me an example that can be used without producing this bug. Thank you very much. You do not neeed the code that I used because almost any code even the simplest code I used produced this error after running for a while. The published video also lag and lost.