Talk:Sound Devices and Interfaces

From Audacity Wiki
Revision as of 15:01, 26 June 2009 by DOStradamus (talk | contribs) (Ramblings about WIndows XP MCE and Realtek driver support for it:; Media devices I've personally see fail to work with MCE and opinion of the root cause)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

RE: WIndows XP MCE and Realtek driver support for it:

Realtek neither states nor denies that their driver package that supports "XP", supports MCE. Given the otherwise complete support for every other version of Windows since Win2000, including the WIn7 Release Candidate, and the 64-bit versions, plus, personally seeing examples of "XP drivers" for media devices that are incompatible with MCE's quirks, I am of the opinion that the XP drivers not only work with MCE, but officially support it! Anyway, my hunch is that the special notice as to whether special note is given here as to whether a sound device works with MCE (and Audacity), is not beacuse "MCE has problems with certain media devices", but "MCE has problems with some USB functionality, and it mainly concerns things that media devices require".
So, I ask, "Is MCE support mainly an issue with USB devices?" If so, I'd venture to say that, in the absence of XP MCE being specifically mentioned one way or the other, whether a device works (or is officially supported to work) with 2003 Server, as the latter version of Windows has serious problems with certain types of USB devices. Those problems are still not corrected today, and here's my theory on why:

I figure that the Windows development trunk had a major chunk of its USB support code completely rewritten, to satisfy one of Vista's design goals (either the clock-cycle-stealing kernel DRM support foisted upon us, or an annoying, new, "security" feature like UAC,, I cynically figure), at the particular place in time that 2003 Server was to branch off. 2003 Server branched off with this all-new code, which most probably had a serious flaw or two in the basic idea of how it was to work. The trunk code was completely redone, but 2003 wound up stuck with it, as the kinds of devices for which problems existed (scanners, cameras, video capture) were not the kind of things MS chad much chance of being plugged into a "server", and therefore, the cost to rewrite all the parts of 2003 that needed to be. so that the new code on the truck could be plugged in, was not justified.

XP MCE must have been released before the errors were discovered. As XP SP2 began to back-port "good" things from 2003 into it, Microsoft hatched an albatross when they based "a tad too much of it" not on XP, but 2003, which included parts of "you-know-what".

MCE apparently had been "all but given away" to certain, large OEM customers of Microsoft's; the XP MCE box I figured out some of that OS' "dirty little secrets" on was not a Media Center PC, but a cheap-a$ Dell, that I reasoned had XP MCE on it solely for the reason that Dell got it for less than it would have had to pay for XP Home!

- Nick Karels
Santa Rosa, CA, USA