[vlc-devel] Re: DirectShow Input Problem on Current Builds of VLC

[Mark Moriarty]

Thank you for the  quick response.

I have 2004 drivers for the card.  There is one new update, just released,
although I do not believe it addresses the items you discuss.

In the 5 March software version the dshow code was able to open the Osprey's
configuration applet without difficulty, so it seems the Osprey does have a
Windows device manager app that is accessible.  It's a more complex applet
than, say, typical Webcams -- the Osprey has many capabilities, many output
resolutions, at least 7 color space options, etc.  I normally run the Osprey
using defaults -- 640x480 resolution, composite input, but had gone through
VLC's "device properties" checkbox to adjust things, see how they looked.

If you could add the leniency back in, it would be appreciated.  The card
really does work quite well with VLC (or did), and it looks like the
framegrabber market area is relatively small -- there are companies with TV
tuners, there are companies with very expensive frame grabbers, but
Viewcast's Osprey line is one of the feww, it appears, that addresses high
resolution at a reasonable cost. 

Thsnkd sgsin.

Mark

-----Original Message-----
From: vlc-devel-bounce at videolan.org [mailto:vlc-devel-bounce at videolan.org]
On Behalf Of Damien Fouilleul
Sent: Wednesday, June 16, 2004 4:53 AM
To: vlc-devel at videolan.org
Subject: [vlc-devel] Re: DirectShow Input Problem on Current Builds of VLC

Mark,

i've posted an answer to your  forum query under
http://forum.videolan.org/viewtopic.php?p=9477#9477
which follows:

I've looked at your debug output, and it shows that your video card driver
fails to return any supported MEDIA_TYPES (resolution & chroma). 
I've modified the dhow plug-in to use those media types, in order to
optimize the capture. unfortunately, by doing so I removed the leniency of
the dshow plugin toward badly behaved driver such as yours, hence explaining
the failure.

first of all I would suggest that you try to upgrade your capture card
driver to a WDM version, if possible. Secondly, I will try to allow the lack
of supported media types if user explicitly specifies the resolution and
chroma.

Damien

Mark Moriarty wrote:

>First, apologies if this is the wrong mailing list, as opposed to VLC 
>-- I'm not sure which one it would fall under.
>Windows 2000 (and WinXP), fully patched, directX 9.0B.
>The pre-release 0.7.2 Windows files through at least March worked fine 
>with the Osprey 210 framegrabber.  The release package, however, does not.
>I poked at the source code and it looks like the late March builds were 
>using access\dshow files from 5 March.  There were then updates to the 
>dshow files (dshow and filter) in April and again in May.
>
>When I do a build of the current subversion (pre-release 0.7.3) with 
>the early April dshow files, it looks like VLC is at least getting 
>somewhere talking to the Osprey, to the extent that it hits several 
>Capture functions; it does end up exiting, not able to display the 
>video.  The later, 5 May versions of the dshow files don't get that far 
>-- they immediately generate a message stating that the osprey dll is
something that cannot be decoded.
>
>The Osprey is from Viewcast -- as far as I can tell it really does have 
>good DirectX compatibility, was  recommended to me by several 
>commercial video vendors as a good card with 640x480 resolution.
>
>I posted detailed Message logs in the VLC area of the forum -- a thread 
>with Directshow and Osprey in the title.  It is at:
>forum.videolan.org/viewtopic.php?t=3046&highlight=osprey+directshow
>
>I wouldn't mind reverting back to the 5 March version of dshow files, 
>if that gets me to a working DirectShow input again.  Unfortunately, it 
>looks like there was other code change occurring -- If I drop the 5 
>March files into a current release there is an error in the compile 
>(the error is shown in the forum thread).  It may just mean having to 
>adjust a variable type declaration in the 5 March dshow files, I'm not
sure.
>
>It looks like there's at least one other Osprey person stuck, and 
>another person is also reporting dshow-related issues with the 
>post-0.7.1 VLC builds, someone using a non-Osprey grabber.
>
>Thoughts/comments appreciated.
>
>Mark
> 
>
>  
>

--
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/ To
unsubscribe, please read http://developers.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>

-- 
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>