View Issue Details

IDProjectCategoryView StatusLast Update
0001232DCP-o-maticBugspublic2018-10-17 20:15
Reportercarl Assigned Tocarl  
Status closedResolutionfixed 
Target Version2.12.0 
Summary0001232: Remaking an encrypted DCP in a project results in MXFs with unmatched IDs
  1. Enable use of HMAC when reading DCPs.
  2. Create an encrypted project, make dcp, make dcp again, make DKDM.
  3. Read the DCP into a new project -> IntegrityPack failure: AssetID mismatch from asdcplib.
  4. Do the same thing but with only making the dcp once -> OK.
TagsNo tags attached.
Estimated weeks required
Estimated work requiredUnknown



2018-03-06 21:39

manager   ~0002272

A bit exotic at first, but will this also happen when e.g. creating only a partial first DCP (e.g. with abort), and then continue, maybe multiple times?

  • Carsten


2018-03-06 23:01

administrator   ~0002274

I haven't investigated yet but I would guess so. Not all systems care about these IDs, I think. The problems I have seen so far are related to the HMAC used with encryption.


2018-03-07 14:23

administrator   ~0002281

Should be fixed by 5045742a5225e0771688ee3f8b6f8812bb1903fd in v2.12.x and d516d8e159e99d7b3b8250f39f976574df072cd8 in master.

Issue History

Date Modified Username Field Change
2018-03-06 00:32 carl New Issue
2018-03-06 21:39 Carsten Note Added: 0002272
2018-03-06 23:01 carl Note Added: 0002274
2018-03-07 01:34 carl Description Updated
2018-03-07 14:23 carl Assigned To => carl
2018-03-07 14:23 carl Status new => resolved
2018-03-07 14:23 carl Resolution open => fixed
2018-03-07 14:23 carl Note Added: 0002281
2018-10-17 20:15 carl Status resolved => closed