i've been quiet here, i guess. troubleshooting updates in the vlog, if you're so inclined.

a little while back, i noticed that cycling the mixer was creating a new driver entry in the registry and realized this had something to do with the problem. i think i've finally figured out that the way to get the mixer to load properly is to turn it on before the computer starts. this may be a conflict with the soundblaster, but i'm not sure.

it says to do this in the manual, but i've basically never done this. it would require restarting the computer every day. so, i may have to prepare myself for some wrong sounding mixes, and need to adjust them. basically, everything is up for analysis right now.

i still need to do some testing, but i'm convinced i'm very close and should be done in the next 24-48 hours.

if it's a conflict with the soundblaster, i can at least point out that i had the soundblaster disabled for a long time.

and, the issue is wdm-specific, so it wouldn't really be relevant to the mixing over asio. i think i'm probably safe from having to redo anything.

see, the thing is that i wasn't sure it was wdm-specific. i thought it was. if i knew it was, i wouldn't have bothered with all this, but i couldn't know it was until i figured it out, right?

i think it's making sense now. but i've said that before.