Search the Community
Showing results for tags 'TCP commands'.
Hello, I'm in the middle of building an installation that consists of three independent display servers being controlled by an ipad based control system by Kramer. At it's simplest, we are using the ipad to Play, Stop, and Pause Aux timelines with the UI showing the states of the Aux timelines. And ideally a counter showing the time. While wading thru the forum I found this statement: "One shot polls are interrupt based and if sent too often can impact system performance." When observing the packet stream between the program Universe and WO production, it appears that a getStatus query using "2" for the subscription function is sent about every 30 ms. If we do something similar with the Kramer Control system for three display servers and multiple Aux timelines, is there any way to determine what kind of impact that might have? Also, a syntax question: Elsewhere in the forum I came across this specific syntax for a getStatus query: getStatus 1 "TaskList:mItemList:mItems:TimelineTask \"Movie1\"" The users' guide Control Protocol section defines only the basic getStatus command and the expected reply, but not in the detail noted above. Is there a document in existence that shows that level of detail for each command? Or do I need to use a program like Universe to reverse-engineer something similar for Kramer Control? thank you for your help -patrick
I am working with WO 5 and trying to send TCP commands to 2 Christie DHD800 projectors, but getting no response from the projectors. Sending Command: C0D$0D & C0E$0D on Port 3002 I also tried sending: Commands: SHUT1$0D & SHUT0$0D SHU0$0D & SHU1$0D Port 3001 and 10000 When I use telnet I have no problems sending the command C0D and C0E, (shutter mute and un-mute) Any thoughts on why the projectors are not seeing the TCP command when sending through WO? The network manual mentioned that the connection will be closed after 30 seconds. Do I need to send a command to open the port first and then send the shutter command? Thanks!
Hi, We recently had a show that we updated from watchout 4.3 to 5.1 to use the multiple outputs per display computer and we ran into a couple issues. We had 1 production and 2 display each driving 3 outputs. Watchout machine specs CPU-Core i5 750 @2.66 Ram-4GB GFX-AMD Radeon HD 6970 2GB GDDR5 Mem Win 7 32bit HDD-Solid State drives Rack Mount cases First and main issue was: every time we would change the output # on a display computer it would re-send all of file into the computer even though there files were already there. This certainly caused some slow down in the production. We had to change output # for troubleshooting purposes. But this would also be done if we would need to switch to a back up display computer in which case it would be a problem. 2nd: The auto-detect of the alpha type for stills wasn't detecting properly. This use to work just fine in watchout 4 but in 5.1 I had to go specify the type of alpha for each media. That only seemed to happen on stills. 2nd and 1/2: Hard to say exactly what happened here but 1 night we made some very specific masks and put them into the show. All was well then but the next day when we turned on everything the masks were not the same anymore. (I do not have all the details because we had left by then) I asked the watchout technician onsite to try to play with the alpha modes, I also re-sent him the files because maybe they had been corrupted but in the end he had to re make the masks from scratch. Very strange. Any thoughts on that? 3rd: The production computer is getting TCP command from a medialon machine in this installation and at one point i turned off the triggering so I can work without being triggered but I was still receiving the commands. What do you think? Thank you.