Turtle Beach has just announced the Turtle Beach Earforce X12; successor to the X11. For those that don't know the X11 is currently one of the most successful budget high-end headsets for the Xbox 360. They're pretty spiffy actually. Audiophiles won't find the X11 impressive compared to some of Turtle Beach's fancier offerings, but they're beyond practical for anyone just looking to play online games. The X12 is set to release some time in the fall and will feature a price tag of 59.99 in US dollars. Price-wise it's only a small step up from what the X11 is currently selling for.
The X12 will boast a number of improvements to the old model. One thing they worked in is "Microphone Monitoring." The idea is that you can hear and be aware of the volume of your own voice through the speakers. Not a bad idea. That aside the most important thing is that the X12 will sport 50mm speakers. Supposedly that's huge for a gaming headset and they'll provide "superior audio quality with crisp highs and deep, rumbling lows." So yeah, basically it's gonna be an X11 with better sound quality and some new features. I'm quite seriously considering the upgrade myself.
Honestly if you've never gotten a gaming headset before it's worth looking into. This sucker may well be worth reserving since we don't know exactly when its launching or how readily it will be available. That's a really good price tag if the sound quality is improved as much as Turtle Beach is claiming. Here's the rundown on the X12's features:
· Amplified stereo audio for crisp highs and deep lows
· Premium 50mm speakers for highest fidelity sound
· Variable Bass Boost adds depth and realism to the game audio
· In-line amplifier that allows for independent control of chat, bass and game volume
· Microphone Monitoring so you never have to raise your voice to hear yourself
· Completely powered by USB so you will never need replacement batteries
· Lightweight design with breathable, fabric mesh ear cushions for enhanced comfort
· Fully-compatible with the DSS 7.1 Surround Sound Processor
can cause it. You can fix it by adding *.disqus.com to your whitelists.