Recherche avancée

Médias (1)

Mot : - Tags -/graphisme

Autres articles (51)

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

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (11067)

  • http: Add a new protocol for opening connections via http proxies

    10 novembre 2011, par Martin Storsjö

    http: Add a new protocol for opening connections via http proxies

  • tests/fate/seek : check seek opertation with mov demuxer and file protocol

    9 septembre 2024, par Steven Liu
    tests/fate/seek : check seek opertation with mov demuxer and file protocol

    fix error at fate-seek-* when
    
configure with —disable-everything —samples=fate-suite/ —enable-demuxer=mov
    

    Signed-off-by : Steven Liu <lq@chinaffmpeg.org>
    • [DH] tests/fate/seek.mak

  • Capturing Screen with FFMPEG on RTP protocol

    23 septembre 2020, par mertakkartal

    I am struggling about capturing the screen of remote computer on the same network with ffmpeg on RTP protocol.

    &#xA;

    On the remote computer I run these two parameter blocks in different bash scripts for making the server catches the stream.

    &#xA;

    For video :

    &#xA;

    ffmpeg -f x11grab -framerate 25 -video_size uhd2160 -i :0.0 -c:video h264_nvenc -preset fast -pix_fmt bgr0 -b:v 6M -g 25 -an -f rtp_mpegts rtp://multicastaddress:videoPort

    &#xA;

    For Audio :

    &#xA;

    ffmpeg -f alsa -i hw:0,0 -c:audio aac -b:a 48K -f rtp_mpegts rtp://multicastaddress:audioPort

    &#xA;

    Then , I run my ffmpeg capturing screen parameter block from the server as root privilege like as below :

    &#xA;

    ffmpeg -y -buffer_size 425984 -thread_queue_size 32 -i rtp://@multicastaddress:videoPort -buffer_size 5000 -thread_queue_size 32 -i rtp://@multicastaddress:audioPort -map 0:0 -map 1:0 -c:v copy -c:a copy output.mp4

    &#xA;

    When I run it , it outputs those errors as below ,

    &#xA;

    [rtp @ 0x2329380] RTP: missed 284 packets&#xA;[rtp @ 0x2329380] RTP: missed 487 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1320.4kbits/s speed=1.27x    &#xA;[rtp @ 0x2329380] RTP: missed 2204 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1308.9kbits/s speed=1.24x    &#xA;[rtp @ 0x2329380] RTP: missed 300 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet&#xA;[rtp @ 0x2329380] RTP: missed 468 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1155.6kbits/s speed= 1.2x    &#xA;[rtp @ 0x2329380] RTP: missed 2222 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1197.0kbits/s speed=1.19x    &#xA;[rtp @ 0x2329380] RTP: missed 278 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1156.1kbits/s speed=1.18x    &#xA;[rtp @ 0x2329380] RTP: missed 303 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1064.8kbits/s speed=1.32x    &#xA;[rtp @ 0x2329380] RTP: missed 3 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1064.8kbits/s speed=1.17x    &#xA;[rtp @ 0x2329380] RTP: missed 280 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1095.4kbits/s speed=1.16x    &#xA;[rtp @ 0x2329380] RTP: missed 1737 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1084.1kbits/s speed=1.15x    &#xA;[rtp @ 0x2329380] RTP: missed 485 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1142.9kbits/s speed=1.14x    &#xA;[rtp @ 0x2329380] RTP: missed 767 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet&#xA;[rtp @ 0x2329380] RTP: missed 3 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1080.6kbits/s speed=1.14x    &#xA;[rtp @ 0x2329380] RTP: missed 1562 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1063.9kbits/s speed=1.13x    &#xA;[rtp @ 0x2329380] RTP: missed 282 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1065.8kbits/s speed=1.12x    &#xA;[rtp @ 0x2329380] RTP: missed 1 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet&#xA;[rtp @ 0x2329380] RTP: missed 771 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1024.3kbits/s speed=1.11x    &#xA;[rtp @ 0x2329380] RTP: missed 1731 packets&#xA;[rtp @ 0x2329380] max delay reached. need to consume packet bitrate=1019.1kbits/s speed=1.11x    &#xA;[rtp @ 0x2329380] RTP: missed 298 packets&#xA;&#xA;frame=  453 fps=8.9 q=-1.0 Lsize= 7397kB time=00:00:56.60 bitrate=1070.6kbits/s speed=1.11x&#xA;

    &#xA;

    After checking the video output with mpv player or ffplay ,I can observe that parameters from server caught the stream but mostly with lost packets so there are distortions in the video output file.

    &#xA;

    I tried protocol_whitelist "file,rtp,udp" for preventing packet loss but it did not work out unfortunately.

    &#xA;

    Any other parameter for solving this issue ?

    &#xA;

Navigation