File details is incorect

FayFen wrote on 2/9/2020, 2:34 AM

In relation to an answer I got in the DrZen forum I learn about files detailed view.

So I checked few files, on many it's incorrect . Here it's the most drastic one.

And at your end?


Musicvid wrote on 2/9/2020, 8:30 AM

Nope, they are perfect.

1 Mbps = 1000 Kbps

1 MBps = 8 Mbps

Chief24 wrote on 2/9/2020, 9:49 AM

In your screenshot, for what you are "pointing to", it is only the size of the "Video" stream. Go down to the Audio portion, take that "File Size" and add to the Video File Size.

Presto! They should now "Equal" the file size in the "General" section.

Self Build: Asus ROG Strix X399-e Gaming with 1950X (be Quiet! Dark Rock Pro TR4) @ stock; 64GB Corsair 2666 Mhz; OS-Intel 750 800GB, Project Media-Samsung 960 EVO 1TB & 970 EVO 1TB; Samsung 850 EVO 500GB SSD for various (Magix Xara Photo & Graphics Designer Pro 16), Render, Other Assets; Sapphire AMD Radeon VII; Samsung 28 Inch UHD 3840x2160; Windows 10 Pro 64-Bit (1809); (2) Intel 660p 2TB PCI-e on Asus Quad M.2x16; Magix Vegas Pro 15 Suite (416), Magix Movie Studio Platinum 16 Suite (167); Canon EOS 80D; GoPro Hero 5+ & 6 Black & (2) 7 Black; Sony FDR AX-53 HandyCam; Sound Forge Studio 12.6; Creative SoundBlaster Zx sound card; Magix Music Maker Premium 2019

matthias-krutz wrote on 2/10/2020, 12:49 PM

Unfortunately, it is a bit more complicated. The selected example actually only shows the minor problem that the usual unit of measurement MBit / s is not used. The bigger problem is that the video data rate is displayed differently, depending on whether a file is opened with so4compoundplug.dll or compoundplug.dll. If it is decoded with so4 .., the values correspond to the bit rate, but with the wrong unit. The examples are from VP17.