Hi guys,
Recently I've had to replace my sound card due to a water cooling incident...I've since switched to air cooling. Anyways, I had a Sound Blaster Audigy 4 (I think), which stopped working. I replaced it with an HT Omega Striker 7.1. Since then, I've had issues with the Midi (actually, the synth) volume control. I have the wave volume set just right so i can watch movies in VLC and listen to music in winamp, with my amp set at the right level. In my winamp playlist there are a few midi files, and whenever one of those midi files plays (I have it set on random), the synth volume jumps to almost max. I can then turn it down to a reasonable level, but each time another midi song plays, it resets itself to that high volume level. This is really annoying because most of the time it happens at night when I'm supposed to be asleep (parents....), and every time it does happens, the music overdrives my amp and sounds really bad. Has anybody else had this problem? I looked through the HT Omega driver software and couldn't find anything that might do it, and spent 10 or 15 minutes looking through the registry and couldn't find anything. When I took out the Sound Blaster card, I uninstalled the drivers, so unless it left some garbage behind, I don't see how they could be fighting. Here's some info on my system:
CPU: Intel Pentium D 830
Mobo: Intel D955XBK
Video Card: eVGA 8800GTS 640MB
Sound Card: HT Omega Striker 7.1 Version 1.0.55.00
--Audio chip: CMI8770
--Driver Version: 5.12.8.1509 (the one that came on the CD)
--DirectX Version: 9.0c
OS: Windows XP Pro, SP2
That should be all the relavent information...It's in the middle PCI slot (the top one is dead due to previously mentioned water cooling incident), and I put a heatsink on the audio chip, because I had an extra one and heatsinks are awesome. I made sure it wasn't touching (shorting) anything important though.
In the process of writing this, I said oh, duh, I should update the drivers. So I went to the ht omega site and downloaded an update, installed it, rebooted, and the problem is still there. The new driver version is: 5.12.8.1730.
Any thoughts/ideas?
Thanks,
Eric
hardware
prices 
