I know, this belongs on the NAT thread...And it is there too. Please don't sue me for double posting.... I am not a sampler, and use NAT only rarely to apply the GDRIVE patch to libraries. But as I have been hearing people complain about NAT not working for them, and me responding how mine has always worked and maybe their issues are system specific, I realized that I hadn't opened NAT in a while. Well, my NAT does not open anymore and the only thing I have changed is upgrading to the newest Nebula. I always upgrade both 32 and 64bit even though I almost never use 32bit anything anymore. But I know Nebula 32bit is needed for NAT.... Now Nat tries to open, flashes on the screen, and vanishes. I have tried running under various compatibility settings, and even tried i9nstalling with different compatibility settings, but NAT is broken here. Any ideas what is going on here?
Very weird indeed. Nebula is awesome sounding software, if we can see the back end get to the same quality as the sonic quality, we will ALL (users, devs, and Acustica) be happier and more comfortable with the longevity and stability!
I will email you RJ. Another user just emailed me a "hacked" NAT, and after changing the simple location info in one of the xml's, I just renamed my Nat folder to something like "Nat-old" (I am sure it could be simply removed, but I like to stay organized), and put this entire new Nat folder in the repository, and it works great!
Add another report for Nat suddenly not working anymore (the same startup thing, you see a flash of _something_ and then nothing).
No idea since when, it's a while since I toyed around in it. Most of the time I try reinstalling the older version and seeing if that works, then upgrading version-by-version to see when it breaks. But didn't feel like spending time on it since I rarely use NAT.
But if sucks that it's not working for renaming / managing libraries...