Thad E Ginathom
Well-Known Member
Thanks Sid... do you have a link to that review? [EDIT: got it
] I'm not sure that I'm up to it, but I'd like to have a go at understanding it in context. Doesn't a USB cable have two ends? And isn't there a USB Interface at both of them? Hope to read the whole article for better information.
If electrical isolation is your aim, you can have that easily --- but the optical interface is currently unfashionable with audiophiles.
There used to be a document wandering around the internet (not sure that it ever had a continuing permanent link. don't know why) that described customising an XP (or possibly even earlier) system for audio. I have no idea (no experience) how much Windows services (and the management interface) have changed in the, err, 3[?] versions since XP, but it might still be a good starting point. Document changes carefully and make only a very few at a time. There are weird and unobvious dependencies, and having to back out changes is perfectly possible, or even re-installation if one makes the system unbootable.
Fiddling with process priorities and hardware is, obviously, somewhat esoteric, and mostly beyond the means of most of us.
Wouldn't it be nice (well, for Windows users...) to have a tick-list disable the following services etc etc interface to a program to handle a subset of known-to-besafe-without services. They could be grouped into elementary/mid/advanced/dodgy groups.
Not an idea that looks like it would appeal to the Fidelizer author, it seems.
Anyway, word from the opposite side of the Windows seems to be that MS audio handling has improved greatly in recent editions.
And we're all stuck with the fact that the PC is not a real-time machine...

If electrical isolation is your aim, you can have that easily --- but the optical interface is currently unfashionable with audiophiles.
It's not so much that I think that the guy might be up to anything dodgy (and no, in case anybody is asking, I don't analyse every program I install on my system!) but there is stuff there that I don't approve of.gobble said:It is good to be paranoid. From the audiogon forum
There used to be a document wandering around the internet (not sure that it ever had a continuing permanent link. don't know why) that described customising an XP (or possibly even earlier) system for audio. I have no idea (no experience) how much Windows services (and the management interface) have changed in the, err, 3[?] versions since XP, but it might still be a good starting point. Document changes carefully and make only a very few at a time. There are weird and unobvious dependencies, and having to back out changes is perfectly possible, or even re-installation if one makes the system unbootable.
Fiddling with process priorities and hardware is, obviously, somewhat esoteric, and mostly beyond the means of most of us.
Wouldn't it be nice (well, for Windows users...) to have a tick-list disable the following services etc etc interface to a program to handle a subset of known-to-besafe-without services. They could be grouped into elementary/mid/advanced/dodgy groups.
Not an idea that looks like it would appeal to the Fidelizer author, it seems.
Anyway, word from the opposite side of the Windows seems to be that MS audio handling has improved greatly in recent editions.
And we're all stuck with the fact that the PC is not a real-time machine...