Recherche avancée

Médias (1)

Mot : - Tags -/wave

Autres articles (54)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Les statuts des instances de mutualisation

    13 mars 2010, par

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (7572)

  • How to show video (no audio) from ffmpeg via RTP in VLC ?

    15 juillet 2019, par Sagi Mann

    I’m trying to stream RTP (video only) from ffmpeg to VLC :

    ffmpeg -stream_loop -1 -i video.mp4 -vcodec copy -an -f rtp rtp://0.0.0.0:1235

    In VLC app, I do file -> "open network" and set the url to rtp ://@:1235.
    But I get an error :

    SDP required
    
A description in SDP format is required to receive the RTP stream.
    
Note that rtp:// URIs cannot work with dynamic RTP payload format (96).

    What am I doing wrong ? I see in ffmpeg’s output that SDP is being generated :

    SDP:
    
v=0
    
o=- 0 0 IN IP4 127.0.0.1
    
s=No Name
    
c=IN IP4 0.0.0.0
    
t=0 0
    
a=tool:libavformat 58.20.100
    
m=video 1235 RTP/AVP 96
    
b=AS:1205
    
a=rtpmap:96 H264/90000
    
a=fmtp:96 packetization-mode=1; sprop-parameter-sets=Z01AH9oBQBbsBEAAAAMAQAAADIPGDKg=,aO88gA==; profile-level-id=4D401F

  • Direct Show Video capture performance

    23 mai 2019, par Barry Andrews

    I originally started out looking for an example of how I can use FFMPEG in c++ builder to create an application to record from usb capture device and playback video because of apparrent poor performance

    I tried Mitov components, Datastead, FFMPEGVCL and winsoft camera which use directshow but their capture performance seemed poor.

    I need to capture 1920x1080 at up to 60fps into a compressed format and play this back later at both normal speed and slow speed.

    What I found was that DirectShow itself has a number of limitations which can be improved by adding things like FFMPEG, but ultimately PC hardware, in particular the HDD and processor limit capture capability.

    1920x1080 60fps is basically the upper end for DirectShow so you need to have best performing hardware in order to achieve this sort of performance @Spektre kindly gave me examples of DirectShow using the API direct which were good for comparison with the purchased components.

    Using this and comparing to the components I found that MITOV has a major issue with regards the larger video sizes and frame rates. Using this 1920x108 30fps and 60fps can be previewed but they have a massive delay between video feed and preview (5 or 6 seconds). The other components performed similar to the API direct method with only minor variations in performance. None were able to capture and record 1920x108 60fps with any sort of compression filter without large frame drops and very jerky preview.

  • libavdevice/gdigrab : fix ffmpeg -devices doesn't show gdigrab

    17 mai 2019, par Jun Zhao
    libavdevice/gdigrab : fix ffmpeg -devices doesn't show gdigrab

    missed the category AV_CLASS_CATEGORY_DEVICE_VIDEO_INPUT lead to
    
ffmpeg -devices doesn't show gdigrab as a input device
    

    FIx #7848
    

    Found-by : dangibson
    
Reviewed-by : Paul B Mahol <onemda@gmail.com>
    
Signed-off-by : Jun Zhao <barryjzhao@tencent.com>
    • [DH] libavdevice/gdigrab.c

Navigation