the drivers are totally stable, finally. i'm a little apprehensive about rebooting, but for now everything seems ideal.

but, because i'm neurotic, the mixer issue presents a big challenge. i have multiple possible mixes, resulting from the mixer doing weird things. a little bit of further testing suggests that saving the mixer file separately produces corruption on the save, but saving it with the project produces corruption on the load. it's bizarre, frankly. the only dlls it's pulling are in the kernel; it's not even reading any of the C libraries. my best guess is that's probably a mathematical error in the code. but, knowing that doesn't address the issue at hand: which do i use? do i start over?

when i go over this for the already finished tracks, i'm going to be very selective in what i replace. i know that most of the songs were saved repeatedly before i exported, meaning i've verified that the final out is desirable. and what i'm noticing is that i often can't tell the difference between the mixer error on an a/b. i've tested it quite a bit at this point. it comes out in the null, but i can't actually hear it.

but, i'm neurotic.

so, for these songs that i'm approaching with a fresh understanding of the software, i have to work each of these parts out on an a/b basis.

there was never a benefit in the fading highs. but, when the subbass was floored, it made me think about a few things a little differently. and i'm going to want to work a bit of that in.

it might work out as a net positive in the end. but, i'm bloody happy that this mess is done with. it's just that putting the pieces back together is not going to be that quick, after all. lots of listening. lots of comparing.

lots of being neurotic.