Jump to content

jfk

Moderator
  • Posts

    1,808
  • Joined

  • Last visited

Posts posted by jfk

  1. 12 minutes ago, Essam Ahmed said:

    … is there amethod to make factory reset for the Display server WatchPax4, i think this may solve the problem …

    No, the user factory reset startup option was added with the WATCHPAX 4’s successor, the WATCHPAX 40 (and soon the WATCHPAX 42).

    The WATCHPAX 4 (like all WATCHPAX) is a locked OS. It is highly unlikely a factory reset would change anything other than clearing all shows and clearing startup script. But if you wish to return it to Dataton or a Premium Partner, a full factory reset can be done as a service department procedure.

  2. 59 minutes ago, Essam Ahmed said:

    i have one display server watchpax4 and  one production laptop with watchout liciense and connected togther within the same subnet, the production pc see the display and the conection is"Ok" asper atcched image.

    but when make online the message " From Display "Display_1" of Stage Tier "Base" of StageList of Stage, 2022-06-28 9:27:31 PM
    Runtime error; Command: activate; Display Address or Output not found", and

    " From Display "Display_1" of Stage Tier "Base" of StageList of Stage, 2022-06-28 9:27:31 PM
    Runtime error; Command: gotoTime; No show active"   appear 

    if any face the same problem can advise.

    thanks...
     

    IMG_20220628_162717.jpg

    IMG_20220628_162749.jpg

    The second error is simply a side effect of the first error. The simple ping that the OK indicates is a simple TCP packet getting through. It does not indicate either way if a firewall is partially blocking the more sophisticated communication needed to transfer files and go online.

    While you may use an IP address in the computer field, i strongly recommended against it. Especially with WATCHPAX. Use WATCHOUT name for the display server instead. For one thing, using the IP address masks issues that show up in other ways and should be corrected. But the more likely cause is a firewall or some other form of network disruption.

  3. 2 hours ago, diskin said:

    Could the gamma calibration between the projectors improve the seam with mixed video content?

    The proper gamma settings will improve the blend, regardless of content.

    2 hours ago, diskin said:

    How can I do an auto-calibration to projectors in watchout ?

    While there is a way to integrate auto calibration using WATCHOUT’s MPCDI support, that method is limited to WATCHOUT’s eight-bit blending.

    For extremely challenging situations there are superior options.

    There are projectors designed for overlapped blending that handle the blending task internally independent of WATCHOUT and they blend at ten-bit.

    A step above are camera based calibration systems. To exceed what is possible in WATCHOUT, they operate at the gpu level “underneath” WATCHOUT. In that scenario, WATCHOUT is set to a single non-standard resolution representing the total of all blended outputs. The calibration system configures the gpu before WATCHOUT is started. When WATCHOUT then requests a non-standard resolution (like a single output of 7248x1080 for example) the graphics card complies since it was already configured for that by the calibration system. This provides the ultimate since the calibration system on its own handles 10 bit blending, color correction and black level compensation at the gpu level below WATCHOUT.

    At the end of the day the projector is the limiting factor. No amount of upstream manipulation is going to overcome a projector poorly suited to the task. But with a quality projector, additional systems can exceed WATCHOUT’s best efforts.

  4. Ultimately the quality of an edge blend is a function of projector calibration. gamma is particularly important.

    In critical situations, once projector remedies are exhausted, auto calibration systems that add 10 bit blends and black level compensation reach maximum optimization. Scalable Displays running native under WATCHOUT provides such a solution.

  5. 1 hour ago, cihaner said:

    I'm pretty sure the license key is corrupt. and I request a change by paying the hardware fee of the wibu key. My problem is not software update.

    The protection circuit in a WATCHPAX contains a restricted non-transferable license. The price of the WATCHPAX reflects the restriction. ie literally no value is placed on the license in order to keep the hardware cost as low as is feasible.

    If the license is in fact corrupt, arrange to send it in for repair. That is an extreme rare failure, it should be repairable.

  6. You have not specified the WATCHPAX model or the WATCHOUT version you are using. This thread would have been a lot shorter if you had included that basic information.

    3360 WATCHPAX and 3362 WATCHPAX 2 are the only WATCHPAX units capable of running v5.

    Neither of these units as delivered is compatible with v6.6.7+. If you install those most recent versions you will encounter “License key not found”. This is noted in the WATCHOUT release notes.

    Dataton will update the firmware on a WATCHPAX or WATCHPAX 2 to be compatible with v6.6.7+ at no charge. But you must return the unit to Dataton or a premium partner for the update.

    If you want an official statement from Dataton, please use the support channel. The public user forum is just that.

     

     

  7. 7 hours ago, Joe Stoner said:

    WHY do you specify Windowz servers?

    What's wrong with a stable flavour of Linux?
    ATB
    Joe

    Windows includes technology currently used by WATCHOUT, most notably Microsoft DirectX, including graphics card hardware acceleration of DirectX 3D. 

    Even Windows in a virtual machine significantly suffers from the emulation layer in virtual environments.

  8. 3 hours ago, cihaner said:

    I'm asking to confirm. If my license key fails and I return the defective key to you, I only have to pay the wibu key hardware fee. I don't need to pay license fee. is this true?

    Partially true. 

    You are correct, as long as you return the defective key, you do not have to pay the fee for the WATCHOUT software. However, all licensed components included in WATCHOUT (mpeg decoder, AC3 decoder, etc) are charged by the physical key, those licensing fees are not transferable from one key to another. Dataton must pay those fees. Even Wibu, the hardware vendor for the key, adds licensing fees for their software protection system. So the cost is more than the simple hardware cost - there are licensing fees that must be paid by Dataton on every key Dataton enables for WATCHOUT. 

    To the best of my knowledge, the current fee charged by Dataton for a damaged key swap is below cost. i.e. Dataton underwrites damaged key replacement.

  9. 7 hours ago, Karen said:

    … The current failure situation doesn't look like it's related to another VNC. 

    I would not be so sure. Over the years have observed some pretty strange behavior related to a second VNC install. Such as disc full errors when there are terabytes of free space. ie behavior you would not relate to VNC. And simply uninstalling VNC did not fix it, had to restore the original tuned image from before the VNC install. You may be right, it may be unrelated. But it is an issue that has caused unexpected anomalous behavior in the past.

    Also, I would try 16 chunks for the 8k 60p clips (if that is possible).

  10. Fyi for conditional layer control novices

    You can also set default conditions that automatically enable when no conditions are specified. This is useful for defining a default language for example, so the show is less likely to run without audio.

    Those default conditions will re-enable for the 0 condition arguement. i.e. layer condition 0 is NOT all off, it is return to default.

    Default is defined in File - Preferences - Conditions. Anything enabled in this tab when the show is saved becomes the default when the show is opened. However, if you define non-zero conditions at load, or send a non-zero enableLayerCond command after load, either will override the defaults.

  11. Sounds like you are also using Live Update. The error message typically means WATCHOUT Display has crashed. Since the only thing that has changed is the new .mp4 file, that is what i would suspect is the cause.

    For the purpose of diagnosis, first, simplify things. Turn off Live Update and stay offline. Drag the suspect .mp4 into the media window. If that works, put the movie as a cue in an empty aux timeline. play the movie in production preview. If that still works, try to go online with Live Update disabled. Then play the movie on display. If all that works, then we will look at things other than the media.

     

  12. When operating without a production server (aka from a control perspective - cluster mode), 

    load “show name

    defines the control cluster members and defines the control cluster master.

    The control cluster definition consists of the loaded show file’s stage window. i.e. Any valid display server definition (Display - Specification) in the stage window is a member of the control cluster.

    The WATCHOUT computer address parameters (name - cluster name) are something different from a control cluster.

    watchpoint will accept new load commands from a valid IP connection or script at any time from any connection, the most recent takes precedence.

    The load command should only be sent to one member of the control cluster. Since every member of a group contains a copy of the show file, any member can be the master.

    If you want to change the master and/or change the group, simply execute a load of a show containing the desired new parameters.

     

     

  13. 3 hours ago, Bryan said:

    Followup: I forgot to define the computers as a cluster in the network window.

    That is not a requirement. Cluster is an optional patameter. If you do change this parameter in the WATCHOUT Network window, you must then update the show from production without errors before the load command will function correctly. Of course, you must add the new cluster name in File - Preferences - General - Cluster to successfully update the show. 

    3 hours ago, Bryan said:

    This has led me to a new problem, however: now every computer is running EXCEPT the computer I am sending the message to. the conductor machine, whichever one I choose, still displays an "aborted" message but then turns its outputs black. This leads me to a question I am dreading: does Watchout require the conductor display within a cluster to ONLY operate as a conductor?

    No. The WATCHOUT Display computer that successfully executes a ‘load’ command is the cluster master. Single computer clusters are the most common type and of course they work under IP control. The cluster master still functions as a normal display computer.

    3 hours ago, Bryan said:

    If so, this is nothing that I found documented anywhere. If not, does anyone know what might be causing this?

    Not really, have not observed load commands abort.

  14. 4 hours ago, MISTERK said:

    Hi all

    Can i mix different resolutions (same frequence=50hz) within a watchout display ex: 1 output 3840x2160@50hz and another at 1920x1080@50hz

    Yes. As long as all are same refresh rate, no problem.

    4 hours ago, MISTERK said:

    or all resolutions must be the same ?

    No

    4 hours ago, MISTERK said:

    To do this, any differences between nvidia and Amd ?

    No

    4 hours ago, MISTERK said:

    or is it impossible with Watchout ?

    it is possible.

    This was an improvement during the WATCHOUT 6 run. Can not recall which 6 version added this, but it has been a while now.

×
×
  • Create New...