INTERACT FORUM

More => Old Versions => Media Center 12 (Development Ended) => Topic started by: ozmael on October 28, 2006, 11:36:20 pm

Title: Can't rip WMA Lossless with 12.102
Post by: ozmael on October 28, 2006, 11:36:20 pm
I'm using MC 12.102. When I try to rip to WMA lossless I get the error, "Read track failed. Failed to initialize the encoder plugin. Rip failed."

I have WMP 11.0.5705 installed.

Ozmael
Title: Re: Can't rip WMA Lossless with 12.102
Post by: Matt on October 29, 2006, 07:28:55 am
WMP 11 beta breaks compatibility with encoder profiles.  Hopefully Microsoft will fix it for the release version.
Title: Re: Can't rip WMA Lossless with 12.102
Post by: ozmael on October 31, 2006, 03:00:43 am
I completely appreciate and understand that Microsoft should probably do more to not break the compatibility of their encoder profiles. But, given that WMP 11 is now released (and it appears that it's still broken when trying to rip to WMA lossless in MC), will there be an update to MC to be compatible with the new WMP 11 encoder profiles?

Regards,

Ozmael
Title: Re: Can't rip WMA Lossless with 12.102
Post by: GreggP on November 01, 2006, 02:21:45 pm
Any progress on this???
Title: Re: Can't rip WMA Lossless with 12.102
Post by: Yaobing on November 02, 2006, 10:53:19 am
"5. Fixed: Windows Media 11 would not support lossless WMA encoding."

Is that it?

http://yabb.jriver.com/interact/index.php?topic=36824.msg251242#msg251242
Title: Re: Can't rip WMA Lossless with 12.102
Post by: Matt on November 02, 2006, 11:05:50 am
Yup, should be fixed.  Silly Microsoft.
Title: Re: Can't rip WMA Lossless with 12.102
Post by: GreggP on November 02, 2006, 11:38:03 am
Does this apply to the latest Media Center 11 build also?
Title: Re: Can't rip WMA Lossless with 12.102
Post by: Matt on November 02, 2006, 11:56:40 am
If the fix is deemed safe, it may be rolled to MC 11.

However, we feel that this is actually a Microsoft bug.
Title: Re: Can't rip WMA Lossless with 12.102
Post by: GreggP on November 02, 2006, 12:33:25 pm
Have you reported this to MS? I'm sure you could report this through your MSDN subscription.

If so, have they acknowledged it as a bug? Or are they in denial (usually they are pretty good at responding to these sort of things).