Recherche avancée

Sur d’autres sites (6836)

• Giving Thanks For VP8

  25 novembre 2010, par Multimedia Mike — VP8

  It’s the Thanksgiving holiday here in the United States. I guess that’s as good a reason as any to release a first cut of my VP8 encoder. In order to remind people that they shouldn’t expect phenomenal quality from it — and to discourage inexperienced people from trying to create useful videos with it — I have hardcoded the quantizers to their maximum settings. For those not skilled in the art, this is the setting that yields maximum compression and worst quality. When compressing the Big Buck Bunny logo image, the resulting file is only 2839 bytes but observe the reconstructed quality :

  
  
  It really just looks like a particularly stormy day in the forest.
  

  First VP8 File From An Independent Encoder
  I found a happy medium on the quantizer scale and encoded the first 30 seconds of Big Buck Bunny for your inspection. I guess this makes it the first VP8/WebM file from an independent encoder (using FFmpeg’s Matroska muxer as well).

  Download : bbb-360p-30sec-q40.webm ( 13 MBytes)

  I think the quality makes it look like it was digitized from an old VHS tape.

  For fun, here’s the version with the quantizer cranked to the max : bbb-360p-30sec-q127.webm ( 1.3 MBytes)

  Aside : I was going to encapsulate the video in this post using a bare HTML5 <video> tag for the benefit of the small browsing population who could view that (indeed, it works fine in Chrome). But that would be insane due to the fact that supporting browsers preload the video with no easy (read : without the help of JavaScript) method for overriding this unacceptable default.

  The Code
  I’m still trying to get over my fear of git. To that end, I have posted the code on Github :

  https://github.com/multimediamike/ffvp8enc

  I still don’t like you, git. But I’m sure we’ll find some way to make this work.

  Other required code changes in the basic FFmpeg tree :

  • Of course, copy vp8enc.c into libavcodec/
  • In libavcodec/allcodecs.c, ’REGISTER_DECODER (VP8, vp8);’ turns into ’REGISTER_ENCDEC (VP8, vp8);’
  • Add ’OBJS-$(CONFIG_VP8_ENCODER) += vp8enc.o’ to libavcodec/Makefile

  Further Work
  About the limitations and work yet to do :

  • it’s still intra-only, no interframes (which is where a lot of compression occurs)
  • no rate control or distortion optimization, obviously
  • no intra 4x4 coding (that’s close to working but didn’t my little T-day deadline)
  • no quantization control ; this should really be hooked up to the FFmpeg command line but I’m not sure how
  • encoder writes into a static-sized, 1/2 MB memory buffer ; this can overflow
  • code is a mess (what did you expect at this stage of the game ?)
  • lots and lots of other things, surely

• RoR ffmpeg installed by brew

  26 octobre 2012, par Thomas Kobber Panum

  I'm developing a Ruby on Rails application that needs ffmpeg, to do some processing of the files I have.

  However, when trying to use ffmpeg, I get this error

  Failed encoding. Errors: no output file created. Full output: dyld: Library not loaded: /usr/local/lib/libogg.0.dylib
  
  Referenced from: /usr/local/bin/ffmpeg
  
  Reason: Incompatible library version: ffmpeg requires version 9.0.0 or later, but libogg.0.dylib provides version 6.0.0

  It's a basically a CarrierWave project, which can be seen here : http://www.freezzo.com/2010/12/23/create-ffmpeg-processor-for-carrierwave-in-rails-3/

• Studying A Game Wave Disc

  23 novembre 2010, par Multimedia Mike — Game Hacking

  I picked up a used copy of game called Gemz — a rather flagrant Bejeweled clone — for a game console called Game Wave Family Entertainment System. Heard of it ? Neither had I. But the game media is optical, so I had to get it and study it.

  
  
  

  When mounted in Linux (as UDF), the disc is reported to contain 2.8 GB of data, so it has to be a DVD. 810 MB of that is dedicated to the movies/ directory. Multimedia format ? Just plain, boring MPEG files (very YouTube-friendly— here’s the opening animation). Deeper digging reveals some more subdirectories called movies/ that, combined, occupy the lion’s share of the disc space. Additionally, there are several single-frame .m2v files in a directory called iframes/ which are used to encode things like load screens.

  
  
  

  There are more interesting data files including .zbm files for images and fonts, and .zwf files for audio. I suspect that these stand for zipped bitmap and zipped wave file, respectively. They can’t be directly unzipped with ’gunzip’. Some of the numbers at the start of some files lead me to believe they can be easily decompressed with standard zlib facilities.

  Based on the binary files on the Gemz disc, I couldn’t find any data on what CPU this system might use. A little Googling led me to this page at the Video Game Console Library which pegs the brain as a Mediamatics 6811. Some searching for that leads me to a long-discontinued line of hardware from National Semiconductor.

  The Console Library page also mentions that the games were developed using the Lua programming language. Indeed, there are many Lua-related strings in the game’s binaries (’zlib’ also makes an appearance).