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?
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:
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.