Recherche avancée

Sur d’autres sites (10549)

• Why does my Blink based browser play hide and seek ?

  21 janvier 2016, par Caius Jard

  We have a C# tool (that I wrote) that records online broadcasts taking place a custom written (that we wrote) flash app. (There are no DRM or copyright issues here.)

  We’ve coded up a system whereby this tool is installed on a Windows Server 2012 R2 Amazon AWS instance. After we boot the instance, the tool loads, waits for the right time to start recording, launches a browser and passes the command line argument of the URL to access the broadcast. The browser will then load the flash app and the interview audio and video will start arriving at the browser instance on AWS

  By way of a virtual audio cable driver, screen / audio capture directshow filters and ffmpeg a screen recording is taken. The C# tool calls ffmpeg and ffmpeg will record the screen reliably for the entire interview, then the tool shuts the whole thing down

  The problem I’m having is that both Chrome and Electron browser sometimes simply don’t draw themselves on the screen so all ffmpeg ends up recording is a blank desktop and the audio of the broadcast (hence, the browser IS running)

  We found this out when recordings started turning up with X hours of merely recording the windows desktop and the tool’s main window with a countdown timer.

  A screenshotting facility was built into the tool and added to its web control interface, and this way we can test whether the browser is visible - a human looks at the screenshot of every broadcast, just after recording has started (the browser is supposed to be on show by this time)

  We notice that 50% of the time, the browser isn’t drawing itself on screen. By 50% I mean that every other recording that the AWS instance carries out, will be blank : AWS starts, records ok, shuts down. AWS starts again an hour later for a different broadcast, recording is blank, shuts down.. Starts/ok/shutdown. Starts/blank/shutdown. Repeat ad infinitum

  What’s even more strange is that if I run VNCviewer on my dev machine and connect up to an instance that is having a problem, the instant that the VNC connection is up and the remote desktop is showing on my screen, the browser suddenly appears as if nothing was ever wrong. A screenshot from before the VNC connect shows blank desktop, connect VNC, take another screenshot and the browser is there. All through it the audio is fine - the browser connected to the boadcast is fine, for sure

  It’s as though Chrome/Electron thinks "you know what, noone is looking at me so I’m not going to bother drawing myself". No screen saver is set, though the power plan has the setting "turn off the display after 15 minutes".

  Perhaps Chrome/Electron have a test amounts to "if the display is off, don’t draw". I can’t explain the inconsistency though - the recorder launches at least 1 hour before it’s needed, and sits there idle until it’s time to start the browser. You’d hence imagine that the "power off the monitor after 15 mins" setting would reliably have ensured the "monitor" is "off" by the time every recording start comes around

  This behaviour doesn’t happen with any of the other browsers (but unfortunately the app doesn’t and cannot work in them because it uses some weird chrome-only technology/API).

  Can anyone suggest anything to look at to help debug this, or anything I can build into the C# tool to overcome the problem ? Coding it up to connect to itself via VNC for a few seconds after it has launched the browser.. Well that just tastes nasty.

  Naturally, as soon as I connect to the machine via VNC (rather than RDP - RDP isn’t usable because the recording context is in a logged on session for a particular user) the problem goes away, which makes it frustratingly hard to debug.

• Converting a H.264-Stream with node.js using fluent-ffmpeg

  10 novembre 2014, par Andreas Lackner

  I want to convert a H.264 stream (provided by a foscam via RTSP) into a ogg-stream (via HTTP) using node.js and ffmpeg.
  So far I tried it with VLC, wich works fine. But VLC needs too much CPU power.

  I’ve tried the following :

  var ffmpeg = require('fluent-ffmpeg');
  
  var http = require('http');
  
  
  
  http.createServer(function (req, res) {
  
      var command = ffmpeg();
  
      command.input('rtsp://user:password@foscam.example.com:88/videoMain');
  
      command.inputFormat('rtsp');
  
      command.videoCodec('libtheora');
  
      command.audioCodec('libvorbis');
  
      command.toFormat('ogg');
  
  
  
      console.log('New Request');
  
      res.writeHead('200', {
  
          'Content-Type' : 'video/ogg',
  
          'Connection' : 'keep-alive',
  
          "Accept-Ranges" : "bytes"
  
      });
  
      command.on('error', function(err, stdout, stderr) {
  
            console.log("error:"+err);
  
            console.log('ffmpeg stdout: ' + stdout);
  
            console.log('ffmpeg stderr: ' + stderr);
  
          });
  
      command.output(res);
  
  }).listen(8080, 'localhost');

  If I try to open the stream with VLC, I don’t get any response.
  Does anybody know what’s wrong ?

• Thread count option in FFmpeg for FASTEST conversion to h264 ?

  9 février, par S B

  I need to maximize speed while converting videos using FFmpeg to h264

  



  

  • Any input format of source videos

  


  • User's machine can have any number of cores

  


  • Power and memory consumption are non-issues

  


  



  Of course, there are a whole bunch of options that can be tweaked but this question is particularly about choosing the best -thread <count></count> option. I am trying to find an ideal thread count as a function of

  



  

  • no. of cores

  


  • input video format

  


  • h264-friendly values maybe ?

  


  • anything else missed above ?

  


  



  I am aware the default -thread 0 follows one-thread-per-core approach which is supposed to be optimal. But I am not sure if this is time or space-optimized. Also, on certain testcases, I've seen more threads (say 4 threads on my dual core test machine) finishes quicker than the default.

  



  Any other direction, say configure options w.r.t. threads, worth pursuing ?