as an aside ... I really miss NOT being able to use my NAT app that came with NEBULA. Ever since the last upgrade [to Server], my NAT app has several issues ... like crashing, or when I get it to run, the main window cannot be expanded [dual screen setup] so that I can navigate the way I used to. Hope 'G' gets a fix out for this SOON!
No NAT Crash here, W7 SP1 x64! NAT from Nebula3 PRO and Server are almost the same. NAT is a stand alone portable app. Upload your NAT folder and send me an MP with the URL and I'll try it.
Sorry to interupt, but, referring to my earlier post to Enrique ...
The NAT files you returned to me did not make a difference ... same crash IF a Nebula instance is not 1st loaded before moving the main NAT window. Also, NAT still does not expand across dual monitor display.
I recall a 'graphics engine' change made awhile back ... this was the start of thie problem. Prior to that, NAT worked fine ... no crash, expanded display.
There is a issue into last NAT/Nebula when you load Nebula into NAT, sometimes does not load, some times load. But not crash or GUI issues in dual monitor setup. Seems to me related to WXP x86. We will check ASAP.
Enrique Silveti. Acustica Audio customer and technical support.
Don't want to start a new tread but what does the <EXPORTAUDIOQUALITY> 1 </EXPORTAUDIOQUALITY> in 'Nebula3 Reverb.xml' do? I am not asking about the <FIXEDQUALITY> 0 </FIXEDQUALITY> parameter which should not be touched ever.
Melon_Jack, that's probably due to the shorter kernels lengths when switching to TIMED. You can edit the kernel lengths in the XML. I also had this with R2R, and I got the best results with low frequency response when switching to SPLIT/HYBRID.