I can't comment on performance issues that you experience, but as for
reported formats DX8 was known to ignore formats that capture driver reports
and use predefined set of its own formats. Basically there was a hardcoded
table with "good" formats in it. Anything out of this table that the capture
driver reported was ignored. If the driver did not support one of the
formats in the "good" table that was just too bad.

I don't know whether or not they fixed it in DX9, but from what you say it
sounds like they did. Finally!

-- Max.



"Andy Leafe" <Andy Leafe@discussions.microsoft.com> wrote in message
news:5622A85A-7BDF-4F89-8CDD-FEB8DBD8833E@microsoft.com...
transfers over a dedicated USB 2.0 High Speed interface.
per 125us)

dear max,
what is hardcode table and where can I find ??
thanks.

"Max Paklin" wrote:

The list of formats that is shown when you open the property page on the
output pin of your capture driver is what I referred to as "table".
What I said was that the list was hardcoded and capabilities reported by the
capture driver were not taken into account to build that list. This is from
my own experience, but it can be outdated (I discovered this 2-3 years ago).

-- Max.



"tiyayin" <tiyayin@discussions.microsoft.com> wrote in message
news:F252D615-07B6-49D2-B678-8FEFE7441725@microsoft.com...