Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×
Google Technology

Google Discontinues On2 Flix Engine Video Encoder 56 56

trawg writes "Google have recently discontinued sales of the Flix Engine, the last remnants of the purchase of On2 that they were selling directly to users. On2, developers of the VP8 video codec that formed the basis of their new WebM video format, was bought by Google early in 2010. The Flix Engine was a comprehensive API for Windows and Linux that allowed integration of On2 encoders directly into any software product. While you can still buy some On2 products from another company, it's not clear what effect this will have on Google's ultimate video strategy."
This discussion has been archived. No new comments can be posted.

Google Discontinues On2 Flix Engine Video Encoder

Comments Filter:
  • by sirsnork (530512) on Saturday December 25, 2010 @03:17PM (#34666492)
    FInal Cut Pro comes with an Apple encoder and thats the default format it saves in. Unfortunatly you can't get he codec (even for decoding) seperately from FCP, so the only way to read a Final Cut Movie without it being reencoded is by buying FCP.. and thats Mac only.... Apple don't even release the decode codec for the Apple platform. I discovered this a little while ago and was reminded just how much lock in Apple goes for.
  • by jo_ham (604554) <joham999@gmaOPENBSDil.com minus bsd> on Saturday December 25, 2010 @04:07PM (#34666658)

    Apple's codec is not necessarily the default - you get to choose what format you want your timeline to use, and what format you want an export to use (either self contained or reference).

    Back when I was doing it professionally, we were using sony's xdcam HD format right in fcp, since we were shooting on HD xdcam gear. We also had a small group of Sony z1's that shot in HDV for little projects.

    We never used apple's pro res codec, and were never forced to. If you want fcp to work in a heterogeneous editing environment then it is easy to do from a format perspective - it supports many common professional formats, as well as its own prores codec, that you do not have to use if you don't want. Even if you somehow don't pay attention and get stuck with something in that format you can use compressor to convert it into something else. Just take the generation loss as a penalty for not paying attention to what formats you were using.

  • by jo_ham (604554) <joham999@gmaOPENBSDil.com minus bsd> on Saturday December 25, 2010 @04:09PM (#34666662)

    They were dumb then. You have to specifically select prores - if you asked for something else they could easily provide it. FCP supports far more codecs than just that one.

    PEBKAC error on their part I think.

If the code and the comments disagree, then both are probably wrong. -- Norm Schryer

Working...