NetVST Wiki

networking for VST/AU plugins

User Tools

Site Tools


more_about_netvsthost

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
more_about_netvsthost [2017/03/08 16:34]
shane Fix toolbar diagram
more_about_netvsthost [2017/12/12 20:34] (current)
shane [Using NetVSTHost for Macintosh]
Line 3: Line 3:
   * NetVSTHost only handles VST2 plugins, not the newer VST3 standard   * NetVSTHost only handles VST2 plugins, not the newer VST3 standard
   * You can't mix and match 32-bit and 64-bit plugins in a single NetVSTHost instance.   * You can't mix and match 32-bit and 64-bit plugins in a single NetVSTHost instance.
- 
-The present NetVSTHost is really a very quick hack of the open-source VSTHost code. (At least for now. See [[more_about_the_project|this page]] for more about we plan to go with it.) As a result, several of the program'​s original features don't actually work in NetVSTHost, even though you'll still see them in the GUI: 
-  * Although the **Devices** menu allows you to call up dialogs to configure Wave (PCM audio) and MIDI I/O devices, NetVSTHost doesn'​t use either, so only the **Network** menu entry is relevant. 
  
 Once you have configured your network IP address and port number in the Network Parameters dialog, NetVSTHost will save them in the Windows Registry and come up ready to receive network connections each time you start it. (Unless there is a network error, e.g., if you removed a network adapter. Just open the Network Parameters dialog again and re-configure,​ and you should be good to go.) Once you have configured your network IP address and port number in the Network Parameters dialog, NetVSTHost will save them in the Windows Registry and come up ready to receive network connections each time you start it. (Unless there is a network error, e.g., if you removed a network adapter. Just open the Network Parameters dialog again and re-configure,​ and you should be good to go.)
Line 22: Line 19:
  
 {{::​2017-03-06_14-39-01.png|}} {{::​2017-03-06_14-39-01.png|}}
 +
 +The **Audio/​Network switch** (loudspeaker icon) lets you switch between sending sound to the computer'​s own audio output or across the network. For network operation, this button should **NOT** be pushed in.
  
 Once you have opened at least one plugin (effect or synth), several of the buttons on the NetVSTHost toolbar will appear, and you can use them as shown below. Once you have opened at least one plugin (effect or synth), several of the buttons on the NetVSTHost toolbar will appear, and you can use them as shown below.
  
-{{::vh_tbar.png|}}+{{:vst_tb.png|}}
  
 ===== Chaining VSTs ===== ===== Chaining VSTs =====
Line 49: Line 48:
 The diagrams and discussion above concentrated on synthesizers,​ and in this respect the diagrams are a little misleading. The words "PCM audio from network"​ should really be "MIDI event data from network",​ because synthesizers accept MIDI events and produce audio. Effect plugins, in contrast, accept unprocessed audio and produce processed audio. The diagrams and discussion above concentrated on synthesizers,​ and in this respect the diagrams are a little misleading. The words "PCM audio from network"​ should really be "MIDI event data from network",​ because synthesizers accept MIDI events and produce audio. Effect plugins, in contrast, accept unprocessed audio and produce processed audio.
  
-When you have configured your system of VST chains to act like a synthesizer,​ use the **NetSynth** plugin ​(**firstSynth** on a Mac) in your regular DAW to access it. As long as you configure NetSynth with the same IP address and port number as the NetVSTHost instance containing your chain, you should be able to send out MIDI and hear/record the resulting sound.+When you have configured your system of VST chains to act like a synthesizer,​ use the **NetSynth** plugin in your regular DAW to access it. As long as you configure NetSynth with the same IP address and port number as the NetVSTHost instance containing your chain, you should be able to send out MIDI and hear/record the resulting sound.
  
-When you set up a system of VST chains to act like one large effect, taking in audio and returning processed audio, use the **NetFilter** plugin ​(**firstFilter** on a Mac) in your DAW. As with NetSynth, you must configure NetFilter with the same IP address and port number as the NetVSTHost instance containing your effect chain.+When you set up a system of VST chains to act like one large effect, taking in audio and returning processed audio, use the **NetFilter** plugin in your DAW. As with NetSynth, you must configure NetFilter with the same IP address and port number as the NetVSTHost instance containing your effect chain.
  
 ===== Using multiple NetVSTHost instances on one PC ===== ===== Using multiple NetVSTHost instances on one PC =====
Line 64: Line 63:
  
 ===== Using Virtual PCs on a Macintosh ===== ===== Using Virtual PCs on a Macintosh =====
 +**See next section for a simpler approach.**
 +
 Virtual PC software such as [[http://​www.vmware.com/​products/​fusion.html|VMWare Fusion]] and [[https://​www.parallels.com/​desktop|Parallels Desktop]] allows running an instance of Microsoft Windows as an application program on your Mac. These systems install a virtual local-area network (VLAN) on your Mac, in which each virtual PC, and your Mac itself, appear to have a separate network adapter, all connected by a virtual network hub. Virtual PC software such as [[http://​www.vmware.com/​products/​fusion.html|VMWare Fusion]] and [[https://​www.parallels.com/​desktop|Parallels Desktop]] allows running an instance of Microsoft Windows as an application program on your Mac. These systems install a virtual local-area network (VLAN) on your Mac, in which each virtual PC, and your Mac itself, appear to have a separate network adapter, all connected by a virtual network hub.
  
Line 70: Line 71:
 Each virtual PC program has its own way of setting up VLANs, so you may have to consult your system'​s documentation to really understand what's going on. With VMWare Fusion, for example, each VLAN will have its own distinct range of IP addresses, of the form "​192.168.X.Y"​ where X and Y are numbers less than 255. All nodes on the network (all virtual PCs plus your Mac) will be assigned the same value of X and different values of Y. Each virtual PC program has its own way of setting up VLANs, so you may have to consult your system'​s documentation to really understand what's going on. With VMWare Fusion, for example, each VLAN will have its own distinct range of IP addresses, of the form "​192.168.X.Y"​ where X and Y are numbers less than 255. All nodes on the network (all virtual PCs plus your Mac) will be assigned the same value of X and different values of Y.
  
-~~DISCUSSION~~+===== Using NetVSTHost for Macintosh ===== 
 +The new Mac //​NetVSTHost//​ app provides a simpler and cleaner way to run Windows-only VSTs on a Mac. 
 + 
 +Virtualization solutions like [[http://​www.vmware.com/​products/​fusion.html|VMWare Fusion]] and [[https://​www.parallels.com/​desktop|Parallels Desktop]] eat up a lot of RAM and CPU power, because they have to run a full Windows operating system as well as //​NetVSTHost.exe//​. The Mac version of //​NetVSTHost//​ uses [[https://​www.winehq.org/​|Wine]] to implement only a few of the most critical parts of Windows, which is more efficient. 
 + 
 +Some VST plugins might require additional Windows components (DLLs) which are not included in the Mac //​NetVSTHost//​ app bundle, and hence might fail to load, or might not run correctly. In such cases, a full virtualization solution (or using a separate PC) may be your only choice. 
 + 
 +Running //​NetVSTHost//​ on the same Mac as your DAW is //a way// to use Windows-only VST plugins inside a Mac DAW like Logic Pro X, but using a separate Windows PC is //a better way//, for two reasons: 
 +  - Running under a full Windows installation means your plugins will always work 
 +  - Running plugins on a separate PC reduces the CPU and memory load on your DAW machine (in this case, your Mac)
  
more_about_netvsthost.1488990849.txt.gz · Last modified: 2017/03/08 16:34 by shane