Recherche avancée

Sur d’autres sites (5182)

• NodeJS - How to pipe same video stream to multiple clients ?

  30 août 2013, par SergioBR

  We have a situation trying to serve a video stream.

  Since HTML5 video tag does not support udp to multicast, we are trying to re-use an already converted ffmpeg stream and send it to more than one response. But that does not work.

  The first response gets the stream alright, but the second one does not.
  It seems that the stream cannot be piped out to another response, neither can it be cloned.

  Has anyone done that before ? Any ideas ?

  Thanks in advance !

  Here's the code :

  var request = require('request');
  
  var http = require('http');
  
  var child_process = require("child_process");
  
  var n = 1;
  
  var stdouts = {};
  
  
  
  http.createServer(function (req, resp) {
  
  
  
  console.log("***** url ["+req.url+"], call "+n);
  
  
  
  if (req.url != "/favicon.ico" && req.url != "/")
  
  {
  
  var params = req.url.substring(1).split("/");
  
  
  
  switch (params[0])
  
  {
  
    case "VIEW":
  
      if (params[1] == "C2FLOOR1" || params[1] == "C2FLOOR2" || params[1] == "C2PORFUN" || params[1] == "C2TESTCAM")
  
        var camera = "rtsp://192.168.16.19:554/Inter/Cameras/Stream?Camera="+params[1];
  
      else
  
        var camera = "http://192.168.16.19:8609/Inter/Cameras/GetStream?Camera="+params[1];
  
  
  
      // Write header
  
      resp.writeHead(200, {'Content-Type': 'video/ogg', 'Connection': 'keep-alive'});
  
  
  
      if (stdouts.hasOwnProperty(params[1]))
  
      {
  
        console.log("Getting stream already created for camera "+params[1]);
  
  
  
        var newStdout = Object.create(stdouts[params[1]]);
  
  
  
        newStdout.pipe(resp);
  
      }
  
      else
  
      {
  
          // Start ffmpeg
  
          var ffmpeg = child_process.spawn("ffmpeg",[
  
          "-i",camera,
  
          "-vcodec","libtheora",
  
          "-qscale:v","7",        // video quality
  
          "-f","ogg",             // File format
  
          "-g","1",               // GOP (Group Of Pictures) size
  
          "-"                     // Output to STDOUT
  
          ]);
  
  
  
          stdouts[params[1]] = ffmpeg.stdout;
  
  
  
          // Pipe the video output to the client response
  
          ffmpeg.stdout.pipe(resp);
  
  
  
      console.log("Initializing camera at "+camera);
  
      }
  
  
  
      // Kill the subprocesses when client disconnects
  
  /*
  
      resp.on("close",function(){
  
        ffmpegs[params[1]].kill();
  
        console.log("FIM!");
  
      });
  
  */
  
      break;
  
  }
  
  }
  
  else
  
  {
  
  resp.writeHeader(200, {"Content-Type": "text/html"});
  
  resp.write("WRONG CALL");
  
  resp.end();
  
  }
  
  n++;
  
  
  
  }).listen(8088);
  
  
  
  console.log('Server running at port 8088');

• REMOVE encode settings from mediainfo for H265 HEVC .mkv ? Remove Writing library ?

  13 octobre 2020, par For Fun

  I want to know how I can remove encode settings from the mediainfo with mkvpropedit or ffmpeg ?

  


  İn this post :
https://video.stackexchange.com/questions/18227/removing-mp4-encoding-information
I found this command :
ffmpeg -i INPUT -c copy -bsf:v 'filter_units=remove_types=6' OUTPUT
  
for only h264 AVC !

  


  so how can you do this for h265 HEVC ?
What command do i need to use ?

  


  İ want to remove this :

  


  cpuid=0 / frame-threads=3 / no-wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x1080 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=2 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=0 / b-pyramid / bframe-bias=0 / rc-lookahead=15 / lookahead-slices=0 / scenecut=40 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=2 / limit-refs=3 / no-limit-modes / me=1 / subme=1 / merange=57 / temporal-mvp / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=2 / selective-sao=4 / early-skip / rskip / fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=18.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00

  


• What do these two parts of libavcodec/h263data.h do exactly ?

  5 avril 2013, par Chris Lindgren

  Below are two segments of code from the FFMPEG library, specifically located here : libavcodec/h263data.h (http://ffmpeg.org/doxygen/0.6/h263data_8h-source.html).

  I would like to know more about how these two segments operate in the larger context of the codec library. Below, after these examples, I describe my understanding thus far and provide two clearer questions that I would like answers on.

  Thank you for any help !

  EXAMPLE 1

  00035 /* intra MCBPC, mb_type = (intra), then (intraq) */
  
  00036 const uint8_t ff_h263_intra_MCBPC_code[9] = { 1, 1, 2, 3, 1, 1, 2, 3, 1 };
  
  00037 const uint8_t ff_h263_intra_MCBPC_bits[9] = { 1, 3, 3, 3, 4, 6, 6, 6, 9 };

  AND EXAMPLE 2

  00039 /* inter MCBPC, mb_type = (inter), (intra), (interq), (intraq), (inter4v) */
  
  00040 /* Changed the tables for interq and inter4v+q, following the standard ** Juanjo ** */
  
  00041 const uint8_t ff_h263_inter_MCBPC_code[28] = {
  
  00042     1, 3, 2, 5,
  
  00043     3, 4, 3, 3,
  
  00044     3, 7, 6, 5,
  
  00045     4, 4, 3, 2,
  
  00046     2, 5, 4, 5,
  
  00047     1, 0, 0, 0, /* Stuffing */
  
  00048     2, 12, 14, 15,
  
  00049 };

  I understand that we're looking at a small part of the larger library of compression algorithms that affect orthogonal schemes, which predict the “correct,” or more aptly put, "original" inter- or intra-motion vectors, which are represented here in the names "ff_h263_inter_MCBPC_code," "ff_h263_intra_MCBPC_code," and "ff_h263_intra_MCBPC_bits."

  I know that the names in these two blocks of code demarcate the following :

  1. const refers to the declaration of a read only variable that can still be used outside of its scope like any other variable. The difference, stated in another way, is that the values in this array cannot be changed by any methods called outside of itself.

  2. uint8_t is an unsigned integer with a length of 8 bits that is part of a C99 standard, which is called "fixed width integer types." This particular type, an “exact width integer,” computes a range of signed or unsigned bits with a minimum value of 0 and a maximum value of 8, (i.e., the 8x8 macroblocks), which guarantees this number of bits across platforms, whether, let's say, 32-bit or 64-bit operating systems. (I researched this bit here : “Fixed width integer types” http://en.wikipedia.org/wiki/Stdint.h#stdint.h)

  3. MCBPC refers to Macroblock Type & Coded Block Pattern for Chrominance, but I don't fully understand the exact role of these particular arrays are in the scheme of the file and libavcodec. I understand more conceptually, than I do the details/number values defined in these examples.

  So, considering this, here's what I would like to know more about :

  1. Is my understanding, thus far, off in any way ?

  2. Can someone help breakdown what each code segment does ? more specifically, what do these number values signify/do in each case ?

  3. What does "Stuffing" mean ?

  Thank you, again, for any help in this matter !