Jump to content

jfk

Moderator
  • Posts

    1,802
  • Joined

  • Last visited

Posts posted by jfk

  1. 43 minutes ago, Crystal Lee said:

    @jfk 4 Channels I believe. The USB hardware options require software to be downloaded correct?

    No!

    The driver for Focusrite Scarlett interfaces is already installed. The newest WATCHPAX 62 image has a Focusrite Scarlett driver gen 4, the original WATCHPAX 62 configuration includes the driver for Focusrite Scarlett driver gen 3. 

    43 minutes ago, Crystal Lee said:

    Will the WP allow this to be installed? I assumed it would not. 

    Your assumption is correct, but there is No need to install anything.

     
  2. 1 hour ago, RBeddig said:

    Have you ever seen your second display on GPU channel 2 on this machine?

    On my notebook, I have to set e.g. channel 5 to connect to a display on my HDMI port.

     

    1 hour ago, Manoj Mulam said:

    Yeah I set gpu channel 2 on seconds

    Display but it was not showing 

    Isn’t Rainer suggesting that your external output may be a different channel number than 2? Have you tried other output numbers? Seems Rainer had to go all the way up to 5 to find his second output.

  3. 18 hours ago, Brian said:

    … QuickTime reports the file as NotchLC and will play it just fine. …

    I was under the impression that NotchLC playback is available to individuals royalty free. When a software vendor adds NotchLC support, the software vendor must pay a per usage royalty. That would explain why a NotchLC movie would play in QT and error / require a license for WATCHOUT asset manager.

    18 hours ago, Brian said:

    … I was able to re-encode the video to NotchLC with After Effects and the resulting file works great. …

    Now that is baffling. Could you provide an example of a NotchLC file that plays in QT but errors in a licensed WATCHOUT asset manager?

  4. The codecs may be an issue as well. The movie frame rate and the output frame rate have an impact. This may be on the edge for ProRes, should be no issue for HAP. While 24 fps may make smaller files, the added workload of converting 24 fps to 60 fps on the fly may play a role as well. Frame blending setting also may have an impact.

  5. 1 hour ago, ManuelM said:

    Something weird has happened to my project on the production computer.

    I had it open when a power failure occured. After restarting the computer and opening Watchout, it asked me to load an autosave that was more recent. I clicked yes and the computer froze. 

    I forced restart again and tried to open the original project file directly, but the computer keeps crashing.

    Have any case like this happened before? Any clues?

    WATCHOUT version?

    can you open a new show in watchmaker / production?

     

  6. 4 hours ago, Jacky said:

    Thanks for the reply, so there was a typo in the show name. thats why when we where calling the load show command it got stuck in analyzing. Its like you said its a upper lower case issues our devs missed it. Thanks!  …

    and thank you for taking the time to reply back with the resolution.

    4 hours ago, Jacky said:

    … Also what is weird about it is that if i load show via command and it failed then online the show via production successful, then send Telnet command to the display with the correct task names it will still play. My guess is that show names doesn't matter after the show is loaded? also would be a good thing to know, since i always thought that they where linked. Thanks!

    You will probably mostly get away with that when there is only one watchpoint computer in the cluster. Some messages from the watchpoint computer may still be sent to the watchmaker computer since that is where the last successful load came from. If there were more than one watchpoint computer in the cluster, the watchpoint computer receiving the command would not relay it to the other cluster members since a successful load is required to redefine the cluster master.

  7. On 3/4/2024 at 1:37 AM, Jacky said:

    … software restart for the watchpoint software. everytime we would use "load" command it would just get stuck on analyzing, but if we use the production software to push an "online" they it will bootup the display. …

    Been thinking about this one. Question - when using watchmaker/production do any errors appear in the message window? A load on watchpoint encountering a same error may get stuck where watchmaker has its error messaging subsystem to deal with it.
    Also, you mention a watchpoint software restart, … so the issue is after a watchpoint computer power up, no watchmaker session since power up, while hanging on the logo screen with progress bar, triggered from an IP load? 
    Also, and I hesitate to re-iterate this but are you certain watchmaker and watchpoint are attempting to load the same show? For example “Main show” and “Main Show” are two different shows.

     

     

  8. On 12/16/2023 at 5:05 AM, SawLae said:

    Can I ask about Watchpax2? I want to know how to set up Watchpax 2 the first time And how to edit the IP address of the Watchpax2.

    As to your original question, editing the IP address of a WATCHPAX or WATCHPAX 2 running version 5.5.x is a bit complex. A WATCHPAX or WATCHPAX 2 running v5.5.x ALWAYS uses DHCP to determine its IP address. That cannot be changed. The setIP command in a startup script of a WATCHPAX running version 5.5.x sets a virtual IP address in addition to the address determined by DHCP. That can result in some unexpected behavior. (This is changed in v6, in v6, the setIP command does in fact set a fixed IP address.) If you want to set a fixed IP on a WATCHPAX or WATCHPAX 2 running version 5.5.x, the recommended method is to provide a DHCP server with IP reservations. IP reservations reserve IP addresses for a specific MAC addresses. (I personally use a simple router DHCP server with the needed IP reservation function.) Related to that, always use WATCHOUT name when assigning the stage displays to a WATCHPAX, never use the IP address. (WATCHOUT name is assigned to a WATCHPAX or a display server using the WATCHOUT Production Network Window.)

     

     

     

  9. The answer may be different based on the WATCHOUT version you are using. v5.5.x and v6 have differences in WATCHPAX configuration.

    Note, a WATCHPAX 2 as shipped from the factory is NOT compatible with the current version of WATCHOUT. The original configuration of WATCHPAX 2 is only compatible with WATCHOUT 6.6.5 and older versions. If you wish to use versions 6.6.7 or higher, the unit must return for factory update (this can be done by Premium Partners or Dataton factory.)

    WATCHPAX run the same WATCHOUT Display software as any other WATCHOUT Display computer. So any user guide reference to the display software applies to WATCHPAX as well.

    IP address is set with a startup script stored on the WATCHPAX. See: https://www.dataton.com/watchout-users-guide/appendix/c-control-protocol/controlling-the-display-software

    BTW The setIP command only applies to  WATCHPAX so it is documented in the WATCHPAX sample startup script. see:

    Also

     

     

  10. No, there is no command to determine conditional layer status. Conditional layers are typically used with external control methods. The control system should keep track of conditional layer status. Anytime the control system sends a conditional layer command, it sets the status of every conditional layer.
    And a reminder,      enableLayerCond 0        does NOT turn off all conditions, it resets to the default conditional layer states defined in the preferences tab when the show was saved.

×
×
  • Create New...