Guess I was hoping to not have to back up the whole disk from now on?
How is this any good as I can't stream the movie anymore I have to back
up to a 50gb blu-ray from now on, what good is this to me and how is it a waste
other than my last two days trying to help you. I said I would wait till someone else complained... it's only a matter of time and now i get attitude?
Sorry for that - we have quite a lot on our desks at the moment and James was just venting some frustration with the workload.
Your information was, after all, a little misleading at first, so we did waste some of our time, which obviously we don't really have right now, heading in the wrong direction.
What I think is going on: when TMT is playing back a blu-ray disc, it will specifically choose its built in codecs for playback - in this case it's the AVC codec for the video part. It manually builds the filter graph required to handle the disc, including the HD audio codec, which is restricted in that it will only work with full BDs due to licensing conditions.
If you play an individual m2ts file, TMT will not bother choosing an appropriate set of codecs itself, as the file can be anything containing any number of codecs potentially unknown to TMT.
So it leaves it up to the OS (direct draw etc) to build an appropriate filter graph - which is the official way to go.
If you happen to have more than one AVC codec, there's a very good chance that a different codec will be chosen (which is what Adbear meant).
So, it's possible that the video has authoring bugs that are handled gracefully by Arcsoft's built in codec but not by the other.
Or the other codec might have a flaw that just happens to show with these discs.
Another theory: there is certain information that is redundantly stored in both the actual m2ts files and in the .clpi/.mpls files on the disc.
The software players usually prefer the stream information from the .clpi files over the same information stored in the PMT packets in the m2ts files.
But if you play an individual m2ts file, the only available source are those PMT packets. If there's something wrong with those, strange things might happen.
I can't really think of how the stream info would cause this specific phenomenon, but it is noteworthy that these differences apply depending on how you play the disc.
So - remuxing would be an interesting attempt to cure this.
Anyway - I doubt this is an AnyDVD issue.