hat
Enthusiast
- Joined
- Nov 20, 2006
- Messages
- 21,731 (3.41/day)
- Location
- Ohio
System Name | Starlifter :: Dragonfly |
---|---|
Processor | i7 2600k 4.4GHz :: i5 10400 |
Motherboard | ASUS P8P67 Pro :: ASUS Prime H570-Plus |
Cooling | Cryorig M9 :: Stock |
Memory | 4x4GB DDR3 2133 :: 2x8GB DDR4 2400 |
Video Card(s) | PNY GTX1070 :: Integrated UHD 630 |
Storage | Crucial MX500 1TB, 2x1TB Seagate RAID 0 :: Mushkin Enhanced 60GB SSD, 3x4TB Seagate HDD RAID5 |
Display(s) | Onn 165hz 1080p :: Acer 1080p |
Case | Antec SOHO 1030B :: Old White Full Tower |
Audio Device(s) | Creative X-Fi Titanium Fatal1ty Pro - Bose Companion 2 Series III :: None |
Power Supply | FSP Hydro GE 550w :: EVGA Supernova 550 |
Software | Windows 10 Pro - Plex Server on Dragonfly |
Benchmark Scores | >9000 |
1. No, audiodg does nothing more than signal processing using the CPU (something Creative X-Fi cards use less of, anyway).
2. It's perfectly normal for drivers from any vendor to insert 3rd party code into audiodg process (that's why audiodg was designed to run as a separate process in the first place, and not some internal kernel module). In Entertainment mode, the X-Fi driver offloads CMSS3D and Crystalizer processing to it.
3. Yes, it's an absolutely trivial issue, close to being a non-issue for a vast majority of users, because it doesn't affect stability or security, further, doesn't affect the quality of the product.
1. "The second reason for using a separate process for the audio engine is DRM. The DRM system in Vista requires that the audio samples be processed in a protected process, and (for a number of technical reasons that are too obscure to go into) it's not possible for a svchost hosted service to run in a protected process."
2. That may be, but my points are that:
a. It doesn't have to cause a huge memory leak that eventually kills performance
b. These features worked fine in XP, which did not have audiodg...
3. Again, I hardly consider an issue trivial when features that I paid $150 for don't work properly. In fact, it's the complete opposite of trivial.
What I'm saying is that the memory leaks don't affect the performance or quality of audio, or any of its features, and that something like memory leaks with audiodg does not affect that in any significant way.
What world do you come from? Where you undergo surgery for sneezing? Where you spin a chaingun at your neighbour's dog for peeing on your mailbox? Where something as trivial as audiodg memory leak deters you from buying X-Fi, especially when you're getting it for $50? Then it's your world that's bizarro, mine is fine.
The memory leaks don't affect performance? Since when does a memory leak not affect performance? When I have 4GB RAM, and audiodg is indefinately eating memory, how is it not a performance issue when it hits around 2GB, leaving 2GB for the game, the OS, and god knows what other background programs to operate on? How does audiodg not affect features when you yourself said that developers use it specifically to build thier audio feaures into, and when memory leaks happen when these features are being used, how does that not affect the performance or the features?
Again, a memory leak that occurs when I use features that I expect to be able to use with my $150 sound card (or in this case, $50, but not really because there's the $70 mail in rebate that takes months to get), is not a trivial issue, it's a huge issue. As I said before, I wouldn't use a Creative X-Fi if someone gave it to me for free, because I wouldn't want the memory leak issue.