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

Damien Fouilleul damien.fouilleul at laposte.net
Wed Jun 16 11:53:18 CEST 2004


i've posted an answer to your  forum query under 
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.


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:
>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.

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>

More information about the vlc-devel mailing list