Closed liloneum closed 10 months ago
Done, kind of. See https://github.com/wolfgangw/backports/commit/361f19baa330b020ffb23d5cad3d2827473133a2
Note that we are seeing 4K/HFR systems in the field which are spec'd for 500 Mb/s. dcp_inspect tries to let everyone live and therefore has this notion of legacy and 2nd gen systems built in. Errors and hints accordingly.
Perfect! Wow, it seems it is almost reaching an exhaustive analyse!
Just a detail, see this report:
Reel 1: 192 00:00:07:17 @ 25.0 049ddb16 MainPicture (SMPTE, 00:00:07:17, plaintext, 1998x1080, 41.81 Mb/s, pictures) 192 00:00:07:17 @ 25.0 d99b6337 MainSound (SMPTE, 00:00:08:00, plaintext, 6ch 48kHz 24bps, audio) Reel 2: 152316 01:41:32:16 @ 25.0 93a133b3 MainPicture (SMPTE, 01:41:32:16, plaintext, 1998x1080, 158.98 Mb/s, pictures) 152316 01:41:32:16 @ 25.0 24aeda63 MainSound (SMPTE, 01:41:32:16, plaintext, 6ch 48kHz 24bps, audio) Total duration: 152508 01:41:40:08 @ 25.0 CPL cf379d6c-ddd9-4cef-9356-2f1a1027ed14: Composition summary: "*****", SMPTE, Plaintext, 2D, Flat, 2K, 100.4 Mb/s, 01:41:40:08, 25.0 fps
The first reel lasts 00:00:07:17 with a bit rate of 41.81 Mb/s The second reel lasts 01:41:32:16 with a bit rate of 158.98 Mb/s The average bit rate for the CPL lasting 01:41:40:08 is 100.4 Mb/s ([41.81+158.98]/2) It is not correct and should be calculated proportionally to the duration of each reel, right?
Indeed :) Thank you, coming up.
Done. See 1f8782345e87d7dbb42805a8b2df094dce122491 (Weighted mean reported in composition summary).
Also note that the reported bitrates are taken from the assets' complete frame ranges respectively -- instead of frames entry
to entry + duration
.
I think it is good enough, though. Cases where the bigger part of an asset (with wildly different bitrate) would go unused should be rare. Agree?
Yes it's quite enough! This issue was minor.
Nice to have:
Analyse average and max bitrate (e.g. asdcp-info -r). Error (or hint?) if bitrate exceeding 250 Mb/s