|
|
This topic comprises 3 pages: 1 2 3
|
|
Author
|
Topic: Dolby DSS100 Show Manger Software upgrade to 4.8
|
|
|
|
|
|
|
Leo Enticknap
Film God

Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 05-20-2019 12:58 PM
Yes, using the Barco Communicator PC app running on a PC hooked to the same LAN as the projector.
However, if you have not run the projector that way before (from your message, I'm guessing that you operate the projector solely using the side button panel and cues sent from the server), the setup involved is significant, and you'd need to register on mybarco.com to download Communicator.
A much easier way would be to email Barco with the serial number of your projector, as described above. That number should be on a label, either on the side of the projector near the lamphouse cover, or on top of it next to the lamphouse vent opening. From that number, they should be able to tell you if your projector shipped with a type 4 or 5 board in it, as Dave describes. If they tell you that it did, then I think you need a tech to update the projector and recover the TLS certificate if and as needed, then update the server and media block.
| IP: Logged
|
|
|
|
|
|
|
|
|
|
Marco Giustini
Film God
Posts: 2713
From: Reading, UK
Registered: Nov 2007
|
posted 05-23-2019 04:33 AM
Stephan, Are you sure about Cinelink I on DCI version for DSP100? I thought one point of the DCI version was the inability of running CineLink I.
Anyway, the best way is to test enable CineLink II TLS on your DSP. It's really easy and that will give you *THE* answer. You can revert to Cinelink II DH at the end if it does not work.
(I'm going by memory here) - With the server fully booted up, press CTRL-ALT-F1 to get onto terminal - log in with user (administrator) and password (password is on the manual, on the upgrade section - on my manual it's section 4.6.2) - Get into the script folder by typing cd scripts (enter) - type the following command
./linkencrypt.sh TLS
- that will enable TLS. You will lose connectivity with the mediablock for a few seconds. When the mediablock is back, it's in TLS mode.
- Go back to GUI by pressing CTRL-ALT-F8 - Your projector may or may not reconnect at this point, give it a couple of minutes. - If it does not reconnect, power cycle both server and projector and see what happens.
- If the projector really does not reconnect anymore (give it plenty of time), follow the steps above to put the projector back to the original encryption but change the line you type to
./linkencrypt.sh DH
- then reboot etc.
(Still, if it does not work, you could try running the certificate recovery procedure but I'd leave that for later)
| IP: Logged
|
|
|
|
Leo Enticknap
Film God

Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 05-23-2019 10:01 PM
I once had Cinelink I running on a DSS200 with an NEC NC2500 that had a non-Gore board interface board (one that could not do TLS, period). This was in 2016 - can't remember what version the 200 was on, but likely 4.7 or 4.8.
The only potential gotcha there is that if ever the server needs to be replaced with one that is not a Dolby DSS model, and the projector really can't do TLS, you're in trouble.
quote: Jesse Clifford Well, after a bunch of calls to manufacturers and techs it seems as though the projector (Barco DP2000) will not be compatible due to the fact that it is a series 1 projector. I am at a loss of what my next step can be. Like I said, this is a small town theater and they had just got this used 4 years ago and I know they do not have the money to purchase a new projector. Any help is very much appreciated.
I hope this doesn't come across as a flame, but we've already made a number of suggestions for how to address this, and explained that most of the Series 1 projectors currently in use can be made to work with fully DCI-compliant servers and media blocks.
Maybe I'm reading too much into this, but I get the impression that you don't want to call a tech out to work on your system if it can't actually be done. I understand your situation: looking at a map, you appear to be located roughly equidistant, about 400 miles, from Denver, Kansas City and Minneapolis/St. Paul, which I'm guessing are where the nearest Barco and Dolby trained techs are located. So getting one to your theater is going to be seriously expensive: a day's travel in each direction, plus at least one overnight stay, over and above the cost of the callout itself.
That having been said, if you want to make progress fixing this without having to do that, you might need to take a risk in going outside your comfort zone, and try some of the things we've suggested here.
Running your projector's serial number by Barco and asking them if the input board is TLS compatible or not does not need any specialist technical knowledge. If they tell you that it is (i.e. that it has a type 4 or 5 board in it), then at least you know that if you do call a tech out to your location, that they will be able to upgrade the projector and server to make them fully DCI compliant. The only other thing you'd need is an upgrade KDM for the DSP100, and the vendor you choose to get a tech out should be able to take care of that for you. You could also have the tech do planned maintenance on both while (s)he is there, thereby killing two birds with one stone.
If you want to go further without professional help, then the suggestions we've made in the replies above include:
- Putting your media block into TLS mode and seeing if you can still play DCPs. If you can, then you know that you can upgrade the server and media block software to 4.7.8.7 (fully DCI compliant, and will play most SMPTE DCPs). If you can't, the cause may be a known issue (TLS certificate recovery) that is fixable by a tech, but it may also be that you have an incompatible board.
- Checking the version of the TI card in your projector using Barco Communicator, to establish hardware compatibility.
- Trying Cinelink I.
If you don't feel confident doing any of this stuff, and still want to make progress in getting your system DCI compliant and reliable for use with SMPTE DCPs, I'm afraid that there probably isn't any way around getting a tech out to your location.
| IP: Logged
|
|
|
|
Leo Enticknap
Film God

Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 05-24-2019 01:51 PM
It would, but I get the strong impression from the OP's earlier posts that there is very limited technical knowledge at this site, and that even setting up a PC with Teamviewer that is connected both to the management LAN and the Internet might be a stretch for them.
I've learned through bitter experience in the last couple of years that you have to think quite carefully about how much self-help an end user is able to bring to the table in cases like this. If it's not enough to assist with the remote access work effectively and without the risk of misunderstandings resulting in the tech hundreds of miles away barking up the wrong tree, then it's best for everyone involved to recommend a tech callout, even if, as in this case, we're looking at a lot of travel time. If the tech callout is planned thoughtfully, then it can be a good investment for future troubleshooting, e.g. (s)he installs and sets up a remote access PC while on site.
The reason that I suggested that he runs the projector's serial past Barco and finds out from them whether it has a TLS-compatible board or not is that if it does, and he knows for sure that it does, then that removes the risk that he'll spend significant money having a tech drive for several hours to the theater, hook his laptop up to the projector, say, "Very sorry, Sir, but this can't be done" three minutes later, and then drive straight back again.
As for Cinelink I, the only red flag I can think of is that, as far as I know (and please correct me if I'm wrong), the Dolby DSS servers and media blocks are the only ones that can use Cinelink I with a fully DCI-compliant software version. Therefore, for example, if this DSS100/DSP100 dies and is replaced by, for example, a second hand Doremi or GDC with DCI-compliant software already installed, then if the projector really can't do TLS (IMHO a small risk, but one that can't be ruled out until it's checked out), then the end user is in trouble. But as a short-term workaround, it'll work.
| IP: Logged
|
|
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 3 pages: 1 2 3
|
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.
|