Jump to content


Photo

5.2 Does not see VisionRBG Capture while 5.1 consistently does.


  • Please log in to reply
22 replies to this topic

#1 Nate

Nate
  • Member
  • PipPip
  • 12 posts
  • LocationOMAHA, NEBRASKA

Posted 21 April 2012 - 05:30 PM

I recently upgraded my display computer to Watchout version 5.2 (from 5.1). I did this by uninstalling Watchout and Codemeter, restarting the system, and then installing 5.2.

Now, when I push a show originally made in 5.1 (but recently saved to a 5.2 version), I get an error reporting back from my display machine saying that it does not see a feed coming in from my VisionRGB capture card. I have opened the Vision software and can confirm that it is receiving a feed. I also confirmed that WatchPoint is still looking for the capture card on the same input as designated in the show. So, everything looks great on the settings side.

I have tried an uninstall which included deleting remnant files from my Watchout folder without success.
I have tried deleting the show files from the display computer and pushing a fresh copy without success.
I have created a new 5.2 show with only a capture input and still received no feed from the card.

Finally, I rolled back to 5.1 and pushed my original show. The capture comes up perfect like before. So, what's the story here guys? Does 5.2 require a Vision driver upgrade or setting change?

#2 Adela Kriland

Adela Kriland

     

  • Dataton Partner
  • PipPipPip
  • 41 posts
  • LocationSweden, Mexico

Posted 22 April 2012 - 09:00 PM

Just a try if I can give my opinion.

Can you install the Vision driver again after installing WO. Maybe this fixes the problem.

It worked for me with a Datapath RGB E2. Driver 6.1

Regards

Adela Kriland

#3 Nate

Nate
  • Member
  • PipPip
  • 12 posts
  • LocationOMAHA, NEBRASKA

Posted 23 April 2012 - 02:30 PM

Can you explain the process you used to reinstall the driver? Did you uninstall, reboot, and then reinstall the same version?

#4 ViPeRePiV

ViPeRePiV
  • Member
  • PipPip
  • 9 posts

Posted 23 April 2012 - 06:58 PM

I too ran into this same problem and had to go back to WO 5.1

My situation was even more interesting:
  • Setup WO 5.2
  • VisionRGB-E2s (driver

    v6.3.2) using VGA as the source (RGB - 720p chosen in WO)

  • Changed source to DVI (HDMI - 720p chosen in WO)
  • Get error "Runtime Error: Video Display Signal Not Found" or something close
  • Video can be seen using Vision software without issue
  • Tried uninstalling Vision drivers and shutdown/restart then re-install with no luck
  • Then uninstalled WO 5.2 and reverted to 5.1, all worked OK

-doug

#5 Nate

Nate
  • Member
  • PipPip
  • 12 posts
  • LocationOMAHA, NEBRASKA

Posted 24 April 2012 - 05:02 AM

Uninstalling, rebooting, and reinstalling the vision driver did not solve my problem. The issue persists.

#6 ViPeRePiV

ViPeRePiV
  • Member
  • PipPip
  • 9 posts

Posted 24 April 2012 - 10:49 PM

Nate,

Curious on what format video you are trying to use.

- VGA or DVI/HDMI or Component
- Resolution

Originally, my setup worked using a VGA input, but stopped when I chose HDMI (for DVI use)

Also, a correction on card used, I believe I was using a VisionRGB-E2 (not the newer "S" version)

Doug

#7 Jonas Dannert

Jonas Dannert
  • Administrator
  • 594 posts
  • LocationStockholm, Sweden

Posted 25 April 2012 - 08:46 AM

RGB should be chosen for DVI and VGA use.

/jonas

#8 Adela Kriland

Adela Kriland

     

  • Dataton Partner
  • PipPipPip
  • 41 posts
  • LocationSweden, Mexico

Posted 25 April 2012 - 09:14 AM

Hello,

Now I have tested, I am using WATCHOUT 5.2, Datapath driver 6.3.2. I am using capture with DVI and VGA. And no troubles at all.
BUT you have to be sure that there is a firmware upgrade in the Datapath Card when you install 6.3.2 if not you have to uninstall the driver and install it again from scratch.

Hope this helps.

And you can just change the connectors DVI to DVI to VGA hot and it takes it. Tested in 2 different computers.

Regards and have a nice day

Adela

#9 jfk

jfk

     

  • Moderator
  • 326 posts
  • LocationCincinnati, OH USA

Posted 25 April 2012 - 02:01 PM

Hello,
Now I have tested, I am using WATCHOUT 5.2, Datapath driver 6.3.2. I am using capture with DVI and VGA. And no troubles at all.
BUT you have to be sure that there is a firmware upgrade in the Datapath Card when you install 6.3.2 if not you have to uninstall the driver and install it again from scratch.

Hope this helps.

And you can just change the connectors DVI to DVI to VGA hot and it takes it. Tested in 2 different computers.
Regards and have a nice day
Adela


Thanks for sharing your results. :D

To clarify, the uninstall / reinstall forces a firmware upgrade of the card as part of the clean install of the driver?
Does the installation process notify you the firmware upgrade is performed?
Is there any way to query the DataPath hardware to determine it's firmware version?

Thanks again.

#10 Adela Kriland

Adela Kriland

     

  • Dataton Partner
  • PipPipPip
  • 41 posts
  • LocationSweden, Mexico

Posted 25 April 2012 - 04:44 PM

Hello,

When you install the new driver 6.3.2 it makes a firmware upgrade.
If this process is not done, because the card is not detected, then it does not work.
One way that I normally fix this is installing an older version meaning it downgrade the firmware sometimes and then install the new driver. And it goes through the process to upgrade the firmware.

I tried both the 6.1 that has work for me very good with version 5.1 and 5.2 WO. I have to accept that version 6.3.2 of the driver for Datapath seams faster, I combined with Decklink and Intensity with the new driver 9.5 which has much better performance reagarding the delay it had from activating the capture until you get the real picture.

Hope this helps.

Regards

Adela

#11 ViPeRePiV

ViPeRePiV
  • Member
  • PipPip
  • 9 posts

Posted 25 April 2012 - 11:51 PM

RGB should be chosen for DVI and VGA use.

/jonas


Is this something that has changed from WO 5.1 to 5.2?
I have been using HDMI as the choice for Datapath VisionRGB-E1s cards for a few months with no issues.


I can confirm with Windows 64-bit and WO 5.2 that choosing RGB works with a VisionRGB-E2 (6.3.2 drivers), whereas choosing HDMI gives the error "Runtime Error: Video Display Signal Not Found" or something close
Will try to install Windows 32-bit tomorrow to see if this behavior is the same.

-Doug

#12 Nate

Nate
  • Member
  • PipPip
  • 12 posts
  • LocationOMAHA, NEBRASKA

Posted 26 April 2012 - 02:12 AM

Further inspection has shown that, while my original input was set to "component" for DVI and worked normally, 5.2 seems to require it to be set to RGB. Changing it to RGB, updating the display computer, and firing the show yields a capture display. I am currently working without issue on 5.2 due to this change only.

#13 Mike Fahl

Mike Fahl

     

  • Moderator
  • 215 posts

Posted 26 April 2012 - 08:01 AM

We've identified a regression when using 5.2 with Datapath Vision RGB PRO (the very old, VGA-only card). This will be corrected in the next maintenance update. We apologize for the inconvenience.

As a temporary work-around, you may prefer to revert to 5.1 if your system relies on this capture card.

Mike

#14 Rogier Tuinte

Rogier Tuinte
  • Member
  • PipPipPip
  • 26 posts

Posted 08 May 2012 - 05:30 PM

Same problems for me with the VisionRGB-E2s card and Watchout version 5.2
Tried the above mentioned things as well.
Installed a new card in a Watchout system with version 5.2 already installed. (driver v6.3.2)
When I add a live feed cue on the timeline. (using DVI as the source (RGB - 720p50 chosen in WO) and go for the first time online while the timeline is at the live feed cue the capture is working. When i move the timeline to another point and then back to the live feed cue. The capture is not working...
Closing the display software and opening the vision software I can see the feed.
I've to restart the display machine completely to get the capture working again.
As long as the live cue is active everything is working. Changing opacity, etc, etc.

Kind regards,

Rogier

#15 Rogier Tuinte

Rogier Tuinte
  • Member
  • PipPipPip
  • 26 posts

Posted 08 May 2012 - 05:37 PM

Changed to version 5.1 and it seems it's working again...

#16 Fredrik Svahnberg

Fredrik Svahnberg
  • Administrator
  • 95 posts

Posted 08 May 2012 - 07:33 PM

Rogier, please install WATCHOUT (v5.2) and the Datapath card fresh on a different machine and try again. I suspect something in your installation process.

Best regards,
Fredrik S

#17 Rogier Tuinte

Rogier Tuinte
  • Member
  • PipPipPip
  • 26 posts

Posted 08 May 2012 - 09:37 PM

I'll try a fresh install on a different machine tomorrow.

I've to tell that in this machine I used the older Datapath Vision RGBPro card before.

But I removed the card and the drivers and related software from the system before installing the new Vision RGB-E2s card.

Maybe it's still a conflict with the old drivers?!


Something strange I noticed also is that beside the old RGBPro capture card I also removed a BMD SDI capture card. It looks like that the display software not recognise that the old cards are removed. The old entries are still listed in the "video in" menu in the display software..


Rogier


#18 Rogier Tuinte

Rogier Tuinte
  • Member
  • PipPipPip
  • 26 posts

Posted 09 May 2012 - 11:36 AM

Hello Fredrik,

Same problem after installing the card and Watchout 5.2 fresh on a different machine.

System specs:

MB: ASUS INT S1155 P8P67 EVO
CPU :Core i7 2600 BOX 3.40 8MB 1155 HDg
OS :Win 7 SP1 Home Prem 32b NL
PCIex16_1 slot: ATI EAH6950 DCII/2DI4S/2GD5
PCIex16_3 slot: Datapath VisionRGB-E2s

#19 Fredrik Svahnberg

Fredrik Svahnberg
  • Administrator
  • 95 posts

Posted 09 May 2012 - 12:02 PM

Have you tried a different source?

I would suggest a very normal computer with a DVI output set to 1024 x 768. Set the Signal Input in WATCHOUT to "RGB" and Video standard to "Other" - then type 1024 x 768 manually.

Best regards,
Fredrik S

#20 Rogier Tuinte

Rogier Tuinte
  • Member
  • PipPipPip
  • 26 posts

Posted 09 May 2012 - 02:27 PM

Thanks!
This solved the problem for me.
When I type the dimensions manually it works, instead of using a video standard preset.
Strange...