tobiasbecker

Info about the problem with Adobe Creative Cloud 2018 concerning HAP / QTKit-Support (April-Update CC 2018): If you miss the HAP-Family or H.264 from the Quicktime-Component please install the "downgrade" via the Creative Cloud Desktop App: Premiere Pro CC 2018: 12.0.1 AfterEffects CC 2018: 15.0.1 MediaEncoder CC 2018: 12.0.1 Then you have all the known options. These options are gone with 12.1.1 / 15.1.1. So watch out for the small .0 at the second position... Win and Mac are identical here, except for ProRes-Family on Mac of course. For your orientation attached you find a screenshot with arrows: Green = also avail in the new version after April update Orange = not avail but replacement Red = missing and bad Generally there is a "native" H.264 encoder in AdobeMediaEncoder (but not as render target in AfterEffects > render AE Comp via AME) so you don't need the Quicktime-Component for this anyway. The only real "showstopper at the moment is HAP/Q/Alpha so for this you need to stay on .0 for so long or search for other tools. Thanks to @jochri for the hint some time ago.

thanks for sharing!

Hi, I'm using somewhat of a different WO Master computer configuration and had an interesting experience today (WO 5.2.2, 64bit master, 32bit client). WO Master is using a Intel Pro network card which allows for different VLANs to be processed by the card. As the WO Master also runs Universe (show control) on a 2nd monitor it is talking in different networks using VLANs. All this is working fine - I also have the WO VLAN being top priority in Windows according to this http://forum.dataton.com/topic/668-routed-watchout/ thread. Now: as soon as I have a network (eg a VLAN without DHCP but also without manual IP address) that has a link-local address (169.254.x.x) address WO stops synchronizing between master and clients. As soon as I disable the virtual NIC WO works flawless again. What this means on the network side to my knowledge: The WO Master Windows decides where to put the traffic according to the assigned local IP addresses. IF there is an interface with 169.254.0.0/16 available its sending traffic for an IP in that range down that network adapter (and not the WO adapter any more). As soon as I disable this interface traffic to this address should not be forwarded (its going to the gateway of the first adapter which is WO which is empty but anyway). Question (to Dataton or anybody else): is there any explanation what is happening in that link-local IP range so that its essential for WO to run? Any other ideas or explanations? Just curious.. :-) Thanks.

2k with S400+W7000 works by the way ;-)

Hello fellow Watchout users, for an upcoming show I'm required to run a number of display computers with 2 outputs each on 2048x1080p/50 All outputs are on hardedge so it will be Watchout v5.5 with the S400 sync cards (+some FirePro cards) in each display computer. They will be connected to a lightware DVI matrix that would output a preferred EDID with this timing (EDID 46 / 2048x1080p/50 1 or 2, see also: EDID Manager rear ) I had issues in the past with lightware EDIDs and WUXGA (1920x1200p/50) where the display computer would recognize the resolution just fine but in the very moment I go to full screen in WO the resolution changes to something else. I am aware of the preferred timing issue with EDIDs and as far as I know, the lightware timings are exclusive (so no other resolutions for the graphics card to chose from). I did tests with 1920x1080p/50, WO v5.5, S400, FirePro cards and they were running great. Also I have been working with 1920x1080p/50 setups since years and it works. So right now I'm specifically looking for people who have done 2048 pixels wide per output, maybe even with an S400. Anybody? Does it work? Any hiccups or tips? Thanks! Tobi

Hi, I have tried to install the Dante Virtual sound card on a WO display computer in April 2012. The display computer had 2 physical ethernet ports on the motherboard. One was used with a separate gigabit switch for the Watchout network exclusivly, the other one was used with a different gigabit switch for Dante. WO IPs were 192.168.x.y Dante IPs were 169.254.x.y (thats what they default to, its a feature not a missing DHCP). Subnet mask on both interfaces was class b or c / 255.255.0/255.0. So from a networking standpoint all WO traffic should have been routed to interface 1, and all Dante traffic should have been routed to interface 2. For some reason at the time (I didn't had the time to investigate further) as soon as Dante was activated the display computers would not play in sync any more and there were occasional dropouts in the communication. We then went back to a RME Fireface to playout the multichannel audio. As Dante is now more common in the industry and multi channel application happen day to day with WO I was wondering if there are any plans to extend the support of Dante networking? In this thread I already found a tool to assign Mono or Stereo files to specific output tracks, which is a good starting point to make the handling of multi channel audio files in the WO interface much easier ( http://forum.dataton.com/topic/2-is-there-a-possibility-of-multi-tracking-and-outputting-within-the-watchout/ ). Has anybody tested the Virtual sound card with WO and found similar issues? Wouldn't it be great if one could from within Watchout assign input and outputs channel to and from Dante? More about Virtual sound card: http://www.audinate.com/index.php?option=com_content&view=article&id=235 Thanks Tobi

Hi Jonas, thanks for your reply. If the selected sync master ("tic box") is selected, how is this sync information then transfered to the other display PCs? I was under the impression that TCP/UDP connections are not accurate enough (or software in general not able) to create phase sync (talking multiple HD hard edge LED walls here) between different display computers on the graphics card / hardware level. If you write that you have to define a master within the software sync (TCP / UDP) world of WO ("tic box") and at the same time the local display computers running local DirectX are NOT able to phase lock to the local (synced) graphics card, does this mean WO is somehow transferring phase sync information over the TCP/UDP-WO-network? And if not, and if DirectX is not able to phase / frame lock to a local graphics card, how is the sync information reaching the display computers (or, to be more specific, the local DirectX instance)? If all display computers somehow get some information from their local graphics card / or S400? to create phase / frame lock DirectX output why do I need Watchout Master to do anything ("tic box") except telling each local instance of Watchout Display of look at their local graphics card / S400 and create a phase / frame lock DirectX output? If DirectX cannot 100% phase / frame lock to a graphics card / S400 why is there is (apparently working) sync option in the first place? Please help me understand Thanks Tobi

Thanks. But what is the sync master doing / what does the tic box do? Why is it needed to output phase sync video? Doesn't DirectX lock to whatever the graphics cards generates (frame sync wise) which is locked to the S400? In the AMD control panel the S400 syncs to external tri level (on all display computers). If somebody could clarify that would be great!

has anybody tested the setup the thread starter described with WO 5.5?

Hi, I was wondering if there is any way or status window where I can see that a display computer is actually using the sync settings from the S400. In what way it the "heartbeat" from Watchout transmitted over TCP/IP (synching playback across WO display computers ) relavant to be in sync with the S400? What happens "behind the scenes" when I set the new tic box in Display > Advanced > Synchronisation? If I would have more than one display computer EACH equipped with a S400 do I then still need to set the tic box? My requirement is "only" to have displays computers that are in phase sync to each other NOT to sync to an external source. In my understanding the S400 makes the graphics card generate its own 50Hz in phase sync to the S400 sync. If that happens on all display computers then WO / DirectX also should display their 50Hz in phase sync with the S400. So then why do I still need the new tic box? Or what do I miss? Thanks Tobi

Hi, a client asks for quality reasons to NOT run H.264 or MPEG2. (mainly banding in comparison when using uncompressed tif with DVS machines in the past..). So I'm looking for an 8bit (visual) lossless codec for stable and synchronous Watchout Playback (4+ hard edge outputs, 1920x1080p/50 each). I have read here that .mp4 actually is played back by an internal Watchout-Decoder, while most of the others are played back through Quicktime-Decoder. I would like to use a codec that is similar stable / decoder provided by Watchout. Is that possible? If not: are there any best known practices for ProRes (in .mov-Container) playback? Thanks for all input Tobi

Dear community, can anyone recommend (affordable) software that encodes m2v and maybe wmv in 1920x1080p/50/60 1366x768p/50/60 (1366 / 16 = no integer) etc.? Most of the tools I use and post production houses use cannot encode the above (including TMPGEnc and Telestream Episode 6 Pro). Episode 5 does the above but since the wise people at Telestream changed their MPEG2 encoder between 5 and 6 its no longer possible. Other tools you have used / can recommend? Thanks, Tobi