Jump to content

RBeddig

Dataton Partner
 View Profile  See their activity

  • Posts

    623

  • Joined

  • Last visited

 Content Type 

Everything posted by RBeddig

  1. RBeddig
    In WATCHOUT 7, you have to... a) define a runner (display computer) in your setup to be the active DIRECTOR. E.g., by selecting it in the drop down menu on the top right of PRODUCER or by defining this in the device window. b) define which timeline should start automatically after booting the display server by selecting "Auto Run" in the timeline properties. c) save, restart the display server and close the production computer or at least PRODUCER. The display server should now start with your selected timeline.
  2. RBeddig
    Hi, Has anyone successfully tested the SC720N4 HDMI2.0 / 4 CH 4K60 HDMI2.0 capture card from Yuan? https://www.yuan.com.tw/product/8
  3. RBeddig
    Hi Morgan, Someone is looking for the MIC3 manual in English. Unfortunately I only have it in German. Could you place it on your drop box once more pls.? Cheers, Rainer
  4. RBeddig
    Not sure whether MSC will ever find it's way into WATCHOUT since this protocol is about 10 years older than WATCHOUT 1.0. But maybe the dev team will look into this in the future. WATCHOUT 7 can see osc messages when those are float values. The iPhone app "protokol" by Hexler LLC is a nice free tool to see what data is actually sent by the osc sender. In WATCHOUT 7 you first create a new variable, e.g. osc.addr(“/Level/0”) with a value range of 0…1. Learning an osc key didn’t work for me (yet?). Then, sending a float value like 0.1234 to the osc address /Level should move the slider in your variable window. I used another little free iPhone app "Clean OSC" to send test data. Once this works, you can use the variable like any midi or artnet variable to work on an effect or to trigger a timeline.
  5. RBeddig
    BTW, neither .mov nor .mp4 endings can tell anything about the codec of such a file. Both are just envelopes and NOT codecs. .mov can hold many different codecs from HAP to ProRes to H.264 or H.265 or uncompressed or animation or.... .mp4 can hold AVC/H.264 but I've also seen H.265 files in such an envelope. So specifying "envelopes" as media definitions is about the same as telling someone that you send a letter in a blue envelope. Won't tell the receiver anything about what's inside.
  6. RBeddig
    Are you sure that the assets have already traveled to the display server? When loading a file into the asset server or assets window, you'll first see a progress bar underneath the name of the file in the assets window. This indicates that the new asset is getting optimized. Then, if you drag such a file into a timeline, the display computer (runner) will ask the asset manager for the file and copy it to it's own drive. There is also some progress bar to visualize this step but it is a bit more hidden. Click onto the small clock symbol next to the message bell symbol in the top right corner of the producer software. If media is traveling to a runner, you'll see a progress bar indicating the remaining time.
  7. RBeddig
    Yes, while the NDI signal will use way more bandwidth than WATCHOUT. Not me. We have an installation where WATCHOUT is used as a seamless switcher to drive an LED screen with 5760x2160px and different sub-screen areas. The server has 4x HDMI 2.0 inputs for external sources and we have two 4K NDI streamers (Newtek Connect Spark Pro 4K to NDI) in the room. This worked so far but you need to consider bandwidth limitations. What are your sources? Are we talking about NDI or NDI|HX? Newtek writes in it's manual for the mentioned devices: https://downloads.ndi.tv/Firmware/SparkPro/NewTek Connect Spark Pro Manual.pdf Also read page 13 of the manual! Pls. also read this nice article on NDI bandwidth: https://streamgeeks.us/how-much-bandwidth-do-i-need-for-ndi/ If you would talk about 4x NDI 1080p60 into 4 pictures on your WATCHOUT screen, you would need a network bandwidth of roughly 1Gbit/s without any headroom!
  8. RBeddig
    Yes! Jim is correct. You just need to install a small free web server on your computer and place the images in a folder so that you can access those through any browser with a URL path. If this works from a browser, you can use the image proxy in WATCHOUT to load the images on-the-fly.
  9. RBeddig
    Maybe you could instead try to use the feature of WO 6 to show image through an URL path. One difference in the media handling is that DIS will immediately show the new image if you change one while it is visible on your screens while using the URL path (add image proxy...) will load the image which is valid before the cue gets visible.
  10. RBeddig
    Normally Watchpoint stores the last setting and will even complain if you start the server without the audio interface being connected. Maybe Watchpoint can’t write to some drive or partition so the information doesn’t get stored. Have not seen such a behavior myself.
  11. RBeddig
    It sounds a bit as if some user rights have been limited. Have you gone through the full tweaking list for Windows? BTW, why don't you use ASIO for DVS?
  12. RBeddig
    If you google a bit, you may come to pages like this: https://lxadm.com/a-new-guard-page-for-the-stack-cannot-be-created/ All the pages point to either a problem of insufficiant memory or stack overflow. The memory is something you can test by running the Windows performance monitor in the back or testing the memory with memtest or similar problems. On the other side, WATCHOUT 6.1 is exactly 8 years old and there have been many improvements and bug fixes over the years. Maybe you should check the release notes to see if you do something which is described here as a fixed bug in a younger version. https://www.dataton.com/watchout-release-notes
  13. RBeddig
    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.
  14. RBeddig
    Are you referring to the warning message that it is not recommended to add a display to the production computer? This is just a new warning message. You can just click ok and create a local display but you're in charge of performance issues etc. when running all on one physical computer.
  15. RBeddig
    SMARTPAX_from_trax-3-user-manual.pdf
  16. RBeddig
    I looked through my manual collection this morning and found the description of the original SMARTPAX (3340) in the TRAX 3 user guide. I Extracted those pages for you. The description for the SMARTPAX QC can be found in the links mentioned by jfk above. Where are you located? You can send me a PM if you prefer. The main problem might be to find the triac (S-AV) adapters today.
  17. RBeddig
    Smartpax doesn’t drive triac adapters. For this you need a Pax. Smartpax can control many serial devices, send and receive timecode and DMX or control I/O connections. It can also be used to control newer projectors like Kodak Ektapro 5xxx, 7xxx and related.
  18. RBeddig
    Yes, but this is probably more a question of the performance of your computer and the codecs you plan to use. WATCHOUT 7 now gives you some good indication of the load on the CPU and GPU. But, you carry the higher risk when your hardware breaks and everything is on that computer.
  19. RBeddig
    The update procedure is correct. Since the encrypting mechanism of the wibu keys has changed, old keys need to be physically swapped if they are not small plastic keys with a serial number of 3-344xxxx or newer. So basically you would pay for both steps and receive a new key with version 6 and 7. Since you're in Amsterdam, contact Walter of AVtrade for details.
  20. RBeddig
    And another important question: do you have a WATCHOUT 7 license key or are you testing without a dongle?
  21. RBeddig
    Which version of WATCHOUT are you using? Are you using a notebook with one (?) or two (?) monitors connected? Which open processes / windows do you see when pressing the Windows key? Do you then see two WATCHOUT icons in the taskbar?
  22. RBeddig
    In WATCHOUT 6, virtual displays unfortunately can't be warped at all. This will be different in WATCHOUT 7.
  23. RBeddig
    It's actually the numpad "0" key starting the timeline. You could also take a look at the free version of Universe Control. It should be able to generate a control page as a web page and can control up to three devices. Universe has a very good driver for WATCHOUT.
  24. RBeddig
    This error usually shows up when the resolution set in the WATCHOUT production software does not match the EDID received from the image. Very often it is the case if you set 50fps in WATCHOUT and the display EDID wants 60fps but it can also be the resolution itself which is not supported by the display.
  25. RBeddig
    ด้วยความยินดี
×
×
  • Create New...