Recherche avancée

Sur d’autres sites (5946)

• getting ffmpegthumbnailer to work on heroku

  28 novembre 2013, par scientiffic

  Has anyone gotten ffmpegthumbnailer to work on heroku ? The only documentation I can find online is here :

  Using Heroku Vulcan to build lib with dependency

  And it seems like it was never answered.

  As I try to install ffmpegthumbnailer, I get the error :

  checking for FFMPEG... no
  
  configure: error: Package requirements (libavutil libavformat libavcodec >= 52.26.0 libswscale) were not met:
  
  
  
  No package 'libavutil' found
  
  No package 'libavformat' found
  
  No package 'libavcodec' found
  
  No package 'libswscale' found
  
  
  
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  
  installed software in a non-standard prefix.
  
  
  
  Alternatively, you may set the environment variables FFMPEG_CFLAGS
  
  and FFMPEG_LIBS to avoid the need to call pkg-config.

  I do have ffmpeg installed, though, which I can check with heroku which ffmpeg, which returns vendor/ffmpeg/bin/ffmpeg

  I tried adding environment variables FFMPEG_CFLAGS and FFMPEG_LIBS :

  FFMPEG_CFLAGS:   bin:vendor/ffmpeg/include:vendor/libav/include
  
  FFMPEG_LIBS:     vendor/ffmpeg/lib:vendor/libav/lib
  
  LD_LIBRARY_PATH: vendor/ffmpeg/lib:/usr/local/lib
  
  PATH:            bin:vendor/ffmpeg/bin:vendor/bundle/ruby/1.9.1/bin:/usr/local/bin:/usr/bin:/bin

  How do I get my Heroku app to recognize my installation of ffmpeg when I install ffmpegthumbnailer ?

• Adding HEVC reference decoder to ffmpeg framework

  4 mars 2014, par Zax

  I have a tweaked HM reference code of HEVC Decoder based on my requirements. I also know that FFMPEG version 2.1 onwards supports HEVC. But its a necessity for me to integrate my modified HM code.

  Hence I have gone through the post :

  http://wiki.multimedia.cx/index.php?title=FFmpeg_codec_howto

  According to this post, I need to define some functions that are needed to add a new decoder support to FFMPEG framework.

  The structure is : typedef struct AVCodec

  I have defined a structure as shown below :

  AVCodec HMHEVC_decoder =
  
  {
  
      .name           = "hmhevc",
  
      .type           = AVMEDIA_TYPE_VIDEO,
  
      .id             = AV_CODEC_ID_HMHEVC,
  
  
  
      .init           = hmhevc_decode_init,
  
      .close          = hmhevc_decode_close,
  
      .decode         = hmhevc_decode_frame,
  
  };

  However, looking at the other examples, I feel I have to add another variable like :

      .priv_data_size = sizeof(HEVCContext),

  But the problem is that I don't have any such context. So in case I don't define this, what are the things that FFMPEG framework wont provide my decoder ?

  Also is definition of this private data context compulsary ?

  What are the other fields that have to be compulsorily defined ?

  My main intention is that FFPLAY should be able to play the decoded frame.

• New Challenges

  1er janvier 2014, par silvia

  I finished up at Google last week and am now working at NICTA, an Australian ICT research institute.

  My work with Google was exciting and I learned a lot. I like to think that Google also got a lot out of me – I coded and contributed to some YouTube caption features, I worked on Chrome captions and video controls, and above all I worked on video accessibility for HTML at the W3C.

  I was one of the key authors of the W3C Media Accessibility Requirements document that we created in the Media Accessibility Task Force of the W3C HTML WG. I then went on to help make video accessibility a reality. We created WebVTT and the <track> element and applied it to captions, subtitles, chapters (navigation), video descriptions, and metadata. To satisfy the need for synchronisation of video with other media resources such as sign language video or audio descriptions, we got the MediaController object and the @mediagroup attribute.

  I must say it was a most rewarding time. I learned a lot about being productive at Google, collaborate successfully over the distance, about how the WebKit community works, and about the new way of writing W3C standard (which is more like pseudo-code). As one consequence, I am now a co-editor of the W3C HTML spec and it seems I am also about to become the editor of the WebVTT spec.

  At NICTA my new focus of work is WebRTC. There is both a bit of research and a whole bunch of application development involved. I may even get to do some WebKit development, if we identify any issues with the current implementation. I started a week ago and am already amazed by the amount of work going on in the WebRTC space and the amazing number of open source projects playing around with it. Video conferencing is a new challenge and I look forward to it.