Slashdot Mirror
Creative Goes After Driver Modder
FreedomFighter writes "Since the release of Windows Vista, Creative has promised their Sound Cards as being 'Vista Ready'. Unfortunately, as many unlucky customers did discover, this is not true. What the users actually found were buggy, feature crippled drivers. Creative insisted that features such as Decoding of Dolby® Digital and DTS(TM) signals and DVD-Audio which worked fine in WinXP, would not work on windows Vista. With Creative releasing less than one new driver a year, things seemed bleak. Fortunately, a talented user, Daniel_K, was recently able to 'fix' many of the drivers, enabling the incompatible features and also fixing many bugs. Just today Creative has decided to put a stop to this. They removed all links to his modified drivers, and banned several users who were posting links to the now banned drivers."
Creative doing something dumb is a shock? They haven't done anything intelligent in nearly decade.
Used to be I would buy ONLY Creative sound hardware. Now I've given up after even a USB sound box of theirs didn't work, but the $15 Taiwanese ugly grey box worked fabulously with no effort, and on Linux, too.
Now they not only refuse to release decent drivers, but actively annoy those who do. What, exactly, is the value proposition here for me as a customer?
expandfairuse.org
Well done Creative. You've universally upset users, upset developers and made yourself look like petulant asshats. Did you get your panties in a bunch because a lone hacker with a binary patcher could produce better drivers than your clearly mediocre driver developers?
Well your drivers always sucked and your hardware business is being steadily eaten by rapidly improving onboard audio and much better high end audio cards. You are not long for this world.
Shamelessly stolen from bash.org
:: later ::
<booradley> I'd like to perform a one act play I call, "Creative screwed me like a bitch"
<booradley> <audigy> Buy me! I'm ever so sexy
<booradley> <boo> ok. come home with me and we'll play among the stars
<booradley> <audigy> tee hee! I love you, boo!
<booradley> <boo> I love you too, audigy
<booradley>
<booradley> <boo> there, you're all installed. how do you feel?
<neshura> down in front!
<booradley> <audigy> LET JESUS FUCK YOU! VRAAAGH!
* audience gasps.
<booradley> * audigy is putting noise across your PCI channels
<booradley> <hard drive> Mein leben!
<booradley> * hard drive has died
<booradley> <audigy> Blaaah! blaaaugh! your mother sucks cocks in hell! graaagh!
<booradley> <modem> aaieee
<booradley> *modem has died
<booradley> and the new modem I got connects at 32k tops
<Shendal> By far, that's the best one-act IRC play I've read this season. Do I smell a Tony award?
From how I read the post, Creative licensed code from third parties only for XP, not Vista. Since this code is needed to use certain functionality, this functionality is disabled on Vista. In other words, Creative's bad negotiating comes to bite their customers in the ass. How could they be this stupid -- "oh, we only licensed this stuff for Windows XP? Too bad, let the customers suck it up"
From the useless forum thread, it looks like one cowboy decided to make things easy for users suffering from Creative's ineptitude. As noble as his motives are, his methods weren't exactly legal. Looks like he was redistributing altered binary packages and asking for donations for his effort and time. I understand he was trying to help users but again his methods (and not his motives) are suspect. If Creative had any brains, they would probably hire the guy (daniel_k) as a contractor, get his contributions in, pay him a few Euro (or Yen or anything but the US$) and check that stuff into their CVS and call it their own.
This is what happens when non-technical management + legal team + marketing get together to make decisions (and it's not just Creative...). I've been using a Creative Soundblaster 5.1 Live for the last 7 years - the card cost me 25$ and I've spent over 2000$ in AGP / PCI-Express cards in the same time. I am not much of an audiophile and the card just plain bloody works. Creative makes great hardware - the whining on that forum was driver support for Microsoft Vista but that's another nightmare story...
We, at Creative, are unable to mass produce chips that differentiates themselves by its design as we used to do. A few years ago we throw all of our money making a single chip design and our bussines since then has been to ship it with a simple eeprom saying what version of our card had you bought, and enable/disable features only at driver level. So please please please stop hacking our drivers to allow the advanced functionalities work in the low level cards, because in that way nobody will buy our multihundred bucks cards.
Sincerely yours.
Creative turning to shit seems to correlate with the disappearence of it's competition.
Indeed. Instead, they bought two of the finest synthesizer and sampler vendors and sent them down the drain.
This, Creative, I will never forget. And for this simple reason you won't sell anything to me. Never.
Yes, even if you shipped it with Linux drivers...
The original SoundBlaster was basically a copy of the Adlib (a soundcard by a small American company) with digital output tacked on. Problem was the implementation was so broken it was impossible to play back audio without crackles and pops.
.. or SoundBlaster 512, they had many names for it).
The Soundblaster pro was better, but that's not saying a lot. The fact that the follow up - the Sound Blaster 16 - was NOT Sound Blaster Pro compatible is a clear indication how murky the SB Pro's underpinnings actually were.
Speaking about the SoundBlaster 16. Despite what you may believe the SB16 is NOT a 16-Bit soundcard. It can indeed play back 16-Bit samples, but the drivers simply down converts them to 12-bits.
The AWE was better but it was basically what the SB16 should have been and the competition by this time made the AWE look silly - and that is not mentioning the rather dishonest 64 simultaneous channels claim their marketing department threw about.
Creative's first attempt at a PCI soundcard turned out so murky that 1997 era mobos have something called a "SoundBlaster link" to make them happy. Finally giving up Creative bought another company that had made a PCI soundcard and slapped the SoundBlaster brand on it. (SoundBlaster 16 PCI
The SoundBlaster Live! was not PCI 2.1 complainant. If you somehow didn't know that you had to turn off PCI delayed transactions in the BIOS you would get blue screens every now and then. It also caused disk corruption on Via chipsets. Fun fun fun.
Since then the Live has been rebranded several times. They even spewed out a SoundBlaster Live 24-Bit that did the old SoundBlaster 16-Bit down sampling trick. How nice of them.
The SoundBlaster X-Fi is much nicer than the Live and the Soundcard I'm currently listening to. But beware, Creative is up to their old tricks even here. They talk a lot about their 24-Bit Crysalizer - for instance - but it is actually a 24-Bit Compressor similar to the 16-Bit compressors used by CD mastering studios. Like any audiophile can tell you a compressor helps cheepo speakers by making the sound a little more vivid and louder, at the cost of less fidelity on high end equipment.
Also note that the SoundBlaster X-Fi PCIe Xtreme Audio is not an X-Fi but a good 'ol SoundBlaster Live! in new clothes!
You might of [sic] tried to learn how to conjugate verbs in English.
The PK means the stock is traded off the pink sheets. Companies wind up there, and not on a legitimate exchange like the NASDAQ, because no CPA will sign off on their financial statement.
Must be a real open company.
after re-reading the entire thread for my amusement, I think this is not a simple case of ineptitude from Creative.
/. community are more aware then others that there is no compelling reason at all why HW from XP should not work on Vista - but there might be commerical reasons why.
after all they have the original source code and we have to assume some partway competant SW engineers.
it seems that some of what Daniel K did was reactivate some features that had been intentionally crippled from older cards.
this seems more to be nefarious decisions on backwards compatibilty and forward roadmap taken on profit grounds not technical grounds. after all, we of the
follow the logic here. a brand new and shiny OS hits the market and you need to release drivers for it. would it not be tempting to cripple some of the older cards and hence try and tease people to upgrade to the latest HW? even better you could hold back some of the features of the later versions and try to gain additional income for them in the form of top range drivers. its an insane tactic but one that is used in the field quite alot.
the bad thing is that somebody then dissassemles that code for the driver realises what has happened and then patches the removed functionality back in.
this tactic is very prevalent in the industry - by attempting to artificially shorten the product life cycle you try to force repeat purchace and then profit. when there are no more additional features you can dream up then you attempt to deprecate the original in order to force purchase of the new. Creatice make no money at all from people using old sound blaster tech on vista so they will do everything they can to halt it.
maybe I'm just being paranoid, but I see this sort of thing all the time and it make a more logical explanation to me then "large multinational cannot write new drivers even when they have the source code".
comments?
Not necessarily. The Ipod clearly has the majority market, but that didn't stop them from making a crap alternative.
I've wished since about week two of owning my Creative Zen Touch (40GB) that I had bought something else. Namely, the Ipod. Creative is a pain to deal with if you have support issues. So is their player. Disconnected three times after being on hold 17 minutes each time (HMMM....). If you just want something to listen to music with, their players will work. But don't expect any of the promised firmware updates to fix any issues with the player, so make sure you know all the current problems with it. The problems with mine? Scrolling accuracy to select songs is horrible. 10x worse than the Ipods (which is perfect). You move your finger down the strip to move the selector bar that selects songs, and the UI responds a quarter second later. On top of the that, it's inaccurate and unpredictable. Sometimes moving your finger 1mm will move the song selector one song, sometimes not at all, and sometimes it'll jump down three. You simply can't select songs safely when you're driving. In contrast, the Ipod's scroll wheel is predictable and goes where you want it. Every single time. Move thumb 1mm, it moves 1 song (or might be 2mm I don't know).
Other issues:
-after about 6 months of use the "forward/skip" [>>|] button halfway breaks. By that I mean sometimes you want to fast forward in the song (this is another frustrating thing I'll get to later) so you have to hold down the forward/skip button until the slider gets to the point in the song you want to listen to...so you let go of the fast forward, and then, strangely, the player skips to the next track. Apparently sometimes taking your finger off this button after having it held down tells the player to stop fast forwarding and skip to the end of the song.
-As for fast forwarding, it's the most un-intuitive design ever. It isn't at all easy like on the Ipod, where you press the middle button and then move your thumb around the wheel. When you do this, the Ipod moves the slider that marks what part of the song is playing. You find the part you want, stop moving your thumb on the wheel, press the middle button again, and it plays. On Creative's players, you have to press forward and hold it down for about 5 seconds to skip 30 seconds. A total PITA. Like to listen to your songs gapless (IE you've ripped a CD as one whole MP3)? Be prepared to hold that button down and watch the UI for 20 seconds--(the slider movement speed increases exponentially, which means) when you finally hit the minute mark you want to listen to, and thanks to the laggy UI, you let go and find that it keeps moving ahead for the equivalent of two-ish minutes. Then it starts playing. So until you get used to letting go early, you'll be holding "[|]" down for another 5 seconds till you get back to wherever you originally wanted to be. On top of all that, the player doesn't anticipate "jee, you know, this guy is scrolling forward and this part of the song isn't in my memory, I better spin up the harddrive to be ready for it", it waits until you've stopped fast-forwarding, and then decides to spin up the harddrive, load that part of the song, and play it. And then if you overshoot where you were fastforwarding to, it does the exact same thing, it stops spinning and waits till you've stopped rewinding to spin up the harddrive and load that part of the song (which can't be good for the harddrive anyways, I'm sure this is what broke my first harddrive in the Zen Touch. Thankfully no problems with the warrant replacement). Like I said, don't expect to use this when you're driving.
-If something about your player breaks, be prepared to pay the shipping costs [and insurance if you want to be safe] on your end as well as $35 (when mine broke this was how much it was, it has now changed to $25) as a "processing" fee.
-good luck finding player covers if you want it protected. There's two that I know of, but they're both only available online. One is leather and costs something l
I've been a long time Creative user, and they've lost me with this one. I have used Soundblaster cards since the 8-bit Soundblaster Pro. Since then I've owned the Soundblaster 16, AWE 32, and a couple cards in the Audigy series. For over 15 years, I've used Creative's cards almost exclusively (aside from a brief stint with the Pro Audio Spectrum 16).
When Vista SP1 was released last week, I didn't see it in Windows Update because the latest driver available for my Audigy 2 ZS Platinum Pro was not compatible with the update (see this KB article). This driver hasn't been updated since March 2007, and didn't work all that well to boot. Analog 5.1 surround was sketchy, and the sub channel didn't even work.
Daniel_K came to the rescue in my situation. I needed to uninstall my drivers to upgrade to SP1, then install his driver package get my card working again. The installation went very smoothly, and my card is working better than it ever has on Vista. There are some quirks, but all surround channels are working as they should, and sound quality seems to be improved over the previous drivers (although this could easily be attributed to the placebo effect).
The last thing that Creative should be doing is going after Daniel_K. If anything, they should hire the guy to teach their driver team a thing or two.
Sadly, this is not likely a technical issue, but a marketing one. Creative seems to have made a deliberate decision to leave Audigy users in the cold in an effort to get them to upgrade to their new X-Fi series. Problem is, it doesn't seem to be working. Peruse Creative's support forums and you'll see post after post lamenting their substandard driver support with promises to avoid their cards in the future.
Creative's strategy may work with casual customers with a sub-$50 card, but not for others who have invested over $200 for a high-end Audigy card with a breakout box. Those people are still looking for return on their investment, and will be the first to walk away from Creative when they get snubbed.
Hopefully this is a misunderstanding, and Creative will work out a deal with Daniel_K. If this doesn't happen, they stand to lose some of their most loyal customers. Given their track record so far, the outlook doesn't look good.