24 Oct
2017
24 Oct
'17
10:56 a.m.
Am 24.10.2017 um 12:12 schrieb Carl Hetherington:
On Tue, 24 Oct 2017, Carsten Kurz via DCPomatic wrote:
Do we know for sure that with these DSS-200 issues, the J2K/MXF was done by DOM - not
externally? I remember that Dolbys had sync issues not related to DOM years ago. Do we now
wether this is on current software?
The Barco ICMP is very explicit in it's log about decoder issues - just recently I
sent logs to a company using colorfront transcoder. I don't know any other server with
that level of detail in it's log.
I usually have our ICMP on the very latest software, and except for the initial HMAC issue
last year, never had problems. Admittedly, I think I have not created content for it with
2.11.x. I think the last one was a full length musical piece, but according to the CPL, I
did it with 2.10.5. There were no issues, that for sure.
Currently, Barco issues many service releases, there is a new version every few weeks.
Quite possible that one or the other contains a quirk.
- Carsten
Am I right that the 4k wavelet layer issue was the only recent change to the J2K in
2.11.x ?
It's the only one I can think of but I haven't checked carefully...