Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (106)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

Sur d’autres sites (10637)

  • Not best results for [screen capture] streaming with ffmpeg js

    13 mai 2021, par Nikola Lukic

    Platform : Windows 10
Ffmpeg version 4.4-full_build-www.gyan.dev

    


    This app works fine on macos.

    


    node websocket-relay.js supersecret 8081 8082

http-server --host=https://localhost --port 8080

ffmpeg -f  gdigrab  -i desktop -framerate 30 -video_size 640x480 -f mpegts -codec:v mpeg2video -s 640x480 -rtbufsize 100M -b:v 1000k -bf 0 http://localhost:8081/supersecret


    


    Logs :

    


    frame= 5515 fps= 20 q=31.0 size=    8302kB time=00:04:36.20 
frame= 5526 fps= 20 q=31.0 size=    8317kB time=00:04:36.77 
frame= 5537 fps= 20 q=31.0 size=    8331kB time=00:04:37.31 
frame= 5548 fps= 20 q=24.8 size=    8346kB time=00:04:37.87 
frame= 5558 fps= 20 q=31.0 size=    8352kB time=00:04:38.37 
frame= 5569 fps= 20 q=31.0 size=    8368kB time=00:04:38.91 
frame= 5579 fps= 20 q=31.0 size=    8382kB time=00:04:39.41 
frame= 5590 fps= 20 q=31.0 size=    8397kB time=00:04:39.97 
frame= 5600 fps= 20 q=31.0 size=    8411kB time=00:04:40.48 


    


    Finally in my browser i got something like that :

    


    enter image description here

    


    Any suggestion !
I am new for ffmpeg topic...

    


  • How to convert cctv footage to h265 for streaming and recording in nginx-rtmp module ?

    6 avril 2021, par Joram

    I am using the nginx-rtmp-module here to pull an rtsp stream from a camera on local network and convert it to rtmp. This rtmp stream is then converted to hls and made available for livestreaming. It is also being recorded in 5 min segments. (these things can all be seen in the nginx.conf below).

    


    I want to change the video codec to h265 to save storage space, since each 5 min video is ~230mb, and using opencv and python, I was able to get <100mb per 5 min video using h265, so I know there is a lot of space for storage saving.

    


    How can I change the codec of the stream to h265 ?

    


    I have tried installing libx265-dev and setting -vcodec libx265, however this tells me flv is an invalid container and I'm getting nowhere with finding a valid container for streaming + recording.

    


    My nginx.conf :

    


    rtmp {
    server {
        listen 1935; # Listen on standard RTMP port

        application relay {
            
            live on;

            hls on;
            hls_path /tmp/hls;
            hls_fragment 15s;


            exec_static /usr/bin/ffmpeg -i rtsp://test:test@192.168.100.10:8554/fhd -vcodec copy -f flv rtmp://localhost:1935/relay/fhd; 

            # record block  
            record video;
            record_path /tmp/hls;
            record_unique on;
            record_interval 5m;
        }
    }
}


    


  • avformat/wavenc : Fix leak and segfault on reallocation error

    22 février 2021, par Andreas Rheinhardt
    avformat/wavenc : Fix leak and segfault on reallocation error
    

    Up until now, the wav muxer used a reallocation of the form ptr =
    av_realloc(ptr, size) ; that leaks upon error. Furthermore, if a
    failed reallocation happened when writing the trailer, a segfault
    would occur due to avio_write(NULL, size) because the muxer only
    prints an error message upon allocation error, but does not return
    the error.

    Moreover setting the pointer to the buffer to NULL on error seems to
    be done on purpose in order to record that an error has occured so that
    outputting the peak values is no longer attempted. This behaviour has
    been retained by simply disabling whether peak data should be written
    if an error occurs.

    Finally, the reallocation is now done once per peak block and not once
    per peak block per channel ; it is also done with av_fast_realloc and not
    with a linear size increase.

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

    • [DH] libavformat/wavenc.c