Film-Tech Forum ARCHIVE: TMS GDC Dss200

This is topic TMS GDC Dss200 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=003012

Posted by Adam Batista (Member # 8972) on 04-24-2017, 05:07 PM:

Hi guys, I need your help.
I have TMS Vr. 4.1.8100 GDC.
1 DSS200 Vr 4.5.3 (13)
Does not enable Player in TMS - DGC with IP control xx.xx.x.129
Can you help me?

Thank you.

Posted by Leslie Hartmier (Member # 7053) on 05-04-2017, 04:51 PM:

Just as a question, are you connected to the media network or the management network?

One will control the servers, and the other will not to my recollection.

Leslie

Posted by Ioannis Syrogiannis (Member # 3235) on 05-05-2017, 03:33 AM:

As far as I can see, since the IP is for some reason partly masked(?), the IP that Adam or the configurator used is the management (Auditorium/control) one (192.168.x.129).
I am not familiar with the GDC products. Yet, being familiar with the DSS series of dolby servers, I would say that there is no reason for a TMS or LMS to be connected to the Auditorium network, since the Theatre network (192.168.241.x+2) is for transferring data (content) and connecting TMS and the Jupiter client from a PC.

(Auditorium network may support a VNC connection with the latest software including 4.5.3.13, but not much more in terms of using APIs to control and to move data.)

It looks like that the connection is configured (physically, in settings or both) to the wrong adapter.

You 'll have to also consider the possibility, though, that even after configuring the network in a proper way, the TMS won't be able to do much more than FTP the files in and out of the DSS library. The software version of the DSS200 is quite old, and the APIs that Dolby uses change considerably, if you take into consideration that not every Jupiter client is working with every software version.
So, I would check the Dolby DSS software versions that the particular TMS software version would cover and support.

Also, I would recommend a software upgrade to the DSS server, since a lot of improvements have been made and a lot of bugs has been "squeezed" during the last years. If not for anything else, for the sake of less subtitle issues during the shows.

Posted by Stephan Shelley (Member # 8587) on 05-05-2017, 08:26 PM:

GDC and Doremi have separate management and media networks.The do not send control over the media (theatre) network like Dolby does. In advance settings on the DSS 200 you can change the management to the auditorium network and then will work with 3rd part TMSs.

Posted by Danial Simmonds (Member # 4638) on 05-11-2017, 01:59 AM:

I believe in the TMS when you register the screen both management and media networks will point to the Theatre IP of the DSS for dolby server's. Well as i know when i setup Doremi TMS with Dolby last time it was like that.

Posted by Ioannis Syrogiannis (Member # 3235) on 06-28-2017, 02:08 AM:

quote: Stephan Shelley
GDC and Doremi have separate management and media networks.The do not send control over the media (theatre) network like Dolby does.

GDC I don't know. The Doremi servers have two ethernet controllers. Yet, if you 'll (rightly so) differentiate control and data usage or not, is up to you. No restrictions from the system to use both for both. Not that it would be wise of one to do so.

As for changing the control network on DSS200, most third party TMSs use auditorium network for control. I was not negative about it in my post. (If you have done so, have you ever had luck on using the jupiter client with the auditorium network?) Yet, we were presented with just one IP from the TMS configuration scheme and that was seemingly the auditorium one, unchanged, according to the dolby (DSS) IP convention. I guess that, if only one IP is to be configured, that would be the theatre network one and would probably need to be changed, according to the TMS's convention.

P.S.
No response from the original poster. I guess that he either had the issue solved or found a workaround. Petty that all those threads remain with a question mark above the title.

Posted by Mark Gulbrandsen (Member # 72) on 06-28-2017, 11:29 AM:

On GDC is depends on which model you refer to. The full size GDC servers do use two ethernet, one for management and one for media. The media is gigabyte but management is not. On the SX-3000 everything goes through a single gigabyte ethernet with options left for doing different configurations and such with the second SX-3000 ethernet. But using that second ethernet is totally unnecessary. Also makes installation half the work running a single cable back to the TMS.

Mark

Posted by Leo Enticknap (Member # 534) on 06-28-2017, 11:56 AM:

quote: Ioannis Syrogiannis
(If you have done so, have you ever had luck on using the jupiter client with the auditorium network?)

Yes, and with no problem. I used to run three houses with DSS200s, all of which had the Jupiter client running on PCs on the auditorium (management; 192.168.X.129 in the Dolby scheme) network. The only limitation is that unless the theatre (media) network is in use and separate auditorium numbers for each DSS200 are defined in the config wizard, multiple DSS200s on an auditorium network only will not be able to see each other, so you won't be able to transfer DCPs between individual DSS200s using Show Manager.

But I had no problem using the Show Manager Jupiter/Java app communicating with a single DSS200 through the auditorium network.