Recherche avancée

Sur d’autres sites (8007)

• mov : Trim dref absolute path

  16 février 2016, par Vittorio Giovara

  mov : Trim dref absolute path
  Samples produced by Omneon (Harmonic) store external references with
  
  paths ending with 0s. Such movs cannot be loaded properly since every
  
  0 is converted to ’/’, to keep the same parsing code for dref type 2
  
  and type 18 : this makes the external reference point to a non-existing
  
  direactory, rather than to the actual referenced file.
  Add a brief trimming loop that drops all ending 0s before trying to
  
  parse the external reference path.
  Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
  

  • [DBH] libavformat/mov.c

• error enoent when assigning path to ffmpeg

  12 septembre 2022, par seriously

  I am trying to set up a relay from my rtmp server and I'm using an npm module called node-media-server. I have set up my rtmp protocol successfully but when I am trying to set up the relay it expects me to add a path my my ffmpeg library so i npm installed ffmpeg then supplied the node_module path to the relay but I keep on getting error uncaughtException Error: spawn C:\blah\blah\node_modules\ffmpeg ENOENT the ffmpeg library definitely exist at the specified location. Why is this happening ? Thanks in advance.

  


  Link to the module im using : https://www.npmjs.com/package/node-media-server

  


  


  


  const NodeMediaServer = require('node-media-server');
const path = require('path')
const ffmpegPath = path.join(__dirname, '..', 'node_modules', 'ffmpeg')

const config = {
  rtmp: {
    port: 1935,
    chunk_size: 60000,
    gop_cache: true,
    ping: 30,
    ping_timeout: 60
  },
  http: {
    port: 8000,
    allow_origin: '*'
  },
  relay: {
    ffmpeg: ffmpegPath,
    tasks: [{
        app: 'live',
        mode: 'push',
        edge: 'rtmp://localhost:1936',
      },
      {
        app: 'live',
        mode: 'push',
        edge: 'rtmp://localhost:1937',
      }
    ]
  }
};

var nms = new NodeMediaServer(config)
nms.run();

  


  


  



• lavu/frame : fix malloc error path in av_frame_copy_props()

  15 décembre 2014, par wm4

  lavu/frame : fix malloc error path in av_frame_copy_props()
  The error path frees all side data, but forgets to reset the side data
  
  count. This can blow up later in av_frame_unref() and free_side_data().
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavutil/frame.c