Mac OS 64 bit | Request | Beg | Plea

[gege]

The jBridge, depending on how many are opened, adds a small <3% overhead, that is better than no Nebula at all (Logic X).

About the interface I think you should try and set up the original VST .xml files, once setup there when you lead the bridged (that is the bridged VST) it should take that interface.

Obviously is a temporary solution to allow anyway everyone to use Nebula 'sound' on Logic 9/X while waiting for something more definitive

[ngarjuna]

I haven't utilized this new solution but I think in regards to the skin problem this might be a possible workaround: figure out the filename of the skin that it keeps defaulting back to (OVERWRITEME.N2S or something like that if I had to guess). Change its name (OLDDEFAULT.N2S or whatever) and rename the skin you want to use OVERWRITEME.N2S or whatever the old default was called.

Alternatively you can try to hunt through XML and change the filename pointer there. My guess is that it's not saving the change (rather than continually overwriting the committed change) but that's just a guess, could be wrong. So I'd personally try the first idea.

[noisyneil]

thanks ngarjuna. that works!

[giancarlo]

we are working hard on mac osx lately.
It's a bit more stable also windows version too.
We are working on a new engine, we'll support all new cpu

[jeffbdavis]

we are working hard on mac osx lately.
It's a bit more stable also windows version too.
We are working on a new engine, we'll support all new cpu

[giancarlo]

compiled core4 for mac osx too. Apparently everything is running flawlessly. We'll start betatesting soon, I'll try to compile all versions tomorrow and to prepare new installers around the end of this week.

[jeffbdavis]

Thanks for all the work you're doing, Giancarlo! Can't wait to try the updates...

[brp]

wow, that sounds great g!!

i recently put a new system together: i7 3930k c2, asus p9x79 ws, 4x4gb corsair dominator platinum 2400 (oc)... and overclocked it to about 4200ghz / 2400.

but when i want to setup a compressor program proper, meaning using 13.5ms of freqd kernels and prg rate 0.104ms resulting by disabeling rate s and smooth on glob page, my system still makes the scatman... but it seams that's only the case because nebula somehow doesn't distribute its threads proper to the different cpu cores. i use the nebula-reverb, which is ment to be able to handle multithreading. but the meter in the asus software as well as the taskmanager doesn't show a helthy distribution. here in the forum everyone seems to say that these meters are wrong. however, i did the following test: i disabled 5 of the 6 cores and also multithreading so that i could run the system at 4800ghz without thermal problems and guess what? scatman was dead!!!

if you do the math, it becomes obvious that nebula is not able to get the full power out of multicore cpu. and no, it's not the buffer. i tried it with huge buffers everywhere (asio up to 4092).

so now i'm wondering if the new engine is bether regarding multithreading and if not: pleeease make it


all the best
pascal

[giancarlo]

yes it should help

[brp]

awesome g!enius!

[greekpeet]

compiled core4 for mac osx too. Apparently everything is running flawlessly. We'll start betatesting soon, I'll try to compile all versions tomorrow and to prepare new installers around the end of this week.

awesome sauce!

[jkervin]

Psyched for this!

[Mojoe]

Any News for the Update, cant wait to use the 64bit Version, its now a long time without Nebula.

[giancarlo]

as first step we'll release a vst64 to nebula server users. This vst64 should be good enough for a wrapped usage, ie using jbridge.
If it will work correctly we'll release vst64 to nebula3 pro users.

We are still working on au side. Steinberg wasted 2 years on that, we are wasting a similar amount of time (we started late, in the middle of 2011, because we are a small company). As stated correctly by arne (steinberg),

We are now at the same point we were 2 years ago before Apple dropped 64 bit HIToolbox. So nothing really won from a users point of view. Internally it was a good thing to re-factor our UI code and gave us the opportunity to fix some bugs and streamline our native implementations.

in our specific case we introduced tons of bugs too.

[brp]

some years ago i asked you why you are not going with juce..

and i still can not see anything positive with the way you go. it just looks like you're sado masochistic going such a painful way. i myself are a bloody beginner with programming and still was able to make some useful tools for my studio!! i know, you'd had a lot to rewrite with juce. but if i see things right, you have the nebula engine as c++ code with lots of assembler lines, which should compile with juce as it is. you mainly had to rewrite the gui which is really not more difficult and timeconsuming as you would build a gui from lego

i'd bet such a smart guy like you would have no longer than four weeks to port nebula to juce. sure, the gui probably would look different. but who cares!! i'd really like to see you working on the engine rather porting nebula to each pluginformat separately!!! and i think you'd like too, not?

have you ever tryed juce? you can just try everything for free as long as you want! you're even allowed to make freeware for free with it. if you want use it commercially you'd have to buy a license for about 700$.

go to the juce homepage to learn more about it. it's really worth at least learning to work with it. there is so much beautiful code in there, that nearly every programmer would find some inspiration to improof his own code!!

but dont get me wrong, i'm with you whatever your way will be. i follow you g-sus

all the best
pascal