Written by Chris Albrecht
Posted Thursday, December 11, 2008 at 4:36 PM PT

 

DivX Lays Off 21 People

Video codec company DivX has let go of 21 people, or roughly 10 percent of the company’s workforce in San Diego (though some of the cuts rook place globally as well), TechCrunch is reporting. A DivX spokesperson confirmed the layoffs with us via email saying “The layoff was 21 people, across multiple departments. It was driven by the economic environment.”

It’s been a tough year for DivX. The company kicked off 2008 by shuttering its video-sharing site Stage6 in February amidst increased operating expenses and pre-emptive copyright litigation. Then in November, it sued Yahoo for allegedly backing out of a toolbar marketing agreement that reportedly represented 20 percent of the company’s revenue. Oh, and its CTO resigned at the start of this month.

DivX CEO Kevin Hell stopped by our office in August to talk about the transition DivX was undergoing as it moved from a PC-based video company to platform that could play video on multiple devices (clip embedded below). Hell also said this was “win or go home” time for DivX. Unfortunately, the company sent a lot of people home.

Follow us on Twitter or subscribe to the feed

Sphere
« Previous Post Next Post »

Comments & Trackbacks

  1. [...] 21 people from its workforce, or just under 10 percent of its total staff, TechCrunch reported and NewTeeVee confirmed. The layoffs were across multiple departments and of of course, as a DivX (NSDQ: DIVX) [...]

    Paid Content : Layoffs Roundup: DivX; Fuse; ReelzChannel; Classmates.com; Exponential Interactive on December 14th, 2008 at 10:36 pm - Permalink
  2. [...] big bucks on toolbars forever in times like these. Just ask DivX Inc: The codec maker recently had to fire 21 people because Yahoo backed out of its toolbar distribution [...]

    2008: A Bloody Year for Commercial P2P « NewTeeVee on December 31st, 2008 at 9:01 pm - Permalink

Leave a reply








Safari hates me

If your comment doesn't show up immediately, it may have gotten caught in our trusty (but occasionally overly ambitious) spam filter. Please drop us a note and we'll retrieve it.