Recherche avancée

Médias (91)

Autres articles (71)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (7066)

  • Connecting IP Camera with YouTube using FFMPEG

    19 novembre 2022, par vcima

    I´m trying to connect my ip camera with Youtube using ffmpeg to convert the stream from RTSP to RTMP.

    


    rtsp_url="rtsp://xxxxxx"
rtmp_url="rtmp://xxxxxx"

ffmpeg -rtsp_transport tcp -i $rtsp_url -tune zerolatency -vcodec libx264 -pix_fmt + -c:v copy -c:a aac -strict experimental -f flv $rtmp_url


    


    This works fine, but I have several problems that I don't know how to solve.

    


      

    1. Sometimes, for different reasons, I lose the connection with the camera : stoppage during the night, coverage problems... and I don't want the process disconnect from Youtube. How could I do it ? Could I put a default image while there is no connection to the camera ?

      


    2. 


    3. The last question would be. How can I guarantee that the Youtube player id associated with the process is always the same. It is quite inconvenient to have to update the player every time there is a connection problem.

      


    4. 


    


    Regards

    


  • FFmpeg child process closed, code null, signal SIGSEGV

    22 novembre 2022, par AMRITESH GUPTA

    I have been working on a project where I am trying to get users' audio and video and stream it to youtube live. I tested my code on my windows machine, and everything is working fine, but when I deploy my server code on Heroku, I get this error FFmpeg child process closed, code null, signal SIGSEGV.

    


    I used https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git for Heroku buildpack.

    


    Code snippet :

    


    const inputSettings = ['-i', '-', '-v', 'error'];

const youtubeSettings = () => {
    
    return [
        // video codec config: low latency, adaptive bitrate
        '-c:v',
        'libx264',
        '-preset',
        'veryfast',
        '-tune',
        'zerolatency',
        '-g:v',
        '60',
  
        // audio codec config: sampling frequency (11025, 22050, 44100), bitrate 64 kbits
        '-c:a',
        'aac',
        '-strict',
        '-2',
        '-ar',
        '44100',
        '-b:a',
        '64k',
  
        //force to overwrite
        '-y',
  
        // used for audio sync
        '-use_wallclock_as_timestamps',
        '1',
        '-async',
        '1',
  
        '-f',
        'flv',
        youtubeURL,
      ]
    
}

const ffmpegInput = inputSettings.concat(youtubeSettings());


io.on('connection', (socket) => {
    console.log(`socket connected to ${socket.id}`)
    
    try{

    const ffmpg = child_process.spawn('ffmpeg',ffmpegInput)

    ffmpg.on('close', (code, signal) => {
        console.log(
          'FFmpeg child process closed, code ' + code + ', signal ' + signal
        );
        // ws.terminate()
      })

    ffmpg.stdin.on('error', (e) => {
        console.log('FFmpeg STDIN Error', e)
    })

    // FFmpeg outputs all of its messages to STDERR.  Let's log them to the console.
    ffmpg.stderr.on('data', (data) => {
        console.log('FFmpeg STDERR:', data.toString());
    })

    socket.on('message', (msg) => {
        console.log('DATA', msg)
        ffmpg.stdin.write(msg);
    })

    // If the client disconnects, stop FFmpeg.
    socket.conn.on('close', (e) => {
        console.log('kill: SIGINT')
        ffmpg.kill('SIGINT')
    })
}
catch(err){
    console.log(err);
}


    


    Heroku logs

    


    enter image description here

    


  • Youtube DL Unable to get local issuer certificate - CERTIFICATE_VERIFY_FAILED

    24 novembre 2022, par Casper Kristiansson

    I'm trying to use youtube DL with FFmpeg to download an m3u8 stream. Just recently I started receiving this error :

    


    ERROR: Unable to download webpage: <urlopen error="error" verify="verify" unable="unable" to="to" get="get" local="local" issuer="issuer" certificate="certificate">&#xA;(caused by URLError(SSLCertVerificationError(1,&#xA;&#x27;[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:&#xA;unable to get local issuer certificate (_ssl.c:992)&#x27;)))&#xA;</urlopen>

    &#xA;

    I know Youtube DL supports an option for nocheckcertificate but by enabling this after a couple of minutes the target machine will refuse the connection. When trying to use the same m3u8 stream on another computer, I could download the stream without any issues.

    &#xA;

    I know that someone from Youtubedl CERTIFICATE_VERIFY_FAILED suggested fixing "your system's CA certificate list". What is the process of doing this ?

    &#xA;

    I tried upgrading/reinstalling python and reinstalling the latest Windows update

    &#xA;

    I also want to mention that there hasn't been any issue with downloading for the past year but recently stumbled upon this when switching proxy providers. But because the same setup works on another PC without any issue it's probably not the reason.

    &#xA;

    The system the program is running on is Windows

    &#xA;

    Edit : Another note is that downloading other public m3u8 streams works perfectly fine, so the problem is probably with the system CA SSL.

    &#xA;