21 Jan
2016
21 Jan
'16
5:58 p.m.
Has anyone been successful in creating encrypted IOP or SMPTE DCPs for a Barco Alchemy
ICMP? I have tried with 2.6.16, both in IOP and SMPTE format, SMPTE with Modified
Transitional 1 and DCI specific.
DCP and KDM is ingested successfully, and the interface shows them associated, the key
validity window is displayed, properties shows 'valid' 'no errors'. I can
load the clip into the player, but when I hit 'Play', nothing appears, the player
claims it is playing, but silently goes to stop after 5s - this is the same for every
variant I tried.
I can play commercial unencrypted and unencrypted DCP-o-matic content without a problem. I
also tried one time with 1.81, same result. We have not yet registered the certificate
with a distributor or mastering service, so we have never received a commercial encrypted
feature + KDM. Actually I was just trying to create a successful enrcypted DCP and KDM to
test wether the certificate is working.
Any idea?
I have tried with both certificate downloaded from Barco database, as well as from the
ICMP itself using Communicator.
The syslog contains a lot of this stuff:
---
FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a smpte content
Jan 21 17:23:05 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Jan 21 17:23:06 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Jan 21 17:23:06 FFBARCO user.warn SM: SM- PlayoutEventsHandler::addFrame No BER data,
playout event cannot be logged
Jan 21 17:23:06 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Jan 21 17:23:06 FFBARCO user.warn SM: SM- PlayoutEventsHandler::addFrame No BER data,
playout event cannot be logged
Jan 21 17:23:06 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Jan 21 17:23:06 FFBARCO user.err SM: IMB Event- Security decryption error starting at
FrameId=479 on Channel=0 playBack=2
Jan 21 17:23:06 FFBARCO user.err SM: IMB Event- Audio data error pcieDataCountError=0
ddrWriteCountError=0 channelCountError=0 audioBufferIsEmpty=0 audioEnableTimeout=1
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1e00: 0bad0add 00000001
60010101 00bb801c 00000080 00001001 00000000 00100000
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1e20: 10000000 00000000
00000000 10000000 00000540 00010320 00010320 00000211
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1e40: 00000000 1500001e
00000000 00000000 00000000 00000000 00000000 0bad0add
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1e60: 00000400 0bad0add
0bad0add 0bad0add 00410505 0bad0add 0bad0add 0bad0add
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1e80: 0bad0add 0bad0add
0bad0add 0bad0add 0bad0add 0bad0add 0bad0add 0bad0add
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1ea0: 0bad0add 0bad0add
00000000 00400000 0000c012 00000040 00000040 0000270e
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1ec0: 00000000 00ffffff
00000001 00000000 0040019f 00003333 00081000 00000333
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- debug info 1ee0: d3e230e2 0050f947
c19bffff 00ffffff 00000400 00000000 00000000 0bad0add
Jan 21 17:23:06 FFBARCO user.err SM: IMB Event- Security decryption error starting at
FrameId=300 on Channel=2 playBack=1
Jan 21 17:23:06 FFBARCO user.err SM: IMB Event- Security decryption error starting at
FrameId=479 on Channel=2 playBack=2
Jan 21 17:23:06 FFBARCO user.debug SM: IMB Controller- Notify STOPPED state for frame
8388607
---
- Carsten
2 Feb
2 Feb
3:55 a.m.
Am 21.01.2016 um 18:58 schrieb Carsten Kurz:
Has anyone been successful in creating encrypted IOP
or SMPTE DCPs for a Barco Alchemy ICMP? I have tried with 2.6.16, both in IOP and SMPTE
format, SMPTE with Modified Transitional 1 and DCI specific.
These encrypted DCPs for our new Barco ICMP seem to be a real problem. When I didn't
succeed with DCP-o-matic, I asked one of the mastering studios that we get commercial
content from to issue a test-KDM for a feature we were regularly playing on our Sony
system. They replied quickly with a center KDM for both the Sony and the Barco. That
feature played without issues on both systems. The KDM was created by Waimea (CineCert).
The Mastering System was Dolby.
Now, knowing that we have a Sony and Barco, they asked me wether I could test content made
on their new/future mastering system, and sent me encrypted IOP and SMPTE versions of the
SINTEL Short (with subtitles) to test on both the Sony and the Barco.
Well, the SONY played all the content without any issues, the Barco NONE. Actually the
player app crashed on both IOP and SMPTE CPLs, even though everything was 'green'
- all content ingested fine, KDM attached to CPLs, everything indicated 'OK'. But
when playing, the Barco Player crashed and I actually had to reset it using the reset
button. The error msgs in the log are similar to those I got when I tried to play
encrypted DCP-o-matic content - just that the player did not crash as hard on that DOM
content (I could still stop and continue working).
---
Feb 2 01:14:21 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Feb 2 01:14:21 FFBARCO user.err SM: IMB Event- Security decryption error starting at
FrameId=0 on Channel=0 playBack=1
Feb 2 01:14:21 FFBARCO user.info SMS: Report- |SHOW-START|
[Sintel_SHR-1_S_EN-ES_DE_71_2K_BI_20151130_CPP_IOP_VF]
Feb 2 01:14:21 FFBARCO user.debug SMS: Player- Player subtitles: set gip timeline: PLAY
Feb 2 01:14:21 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Event- J2K decoder event wd0=0 wd1=20000 at
FrameId=0
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e00: 0bad0add 00000001
4a8101a1 00bb8019 00000080 00001001 00000000 00100000
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e20: 10000000 00000000
00000000 10000000 000007e8 00010320 00010320 00000211
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e40: 00000000 1510001e
00000000 00000000 00000000 00000000 00000100 0bad0add
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e60: 00000400 0bad0add
0bad0add 0bad0add 00410505 0bad0add 0bad0add 0bad0add
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e80: 0bad0add 0bad0add
0bad0add 0bad0add 0bad0add 0bad0add 0bad0add 0bad0add
Feb 2 01:14:21 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1ea0: 0bad0add 0bad0add
00000000 00400600 0001c124 0000002d 0000002d 000034f9
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1ec0: 00000000 00ffffff
00000000 00000000 002e001c 00003333 00081000 00000333
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1ee0: 4f93d152 0095121e
8a6bffff 00ffffff 02108400 00000000 00000000 0bad0add
Feb 2 01:14:22 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Feb 2 01:14:23 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Feb 2 01:14:24 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Feb 2 01:14:25 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame It is not a
smpte content
Feb 2 01:14:25 FFBARCO user.err SM: IMB Event- Security decryption error starting at
FrameId=300 on Channel=0 playBack=1
---
- Carsten
4:16 a.m.
Are you having problems with NON subtitled content? Alchemy looks
pretty strict with subtitles.
Curious that Alchemy it's complaining about "checkFrame It is not a
smpte content" for an Interop DCP.
On Mon, Feb 1, 2016 at 10:55 PM, Carsten Kurz via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Am 21.01.2016 um 18:58 schrieb Carsten Kurz:
Has anyone been successful in creating encrypted IOP or SMPTE DCPs for a
Barco Alchemy ICMP? I have tried with 2.6.16, both in IOP and SMPTE format,
SMPTE with Modified Transitional 1 and DCI specific.
These encrypted DCPs for our new Barco ICMP seem to be a real problem. When
I didn't succeed with DCP-o-matic, I asked one of the mastering studios that
we get commercial content from to issue a test-KDM for a feature we were
regularly playing on our Sony system. They replied quickly with a center KDM
for both the Sony and the Barco. That feature played without issues on both
systems. The KDM was created by Waimea (CineCert). The Mastering System was
Dolby.
Now, knowing that we have a Sony and Barco, they asked me wether I could
test content made on their new/future mastering system, and sent me
encrypted IOP and SMPTE versions of the SINTEL Short (with subtitles) to
test on both the Sony and the Barco.
Well, the SONY played all the content without any issues, the Barco NONE.
Actually the player app crashed on both IOP and SMPTE CPLs, even though
everything was 'green' - all content ingested fine, KDM attached to CPLs,
everything indicated 'OK'. But when playing, the Barco Player crashed and I
actually had to reset it using the reset button. The error msgs in the log
are similar to those I got when I tried to play encrypted DCP-o-matic
content - just that the player did not crash as hard on that DOM content (I
could still stop and continue working).
---
Feb 2 01:14:21 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame
It is not a smpte content
Feb 2 01:14:21 FFBARCO user.err SM: IMB Event- Security decryption error
starting at FrameId=0 on Channel=0 playBack=1
Feb 2 01:14:21 FFBARCO user.info SMS: Report- |SHOW-START|
[Sintel_SHR-1_S_EN-ES_DE_71_2K_BI_20151130_CPP_IOP_VF]
Feb 2 01:14:21 FFBARCO user.debug SMS: Player- Player subtitles: set gip
timeline: PLAY
Feb 2 01:14:21 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame
It is not a smpte content
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Event- J2K decoder event wd0=0
wd1=20000 at FrameId=0
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e00:
0bad0add 00000001 4a8101a1 00bb8019 00000080 00001001 00000000 00100000
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e20:
10000000 00000000 00000000 10000000 000007e8 00010320 00010320 00000211
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e40:
00000000 1510001e 00000000 00000000 00000000 00000000 00000100 0bad0add
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e60:
00000400 0bad0add 0bad0add 0bad0add 00410505 0bad0add 0bad0add 0bad0add
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1e80:
0bad0add 0bad0add 0bad0add 0bad0add 0bad0add 0bad0add 0bad0add 0bad0add
Feb 2 01:14:21 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame
It is not a smpte content
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1ea0:
0bad0add 0bad0add 00000000 00400600 0001c124 0000002d 0000002d 000034f9
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1ec0:
00000000 00ffffff 00000000 00000000 002e001c 00003333 00081000 00000333
Feb 2 01:14:21 FFBARCO user.debug SM: IMB Controller- debug info 1ee0:
4f93d152 0095121e 8a6bffff 00ffffff 02108400 00000000 00000000 0bad0add
Feb 2 01:14:22 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame
It is not a smpte content
Feb 2 01:14:23 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame
It is not a smpte content
Feb 2 01:14:24 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame
It is not a smpte content
Feb 2 01:14:25 FFBARCO user.warn SM: SM- PlayoutEventsHandler::checkFrame
It is not a smpte content
Feb 2 01:14:25 FFBARCO user.err SM: IMB Event- Security decryption error
starting at FrameId=300 on Channel=0 playBack=1
---
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
--
http://akadcp.com/
https://www.facebook.com/akadcp
10 a.m.
Am 02.02.2016 um 05:16 schrieb Manuel AC via DCPomatic:
Are you having problems with NON subtitled content?
Alchemy looks
pretty strict with subtitles.
Curious that Alchemy it's complaining about "checkFrame It is not a
smpte content" for an Interop DCP.
Yes - same error message for both Interop and SMPTE DCP...
- Carsten
11:11 p.m.
On Tue, 2 Feb 2016, Carsten Kurz via DCPomatic wrote:
Am 21.01.2016 um 18:58 schrieb Carsten Kurz:
Has anyone been successful in creating encrypted IOP or SMPTE DCPs for a Barco
Alchemy ICMP? I have tried with 2.6.16, both in IOP and SMPTE format,
SMPTE with Modified Transitional 1 and DCI specific.
These encrypted DCPs for our new Barco ICMP seem to be a real problem.
When I didn't succeed with DCP-o-matic, I asked one of the mastering
studios that we get commercial content from to issue a test-KDM for a
feature we were regularly playing on our Sony system. They replied
quickly with a center KDM for both the Sony and the Barco. That feature
played without issues on both systems. The KDM was created by Waimea
(CineCert). The Mastering System was Dolby.
Now, knowing that we have a Sony and Barco, they asked me wether I could
test content made on their new/future mastering system, and sent me
encrypted IOP and SMPTE versions of the SINTEL Short (with subtitles) to
test on both the Sony and the Barco.
Well, the SONY played all the content without any issues, the Barco
NONE. Actually the player app crashed on both IOP and SMPTE CPLs, even
though everything was 'green' - all content ingested fine, KDM attached
to CPLs, everything indicated 'OK'. But when playing, the Barco Player
crashed and I actually had to reset it using the reset button. The error
msgs in the log are similar to those I got when I tried to play
encrypted DCP-o-matic content - just that the player did not crash as
hard on that DOM content (I could still stop and continue working).
That's all very interesting. So we have DCP-o-matic and
new-mastering-system failing and Waimea working.
Can I see the DCP-o-matic and Waimea KDMs in case there is something in
the XML that is obviously different? It does seem unlikely considering
that the KDMs are ingested ok in both cases.
With best regards,
Carl
11:23 p.m.
Am 03.02.2016 um 00:11 schrieb Carl Hetherington via DCPomatic:
That's all very interesting. So we have
DCP-o-matic and
new-mastering-system failing and Waimea working.
Can I see the DCP-o-matic and Waimea KDMs in case there is something in
the XML that is obviously different? It does seem unlikely considering
that the KDMs are ingested ok in both cases.
It's probably too hard to believe that the MXF wrapping/encryption is bad (especially
since the Sony plays these 'commercial' DCPs both in Interop and SMPTE).
Then add to that the fact that our Sony doesn't play encrypted SMPTE DCPs created with
DOM... (still an unresolved issue).
I will forward the KDMs to you.
- Carsten
7 Mar
7 Mar
5:25 p.m.
Alright, now this issue has been fully resolved.
Turned out there is an optional feature in creating encrypted MXF files that is called
frame HMAC. The Barco ICMP would crash on trying to play MXF files missing these HMAC
tags.
Both DCP-o-matic and Colorfront Transkoder were not writing these (optional) HMAC tags,
and the Barco ICMP was the only server/media block who would actually crash on these
files.
As a result, I was not able to create encrypted INTEROP or SMPTE DCPs for our Barco ICMP.
The same DCPs would play without any issues on our Sony.
So, this issue now was resolved from both sides: Barco issued a firmware update for the
ICMP (1.2.2.11) which will accept MXF files that do not contain HMAC. Plus, Colorfront
Transkoder AND DCP-o-matic are now writing HMAC.
So, if you have trouble creating encrypted INTEROP or SMPTE DCPs for a Barco Alchemy/ICMP,
either have them update their ICMP software to at least 1.2.2.11, and/or use DCP-o-matic
from version 2.6.31 up.
Here is an explanation of what HMAC is from Mr. John Hurst:
'The HMAC (Hashed Message Authentication Code) is an optional set of values appended
to each encrypted picture frame. It allows the decoder to detect altered or re-ordered
frames. See SMPTE ST 429-6 for the details. Not only is the HMAC optional in the MXF
file, it is also optional decoder behavior, i.e., the decoder can ignore it when it is
present.'
- Carsten
7:37 p.m.
Thank you for all your work on this, Carsten.
On Mon, 7 Mar 2016, Carsten Kurz via DCPomatic wrote:
Alright, now this issue has been fully resolved.
Turned out there is an optional feature in creating encrypted MXF files
that is called frame HMAC. The Barco ICMP would crash on trying to play
MXF files missing these HMAC tags.
Both DCP-o-matic and Colorfront Transkoder were not writing these
(optional) HMAC tags, and the Barco ICMP was the only server/media block
who would actually crash on these files.
As a result, I was not able to create encrypted INTEROP or SMPTE DCPs
for our Barco ICMP. The same DCPs would play without any issues on our
Sony.
So, this issue now was resolved from both sides: Barco issued a firmware
update for the ICMP (1.2.2.11) which will accept MXF files that do not
contain HMAC. Plus, Colorfront Transkoder AND DCP-o-matic are now
writing HMAC.
So, if you have trouble creating encrypted INTEROP or SMPTE DCPs for a
Barco Alchemy/ICMP, either have them update their ICMP software to at
least 1.2.2.11, and/or use DCP-o-matic from version 2.6.31 up.
Here is an explanation of what HMAC is from Mr. John Hurst:
'The HMAC (Hashed Message Authentication Code) is an optional set of
values appended to each encrypted picture frame. It allows the decoder
to detect altered or re-ordered frames. See SMPTE ST 429-6 for the
details. Not only is the HMAC optional in the MXF file, it is also
optional decoder behavior, i.e., the decoder can ignore it when it is
present.'
- Carsten
3339
days inactive
3385
days old
7 comments
3 participants
participants (3)
-
Carl Hetherington -
Carsten Kurz -
Manuel AC