Old error ever going to be fixed?

[Stephen van Vuuren]

I still see this error in EasyDCP player occasionally on DCP servers although never seems to cause problems except for one Qube server years ago:

code 60003 from Sun May 24 16:07:07 2015:

Referenced XML-Schema unknown

(l. 2) Element '{http://www.digicine.com/PROTO-ASDCP-AM-20040311#}VolumeIndex': No matching global declaration available for the validation root.

I can't remember now why this still there?

stephen

[SL film]

oh yes...i'm getting the same "warnings" all over. plays fine everywhere but still spits out that warning.
must be a minor issue in the syntax. dcp-o-matic does the same!

[SL film]

btw: this is what i'm getting in easyDCP:

Code 60003 from Tue May 26 13:40:50 2015:

Referenced XML-Schema unknown

Validating against schema "http://www.digicine.com/PROTO-ASDCP-VL-20040311#":

(l. 2) Element '{http://www.digicine.com/PROTO-ASDCP-AM-20040311#}VolumeIndex': No matching global declaration available for the validation root.

On Sunday, May 24, 2015 at 10:10:52 PM UTC+2, Stephen van Vuuren wrote:

[SL film]

maybe that server is just down ,)

On Sunday, May 24, 2015 at 10:10:52 PM UTC+2, Stephen van Vuuren wrote:

[Stephen van Vuuren]

The URL still works fine, but overall weird that it’s part of the spec.

 

stephen van vuuren

336.202.4777

 

http://www.insaturnsrings.com/

http://www.sv2dcp.com/

http://www.sv2studios.com/

 

A film is – or should be – more like music than like fiction. It should be a progression of moods and feelings. The theme, what’s behind the emotion, the meaning, all that comes later.

–Stanley Kubrick

--
You received this message because you are subscribed to the Google Groups "opendcp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendcp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Terrence]

As far as I know this is what it should be. I've only ever seen
EasyDCP player complain and I'm not 100% certain they are doing the
correct thing. EasyDCP uses
http://www.digicine.com/PROTO-ASDCP-VL-20040311 which is does not
exist within the MXF Interop specification. I seem to recall getting
this error with DCP's made by Clipster too, but it was long time ago,
so I can't be sure.

The SMPTE specification is clear, both the AssetMAP and VolumeIndex
use the same URI. So, I don't know why they would have done it
differently in MXF Interop.

[Stephen van Vuuren]

Weird, I've got the newest version (demo obviously) of EasyDCP Player and still there. Just an annoyance to see DCPs open with warning and have to click to see, no, it's the same old warning as before, every time.

Of course, I can't complain directly to them since I don't own their software, but why this is still there is very strange. That's even more strange they use a bad URL.

I wonder if it's there (conspiracy theory) so that people testing DCP's made by software other than their own is always flagged but theirs looks clean. Would make their presentations go well :)

stephen van vuuren
336.202.4777

http://www.insaturnsrings.com/
http://www.sv2dcp.com/
http://www.sv2studios.com/

A film is – or should be – more like music than like fiction. It should be a progression of moods and feelings. The theme, what’s behind the emotion, the meaning, all that comes later.
–Stanley Kubrick

[Terrence]

This is what the spec has to say...

VolumeIndex

Location
The VolumeIndex parameter shall be contained in a file named
‘VOLINDEX’ located in the root directory of the UDF partition.

Format
The VOLINDEX file shall be a valid, UTF-8 encoded, XML file containing
three elements:

A required, base element named “VolumeIndex”
A required, non-zero, positive integer element named “Index”.
An optional text string named “AnnotationText”

Unlike the other XML files, there is no schema or example.

In the SMPTE spec, they have the XML schema example.

<?xml version="1.0" encoding="UTF-8"?>
<am:VolumeIndex xmlns:am="http://www.smpte-ra.org/schemas/429-9/2007/AM">
<am:Index>1</am:Index>
</am:VolumeIndex>

Which is clearly the same as the xmlns uri as used in the asset map.
This kinda leads me to think the intention would have been the same
for MXF Interop. Just my opinion tho...

On Tue, May 26, 2015 at 4:13 PM, Stephen van Vuuren