View Bug Details

IDProjectCategoryView StatusLast Update
0001072DCP-o-maticClean-uppublic2018-10-17 20:13
ReporterCarsten Assigned Tocarl  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformMacOSOS X OS Version10.11
Product Version2.10.5 
Summary0001072: Use common namespace http://www.digicine.com/PROTO-ASDCP-VL-20040311# in VOLINDEX file
Description

I think we should finally acknowledge that http://www.digicine.com/PROTO-ASDCP-VL-20040311# should be used in Interop VOLINDEX file, instead of http://www.digicine.com/PROTO-ASDCP-AM-20040311#

This fixes warnings in validation tools, e.g. easyDCP Player/easyDCP Validator

  • Carsten
TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredUnknown

Activities

mhm

2017-05-15 00:17

reporter   ~0001674

Actually I think that EasyDCP Player/Validator is incorrect here. The syntax and constraint for VOLINDEX and the VolumeIndex element for Interop is defined in the context of Assetmap.

Please see the Interop document mpeg_ii_am_spec.doc and also:
this old opendcp ticket: https://github.com/tmeiczin/opendcp/issues/251

discussion:
https://groups.google.com/forum/embed/#!topic/opendcp/iIs0hPXHCFQ
http://dcinemaforum.com/forum/index.php?topic=456.0

Although the http://www.digicine.com/PROTO-ASDCP-VL-20040311# namespace is in common use, I still think it is wrong. But either way it does not seem to that it leads to ingest failures.

So the question here is really: Should DCP-o-Matic change namespace for Interop VOLINDEX files just to silence EasyDCP warnings?

mpeg_ii_am_spec.doc (84,992 bytes)

Carsten

2017-05-15 00:41

manager   ~0001675

I have looked up all these resources before I filed this bug. After having read through the interop am spec multiple times, I am convinced that this document is just incomplete, but does not advise against a separate namespace for the VOLINDEX file. I have more references that show that the same people (from Dolby) who created said document at the same time created demonstration Interop packages using the http://www.digicine.com/PROTO-ASDCP-VL-20040311# namespace. Thus it occurs to me this is NOT an easyDCP Player peculiarity. I checked many (>20) different commercial movie trailers that have been created with old and current versions of Cineasset, Clipster, FinalDCP, and easyDCP Creator, as far back as 2004.
They all use http://www.digicine.com/PROTO-ASDCP-VL-20040311#
Even the original DCI StEM packages use it...

I think we are wrong here. Yes, it is no big deal on real DCI servers, but we should not risk open source software reputation lightheartedly. This is not to bow to a dominating but wrong-doing software.

  • Carsten

mhm

2017-05-15 01:16

reporter   ~0001676

Hmm.. I agree that the Interop "spec" contains a lot of ambiguities, so perhaps you are right.

Maybe the right thing would be to ask someone who was there when the interop documents were written, like John Hurst or on the ISDCF list.

Carsten

2017-05-15 01:23

manager   ~0001677

Yes, we could ask John about it. The digicine file repository I have still lists the documents with their historic creation date. There are two versions of the mpeg_ii_am spec from june 2004 (9/17).

But there is a file mpeg_ii_Minutes and Action Items from July 27 (2004) - and it cites:

'2. (Kodak/Dolby)Need to create schema for the VOLINDEX file and add to Asset Map document.'

  • Carsten

mhm

2017-05-15 12:14

reporter   ~0001678

Intresting! I had missed that. But did the creation of this schema ever happen?

Carsten

2017-05-15 12:38

manager   ~0001679

The trouble is, we tend to think that Interop is a 'standard' preceding SMPTE. However, if you look at the documents at digicine, it becomes clear that it is just a pile of documents that a bunch of people threw together to get digital cinema going. And if you look at some meeting notes, it was also rushed for various reasons. So, we probably shouldn't put too much weight in the fact that something isn't mentioned there. Yet it would certainly be nice if we can find a reference somewhere else... It must be somewhere, since all these commercial software packages did not make it up individually, as they all use the same VL namespace.

  • Carsten

Carsten

2017-05-15 13:02

manager   ~0001680

Okay, I did it, I attacked ISDCF mailing list about it. Let's see what comes out...

  • Carsten

mhm

2017-05-15 15:10

reporter   ~0001683

Thank you! :)

carl

2017-05-21 23:49

administrator   ~0001684

I've put this in now.

Carsten

2017-06-17 00:40

manager   ~0001718

Sorry for re-opening, but, as there has been some discussion about this here, I wanted to finally confirm that, after Carl has adjusted the VOLINDEX namespace in the recent test releases, easyDCP Player does no longer complain ('Warning') about DOM DCPs.

So, this actually also confirms that this was the issue easyDCP player did not like about DOM DCPs.

  • Carsten

carl

2017-06-17 23:59

administrator   ~0001719

Great, thanks Carsten.

Bug History

Date Modified Username Field Change
2017-05-14 23:27 Carsten New Bug
2017-05-15 00:17 mhm File Added: mpeg_ii_am_spec.doc
2017-05-15 00:17 mhm Note Added: 0001674
2017-05-15 00:41 Carsten Note Added: 0001675
2017-05-15 01:16 mhm Note Added: 0001676
2017-05-15 01:23 Carsten Note Added: 0001677
2017-05-15 12:14 mhm Note Added: 0001678
2017-05-15 12:38 Carsten Note Added: 0001679
2017-05-15 13:02 Carsten Note Added: 0001680
2017-05-15 15:10 mhm Note Added: 0001683
2017-05-21 23:49 carl Assigned To => carl
2017-05-21 23:49 carl Status new => resolved
2017-05-21 23:49 carl Resolution open => fixed
2017-05-21 23:49 carl Note Added: 0001684
2017-06-17 00:40 Carsten Status resolved => feedback
2017-06-17 00:40 Carsten Resolution fixed => reopened
2017-06-17 00:40 Carsten Note Added: 0001718
2017-06-17 23:59 carl Status feedback => resolved
2017-06-17 23:59 carl Resolution reopened => fixed
2017-06-17 23:59 carl Note Added: 0001719
2018-10-17 20:13 carl Status resolved => closed