Jump to content

Benoit

Dataton Partner
  • Posts

    138
  • Joined

  • Last visited

Posts posted by Benoit

  1. Hello Stiegzinator,

     

    The Samsung protocol is hard to find. It depends of your monitor ID and there is a checksum at the end. For monitor 1, try send to your monitor IP port 1515:

     

    power on :

    $AA$11$01$01$01$13

     

    and power off:

    $AA$11$01$01$00$12

     

    Samsung doc explicitly tell you to send the command for 3 times every 2 Seconds until ACK command. If there is no ACK within 3 times, It means failure.

     

    Good luck,

     

    Benoit

  2. Hi Michael,

    We already tried to emulate some Spyder features for some customers.

    I think for the best result you should not use only tasks because you will need to know what are the tasks status to know what Watchout need to do.

    What we did is to use inputs for fade, pip positions ect… and drive the inputs with control cue that send commands to Watchout itself. It’s a bit tricky but there are 2 main advantages to do what you expect:

    • All effects are driven by inputs so you can ask a media to fade out in 1 second, if he is already transparent there is no side effect.
    • All media are active and you don’t jump into aux timelines, Watchout react much more faster with no pre-roll, it’s particularly useful for live inputs (even if there are others trick to solve this problem).

    For example, here how to setup a background video with 2 presets to show and hide the background:

    • Create a generic input called “Bgnd_opacity” (limit 1).
    • Create a task named “Bgnd” and put your background video in a layer
    • Add an opacity tween but don’t add any key points, map the tween to the input “Bgnd_opacity”. Now if you move the input, it change the opacity.
    • To play the video background when you fade in, add “Bgnd_opacity > 0” to the trigger of the task
    • To stop the video background, create a new aux timeline “Bgnd_stop” with 2 control cue “stop aux timeline named Bgnd” and “stop itself”. Add “Bgnd_opacity=0” to the trigger of the task. Now you just need to control the input to fade and start and stop the video.
    • To control the input from anywhere, create an output “WO”, IP=127.0.0.1, Port=3039
    • Create a new task named “preset 1”, add the “WO” output and in the cue settings, data to send=”setInput "Bgnd_Opacity" 1 1000$0D” (let’s say the preset 1 start the bgnd with a fade of 1 sec.)
    • Create a new task named “preset 2”, add the “WO” output and in the cue settings, data to send=”setInput "Bgnd_Opacity" 0 1000$0D” (let’s say the preset 1 stop the bgnd)

    By doing this you can call many time “preset 2” with no effects if the bgnd is already stopped.

    And you can mix many inputs for fade, pip position etc. in your presets.

     

    Of course, it’s a bit tricky and there is certainly many others things to do, but it works…

     

    Tell me if it’s not clear,

     

    Benoit

  3. Hello,

    I’d like to suggest something.

    When you remove a media, it tells you if the media is used. If you work with a huge project, it’s not so easy to know where the media is used.

    Maybe you can update the message box to tell the user where the media he tried to delete is used:

    “Selected media is in use and cannot be removed. Used in the following tasks:

    • Task 1 (00:00:01, layer 23)
    • Task 2 (00:12:48, layer 3)

    …”

    Thanks,

    Benoit.

  4. Hello,

    The “interaction name” can be used by 3rd party software to create interactivity.

    Here you can find a project we did using this feature (sorry, in French) : http://www.videmus.fr/salle-immersive-et-interactive-lalimentarium-de-nestle/

    It’s a 14 ultra-short throw projectors setup, 7 Watchpax, with 2D lasers scanning the walls for visitor’s fingers.

    If you add a task name in the “interaction name” field of a cue, the task starts when someone touch the cue.

    Let me know if you want more info.

    Benoit.

×
×
  • Create New...