Jump to content

Search the Community

Showing results for tags 'windows 7'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. Dear Dataton User community, we are very happy to announce that WATCHOUT 6.2 now is officially available for download from the web: https://www.dataton.com/ News & Views / Blog In addition, our blog - News & Views – has hit the streets! The first blog posts are available, with information about the technology used in the new features of WATCHOUT. http://newsandviews.dataton.com/ Best regards, The Dataton team!
  2. So I have had my Blackmagic Intensity Pro HDMI capture cards (3) for over a year now, and noticing that when I plug a DVI input into the machine while in Watchout, the machine freezes up and restarts! I have 3 Display machines, same spec, all Windows 7 64bit. When I run a backup system, and split the signal from 1 source (Screenpro 2/Macbook Pro) through a Kramer VM-4HDCP or simple HDMI splitter, the machines both have the same issue and restart. Very annoying and embarrassing when watching the machines boot up across a wide screen. Has anyone else had this issue? What am I doing wrong? If I start machines with solid inout signal plugged in they seem very happy!
  3. Hey there. We have recently purchased the ATI Radeon HD6990 with 4x Mini Display Ports and 1x Dual Link DVI Output. We have also purchased the Black Magic Decklink SDI Capture Card for an upcoming gig. As we have just got it all working together we thought we'd put it to the test, only to discover, that the input from the capture card doesn't work over the blended areas, it simply appears blank. Please let us know if there is something we are doing incorrectly so that we can solve this issue. Our proof of this issue is that after going to File/Preferences/Edge Blend and taking the blend out all together, immediately the full capture spans across all the displays. This is something we are hoping to rectify else we will need to pull in the likes of an encore or similar and budget of course doesn't allow. So if you have any ideas, please let us know by responding in this post. Many thanks.
  4. I'm not sure if any one else using multi-ouputs in v5 has come across this, but I'm trying to get my head around it... My machines all have ATI Firepro V7900 cards for multi-output use. For those who are not familiar with these cards, they have 4x DP physical ports, arranged very nicely across a single PCI plane. Looking at the back of the card, my logic thinks.... hmmmm... Top --> Bottom must either equal outputs 1 --> 4 or 4 --> 1. However, my latest experiences seem to result in some (in my humble opinion) illogic from Microsoft, when assigning IDs to connected displays. Call me crazy, but it seems like Windows 7 'remembers' certain combinations of connected displays, and assigns IDs based on 'remembered' EDID info of those given displays for different combinations. Furthermore, I cannot figure out how Windows 7 determines these assignments of IDs, when it determines and 'remembers' and why it refuses to follow a logical, sequential order. As I've come across these experiences, I have learned to NOT fight the illogic and just take what Windows gives me. Lucky for us, we are able to sort it all out in the WATCHOUT environment. None-the-less, it is very annoying to anal-retentive, engineer, propeller head types like me. So my question to the WO community? Does any one know any clever tricks or have some further insight on how to force Windows to assign IDs according to their physical backplane order? If so.... perhaps, I can take a P-touch labeler to my GFX cards, and be free from Microsoft trying to be smarter than me JJ
  • Create New...