my profile | my password | search | faq & rules | forum home

» Film-Tech Forum ARCHIVE   » Operations   » Digital Cinema Forum   » Dolby DSS100 ajust time (Page 1)

This topic comprises 2 pages: 1  2

Author Topic: Dolby DSS100 ajust time Michel Pomerleau Film Handler Posts: 3 From: Magog, Quebec, Canada Registered: Aug 2012 posted 03-02-2015 05:47 PM                     Hi, the DSS100 dosen't have the exact time, it has 5 min off the real time, and the show start always 5 min late, there is a way to ajust the time, it is connected to a Doremi TMS, the TMS have the right time.  |  IP: Logged Leo Enticknap Film God Posts: 7474 From: Loma Linda, CA Registered: Jul 2000 posted 03-02-2015 05:59 PM                        With a 200, you can change the time in the BIOS settings. Dunno if this applies to a 100 as well.  |  IP: Logged Mike Renlund Film Handler Posts: 71 From: San Francisco Registered: Feb 2008 posted 03-03-2015 12:01 PM                     You can set the DSS100 motherboard time via the BIOS just as you can on the DSS200. Power off the DSP100. Reboot the DSS100 and tap the DEL key during the initial start-up of the unit. You will be taken to the BIOS. Change the time to be correct. Then save and exit the BIOS. Allow the DSS100 to fully boot into Show Manager. Power up the DSP100 and let it connect to the ShowStore. This should set the correct time on the system. Mike Renlund Dolby Laboratories  |  IP: Logged Steve Guttag We forgot the crackers Gromit!!! Posts: 12814 From: Annapolis, MD Registered: Dec 1999 posted 03-04-2015 06:41 AM                     Please note...the BIOS time is UTC time so you should NEVER need to adjust hours unless it is way off time (hours off). Note too, the DSS100 can go up to Dolby 4.7.3.3 which has a vastly improved NTP results (not that NTP has been improved but how the DSS100 uses it). As such, if you set up the DSS100 to use an NTP time server on system 4.7.x.x, you'll find drift never happens. Another thing to do is it also make sure that the "secure time" is also set to proper time (projector must be on to set it).  |  IP: Logged Michel Pomerleau Film Handler Posts: 3 From: Magog, Quebec, Canada Registered: Aug 2012 posted 03-04-2015 08:32 AM                     The DSP100 have the right time but the Showmanager have the wrong time. But the show start with the Showmanager time.  |  IP: Logged Steve Guttag We forgot the crackers Gromit!!! Posts: 12814 From: Annapolis, MD Registered: Dec 1999 posted 03-04-2015 03:19 PM                     Right...so just set the BIOS time and you'll be all set. Again, if you get an NTP source on it...it won't drift either. If the DSP100 time is right...rebooting the server without an NTP source should set the DSS100 since it will get its time from the DSP100 if the NTP server is not present.  |  IP: Logged Michel Pomerleau Film Handler Posts: 3 From: Magog, Quebec, Canada Registered: Aug 2012 posted 03-04-2015 07:15 PM                     The time on the Bios was ok for the min but the Hour was Universal time. so I've only save it as is, reboot and now it's perfect now same time on both DSP100 and ShowManager. Thanks  |  IP: Logged Marco Giustini Film God Posts: 2713 From: Reading, UK Registered: Nov 2007 posted 03-05-2015 02:28 PM                     Steve/Mike, I thought the secure clock of the media block had priority on the BIOS clock? If no NTP is found the system clock is then initialised using the DSP100's clock and the BIOS one is basically ignored - just used to set up the system clock when the system boots up.  |  IP: Logged Mike Renlund Film Handler Posts: 71 From: San Francisco Registered: Feb 2008 posted 03-05-2015 08:39 PM                     Marco, If the ShowStore clock has drifted outside the range that NTP allows (trying to get time from the Media Block or other NTP source), then the ShowStore clock will stop syncing to the NTP source. That sounds like what has happened here. By making the manual adjustment to the motherboard time, the overall system will stay on time. Mike Renlund Dolby Laboratories  |  IP: Logged Marco Giustini Film God Posts: 2713 From: Reading, UK Registered: Nov 2007 posted 03-06-2015 01:26 AM                     Hello Mike If not mistaken the script executes a 'ntpdate' at startup which syncs the system time no matter what. Then ntpd is started (and that cannot adjust over a much more limited range indeed). ntpdate has a max range as well but 5 minutes are definitely OK. I thought in these cases the only solution was to set up an NTP server? Thanks  |  IP: Logged Mike Renlund Film Handler Posts: 71 From: San Francisco Registered: Feb 2008 posted 03-06-2015 10:31 AM                     The time syncing definitely improved over time but there were periods where it did not work well (not sure which version Michel is using). 4.7.3 is the furthest you can go with a 100 series system and has good time syncing. The other Dolby servers (DSS200/220) and Show Libraries can take system 4.8. We made some major changes there and the time syncing is improved quite a bit.  |  IP: Logged Steve Guttag We forgot the crackers Gromit!!! Posts: 12814 From: Annapolis, MD Registered: Dec 1999 posted 03-06-2015 11:47 AM                     I'd agree...the biggest improvement happened in 4.7.x.x. There were still a few specific servers that seemed to have a hard time (I'm guessing their internal clocks were less accurate to begin with)...4.8.2.x seemed to take care of them. The DSS100 series seemed to start with more accurate clocks to begin with. Now the CAT745...that is another story. Its "clock" sucks and doesn't sync via NTP. Note, the problem with it is seemingly when it is on battery power.  |  IP: Logged Vegard Olsen Film Handler Posts: 8 From: Bergen, Hordaland, Norway Registered: Feb 2014 posted 03-09-2015 03:39 PM                    It's beyond me that a solved problem like time can be so hard to get right. In this regard Doremi has been miles better than Dolby. System clock == secure clock. 6 min drift per year as per DCI, extended to 30 min with license. NTP works.  |  IP: Logged Steve Guttag We forgot the crackers Gromit!!! Posts: 12814 From: Annapolis, MD Registered: Dec 1999 posted 03-09-2015 04:25 PM                     GDC tried to do the system/secure clock being one and the same...didn't pass DCI muster. I don't have a problem with there being two different clocks at all. The secure clock really only makes a difference to keys...hence the restriction on how far one can set it. The show clock should really be precise to local time. Why they both can't use NTP to keep dead on is beyond me and why something that is "figured out" like NTP and time had to be such a struggle.  |  IP: Logged Marco Giustini Film God Posts: 2713 From: Reading, UK Registered: Nov 2007 posted 03-09-2015 04:33 PM                     It's the way NTP has been designed. It's a protocol designed to keep your clock synced down to the MILLISECOND (I believe it is a requirement for some database). To achieve that it is very fussy in terms of several aspects of its setup and its sources. That is one of the reasons why 'ntpdate' is used to sync the system at startup: ntpd would not allow that - or it would be much slower and limited in range; ntpdate just steps the clock no matter what. ntpd just does not work like that.  |  IP: Logged

All times are Central (GMT -6:00)

This topic comprises 2 pages: 1  2

Printer-friendly view of this topic

Hop To: Select a Forum: Category: Operations -------------------- Digital Cinema Forum Film Handlers' Forum Large Format Forum Ground Level Feature Info, Trailer Attachments & REAL Credit Offsets Category: Community -------------------- Film-Yak Film Handlers' Movie Reviews The Afterlife Bob Maar's Joke-A-Thon Category: Classified -------------------- Equipment and Supplies Wanted/For Sale Help Wanted/Seeking Employment Category: System -------------------- Software Beta Testing Forum

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.