Re: Why dont capture devices save their settings?
- From: Tim Roberts <timr@xxxxxxxxx>
- Date: Fri, 29 Dec 2006 20:39:46 -0800
"The March Hare [MVP]" <phil@xxxxxxxxx> wrote:
On 26 Dec 2006 08:48:05 -0800, rep_movsd wrote:
Is there any valid reason why settings are lost or is it just sloppy
coding?
To add to what Chris wrote, there are two basic reasons you see this:
- MS added capture later in the game to dshow; they did not provide a
channel for input on the design of this feature and did not realize how
important it was so that there was a mandatory interface for persisting the
capture device properties (G.: correct me if I'm wrong here)
The capture driver models were designed asynchronously to (and, in several
cases, well before) DirectShow. Driver writers were too busy worrying
about pulling bits from their cameras without dropping frames; the niceties
of user interface design fell below the line.
When I was doing camera drivers for Intel, which was as early as 1998, they
always insisted that settings persist in the registry.
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
.
- Follow-Ups:
- Re: Why dont capture devices save their settings?
- From: The March Hare [MVP]
- Re: Why dont capture devices save their settings?
- References:
- Why dont capture devices save their settings?
- From: rep_movsd
- Re: Why dont capture devices save their settings?
- From: The March Hare [MVP]
- Why dont capture devices save their settings?
- Prev by Date: Re: WMI / ETW event tracing for DirectShow - Is it real?
- Next by Date: Re: CPU usage reduction
- Previous by thread: Re: Why dont capture devices save their settings?
- Next by thread: Re: Why dont capture devices save their settings?
- Index(es):
Relevant Pages
|
