Login

True revolution on RAM side, 1.3.480 experimental released

Tips & tricks, working results, technical support

Re: True revolution on RAM side, 1.3.480 experimental released

Postby Arne » Thu Apr 21, 2011 10:37 am

Thanks himhui, I`ll give it a spin ;-)
Arne
User Level XI
User Level XI
 
Posts: 170
Joined: Sat Nov 20, 2010 10:31 pm
Location: Bergen, Norway

Re: True revolution on RAM side, 1.3.480 experimental released

Postby Arne » Thu Apr 21, 2011 1:42 pm

UPDATE:

I jBridged the Nebula Server 64 bit client and himhui, you where right, Samplitude does not crash anymore upon loading even with 48 or more instances loaded.

However, jBridging the server client does not gain any efficiency in RAM use as the jBridge auxhost64 creates its own instance which require another 24 MB of RAM per instance. This comes in addition to the Nebula Server 64 RAM allocation and therefor not recommended.

However, going 64bit (By jBridging) solved Sampltude from crashing upon loading which is very nice, thank you! And now I just wait until Magix releases version 12 of Samplitude this summer! This version will support VST 64 bit.

Thank you, and sorry if we high-jacked the thread :-)
Arne
User Level XI
User Level XI
 
Posts: 170
Joined: Sat Nov 20, 2010 10:31 pm
Location: Bergen, Norway

Re: True revolution on RAM side, 1.3.480 experimental released

Postby himhui » Thu Apr 21, 2011 2:52 pm

Arne wrote:UPDATE:

However, jBridging the server client does not gain any efficiency in RAM use as the jBridge auxhost64 creates its own instance which require another 24 MB of RAM per instance. This comes in addition to the Nebula Server 64 RAM allocation and therefor not recommended.


Thank you, and sorry if we high-jacked the thread :-)


Do you mean localserver doesn't benefit ram reducing when jbridge is in use?

nebula 32 bit x1 instance
Snap20.jpg
neb 32bit
Snap20.jpg (67.89 KiB) Viewed 765 times


neb x64 (jbridge) x1 instance
Snap17.jpg
neb reverb jbridge
Snap17.jpg (48.88 KiB) Viewed 764 times


neb localser x64 x1 instance
Snap18.jpg
localwerver jbridge
Snap18.jpg (75.38 KiB) Viewed 765 times
Last edited by himhui on Thu Apr 21, 2011 3:51 pm, edited 2 times in total.
97v4 /Win7 x64 /64G ram /Nvidia Quadro K620
Reaper 5.28 /X-Touch
Prism Orpheus /RME Babyface Pro
User avatar
himhui
Expert
Expert
 
Posts: 1074
Joined: Sun Mar 28, 2010 6:04 pm

Re: True revolution on RAM side, 1.3.480 experimental released

Postby himhui » Thu Apr 21, 2011 3:34 pm

I think the difference is huge...

14 instances of PCM91 EKO PLATE (@360m)
Attachments
localserver.jpg
localserver.jpg (39.79 KiB) Viewed 758 times
neb rev.jpg
neb rev.jpg (16.83 KiB) Viewed 758 times
97v4 /Win7 x64 /64G ram /Nvidia Quadro K620
Reaper 5.28 /X-Touch
Prism Orpheus /RME Babyface Pro
User avatar
himhui
Expert
Expert
 
Posts: 1074
Joined: Sun Mar 28, 2010 6:04 pm

Re: True revolution on RAM side, 1.3.480 experimental released

Postby giancarlo » Thu Apr 21, 2011 4:16 pm

Arne wrote:UPDATE:

I jBridged the Nebula Server 64 bit client and himhui, you where right, Samplitude does not crash anymore upon loading even with 48 or more instances loaded.

However, jBridging the server client does not gain any efficiency in RAM use as the jBridge auxhost64 creates its own instance which require another 24 MB of RAM per instance. This comes in addition to the Nebula Server 64 RAM allocation and therefor not recommended.

However, going 64bit (By jBridging) solved Sampltude from crashing upon loading which is very nice, thank you! And now I just wait until Magix releases version 12 of Samplitude this summer! This version will support VST 64 bit.

Thank you, and sorry if we high-jacked the thread :-)



why are you jbridging? just use the 32 bits client and 64 bits server....
User avatar
giancarlo
Founder
Founder
 
Posts: 9186
Joined: Mon Sep 21, 2009 10:40 pm
Location: Italy

Re: True revolution on RAM side, 1.3.480 experimental released

Postby Arne » Thu Apr 21, 2011 5:13 pm

Interesting giancarlo, I was not aware that you could use the 32bit Client with 64 bit server ;-)

My problem is that all my "large" Samplitude project crashes upon loading when I save with the Nebula Client 32 bit or Nebula Client 64bit (jbridged). I cannot reopen the project(s).

This problem seems to be either Samplitude RAM depended or number of Nebula instances running. It does not happen when I make a new clean project and install 48 jBbridged Nebula VST 64 bit server clients. It only happens when I insert Nebula into an existing project (or new) which contains other VST`s such as UAD, NTEN`s (Acqua Engine) and others.

Not sure why this is happening, but the work around is to disable all Nebula plugins upon save and activate them manually after loading the project.
Arne
User Level XI
User Level XI
 
Posts: 170
Joined: Sat Nov 20, 2010 10:31 pm
Location: Bergen, Norway

Re: True revolution on RAM side, 1.3.480 experimental released

Postby giancarlo » Thu Apr 21, 2011 5:25 pm

I think you have duplicate nebulas in your system. Check that you have simply a nebula3 and a nebula3 reverb instance in ALL your computer. Than you should be able to open it using localserver without crashes. The application is more or less like a jbridged one.
User avatar
giancarlo
Founder
Founder
 
Posts: 9186
Joined: Mon Sep 21, 2009 10:40 pm
Location: Italy

Re: True revolution on RAM side, 1.3.480 experimental released

Postby Arne » Thu Apr 21, 2011 5:38 pm

I am aware of that, and I do not have any duplicates in my system, only one version of 32 bit and one version (different naming) of Nebula 64bit which I jBridged for a test. Large Samplitude projects crashes upon loading when I have more than 15 active Nebula VST`s inserted. However, when I disable them all upon save and reactivate after loading it seems to work fine.
Arne
User Level XI
User Level XI
 
Posts: 170
Joined: Sat Nov 20, 2010 10:31 pm
Location: Bergen, Norway

Re: True revolution on RAM side, 1.3.480 experimental released

Postby himhui » Thu Apr 21, 2011 7:27 pm

I did a test again with my 32bit Daw +win7 x64 to confirm that:-

1) Neb x32 (localserver) can open up to 48 instances
2) Neb x64 (with jbridge) can open up to 62 instances

Provided that prohect can reopen without crashing, the result may be different from daw to daw
97v4 /Win7 x64 /64G ram /Nvidia Quadro K620
Reaper 5.28 /X-Touch
Prism Orpheus /RME Babyface Pro
User avatar
himhui
Expert
Expert
 
Posts: 1074
Joined: Sun Mar 28, 2010 6:04 pm

Re: True revolution on RAM side, 1.3.480 experimental released

Postby Arne » Sun Apr 24, 2011 4:05 am

I must admit that after hours trying to get the Nebula server to work on a second machine (not running locally) was not a great success story. Both computers are in same network and both machines can fully read each other. No firewalls in between. IP number for both machines identified whereof IP address for remote machine running server are correctly added to XML file client machine. (Tried both server 32 bit and 64 bit on remote machine - but no client connections)

XML file in server folder on machine running server is set with local address 127.0.0.1 or simply .

None of the configurations seem to work with 1.3.480 experimental or earlier version.

I truly wish for an install guide after spending hours going through every thread on this forum related to server issues.

Maybe I have missed something obvious ??
Can someone please provide guidance and help?
Arne
User Level XI
User Level XI
 
Posts: 170
Joined: Sat Nov 20, 2010 10:31 pm
Location: Bergen, Norway

PreviousNext

Return to Working with Nebula

Who is online

Users browsing this forum: daniddd and 4 guests