Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

About Merten

  • Rank

  1. Hi, we are running WO 6.4.1 on Win7 and just installed a RME UC. It is synced to 48 kHz wordclock, we use the spdif (coax) output. Audio is played out from the production PC via ASIO at 48 kHz. Everytime a show gets opened, WO jumps back to 44.1 kHz. To get it on 48 again you have to choose a higher sample rate (96, 192) first and then 48 for it to be set properly. It is not possible to go from 44.1 directly to 48 kHz. Although it shows 48 in WO, in RME's specifications it is still getting 44.1 from WO. Anyone had similar issues? Maybe it's the ASIO driver? Is there a recommended driver? ASIO4all perhaps? Another thing: The audio setup is saved globally, which is interesting, since it is the only thing to be saved globally, and not only in the show. Seems like a bug to me...
  2. Thanks Mike, but that would make no difference taking the detour via companion. It is working with the 'bank press' now, it would be neat to get it working by just send an output string out of Watchout directly to the Midi-Relay. The question is, if json methods can be sent as an output string.
  3. Hi, we discovered free way to send out MIDI/MSC from Watchout via Bitfocus Companion and the module Midi-relay. Midi-relay is a small java app which sends/receives MSC/notes from your midi-interface by getting http requests. For every command there is a button to program in companion, plus sending a String output http request "BANK-PRESS" from WO to trigger that button. It works flawlessly and being able to trigger sound and light is a big step. The detour over companion is quite time consuming, a direct string output would be nice. So far I had no luck sending a POST http-request with WO: MIDI-relay is running on WO-production, port 4000 { midiport: 'MIDI Port Name', midicommand: 'msc', deviceid: 0, commandformat: 'lighting.general', command: 'go', cue: '10', cuelist: '13', cuepath: '' } So the string from WO would be: POST {...} $0D I tried monitoring with wireshark to see what the syntax in WO should be but did not get clear results. Is it possible to send a .json method as a string output at all? I was looking into the the bome-box / network before, but there is no way to send commands from WO production, as serial output is only available on a display PC or with a TCP/serial converter. Or am I getting sth wrong? https://github.com/josephdadams/midi-relay https://www.bome.com/products/bomenet
  4. Deltacast... https://www.deltacast.tv/products/product-list
  5. Hi, when I change the position of a corner by clicking on it and then moving it with the arrow keys, it is no longer possible to change the position by arrow keys. The selected corner stays white (selected). Is there a way to deselect the corner or is there an other way to get the position working with arrow keys again? Thanks, Merten(v.6.3.1)
  6. Thanks, Rainer! Works perfectly. Finally a solution for a very old problem, we used to deal with by just fading over. Honestly, I find that the programming effort relatively high for such a "simple" thing...but it works! Walter's solution might be a bit easier, also thanks for that! Regards, Merten
  7. Yes, jfk is right. I contacted Blackmagic and they tell me that Watchout is not an officially supported software. And Dataton has to change something... We use our 1080p25 cameras with Display PCs running the old BM 10.1.1 driver. Another workaround is to use an other SDI capture device like this one. https://www.vision-dimension.com/de/bilderfassung/usb3-video-grabber/xi100dusb-sdi/170 Works really well, no problems with WO and you can keep the newest BM driver. It would be helpful for other WO/BM Decklink users to know about the issues and to collect posts to find a solution. The Decklink series are recommended in the Technical Notes in the Document 'Capture Cards' and a lot of people use them. Perhaps it would help to make a list, which signal works with which driver and what is the right resolution to choose in WO's live video dialogue. Just an idea...
  8. Same thing here... http://forum.dataton.com/topic/2225-1080p25-with-blackmagic-decklink-quadduo/
  9. Thanks for the quick answer! I just wanted to make clear that there is no problem with the signal and that the capture card display the camera. I discovered, that when you use Decklink driver 10.7 or 10.7.1, that the physical inputs of the Decklink Quad are changed. Input former input 1=4, 2=3, 3=2, 4=1. So I have to change them in WO Display Video In. I saw that there are some topics regarding similiar problems, so I'm not alone... http://forum.dataton.com/topic/1931-blackmagic-decklink-quad-capture-issues/?hl=decklink http://forum.dataton.com/topic/1368-blackmagic-decklink-4k-extreme-capture-issue/?hl=decklink http://forum.dataton.com/topic/1931-blackmagic-decklink-quad-capture-issues/?hl=decklink
  10. Hi, I am having issues with cameras, putting out 1080p25. I cannot get them to sho in WO Display (v6.2.1). I am using the newest Decklink driver 10.7.1. In Blackmagic Media Express the camera is there. The new auto-detect in the software tells me the input is 1080p25. But no chance to get it working with WO. I tried with two different cameras. I tried with the Decklink Quad (v1), Decklink Duo (v1+2). When I downgraded the Blackmagic driver to Decklink version 10.1.1 it is working in WO. Another thing is, that I have to use "Decklink Video Capture" instead of "Blackmagic WDM Capture" with version 10.7.1 (or newer than 10.3.7). Otherwise, I only get Input 1 working in WO. All other Inputs are dead, although they are shown in Media Express. Any clues?
  11. Same here. I had to downgrade from 10.3.7 to 10.1.1. Although it seems to make a difference wether you use the "Blackmagic WDM capture" or the "Decklink Video capture" drivers in WO Display's Video In window. http://forum.dataton.com/topic/1934-bmd-desktop-video-driver/
  12. When WO Display crashes, on the Display computer a and Windows-message appears: Watchout doesn't function any more. (In german: Watchout funktioniert nicht mehr). In WO Production I get the message "Lost connection to Display computer". In most cases, after about 30s, WO Display runs again. I think, the 2nd instance of Watchout Display (WP) is taking over. Sometimes I have to restart WO Display manually. When the connection is lost, the Display PC is putting out black. The crash happens, when the cursor in the timeline is standing on a Live Input, of which the driver was changed, as desribed in my previous post.
  13. Thanks for the quick answer! So I guess it's the usual BM hassle... Though it's weird, WO doesn't show Live Input when I change the driver in the Video In Menu (WDM/Decklink) and crashes. And that it worked again when I downgraded to the older working driver Version. Perhaps, Windows (WDM) remembers which input card was used.
  14. Thanks, jfk! Do I always have to use capital letters in WO? In Packetsender I discovered this $0A for \n before, but written $0a.... Gonna give it a try!
  15. Hi, I just wanted to share some of my latest BMD Decklink issues, in the hope to get some feedback from some (worried) users. Does someone know, if the newest driver version 10.5.2 for the BMD Decklink Video Capture Cards (SDI Duo/Quad) works with WO? Currently, we have installed version 10.1.1 and 10.3.7 as these work okay, as far as BMD things work... I discovered, when I updating the driver from 10.1.1 to 10.3.7 (to capture a GoPro4, what's not possible with 10.1.1) on a display PC wit Decklink Quad SDI, that older WO shows, with Live Cameras in it, created with the older driver didn't work anymore. The camera signals came into the card, but WO was not able to show them. I downgraded to 10.1.1 and it wored again. So, does does the WO show save, which BMD Decklink driver was used when creating the show? And does it help re-installing Watchout after I updated the Decklink driver+firmware? The goal is, to be able to run all old shows with most stable decklink driver...if something like this exists. An other strange thing is, that with version 10.3.7, Watchout Display is only able to show live video, when "Decklink Video Capture" is selected. (cntrl+W, then Live Input Devices) On 10.1.1 we used to run the "WDM capture", as recommended. Also, it is not possible, to run a show with Live Video, which was created with a Display-PC where the WMD driver was selected on an other PC where Decklink Video driver is selected. Watchout Display even crashes, when you try to go online on a Live Input in the timeline. So I guess WO loses the connection to the Live Input Card, once the Driver is different from the original. Am I right with this assumption?
  • Create New...