Recherche avancée

Médias (91)

Autres articles (56)

  • 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

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

Sur d’autres sites (11267)

  • Low memory killer because of ffmpeg in Android

    22 avril 2021, par engineer ece

    I'm running an application in Android embedded card. The application is implemented in C. It runs an ffmpeg process using system() API which streams transport stream data over IP. When I started the application, approximately 2 hours later, low memory killer daemon is killing the background processes slowly. After some time it's killing the application also. And the GUI screen is hanged completely.
    
ffmpeg command :
    
ffmpeg -loglevel quiet -re -i "udp://192.168.47.1:8080?buffer_size=10000000&fifo_size=100000000&overrun_nonfatal=1" -map 0:p:1 -f mpegts udp://192.168.47.172:9090?pkt_size=1316

    


    low memory killer log :

    


    [ 7975.838158@2] lowmemorykiller: Killing 'droid.deskclock' (4779), adj 906,
[ 7975.838158@2]    to free 18940kB on behalf of 'kswapd0' (1978) because
[ 7975.838158@2]    cache 109744kB is below limit 114688kB for oom_score_adj 529
[ 7975.838158@2]    Free memory is 9276kB above reserved. nonmove free (32936kB),(63700kB)
[ 7976.045769@2] lowmemorykiller: Killing 'd.process.media' (4902), adj 906,
[ 7976.045769@2]    to free 23028kB on behalf of 'kswapd0' (1978) because
[ 7976.045769@2]    cache 112320kB is below limit 114688kB for oom_score_adj 529
[ 7976.045769@2]    Free memory is 5440kB above reserved. nonmove free (31148kB),(66164kB)


    


    Query :

    


      

    • Does ffmpeg consume more CPU & memory over the course of time, which in turn causing low memory killer ?
    • 


    


  • lavc/pngdec : restructure exporting frame meta/side data

    20 mars 2021, par Anton Khirnov
    lavc/pngdec : restructure exporting frame meta/side data
    

    This data cannot be stored in PNGDecContext.picture, because the
    corresponding chunks may be read after the call to
    ff_thread_finish_setup(), at which point modifying shared context data
    is a race.

    Store intermediate state in the context and then write it directly to
    the output frame.

    Fixes exporting frame metadata after 5663301560
    Fixes #8972

    Found-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavcodec/pngdec.c
  • Using ffmpeg to "re-time" an RTSP stream ?

    29 mars 2021, par Tom S

    I recently set up a birdbox in my garden, and have been using a cheapie camera that I bought, along with ffmpeg on a raspberry pi to stream from the camera to YouTube.

    &#xA;

    But YouTube keeps telling me that I am sending data too fast - multiple seconds of video per second, and at that point the stream seems to stall and I just get a buffering spinner on YouTube and have to restart ffmpeg to restore the stream.

    &#xA;

    This is happening very frequently, infact even more frequently now than when I originally got everything up and running for some reason... So much so that Ive had to setup ffmpeg to run as a service, and restart it once an hour via cron. But even this is not enough and now it seems that it can go bonkers within 10-15 minutes of a restart - almost like the more often I restart the quicker it gets...

    &#xA;

    I dont know where the issue is, or how to find it (does ffmpeg simply restream "verbatim" what ever the camera supplies ?), but I wonder if it might be possible to have ffmpeg re-time the stream so that I only send to YouTube the 25fps that it is happy with (i.e. dropping any frames in excess of this) ?

    &#xA;

    I have key frames set to 1 second on the camera.

    &#xA;

    Thanks !

    &#xA;


    &#xA;

    Here is my service file which contains the command that I use to start ffmpeg :

    &#xA;

    [Unit]&#xA;Description=BirbCam 1 streaming service&#xA;After=network.target&#xA;StartLimitIntervalSec=0&#xA;&#xA;[Service]&#xA;Type=simple&#xA;Restart=always&#xA;RestartSec=1&#xA;User=root&#xA;# Uncomment one ExecStart line below, then run `sudo systemctl daemon-reload` before restart&#xA;# With audio&#xA;ExecStart=/usr/local/bin/ffmpeg -rtsp_transport tcp -i rtsp://172.25.144.35:554/user=admin&amp;password=&amp;channel=1&amp;stream=0.sdp?real_stream -tune zerolatency -vcodec libx264 -pix_fmt &#x2B; -c:v copy -c:a aac -strict experimental -f flv rtmp://a.rtmp.youtube.com/live2/xxxx-xxxx-xxxx-xxxx-xxxx&#xA;&#xA;# Without audio&#xA;# ExecStart=/usr/local/bin/ffmpeg -f lavfi -i anullsrc -rtsp_transport tcp -i rtsp://172.25.144.35:554/user=admin&amp;password=&amp;channel=1&amp;stream=0.sdp?real_stream -tune zerolatency -vcodec libx264 -pix_fmt &#x2B; -c:v copy -c:a aac -strict experimental -f flv rtmp://a.rtmp.youtube.com/live2/xxxx-xxxx-xxxx-xxxx-xxxx&#xA;&#xA;[Install]&#xA;WantedBy=multi-user.target&#xA;

    &#xA;