Film-Tech Forum ARCHIVE: Issue with Enigma link decryptor

This is topic Issue with Enigma link decryptor in forum Digital Cinema Forum at Film-Tech Forum ARCHIVE.

To visit this topic, use this URL:
https://ft-forum.com/ft/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic;f=16;t=001924

Posted by Tommy Zackariasson (Member # 6505) on 06-02-2014, 03:09 PM:

Just got an e-mail from our tech-company (translated by Google):

"BACKGROUND
During the first months of 2014 encountered a problem that affects everyone using serial 2 -
projectors. DLP projectors use all the PCB " Enigma Link Decryptor " Playback
encrypted movie content. For the server to accept the connection to the projector so it requires that a number of
conditions are met. One of these is that there is available space in Enigma card to store new
log files .
Enigma card should always be empty at the log files. An emptying of these done every time a show or a clip has
has finished in the server, but : If play is stopped and closed manually before it times out so
will no log files will be extracted .
A common example : Projectionist stops playback before it has been finished because no visitor is left
in the auditorium to see the credits . "
All digital cinema servers retrieves consistent only log files from the same day and time as the current
playback is stopped . So why will the next film screening unable to extract log files from the
previous display . This is the cause of the problem.
Cinemas has called into problems related to this information sheet has had one or more of the following
messages on their projectors. ( Error taken from a Barco Series 2 )
1.Code 5835 : "ti -link decryptor - security log is almost full" ( Error )
2.Code 5836 : "ti -link decryptor - security log is full" ( Error )
3.Code 5831 : "ti -link decryptor - system error" ( Error )
Showing your projector on the error No. 1, playing after the current display is not up any more films. only
a show to result in projector is locked and thus demonstrates the error No. 2.
Would your projector to show the error message # 2 must Enigman replaced. The logs are then already filled to
max and will not go to get out of the projector.
Would your projector to show the error message # 3 but not in combination with any of the others. Try first
and foremost, a reboot of the projector. This need not be related to the problem log .
The solution is a manual extraction via your streaming server . However, there are a few requirements
versions that must be met before this can be done.
Note , a manual extraction does not always work . In some cases , the cards have been beyond redemption of
other reason than that the log files had an earlier date. In these few cases, so having one or more log files in
Enigma The card has become corrupt and hence they can not be charged out of the card. The problem then is that, although the
logs which are not corrupt nor can be removed. The cards that ended up in the position can not be saved and
must be replaced."

Sorry about the poor translation but I think you get the picture.
It seems that if you have a ti link decryptor version earlier than 1.6.22 you should upgrade asap!

Posted by Carsten Kurz (Member # 5396) on 06-02-2014, 03:32 PM:

Search the forum, the LD-Log issue has been discussed here a couple of times.

There are two known issues, one recoverable (log full, server needs to download/empty ld-log memory), one non-recoverable (all LD-Log memory marked as corrupt).

I would think that sooner or later all DLP manufacturers need to move about it considerably, or will risk a class action suit. Until now it seems they simply want to keep this under the rug. Which seems ridiculous to me given the nature and potential number of issues.

- Carsten

Posted by Tommy Zackariasson (Member # 6505) on 06-02-2014, 03:40 PM:

Ok, missed that, sorry.

Tommy

Posted by Carsten Kurz (Member # 5396) on 06-02-2014, 03:44 PM:

Didn't mean to repress you, just hinting at other discussions and information.

Actually this issue needs to be brought to attention as much as possible, as it means lost shows.

Looks as if manufacturers do not want to issue clear statements towards it. It's a TI problem, so all series II DLPs sold/installed with a specific range of firmware versions and operated 'classic style' with HD-SDI are affected. With a clear conceding statement towards the issue, I guess manufacturers would face a high number of compensation claims, even for those units out of warranty.

- Carsten

Posted by Steve Guttag (Member # 268) on 06-02-2014, 06:39 PM:

I have made a bit of a study on this one and if you search the forums as Carsten mentioned you'll see MANY other discussions on the matter.

By the description, this is a Barco projector (their error codes). Depending on your server and software revision, one can take preemptive measures as well as likely download the logs. In the case of the Dolby server, one has to be on System 4.7.0 or higher and there is a CLI script behind a log in password that will allow one to tell the Enigma to downloaded EVERYTHING...it takes about an hour. And then after that...you'll need to run 16 5-second blank shows in 5 minute intervals to pull them again in about 512 hunks. I have done this now on all of our customers preemptively after it successfully recovered about 8 "almost full" conditions.

Now the nasty one is once the enigma is full, it is a brick unless you are TI to recover it.

The even more nasty one is the corrupted enigma...as I understand it, if there was a problem during a download...say you killed the projector power while the security logs were being downloaded...you could get a corruption. There are 16 banks in the Enigma, each with 512 entries. The trigger will be cocked...because when the system makes it through downloading 8190 logs over the course of months the normal way...when it gets to that corrupted entry...BAM, the enigma bricks.

I have determined that Christie is the least likely to have this problem (by sheer luck, in my opinion because I doubt they knew about this potential when they designed the projector). Christie puts the Enigma on the PIB module...which stays powered since that is also the communication system...as such, the Enigma probably never loses power suddenly. This is not the case for either NEC or Barco...both of which I've had Enigma issues.

The other server brands also have a means to force the download and I've heard mixed results.

Posted by Brad Miller (Member # 2) on 06-02-2014, 09:03 PM:

I can verify Dolby server version 4.7.0 does not fix the problem, and neither does 1.66.22 or 1.7 of the enigma software.

What Steve wrote is reality. My only recommendation for Barco and NEC owners is to NEVER turn the power off to the projector. As it has been explained to me, the enigma randomly does housekeeping (not just downloading logs at the end of a show) and if the power is interrupted during any enigma activity, then when the logs make their next round several months down the road...BAM it's dead (with no warning).

BTW the enigma "housekeeping" has no way to tell when it is happening, so even random power cycling of a Barco or NEC is a risk that will create a problem to surface several months down the road. (It won't "brick" the enigma at the time of the power cycle.)

Because of Christie's design, this issue is virtually non-existant.

Posted by Mike Blakesley (Member # 26) on 06-02-2014, 09:45 PM:

quote: Brad Miller
My only recommendation for Barco and NEC owners is to NEVER turn the power off to the projector.

Do you mean, never turn off the master power switches OR never shut it down? We shutdown every night but due to those flaky switches, the main power stays on all the time.

Posted by Steve Guttag (Member # 268) on 06-03-2014, 06:47 AM:

On a side note. Enigma 1.8 is said to address this problem. My crystal ball says to look for it in the August-September time frame.

I have yet to loose an Enigma since Dolby 4.7.x has been issued. Those that were almost full were returned to clean/green status those that were preemptively cleaned never developed an issue. Our customers do power the projector down nightly.

My personal opinion is that TI should be warranting these boards until they get their software right...it is a design flaw that is very expensive to deal with at the theatre level. Furthermore, OEMs refuse to have them fixed outside of the 2-year warranty.

Posted by Mark Gulbrandsen (Member # 72) on 06-03-2014, 02:51 PM:

Mike...

It's not really an issue with NEC-GDC. Although it used to be before a certain firmware version.

Mark

Posted by Tommy Zackariasson (Member # 6505) on 06-03-2014, 03:03 PM:

quote: Brad Miller
I can verify Dolby server version 4.7.0 does not fix the problem, and neither does 1.66.22 or 1.7 of the enigma software.

Now that is interesting Brad because this is what they say in the mail:
"If the (Dolby) server version is 4.7.0 or higher it doesn't need upgrading to solve the problem"
And later:
"If the Enigma is version 1.6.22 or higher it doesn't need upgrading to solve the problem"
Could it be that they mean that these versions are needed to be able to do the manual cleaning?

Posted by Carsten Kurz (Member # 5396) on 06-03-2014, 03:38 PM:

They may just be referring to the regular log memory readout. No server update can help with the corrupt memory issue leading to bricked enigmas once it's starts building up.

- Carsten

Posted by Marco Giustini (Member # 4544) on 06-05-2014, 05:10 PM:

I agree TI should be held responsible for this. They cannot simply ask the customer to replace the boards. It is a software flaw and the customers are paying for it. Nice way to do business.

Steve,
Will we be able to see 1.7 on Barco by the time TI releases 1.8? [Smile]

Posted by Steve Guttag (Member # 268) on 06-05-2014, 07:55 PM:

No, Barco has opted to skip 1.7 since it doesn't seem to bring anything to the table (they skipped 1.5 too).

Posted by Monte L Fullmer (Member # 2797) on 06-05-2014, 08:24 PM:

Wonder if that is what happened to us last Friday:

a DP2K-20C suddenly stopped during a performance (it has the SX-3000 IMB installed in the slot). Thus, following procedure with IMB installs is to: shut down the IMB via the TMS, then kill the power to the projector (by flipping the breaker in the panel that controls this unit since we have no said booths at this location...which can be a PITA at times..) wait for 10 seconds the turn on the projector and this powers up the IMB. Then, reconnect in the TMS.

This trick worked, but again, presentation shut down after 40 min into the presentation. This time, the tech was called, who just happened to be in the area, looked at it and couldn't totally figure it out and had to call GDC on this one for some help.

Found out that the cache log file in the BARCO was all but full which caused the shutdown.

There was a firmware update that the "ST" can clear out the cache.

I remember then, that with BARCOS, that the log files cache needs to be emptied out from time to time to prevent this shutdown to happen. Tech did the firmware update and clear out the cache and our issue was taken care of.

Now, what I presented above: would this be the same issue, or something else, for it sounds like what happened here with my description above.

Now, going back to what Brad mentions about not shutting off the units, I know of a lot of locations that do weekly cold reboots at least once a week, including us. Thus, are we in danger of what happened in the above case?

thx-Monte

Posted by Carsten Kurz (Member # 5396) on 06-06-2014, 05:31 AM:

These Enigma/LD-Log issues do not occur on IMB systems.

There was, however, a similar problem with a corrupt file system in ICP software below 3.0. This was also caused by projector shutdowns in conjunction with a software flaw. And it was persistent over consecutive ICP software upgrades once it started to build up.

- Carsten

Posted by Steve Guttag (Member # 268) on 06-06-2014, 06:29 AM:

The nasty thing about the ICP issue was that even if you updated to 3.0 and above but had started the corruption...you still have it! The only way to eradicate it was to perform an ICP update/recover. Each of the OEMs had a separate but similar procedure whereby one saves their ICP settings (screen, source...etc. files), wipe the ICP, reformat it, load software on it from scratch and then reload your stuff back on...in essence, you are doing the same thing as reformatting your HDD in your computer and putting everything back.

The Enigma also, below 1.5 could be corrupt via date information it had in it. Again, updating to 1.5 and above would not fix the problem...just prevent it from happening again. The corruption due to an interruption of an Enigma procedure, however, can and does, still happen in 1.5 and beyond. I hear 1.8 will finally fix that one. I also hear that Enigma 1.7 adds new commands, if your server takes advantage of them to improve log extraction beyond what they can do now. But it is a two-ended step that your server company must take advantage.

Posted by Frank Cox (Member # 6258) on 06-06-2014, 06:06 PM:

I have a Christie 2210 and a GDC server. Is this an issue that could affect me?

Posted by Steve Guttag (Member # 268) on 06-06-2014, 06:52 PM:

With a Christie S2 projector, the odds are diminished of the sudden power-off since the Enigma is on the PIB board, which remains powered (unless you kill the power to the projector).

However, you didn't specify the model of GDC. If you have an SX3000 OR a model with an IMB...then no you CAN'T be affected since there is no Enigma used for DCPs. But if you have an SX2000 or SX20001 (conventional mediablock) then yes, "you may be at risk"

Posted by Frank Cox (Member # 6258) on 06-06-2014, 07:17 PM:

I just checked. I have a Christie CP2210 and a GDC 2001A.

If this enigma thing could be an issue, is there anything that I can or should be doing to prevent problems?

Posted by Monte L Fullmer (Member # 2797) on 06-08-2014, 12:22 AM:

How about Doremi units? I know of ones that use the "Showvault" version.

Have to warn one owner that has a GDC 2100 full server at his drive-in location on this since he fully shuts his system totally off at the end of each night.

-Monte

Posted by Carsten Kurz (Member # 5396) on 06-08-2014, 11:59 AM:

It's not a server, but a projector issue. Just that some server types hint towards the usage of HD-SDI connections with the Enigma board in the projector.

E.g. a standard Doremi DCP2000 or a 2k4 would use HD-SDI towards the projector, which needs the enigma board for operation, hence the projector COULD be affected.

A ShowVault (or a 2000/2k4 CONVERTED to a ShowVault) uses an IMB into the projector, so the enigma board is or could be there, but is not used, hence no risc.

- Carsten

Posted by Vegard Olsen (Member # 8102) on 06-08-2014, 12:16 PM:

The Doremi have in Diagnostic Tool an option to "purge all projector logs" which will read all entries on the LD, similar to the script Dolby added in version 4.7.x. I believe Doremi introduced this option in version 2.2.5.

Posted by Carsten Kurz (Member # 5396) on 06-08-2014, 01:50 PM:

Again, this only solves the issue of full ld logs, when automatic download did not happen for a long time. It does not help with corrupt LD-Log memory and bricked enigma boards.

Also, the ICP memory corruption issue mentioned above is field serviceable. A bricked enigma is not.

- Carsten

Posted by Steve Guttag (Member # 268) on 06-16-2014, 01:25 AM:

It looks like NEC is the first out of the gate with Enigma 1.8!

Oddly, NEC changed their main software package (4.212) on the same date as they issued Enigma 1.8. It is odd in that NEC 4.212 still installs Enigma 1.7. They have one manually update the Enigma to 1.8 (still in the DCC but using the manual Enigma update buttons).

So it should be a matter of time before the other two follow suit. The next question is...do the server companies have to add new extraction commands to take advantage of the "improvements" to the Enigma or will it just fix itself/prevent corruption issues.

Posted by Marco Giustini (Member # 4544) on 07-07-2014, 12:13 PM:

NEC have released Enigma 1.8, how long will it take for Barco to add it?

Posted by Dave Macaulay (Member # 813) on 07-07-2014, 05:35 PM:

Barco seems happy to keep going with 1.6. I don't know when that will change.

Posted by Steve Guttag (Member # 268) on 07-07-2014, 06:41 PM:

My inside sources say that they were waiting for 1.8. So I think we'll see it by August.

Posted by Brad Miller (Member # 2) on 07-10-2014, 05:05 PM:

Barco added enigma v1.8 on June 30th.

Posted by Steve Guttag (Member # 268) on 07-10-2014, 06:53 PM:

Note, NEC, as of SP 4.214 now include Enigma 1.8 as part of the service pack. Also the DCC was updated to allow a hot button to read Enigma logs.

Looks like Christie will be the last out of the gate on this one but I would suspect that it hits the streets in the near future.

Note, the date from Barco was probably when it was approved for issue...it didn't hit My Barco until 7/10/14 (I've had my eye on it).

Posted by Mattias Mattsson (Member # 4308) on 07-11-2014, 01:15 AM:

Can anyone confirm if the Solaria Release v4.2.1 (2) released July 8th contains Enigma v1.8?

Posted by Steve Guttag (Member # 268) on 07-11-2014, 02:49 AM:

It does NOT...it has Enigma 1.7.

Posted by Nerijus Marmokas (Member # 6712) on 07-11-2014, 03:14 AM:

I have tried Barco's Enigma software v1.8(24) on a couple of enigmas with "logs full". The new software did the magic and skipped the "bricked" memory block. So now the boards are operational. Enigma now stores its logs in any free sector, it is no longer sequential.

I was this close to dumping the boards to the trash [Smile]

Funny that while these boards were in warning state, I couldn't fix the problem with any method that is known to me, while finally they were no longer operational. And this software update fixed all that just in minutes.
Of course it would have been awsome to have this update few years ago..

Nerijus

Posted by Carsten Kurz (Member # 5396) on 07-11-2014, 05:33 AM:

Who payed for the replacement boards in this case?

- Carsten

Posted by Nerijus Marmokas (Member # 6712) on 07-11-2014, 05:56 AM:

We did. The projectors which had the issue already had an expired warranty. Huge bummer, show stopper and unwanted expenses.
Also kind of weird that it is solved only now, when there are many other options, than to use LD board.
We have now 40 auditoriums in our country, but only 6 have LD. Others use Dolby IMB. And I know that many partner and competitor cinemas use IMB's also.
This software fix is awfully late.

Regards,
Nerijus

Posted by Marco Giustini (Member # 4544) on 07-11-2014, 10:46 AM:

same here, got the notification today.

Posted by Steve Guttag (Member # 268) on 07-11-2014, 01:37 PM:

The problem, in my opinion was where the "pain" was applied. Since you have no direct relation with TI...and it was the TI board with the problem...if the projector warranty expired, you were hosed because it wasn't a projector problem. It took until TI go around to fixing their software issue to resolve their problem with their product. I agree that it is awfully late for something so catastrophic (and expensive) in nature.

Personally, I STILL prefer to use conventional HDSDI lines and conventional mediablocks (e.g., CAT862 for Dolby) than anybody's IMB. They just seem MUCH more reliable and there isn't any "order" to shutdowns.

If you aren't doing HFR 3D or 4K, the IMBs bring little to table other than notably increased failure rates. Now some of the smaller projectors either don't give you the option or one loses things like the DVI inputs if you have the HDSDI board so you don't have an option there.

Posted by Mattias Mattsson (Member # 4308) on 07-11-2014, 06:38 PM:

Steve, thanks for the info!

Posted by Marco Giustini (Member # 4544) on 07-12-2014, 04:15 PM:

Nerijus,
Thanks for letting us know.

Then whoever kept that bucket of bricked Enigma can put them back to stock, interesting.
The whole saga has been ridiculous. TI should have acknowledged the bug, fixed it and provided FOC replacements.
Now customers paid for new Enigma and TI/Manufacturers/Installers have working Enigma for free. Nice.

Posted by Carsten Kurz (Member # 5396) on 07-12-2014, 05:56 PM:

Yep. Should one feel relieved that it's finally solved or be frustrated about something like this actually happened...

OEMs should have carried this towards TI instead of charging for replacement boards. I guess OEMs AND TI could have ensured early on that this issue can be resolved and that swapped boards can be revitalized later with no risc.

- Carsten

Posted by Steve Guttag (Member # 268) on 07-13-2014, 09:55 AM:

About the bucket of Enigmas...if you didn't keep them charged...they are dead bricks and can't be revived by mere mortals.

Posted by Steve Guttag (Member # 268) on 07-15-2014, 06:35 AM:

Just a note to say I have now revived one of our bricked Enigmas from the dead (it was kept charged after it bricked). Enigma 1.8 brought it back to life...didn't even have an "Almost Full" warning either. It was ready to run movies once updated.

Posted by Harold Hallikainen (Member # 5405) on 07-15-2014, 06:40 AM:

USL has a product to keep Enigmas powered. I don't remembervwhat it's called, though.

Harold

Posted by Clint Koch (Member # 1179) on 07-15-2014, 01:43 PM:

EP-100 is the USL part number.

Posted by Pete Naples (Member # 761) on 07-15-2014, 02:35 PM:

Does it come with a pill box? [beer]

Posted by Clint Koch (Member # 1179) on 07-15-2014, 03:38 PM:

Why yes, it does.

Posted by Carsten Kurz (Member # 5396) on 07-15-2014, 07:36 PM:

It even comes with a brochure ;-)

http://ftp.uslinc.com/ftp/Products/EP-100/Documents/Manual/EP-100_manual_140206.pdf

- Carsten

Posted by Brad Miller (Member # 2) on 07-21-2014, 11:25 AM:

quote: Steve Guttag
Just a note to say I have now revived one of our bricked Enigmas from the dead (it was kept charged after it bricked). Enigma 1.8 brought it back to life...didn't even have an "Almost Full" warning either. It was ready to run movies once updated.

Thought I would chime in with another example. I had an enigma go into "security logs full" without warning this morning on a Barco. Updating to 1.8 (followed by a projector/server reboot) immediately brought it back to life ready to go just as Steve reported. [thumbsup]

Posted by Marco Giustini (Member # 4544) on 07-21-2014, 01:15 PM:

if I were a customer who lost money and shows on this issue, I would be seriously angry.

Posted by Steve Guttag (Member # 268) on 07-21-2014, 01:18 PM:

Oh...they already are!

Posted by Mark Gulbrandsen (Member # 72) on 07-21-2014, 01:31 PM:

I haven't had this problem. [Cool]

Posted by Marco Giustini (Member # 4544) on 08-06-2014, 02:51 AM:

What happens when the battery on the Enigma goes flat? Will the board become completely unresponsive? I got an old 'logs full' Enigma out of the rubbish but the projector says 'no communication' (it was giving the 'logs full' error before). Can I assume that it is just too late?

Posted by Brad Miller (Member # 2) on 08-06-2014, 03:31 AM:

Yup, the battery died since it wasn't recharged.

Note it takes about 48 hours to do a full charge on one of those batteries.

Posted by Marco Giustini (Member # 4544) on 08-06-2014, 12:40 PM:

Thanks Brad.

I'll use it as a doorstop.
TI could have at least told us "we'll fix it sooner or later" and we would have kept them charged.

Posted by Marcel Birgelen (Member # 6801) on 08-06-2014, 06:37 PM:

I'm wondering, why does the Enigma actually need a battery? Both configuration and logs are stored on internal flash and it also doesn't need to keep track of time...

So, is it really just for tamper detection?

Posted by Steve Guttag (Member # 268) on 08-07-2014, 06:28 AM:

Actually no...it DOES keep track of time and has the same time adjustment restrictions on it. Its clock and the "secure clock" are actually different clocks. All of the OEMs have a means to set the Enigma clock via their own programs plus one, if they have the right access, can set the clock directly using TI's program.

What is lost is its certificate once the battery dies. No certificate, no Enigma. Since it is the high-security thing it is going to be the most fussy.

There was no promise that TI would "fix" the problem. What they did seems so obvious (not require a sequential log storage areas...skip over anything corrupt) one would think they would have gotten that one on the first "bricked" Enigma that came back under warranty. I think TI was VERY asleep at the wheel on the Enigma. It has been a nuisance since day one. It could self-corrupt, each fix seems to be relating to that and this final one was basically ignoring its self-corruption. What we don't know is with Enigma 1.8, if one runs a script like Dolby's getAllProjectorLogs, if it will force read all of the logs such that the corrupted entries get cleared. I'm crossing my fingers that it does. However with 8192 entries and only 512 needing to be available to avoid an "almost full" condition, this will probably push any future potential problems out beyond the life of the projector.

Posted by Marcel Birgelen (Member # 6801) on 08-07-2014, 01:48 PM:

quote: Steve Guttag
Actually no...it DOES keep track of time and has the same time adjustment restrictions on it. Its clock and the "secure clock" are actually different clocks. All of the OEMs have a means to set the Enigma clock via their own programs plus one, if they have the right access, can set the clock directly using TI's program.

And for what reason does it need to keep track of time on its own? To check if the certificate (which actually shouldn't expire) is still valid?

And this certificate and private key, are you sure it's only stored in volatile memory? Because that sounds somehow utterly awkward... Although, I could be one of their paranoid black box security measures... If you open the seal it will kill the power and the memory will lose its content within a few seconds.

Posted by Steve Guttag (Member # 268) on 08-07-2014, 02:22 PM:

The log entries are done based on IT's time, not the mediablock's secure time. The Enigma is a self-contained unit. It does have its own tamper switches too...which will also clamp it down tight. Oh, that device is all about paranoia. I'm not defending it in the slightest either.

Posted by Carsten Kurz (Member # 5396) on 08-07-2014, 02:42 PM:

TI probably did not want any of these security relevant modules to circulate as spare parts year after year in the wild, I could imagine.

- Carsten

Posted by Marco Giustini (Member # 4544) on 08-07-2014, 03:25 PM:

I believe they just don't care. Thousands of "faulty" enigmas have been replaced worldwide. Customers have paid for them till the last penny. Happy days.

Posted by Steve Guttag (Member # 268) on 10-27-2014, 01:47 PM:

Christie has issued 4.2.2 (2) which contains Enigma 1.8.24 which should end this silliness once and for all. All three DLP companies now have an Enigma 1.8 update.

Posted by Carsten Kurz (Member # 5396) on 10-27-2014, 04:20 PM:

Which Barco release did contain Enigma 1.8 first?

- Carsten

Posted by Magnus Eriksson (Member # 6085) on 10-27-2014, 04:58 PM:

Barco_DriversFirmware_R33023501
/M.E.

Posted by Carsten Kurz (Member # 5396) on 10-27-2014, 05:44 PM:

Thanks. Hmm, are you sure? Strange, I just notice Barco still offers Enigma 1.6 from 2012 under device specific software/drivers. Barco R33023501 still references that version. I read here Barco skipped 1.7, but does R33023501 really contain 1.8?

Edit: Hmm, seems Enigma 1.8 comes with Barco 1.12.160 for B/C series and 1.3.44 for S series?

- Carsten

Posted by Magnus Eriksson (Member # 6085) on 10-28-2014, 03:11 AM:

Yes, I see what you mean. Barco obviously keep the R-number even if the sw version is changed.
"DP2K Linkdecryptor Enigma" 1.8.24 was released 30 June 2014.
/M.E.

Posted by Steve Guttag (Member # 268) on 10-28-2014, 06:58 AM:

Barco doesn't package, to the best of my knowledge, the TI software (either Enigma or ICP) with their software. They keep them separate and can be updated separately. Now they do recommend certain combinations...particularly ICP versus projector software.

Posted by Marcel Birgelen (Member # 6801) on 10-28-2014, 07:59 PM:

Barco indeed doesn't "package" their separate firmware/software updates into large packages.

But that R-number, isn't that just the Barco internal identification for the "Enigma package"? Because, the actual version numbers are usually appended to the R-number.