Quote:
Originally Posted by ardeegee
If I remember right (now depending on old memories, not google) Divx  was the hack of the Microsoft MP4 codec. They then made a "clean room" version Divx when they wanted to go commercial. xviD forked off the open source Divx when Divx went closed source-- but I don't remember if xviD comes from the hacked MS code or the "clean room" code.
If you are talking about AutoGK, and it worked the same way then that it works now (first demux AC3, then convert it to MP3, then test compressibility of video, then run two encoding passes) that's 5 steps slowing it down. When I first started creating Divx files using DeCSS and Flask, it did a 1-step conversion-- and took over 24 hours to convert a typical movie at 320x240. Uphill both ways, in the snow. (This was on an AMD K6-2 400 MHz.) |
Yeah, XVID was the fork of the DIVX project, and all this is just so full of memories I'm feeling misty
I remember Flask and DECSS and TMPGENC before that for doing VCD's and then KVCD's and then SVCD, but the one I cut my teeth on was the original GK, without the Auto part (AutoGK still works now) you had to do all the separate steps one after the other and then run compressibility tests and apply filters, man it was protracted. And if I'm recalling correctly the first movie I ever converted was the Matrix and I had a 20GB hd
Now I can do 720p real time from Blu-Ray dumps on my video encoding rig
I'm hoping that WebM becomes ubiquitous as a delivery format, because we've not had any kind of official video standard as yet. The next step is to see if the file sharers jump on this. Once they do, it'll take off in leaps and bounds (even though I'm reading it's technologically inferior to h264).