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?

Comments

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: #1 MSI TRX40 Pro Wi-Fi w/3960X (be Quiet! Dark Rock Pro TR4) @ stock; 128GB Team Group 3200 MHz; OS/Apps - WDSN850X PCI-e 4.0x4 4TB, Documents/Extras - WDSN850X PCI-e 4.0x4 4TB; XFX AMD Radeon 7900XTX (24.12.1); Samsung 32 Inch UHD 3840x2160; Windows 11 Pro 64-Bit (24H2 26100.2894); (2) Inland Performance 2TB/(2) PNY 3040 4TB PCI-e on Asus Quad M.2x16; (2) WD RED 4TB; ProGrade USB CFExpress/SD card Reader; LG 16X Blu-Ray Burner; 32 inch Samsung UHD 3840x2160.

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS (Happy Otter Scripts); DVD Architect 7.0 (100);

Sound Forge Audio Studio 15; ACID Music Studio 11; SonicFire Pro 6.6.9 (with Vegas Pro/Movie Studio Plug-in); DaVinci Resolve (Free) 19.1.3

#2: Gigabyte TRX50 Aero D w/7960x (Noctua NH-U14S TR5-SP6) @ stock; 128GB Kingston Fury Beast RDIMM @4800 MHz; OS/Apps - Seagate Firecuda 540 2TB PCI-e 5.0x4; Documents/Extras/Source/Transcodes - 4TB WDSN850X PCI-e 4.0x4; 4TB Inland Performance PCI-e 3.0x4; 2TB Inland Performance PCI-e 4.0x4; BlackMagic PCI-e Decklink 4K Mini-Recorder; ProGrade USB SD & Micro SD card readers; LG 32 Inch UHD 3840.x2160: PowerColor Hellhound RX Radeon 7900XT (24.12.1); Windows 11 Pro 64-Bit (24H2 26100.2894)

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS; DVD Architect 7.0 (100); Sound Forge Audo Studio 15; Acid Music Studio 11

Canon EOS R6 MkII, Canon EOS R6, Canon EOS R7 (All three set for 4K 24/30/60 Cinema Gamut/CLog3); GoPro Hero 5+ & 6 Black & (2) 7 Black & 9 Black & 10 Black & 11 Black & 12 Black (All set at highest settings - 4K, 5K, & 5.3K mostly at 29.970); Sony FDR AX-53 HandyCam (4K 100Mbps XAVC-S 23.976/29.970)

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.

Compoundplug.dll

So4compoundplug.dll