Osprey 560 in Windows 2000 and 2003
Printed From: ViewCast
Forum Name: General Development
Forum Discription: This is your chance to seize the floor and discuss each and every element of Osprey Video products
URL: http://forum.viewcast.com/forum_posts.asp?TID=323
Printed Date: March 27 2006 at 1:06am
Topic: Osprey 560 in Windows 2000 and 2003
Posted By: waldekev
Subject: Osprey 560 in Windows 2000 and 2003
Date Posted: March 15 2006 at 3:08am
|
I have 2 servers - 1 running Windows 2000 and the other running 2003. If i start Windows Media Encoder on the one running Win 2000 i get the Osprey card showing up in device options for both Audio and Video. On the 2003 server ( running the same version of Media Encoder) i only see the osprey card showing up in video - the audio setting only shows "Multichannel WAV source" ? I've installed the latest driver from the web site. Any ideas anyone ?
|
Replies:
Posted By: Mick
Date Posted: March 15 2006 at 9:37am
Hi waldekev.
The WinXP drivers worked great for me with an Osprey 500 which was intstalled on a machine that was running Windows 2003. FTP using anonymous login to:
ftp2.viewcast.com
and once connected, navigate down to:
/pub/OSP-500/winXP/latest/
and
download all of the files in that folder. The main installer is
Osprey-5002.2.1UpdateforXP.exe. Read the ReadME.txt file before
installing and then afterwards, read ReadME_Patch4.txt and
ReadME_Patch5.txt to see if you need to install the patches as well.
|
Posted By: taylorm_33
Date Posted: March 15 2006 at 11:19am
|
How are you accessing the encoder? As I remember, Win2003 does not allow access to audio devices using remote desktop. Just a thought.
|
Posted By: waldekev
Date Posted: March 15 2006 at 11:29am
|
I'm impressed ! Thats exactly it ... i've been using terminal server from my desk because our computer room is so cold. Many thanks
|
Posted By: Mick
Date Posted: March 16 2006 at 1:43am
Ha! Well done! I totally forgot abotu that. It has been over a year since I setup those 3 machines and I discovered that problem early on in the piece. As such, I had to remotely configure WME9 via VNC (TightVNC to be exact).
Edit: It wasn't around when I was using TightVNC, but you might find that UltraVNC is even better (or perhaps Remote Admin).
|
|