Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (23)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (3639)

  • Is there a way to send ffmpeg data directly to a TCP Client ?

    3 février 2021, par KosmosisDire

    I am using ffmpeg to send screen capture directly to a C# TCP server. However, due to some bug or technical limitation, the Quest 2 (my build device) cannot bind ports. (There is very little info regarding this bug online, but as far as I can tell I can't get around it). So I cannot have a C# server on the Quest, I must have a client on the quest to receive data. However, ffmpeg sends data as a TCP client. So I need ffmpeg to act as a server.

    


    I tried sending the data through a server on my computer that then sends the data to the C# client. But I get less than 1 fps with huge lag. Normally, I get a good 30 fps with low latency when sending directly to a server.

    


    So my question :

    


    Is there a way to get ffmpeg data directly to a client, or indirectly without increasing the latency ?

    


    Here is the ffmpeg command I am using :

    


    ffmpeg -f gdigrab -i desktop -pixel_format rgb8 -video_size 896x504 -vf scale=896:504 -framerate 5 -r 30 -f rawvideo tcp://127.0.0.1:846


    


    I can include code for my C# client and server attempts as well as the middleman server, if I need.

    


    Thanks for any help !

    


  • How to extract EPG data from a rec/ts file ?

    5 janvier 2016, par wolfrevo

    I need to extract the data stream of a rec/ts file.
    What I’ve tried until now is with avconv

    avconv -i filename.rec

    I get this output

    avconv version 0.8.17-6:0.8.17-1, Copyright (c) 2000-2014 the Libav developers
    
  built on Mar 15 2015 17:00:31 with gcc 4.7.2
    
  ...
    
Input #0, mpegts, from 'filename.rec':
    
  Duration: 01:54:55.94, start: 74083.801633, bitrate: 400 kb/s
    
  ...
    
  Program 28479
    
    Metadata:
    
    ...
    
    Stream #0.0[0x475](ger): Audio: mp2, 48000 Hz, stereo, s16, 320 kb/s
    
    Stream #0.1[0x81a]: Data: [5][0][0][0] / 0x0005
    
    Stream #0.2[0x881]: Data: [11][0][0][0] / 0x000B
    
    ...

    AFIK the data stream contains the EPG information. Does it ?

    The following command

    avconv -i filename.rec -f ffmetadata metadata.txt

    outputs this to metadata.txt

    ;FFMETADATA1

    and with

    avconv -i filename.rec -map 0:1 -f ffmetadata metadata.txt

    I get the message Data stream encoding not supported yet (only streamcopy)

    The file filename.rechas following content which I would like to extract :

    enter image description here

  • H264 - how to interpret encoded video data [closed]

    30 décembre 2024, par Ragdoll Car

    I would like to know how to interpret encoded video data by H.264 codec e.g. FFmpeg's AVPacket.data.

    


    Are there any good resources about that to study ?

    


    I've been looking for the Internet, but I didn't find any documentation about H.264 format.

    


Navigation