Several reports from users testing the latest leaked build of Windows 7 indicate a potential data corruption issue using Microsoft's Windows Media Player 12.Windows 7 beta 1 build 7000 leaked over the Christmas holidays and a Microsoft spokesperson has confirmed that there is a bug which affects the leaked build. Approximately 2-3 seconds will get shaved off the beginning of MP3s if you have set your Windows Media Player 12 settings to retrieve information from the internet and update files. The default configuration for WMP12 sets this if you use the "express" option during setup.
"The problem only happens when you edit metadata on a certain class of MP3 file (a file with a header larger than 16KB). When the new metadata is written, it corrupts the beginning of the file. This can happen either when you edit the metadata from inside WMP or Explorer, or it can happen if you have WMP set to automatically fill in missing metadata using the online service and add the MP3 to your library. This problem is only present in the recently leaked build" (7000) according to one poster in our forums.
Microsoft's official response is "Microsoft is aware of this issue and it will be addressed in the beta program". The company is currently hard at work readying a QFE (quick fix engineering) patch that will be distributed by Windows Update for those with official and non-official access. A support (KB) article is expected soon.
This highlights the importance of not using leaked builds with any applications or data that is critical and waiting for beta builds from official channels. We expect Microsoft to stress the urgency of applying the QFE patch to those in the beta program.
- Does that mean Microsoft purposefully leaked the Beta?
edit: oh and ... how did you imply that MS leaked the beta purposefully?
Read the forums (link in the article)
Not sure where you're getting that impression. Nowhere in the forums does it state MS leaked the beta on purpose. Seems a little crazy.
oops..that was my bad, I thought georgevella was asking about the bug, which is discussed in the forums
I think it's more of a conspiracy theory that he's suggesting.
http://www.microsoft-watch.com/content/win..._windows_7.html
BitTorrent brought the Christmas present Santa didn't: Leaked build of Windows 7, whose official Beta 1 release is perhaps days away. Was this a craftily timed Microsoft marketing leak?
I sure as hell think so. It's certainly what I would do if I worked at Microsoft on Windows evangelism. The timing is perfect, from a marketing perspective. The leaked build hit BitTorrent sometime on Saturday, right after Christmas when the Windows geeks had nothing better to do and bloggers and journalists had nothing better to write about. The leaked build is designated "7000," which strongly suggests that the code is the same as forthcoming Beta 1, or close to it.
BitTorrent brought the Christmas present Santa didn't: Leaked build of Windows 7, whose official Beta 1 release is perhaps days away. Was this a craftily timed Microsoft marketing leak?
I sure as hell think so. It's certainly what I would do if I worked at Microsoft on Windows evangelism. The timing is perfect, from a marketing perspective. The leaked build hit BitTorrent sometime on Saturday, right after Christmas when the Windows geeks had nothing better to do and bloggers and journalists had nothing better to write about. The leaked build is designated "7000," which strongly suggests that the code is the same as forthcoming Beta 1, or close to it.
Obviously if a blog says it's true it must be...
Sure there is. Just as an example, official downloads tend to have release notes, "known issues" sections, and other warnings or special instructions.
I'll admit, I'm running a leaked copy (6801 in Virtualbo
Hardly - the first sentence explains more fully, and the only way you can be running WMP12 is with the Win7 beta.
That said, this is what betas and test builds are for! It also makes a good excuse to give the Windows Update features a little widespread testing, too.
Technically it's the property handler code that commits data back to the MP3 when you change metadata.
Of course! lol
There are plenty of other reasons not to use WMP, but that's beside point. lol
Just like you...
winamp handles all my video game music plugins
Very childish.
Give up. Winamp has been around as long as the MP3 format itself and doesn't deserve any criticism. Admittedly they lost their way when they got bought out but.. I'm willing to bet it's been on computers as long as you have!
So what? Microsoft and Apple have been around how long exactly? Does that make them exempt from any sort of criticism?
How long it's been around doesn't matter if the software isn't that great. Some people like it, and that's fine. For me, and probably others, it's not what I'd call a "decent" choice of media players.
And perhaps due to bad experiences from some individuals, they may feel it's absolute garbage. That's how I feel about Ubuntu, but hey, if we're not allowed to express our opinions, what are we doing here then?
I'm not suprised things like this happens, but some seem to be, and blame everyone else than themselves :p
I'm not suprised things like this happens, but some seem to be, and blame everyone else than themselves :p
since when has listening to mp3's been productive? same time watching pr0n at work did i guess
I'm not suprised things like this happens, but some seem to be, and blame everyone else than themselves :p
since when has listening to mp3's been productive? same time watching pr0n at work did i guess
He means a production machine as opposed to a testing machine. At least... that's what I think he means.
I'm not suprised things like this happens, but some seem to be, and blame everyone else than themselves :p
since when has listening to mp3's been productive? same time watching pr0n at work did i guess
He means a production machine as opposed to a testing machine. At least... that's what I think he means.
precisely
6801 didn't have this problem.
Last edited by Brandon Live on 05 Jan 2009 - 04:18
Gonna do a backup just in case.
Last edited by Franky601 on 05 Jan 2009 - 05:44
If you wait for the official beta release you'll have nothing to worry about.
Do you happen to know if technet subscribers are going to get the beta any sooner, or if it's going to be at the same time as the public beta?
So judging from your answer we can expect the fix being integrated into the official beta? Which means it would be a different build from what has leaked.
Tom
Tom
That is not what I said.
I'd have ticked the same option when using "Custom" install as well.
It's a useful feature when it doesn't take the first few seconds off your songs
Maybe because some people don't know much about computers and/or the custom settings and just use express.
I'm wondering whether the 'official' beta build will be updated with a proper fix or will it just be the same (byte-to-byte) like the leaked one. Not everyone runs Windows Update just right after the installation, many people have it turned off.
When will they learn.
When will they learn.
Not anytime soon. I'm using it as a main OS, with the full knowledge that if anything goes wrong, its my fault.
I currently use my machine to play games, surf porn* and listen to music - via itunes. Nothing too serious or important.
If you are too stupid to accept that, thats not my fault. This whole news post fills me with "meh"
* - occasionally I have been known to use the internet for other purposes.
This article is complete fail.
This isn't news, more like a small word of warning for people who are currently using a beta.
Will it be affected?
If the MP3 is on the network, it would potentially be effected there
*it writes to the file
i prefer Winamp for playing.
Here i got some more info about this article
http://www.google.co.in/search?hl=en&q...earch&meta=
+1 .. my thoughts exactly ^
These same people then cry tears when it nukes their system
a ) installed this leaked win7 (build 7000)
b ) uses wmp12.
c ) Edit metatag from a mp3 using wmp12 where there are several application that do a better job editing tags (massive, automatic and such).
d ) The edited mp3 contain a non-common size of metadata (larger than 16k).
then you are in trouble.
Last edited by warwagon on 05 Jan 2009 - 15:28
It's good that Microsoft is gonna fix this issue.
happened with me
all the Mp3 Downloads i had we corrupted
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.