Microsoft knows exactly what the solution is:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dx8_c/direc
tx_cpp/htm/smartteefilter.asp
Microsoft routinely uses the "smart tee filter" concept in video capture
applications, e.g. amcap.exe, wmcap.exe, etc.
Yet for some reason, Microsoft apparently refuses to fix the problem.
Regards,
Joe
Cheers,
John.
I don't think I have it backwards. If I were developing software, I'd want
it to be compatable with as much hardware as possible.
Ati should have built preview into their
> board
> as per directshow specs.
If it is a "requirement" of "directshow specs", then how come Microsoft uses
smart tee filters in their other video capture applications?
Design for a "wintel" system, then make it "wintel"
compatible.
"John Kaliski" <j...@NOSPAM.com> wrote in message
news:rteM8.26236$LC3.2...@bgtnsc04-news.ops.worldnet.att.net...
No, they should support hardware designed for the PC platform - in a similar
way to the software they wrote for the Xbox that handles the Xbox hardware.
Cheers,
John.
"John Kaliski" <j...@NOSPAM.com> wrote in message
news:mOhM8.29414$UT.20...@bgtnsc05-news.ops.worldnet.att.net...
Moreover, the fact is that ATI and other manufacturers were building
essentially the same type of video capture cards *before* Microsoft
introduced Directshow. This is probably why the Microsoft Directshow SDK
contains built in, standard, "filtergraphs", among which is the "smart tee
filter"; the usage of which is well documented by Microsoft and is used in
most Microsoft capture applications (with the notable exception of WME).
Lastly, even if ATI is "wrong" in apparently not directly supporting
preview, how is it that this should cause an application such as WME not to
work at all, rather than, say, just not having preview?
"Nobody_of_Consequence" <non...@hotmail.com> wrote in message
news:GgwM8.104561$4i.99...@bin2.nnrp.aus1.giganews.com...
The implementation of DirectShow is hardly simple to support (from an
application programming point of view), and Microsoft has definitely
dropped the ball in terms of standardization, and forcing hardware
manufacturers to comply with those standards. Let's also not forget
that digital video camcorders are governed by a completely different
spec that many times does not have a one-to-one correlation with
Microsoft's idea of video capture.
NONE of the example programs that ship with the DirectX SDK support the
ATI card, but they are about to release a knowledgebase article
concerning support for those types of capture devices.
--
=========================================================
DeMONS/1 for Nascar Racing 3 & Nascar Legends
http://www.paddedwall.org/demons
DeMONS/2 for Nascar Racing 4 and 2002 Season (in development)
http://www.paddedwall.org/demons2
RASCAR Roster
http://www.paddedwall.org/rascar
Redneck Techno-Biker & "programming deity"
http://www.paddedwall.org/john
Barbarian Diecast Collector (460+ cars and counting)
http://www.paddedwall.org/diecast
If you want to send me email, go to the first URL shown
above & click "Send Me Mail" in the contents frame.
=========================================================
If the softrware can't detect the capture device, you don't have ANY
capability. Preview is available for all capture devices that support
WDM (and the ATI cards certainly do that), you just have to know how to
detect these devices and activate it.
I think that ATI also has a developer section on their web site that
describes exactly how to use their hardware from a programming point of
view.
Please see my original post. Windows Media Encoder 7.1 does detect the
capture device, the problem is, WME 7.1 says it's broke.
Preview is available for all capture devices that support
> WDM (and the ATI cards certainly do that), you just have to know how to
> detect these devices and activate it.
Please see my priginal post. Microsoft does know how to make it work. With
regard to WME 7.1, they just didn't do it for some reason.
<snip>
> >
> I recently had to write a WDM video capture module for our application,
> and the ATI Radeon All-In-Wonder card was a special case.
A "special case" in what sense?
We had to
> delevope a LOT of code for it. The problem is with both Micorosft AND
> ATI. ATI is committed to proividing support for legacy video
> connections (analog), but WDM/DirectShow are developed specifically for
> DIGITAL applications connected through Firewire or USB.
In this case, the problem apparently is that Microsoft simply isn't
following its own guidelines.
>
> The implementation of DirectShow is hardly simple to support (from an
> application programming point of view), and Microsoft has definitely
> dropped the ball in terms of standardization, and forcing hardware
> manufacturers to comply with those standards. Let's also not forget
> that digital video camcorders are governed by a completely different
> spec that many times does not have a one-to-one correlation with
> Microsoft's idea of video capture.
Huh?
>
> NONE of the example programs that ship with the DirectX SDK support the
> ATI card,
That's not correct. Look at amcap.exe.
but they are about to release a knowledgebase article
> concerning support for those types of capture devices.
Actually, the information is already in the MSDN library:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dx8_c/direc
tx_cpp/htm/videoportpins.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dx8_c/direc
tx_cpp/htm/smartteefilter.asp
Who says they aren't?
> Who defines pc platform? Duh, Intel and Microsoft.
Intel had a hand in it, definitely not Microsoft.
Cheers,
John.
NVidia's WDM drivers don't have these problems....why do ATI's?