i have an idea for 2016 / 2017: It is a community event.
So here comes my idea: Why not let the community decide which hardware should be sampled next (one time)?
If we all get into the boat and we (the community) could make the decision - and we could decide what acoustica should sample next - it would be much fun and pleasure. A community product. People decide what it will be... and could even make suggestions for the final gui... why not?
Or just suggest ten hw units (which are also sample able) and community decides what is next...
P.S.: i openend an own thread here in the forum... but i think nobody wil find it
Nebula4 doesn't add anything from this point of view, because it is just a multi instance loader, and it is compatible with nebula3 which is a single instance. Nebula4 doesnt have a different audio engine. The engine is nebula, the same we are using today. Each nebula instance is a "program". Trims are "programmed" controls. We'll not make nebula "dirty" just because it is version 4. We want to keep the design as much simple as we can, so we can do complex things (like we are doing today in acquas, where complexity increases but without adding exceptions and strange choices). Almost all acquas have a programmed trim. When nebula will support chains you'll be able to merge trim controls easily.
What is nebula4: it merges acqua and libraries. Nothing more, nothing less. We'll add several little things, but not "controls". They should be provided by single components inside. Trimming is a piece of the programming language. Just to explain clearly, the actual output control is and will be the same control we'll expose, ever. Trim could be exposed or not, it depends on the program. Cause backward compatibility, output control will never change any more.
Midi support is an implementation like other ones It is not about version 3 or 4.
Just to be clear: - 3 is single instance - 4 is multi instance
Everything else is pure speculation. Since 4 is based on a different framework and appearance (in order to translate to multi instance management), several things will be simple to do. External meters, preset browser, routing, multi instance management: they will be added later (something maybe from the very first release). We are still planning features so we don't have a timeframe for every new feature now.
Very first release will load nebula libraries (but skinned) and acquas. So we are merging both worlds, and things are more integrated and elegant (no more skin with strange sizes and shapes, uniform design)