Announcement

Collapse
No announcement yet.

Setting up Fader Cues with Doremi DCP 2000 and DTS XD10p Audio Processor

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Setting up Fader Cues with Doremi DCP 2000 and DTS XD10p Audio Processor

    Hi All! I need some help figuring out audio cues for our system. We currently use GDC as our TMS, Christie 2000s Projectors with Doremi DCP 2000 Servers and DTS XD10p Audio Processor. The DTS XD10p is apparently not a compatible unit for the GDC TMS system. I am trying to get audio fader cues to integrate into our playlists because currently we are having to manually adjust setting for Previews and then for Feature levels. I have reached out to Doremi regarding this and they are saying I most likely need to use GPO's to accomplish this. Is there anyone who can point me in the right direction (or help with instructions) on how to get these cues working on our system? I am fairly new to all of the back end tech side of this, so I am having trouble figuring it out.

    Kevin Kelley
    Moviemedic

  • #2
    I'm not at work to check mine, but does the DCP2000 device libraries include the X10p in it's audio processor list? It would have to be RS-232 methods I think as there is no network on the x10p.

    We don't use a TMS in my booth, so others will have to chime in. Seems like a glue device like a JNIOR might be warranted here to translate TMS network commands into RS-232 or GPIO signals. Or at least it might be the path of least resistance.

    Comment


    • #3
      The GPIO approach would probably look something like setting up DOREMI's GPO to send pulses to the two-wire remote-fader connection (or the two pins in the automation jack). But I think it can only increment and decrement in 0.1 steps per "press". But might be all you need.

      Comment


      • #4
        Doremi had me being to set up the DTS XD10p as a new Macro Device under the RAW setting, but because our DTS isnt connected to a network, we dont have the IP and port info to complete that. Thats when they suggested the GPO. I know we do use the jNior device for regular cues. Other than that i am kind of clueless on how to get this working.

        Comment


        • #5
          Originally posted by Kevin Kelley View Post
          Doremi had me being to set up the DTS XD10p as a new Macro Device under the RAW setting, but because our DTS isnt connected to a network, we dont have the IP and port info to complete that. Thats when they suggested the GPO. I know we do use the jNior device for regular cues. Other than that i am kind of clueless on how to get this working.
          That's cause there is no network interface on the X10p that I can tell. Your options are decode the RS-232 commands it accepts (or find that documentation)... or continue down the RAW GPO route.

          I'll look into the GPO setup options next time I'm in the booth. It would not be too difficult, just familiarity is required.

          You also have the option for the JNIOR to send the GPO instead of Doremi, if you are more familiar with that tool.

          Comment


          • #6
            I am familiar in the aspect that I know we USE the JNIOR and it controls the cues between the projector and components. I am not familiar in the HOW it sends the cues or the way to get it to do that! LOL

            Comment


            • #7
              The XD10P as well as the JSD80 is fully controllable with a RS232 connection and the commands are I believe in the Manual and are sent as ASCI text.
              If you are using a DOREMI the serial port behaves well only when sending it in HEX as there is a issue with the carriage return

              Comment


              • #8
                I believe the XD-10P was an OEM version of the USL JSD-80. The original JSD-80 did not have Ethernet, but it was added later. If it has Ethernet, there is a daughter board on the control board (far right board) that provides the Ethernet support. As far as I remember, the RS232/Ethernet automation commands are the same for either model. The JSD-80 manual is available at http://ftp.uslinc.com/Products/JSD-8...onCommands.pdf , and the RS232 handshake information is at http://ftp.uslinc.com/Products/JSD-8...0handshake.pdf . If the unit supports Ethernet, the same commands should work on TCP port 10001.

                Good luck!

                Harold

                Comment


                • #9
                  As far as I know, the XD10P was only sold with RS232, but that's not a problem as the Doremi supports audio automation over RS232. The XD10P RS232 automation command set is very limited, but volume and format selection is available.
                  Attached Files

                  Comment


                  • #10
                    Originally posted by Carsten Kurz View Post
                    As far as I know, the XD10P was only sold with RS232, but that's not a problem as the Doremi supports audio automation over RS232. The XD10P RS232 automation command set is very limited, but volume and format selection is available.
                    That's the magic document right there. Should be doable via RS-232 from doremi or JNIOR with that guide. Some experimentation on the escaped character required to end the command might be needed from their interface. But one can prove out the commands work with just a usb to RS232 cable, I found the ones with the FTDI chipset to be the most generally compatible... plus no windows drivers required.

                    Example:
                    https://www.amazon.com/Adapter-Chips.../dp/B0759HSLP1

                    Comment


                    • #11
                      To command an RS232 device from a DCP server that does not have onboard RS232 capability, an Ethernet to RS232 adapter is probably a better way to go than trying to hack and add to the server software to get it to support a USB to RS232 device. We generally use these if only one-way communication is needed and only one device needs to communicate with the RS232 device, and this more expensive alternative if two-way communication is needed and/or more than one IP device needs to communicate with the RS232 device.

                      Comment


                      • #12
                        I have used Lantronix for RS232 to LAN conversion. Others have mentioned that Star-Tech's is reliable too.

                        Comment


                        • #13
                          Originally posted by Leo Enticknap View Post
                          To command an RS232 device from a DCP server that does not have onboard RS232 capability, an Ethernet to RS232 adapter is probably a better way to go than trying to hack and add to the server software to get it to support a USB to RS232 device. We generally use these if only one-way communication is needed and only one device needs to communicate with the RS232 device, and this more expensive alternative if two-way communication is needed and/or more than one IP device needs to communicate with the RS232 device.
                          Apologies, I wasn't suggesting the USB method as permanent... DCP2000s have RS232. The cable suggestion was just for someone perhaps new to this for testing ascii commands from a laptop to your target device before you move onto getting the DCP server or IPbased glue device to talk in an automation way. Maybe your response was general, but I read it as a reply. ;-)

                          Comment


                          • #14
                            Sorry; skim reading in haste. I also use a USB to RS232 adapter with a terminal app on my laptop to confirm manually that API commands work, polling commands give me the expected data back again, and that the correct communication protocol (Telnet, SSH, etc.) is being used.

                            Even though they introduce another point of failure into the system, an IP to/from RS232 device is the only way I know of to handle server automation from the current generation to external devices that can only communicate via RS232. IMHO, onboard RS232 should not have been dropped in the transition from rack servers to combined server/media block units that go in a projector's card cage. There are two many peripherals still in use in the field that need it.

                            Comment


                            • #15
                              I suspect that you get diminishing returns. They aren't going to want to put a DB9 on the faceplate (too much real estate) so you are left with yet another RJ45. There are VERY few devices in a cinema that are RS232 only. Buy a RS232 to Ethernet device (as we've been discussing) for those few things. Note, I'm still big on dedicated automations (Eprad eCNA being my main goto...that and Q-SYS). Ethernet is so much more pervasive and makes interconnections easier too.

                              Comment

                              Working...
                              X