"It is a damn poor mind indeed which can't think of at least two ways to spell any word."
--Andrew Jackson

Don't forget Antares was missing from the night sky; I cling to my theory that it going supernova damaged to ozone layer sufficiently to precipitate an ice-age that dropped the ocean levels, closing Gibraltar.

When MPEG LA first announced the VP8 pool formation, a rush of companies applied to be in the pool, partly because everyone wanted to see what everyone else had. That gave way to some amount of disappointment. And by 'some amount' I mean 'rather a lot really, more than the MPEG-LA would care to admit.'

Eventually, things whittled down to a few holdouts. Those '11 patent holders' do not assert they have patents that cover the spec. They said '_may_ cover'. The press release itself repeats this. Then these patent holders said 'and we're willing to make that vague threat go away for a little cash'. Google paid the cash. This is what lawyers do.

That's why it's a huge newsworthy deal when companies like NewEgg actually take the more expensive out and litigate a patent. It is always more expensive than settling, even if you'd win the case, and very few companies are willing or able to do it. Google was probably able, but not willing.

We deal with this in the IETF all the time. Someone files a draft and a slew of companies file IPR statements that claim they have patents that 'may' read on the draft. Unlike other SDOs though, the IETF requires them to actually list the patent numbers so we can analyze and refute. And despite unequivocal third-party analyses stating 'there is no possibility patent X applies', these companies still present their discredited IPR statements to 'customers' and mention that these customers may be sued if they don't license. This is not the exception; this is standard operating procedure in the industry. These licensing tactics, for example, account for more than half of Qualcomm's total corporate income.

It's this last threat that Google paid a nominal sum to make go away. It's the best anyone can hope for in a broken system. If those 11 patent holders had a strong claim, it is exceedingly unlikely they would have agreed to a perpetual, transferable, royalty free license.

I'll add my own thoughts here, also posted at http://xiphmont.livejournal.com/59893.html

"After a decade of the MPEG LA saying they were coming to destroy the FOSS codec movement, with none other than the late Steve Jobs himself chiming in, today the Licensing Authority announced what we already knew.

They got nothing. There will be no Theora patent pool. There will be no VP8 patent pool. There will be no VPnext patent pool.

We knew that of course, we always did. It's just that I never, in a million years, expected them to put it in writing and walk away. The wording suggests Google paid some money to grease this along, and the agreement wording is interesting [and instructive] but make no mistake: Google won. Full stop.

This is not an unconditional win for FOSS, of course, the LA narrowed the scope of the agreement as much as they could in return for agreeing to stop being a pissy, anti-competetive brat. But this is still huge. We can work with this.

For at least the immediate future, I shall have to think some uncharacteristically nice things about the MPEG LA.*

*Apologies to Rep. Barney Frank"

>If you insist on recording in stereo though, you might do as they did, and record with a Mid-Side array and use a matrix to decode back to L-R, so you can control the stereo spread in post-production.

That would not have controlled the reverb; the space this was recorded in was a concrete floor with concrete walls and no acoustic treatment. Like I said, it was a tradeoff, and one that was successful if not perfect.

Oh! And 'linear' was completely wrong. I don't know how I braino-ed that in there, the [at very least perceived] distortion/noise tradeoff is not linear.

Right, and this is why dither is only applied to 'last-mile' audio intended to be consumed. Dither 'screws' you in other ways if you intend to use that audio in production, such as losing all the property of removing the distortion, yet still having the additive noise. But we're still talking about changes 100+dB down.

>Counter nitpick: Monty, as a professional motion picture sound designer, I cannot tell you how distracting it is to hear your voice constantly changing its pan across the stereo field :)

The audio was recorded with a stereo pair. It wasn't panned artificially :-) Look down a few comments for more about this, you weren't the only person to complain.

I think it's more "I want people to know why I do the stupid things I do." Latent fear of being committed.

As a nitpick, you get dithering losses _or_ quantization distortion, or a linear tradeoff between the two. You don't get the worst case of both on top of each other unless you screw up.

Without dither, worst case, all your 16 bit quant distortion products will be under -100dB regardless of input amplitude. I actually display the worst case in the video to make it easy to see. Quantization distortion aliases, and I chose an integer sample period so the aliased distortion would always land in the same bins after folding. If I hadn't, it would have spread out more and been even lower. If I had chosen a relatively prime frequency, the quantization distortion would have spread out across all bins equally.

> Stop using cdparanoia - it isn't very good, at all. It tests poorly, we're sad to say.

Really! As the author, I'd love to hear hard specifics. or maybe a bug report.

> You want to use Secure Mode with NO C2, accurate stream, disable cache.

You can't disable the cache on a SATA/PATA ATAPI drive. The whole point of cdparanoia's extensive cache analysis is to figure out a way to defeat the cache because it can't be turned off. There is no FUA bit for optical drives in ATA or MMC.

The 'accurate stream' bit is similarly useless (every manufacturer interprets it differently) and C2 information is similarly untrustworthy.

Plextors are not recommended for error free or fast ripping. They try to implement their own paranoia-like retry algorithm in firmware and do a rather bad job about it. They also lie about error correcting information (you do not get raw data, you get what the drive thinks it has successfully reconstructed). Plextors often look OK on pristine disks, but if you hit a bit error (like on just about any burned disk), you don't know what it's going to do. Plextors are, overall, among the more troublesome drives _unless_ you're using a ripper that does no retry checking (ie, NOT cdparanoia and NOT EAC). If you use iTunes, you want a Plextor. Otherwise, avoid them.

That was true ~15 years ago. Since then, Plextor's firmware gets along very badly with the rippers that try to be frame accurate, because Plextor tries to implement a much lighter-weight more error prone version of the same algo on the drive. The drive still doesn't do a realiable job, and it seriously mucks up the ripper.

Your id isn't from 97 as some others have already pointed out. I think it was late 97 early 98 when the registration system was implemented. I think I waited a while before registering and still have a four digit one. People liked the anonymity of the original site, heh.

Yeah, you don't want to mess with neutron sources. Fast neutrons penetrate lots of materials (due to the lack of charge), much like gammas, and can produce short-lived isotopes that continue to decay after the source has been removed.