Audio connectivity
How do I set up my system to run the MelodyneBridge or the ReWire slave mode?
If you run Melodyne as a MelodyneBridge client or as a ReWire slave, audio is streamed from one application to another in real time. Therefore Melodyne offers a set of configuration parameters which you will find in the Hardware Preferences panel whenever Melodyne is running as a client or slave. These parameters should be adapted to the hardware configuration of the host application:
- The first button allows you to reconnect to the host application, which is useful if the connection has been lost for any reason (as might be the case, for example, if for any reason the streaming has ceased to function or the MelodyneBridge has become ‘inactive’ despite the fact that Melodyne is running as a bridge client).
- The buffer size is the most important parameter. It should always be larger than the I/O buffer of the host. If they are the same size or Melodyne’s buffer is smaller, it may cause stuttering of the audio, dropouts or serious disturbances in the signal. Enlarging Melodyne’s buffer size here does not result in additional latency though the larger the buffer, the longer Melodyne takes to synchronize to the host application.
- The buffer count defines the number of buffers used to communicate between Melodyne and the host. Only increase this value if you need to increase the buffer preload (see below) or if you get dropouts on specific tracks while running multiple bridge plug-ins simultaneously.
- To enable the MelodyneBridge plug-in to run without [plug-in] latency, Melodyne renders the audio a few buffers earlier than requested by the host application. The buffer preload defines the number of buffers Melodyne renders in advance, with the value 2 being a good choice in most cases. Increase this value if you get dropouts or to handle system load peaks. In that case, you may also try to increase the buffer count.
- The File Cache parameter has the same significance here as when Melodyne is running in stand-alone mode: it defines the number of samples Melodyne loads into RAM when streaming [an audio file / audio files] from the hard drive.
- It may also be a good idea to switch off any of Melodyne’s MIDI options when the program is running as a slave or client.
Setting up the host application
Even though it is not normally necessary to take any special measures to configure the host application, we have included some detailed configuration tips for Cubase, Sonar and Logic on separate pages. In general, it’s advisable to use large audio I/O buffers, to give the host a high priority and to switch off multiprocessor support within the host application, even though your computer might be equipped with multiple processors.
