Film-Tech Cinema Systems
Film-Tech Forum ARCHIVE


  
my profile | my password | search | faq & rules | forum home
  next oldest topic   next newest topic
» Film-Tech Forum ARCHIVE   » Operations   » Digital Cinema Forum   » extracting logs from a Barco DP2K-23B / also link decryptor full error (Page 2)

 
This topic comprises 4 pages: 1  2  3  4 
 
Author Topic: extracting logs from a Barco DP2K-23B / also link decryptor full error
Steve Guttag
We forgot the crackers Gromit!!!

Posts: 12814
From: Annapolis, MD
Registered: Dec 1999


 - posted 09-19-2013 10:51 AM      Profile for Steve Guttag   Email Steve Guttag   Send New Private Message       Edit/Delete Post 
The LD log thing is not unique to Barco, it is really an Enigma problem (TI) in how it marks the logs and what it reports to the servers as "read" and not read. The enigma has 16 banks of 512 logs or 8192 entries. If there is corruption anywhere in a bank, that whole bank is essentially dead...as each bank dies, there is less an less room until you are down to the last one. When that one starts to fill up or gets full, it is a brick, for all intents and purposes.

TI issues a new firmware, 1.7, earlier this year (I don't think it was as early as January...more like April but it was some months ago. Both NEC and Christie have it in their current software. For NEC it came with 4.201 and for Christie it was on 4.1.0(3). As Brad notes, it has not been issued for Barco yet. Though, I suppose one could take it from an NEC service pack, if need be.

However, there is another piece to the puzzle. TI has created new commands to allow the server manufacturers to extract the logs differently or more completely (as I understand it). So in order to take advantage of the new commands, the server companies have to put it into their software too.

I know that Dolby does not have it in their current software but it is slated to go in pretty soon.

I don't see how it could be a Barco issue as this is communication directly between the Enigma and the server and is not projector specific. Furthermore, I've had it happen on non-Barco projectors.

Brad identified the best attempt at clearing the Enigma when it gets to the "almost full" state. That is, break the marriage to force a DCI required 512 log download and then run 16 shows (one for each bank) with a 5-10 second blank clip in it. To do it automatically, allow for at least 5 minutes for downloading the full 512 logs so set up shows with 5 minutes of break between them and let the thing run its course.

What would be nice is if there was a "button" that one could force a full log extraction from the Enigma...regardless if it was already marked "read". Just force it to barf the whole thing.

I don't think either TI, the Projector companies nor the server companies have moved NEAR fast enough of this as it will cause loss of show, income and now that these enigmas are our of warranty on the 2010 projectors, it will also cost $$$ to replace. TI should extend the warranty on these until the problem is actually fixed. The theatres didn't break the thing...it isn't physically broken...it is a software bug created by TI.

 |  IP: Logged

Marco Giustini
Film God

Posts: 2713
From: Reading, UK
Registered: Nov 2007


 - posted 09-19-2013 12:16 PM      Profile for Marco Giustini   Email Marco Giustini   Send New Private Message       Edit/Delete Post 
Agreed. At the very least they should release a software to recover a broken Enigma. Maybe DCI does not allow it, but I'm sure a workaround could be done: it could authorised on a case by case basis for example, like an update KDM.

I'm sure that those faulty enigma go back to the factory where someone plugs a cable to it and press a button.

 |  IP: Logged

Pete Naples
Phenomenal Film Handler

Posts: 1565
From: Dunfermline, Scotland
Registered: Feb 2001


 - posted 09-19-2013 01:50 PM      Profile for Pete Naples   Email Pete Naples   Send New Private Message       Edit/Delete Post 
The LD firmware is separate from the ICP Dave, I think Barco are currently on a lower revision than others.

 |  IP: Logged

Marco Giustini
Film God

Posts: 2713
From: Reading, UK
Registered: Nov 2007


 - posted 09-19-2013 02:10 PM      Profile for Marco Giustini   Email Marco Giustini   Send New Private Message       Edit/Delete Post 
Dave,

when the LD bricks you can purge it as you mentioned as many times as you want, but you won't clear the error. The procedure takes, as you say, 45 minutes and the error won't clear up.

 |  IP: Logged

Steve Guttag
We forgot the crackers Gromit!!!

Posts: 12814
From: Annapolis, MD
Registered: Dec 1999


 - posted 09-19-2013 04:18 PM      Profile for Steve Guttag   Email Steve Guttag   Send New Private Message       Edit/Delete Post 
Marco, when you tried this on a "bricked" Enigma (using the Doremi Purge)...what version of Enigma software was running? 1.6 or 1.7?

 |  IP: Logged

Carsten Kurz
Film God

Posts: 4340
From: Cologne, NRW, Germany
Registered: Aug 2009


 - posted 09-20-2013 05:59 AM      Profile for Carsten Kurz   Email Carsten Kurz   Send New Private Message       Edit/Delete Post 
Wow. Is this real? Sounds like a real problem. I thought it was solved last year when Doremi came out with this LD-Log fix. Apparently not. Are we going to see enigmas bricked in huge quantities soon? Are the OEMs going to let this happen?

- Carsten

 |  IP: Logged

Steve Guttag
We forgot the crackers Gromit!!!

Posts: 12814
From: Annapolis, MD
Registered: Dec 1999


 - posted 09-20-2013 08:09 AM      Profile for Steve Guttag   Email Steve Guttag   Send New Private Message       Edit/Delete Post 
So far, the answer is YES...they are going to let this happen! Again, this is a two part puzzle. You have to have Enigma 1.7 (two out of three projector companies have this) and the server companies have to take advantage of the new commands available in 1.7...I don't know of anyone other than Doremi that has that. I just know that others are "working on it." Also Barco is to release 1.7 Enigma any day now (been like that for months though).

 |  IP: Logged

Ken Lackner
Phenomenal Film Handler

Posts: 1907
From: Atlanta, GA, USA
Registered: Sep 2001


 - posted 09-20-2013 08:49 AM      Profile for Ken Lackner   Email Ken Lackner   Send New Private Message       Edit/Delete Post 
I'd like to chime in here.

Barco 32B with Barco version 1.8.85 and TI 3.2.340, including Enigma v1.6.
Doremi DCP-2K4, fw 21.3r, sw 2.2.5-0, sm 2.0.15-0

I've received several calls over the last year that the show would not play due to the security log full issue, and purging the LD logs from the Doremi Diagnostic Tool has always solved the problem. Never has the projector been rendered permanently inoperable due to this issue, although a show will be lost since it takes 30-45 minutes to purge the logs. I now have the site do this once a week and haven't had any complaints in months.

Steve, are you saying that the bricked Enigma issue is introduced in 1.7, or corrected in 1.7? I'm a little confused. Like I said, this projector is running 1.6, and logs can always be cleared to restore normal operation. I've never had to break the marriage to fix or prevent this.

 |  IP: Logged

Marco Giustini
Film God

Posts: 2713
From: Reading, UK
Registered: Nov 2007


 - posted 09-20-2013 09:40 AM      Profile for Marco Giustini   Email Marco Giustini   Send New Private Message       Edit/Delete Post 
Steve,

I've come across several LDs with the logs full issue, some were on 1.4 and some on 1.6. I have never been able to restore an LD using the doremi tool - or the Dolby procedure. Logging onto the Enigma, all logs are marked as "read", but the projector is still reporting the error.

Usually when I come across a bricked 1.4 Enigma I upgrade it to 1.6 hoping that that would fix it, but so far I have never been successfull.

Ken,

1.4 has a known bug where some logs could be created with a future date - hence never cleared. That was fixed with 1.6 but that hasn't prevented some LDs to report a "log full" condition which cannot be addressed in any way.

I do not know what 1.7 is doing, hopefully will prevent such stupid issues to happen again.
As I said, I understand that DCI do not want TI to release tools which can reset the heart of the security on a projector, but maybe they could consider releasing a special tool for these circumstances, it's just nonsense that cinemas have to lose shows for this.

 |  IP: Logged

Pete Naples
Phenomenal Film Handler

Posts: 1565
From: Dunfermline, Scotland
Registered: Feb 2001


 - posted 09-20-2013 10:19 AM      Profile for Pete Naples   Email Pete Naples   Send New Private Message       Edit/Delete Post 
The phrase 'not fit for purpose' springs to mind.

 |  IP: Logged

Ken Lackner
Phenomenal Film Handler

Posts: 1907
From: Atlanta, GA, USA
Registered: Sep 2001


 - posted 09-20-2013 10:31 AM      Profile for Ken Lackner   Email Ken Lackner   Send New Private Message       Edit/Delete Post 
So then how come the Enigma mentioned in my previous post is not becoming bricked when the issue occurs? Is the projector experiencing a different issue with similar symptoms? I thought maybe it was one of those issues that doesn't happen every time, but you guys are saying you have never been able to recover an Enigma once this happens, and I have always been able to.

I still think there is something I am missing here.

 |  IP: Logged

Carsten Kurz
Film God

Posts: 4340
From: Cologne, NRW, Germany
Registered: Aug 2009


 - posted 09-20-2013 01:48 PM      Profile for Carsten Kurz   Email Carsten Kurz   Send New Private Message       Edit/Delete Post 
I think Steves post on top of page 2 explains this. One issue is the LD-Log filling up. That can be cleared using serverside software or tools, and that's probably what you have been lucky with so far. I think TMS based Doremi systems suffered from this issue a lot because it is common for these systems to run all day and to have playlists pushed around all the time, while the server routinely would only store and clear the logs with no playlist loaded.

The other more serious issue seems to be log memory banks becoming corrupted. As more and more of them become marked bad, there is less and less log memory available - until the bitter end, where clearing the log memory doesn't help anymore, as it doesn't fix the corruption.

- Carsten

 |  IP: Logged

Steve Guttag
We forgot the crackers Gromit!!!

Posts: 12814
From: Annapolis, MD
Registered: Dec 1999


 - posted 09-20-2013 02:36 PM      Profile for Steve Guttag   Email Steve Guttag   Send New Private Message       Edit/Delete Post 
Enigma 1.7 does not "fix" nor "introduce" problems, it merely has new commands available to server manufacturers to clear the problems it already has.

As others have noted, 1.6 stopped some of the corruption issues that occurred in Enigma 1.4 but DIDN'T FIX them...if you got a corruption already, it stays!

Ken, your logs filling up may be due to the server itself not downloading the logs frequently enough. That is different. This can occur if shows are tightly spaced and there isn't sufficient time to download the logs...if enough of those events occur, then the logs can fill up and "purging" them will download them, finally.

The bricking issue is not that...it has to do with corruption where the server CAN'T download the logs. The Engima reports everything is read to the server but it claims logs are almost full or full. Once it is "full" then it is bricked and it would seem servers can't talk to it anymore. At least the Dolby server can't talk to it anymore. This is the one that I've had the most experience with.

 |  IP: Logged

Marco Giustini
Film God

Posts: 2713
From: Reading, UK
Registered: Nov 2007


 - posted 09-20-2013 03:19 PM      Profile for Marco Giustini   Email Marco Giustini   Send New Private Message       Edit/Delete Post 
Ken,

Keep also in mind that interrupted shows generate more security logs for the server to download.

If you play a short clip on a Dolby server, you'll see that at the end just a few logs are downloaded. If you keep stopping the same clip before it ends, the first time you allow the clip to reach its end you'll see the server downloading many more logs.

I guess some cinemas may not have enough time between playlists for the Doremi to download the logs (it begins 5 minutes after the server has been idle on recent software), or stop the playback before the end - which prevents the Dolby from downloading.
If you keep doing so for a while, eventually you end up with the "logs almost full" and it's only a matter of allowing the server to download them.

 |  IP: Logged

Steve Moore
Expert Film Handler

Posts: 211
From: Leeds, West Yorks, UK
Registered: Apr 2008


 - posted 09-20-2013 04:23 PM      Profile for Steve Moore   Email Steve Moore   Send New Private Message       Edit/Delete Post 
So is clearing or purging logs on a Doremi (all the ones in our circuit are DCP2000) an essential thing to do on a regular basis, are you all saying? We are all running Christie CP2000s, series 1 machines. Are we likely to all suddenly get the same problem and not be able to run a show if a log gets full? Are there various different logs I should be clearing. Has there been a post before on FT.com which explains what the various logs are for or what they store?

 |  IP: Logged



All times are Central (GMT -6:00)
This topic comprises 4 pages: 1  2  3  4 
 
   Close Topic    Move Topic    Delete Topic    next oldest topic   next newest topic
 - Printer-friendly view of this topic
Hop To:



Powered by Infopop Corporation
UBB.classicTM 6.3.1.2

The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion and agrees to release the authors from any and all liability.

© 1999-2020 Film-Tech Cinema Systems, LLC. All rights reserved.