Jump to content

Mike Fahl

Member
  • Posts

    721
  • Joined

  • Last visited

Everything posted by Mike Fahl

  1. Yes, it can be replaced. Please contact support@dataton.com, or your local Dataton partner. Mike
  2. In the computer that exhibits this behavior, and restarting WATCHOUT doesn't help. Mike
  3. If a restart of WATCHOUT doesn't solve the problem, and the only thing that helps is a reboot of the computer, it's definitely a driver bug. Try another graphics card (if this is a desktop class computer), or at least another driver version. Mike
  4. This is not a problem I've encountered. Are you saying you have this with H.264 as well as HAP codecs? How long does it take for this problem to occur? How many times does the video play during that time? Are you saying that restarting WATCHOUT doesn't correct it; you have to reboot the entire computer to fix it? Mike
  5. Does you computer have a MIDI port? It seems something in the show you're loading tries to communicate with MIDI, but there's no MIDI port. Mike
  6. Another option, that sometimes works really well, is to use a green or blue matte where you want the video to be transparent, then use the color keyer in WATCHOUT to knock out that background. This allows you to use more efficient codecs than Animation, such as MPEG-2 or H.264. Mike
  7. To answer your other question about RAM. I'd say put 8 GB in a 64 bit machine if you intend to use it mainly as a WATCHOUT player. This gives WATCHOUT 4 GB with 4GB left for the OS and other duties. More wouldn't really be of any significant advantage, except possibly for use as a large RAM disk. Mike
  8. I guess noone knows really. It sounds a bit excessive to me, and it's definitely beyond what we had in mind when we designed that featre. Mike
  9. Yes, the pulsating effect is sometimes an issue with ffmpeg. You can try a sm,aller GOP (with a corresponding increase in bitrate). No, a GOP of 1 is an all-I-frames. Generally, that's not required in WATCHOUT. If you're on WO6, there are more options for video playback, such as HAP and Prores. HAP should have no trouble with that resolution, and is very easy on the CPU (albeit heavy on data rate). They should be identical, given the same versions. Mike
  10. This indicates something's wrong with the graphics card driver. I've been using WATCHOUT on Win10 for quite some time, and it works fine. There are still some rough edges around some drivers, though. Particularly on laptops. Mike
  11. FYI, that has been fixed for the next version of WATCHOUT. Mike
  12. Mike Fahl

    h.265 ?

    No. Besides its lower data rate (which usually isn't of much use for WATCHOUT), I see no particular advantage of using it with WATCHOUT. It's a significantly heavier codec than H264, and hardware accelleration is so far pretty much non-existent. Mike
  13. That's fixed by my comment above. Here it is again: It appears to be caused by some new behavior introduced in Windows 10. To avoid this problem, go to Start-button, Settings, Devices, Mouse & touchpad and turn off “Scroll inactive windows when I hover over them”. The scroll wheel should now work as before in Watchout. Mike
  14. Ok, that's WATCHOUT crashing. Likely when analyzing some video, which happens during the downloading of assets. The fact that your "Show Sage backup system" doesn't crash indicates there's a difference somewhere. My guess is there are some rouge codecs installed on your misbehaving machine. Those can sometimes cause problems. Take a look at the "tweak list" on this forum for instructions on how to properly configure your PC. Mike
  15. This can either be a network related problem, or it can be the display computer crashing for some reason. What happens on the display computer when you get tis message? Does it briefly show logo screen or windows desktop? Mike
  16. On some computers, depending on their graphics subsystem, resizing the Stage window is an "expensive" operation. The same may apply to the preview tabs in the display dialogs in WATCHOUT 6. My advise is to not resize these windows while running time critical functions. Mike
  17. The first message you mention; "Display Setting Not Available", indicates that you have your display settings in your show set to a resolution not supported by the display computer or the display attached to it. Make sure that the correct resolution set in the display's dialog box (doubleclick the display in the Stage window to open its settings). I believe the subsequent error messages you mention are caused by this first error. If you continue having trouble, I suspect the EDID from the Encore. Try connecing a regular 1920x1080 display to the display computer instead, to see if that works. Hope this helps. Mike
  18. Yes, using multiple projectors is not a problem. The UV applies to the 3D model loaded into WATCHOUT, not to each individual projector. Then the 3D projectors just "look" at the object from various angles, corresponding to where the real projectors are located. Mike
  19. Can you load all the different videos onto WATCHOUT, and run them as separate timelines? If so, you can trigger the desired timeline from an external system over TCP/IP, talking to the display cluster directly. Mike
  20. For testing purposes, you can use a TELNET client form a terminal window. Built into MacOS X as standard, and inWindows it can be enabled in Programs and Features. You can also use the "putty" freware program for Windows. If you run it on same computer as production software, you can connect to "localhost" or "127.0.0.1", using port 3040. Don't forget to enable the TCP port in Preferences for the loaded show. Mike
  21. If possible, forward the file to support for further investigation. Contact them at support@dataton.com for details. Mike
  22. I suggest you read the section titled "Controlling Tween Tracks" in the "Inputs and Outputs" chapter of the WATCHOUT manual first, as it explains the procedure. Mike
  23. When running the system from the production computer, then plug the timecode into the production computer. You can enable/disable timecode in Preferences, or by simply disconnecting the timecode. If you want to run the cluster without the production computer (form some other external control system), you need to connect the timecode to the primary cluster computer. Mike
  24. Note that WATCHOUT 6 allows you to explicitly specify the display computer through which audio is to be played, rather than by placing he icon inside its rectangle. Either method can be used, and is specified inside the audio cue. Mike
  25. Note that the setIP command has been enhanced in WATCHOUT 6, allowing you to set the gateway and DNS as well, if desired. Should be documented in the example script file included on WATCHPAX. Mike
×
×
  • Create New...