Nebula version 1.3.903 released

Tips & tricks, working results, technical support
indelible
User Level VIII
User Level VIII
Posts: 86
Joined: Fri Jun 11, 2010 12:10 pm

Re: Nebula version 1.3.903 released

Post by indelible » Mon Jun 15, 2015 8:12 pm

Any news about the issues in H******* Mixbus (PC)? Even .903 is not working. I opened a ticket months ago

javahut
User Level V
User Level V
Posts: 57
Joined: Sun Jan 30, 2011 1:49 am

Re: Nebula version 1.3.903 released

Post by javahut » Mon Jun 15, 2015 11:52 pm

Support wrote:
G has communication with Noel from Cakewalk started yet?
We are waiting reports from two customers that report issues with Sonar. None replayed ticket yet.
Okay... you have my ticket re-opened concerning 1.3.903 Pro and Server version being virtually unusable in Sonar when used as directed.
downtempo.dub.psychedlic.twang
Canartic - Modulotion

turbidnick
User Level 0
User Level 0
Posts: 7
Joined: Wed May 05, 2010 9:33 pm

Re: Nebula version 1.3.903 released

Post by turbidnick » Sat Jun 27, 2015 9:22 pm

I just upgraded from x64 version 1.3.770 to this and now when I load nebula in reaper it says

Acustica Loader ver 1.3.903
Debug level : 0
Master Ok (nebula3 reverb.xml)

Then immediately crashes reaper.

any ideas what's going on here? I have a major project loaded with nebula everywhere on it and need to get it running again. Any help will be greatly appreciated, thanks

richie43
Expert
Expert
Posts: 5049
Joined: Fri Feb 04, 2011 8:47 pm
Location: Minnesota, USA
Contact:

Re: Nebula version 1.3.903 released

Post by richie43 » Sun Jun 28, 2015 12:35 am

turbidnick wrote:I just upgraded from x64 version 1.3.770 to this and now when I load nebula in reaper it says

Acustica Loader ver 1.3.903
Debug level : 0
Master Ok (nebula3 reverb.xml)

Then immediately crashes reaper.

any ideas what's going on here? I have a major project loaded with nebula everywhere on it and need to get it running again. Any help will be greatly appreciated, thanks
I just PM-ed you, but here it is again......

If you are in the middle of a big project, you should never make such a huge upgrade to software, actually. For your own sanity's sake, I suggest getting a copy of installers for the version you had working and finish.
Before you do that though, it could be that it needs to be reauthorized OR the new version installed to a different location and you have both installed (which can be horrible with nebula). Try replacing the "init" files that were sent to you to authorize it (or run the exe if you were given one). That can often fix issues.
Also, delete the entire contents of the temp folder in your "Nebulatemprepository". Also delete the "~scanboot" file in the "Setups" folder in the repository (only that one if there are other files in the Setups folder). Any time you do an upgrade, always delete this temp cache and ~scanboot file and let Nebula rebuild them.
If these all fail, your best bet is to reinstall an older version until you have the time and patience to upgrade and trouble-shoot.
The Sounds of the Hear and Now
http://soundyaudio.com/

turbidnick
User Level 0
User Level 0
Posts: 7
Joined: Wed May 05, 2010 9:33 pm

Re: Nebula version 1.3.903 released

Post by turbidnick » Sun Jun 28, 2015 5:19 am

Right you are about not upgrading mid project! Thanks for your help, I got it working again. Had to backup the programs/vectors folders and delete my old nebula folder all together. Then re-install nebula and all of my programs one by one and it's working now.

User avatar
Support
Expert
Expert
Posts: 3640
Joined: Mon Feb 24, 2014 11:33 am
Location: Lodi, Lombardia, Italy.
Contact:

Re: Nebula version 1.3.903 released

Post by Support » Sun Jun 28, 2015 10:38 am

turbidnick wrote:I just upgraded from x64 version 1.3.770 to this and now when I load nebula in reaper it says

Acustica Loader ver 1.3.903
Debug level : 0
Master Ok (nebula3 reverb.xml)

Then immediately crashes reaper.

any ideas what's going on here? I have a major project loaded with nebula everywhere on it and need to get it running again. Any help will be greatly appreciated, thanks
Read support ticket.
Best regards,
Enrique Silveti.
Acustica Audio customer and technical support
http://www.acustica-audio.com

greekpeet
User Level XI
User Level XI
Posts: 171
Joined: Mon Mar 29, 2010 9:28 pm

Re: Nebula version 1.3.903 released

Post by greekpeet » Thu Jul 02, 2015 6:07 pm

javahut wrote:God... I don't know where to start.


First, I've spent a month and a half trying to solve a new problem with my PC, and in the process... rebuilding my audio PC to a 5930k from a 980x, new 32GB DDR4 RAM (from old 24GB DDR3), new SSD Samsung Pro 1TB for audio and samples (OS is and has been SSD Samsung 840 Pro 500GB), reinstalling everything from scratch. Uninstalling recently updated plugins... trying to figure out what's causing the problem. Thinking it must be a "bloated" Sonar. Purchased Reaper and started trying to learn it. Realized there's too much in Sonar's workflow I can't do without enough to spend time learning Reaper. Back to trying to figure out the problem with Sonar. Purchased server version of Nebula. All to no avail... as I continued to have the same severe audio engine drop out problem that's been plaguing me for the last month and a half continue.


Then on a whim... I uninstalled the 1.3.903 server completely... reinstalled the Pro version of 1.3.846, making sure to completely rebuild plugins, xmls, and VST registry for Sonar. And... voila! Everything back to normal.


I don't know what you guys did to 1.3.903. All I know is... I can run a metric $h|T ton of Nebula plugins in a single project without problems in 1.3.846. I can't play through a project once with less than a quarter of that amount of Nebula plugins in 1.3.903 on the server version.


So anyway... relieved that all's working again after a month and a half of problems, and several thousand $$$$ later. Nice to have a newer "upgraded" PC (though I lost my PoweCore PCI in the process).


I just hope the guys at Acustica can figure out what it is exactly that's different about 1.3.903 from 1.3.846, and can fix it. Or figure out a way to explain in English what the difference is and what we need to do to make the newer versions of Nebula work as well.


For everyone that says 1.3.903 works better? Either you have something entirely different with your system than several of us here do... or you don't really use Nebula heavily. Because there is without a doubt a HUGE difference between the two versions... and I'm using a LOT of Nebula in my projects. And this makes 2 systems I've used 1.3.903 on now that both exhibited the exact same problem with the update (one wasn't an update, but a completely new install on a completely new, modern X99 system).


Can't wait to see if I see an even bigger increase with the 1.3.846 Server version (now that I own it) over the Pro version.


But I'm really kinda worried that Acustica doesn't recognize that there's a problem. And what's different in the newer version that might be causing it to perform so very much worse than 1.3.846, in some systems at least. Is there a setting in an XML or something for the new version? Something not assembled correctly? I don't know. But I'd hate to be stuck on 1.3.846 and now never be able to upgrade again. As much trouble as this has been, and as much time and money as this has cost me, I'm afraid I'll have to abandon Nebula after all this time using it, and go back to algo plugs for everything. Please, Acustica, try to solve this problem. There definitely is one. I really hope you don't ignore it. Maybe it'll work itself out in the next update (fingers crossed).


At least I'm back in the audio business for now, and out of the technology troubleshooting business... at least for a little while.

Sent a support ticket with the same issues everyone else is having with it having major issues with playback again today. Sent support tickets in the past that ended up being closed several months ago with no resolution.

Reverted back to .846 a few months ago, got massive kernel panics in OSX every single time.

Went back .839, with it running the way it was supposed to. Well sorta… .839 crashes all of my compressor libraries upon loading, so that kinda makes about $300 worth of libraries not function for oh six months now… Literally it has been six months since I have been able to use a single compressor program in Nebula.

I get it, they are focused on Nebula 4 and the ACQUA line. Cool, but its NOT cool to have this keep coming up with not a single upgrade to their core line.

To be honest I spent about $900 on UAD plugins instead of any of the new ACUQA line. Was literally about to spend almost $1000 on the new technology but feel really left out in the cold as a long term customer.

Why?
Because I am voting with my wallet. That and demoing Honey with it major crackling CPU spikes when turning knobs making it unusable. Amber was a great EQ, loved using it on a new project, and worked very well. Demo ran out and decided not to purchase.

Again, out of principle.

When you have upgrades that render whole groups of libraries going on half a year…

Still have hope but honestly beyond frustrated at this point.

If Nebula 3 does not get these things fixed up, and Nebula 4 comes out with 3 getting no more support. I am dumping the platform completely for future support, using what I have and moving to a hybrid setup.

You can rent amazing gear here locally for the weekend for half the price of most of the new ACQUA lines. It's just business.

I really hope they sort out 3 before the next jump to 4.

Still have a heart in this technology but sometimes you gotta give up.

User avatar
giancarlo
Founder
Founder
Posts: 11214
Joined: Mon Sep 21, 2009 10:40 pm
Location: Italy

Re: Nebula version 1.3.903 released

Post by giancarlo » Sat Jul 04, 2015 7:30 am

we are moving nebula to a new engine

Also it fixes crackling some user is experiencing on mac osx side and core6.
It should be pointed than a lot of users don't experience issues in core6 and they can load a lot of instances now, but in any case we are working on a better scheduling of threads

javahut
User Level V
User Level V
Posts: 57
Joined: Sun Jan 30, 2011 1:49 am

Re: Nebula version 1.3.903 released

Post by javahut » Sun Jul 05, 2015 7:30 pm

Gotta say though, several weeks ago I changed the Nebula Server application, running locally on this same machine, to run with /affinity FF0, and now with a priority of /Realtime, and it has made a HUGE difference with Sonar Platinum. I'm pretty much free of audio engine dropouts, and thread work went WAY down, and I seem to have much more headroom... as in I can add even more Nebula plugins now.


This is working pretty well now, for Sonar Platinum use. But if Acustica has found a way for even better thread scheduling... I say GREAT! So glad you are placing a priority on getting the thread scheduling affinity and priority the best it can be... for all host DAWs.


And if you're using the latest Sonar, and are having problems... I would say until they get whatever it is solved to more easily work well with Sonar... it's worth the small price to upgrade from Pro to Server, and run the Nebula Server app locally, and set your Nebula XMLs to run through Nebula Server on all but the first one or two cores of your machine. It's working pretty well here now.


I may not have to switch to Reaper after all :D , even though I have been learning it and playing with it the past few weeks. Right now, my mixes still sound better in Sonar, so I'm hoping I can keep using Nebula Server this way until the other problems are sorted out.
downtempo.dub.psychedlic.twang
Canartic - Modulotion

User avatar
himhui
Expert
Expert
Posts: 1277
Joined: Sun Mar 28, 2010 6:04 pm

Re: Nebula version 1.3.903 released

Post by himhui » Mon Jul 06, 2015 7:09 am

indelible wrote:Any news about the issues in H******* Mixbus (PC)? Even .903 is not working. I opened a ticket months ago
I don't think Mixbus v2.5 or previous versions support nebula and acqua though it won't crash on mainbus only. Mixbus v3 may get improved but let's see. Ardour 4 is the sample of mixbus v3, it works with nebula(still not recognize nebula dll with different name)and acqua but can't compensate the latency well over around 3000ms per plugin at present.
Xeon E5-2697 v4/Win10 x64/64G ram/ Quadro K620
Reaper 5.974/X-Touch
Prism Orpheus/ RME Babyface Pro

User avatar
himhui
Expert
Expert
Posts: 1277
Joined: Sun Mar 28, 2010 6:04 pm

Re: Nebula version 1.3.903 released

Post by himhui » Mon Jul 06, 2015 7:28 am

himhui wrote:
indelible wrote:Any news about the issues in H******* Mixbus (PC)? Even .903 is not working. I opened a ticket months ago
I don't think Mixbus v2.5 or previous versions support nebula and acqua though it won't crash on mainbus only. Mixbus v3 may get improved but let's see. Ardour 4 is the sample of mixbus v3, it works with nebula(still not recognize nebula dll with different name)and acqua but can't compensate the latency well over around 3000ms per plugin for each track at present.
Xeon E5-2697 v4/Win10 x64/64G ram/ Quadro K620
Reaper 5.974/X-Touch
Prism Orpheus/ RME Babyface Pro

User avatar
Support
Expert
Expert
Posts: 3640
Joined: Mon Feb 24, 2014 11:33 am
Location: Lodi, Lombardia, Italy.
Contact:

Re: Nebula version 1.3.903 released

Post by Support » Mon Jul 06, 2015 1:54 pm

Sent support tickets in the past that ended up being closed several months ago with no resolution.
R: Incorrect. Not all your support ticket are closed. TECH-0000001141 Audio dropouts using TIMED kernels still open. About TECH-0000000972 and TECH-0000000573 we did not receive response, ticket system send an alert 72 hours after no ticket replay, and then close it.
Went back .839, with it running the way it was supposed to. Well sorta… .839 crashes all of my compressor libraries upon loading, so that kinda makes about $300 worth of libraries not function for oh six months now… Literally it has been six months since I have been able to use a single compressor program in Nebula.
R: Correct due those compressor libraries are not compatible with this version of Nebula due where created with a newer version of NAT.
I get it, they are focused on Nebula 4 and the ACQUA line. Cool, but its NOT cool to have this keep coming up with not a single upgrade to their core line.
R: Incorrect. We have endeavored to maintain compatibility with legacy OSs like OSX 10.6 and 10.7 or Windows XP releasing Nebula with VSTGUI3 UI framework. OSX 10.7 to 10.8 was a big step for OSX 64 bits applications due Apple did not update Cocoa A*I for 64 bits OSX OSs and force every developer to move to Carbon A*I. Downward compatibility was abandoned, thus, in this scenario we recommend to keep a hardware/software balance in customer's computers systems.

- i7 g2/g3 computers should use OSX 10.7. Audio host should run at 32 bits and audio plug-ins should run at 32 bits. Nebula should be installed in legacy mode for VSTGUI3. We recommend to use 1.3.8xx version(s).
- i7 g4/g5 computers should use OSX 10.8*. Audio host should run at 64 bits and audio plug-ins should run at 64 bits.
Nebula should be installed in normal mode (for VSTGUI4). We recommend to use 1.3.9xx version(s).

* Seems OSX 10.10.3 is also stable for 64 bits host/plug-ins.

Cocoa is Apple's native object-oriented application programming interface (A*I) for the OS X operating system.
https://en.wikipedia.org/wiki/Cocoa_%28API%29

Cocoa is Apple's native object-oriented application programming interface (A*I) for the OS X operating system.
https://en.wikipedia.org/wiki/Carbon_%28API%29
(Read: Cocoa and Carbon.)
That and demoing Honey with it major crackling CPU spikes when turning knobs making it unusable.
R: It is a problem with bad hardware/software balance. Please, read the previous answer. You are trying to run 64 bits applications in a not complete 64 bits OS.
If Nebula 3 does not get these things fixed up, and Nebula 4 comes out with 3 getting no more support.
R: Incorrect.
Best regards,
Enrique Silveti.
Acustica Audio customer and technical support
http://www.acustica-audio.com

User avatar
giancarlo
Founder
Founder
Posts: 11214
Joined: Mon Sep 21, 2009 10:40 pm
Location: Italy

Re: Nebula version 1.3.903 released

Post by giancarlo » Mon Jul 13, 2015 1:23 am

I'll repeat myself again and again

giancarlo wrote:we are moving nebula to a new engine

Also it fixes crackling some user is experiencing on mac osx side and core6.
It should be pointed than a lot of users don't experience issues in core6 and they can load a lot of instances now, but in any case we are working on a better scheduling of threads
to mac osx users: if you experience crackles just set MIXRATECYCLES to 0 (zero). We are moving to a better threading model. This is NOT related to nebula though, this is a nebula thread, so please move to a correct thread.

1.3.903 works pretty well on most of systems. We suggest to downgrade to a previous version if it does not work as expected, this is a common rule in nebula. If a library was created with a new nat and it is not compatible with nebula ask to use a previous nat/nebula to the library developer!

1.3.903 is the latest one. It is pretty NEW, since in our acqua plugins we are running 1.3.959 (and all new releases introduce new features, not bugfixing).
1.3.839 is NOT so much old. But it was buggy on lookahead. Lookahead was fixed because it was crashing on several computers and the result is a slower scheduling which introduces issues in sonar and several other host. Reason why not everyone has issues is just because someone is running new hardware so it goes faster, someone is running a more optimized host.

But here I should be damn clear. 1.3.903 is SLOWER. It is SLOWER because bugfixing made it SLOWER. There was an additional buffer which could lead to crashes, and it was helpful for cpu balancing. But it was the CAUSE of the crash. Lookahead before was NOT working as expected. Lookahead was FIXED, and it makes nebula SLOWER.

Just to use different words, a bug was the REASON for crashes, and it was the reason for the lower cpu load. You can keep the bug, or you can keep the better cpu load. You cannot have both of them. I don't know why reaper apparently works better than sonar, at least some user reported it. We try to support all hosts but performances are different sometimes, especially for high-demanding plugins like nebula. Obviously different hosts have different optimizations. Just to make it clear, we do NOT force affinity threads. We don't mess with threads. We CREATE new threads. I don't have a clue why sonar tries to modify them really, if it does it. I don't know even if it does it.


Now you have different solutions:
- buy a faster pc
- use a different host
- wait for a miracle, which should be a better engine. If we make the engine "faster" it could compensate the lacking of the WRONG buffer we were forced to change in order to support properly look ahead. I'll repeat again: this buffer was increasing the time available for running audio, but it was WRONG: it should be reserved for look ahead purposes. As result of it, look ahead now is correct.

NoNameComesInMind
Member
Member
Posts: 273
Joined: Wed Apr 22, 2015 1:45 pm

Re: Nebula version 1.3.903 released

Post by NoNameComesInMind » Mon Jul 20, 2015 6:46 pm

Hello!

it has probably been taken up before, but if i was to say
investing in Nebula Server, will the upcoming Nebula 4 release be an upgrade for a reasonable price or how is your take on upgrading?

Best,
EQualizer, Nebula, Coffee.

User avatar
theheliosequence
User Level X
User Level X
Posts: 148
Joined: Thu Dec 11, 2014 4:23 am

Re: Nebula version 1.3.903 released

Post by theheliosequence » Tue Aug 18, 2015 12:13 am

NoNameComesInMind wrote:Hello!

it has probably been taken up before, but if i was to say
investing in Nebula Server, will the upcoming Nebula 4 release be an upgrade for a reasonable price or how is your take on upgrading?

Best,
I'm also curious about this. Would like to start diving into Nebula Server, but from all I'm reading it looks like there might be no point in owning it once Nebula 4 is out? Giancarlo expressed that Nebula 3 (server) and 4 would be different products but I honestly don't really understand why Nebula 3 Server would continue to exist or why anyone would continue using it if they had both versions. He mentions people might not like the new version (perhaps referring to charging for the upgrade?) and then says the reason to keep Nebula 3 going is "because there are people interested in single configurable instances more than a skinned multi-instance loader. Several users are interested in a fast configurable loader with many affordable libraries, for example."

Is Nebula 4 not going to be a fast configurable loader with many affordable libraries? Perhaps it will have limitations to ensure AAX compatibility that Nebula 3 won't have? Or perhaps 3rd party developers will have to charge more for Nebula 4 libraries because of a more involved, time consuming process?

I'm definitely not trying to be negative, just trying to be smart and figure out the best way to move forward with Nebula without buying the program twice if I ultimately want the best product moving forward.

Here is the full quote from a Gearslutz thread:
Giancarlo:
more or less you'll have a rack of skinned nebulas, exactly as we planned and described 3 years ago. So you can control multiple-instance plugins in a better way. All libraries will be also available in skinned format (even a default one if a skin is missing).
So nebula4 solves an issue we cannot solve in nebula3 today: when you have a module based on multiple instances you will be able to edit each single instance. At the moment nebula3 is based on single instances only, and they are not skinned (unless you use a configuration external tool like nebula setup).

About the tech, today nebula3 server is the only one which shares the new nebula4 engine. Something is supported also in nebula3 pro, but this situation will change after the introduction of Core7. Core7 will be a little surprise.

About the future: when nebula4 will be out we'll remove "nebula3 pro". The actual nebula3 server version will NOT be removed. We'll have only 2 products, nebula3 and nebula4. They will be client/server versions. For the first time in our history the new product will not be a free upgrade, but we'll take in account if you are already a customer for a proper upgrade policy. Nebula4 is not an upgrade of nebula3. It is a completely different product. It is possible the market will not like it, for example (for the same reasons why someone does not like other rack-based products today).

In my mind there is enough space both for nebula3 and nebula4, because there are people interested in single configurable instances more than a skinned multi-instance loader. Several users are interested in a fast configurable loader with many affordable libraries, for example.

Nebula4 will be a new concept/product and I think not all people will like it, so we give a choice. Both nebula3 and nebula4 will share the same engine, so they can be upgraded easily and maintained. All acqua plugins will share also the same nebula3/nebula4 engine and they will be loadable from nebula4, so we can maintain the whole platform easily. Acquas are advanced skinned nebula4 libraries.

About release dates: we planned Nebula4 for march 2016. It was a long journey but the engine was not good enough before. Its tech is already available now in acqua plugins, and Core7 will be available in our server version around october 2015.
Win7 64-bit i7 3930K, RME MADI FX, N3S/N4, Amber, Aquamarine, Amethyst, Black Series, Blue, Cobalt, Coral, Diamond, Ebony, Emerald, Gold, Green, Honey, Ivory, Lemon, Lime, Magenta, Navy, Orange, Pearl, Pink, Pink Comp, Purple, Sand, Scarlet, Titanium, Ultramarine, White

Post Reply