Jump to content
Dataton Forum


  • Content count

  • Joined

  • Last visited

Everything posted by jfk

  1. Well some images can take longer to load. A few optimizations worth trying. In the Media list, open the media dialog for the jpegs in question and set Transparency to None and confirm Optimize for better performance. If none of that helps, try offsetting the image cues from the pause cue about 0.05 to 0.1 second. A lot of activity occurs when transitioning from 'run to pause' and from 'pause to run', allowing a little time for that to complete before the media change can sometimes clean that up.
  2. OK. when you are finished editing, and simply playing back a show, I would recommend you turn Live Update Off. So are you sitting on a Control Pause, then tapping the space bar to run a cue? That results in the images not appearing as programmed? File type and resolution of the files in question? Would like to look at the timeline programming to see if there are any simple corrections that may clear that up.
  3. Are you referring to the transfer of new media assets while Online with Live Update active? That is NOT intended to provide seamless live show function, live update simply relieves you of the task of hitting Stage-Update after you make changes, it is still an update. Automatic update would be a more accurate description. Update transfers disrupt normal show playback. With live update off, you control when that disruption occurs (and that is the only way WATCHOUT worked for its first 15 years) . All content must be present on the display server before you can expect a cue to run properly with that media.
  4. Could you please clarify what you mean by "when we push an image to the wall" ?
  5. Running 2x miid controllers

    No, they would need to be at 3% or above for that to work. but you might try this instead ...
  6. Yes, version 6.2+ has a full audio matrix switch for each audio file. Up to 24 channels per display computer are available. The audio should be on the same aux timeline with each video. Definitely the display computers. Does not have to be just one (although it can be if you choose), you can use any or all of them. Each audio file (cue) can be independently assigned to a display computer. As for the production computer, your best plan would be to execute the playback without the production computer in the system.
  7. Hourglass

    This commonly occurs when WATCHOUT loads from a startup shortcut before Windows is finished loading. Add or increase the startup delay to avoid this. Reference: WATCHOUT 6.1 User Guide, Appendix D, COMMAND LINE OPTIONS, page 171-172
  8. sync and refresh problem watchpax 2

    I am not sure I understand what you are describing. Are you saying that when you play the timeline in Production while online, one of the WATCHPAX 2 are not playing as it should and the other one is playing? Or are you saying when an external control system tells the WATCHPAX 2 master to play, master plays and client does not?
  9. Dataton Screen and White Bar

    The most common cause is WATCHOUT Display loading before Windows has completed startup. Are you using the -Delay command line option in your startup shortcut? If so, increase the delay.
  10. Importing 3Ds files

    Yes. Live Update applies to the transfer of content and instructions to the WATCHOUT Display servers and is therefore only relevant when online. A WATCHOUT License (USB "key") is required for WATCHOUT Production to perform Online, Output, and/or Export functions.
  11. Importing 3Ds files

    No, you do not have to install 3Ds max/studio on your production system. The message indicates there is a problem with the file. Any 3D file must also contain UV mesh coordinates or it can not be used by WATCHOUT.
  12. Watchpax 2 not discovered

    A DHCP server is not required. Any Windows device set to DHCP (including a new WATCHPAX' default setup) on a network with no DHCP server will self assign an address in the 169.254.x.x range with a subnet mask. With a new WATCHPAX, you will need to set your Production machine NIC to DHCP as well, so the two can communicate.
  13. Watchpax 2 not discovered

    You must have a valid display connected before powering the WATCHPAX 2 on. Also, connect your network before powering on to avoid any confusion. Once it is powered on, confirm you see an amber or green network presence LED illuminated (above the network port to the left of the connector). The network presence LED color indicates network speed. (A yellow LED may also flash on the top right to indicate network activity). Next, what is the IP address and WATCHOUT name shown in the startup logo screen? In the above example photo, the WATCHPAX 2 is running Version 6.2.2, the #3362 is the Dataton Type Number indicating it is a WATCHPAX 2, the 10524 is its serial number, wp2_jfk2.Main is its WATCHOUT_name.cluster_name, is its self assigned IP address and the number 2 indicates it is output 2 (if only one display is connected, the output number will not appear).
  14. Well, I suspect simply stuffing the card in a computer and installing a driver does not magically make the NDI signal appear over the network. Wondering what software they provide to make that happen.
  15. No experience with it. Strictly from a spec standpoint, it does indicate Windows DirectShow compatible. Without WATCHOUT testing, that only means it is worth a try. I am a bit curious about another product claim:
  16. New Watchout Display System

    So far, the best I have seen is a DataPath capture card in WATCHOUT 6.
  17. New Watchout Display System

    Image Magnification. Typically a camera pointed at a podium to magnify the image of the presenter so that all in the room can clearly see him. Since the live presenter and his magnified image are both visible to the viewer, delay / latency is quite noticeable.
  18. Project challenge

    Not sure I understand the question. When you say "scale the image" do you mean pre-scale it to compensate for magnification differences before bringing it to WATCHOUT? No need. You are free to scale the images you wish to place across multiple displays, of course. If set up correctly, you do not need to scale them for each display, that is done globally by the proper stage setup. My response is valid for versions 4 & 5 & 6. I agree with zachboyd, with v6, doing this with virtual displays adds some flexibility. The math is the basically same either way. As for which displays you run native resolution and which displays you run scaled, - it is a personal choice Just keep in mind the impact on hardware demand. i.e.WATCHOUT can do it either way - you can run the largest displays native and scale up for the smaller displays (lowest hardware demand), or you can run the smallest displays native and scale down for the larger displays (much higher hardware demand).
  19. Project challenge

    Very doable. You will need to perform the math to scale them in the WATCHOUT stage so that a single image placed across all of them comes out the same size on each display. You will need to know the resolution of each display and the exact width/height of each one in order to perform the math. (Yes, you know the diagonals, but it is not uncommon to encounter two displays with the same diagonal that are slightly different when the actual measurements are compared. It would also be useful to know if any of the displays are overshooting (not displaying some of the pixels), as this is common with consumer grade panels (or at least it was). You will also need to know the exact distances between the visible area of each display (bezel sizes will vary - measure to the visible area). With all that information in hand, you can accurately lay out the WATCHOUT stage to accomplish your task. No Yes, you rotate them in WATCHOUT (do not rotate them in graphics card settings) Sort of, with the caveats above - yes. To scale for the different sizes, in the display dialog, you uncheck the Width and Height same as Display Resolution setting, and with the proper math, you will compensate for those differences by adjusting the stage resolution.
  20. Network Error with Watchout

    Have also seen this occur with some older network switches when the NIC settings are incorrect for the switch. When Win7 came out, Microsoft changed the default NIC settings to hand off more processing to the switch. Some older design switches are unable to handle the extra processing, and the result is no or extremely slow network transfers. That is cured by reconfiguring the NIC to perform the task the switch was not doing.
  21. Bad image with magewell dual hdmi

    WATCHOUT version? Have seen what you describe when the display computer with the capture card is powered up with the capture signal not present. the capture card can default to 640x480 with no signal, then when you add the signal, whatever it gets it scales down to 640x480 then back up to the res specified in WATCHOUT, significantly degrading the signal.
  22. WIBUCM32.dll is missing?

    The latest key driver is packaged with the WATCHOUT installer. What you experienced is an incomplete installation. I suspect when the WATCHOUT installer says it is finished, it is not quite there yet. i.e. the WATCHOUT application install was complete, but some of the supporting installs were still running in the background. If you open WATCHOUT immediately after the install, it aborts those background tasks, leaving incomplete support for codementer or sometimes some of the codecs are affected. Relaunch the WATCHOUT installer and choose Repair (Repair will only appear if WATCHOUT is already installed). When the repair completes, wait a few minutes before starting WATCHOUT.
  23. As you may notice, this forum underwent an upgrade today. In the past, the sign-in process required you to enter your registered name (not your forum display name) and password. This has now changed, and you now must log-in with your forum display name and password. This rendered my browsers saved log-in information inoperative. Easy enough to correct once you understand that. I decided to place this post when I checked how many people were viewing the forum, and saw 11 guests and 0 logged in users. So I suspect the new log-in may have caught more than a few people unaware. Since guests can see this post, hope this helps
  24. Saw this in the Facebook Forum before seeing it here. Use a generic input in a live tween For example create a WATCHOUT generic input Volume and use its default range ( 1 ). Hook your WATCHNET slider to the generic input. Then the formula is simply Volume Set a startup / default value from WATCHNET using the WATCHNET script command Set Input
  25. Direct URL Images in 6.2

    Just curious, what happens if you open a show made in an older version that already contains cues with URL links?