Recherche avancée

Médias (0)

Mot : - Tags -/signalement

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (41)

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

  • Automated installation script of MediaSPIP

    25 avril 2011, par

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (3112)

  • Capture Windows screen with ffmpeg

    4 mars 2021, par kamae

    The ffmpeg is cross-platform and very powerful software to handle video/audio or to stream it.
On Linux ffmpeg can capture X11 screen with a command below :

    



    ffmpeg -f x11grab -r 25 -s cif -i :0.0 out.mpeg


    



    But is it possible to grab Windows Desktop with ffmpeg ?

    


  • FFMPEG Caption Extraction from MXF files

    4 décembre 2017, par Marian Montagnino

    SMPTE 436m captions are embedded into the MXF video as a file package on a separate stream :

    Stream #0:9: Data: none
    
Metadata:
    
  file_package_umid: 0x060A2B34010101010101012013000000E93B5AA086734ABEAE0A216F20882C49
    
  file_package_name: File Package
    
  data_type       : vbi_vanc_smpte_436M

    It seems that the data is also encoded. Is there any way to extract these captions and export either an SRT file or output the time in/out with caption text as an out stream ?

  • How To Extract RTP Packet Specific Fields From Wireshark Capture ?

    5 novembre 2014, par Lane

    I have a PCAPNG file and I need to get the RTP packets from it. Specifically, one of my RTP packets looks like...

    Frame N : X bytes on wire...

    • Ethernet II, Src : ...
    • IPv4, Src : ...
    • TCP, Src Port : rstp ...
    • RTSP Interleaved Frame, Channel : 0x02, 163 bytes
    • Real-Time Transport Protocol

    ...and what I need from each packet is...

    1. The channel from the RTSP interleaved frame
    2. The length from the RTSP interleaved frame
    3. The payload from the RTP

    ...using this data, I will re-create an audio and video file to re-construct the full video from a local payload (playback is not streaming).

    I am able to successfully get the RTP packets using either...

    tshark -r my.pcap -R -T fields -e rtp.payload -w rtp.out

    or...

    tshark -r my.pcap -R -T fields -e rtp.payload > rtp.out

    ...but the problem I am having is that the first method will save everything I need, but for some reason it will add extra data (i.e. more than just the RTP payload and RTSP interleaved frame contents) in strange places... which is preventing me from writing a program to produce the data I need to test. I attempted to remove all the extra data using several regular expressions, but there are too many different scenarios that overlap onto other valid scenarios.

    The second method will provide only the RTP payload without the interleaved properties I need (it will produce the hex with a colon between each byte, but that is easily handled). Even if I could make another call to get all the RTSP interleaved frame properties, I am going to need to combine the 2 outputs by identifying each packet using a separator / delimiter, which I’d like to avoid (I couldn’t get tshark to do that either...).

    I looked into the tshark read filters, which seems like it should be able to do what I need, but so far I haven’t been able to figure it out. Note that I am only doing this to create sample data and write the logic that formats the data required for playback. Eventually one of my co-workers will modify the streaming client to capture the data in the appropriate format (so I can simply run the data through ffmpeg without modifying it). Any ideas of how I can create the format I need ?

Navigation