Something changed within my computer (without me actively changing or installing anything) literally over night. Tuesday night I was giving the final touches to a mix with 3 band members present. No hiccups at all. Wednesday morning I open Reaper in order to render the files - instant crash. Froze track by track - until it crashed again. Open a different project - instant crash. I can't work anymore!
WTF is going on? The ONLY suspicious thing I see is this - on top the NebulaSetups EMT140, bottom pic shows NebulaReverb with the same program loaded. Both conversion settings are at 9000.
a) why? b) may this be connected to recent Reaper crashes?
are you working at 44,1 khz or 48khz in the project where the crashes happen? if nebula crashes in an 48khz project and works in an 44,1khz project (just try with a fresh project) then it is similar to a mysterious issue i had, where nebula all of a sudden crashed in all samplerates except 44,1 khz. maybe the instance that shows 48khz is the culprit?
i never found the cause on my system, reinstalled nebula completely, it was gone. acqua plugins are not affected.
just a shot in the dark, maybe it's related.
system 1: windows 8 32 bit - samplitude prox, tracktion6, reaper system 2: mac osx yosemite - reaper(32+64bit), tracktion6(32+64bit)
both systems on: macbook pro (late 2009), core 2 duo 3,06 ghz, 4 gb ram, graphic: nvidia geforce 9600M GT 512 MB