View Bug Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002450DCP-o-maticFeaturespublic2023-02-13 05:122024-01-03 00:25
Reportermhm Assigned Tocarl  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status acknowledgedResolutionopen 
Target Version2.16.x 
Summary0002450: Check frame size and color component sizes of frames in verifier
Description

One really useful check (that I believe no other app does, not even wl-test of Wailua) is for frame size, and specifically for frame component size. Especially the last of these two are relatively unknown. I've had some really strange effects at playback with DCP:s that violate this. The sad thing is that violations of this seems to be ignored in every other DCP verifier I know of.

So it is basically two things to check for:

  • Max compressed bytes for any image frame (aggregate of all 3 color components)

  • Max compressed bytes for any single color component of an image frame

I have written up some more details here: https://github.com/Ymagis/ClairMeta/issues/130

Thanks!

I have written up some more details

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredUndecided

Relationships

related to 0001267 acknowledged Investigate problems around 250Mbit/s 
related to 0001664 acknowledged Check that J2K frames are not too large 
related to 0001652 confirmedcarl J2K data rate reporting / checking 

Activities

mhm

2023-03-30 00:27

reporter   ~0005598

Also see this issue in asdcp github:
https://github.com/cinecert/asdcplib/issues/92

carl

2023-04-16 22:35

administrator   ~0005639

libdcp e46e6c6054e4294c35d0f5e17de251b2fbb94cdc checks tile part size.

carl

2023-04-16 22:37

administrator   ~0005640

We already check for the total J2K frame size (compressed) being less than the equivalent of 250Mbit/s, maybe that's enough for the first part of this request?

mhm

2023-04-18 06:55

reporter   ~0005645

If it is in line with the requirements referenced 0002451 then i think it is enough fot the first part of this request, yes.

Bug History

Date Modified Username Field Change
2023-02-13 05:12 mhm New Bug
2023-02-13 07:51 carl Assigned To => carl
2023-02-13 07:51 carl Status new => acknowledged
2023-02-13 07:51 carl Target Version => 2.16.43
2023-02-13 07:51 carl Estimated work required => Undecided
2023-02-16 18:53 carl Target Version 2.16.43 => 2.16.44
2023-02-18 23:54 carl Target Version 2.16.44 => 2.16.45
2023-02-21 09:52 carl Relationship added related to 0001664
2023-02-21 09:52 carl Relationship added related to 0001652
2023-03-03 22:51 carl Target Version 2.16.45 => 2.16.46
2023-03-05 20:36 carl Target Version 2.16.46 => 2.16.47
2023-03-08 00:27 carl Target Version 2.16.47 => 2.16.48
2023-03-23 20:24 carl Target Version 2.16.48 => 2.16.49
2023-03-27 18:36 carl Target Version 2.16.49 => 2.16.51
2023-03-30 00:27 mhm Note Added: 0005598
2023-03-30 12:33 carl Target Version 2.16.51 => 2.16.52
2023-04-11 00:03 carl Target Version 2.16.52 => 2.16.54
2023-04-15 22:37 carl Relationship added related to 0001267
2023-04-16 22:35 carl Note Added: 0005639
2023-04-16 22:37 carl Note Added: 0005640
2023-04-18 00:35 carl Status acknowledged => feedback
2023-04-18 06:55 mhm Note Added: 0005645
2023-04-18 06:55 mhm Status feedback => assigned
2023-04-22 20:03 carl Target Version 2.16.54 => 2.16.56
2023-05-12 13:13 carl Target Version 2.16.56 => 2.16.57
2023-05-28 20:01 carl Target Version 2.16.57 => 2.16.58
2023-06-03 20:21 carl Target Version 2.16.58 => 2.16.59
2023-06-09 09:17 carl Target Version 2.16.59 => 2.16.60
2023-06-21 20:48 carl Target Version 2.16.60 => 2.16.x
2024-01-03 00:25 carl Status assigned => acknowledged