WindowsX
Member of the Trade: Fidelizer Audio
- Joined
- Apr 27, 2007
- Posts
- 1,962
- Likes
- 364
If you are having problems which that software is trying to solve (AFAICT just changes processes scheduling policies), these are pretty clear, as they manifest with audio skipping. Which is audible (and annoying) w/out any effort.
But that's a big if, as with modern many-cores-and-even-more-many-hyperthreads systems, it takes quite a bit of system stress for the audio feeding app, to miss scheduling windows so big to let the audio device starving for data.
I have personally not had audio skipping since I don't even remember, and I stress my system quite a bit with big/parallel software builds.
IOW, I won't go as far as claiming snake oil, but you can be almost certain you can do without it.
It's not about process scheduling policies in Fidelizer. It makes Windows to actually make use of NT6 multimedia platform. Since Windows Vista, there's multimedia class scheduler service, runtime service, and other related API features to handle resource scheduling between audio/video/network better for system and I/O performance.
These features won't touch individual process. If you use Fidelizer with default consumer level, all processes will be left untouched and multimedia platform in Windows itself will be optimized. I recommend everyone to at least trying this software before passing judgement. Many claimed it'll make no difference without trying. They don't understand the nature of software and mistook some of additional features as core features instead.
Regards,
Keetakawee