AUDIOGRIDDER

AudioGridder Server runs on a computer hosting your effect and instrument plugins. On your workstation, on which you run your DAW, you use the AudioGridder FX or instrument plugin to access your plugin library over the network. The plugin is looking for available servers on your network and once connected allows you to create insert chains or load instruments. Midi and audio data from your DAW will be streamed over the network, processed on the server and streamed back.

To control a plugin and adjust its settings, AudioGridder is capturing the plugin UI on the server side and streaming it to the client. At the same time it is capturing mouse and keyboard events on the client and replaying them on the server.

Alternatively, AudioGridder supports a Generic Editor, that allows for direct access to the parameters of a plugin.

If you have problems, find bugs or have questions, you can start a discussion thread at the AudioGridder GitHub page.

If you report a new issue, please be as precise as possible. To identify the root cause of an issue, it is necessary to be able to reproduce it or at least get some conclusions from the info you provide.

• Report only one issue at a time, if you have multiple problems, please create multiple issues.
• Minimize the log files:
  • Stop the server and the DAW
  • Wipe all AudioGridder log folders (server and plugins, see Diagnostics Locations).
  • Enable tracing (read more…). // This is important for analyzing issues.
  • Start the server.
  • Start the DAW.
  • Load only the minimal amount of plugins needed to run into the problem you have.
  • Take only the actions that lead to the problem you have.
• Create zip archive(s) of
  • log folder(s)
  • core file (macOS/Linux, on Windows core files will be written to the log folders)
  • crash reports (on macOS, see Diagnostics Locations)
• If the files you want attach are to large for an issue on GitHub, please follow Submitting Large Files.

Read More

The server supports VST2, VST3 and AudioUnit (on macOS only) plugin formats and is available for macOS and Windows. There are multiple possibilities for your setup. It is suggested, that you dedicate each server instance to a single remote DAW workspace. That is because each server can only stream a single UI at the same time.

You can run multiple parallel UI user sessions on macOS and Windows. Setup a user for each remote workspace, create a UI session (via VNC, note that RDP might not be working reliably with AudioGridder) and run a separate server instance in each session. You need to assign a different server ID to each instance (in the server settings). In your DAW you can address each server instance from the AudioGridder plugin via “server[:ID]” notation.

You can also run multiple servers within your network and access different servers from your DAW at the same time (in different plugin instances).

Read More

The plugin is currently supported on macOS, Windows and Linux as VST2, VST3 and AudioUnit (on macOS only). Note: AAX is likely never coming, as AVID does not seem to support open source projects unfortunately. See the compatibility section for a workaround.

With the AudioGridder FX plugin you can plug a remote insert effect chain into your DAW’s channel inserts. From there you can insert any FX plugin available on the connected server.

Instruments work similarly. Create a software instrument track in your DAW and select the AudioGridder plugin as instrument. Now you can load any of the instrument plugins available on the server.

Each AudioGridder plugin instance will connect to a single remote server instance. But each separate loaded plugin instance can connect to a different server, so you can connect to multiple servers from your DAW at the same time.

Read More