I am trying to setup the server to start encoding as soon as the server boots. I have followed the instructions described at: http://help.adobe.com/en_US/FlashMediaLiveEncoder/3.0/Using/WS5b3ccc51 6d4fbf351e63e3d11c104babd5-7ff6.html
I successfully "registered" it as described in the link above. When I start the FMELauncher.exe, I get the errors:
ed Apr 13 2011 15:06:35 : Selected video input device: Osprey-230 Video Device 1
Wed Apr 13 2011 15:06:35 : Selected audio input device: Unbalanced 1 (Osprey-2X0)
Wed Apr 13 2011 15:06:35 : Failed with error 80040154:CoCreateInstance(CLSID_NullRenderer, 0, (CLSCTX_INPROC_SERVER|CLSCTX_INPROC_HANDLER), IID_IBaseFilter, pFilterVideoRenderer.ppv())
Wed Apr 13 2011 15:06:35 : Failed with error ffffff97:SetupInputVideoPreview(pFilter, pguidCategory)
Wed Apr 13 2011 15:06:35 : Failed with error ffffff97:SetupVideoPreview(pFilterSource)
Wed Apr 13 2011 15:06:35 : Error: Problem with video capture device. Please verify that the video capture device is working correctly and is not already in use.
Wed Apr 13 2011 15:06:35 : Failed with error 80040154:CoCreateInstance(CLSID_NullRenderer, 0, (CLSCTX_INPROC_SERVER|CLSCTX_INPROC_HANDLER), IID_IBaseFilter, pFilterRenderer.ppv())
Wed Apr 13 2011 15:06:35 : Error: Problem with audio capture device. Please verify that the audio capture device is working correctly and is not already in use.
Wed Apr 13 2011 15:06:35 : Closing Application.
When I start up the GUI, using the same XML settings and the same user, it works just fine. This machine is a Windows 2008 R2 64 bit machine.
I have tried:
making this user an admin
changing "compatibility mode" on the executable
different users
different XML files
changing permissions on where the XML file and Log files exist.
Any ideas?
--Bryan
Hey Bryan. I've worked with Osprey cards for eons. Make sure you have the proper drivers for the 230 card. You may have to download the "beta" drivers from Viewcast. Lastly...if the drivers dont load properly, or are being "shared" with other apps on your server.....you will be SOL. I'd also clear out the default.xml in the FLME script!
If you do the same sort of setup on a 32bit will it work?
Lastly...try FLME3.1
Good Luck
KC
Thank for the ideas, I guess I should have specified more info about that. I am running the latest FMLE, (just downloaded it last week), along with the latest osprey drivers (again, downloaded last week). Nothing else runs on this box besides FLME, and the default.xml has been changed too.
It just doesn't make any sense to me that through the GUI it is fine, but running the command line version it says it cannot find the osprey card....
I will test my other setup, running 32bit... thanks for the idea....
Thanks though...
-_Bryan
North America
Europe, Middle East and Africa
Asia Pacific