![]() The decoder we use in VideoReDo only supports the "core" part of the stream, so if you recode the decoder will only see the "core" portion of the stream and convert that to the new format. Then the HD/Lossless data is layered on top of that using extra data and some crazy complex math. DTS uses a weird system where every stream has a compressed, 5.1, "core" stream. Now one thing you may or may not know is that if you recode these streams to any other format in VideoReDo they will NOT use the HD/Lossless version to create those new streams. However we have no way to determine the origin of the file so I'm just going to continue to use the main table of bitrates.Īs for the lossless track MediaInfo is just ignoring the bitrate field when the stream is lossless. I'm assuming that's where Media info is getting it's bitrate. Now there is special note in the spec that says that if the audio originated on a DVD video disc then that value means 1509.75Kbps. When I look at the actual bits in the header of your streams the target bitrate field is set to '0b11000', which is 1536Kbps according to the DTS spec. It's just a difference between how MediaInfo reads the files and how we do. OK I looked into this and it's not a bug. It's just that don't see why you wouldn't want to fix anything that is not correct once it's been pointed out, super-important or only minor-important. If it cannot be relied upon to be correct, then why present that item at all? Incorrectly displayed items should be fixed, not excused as "unimportant, so it can be wrong". I don't think it's unreasonable to presume that every single field value shown can be relied upon to be correct and accurate. As we see from other tools (like MediaInfo, BDEdit, etc.) there are many fields relevant to playing audio/video, and you decided some subset to actually present. You decided which fields would be presented, and which ones not. You went to the trouble of producing a beautiful informational display. Why not just display ABC, if it's not important? Are any fields "important", so that they must be accurate? Why some, and not others, or all? Displaying an incorrect value is incorrect. I understand, but that is exactly the point. Original source medium : Blu-ray(3) detail audio program information from VideoReDo: ID in the original source medium : 4354 (0x1102) ID in the original source medium : 4353 (0x1101) ID in the original source medium : 4352 (0x1100) (1) summary audio information from MediaInfo: Where did 1536 come from? And certainly are not the same for both lossless and lossy DTS, In fact the lossless (VBR) bitrate should be shown as 3637 (or close), instead of the lossy (CBR) bitrate of 1536 (which MediaInfo shows as 1509), Note the bitrate of 1536 shown in the output below from VRD for both the lossless and lossy DTS audio tracks (1 and 2). In fact the bitrate for the lossless audio is obviously much larger than that of the lossy audio. It mistakenly was the same value shown for the first track which was DTH-HD MA (lossless) as for the second track (DTS lossy). Imagine my surprise when I noticed that the audio bitrate value shown in one of the four audio tracks was incorrect. I also presented the summary and detail info from MediaInfo for the same file, just for contrast. I was replying to a user thread question on another forum, and used the "TOOLS -> show video program info" output from VRD to demonstrate something.
0 Comments
Leave a Reply. |