Edge: Please, do not put words in my mouth.
I never said there wasn’t a problem with Twonky. I was arguing the fact that the poster said it doesn’t work with MKV at all. That’s simply not true.
You, yourself, in a prior thread remarked that MKV doesn’t work with anything on the MB:
TheEdge wrote:
What confuses me is that you can’t stream mkv to Media player with MBL and Twonky 5.xx, but you can stream mkv to the same Media player with Twonky 6.xx . I do not know how to put it any simpler than this.
So in a fashion, I’m arguing, too, that accuracy of that statement.
99% of people have problems? That’s gross hyperbole. I would doubt even 5% of people have problems with it. But since neither of us have any real statistics to go by, it’s a moot point.
Does Twonky have issues? Sure. But I’ve already explained why it’s doubtful you’ll ever see WD upgrade Twonky.
Whether the problem comes down to MIME definitons or not is irrelevant.
No, it’s *not* irrelevant.
People with this issue have one of four choices:
1> If it’s a mime type or profile issue (like several file types on PS3s) one can simply edit the clients.db file in Twonky and be working in about 2 minutes.
2> They can install their own version of Twonky on the MBL in about an hour. But you said that it doesn’t work for you even if you do that, so I count that solution as dubious from the start.
3> They can return the MBL and get their money back.
4> They can sit and hold their breath until they turn blue.
It surprises the heck out of me how many people opt for #4.
The fact that Twonky has “fixed” it in later versions actually doesn’t mean that the fault was Twonky’s to begin with. They may have simply added a workaround for Samsung due to an issue with Samsung’s protocol handling.
