Jump to content

jfk

Moderator
  • Posts

    1,810
  • Joined

  • Last visited

Posts posted by jfk

  1. Yes. WATCHOUT includes IP control. It is documented in the WATCHOUT User Guide, Appendix C.

    Commonly, auxiliary timelines are a method of “recalling presets”. Once the connection is established, simple commands provide the function you request. Auxiliary timelines are user nameable, so a simple command like

    run “Preset 1”

    would do what you need. 

  2. 17 minutes ago, joeartist said:

    …. Is there a limitation on virtual display feeding other virtual displays? …

    Yes. Virtual Displays are not intended to be re-entrant. Dataton does not support the use of virtual displays within virtual displays.

    That said, there are people who have done so successfully. But it is unsupported by Dataton.

    Compositions on the other hand are supported in this manner. In many cases, nested compositions provide the function being achieved with nested virtual displays.

  3. Removing and reloading the files are unlikely to have any effect on the issue you describe.

    Changing a still image file type is unlikely to help as well. Note, WATCHOUT does not display the original file during playback. All still images are converted to an internal format and that is used for display. so regardless of file type, all still image formats will perform exactly the same for the same original. 

  4. On 2/7/2022 at 11:37 AM, federico cristobal said:

    thanks for riplying sir,

    were using watchout player....

    i try to ping the ip address it is unreachable plus at the back of the player the signal is orange meaning it is not responding?

    it also showing the license key not found...

    I repeat …

    [quote]What version of WATCHOUT? What type of WATCHOUT Display server?[/quote]

    WATCHOUT Player is still not specific enough.

    i.e. there is a known incompatibility between old Dataton WATCHPAX (tn 3360) and Dataton WATCHPAX 2 (tn 3362) and the newest updates of WATCHOUT (v6.6.7+). It is remedied by a factory update to the old unit’s disc image.

    From WATCHOUT 6.7 Release Notes ...

    Known issues and limitations

    • Before updating Dataton WATCHPAX (product number: 3360 ) or WATCHPAX 2 (product number: 3362) media players to WATCHOUT version 6.6.7 or 6.7, please ensure that the unit’s hardware image version is version r23 or higher for WATCHPAX, and r33 or higher for WATCHPAX 2. If the image version is older, the unit will stop working and a “license key not found” error will be shown after the WATCHOUT version is updated. 

      For more information on how to update the hardware image, please contact your local partner or Dataton.
  5. WATCHOUT is not generating that message, Windows is sending that message. When Windows generates an error, WATCHOUT passes it along so that WATCHOUT may remain in the foreground. (Otherwise WATCHOUT would need to step aside and allow Windows to take control). This is done to attempt to keep WATCHOUT running past operating system errors.

    Anyway … 

    https://knowledge.dataton.com/knowledge/interpretation/translation-of-error-codes-in-watchout

     

     

  6. First off, the most common issue with mp4 encoding is bi-directional frames, they should NOT be used. There are other concerns, like do not use transport streams. Have you consulted dataton’s tips on mp4 encoding? (btw h.264 is mp4 video encoding with audio encoding options not supported in mpeg4 containers. Since you should NOT include audio for WATCHOUT, movie files should be video streams only for WATCHOUT, the audio variables are irrelevant.)

    https://knowledge.dataton.com/knowledge/how-to-encode

     

     

  7. 8 hours ago, mouniroo said:

    ...i just finish to ready the manual of watchout 60 and i am not sure if i will have access to the desktop to setup my software ..

    No, you will not be able to add software to a WATCHPAX. They are locked for a reason. Changing the configuration of the locked down server defeats the purpose, so it is not permitted.

  8. Although nothing has changed as it relates to WATCHPAX, the comments about other servers under a much older version are out of date. In 2017 WATCHOUT still used WDM for audio.

    Since then WATCHOUT switched to ASIO for sound interface and up to 24 channels can be sent via Dante Virtual Sound Card on custom servers.

  9. 59 minutes ago, autonic said:

    … You need to be "online" with the watchpax for this to work! (I thought all DMX-data was streamed from the production machine?) …

    Yes, when operating in production mode, the production station does generate the ArtNet data.

    The online state (license) is required to enable production computer output.That includes all forms of output - IP strings, DMX, display computer communication.

    What is confusing is input is always active, regardless of online state.

    Also confusing, when offline, the production computer will show output status changes in its output window, even though nothing is actually being sent.

  10. WATCHOUT installs codecs to playback .mp4. There should be no need to convert them to .mov container. In fact, for WATCHOUT, .mp4 container is preferred over .mov.

    On the other hand, your phone may encode the video for smallest file size which may include bi-directional frames. B-frames are not recommended for WATCHOUT, B-frames have been known to cause instability with prolonged playback. So you may wish to re-encode them as an .mp4 without B-frames and without audio for best results.

  11. 23 hours ago, Balage said:

    wich port used watchpax for upgrade? 

    Dynamically assigned. Ports used will be greater than 1024, but that is all that is predictable.

    23 hours ago, Balage said:

    … I dont know firewall issue, first i used for upgrade tplink router with default config. (i dont see the router defaults.....all devices mobile device) Setip not configured on watchpax, all setting default on devices. I will try tomorrow this repair instructions.

    The firewall of concern would be on your production computer.

    23 hours ago, Balage said:

    … I wanna understanding wibu protection system ( maybe this is a problem) …

    No, this is not the problem. As I said originally, “Licence key not found” during a propagated version change is normal and unrelated to the failure you are experiencing. Nothing has killed your WATCHPAX license. Please move on from the licensing and focus on the real problem.

    23 hours ago, Balage said:

    … I readed this forum and i got this post (maybe this is the problem? how can i find out?😞

     

    That strictly had to do with an old outdated power up initialization issue and is unrelated to the version change process.

  12. The “License key not found” message is normal when propagating a new version to WATCHPAX. At some point during the process, both the old and new version are loaded. The new version will be denied the key until the old version releases it. In your case, at some point, the new version fails to respond to production. Possible Firewall issue?

    When upgrading from some older versions, an autostart script setIP command causes issues as the new version fails to process the script comand and reverts to DHCP, triggering the unreachable message. Temporarily revert production and WATCHPAX to DHCP to complete the update.

     

  13. 4 hours ago, MauFir said:

    Hi Everybody,

    any news about the servers using GPU Nvidia Geforce 2 and 3 series?

    I heard that Dataton is releasing a new patch for Nvidia GPU.

    In my win 10 servers (WO 6.6.5) I'm using the RTX 2060 with the old driver (460.89), they work but sometimes I've problems, like a disconnection of 2 of the 4 video outputs.

    Thanks!

    Yes, the issue is corrected in the most recent release …

     

  14. 21 hours ago, Wakanda said:

    im having the same problem here, im using a desktop for production laptop and watchpax 60. Can anyone help please.

    please see log below

    Faulting application name: WATCHMAKER.exe, version: 6.6.7.0, time stamp: 0x61764850
    Faulting module name: rthdasio.dll, version: 3.1.7.1, time stamp: 0x5fcdd502
    Exception code: 0xc00000fd
    Fault offset: 0x000193be
    Faulting process id: 0xff0
    Faulting application start time: 0x01d7cf244c98a01d
    Faulting application path: C:\WATCHOUT 6\WATCHMAKER.exe
    Faulting module path: c:\windows\System32\rthdasio.dll
    Report Id: 4cdf5959-d32a-47c6-b1b2-79069a95db8b
    Faulting package full name: 
    Faulting package-relative application ID:

    Again, the WATCHPAX 60 has nothing to do with the error shown. The error shown is a WATCHOUT Production error related to the motherboard audio coprocessor and its software. So the above suggestions all apply.

  15. Sound from a video file is not recommended and is a known possible cause of a crash. The sound should be exported as a .wav file and the video re-encoded without sound.

    You can still play sound from the WATCHPAX 60 and turn off sound playback on your production computer.

  16. The error has nothing to do with WATCHPAX 60, the error is a production computer error. As Rainer points out, the error appears to be an issue with the production computer sound co-processor. Do you even need audio playback from the production computer? Possibly turning it off in production is a simple solution.

  17. 14 minutes ago, Timvideo said:

    Hi all, 

    Ive been trying to understand how to close a 360° projection inside a cilinder ? 
    I can overlap my displays in the stage window, edge blend them, but what should i do with the last (most left and msot right) edge ? 
    How can i blend these ends if i don't want a hard seam ? 

    Thanks ! 

    Create an additional display on each end to force the blends at each end. For these phantom displays,

    uncheck. Enabled:  Use this display

    that will tell watchout not to attempt to connect to the phantom display. WATCHOUT will still apply the blend for the display, whether it is enabled or not.

  18. 10 hours ago, roger said:

    Thank you for your answers, in the installation the watchout works without a controller. I need to update an image stored in a shared fold...

    not sure what is going wrong with this forum system, the above was sent to me as a post moderation notification, but did not appear in the thread. And the notice is truncated so this is just the beginning of the original post submission. Anyway …

    It does not quite work that way. 

    The lowest cost way to replace a still without using WATCHOUT Production or WATCHNET to prepare the image would be to use the URL function and store the images to be replaced at a URL via a web server instead of a shared folder. Then a simple aux timeline could be used to refresh the image that appears in WATCHOUT Display via a run timeline command.

    Alternately WATCHOUT Dynamic Image Server can provide the function using a shared folder, no commands are needed to update the image, it will automatically update as soon as a file is replaced. Only downside would be the requirement for another standard WATCHOUT license to enable the WATCHOUT Dynamic Image Server software.

×
×
  • Create New...