Tweet
Lots of good advice here.
+1 for reseating the Dolphin board.
+1 for reseating the Dolphin board.
-
-
Back with an update, and it's good news, as we're back up and running, with both unencrypted and encrypted content.
Yesterday we reinitialised the RAID, which didn't make an improvement, and then took out, cleaned the contacts of, and reseated the Dolphin board in the Doremi, and that did. Ran some unencrypted trailers, and then the Dolby Encrypted DCP test, and both ran without any issues whatsoever. We dumped another log after playing those, and there were no issues shown aside from the NTP server, which I still need to resolve.
Thank you everyone for all the help and advice here - we're very relieved to be back up and running. We've not even had any proper shows with this equipment yet - it's only been a couple of test screenings for us, nothing public. Hope to change that soon!
The advice on how to keep this equipment going and batteries charged is also very useful. When I had the Dolphin card out I measured the battery and it's showing a very healthy 3v. We also now plan on regularly powering up the projector for 24 hours to keep the battery in its SDI board charged. I'll also be adding a NTP server to the rack at some point soon - currently the times are actually pretty accurate, and within a few seconds of each other. But I'll add a NTP server so they can stay in sync, and to resolve that warning.
The only other warning was on the firmware being out of date - my understanding is that to upgrade the firmware, we need both the upgrade key from dolbycustomer.com, and a the firmware files themselves, which are on Dolby's FTP site for the "service" login - is that correct? None of us have that login at the moment, and Dolby have been typically cagey about giving this sort of thing to us so far.Comment
-
You need indeed both the software and the upgrade key, the later you can generate yourself.
When upgrading, please notice the public release notice about the upgrade path to follow:
Servers on 2.2.x software version, need to be updated to 2.4.4, then 2.6.4 before updating to 2.8.x software.
Servers on 2.4.x software version, need to be updated to 2.6.4 before updating to 2.8.x software.
For access to the software itself, instead of just mailing cinemasupport [at] dolby.com, if you have already an account for the portal, try opening a case. If that doesn't help, reach out here, someone might be able to help as kind of a last resort.
As soon as you can afford it, it's good to try to get in touch with a local integrator to help you with those kind of issues. They usually won't come free, but refunding already sold tickets and managing those broken expectations is in most cases more harmful for your business.
Comment
-
If you have a regular Windows PC on the same LAN as the projector and server, you can use that as a NTP server - instructions attached.Comment
-
The software is already on 2.8.x, it's just the firmware that needs updating. And thanks for the advice on getting the firmware, we'll open a ticket with Dolby to try and get it.Originally posted by Marcel Birgelen View Post
Sadly we don't, and there is no internet connection in the venue either, so having a computer would cause time drift too. I'll be making a little NTP server with a microcontroller (ESP32) that gets time from GPS so it can get the time accurately on startup - got all the parts, just need to put them together.Originally posted by Leo Enticknap View Post
Comment
-
Would that be a stratum 0 or 1 ntp server then?
If not, she ain't a-gonna fly.Comment
-
It would be a Stratum 1 server, as it is directly connected to a reliable UTC clock source (GPS in this case).
A Stratum 0 server would require a direct connection to a reliable clock (most likely an atomic clock) synced to UTC.
Edit: Smarty-pants auto-correct "corrected" UTC to UTP...
Last edited by Marcel Birgelen; 06-18-2024, 01:56 AM.Comment
Comment