Jump to content

Mike Fahl

Member
  • Posts

    721
  • Joined

  • Last visited

Everything posted by Mike Fahl

  1. All should work just fine. Running a MacBook Pro under Bootcamp essentially turns it into a fancy PC laptop. There's another older posting of mine that describes how you can keep both 5 andf 6 installed on the same computer. ( WO6 and WO5 on the same computer )
  2. No. But it has come up before, so I believe it's on the wish list.
  3. Some of the new videos touch upon this. For texture baking, take a look at the "3D Lighting" video here: http://forum.dataton.com/topic/1861-new-tutorial-videos/ (I didn't want to use the term "baking" in the title, since that doesn't really mean anything to you unless you already know what it is, in which case you probably don't need to watch the video anyway).
  4. It may help if you set the aux timeline to PAUSE some time before it's to be started. This allows it to get everytning prepared, and avoids the "tightness" of your current .45 second preroll. If you get no "advance warning", just leave them in PAUSE sitting at time zero until they need to be started. This can be set up in WATCHOUT itself (by making the aux timeline jump back to zero and PAUSE rather then STOP when it reaches its end), so no need to change extrenal programming. Alternatively, you make your external system set them into PAUSE mode right of the bat, as the system starts up and connects to WATCHOUT. Hope this helps.
  5. That spounds like a buggy implementation in the other end. They way WATCHOUT works here is: 1. If the connection is not established, initiate the connection. 2. Wait for the connection to succeed, getting a positive confirmation to that effect. 3. Send the command. If the connection is already open, WATCHOUT goes straight to 3 and sends the command through the already open connection. If you need to repeat the command, it sounds like the device in the other end ignores the initial command. You may want to snoop the line to see if the first command returns an error or something like that (WATCHOUT won't deal with any data coming back, so you can't really tell from within WATCHOUT. Hope this helps.
  6. As far as I understand, you're using TCP to send commands. That should guarantee that no commands are "missed", which can happen in the case of UDP (which is why it's sometimes referred to as "unreliable"). The message you're seeing "Failed delivering data" indicates a failure to connect to the device. Sending over TCP entails connecting, sending the data, and eventually disconnecting. WATCHOUT will disconnect automatically after about a minute of inactivity (assuming memory serves me correctly here). If it has disconnected, it will re-connect again if a new command is subsequently given. So it seems sometimes the device doesn't handle the connection attempt properly.
  7. Very cool! And very specialized, with various teams and players all set up and ready to go, it seems. Thanks for sharing.
  8. No, using an MST hub till not allow you to go beyond the maximum of 6 displays per computer. Besides, many MST hubs introduce their own challenges, often complicating the matter of getting several displays to "behave" reliably when connected to one computer.
  9. Just a quick heads-up to let you know that a couple of new tutorials are up on the academy site: http://academy.dataton.com/cookbook If you've already seen the older stuff there, and want to jump straight to the new videos, here are some direct links: Getting Started Using a Display Computer Editing Media Files Using Live Update 3D Models and Mapping 3D Creation 3D Lighting UV Mapping Basics More about UV Mapping Multiple Texturable Areas Optimizing 3D for Animation Texturing Inside or Outside of a model Interactive Control Remote Control from iOS/Android Advanced Topics Inside the WATCHOUT Folder Remote Management
  10. Yes, matkeane is correct, there's no easing formula supported. Just linear interpolation. The syntax for the basic setInptu command is unchanged (but has improved performance in version 6), while a new setInputs (note trailing "s") improves bandwidth and synchronicity even more by allowing you to set multiple inputs with a single command. Full details will be in the version 6 user's guide, to be release any day now.
  11. OK, so you have one computer where this works with the Dynamic Image Server, and others where it doesn't. Interesting.
  12. Plase forward some example URLs having this problem to support@dataton.com and have them take a look at it.
  13. WATCHOUT can use up to six outputs per computer. They must all come from the same graphics card, and be set to the same resolution.
  14. Again, I this should work better in v6, since the display software bis better at handling larger amounts of input commands. Mike – http://fahl.se/
  15. I guess you're using Windows 10. This behavior is an incompatibility betwene WATCHOUT and a new feature in Windows 10 that scrolls what's under the mouse instead of the window that has focus. Disable this feature in Windows 10, and things should go back to normal again. More details found a bit down in this thread: http://forum.dataton.com/topic/1773-windows-10-watchout-6/ Mike – http://fahl.se/
  16. I'll be making some new training videos over the next few weeks, that will – among other things – show how this can be done in C4D. Stay tuned! Mike – http://fahl.se/
  17. Creative Conners specialize in tracking and scenery automation systems. They interface directly with WATCHOUT. See for example this detailed tutorial: http://creativeconners.com/spikemark-and-watchout-step-by-step Mike – http://fahl.se/
  18. Yes, it will continue to work without the production computer. And you don't "connect your dmxethergate mk2 to your player", it stays connected to the network, so no need to move any cables. Mike – http://fahl.se/
  19. It sholdn't have to reload files that haven't changed since last time that same show was updated. Does it? Mike - http://fahl.se/
  20. Possibly. But keep in mind that MIDI controllers are limited to 14 bit resolution at best. Mike - http://fahl.se/
  21. You should be able to run the WATCHOUT remote (free download) from a desktop computer as well, although it may look a bit out of place. http://www.dataton.com/files/watchout/remote/ More details in this PDF: http://www.dataton.com/assets/WATCHOUT-remote_app_info.pdf Alternatively, WATCHNET can do this as well. Hope this helps. Mike – http://fahl.se/
  22. Just a quick note on the original subject of this posting. In WATCHOUT 6, the control protocols of the production and display computers have been largely unified, removing as many of the differences as possible. This should make it easier to choose either method, as well as starting with one method (e.g., the production computer, since it makes it easier to see what's happening), and then switching to the other method for final deployment. The WATCHOUT 6 User's Guide should be out soon with full details. Mike – http://fahl.se/
  23. This issue has been alleviated in WATCHOUT 6. There are two improvements here: 1. More commands are processed per frame, greatly increasing the number of setInput commands that can be handled. 2. A new setInputs command was added, which takes multiple name-input-slope triplets in one command, increasing the maximum number of inputs that can be managed significantly. This command will be documented in the upcoming WO6 User's Guide. So if you're using v6, you should not have any problem here. If you're at v5, the maximum rate is more constrained, as you say. Mike - http://fahl.se/
  24. I assume you need to enter the password into each the command string as well. Or do you fire that as a separate cue? If you fire it as a separate cue, you can't wait too long between those cues, since WATCHOUT will close the TCP port after about a minute of inactivity, and then re-open it for subsequent commands, which may then require the password again. I'm not familiar with the projector's protool, so I don't know if you can put the password command line at the beginning of each command just to be sure. Also, are you sure the projector uses a single carriage return as the line terminator (that's $0D)? Some devices may use LF ($0A) or both CR and LF. Finally, make sure you type "zero" "dee" for $0D, and not "ooo" "dee". Hope this helps. Mike - http://fahl.se/
  25. First, you need a timecode source. I assume you have something here already, or you wouldn't be asking the question. If not, there are a couple of free iOS apps that can generate timecode. Connect the timecode feed to the audio input jack of the production pc (in your case), or the display PC in case you don't need the production PC in the system. On the produciton PC, use the Timecode Tester app to verify proper timecode reception (see page 85 in the WO5 manual). Quit the timecode tester app, and start the production software. Load you show and enable timecode control in Preferences (see page 122). Start your timecode source, and it will drive your main timeline. In case you want to drive the display PC, see page 268 for the appropriate command. Hope that helps. I also intend making a video that walks through the procedure within the next few weeks. Mike http://fahl.se/
×
×
  • Create New...