Posted: October 10 2003 at 12:43pm | IP Logged

Well bless you for revealing the bug as being the Osprey 220 (In your case it was the Osprey 210........)  I have the exact same symptom with a hot new system I just built.  Damn the Osprey!

My new system was to be a top of the line video capture machine for a health care consulting firm.  It is an ATX dual cpu board by Gigabyte  (GA-7DPXDW-P ).  It sports 2 Athlon MP 2800+ cpus, (200/266 FSB and DDR speeds),  The AMD-760MPX chipset with the AMD 762 NorthBridge chipset with memory controller (also supports 200/266Mhz FSB)    and the AMD-768 Southbridge  PCI 66Mhz/32bit AND 33Mhz/32 bit interfaces  AND is PCI 2.2 compliant..   I have 2 512MB DDR DIMMs  (PC2100  modules) for a toal of 1 gig ram..

I also striped two 120 gig drives to double the transfer rate for capturing video (promis raid controller 20276 is built onto the motherboard)

Even with all this horsepower, the Osprey's captured video had glitches in it (no matter how poor the resolution or small the frame rate  till the glithes stay.ed)

DISABLING THE OSPREYS AUDIO DEVICE VIA THE DEVICE MANAGER IN CONTROL PANEL SOLVED THE GLITCHES IN THE VIDEO CAPTURE FILES.

Viewcast claimed it was the AMD-768.    BALONEY.   Here is there little blurb claiming video trash in the captured files are SUPPOSEDLY not their fault.

Question--I am trying to capture video with my Osprey card and I am seeing glitches/artifacts in the captured video files. What could be causing this ?

Answer--We have found that certain motherboards that utilize the AMD-768 peripheral bus controller do not provide adequate bandwidth requirements to allow the Osprey cards to capture successfully (one motherboard reported to use the AMD-768 controller is the TYAN Tiger MPX (S2466N-4M). We do not have a resolution for this problem and strongly recommend using a motherboard with a different Peripheral bus controller. If you would like to use an AMD based board we would recommend utilizing the AMD760MP chipset platform, which utilizes the AMD-766 peripheral bus controller.   (and Award Bios  NOT the Phoenix!)

HEY, you cannot tell me that adding a few kiloHerz of sound capture bandwidth onto the bus can crater a pci capture process!  This is obivously a problem with the drivers of the Osprey 220  AND or the hardware PCI interface on the Osprey Card..  Come on ViewCast.....get it together!    It seems like the faster the machine, the crappier the Osprey card performs!

I have just a couple of days to solve this problem with the Osprey, after that it's punt all ViewCast products from now till the end of time.

dr

Posted: October 10 2003 at 1:59pm | IP Logged

Catch-22   found out that if you disable the audio on the Osprey 220 card  (in order to stop the video capture file corruption and glitches in the video) the Osprey Capture & Encoding Manager  will not run.  It has to see BOTH the audio and video portions of the Osprey card.    So it is back to looking for work arounds again.  somebody help?

dr

Posted: October 12 2003 at 9:45pm | IP Logged

David, I'm sorry to hear of the trouble you're having, but yes, this is in fact due to the motherboard that is in use here, and not related to the Osprey capture card hardware or drivers. 

After researching this with the engineers at AMD it was determined that due to the fact that the the 32bit/33MHz PCI bus was connected to the 64bit 33/66 bus, the bandwidth on the 32/33 bus was limited to 25MB/s.  See the user's experience from this post http://www.viewcast.com/vcforum/display_topic_threads.asp?ForumID=13&TopicID=156 for more on this.

Currently, the known workarounds for this motherboard are:
a. use another device, such as the system soundcard, for audio recording - there is no need to disable the Osprey's audio, just change the default recording device in the Windows control panel to the soundcard and be sure the application is using that (SimulStream users will, unfortunately, only be able to use it for video).
b. use a color format with less data.  For example, if you're using RGB24 (24 bits data per pixel, try implementing 4:2:2 packed, which is roughly half, YUV9 is 9 bits.
c. implement a different AMD motherboard, such as the  AMD board using the Guinness (MP) chipset

Let me know if you have any questions or if I can help out in any way,

-Steve

Posted: October 15 2003 at 8:12am | IP Logged

Hi David and Steven,

I am having the same problem David's having but with an Osprey 500 DV Pro. After reading this topic I tried capturing without audio and the glitches disappeared instantly. So Steven's argument for being a AMD-chipset problem is not correct. Here's the setup:

SuperMicro X5DPA-TGM iE7501 533F (all Intel chipsets)
Dual Intel Xeon 3 Ghz 512 Kb
1 Gb DDR PC2100
Osprey 500 DV Pro
Windows XP Pro, Windows Media Encoder 9

We have 3 of these systems, which all show the same glitches. Also tried different breakoutboxes and different inputtypes but no differences.
If tried every possible option available as far as I know. The card uses IRQ 19, which was also used by one of the onboard USB controllers, but turning that on or off in the system's bios did not make any difference

I hope Osprey will provide a solution for this soon. Telling us to use onboard audio input is ofcourse not an option(it's not there...), you don't buy a 2000 euro capturecard with XLR input which you cannot use....

Posted: May 13 2004 at 10:42pm | IP Logged

I just posted a request for help for a very similar problem on the Osprey 210 cards. I am in the middle of launching a USA wide 1000 channel video collection system using Osprey 210s. We have optimized the box the operating system and the capture card.

Recently in pre deployment testing we found disgusting artifacts in compressed video stream on multistream capture on our deployment boxes. After writing all the code and testing I thought I was home free and did not see this one coming. OUCH!!

The VideoBank  

Posted: May 16 2004 at 10:24am | IP Logged

I agree with DavidRedwine, it sounds not just mb's problem,I have expierence on 3 different platfroms,

1. Tyan Tiger MPX(S2466-4M). That's a disppointed expierence. As your guys know, two years ago, tiger mpx is the best price/performance mb in the world. Unforturnly, even with only one osprey 200 card, the video will glitch seriously. That was a 512MB, 2 Athlon MP 1800+ system. btw, I am the person who first report that mpx cannot compatible w/ osprey 200

2. after I cannot get help from Viewcast( first posted on April 2002, but cannot get any answer in half a year), I cannot wait. I think it must be amd's problem. So I decide I should stick w/ Intel, I purchase 2 SuperMicro p3tdde( dual P3 mb VIA Apollo Pro 266T Chipset,VT8653T + VT8233). I install 3 even 4 osprey 200s. It's great. Everything is ok.

3.This april I decide I should upgrade my system because one of the system is out of running. After my first poor amd expierence, I decide I should stick w/ Intel. Because my budget very limit, I purchase 3 ASUS PC-DL Dexlue(maybe the cheapest Dual Xeon P4 mb in the world, base on intel 875P chipset). But this time, I am totally disappointed. a system w/ 2 Xeon 2.4GHz, 2GB RAM, but the video glitch and the audio poor. The upgrade just cost me a lot of money ,but what I get are much more worse quality and unacceptible internet streams. w/ more osprey 200/210 installed, more WMEs live encoding(each WME w/ 1 osprey 200/210), the video glitch more seriously and the audio more poor. I have try many methods, after install and uninstall 2.2.0/2.2.2/3.0.0/3.1.0RC2, disable bios options, I cannot get my system works perfect. I am tire on doing compatible test for viewcast. Will this time intel's i875p take respensible for this? As I know i875's south birdge, i82801ER(ICH5R) provide enough bandwidth for PCI BUS(133MB/s) much more than MPX's 25MB/s(as you viewcast guys said).

I have 12 osprey cards, they work perfectly on my dual P3 platfrom. They should work perfectly on my new dual Xeon platfrom. I hope viewcast will solve the problem quickly.

Posted: May 16 2004 at 1:55pm | IP Logged

I have just take a test on my dual xeon platform. I think it will prove that osprey 200/210's driver or sth has problem w/ ASUS PC-DL,

open two WMEs 9 capture from two osprey 210 cards and doing a live internet broadcast, preview from WME video panel and WMP

1. video from osprey video device and AUDIO FROM OSPREY AUDIO DEVICE,THE VIDEO WILL *GLITCHES*

2. video from osprey video device and AUDIO FROM LINE-IN OR MICROPHONE, THE VIDEO WILL *NOT GLITCHES*