Jump to content

Search the Community

Showing results for tags 'tcp'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type



Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 8 results

  1. I've had a few installations in the past few months using WatchPax40 and custom-built machines that required master volume control. In WatchOut control protocol, there doesn't exist yet any command that allow you to adjust the system master volume level. The closest you get to achieve volume adjustment is to define an input variable and attach that input to the video's or audio's volume tweening function (or through DMX). And then, you'll get to adjust the level using "setInput" command. In a show that contain dozens of video or audio files, tweening the same variable to the input can be a bit of an extra work. I've written a utility that I called Remote App for my projects — it allows amongst other things, adjustment to the system wide volume level (1 to 100%) and mute/unmute through network command in a simple to understand protocol. What the Remote App does is listen to TCP port 7000 and wait for volume commands. Example commands below: volume 60<CR> //set system volume to 60% volume ?<CR> //query system volume, the command will respond with volume=60 volume mute<CR> //mute system volume volume unmute<CR> //unmute system volume The download to the utility and guide are: https://omnigram.net/releases/RemoteApp_v2021.06.zip https://omnigram.net/releases/remote-app-guide.pdf At the moment, upon running, the utility will be in 10 mins demo mode. Happy to provide free permanent activation if anyone is interested. Here's the demo video of the utility in use. Best regards, Eddy Omnigram
  2. Hi. I'm writing a C# application that will interact with WatchOut. I will send commands and receive notifications. To do that should I open two connections, one as a client to issue commands to WatchOut and another as a server to receive notifications from WatchOut Outputs? Is there a way to get Outputs in the same connection I use to send commands - and to receive errors? Thank you for reading. ®f
  3. hi , i m facing one problem with watchout diplay cluster when i try to remote control with tcp .. i use c# to create a tcp client and connect to port 3039. it can connect but when i execute command , it return error 8.1 not authorized for the command .. any way to fix it ? previously i did use udp and it works .. but some how the udp message will combine if i send it very fast
  4. Hi, we are developing a TCP client application to control Watchout vie ethernet. We are using SocketTest to control that everything is correct. 1. Our TCP client can send only the first message. After that, Watchout doesn't send back anything. 2. SocketTest works perfectly, it sends as many message sa we want. 3. At the same time, if we turn ScoketTest to server, our TCP client sends to it as many message sa we want. We are investigating about message delimiter, it seems that Watchout uses CR in place of LF. We tried CR, LF and EOF, but we still have the same three situations. is there any more advice about TCP protocol? Thanks Paolo
  5. Using a Crestron system, I am trying to talk to a Watchout System over IP. More specific I am trying to get the status of individual timelines, (Paused, Stopped, etc…).. I received this from a support tech with Dataton. I also have a document with what a response should look like. Example 1: Your WATCHOUT show is named "TestShow" and the auxiliary timeline inside the show is named "Movie1" and you want to know the status continuously. To achieve this you send the following strings (in bold to WATCHOUT display computer by TCP/IP or UDP/IP to port 3039. Note, every line should be ended with a carriage return character (0x0D): authenticate 1 load "TestShow" (you now need to wait some time for the cluster to build up 1-5 sec) getStatus 1 "TaskList:mItemList:mItems:TimelineTask \"Movie1\"" (Now you will get a periodic update of the status of the Movie1 timeline.) (To reset the status you simply send the same string but with the "turn-off" parameter) getStatus 0 "TaskList:mItemList:mItems:TimelineTask \"Movie1\"" Example 2: Your WATCHOUT show is named "TestShow" but you have already sent one load command so the show is already loaded. The auxiliary timeline inside the show is named "My Super Show" and you want to know a "one-shot" of the status. To achieve this you send the following strings to WATCHOUT display computer. Note, every line should be ended with a carriage return character (0x0D): getStatus 2 "TaskList:mItemList:mItems:TimelineTask \"My Super Show\"" I have tried this to no avail. Additional Notes This is what I am getting back Error 6 6 "Command: getStatus; Invalid/unexpected/damaged data: getStatus 1 \"TaskList:mItemList:mItems:TimelineTask \\x22Timeline1\\x22\""\x0D\x0A I copied it directly from the email. But replaced my timeline name. getStatus 1 "TaskList:mItemList:mItems:TimelineTask \"Timeline1\""\x0D A Ping command gives me this Ready "5.5.1" "WATCHPOINT" "Windows" true\x0D\x0A Any thoughts? I copied it directly from the email. But replaced my timeline name. getStatus 1 "TaskList:mItemList:mItems:TimelineTask \"Movie1\""\x0D A Ping command gives me this Ready "5.5.1" "WATCHPOINT" "Windows" true\x0D\x0A Any thoughts? What a response should look like. Example 3: Note the quoted auxliary timeline name, which must use escaped double-quotes since it’s embedded in the property path string. getStatus 1 "TaskList:mItemList:mItems:TimelineTask \"Timeline 1"\" : Status ”TaskList:mItemList:mItems:TimelineTask \"Timeline 1\"” 2 12114 94553321 : Status ”TaskList:mItemList:mItems:TimelineTask \"Timeline 1\"” 2 17210 94558417
  6. Hello all, I have what I believe is a simple question and I am hoping someone can point me int he right direction. I am getting ready to program a show in Watchout this week, and I know that we will want to handle all the dowsing using the internal dowsers on the projectors (panasonics I believe) and send those cues through watchout. I know this is possible, I have seen many people do it, so I am just wondering if someone could walk me through the broad strokes of the process so I could have a starting place to work from. I know you need to add the projector as a output-I was using the TCP option, I do not believe serial would be an option. I have read a little about about it trying to research this answer myself and I have also found a lot about string commands, enough to know that doing this does involve writing a string command and including that in the output data. How does one determine those? Is there a link out there with common commands for theatrical use? (IE Projector on/off, shutter open/closed). Any help what-so-ever with this question would be greatly appreciated.
  7. Hi! I've been reading through the user guide and am going crazy trying to find the solution for this problem. I normally work with lights so the world of media servers is a little new to me. Basically, I have to watch out computers with two movies, one which is looping and the other has to be triggered at a particular spot in the first movie. I've been trying to use the string output with tcp but not having any luck, hopefully i've just missed something. Computer 1: Computer 2: Trigger output is, ip port number 3039, protocol TCP. Is this correct? The trigger control cue is named Countdown Start and has the data to send "run" (without "") I'd really need some help here! Thank you...
  8. 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.
  • Create New...