Nugget
100+ Head-Fier
- Joined
- Aug 20, 2006
- Posts
- 205
- Likes
- 10
Check nfusion's post above re: copying a registry key. That'll solve your problem.
I had mine working fine until last night. Tried to play a song like normal, and it appeared to start playing but no output. So I closed iTunes, started foobar, and got an error message along the lines of "Expected 2 channels, got 18." I've got no idea what to make of that.
Might be related to a problem that I've been having with the X-Fi Mode Changer applet (the 3rd-party one, not Creative's junk). I can do anything with it except switch into Audio Creation mode. When I try that, it freezes completely and uses 100% of my CPU (more accurately, 50% of a dual-core chip). When I close the process in the task manager, I can't reopen it -- it drops right back into that frozen loop. Weirdly, though, it actually does succeed in activating Audio Creation mode at some point before it locks up. And weirder still, if I boot up in Audio Creation mode, it works fine, unless I switch to another mode and try to switch back again.
Well, that was thoroughly OT. Anyway, anybody knows what's wrong with my foobar install?
I had mine working fine until last night. Tried to play a song like normal, and it appeared to start playing but no output. So I closed iTunes, started foobar, and got an error message along the lines of "Expected 2 channels, got 18." I've got no idea what to make of that.
Might be related to a problem that I've been having with the X-Fi Mode Changer applet (the 3rd-party one, not Creative's junk). I can do anything with it except switch into Audio Creation mode. When I try that, it freezes completely and uses 100% of my CPU (more accurately, 50% of a dual-core chip). When I close the process in the task manager, I can't reopen it -- it drops right back into that frozen loop. Weirdly, though, it actually does succeed in activating Audio Creation mode at some point before it locks up. And weirder still, if I boot up in Audio Creation mode, it works fine, unless I switch to another mode and try to switch back again.
Well, that was thoroughly OT. Anyway, anybody knows what's wrong with my foobar install?