Invalid CPL signature on Barco

[Carsten]

The DCP and KDM with 2.14.57 was created on the cinema windows machine, those with 2.15.171 and 2.16.0 on my MacBook - I am pretty sure I did everything right (I created a new cinema database with my stored certificates from the same sources) - but, I need to try it one more time to be absolutely sure. I may also try KDM inspector ...

KDM inspector suggests that everything is okay with this cert/CPL/KDM combination, it seems.


Hmm. Could this have to do with the separate 2.15/2.16 config folders/files when I use both versions with the same projects/DCPs? I guess I need to trash my config and try from scratch...

[carl]

Hmm. Could this have to do with the separate 2.15/2.16 config folders/files when I use both versions with the same projects/DCPs? I guess I need to trash my config and try from scratch...

Interesting idea - could be. Trashing the config and/or building with 2.14.57 on the macbook might both be interesting tests...

[carl]

The older signing cert is valid for 10 years, the newer for 40, which I guess might matter.

[Carsten]

Unfortunately, even after I trashed my full v2 pref set on my Mac and have 2.16 setup a new one with the first start, the problem persists.

I also just created an unencrypted version from the same project file (just unchecked 'encrypted' and renamed, that one seems to play okay (can not see the actual screen, as I do it remotely, but, the Barco seems to play without complaints).

It's strange that the Barco only complains after loading the CPL, but says that everything is okay in CPL/KDM properties.

I also looked into the detailed Barco error log, but it doesn't mention any details other than that particular error number/msg.

Bildschirmfoto 2022-02-03 um 21.24.45.png

Bildschirmfoto 2022-02-03 um 21.22.24.png

Bildschirmfoto 2022-02-03 um 21.13.00.png

[Carsten]

...

[Carsten]

And, unfortunately, me trying from scratch also doesn't solve the problem on the Sony:

Bildschirmfoto 2022-02-03 um 21.51.13.png

(this is a different error than we had a long time ago when we solved the 'old' Sony SMPTE KDM issue)

So, I guess we should concentrate on differences between 2.14.57 and 2.16

I could try some earlier 2.15 versions, I have a few stored - though not too many early ones. I have e.g. 2.15.30

[carl]

Trying earlier 2.15 versions would be great. I have most of them but I'm away from home and can't get at them until Sunday evening.

[carl]

I think the two easiest approaches are to hack 2.15.x to remove added things, or go back through the versions to find one that works...

[Carsten]

Okay, I'll try 2.15.30

I always used Modified Transitional 1, but I may also try other formulations just out of curiosity...

Hmm. Are we sure this is a KDM or DCP problem? I could create a DKDM and try to cross KDM and DCP between 2.14.57 and 2.16?

- Carsten

[carl]

Great, thank you.