What you're describing sounds like random behavior which, while indeed potentially present with analog equipment (the behavior in that case isn't actually random but it's affected by factors which are quite invisible without a lot of test equipment), I don't understand how Nebula could accomplish that. My understanding was that Nebula used program input to determine which of the sample sets a particular programatic input would use. How would a common signal apply different Nebula samples (using a particular program) from one pass to the next? Is there some kind of pseudo-randomizer? Not really looking for code-specific details, but is this really what Nebula is doing? On one hand that would be pretty cool but from another perspective it's a bit frightening to think I could dial up my "dream settings" only to get a different sound on my render pass (yes, I do realize that is precisely what happens often with fussy hardware). I thought only time based effects would have this feature.Mercado_Negro wrote:Because 2 hardware units don't sound the same either, ever. You'd use your ears in this case to verify if your unit is still in good shape. Null tests with Nebula is pointless and a major waste of time man, there are several hundreds of samples per programs and they are not the same on each pass; you can actually verify this by listening the same passage over and over, it just won't sound the same each time. Been there, done that. That's one of the things I like the most about Nebula, even in that it behaves like hardwarefuseburn wrote:What I don't get either is: Why don't 2 instances of nebula with identical programs - meaning 2x x64 or 2x x86 with R2R or a console) - null out ? The difference signal is always down at -40 till -70 and it sounds like the program rate intervals are not synced (Overtones/distortion). That means you can't even verify if your plugin processing sounds just like the freeze you did 3 days ago, let alone the things I'm talking about in here (comparing x86 vs x64). Why is that ?
I have to run some tests to confirm what you say about differences between 32-bits and 64-bits versions but to be honest, I consider it highly unlikely since compiling is a pretty straightforward step after coding and having all the environment set up. In any case, I'll give it a go for fun
I have certainly experienced what you describe (listening to a pass and thinking to myself "Was that different? The transient on that third snare hit sounded a little different to me...") but I always attributed that to the poor auditory memory and extreme susceptibility to cognitive biases that humans are endowed with; the difference has never been so extreme that it couldn't be explained as psychological.
I'm curious, though, perhaps my understanding is incorrect.