Re: WMP10 / WMA9.0
JosefPiri_at_hotmail.com
Date: 01/15/05
- Next message: Chris: "Re: COOD11CD"
- Previous message: mightymouse2: "sever exacution failed error 8008005"
- Maybe in reply to: TravisL: "Re: WMP10 / WMA9.0"
- Messages sorted by: [ date ] [ thread ]
Date: 14 Jan 2005 19:36:47 -0800
Dear Zach, Ian, Chris, bish, et al,
I've nailed it!
I've tested different combinations and the problem is definitely NOT
related to WMADMOE.DLL.
Rather, the culprit is WMVCORE.DLL: Simply replacing it with version
from WMA9 package enabled my Pioneer car deck to read newly encoded WMA
files! I've tested encoding by using both WMA10 player and dbPowerAmp
(a very good piece of software btw - especially considering the
author gives out a big part of functionality for free...)
In the end, all I had to was to simply copy v9 version of WMVCORE.DLL
over existing one in Windows/System32. (I did not get any 'refusal'
msgs from MS Windows btw - I do have SysAdmin rights on my machine
though... If you run into problems try closing all applications (or
even rebooting)...).
If you can't find old version of WMVCORE.DLL on Internet (btw
9.0.0.3250 is the version I tested), check out your hard drive: chances
are you'll find it in Windows/ServicePackFiles...
Zach's (tnx zach!) 2nd hunch of root cause of WMA10 incompatibility
with most WMA-compatible car decks (as evidenced in this thread:
Pioneer, Kenwood etc) is correct: the issue is related to header data
and not to codec itself. You can easily test if your 'downgrade'
went ok: WMA files encoded after replacing wmvcore.dll should be 2-4K
smaller. Contrary to some earlier suggestions in this thread it does
NOT matter whether the actual codec is reported as Windows Media v9 or
v9.1, as long as wmvcore.dll is v9 and not v10.
<Disclaimer:
Please note that replacing DLLs in System32 is not something anyone
should do and not something I'd advise/encourage (we're doing it
here only bc MS has apparently made a big blunder and, yet, not reacted
for months). Please also note that this ought to be considered a
_hack_. Hence: only music lovers with affected car decks (from Pioneer,
Kenwood...) and with adequate MS Windows knowledge should engage. There
are no guarantees that the rest of Windows Media functionality will
operate properly if DLLs of different versions are combined at will.
End Disclaimer>
To wrap it up, let me bother you with some personal ramblings: (stop
reading here if you don't care)
Isn't this story of WMA10 amazing? With one stroke MS managed to kill
compatibility on a wide array of wma-compatible devices (a market _MS
itself_ created! And all that just before 'plays for sure' campaign
- Amazingly, US media has not picked up on this - yet...). After
several months (as many frustrated msgs in this thread testify) there
is not even an acknowledgement of a mistake, much less a promise of a
resolution. Such a shame, considering that WMA is not such a bad format
and especially considering great technical talent that went into making
it: wma encoding speed is still by far ahead of everyone else (LAME
mp3 preset standard can get up to 8x on my machine, iTunes AAC 10x+:
WMA encoder is at 20x+) with comparable, if not better, music quality -
although this is subjective (I personally have a problem listening to
mp3's - even at 320k). Just today I read a story on CNet evaluating
BillG as software architect: CNet's conclusion: If BillG would have
been a normal person he'd been fired by now.... sadly, our little
WMA10 frustration seems to complement this story...
Cheers,
Josef
- Next message: Chris: "Re: COOD11CD"
- Previous message: mightymouse2: "sever exacution failed error 8008005"
- Maybe in reply to: TravisL: "Re: WMP10 / WMA9.0"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
