Re: [Bdadev-discuss] Webpage and binary driver

[Robert S. <rob...@gm...>]

From: "John Adcock" <Jo...@ad...>
> I'd go with what's easier and having registry settings per country
> is easier, rmeber that at the very least we are going to need to
> check the physical location of the user as part od any install
> routine and at this point we can set up things like this quite
> easily. I agree that MS have some work to do here but I think we
> can easily bypass the problems.

I agree with that, but I think we should leave the driver in a "bugfix
ready" state, so that it works right as soon as Microsoft's components
start working right. IMHO having the workaround in the application makes it
easier to remove it, or even make it "autodetect" - e.g. have it check the
DirectX version and if it's still < 10.0 (or at whatever number Microsoft
finally get their act together) apply the workaround, otherwise not.

After all, the IDVBTLocator object in the IDVBTuneRequest already holds all
the DVB-T parameters. So all we'd implement as a workaround would be
something like:

Result = Tuner->put_TuneRequest(ourDVBTuneRequest);

if (Result == S_OK)
{
 if (DirectXVersion < FixedDirectXVersion)
 {
  // find IBDA_DigitalDemodulator node
  // query DVB-T parameters from TuneRequest's Locator
  // pass DVB-T parameters through IBDA_DigitalDemodulator methods
 };
};

Keep in mind that even with the fixed Microsoft components, the
"country-specific" DVB-T parameters would _still_ need to be determined and
put in place in the IDVBTLocator. So I'd say let's do the "right thing" in
all the places we can do it right now, and only implement workarounds for
missing MS BDA functionality where it's needed...

Regards,
--
Robert Schlabbach
e-mail: rob...@gm...
Berlin, Germany