Recherche avancée

Sur d’autres sites (12588)

• Streaming converted movie with mp4 container in NodeJS, movie playing very fast

  20 septembre 2016, par Mustafa

  I have used stream-transcoder module to convert a file make it a stream. So the file is not stored, it is on the fly.

  app.get("/video", function(req,res){
  
      res.writeHead(200, {'Content-Type': 'video/mp4'});
  
      var src = "movie.avi";
  
  
  
      var Transcoder = require('stream-transcoder');
  
      var stream = fs.createReadStream(src);
  
      new Transcoder(stream)
  
          .maxSize(1280, 720)
  
          .videoCodec('h264')
  
          .videoBitrate(800 * 1000)
  
          .fps(25)
  
          .sampleRate(44100)
  
          .channels(2)
  
          .audioBitrate(128 * 1000)
  
          .format('mp4')
  
          .on('finish', function() {
  
              console.log("finished");
  
          })
  
          .stream().pipe(res);
  
  });

  It works nicely, it is fast, but too fast, the audio is played at the same speed, however the video does not respect the frame rate, whatever is recieved from ffmpeg is immeidately shown, fastly. Additionally, it does not show the total time, I believe it is the problem. I need to somehow specify the length, framerate, but I could not find enough information on that. I thought the stream recieved from ffmpeg should contain that. And I could not find respective headers for that in HTTP.

  Here are the flags that this stream-transcoder module uses for MP4 :

  [ '-i',
  
    '-',
  
    '-vf',
  
    'scale=min(trunc(1280/hsub)*hsub\\,trunc(a*720/hsub)*hsub):min(trunc(720/vsub)*vsub\\,trunc(1280/a/vsub)*vsub)',
  
    '-vcodec',
  
    'h264',
  
    '-b:v',
  
    800000,
  
    '-r',
  
    25,
  
    '-ar',
  
    44100,
  
    '-ac',
  
    2,
  
    '-ab',
  
    128000,
  
    '-f',
  
    'mp4',
  
    '-movflags',
  
    'frag_keyframe+faststart',
  
    'pipe:1' ]

  When I use VP8 encoder and WebM, it works nicely, the time is displayed, video plays normal speed.

• What are some NPAPI video plugin alternatives for Chrome ?

  14 janvier 2014, par ElHaix

  Was : "PPAPI (Pepper) video plugin -NaCl module failed - how to resolve ?"

  Google's Say Goodbye to Our Old Friend NPAPI blog post indicates that NPAPI plugin support will cease by the end of 2014 (in favor of PPAPI).

  We have considered the option of using the ffmpeg libraries to create our own video plugin to simply decode RTSP encoded H.264 video streams on the client - important because we need as near real-time video display (avoiding transcoding latency). Using the ffmpeg libraries, there is still a 3-5 second delay in decoding the stream, not as fast as running MPlayer with the -benchmark option.

  In trying Google's PNaCl recommendation, we just got the LOADING status and the following error :

  NativeClient : NaCl module load failed : PnaclCoordinator : Compile
  process could not be created : ServiceRuntime : failed to start

  We don't need an encoder, simply decoding the incoming stream to images would be fine - or other suggestions ?

  What are some NPAPI alternatives to solve this problem ?

• use AForge.Video.FFMPEG.dll to grab video thumbnail

  5 avril 2015, par Sean

  I am using AForge.Video.FFMPEG.dll to grab video thumbnail on website, it will be shown on webpage or other clients. I downloaded latest version of the dll and related native library into /bin folder and copied to system32 folder as well.

  but when I compiled the project, it will told me :
  "
  Could not load file or assembly ’AForge.Video.FFMPEG.DLL’ or one of its dependencies. The specified module could not be found.
  "

  1. I copied all DLLs
     

  2. All DLLs are 32bit, not x64 bit.

  3. I saw another article to introduce how to load native c or managed c++ library in asp.net, but doesn’t work for me.
     http://blogs.msdn.com/b/jorman/archive/2007/08/31/loading-c-assemblies-in-asp-net.aspx

  4. My developing environment : Windows2012R2 VS2010

  5. When I was compiling the project, compiler will throw above exception.

  Thanks,

  Sean