Really, what is taking so long?
And yes, I know about the workaround, which ■■■■■!
CHOP-CHOP!
Well I expect that got their attention. What will you do while you wait?
Yes! Please fix it.
+1… this is very annoying. Hope it will be fixed shortly
Thanks.
ograpin wrote:
+1… this is very annoying. Hope it will be fixed shortly
Thanks.
If you are lucky it will be fixed in a year.
That’s not fair, i can’t understand why is not fixed.
People will change to other player if they don’t arrange it soon.
marcelg wrote:
That’s not fair, i can’t understand why is not fixed.
People will change to other player if they don’t arrange it soon.
Go ahead… You’ll very likely find that it’s not supported in MOST platforms, as this is a rather new “problem.” While the compression is part of the standard, it was rarely implemented before now.
For now, YOU can fix it yourself by doing a 45-second ReMux.
marcelg wrote:
That’s not fair, i can’t understand why is not fixed.
People will change to other player if they don’t arrange it soon.
Better make sure its not on this list:
http://www.bunkus.org/videotools/mkvtoolnix/faq.html#header_removal_compression
Thanks, i what i do on the new files with the header compression.
marcelg wrote:
Thanks, i what i do on the new files with the header compression.
You remux them with MKVmerge version 4.0.0 or lower. You can also use any newer version with video and audio compression turned off.
+1
Please fix
In my opinion, its worth making WDC aware of the issue. But let’s face it, this is a really minor issue. There are much bigger fish to fry.
Those using newer versions of MKVmerge can just disable the header compression option (which is enabled by default). And using header compression won’t buy you much anyways! You might save a couple hundred MB on a 25GB rip.
If I was going to dump energy into this, the more efficient thing to do is to petition the author of MKVmerge to change it so header compression is off by default. There are way more important things for WDC to devote their energies towards.
hydrogin wrote:
“In my opinion, its worth making WDC aware of the issue. But let’s face it, this is a really minor issue.”
Don’t they know it already? I thought I saw a comment from someone on their team (Guy perhaps?) who said they were planning on fixing it.
“If I was going to dump energy into this, the more efficient thing to do is to petition the author of MKVmerge to change it so header compression is off by default.”
Yeah, you might as well try to teach a pig to sing 
hydrogin wrote:
… But let’s face it, this is a really minor issue. There are much bigger fish to fry.
- *> I beg to differ. I was unaware of this issue. I had been merrily enjoying media files. Then, one day I tried to play one that, as it turns out, has the compression. It locked up the player. Not only would the box (gen1) not play the file in question, but it will no longer play ANY media file… not .mkv, not .avi, not .mpg, not .mp3 etc…> I’ve left it unplugged for over 24 hours, I’ve done scads of resets, I’ve deleted the .db file… I’ve spent a week trying to get it working again with the files it used to play.> If it ever works again, THEN I can go back and re-mux any offending files before they bork it again, but having the player just up and die is not a “really minor issue”.> It doesn’t matter if nobody ever used this aspect of Matroska in the past, and in terms of WDTV players, it doesn’t matter what other players also don’t support it. If it’s part of the specs and Matroska developers ASK for it to be supported, and ASK for your player to be tested with their test files, then claiming Matroska support in the specs, on the box and in the manual is just FALSE. It’s called “limited Matroska support”. Without that word “limited” in there, full support is implied. And no warning is given anywhere that attempting to play a Matroska-compliant file MAY render your player unusable.
There IS a firmware fix for this, guys – WD has done it and it’s just a matter of getting released.
I know that isn’t the best thing to hear, but at least it’s something. My hunch is it will come out after Halloween but before Thanksgiving (but that’s only my best guess and is worth what you make of it).
Can anyone explain a simple consumer what HEADER REMOVAL COMPRESSION is?? and what does remux mean?? sorry!!!
its all here.
http://www.bunkus.org/videotools/mkvtoolnix/faq.html#header_removal_compression
http://www.afterdawn.com/glossary/term.cfm/multiplexing
re-muxing is multiplexing again after turning off compression on the video and audio tracks. This makes the file suitable for the WDTV. Re-muxing is very simple and very quick.
pegga wrote:
Can anyone explain a simple consumer what HEADER REMOVAL COMPRESSION is?? and what does remux mean?? sorry!!!
A more high level (and thus wildly imprecise short explanation is:
Mux’ing is when you take several bits of digital stuff and mush it together into one file - like picture, sound, perhaps some subtitles.
Demux’ing is when you take the different bits out of the single file.
Remux’ing is when you take the bits out, usually do something to them, and them put them back into one big bundle.
Header Compression is some guff a program can do to the sound and/or picture before someone mux them.
Clear?
Minor Edit:
worthless
Header Compression is some ^ guff a program can do to the sound and/or picture before someone mux them.
I agree this has to be fixed ASAP.
