Jump to content

kai

Member
  • Posts

    39
  • Joined

  • Last visited

Posts posted by kai

  1. On 12/19/2023 at 5:54 PM, jme said:

    Hi Kai,

     

    Sorry, as Jim says, WATCHOUT 6 does not have any feedback command to return the status of the active layers. But I have in this post included a small example program that have one timeline "ActiveLayers" that, when run, will send feedback to a UDP host with IP 192.168.10.10 / port 12345, with the number of the active layers 1-5.

    So what you need to to do in your control system is listen to the port you setup in WATCHOUT as feedback and the correct IP number pointing to your control system.

    Send the command "run ActiveLayers" to WATCHOUT production computer on port 3040, using UDP or TCP, also make sure you enabled external control under File/Preferences/Control. The timeline will return a number 1,2,3,4,5 or a combination of numbers indicating which layers that is active, back to your control system.

    If you want status of more layers, just add more layers to the timeline "ActiveLayers", set the correct condition on the layer you add and copy paste the string out cue and change the number that you send in the string out cue to indicate the layer that is active or not.

     

    Hope this helps.

    Cheers! /jme

     

    ReturnActiveLayers.watch 11.64 kB · 5 downloads

    Hi Jme,

    Amazing, that is perfect for me to use in our show, after I made a mistake with condition layer in 4 show last week but this topic it's made a smooth running and your session it's make me feel more comfortable.

    Thank you sou much.

    Kai

  2. 10 hours ago, Mike Fahl said:

    I guess you could make a timeline that's always active that sets an input depending on enabled layer condition. I believe you can get the input value from WO. That's more of a work-around for obtaining this, and would really only work for a single layer condition being enabled at a time, but could get you out of a pinch if need be.

    Mike

    Hi Mike,

    Yes, your guess it's correct, and now i'm waiting for WO7 to see all new feature, I hope it's can try to download beta version soon for testing.

     

    Regards,

    KAI

  3. On 12/18/2023 at 3:09 AM, matkeane said:

    If you're only switching 1 conditional layer, you probably don't need an external app, but otherwise I built a little app a while ago to manage them - https://matkeane.com/app/conditional-layers-utility-en. I haven't updated it in a while, but it it could be of help, let me know.

    Hi,

    Your utilities it's made me more understand about watchout condition,

    Thank you so much.

    KAI

  4. On 12/17/2023 at 10:15 PM, RBeddig said:

    Hi Kai,

    To calculate the conditional layer, you need to add all the conditions...

    To turn all conditions on is 1073741823.

    If you then add another "1", you'll turn all conditions off.

    enableLayerCond 1073741824$0D

    condLayer.watch 10.77 kB · 2 downloads

    Hi Rainer,

    Your sample session it's that I need and help me a lot, last week it's nightmare for me during a show,

     

    Thank you so much

    KAI

  5. 42 minutes ago, jfk said:

    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.

    Dear JFK,

    Thank you so much for fast reply, yes a little confuse with cond 0,  I will save no condition layer enable in preference but after send command enable layer 1 then send back to enable layer 0 but it's still enable layer 1.

     

    KAI

  6. On 3/11/2020 at 8:23 PM, Muath I J said:

    Here is my suggested trouble shooting method to save your time to know which output is giving you a headache :

    1- remove the force EDID from all outputs (if its forced ) and unplug all outputs except for output 1 then restart the machine.

    2-in WO production deactivate all the outputs except output 1 by ticking the box (use this display )  .

    3- now make sure u have set the proper EDID that matches output 1 config. in WO and try to go online ( without forcing the signal).

    4- now if it worked keep adding one output at a time and go online, until you find which output is causing the issue then troubleshot that output.

    ***please note when forcing the EDID make sure you upload the file to each output separably and never copy it from another output as it may cause EDID conflict.

     

    Best of luck

    Hi,

    Thank you so much for share your tips,

    KAI

  7. 2 hours ago, jfk said:

    If a customer is encountering a maximum HAP resolution, it is most likely a GPU limitation. i.e. the GPU has buffers that probably max out at 8K. 8K is not a limitation imposed by WATCHOUT, and there are customers who have successfully encoded HAP videos where the width has significantly exceeded 8K, but I can not recall the GPU they were using.

    With HAP encoding and assuming the GPU buffer can handle the final size, it is best to split them up into Display server sized movies. If all of your movies will play out from multiple outputs on a single server, then I see no need to pre-split HAP movies. Although keep in mind the HAP 'chunks' encoding setting is important to success with movies larger than HD60p.

    Hi,

    Thank you so much

  8. 3 hours ago, matkeane said:

    The maximum resolution at which a HAP video file can be imported into Watchout is currently 8000x8000px. I don't know whether that is a software limitation, or whether it is limited by the GPU. Either way, HAP media at higher resolutions must be split into pieces for playback.

    In general, the graphics company will deliver content at full resolution and quality (i.e. uncompressed, if feasible, or using lossless compression) which might, for example, be a ProRes video file or an image sequence (which makes partial content updates/corrections easier). The file size and data rate will usually make this unsuitable for playback. However, the next step is to use this as your master for slicing up and compressing the content, using a codec more suitable for playback in Watchout - HAP, MPEG2, h264, etc, depending on circumstances.

    The delivery format may also depend on your physical proximity to the graphics company - lossless codecs are more suitable for delivery on a hard-drive. If files are being sent over the internet, you may want to compromise with some form of compression to speed up transfer times, or use image sequences which can be transferred image-by-image rather than as one huge file.

    Hi,

    Thank you so much for explain,

     

  9. On 1/9/2019 at 4:16 AM, matkeane said:

    Hi,

    It looks that 25Gb file is the full 13824x3464px resolution though. I thought your plan was to split the content into roughly UHD-ish chunks (in any case, Watchout won't accept HAP files above 8000px).

    On a recent project, I also ended up splitting content into roughly UHD resolution pieces which, at 25fps, were running at around 450Mbps on average. That was a 25 minute show but content was in 1-3 minute scenes which made rendering/copying/importing/updating easier to manage than dealing with content of the full duration.

    Hi,

    We hire a media animation company to make a content for this project and them told me it's first time to make resolution like this , any way I can told them to make any format if I need, them told me to finish render for 1st scene in this 3 week and them told me again it's long 10min and close to 1TB,

    I will try to test every solution to make this project done,

    Thank you for your advice it's help me a lot for newbie like me

     

    Regards,

    Kai

     

×
×
  • Create New...