track #2 (from the end of july, 2014) uses the cubase eq to greater effect, which has allowed for greater testing. the results are very curious, and cement a broken mixer as the cause. there's also a specific behaviour that is not asserting itself and that i believe may be at the root of the problem.
i have all of these eq settings saved in my rampresets.xml file. so, i'm testing at three levels. the first is manually entering the eq, as they exist in the preset file, without saving. the second is re-opening the file after the save. the third is loading the presets from the xml file.
this actually produces three different outputs that are clearly eq-based in the difference files. further, the results can be consistently recreated so they null with like outputs - the output will continue to null over and over after i load the presets, or before i save the file.
it is only the third option that will null with the original output.
but, here's the thing: i shouldn't have to load these presets. cubase should recognize that they are the presets in the file, and the presets should then auto-load. this is something it has always done. but, it hasn't been doing it in the time it's been weird.
i think that there's a good chance that if i can solve this problem then i'll have solved the whole problem. there's a number of things i can test for.
as it is, i currently see no reason to update this ep, which was also finalized at the end of this may. but, i'll have to do some more testing to be sure of it.
https://jasonparent.bandcamp.com/album/the-time-machine
for now, it seems to suggest that *both* of the options i'm dealing with - rendering from ram or rendering from disk - are wrong!
