Recherche avancée

Sur d’autres sites (4308)

• 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

• Live Streaming WebM with Wowza Server

  2 décembre 2010, par noreply@blogger.com (John Luther)

  Guest blogger Charlie Good is CTO and co-founder of Wowza Media Systems

  As a company, we at Wowza move fast and like to tinker. When WebM was announced in May, we saw it as a promising new approach to HTML5 video and decided to do an experiment with live WebM streaming over http.

  Adding WebM VP8 video and Vorbis audio to the other encoding formats that our server supported was easy (we designed the Wowza server to be codec-agnostic). We then created a WebMfile and implemented WebM HTTP streaming.

  We originally created the demo as a proof-of-concept for the IBC show in September, 2010 but have made it available to watch on our web site.

  The file is streamed live (more precisely, "pseudo-live") over http using the Wowza server-side publishing API (PDF). The result is very impressive ; playback starts fast and the VP8 image quality is fantastic.

  You will need a WebM-enabled browser or VLC media player 1.1.5 to view the live stream.

  If you’re interested in keeping up with Wowza’s WebM progress, visit Wowza Labs or drop us a note at info@wowzamedia.com.

  

• Evolution #4815 : Vignette des documents webp

  7 juin 2021, par JLuc -

  Sur Gandi SH, OVH Pro 2010 (comme le tiens b_b) et allwaysdata mutu, gd webp est activé.

  Le pb semble être que le fichier original du logo est affiché redimensionné (comme dans les listes) avec une largeur de 320px calculée et imposée par SPIP :
  img src="../IMG/logo/framboise.resized.webp ?1623097946" style="max-width : 320px ; max-height : 320px" alt="logo_on"

  Mais la colonne ne fait que 286px de large d’après l’inspecteur.