Recherche avancée

Médias (0)

Mot : - Tags -/alertes

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (68)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • 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" (...)

  • 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 (...)

Sur d’autres sites (9420)

  • Anomalie #4717 : Erreurs nombre d’argument des filtres

    10 mai 2021, par jluc -

    Suite aux commentaires, voici la nouvelle PR : https://git.spip.net/spip/spip/pulls/170

  • While converting rtsp broadcast to rtmp in ffmpeg, I send it to the server, how can I send it in base64 format ?

    15 septembre 2021, par Ali Gökkaya

    While converting rtsp broadcast to rtmp in ffmpeg, I send it to the server, how can I send it in base64 format ?

    


    the pipeline i use :

    


    ffmpeg -i rtsp://<ip>:8080/h264_ulaw.sdp -c:v copy -an -f flv rtmp://<server>:1935/server/show1"&#xA;</server></ip>

    &#xA;

    how do i stream this code with base64 ?

    &#xA;

  • When I use Fluent-Ffmpeg to access Ffmpeg, there are two different threads but I dont want it

    25 mars 2019, par Ahmet Hakan Billur

    I try to broadcast with rtsp live stream from IP camera on web app that is improved with node.js-jsmpeg([a link]https://www.npmjs.com/package/fluent-ffmpeg !), web socket, html5(canvas).Everything ok that live streaming works but missing frame and high CPU usaged by streaming on web app and I try to reduce so I can intervene ffmpeg with fluent-ffmpeg but when I monitor CPU usaged I can see there 2 different threads following as and look at screenshot of CPU ;
    enter image description here

    ffmpeg -rtsp_trasport tcp -i rtsp ://10.6.0.225 -f mpeg1video - is worked by jsmpeg and canvas/html5
    index.html

        
    

    
    
    
    
    
    
    
    
    

    
    <div><canvas width="640" height="360"></canvas></div>
    
    div><canvas width="640" height="360"></canvas>  
    
    <code class="echappe-js">&lt;script type=&quot;text/javascript&quot; src='http://stackoverflow.com/feeds/tag/jsLib/jsmpeg.js'&gt;&lt;/script&gt;
    
    

    &lt;script type=&quot;text/javascript&quot; src='http://stackoverflow.com/feeds/tag/jsLib/ffmpegUtil.js'&gt;&lt;/script&gt;
    

    &lt;script type=&quot;text/javascript&quot;&gt;<br />
    
      var canvas = document.getElementById('videoCanvas');<br />
    
      var ws = new WebSocket(&quot;ws://10.6.0.206:9999&quot;)<br />
    
      var player = new jsmpeg(ws, {canvas:canvas, autoplay:true,audio:false,loop: true});<br />
    
    &lt;/script&gt;

    other one /usr/bin/ffmpeg -i rtsp ://10.6.0.225 -y out.ts is work by following piece of code in app.js

    Stream = require('node-rtsp-stream');
    
stream = new Stream({
    
    name: 'name',
    
    streamUrl: 'rtsp://10.6.0.225',
    
    wsPort: 9999
    
});
    

    
var ffmpeg = require('fluent-ffmpeg');
    
var proc = new ffmpeg();
    

    
proc
    
.addInput('rtsp://10.6.0.225')
    
.on('start', function(ffmpegCommand) {
    
    /// log something maybe
    
    console.log('start-->'+ffmpegCommand)
    
})
    
.on('progress', function(data) {
    
    /// do stuff with progress data if you want
    
    console.log('progress-->'+data)
    
})
    
.on('end', function() {
    
    /// encoding is complete, so callback or move on at this point
    
    console.log('end-->')
    
})
    
.on('error', function(error) {
    
    /// error handling
    
    console.log('error-->'+error)
    

    
})
    
.output('out.ts')
    
.run();

    and then I don’t want to get two different ffmpeg command threads in there.
    Does anyone have an idea ?
    Thanks in advice.

Navigation