Login

The Nebula tip of the month (#49 - July 2014)

Nebula tips and tricks

The Nebula tip of the month (#49 - July 2014)

Postby Support » Fri May 30, 2014 8:31 pm

Installing and running Nebula Server in LAN Mode
Tip applicable to:
Product(s): Nebula3 FREE, Nebula3 Server.
OS(s): Windows, OSX.
Plug-in format(s): VST, AU.
Plug-in architecture(s): 32 bits, 64 bits.


Introduction
Nebula Server is a stand alone application for Windows and OSX that work together with Nebula3 Server client plug-in. Nebula3 Server client plug-in loaded into your audio or video host will talk and share resources with Nebula Server stand alone application like others client/server network applications. Nebula Server can run in the same computer than Nebula3 Server client plug-in and work as a x64/x86 architecture bridge or in a second extra computer, a server computer, sharing CPU, RAM and HDD resources through a LAN network.

IMPORTANT: Acustica Audio not provide any networking configuration support, and for this reason we recommend to contract a computer networks specialist if you don't have the knowledge.

NOTE: Server computer should x4 powerful than your client computer. Please avoid legacy or old computers as a server.

How it works
On "local" client computer, you will run your sequencer and inside sequencer you will run Nebula (Nebula3 Server client plug-in). Nebula will try to find a Nebula Server if IP address is correct and the PORT is open. If Nebula find a Nebula Server your emulation presets will be loaded, for this instance, in the "remote" server computer. We call this feature Nebula in LAN mode or Nebula in client mode.

IMPORTANT: Due you can make alias in VST format you can duplicate Nebula3 Reverb (.DLL, .VST and .XML files) and make one for load emulation preset into the client "local" computer (no IP/PORT tags) and other to load into server "remote" computer (adding IP/PORT tags)

NOTE: Each Nebula3 Client instance will go from client computer to server computer and back from server computer to client computer. This create a heavy load in LAN interfaces.

RECOMMENDATIONS:
. Use fixed IP is better less broadcasting LAN issues.
. Use good quality (Intel) NICs.
. Use good quality CAT6/7 cables.
. Avoid to much networking hardware, best situation should be a cross-cable from server to client.
. Use good quality switches if you must use it.
. Use only GigaLAN hardware and cables.
. Avoid firewalls.
. Disable other network adapters like: wireless, Bluetooth, or Thunderbolt, etc.

Installation and configuration
1. Install Nebula Server in "remote" server computer (full set-up of Nebula3 Server package).
NOTE: You don't need to request a license for this computer but you must to install "local" client license to load protected emulation presets.
2. Install emulation presets in the "remote" server computer. NOTE: Nebula Server is not compatible with alternativedatapath.
3. Install Nebula3 Server package in "local" client computer. NOTE: You should install your license in this computer.
4. Set-up "local" client computer Nebula Reverb MAST page .XML file and add PORT and IP address. IP address should be the correct one from the "remote" server computer.
Use PING "IP Address" command in Windows CMD or ping C -5 "IP Address" in OSX terminal to check you can rich your "remote" server computer IP address (remember to avoid firewalls). NOTE: for more information about MAST page .XML file read MAST page F.A.Q.: viewtopic.php?f=36&t=558.

Image

Image

5. Set-up Nebula Server .XML file in the "remote" server computer. Add correct PORT and IP address parameters that should be the server computer port and IP address.
Use PING "IP Address" command in Windows CMD or ping C -5 "IP Address" in OSX terminal to check you can rich your "local" client computer IP address (remember to avoid firewalls). NOTE: for more information about MAST page .XML file read MAST page F.A.Q.: viewtopic.php?f=36&t=558.

6. Run Nebula Server in "remote" server computer.

Image

7. Run Nebula3 Server client plug-in in "local" computer into your sequencer. If a Nebula Server is found your Nebula instance will work in LAN mode or in "client mode". Nebula will request Nebula Server to load emulation preset in the "remote" server computer instead of load it locally.

Image

8. In the "local" client computer go to Nebula3 Server client plug-in > DISK > Server and you can check if Nebula can see a Nebula Server. N/A means NO Nebula Server and you Nebula is still working locally.

Image

Windows Server/Client example setup parameters:

"Local" client computer
. Windows 8.1 x64
. IP: 192.168.2.10
. PORT: 6000
. Mask: 255.255.0.0
. Gateway: 192.168.2.1
. Firewall disable
. CAT6 cross-cable
. No Switch
. No DHCP (Dynamic Host Configuration Protocol)
. IP manual

"Remote" server computer
. Windows 7 HP SP1 x64
. IP: 192.168.2.11
. PORT: 6000
. Mask: 255.255.0.0
. Gateway: 192.168.2.1
. Firewall disable
. CAT6 cross-cable
. No Switch
. No DHCP (Dynamic Host Configuration Protocol)
. IP manual

OSX Server/Client example setup parameters:

"Local" client computer
. OSX 10.10.4
. IP Address: 192.168.2.10
. PORT: 6000
. Subnet Mask: 255.255.0.0
. Router: 192.168.2.1
. Firewall disable
. CAT6 cross-cable and Thunderbolt cross-cable
. No Switch
. No DHCP (Dynamic Host Configuration Protocol)
. IP manual

"Remote" server computer
. OSX 10.10.4
. IP Address: 192.168.2.11
. PORT: 6000
. Subnet Mask: 255.255.0.0
. Router: 192.168.2.1
. Firewall disable
. CAT6 cross-cable and Thunderbolt cross-cable
. No Switch
. No DHCP (Dynamic Host Configuration Protocol)
. IP manual

Conclusion
Networking connection between Nebula Client and Nebula Server is possible in OSX and Windows using standard networking hardware but also with thunderbolt point to point cables.
Note Nebula3 Server will generate high consumption and load of the available network bandwidth due each Nebula instance loaded in client "local" computer will send data to the server "remote" computer and server "remote" computer will send it back again to the client "local" computer and for that reason we recommend to measure the system latency and CPU load in order to setup a correct (big) Nebula DSPBuffer value.
User avatar
Support
Expert
Expert
 
Posts: 3178
Joined: Mon Feb 24, 2014 11:33 am
Location: Lodi, Lombardia, Italy.

Return to Nebula tips

Who is online

Users browsing this forum: No registered users and 1 guest