The group column is very useful, but it has one minor problem. As far as I can tell, to BDInfo a group is basically just any playlists that share any m2ts streams. Typically in a single group on most BD's, there is one full-length video composed of multiple m2ts streams, and everything else in that group is a subset of that first playlist. In other words, all streams in the shorter playlists are included in the longer one. For example a playlist containing all deleted scenes, and then separate playlists containing one deleted scene each.
But sometimes there are cases where BDInfo groups together two playlists that both have unique streams but may share one or two in common. In these instances, it would be helpful to see another column to indicate whether all streams in a playlist are duplicates of the streams in the "main" playlist of that group. Does that make sense?
As an example, I'm looking at a BD now that has 30 playlists in group 3. The longest (runtime) in this group is 37.mpls containing 106-114 and 128.m2ts. The second is 45.mpls containing 117-121 and 128.m2ts. Even though these two share only 128.m2ts, they are considered to be part of the same group. And 128.m2ts is just a copyright notice tacked on to the end of two separate extra features. The remaining 28 playlists in group 3 are just shortened versions of those first two main playlists. But to find that out, I have to manually check each playlist in the group to see what streams it includes, and then refer back to the first two playlists to see if those streams are included.
I don't know exactly how to simplify this in BDInfo, but using the above example, one potential option is: When you check the box for 37.mpls, grey-out the other playlists in that group that contain only duplicates of streams within 37.mpls.
This would make it dramatically easier to ensure you've located all the unique streams in a BD and haven't missed anything that's buried somewhere in a group of otherwise duplicates.
The group column is very useful, but it has one minor problem. As far as I can tell, to BDInfo a group is basically just any playlists that share any m2ts streams. Typically in a single group on most BD's, there is one full-length video composed of multiple m2ts streams, and everything else in that group is a subset of that first playlist. In other words, all streams in the shorter playlists are included in the longer one. For example a playlist containing all deleted scenes, and then separate playlists containing one deleted scene each.
But sometimes there are cases where BDInfo groups together two playlists that both have unique streams but may share one or two in common. In these instances, it would be helpful to see another column to indicate whether all streams in a playlist are duplicates of the streams in the "main" playlist of that group. Does that make sense?
As an example, I'm looking at a BD now that has 30 playlists in group 3. The longest (runtime) in this group is 37.mpls containing 106-114 and 128.m2ts. The second is 45.mpls containing 117-121 and 128.m2ts. Even though these two share only 128.m2ts, they are considered to be part of the same group. And 128.m2ts is just a copyright notice tacked on to the end of two separate extra features. The remaining 28 playlists in group 3 are just shortened versions of those first two main playlists. But to find that out, I have to manually check each playlist in the group to see what streams it includes, and then refer back to the first two playlists to see if those streams are included.
I don't know exactly how to simplify this in BDInfo, but using the above example, one potential option is: When you check the box for 37.mpls, grey-out the other playlists in that group that contain only duplicates of streams within 37.mpls.
This would make it dramatically easier to ensure you've located all the unique streams in a BD and haven't missed anything that's buried somewhere in a group of otherwise duplicates.