Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (47)

  • 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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

  • Création définitive du canal

    12 mars 2010, par

    Lorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
    A la validation, vous recevez un email vous invitant donc à créer votre canal.
    Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
    A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)

Sur d’autres sites (8333)

  • dump_extradata : Insert extradata even for small packets

    14 décembre 2019, par Andreas Rheinhardt
    dump_extradata : Insert extradata even for small packets
    

    3469cfab added a check for whether the extradata coincided with the
    beginning of the packet's data in order not to add extradata to packets
    that already have it. But the check used was buggy for packets whose
    size is smaller than the extradata's size. This commit fixes this.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/dump_extradata_bsf.c
  • avformat/libsrt : small fixes in libsrt_neterrno()

    14 février 2020, par Marton Balint
    avformat/libsrt : small fixes in libsrt_neterrno()
    

    Return os error code if available, check for both SRT_EASYNCRCV and
    SRT_EASYNCSND when transforming them to EAGAIN and only display error if it is
    not EAGAIN.

    Signed-off-by : Marton Balint <cus@passwd.hu>

    • [DH] libavformat/libsrt.c
  • FFMPEG decoder only decoding correctly on small resolutions

    2 décembre 2019, par Matija Manđurov

    So I am building a encoding/decoding system with FFMPEG to use in Unity. The idea is to create an MP4 stream starting from a Texture in Unity that gets converted to an MP4 stream, gets sent over a network connection and returns to a Texture on the other side. I have a working version that handles correctly over small resolutions, and I am pretty sure its not performance related why it is falling at higher resolution. The commands are as follows :

    1) Converting textures to MP4 stream :

    "-pixel_format rgba -colorspace bt709 -f rawvideo -vcodec rawvideo -framerate {_frameRate} -video_size {_width}x{_height} -i - -pix_fmt yuv420p -f mpegts - "

    Input and Output are both using std in and std out. This creates a correct MP4 stream that I have verified is working at least as high as Full HD resolution in real time using FFPlay. So performance wise the encoder is fine.

    2) converting MP4 stream to Raw Video

    "-i - -r {_frameRate} -s {_width}x{_height} -pix_fmt yuv420p -f rawvideo - "

    the input is the incoming MP4 stream sent over the network and output is sent to std out in raw yuv420 frames. This also works in real time on small resolutions. My guess is that I am not defining the input parameters correctly since the errors are as follows.

    1) The process works with no delays with resolutions where both height and width are up to 144. For example 144x144 works perfectly, 160x144 doesn’t work. I assume that that small of a difference cannot be performance related. Is there a buffer than needs to be expanded for larger resolutions ?

    2) I noticed that the bit-rate and frame-rate of the encoder and decoder differ greatly. For example when using a 144*144 texture the bit-rate is 140 kbits/s and frame-rate is 30 (as defined by me), while the decoder for that resolutions is running at 66 frame-rate and a bit-rate of 7250 kbits/s. Again I assume FFMPEG is reading the inputting video wrong due to me falling to defined the input parameters correctly.

    3) When increasing the resolution over 144*144 I noticed that FFMPEG is outputting frames at a much higher rate. I set a system that collects data from std out and prepares a frame once it collects enough bytes. For a low resolution this is happening at exactly the frame-rate specified (in most cases 30) while as soon as the resolution is increased its outputting roughly at 200 frame-rate.

    4) Finally FFMPEG is not producing any errors and visually when I have too large of a resolution the resulting textures are distorted, looking like green static. The green I assume is from my yuv420 to RGB converter.

    In summary my main question is :

    when receiving an MP4 stream over UDP packets that are then forwarded over std in to FFMPEG how does one correctly define the input parameters to make sure FFMPEG is reading the video correctly and outputting rawvideo yuv420 frames.

    Thank you