Jump to content

Mike Fahl

Member
 View Profile  See their activity

  • Posts

    721

  • Joined

  • Last visited

 Content Type 

Everything posted by Mike Fahl

  1. Mike Fahl
    There's a general constraint in WATCHOUT of processing about 60 commands per second. This is regardless of command type, and not specific to the setInput command. If you exceed this limit, command processing may lag or may eventually cause processing to stall (in WATCHOUT or, more likely, in the external program feeding commands to WATCHOUT). In some cases, when you want to control numerous inputs, this may get in your way. Hence, we intend to lift this limit in an upcoming version of WATCHOUT. I have no ETA for this at this point, though, so this is just FYI, that we're aware of this limitation and intend to improve it. Mike
  2. Mike Fahl
    Yes, as Jonas says, make sure your display computers run the same vrrsion as the production computer. Mike
  3. Mike Fahl
    > When you say it 'coasts' how long does it coast for? are we talking frames or seconds? Frames. > does it jump back to the last frame it 'heard' or will it stay where it finished coasting? No, it will stay where it finished coasting. Mike
  4. Mike Fahl
    Do you have an example of a "H264 .mov that often fails on watchout"? If so, please send it to support@dataton.se so we can take a look. In general I'd say the two container formats are equivalent. While a MOV file can contain a wider variety of things than an MP4, the MP4 standard is derived from the MOV file format, so at the core, they're pretty much the same, and are internally treated in the same way in WATCHOUT. Neither touches QuickTime these days, but play using WATCHOUT's native codecs. Mike
  5. Mike Fahl
    Timecode will control the main timeline in WATCHOUT. Start the timecode and WATCHOUT positions and plays the main timeline in sync with the timecode. Stop the timecode and the timeline stops (after a brief period of "coasting" to account for timecode dropouts). You feed this into the cluster master, and any slaves will follow suit. Mike
  6. Mike Fahl
    It seems your two methods for sending commands to the projector behave differently. One difference I can think of is that the TCP connection from WATCHOUT remains open for some time after using it (dont' recall the exact time), while netcat likely drops the connection right away. You may be able to get more details on what's different by monitoring the communication using Wireshark. Mike
  7. Mike Fahl
    Send and email to support@dataton.se, asking them for FTP upload access. Mike
  8. Mike Fahl
    I've played 4k H.264 content in WATCHOUT with very good results. The aspect ratio doesn't really matter, as long as you stay withing 4096 pixels in both directions and your hardware is capable of decoding the video. I.e., 7680x1080 should work as well as 3840x2160 (same number of pixels). Mike
  9. Mike Fahl
    Videos of up to 4096 pixels in width may play without pre-splitting (assuming adequate hardware, of course). Beyond that, you must pre-split due to hardware (graphics card) limitations. Hence if you're using four outputs from a single computer, you may be able to avoid presplitting by playing a single, wide video (again, asuming adequate hardware and depending on encoding format). Pre-splitting may still offer a performance benefit, though (especiellay on computers with lots of CPU cores). Mike
  10. Mike Fahl
    The above is statement incorrect. WATCHOUT maintains sync across computers even when videos run as "free running". They're still synchronized. The term "free running" here merely means they will not pause when the enclosing timeline is paused. Mike
  11. Mike Fahl
    Jeanluc, perhaos you could elaborate a bit more on what you did wrong, as this may help other users who may find themselves in a similar situation. Mike
  12. Mike Fahl
    I believe you should render the videos horizontally as 1920 wide by 1080 tall. I.e., you'll need to rotate them out of AE or whatever you use to produce them. WATCHOUT will then rotates them according to the screen rotation. So if you already pre-rotated them to vertical orientation, WATCHOUT will then rotate them again, ending up with the wrong orientation. While this behavior may feel backwards and confusing when using a display rotated by 90 degrees, it makes more sense if the display is rotated 12 degrees or 45 degrees. Hope this helps. Mike
  13. Mike Fahl
    It will be available this spring. Initial cost will be same as WATCHOUT (it uses a single WATCHOUT license key). Mike
  14. Mike Fahl
    This example goes through pretty much what you're asking for: http://academy.dataton.com/recipe/interacting-database Inludes all code and a fully working example. Hope you find it useful. Mike .
  15. Mike Fahl
    I'm enclosing a larger version of our generic WATCHOUT alignment grid, which I know some of you have used in the past. The old one doesn't quite cut it any more given the ever increasing resolutions we deal with now. This is essentially the same as the old one, just larger. /Mike http://www.dataton.com/media/support/Alignment_Grid_8000x2000.png
  16. Mike Fahl
    Keep in mind that the delay associated with most network camera solutions will generally be measured in seconds ather than frames. Mike
  17. Mike Fahl
    Not likely. Mike
  18. Mike Fahl
    Take a look at the network control prococol in the manual, which should give you an idea on what kind of control you have over WATCHOUT. What CMS do you have in mind? Sheduling should be fairly straightforward, However, editing of shows would have to be done using the WATCHOUT production software. An external control system can excert some control over specific aspects of a running presentation, but can not really alter it in any easy way. You could, for example, trigger independent "auxiliary timelines", control "conditional layers" and use "inputs" to control tween parameters (position, scale, opacity, etc). Hope this helps. Mike
  19. Mike Fahl
    From your brief description it sounds like the UDP network traffic isn't getting through from the dynamic image server to the display cluster.
  20. Mike Fahl
    Actually, you don't need to save the show to persist the MAC addresses for wakeup. Those are stored elsewhere on the production computer (typically in the registry), so you should be able to wake up the displays even if you didn't save the show after power down. Mike
  21. Mike Fahl
    FYI, this can be done already using the -NoLogo command line option to the WATCHOUT Display software. Mike
  22. Mike Fahl
    So what happens? Do they show up at all? I.e. do you see anything rendered from the SWF, such as static items, background color, etc. Is it only the pieces that originate fmor the internret that are amiss? If so, it sounds like its a sandboxing issue. See the description of this topic in the academy docs. How do you "load it locally"? E.g., drag it into a browser? That sounds like a different issue than the one discussed here. The Twitter API has changed, requiring authentication and using a different format to access the data. You need to make "developer arrangements" with Twitter to get the proper credentials to make this work. Mike
  23. Mike Fahl
    Mist MIDI interfaces connect over USB these days, I'd say. But other options exist as well. As long as the OS sees it as a MIDI device, it should work with WATCHOUT.
  24. Mike Fahl
    What was in the MPEG4 files? H.264? I assume it would take a pretty hefty machine to play two 4k H.264. Framerate? Mike
  25. Mike Fahl
    I've done this with 4k MPEG-2 encoded using ffmpeg (the only encoder I found that was capable of encoding 4k MPEG-2). Works fine on sufficiently powerful CPU. GPU performance shouldn't matter much here. Mike
×
×
  • Create New...