none of the drive related things made any difference. which is really pinpointing it to cubase, but what the fuck?

i'm reinstalling again. see, the thing is that my reinstall is actually pretty painless - it's entirely scripted. it's just a process of setting it in motion. i have no real fear of reinstalling, it's just a pain in the ass - and a question of risk reduction.

but, i think it's the most methodical way to do this. i want to stop before i run any user scripts, see what happens and then move forwards incrementally from there.

if it's fucked right off the bat...i'm at a loss...

if it breaks somewhere along the way, i can find the problem and correct it.

yeah, this is...

everything's set to read-only. i've been through this before and know it's an access thing, but it's...i think it's connected to reinstalling. windows is confused because it thinks the previous install owns the drive. and, even when i take ownership and delete the old user and all of these other fun things there's still remnants in the directory structure that are getting in the way. this is all over the internet, and nobody has a good answer.

i'm going to format the drive....that'll wipe out the partition table, which i think is the crux of it. an ntfs error. when i have the project in ram, it's running properly; it's when i save it to disk that it gets corrupted.

still befuddling.

the drivers are fine. thankfully.

but, here's the latest bizarre weirdness. when i line the reconstructed files up in a new project, they render clean. repeatedly. until i save and reopen the file. then i get the screwy behaviour again.

i think that's actually a hard drive issue. i'm running a chkdsk on the drive. i'll format it if that doesn't work.

whatever hit me really walloped me....

gah...

i did a grocery run in the hot afternoon heat and took forever to cool my brain down. it's getting close to bed time, but i can hopefully at least get the tracks realigned in the right way. here i go...

tim robbins was in a band?