SoundGrid Studio and StudioRack - Support Notes

Last updated on: 7/6/2020 12:01:01 PM

This page presents existing issues, some with workarounds, that we are working to solve in SoundGrid Studio and StudioRack. It also summarizes key improvements and main issues solved in the SoundGrid Studio application and StudioRack plugin. We will update this page on an ongoing basis as more issues are solved. We encourage you to contact Waves Support and report any issue you may encounter.

Table of Contents:

Plugin Compatibility

We recommend using the latest compatible plugin version:

  • SoundGrid Studio and StudioRack v11 support v11 and v10 plugins only.
  • SoundGrid Studio and StudioRack v11 support v10 plugins on the following operating systems only: Windows 10, macOS 10.13.6 and macOS 10.14.6.
  • SoundGrid Studio and StudioRack v9 support v10 and v9 plugins, as well as these third-party plugins.

 

Known Issues in SoundGrid Studio (Current Version)

We are currently working on solutions for these issues. We will announce fixes and update the page as more issues are solved. For some of the issues, we recommend workarounds below.

  • When using a SoundGrid Connect setup with a Non-SoundGrid IO, do not manually set the SoundGrid Driver’s ‘Network Driver Buffer’ to 104, this will result in clicks and pops.
  • SoundGrid Studio + eMotion ST 16/32/64 Ch. Mixer licenses will not activate the legacy V9 eMotion ST Mixer within SoundGrid Studio V9. To use the legacy V9 eMotion ST Mixer, register a free SoundGrid Studio + eMotion ST 8 Ch. Mixer license and activate it in the ‘Licenses’ page of Waves Central.
  • While setting SoundGrid Studio to stream audio between your DAW and a SoundGrid audio interface without a SoundGrid server, Outputs 1 & 2 of your interface will be reserved for the eMotion ST mixer’s Control Room, which cannot pass sound without a server. Workaround: Manually patch Channels 1 and 2 of the SoundGrid Driver to Outputs 1 & 2 of your SoundGrid audio interface, in SoundGrid Studio’s Patch page > Device to Device view. For more information refer to this article.
  • If ‘Auto-Config’ is initiated to set up audio streaming between your DAW and a SoundGrid audio interface without a SoundGrid server, a prompt will appear asking you to select where you wish to monitor from. Selecting ‘None’ will patch Channel/s 3 (and above) of the SoundGrid Driver to Output/s 1 (and above). Workaround: Manually patch Channel/s 1 (and above) of the SoundGrid Driver to Output/s 1 (and above) of your SoundGrid audio interface, in SoundGrid Studio’s Patch page > Device to Device view. For more information refer to this article.
  • While your DAW is running and assigned to the SoundGrid Driver or using the StudioRack plugin; Quitting SoundGrid Studio, re-configuring, disconnecting and reconnecting SoundGrid Interfaces from the Network may result in a CPU overload in your DAW and unexpected behavior. Workaround: before any of these actions, always quit your DAW and relaunch thereafter.
  • Changing the Sample Rate of the session in SoundGrid Studio will crash Ableton Live if it the SoundGrid Driver is selected as the ASIO driver.
  • The Solo buttons on Monitor and Auxiliary channels are non-functional.
  • The StudioRack layer’s meter displays are not affected by the U/I settings selected in SoundGrid Studio Setup page.
  • MyMon controller cannot control the StudioRack mixer layer in SoundGrid Studio.
  • Loading a SoundGrid Studio Session via StudioRack will not load the ‘Tempo Sync’ button on the top bar. It needs to be engaged manually.
  • In macOS, SoundGrid Studio’s ‘Full Screen’ button may not appear until (any) device menu is accessed in the ‘Setup’ page inventory.
  • If SoundGrid Studio is open while restarting your computer, it will prompt to save the session (even if unused or unchanged).
  • Mackie Control is not yet fully supported in SoundGrid Studio. This controller may disappear from the list or cause the ‘Link’ layer to appear twice in the eMotion ST Mixer, when toggling between fader banks.
  • SoundGrid Studio Application introduces high local memory consumption, even with minimal processing requirements and channel count.
  • Clicking the ‘Gear’ icon on a non-SoundGrid interface assigned for a SoundGrid Connect setup, will result in a momentary disconnection of both the non-SoundGrid interface and the SG Driver form the I/O devices inventory rack.
  • Certain Soundgrid IO’s may display input and output channels groups (i.e. Mic/Line, Mic/Line/DI, Digital) in a different order in the Patch than in the Route layer of the mixer.
  • eMotion ST Mixer’s Control Room controls (Source, Mono, Mute, Dim and Monitor Select) are not yet assignable to a MIDI controller or to the ‘User Keys’ utility.
  • When disconnecting a TP-Link USB to Ethernet adapter, the SoundGrid network inventory will continue to display that the LAN port and all assigned devices are still connected. Workaround: Click ‘Rescan Ports’ to refresh the inventory status.
  • The ‘Toggle View: Mixer 1’ User Key is not functional in macOS systems.
  • Currently there is no option to insert plugins on the ‘Main’ channel in the standard Mixer layers. Workaround: To insert plugins on the ‘Main’ channel, create a ‘Custom’ layer and display the Main channel, the insert slots will now be displayed.
  • Switching the Mixer Configuration from 16/32/64 channels to 8 channels will lose all Talkback routings to Groups, Auxiliaries and Monitors.
  • After an unexpected shut-down in macOS, SoundGrid Studio will relaunch in a ‘Link Down’ state. Workaround: Quit properly and relaunch – it will load with ‘Link up’.
  • When assigning a mono Mic input as the source to Headphones 1 to 4, the signal will be heard in the left or right channel only and will not be summed to stereo.
  • After assigning a Shared Driver (managed by a different SoundGrid system) in the Setup page and clicking ‘OK’ to apply the same clock source to both systems, the ‘Shared to’ Driver does not become the local clock Master. Workaround: Manually set the ‘Shared to’ driver as Master.
  • After assigning a Shared Driver (managed by a different SoundGrid system) in the Setup page, the Shared driver will appear Red (instead of Orange) but will pass audio and SOE clock successfully. This only happens when the driver is sharing 32 channels.
  • In 32 and 64 channel configurations of SoundGrid Studio, while viewing the ‘Monitor 9-16’ Mode, the labeling above the ‘Main’ fader used for flipping faders is labeled 1-8 instead on 9-16.
  • If a channel is patched to several destinations, these patch assignments cannot be disconnected individually from the ‘Route’ channel mode, Workaround: disconnect them all at once via the ‘Disconnect all’ option in ‘Route’ channel mode, or via the patch.
  • Using the SoundGrid Driver to record at 96kHz with an A&H M-Waves card via any Waves Host application may introduce audible artifacts to the recording.
  • When configuring a DiGiGrid DLI/DLS in SGP mode, with two DigiLink interfaces bridged to the SoundGrid driver (via one or both ports), the analog inputs of the second DigiLink I/O might not be recognized in the DLI/DLS control panel.
    Workaround: Power the DLI/DLS and DigiLink interfaces off and back on again, while the SoundGrid Studio application is running. Once the DLI/DLS is back online, the analog inputs of the second DigiLink I/O will be available. This will need to be performed upon each instantiation of SoundGrid Studio.

 

Known Issues in StudioRack (Current Version)

  • In Windows, using Protools’ ‘Enable Automation’ keyboard shortcut (Ctrl+Win+Alt+Click) will display a blank white menu. Workaround: Use the Protools’ main Automation dialog to enable/disable automation for controls.
  • ‘Bypass’ and ‘Input Gain’ automation data created and saved with StudioRack v9 cannot be recalled with StudioRack v11. You may have to recreate the automation for these parameters.
  • The on/off control of each insert slot in StudioRack is currently not MIDI assignable. All other controls are.
  • StudioRack does not support Protools ‘Global’ grouping of controls between instances of StudioRack and the plugins populating it, except for StudioRack’s input and Output controls.
  • Abbey Road TG Mastering Chain’s Meter Bridge component is not supported in StudioRack.
  • Using Renaissance Equalizer/ Channel’s Light/Dark skins in ‘All band’ view, controls are not assignable to Macros. Workaround: Use Renaissance Equalizer / Channel Legacy skin, or the one-band view in the Light/Dark skins.
  • Editing macro control ranges in JJP signature series is not possible.
  • GTR3.5 controls assigned to macros in StudioRack are not marked with a red frame.
  • MultiMod and MetaFilter plugins are currently not supported in StudioRack.
  • StudioRack’s ‘AUTO’ monitoring source selection feature (to toggle between ‘Input’ and ‘Playback’ modes with DAW transport) only works in host applications that support the Mackie HUI protocol. The following hosts applications do not support Mackie HUI: Bitwig Studio and Ableton Live.
  • StudioRack’s ‘Auto’ setting for toggling input and playback modes will work, but with a delay while using Pre-roll or Post-Roll settings. For instantaneous automatic switching, do not use pre/post roll.
  • Duplicating tracks that include StudioRack Instances in SoundGrid mode in your DAW, will not apply the low latency monitoring ‘Group’ assignment of StudioRack. Workaround: assign duplicated tracks to ‘Group’ manually.
  • If StudioRack is loaded in the VST2.4 format, then switched to VST3, or both formats are loaded simultaneously, StudioRack will not communicate with the SoundGrid Studio application. Workaround: remove StudioRacks and load all as VST3 and it will communicate with SoundGrid Studio.
  • On Windows, if Reaper is launched via the “Reaper (x64) (show audio configuration on startup)” desktop shortcut, even if a full SoundGrid network is configured to offload StudioRack processing, stereo instances of StudioRack will load in ‘Native’ processing mode instead of ‘SG’. Workaround: launch Reaper from the (other) “Reaper (x64)” desktop shortcut.
  • In Logic Pro X, only 126 voices are available for StudioRack instances to offload plugin processing to a SoundGrid Server, even though StudioRack indicates there are 128 voices.
  • Bouncing/rendering audio with StudioRack in SoundGrid processing mode in Ableton Live and Bitwig Studio will result in corrupted audio. Workaround: Switch All instances of StudioRack to native processing. In Ableton Live you can also choose to bounce/render audio in Real time. https://help.ableton.com/hc/en-us/articles/209067709-How-to-render-audio-in-real-time.
  • Switching StudioRack in Ableton Live from SoundGrid to Native processing mode will result in StudioRack’s automation being switched off. Take note of this before performing an offline bounce (turn StudioRack automation back on.)
  • Computer performance may be affected when automation data for multiple controls and multiple instances is being read, when using StudioRacks in SoundGrid processing mode.
  • Loading StudioRack Multi-Mono instances in Pro Tools is not supported.
  • Once a plugin is moved from StudioRack’s main rack to a Split rack and the action is undone, the plugin will not be removed from the Split Rack and result in plugin duplication.

 

Additional Support Notes

The following are not bugs. Rather, they are features you should be aware of when operating SoundGrid Studio and StudioRack:

  • Unlike SoundGrid Studio v9, SoundGrid Studio v11 requires a license (even without assigning a Server or using the mixer). You can register a free “SoundGrid Studio + eMotion ST 8 Ch. Mixer” license, or purchase 16/32/64 channel licenses on the SoundGrid Studio page. Once registered, you must activate this license via Waves Central, before you can use SoundGrid Studio to patch audio from your IO to the Driver and back.
  • Please note: StudioRack is not supported in SoundGrid mode in Pro Tools HDX, HD or HD Native.
  • Command Q and Alt F4 do not quit the application, and will only close the window. Press ‘Quit’ in the Setup page to Quit the application.
  • Control Room and Headphones 1 to 4 and Talkback input/output assignments are not reflected in the Patch pages and can only be viewed, assigned or unassigned within the Control Room interface.
  • SoundGrid Connect is intended for mixing purposes only. It is not supported or intended to be used for recording with real time monitoring of plugins (latency will be introduced if used for recording) or to be used to aggregate between SoundGrid and Non-SoundGrid devices, doing so might introduce audio corruptions. We recommend not to have both SG Connect and SoundGrid interfaces assigned simultaneously. If you choose so, the interfaces must be synced by an external clock, such as WC.
  • Sessions created and saved in SoundGrid Studio v9.7 will not open in SoundGrid Studio v11, old sessions will need to be rebuilt in SoundGrid Studio v11.
  • Only 64bit 3rd party plugins can run in SoundGrid Studio and StudioRack v11 and above. 32bit 3rd party plugins are not supported.
  • StudioRack can report 2050 automation lanes to a DAW for itself and the plugins that populate it. In order to reserve automation lanes for controls that are important to you, avoid globally activating all plugin controls at once, and activate them as needed. StudioRack’s eight Macro controls are always available.
  • Apogee Symphony MK1 is not supported with DLS\DLI interfaces in SGP mode.
  • Presets are saved in the session as part of the SoundGrid Studio ‘*.sgst’ session and not as separate .xml files on your local computer file system, as there were in SoundGrid Studio V9.
  • After removing all automated plugins from StudioRack, Protools’ automation list will still be populated by the previous controls. Workaround: remove and re-insatiate StudioRack.
  • The Bucket View in the CLA MixHub is not supported in SoundGrid Studio or StudioRack.

 

Fixed Known Issues in StudioRack

  • Applying ‘Undo’ on a Macro control movement might apply only to the Macro control itself, and not the control behind it. Workaround: Touch the Macro control again and the control behind it will apply the same valueFixed in 11.0.65.145.
  • StudioRack input gain knob automation can be written in Ableton Live, but not read – Fixed in 11.0.65.145.
  • Studio One on Windows will crash after closing StudioRack’s interface with its ‘Macro Edit’ window open. Workaround: close StudioRack’s Edit Window before closing the plugin interfaceFixed in 11.0.65.145.
  • Loading a preset may reset channel selection of StudioRack’s low-latency input, while in SoundGrid processing mode – Fixed in 11.0.65.145.
  • Switching StudioRack in Cubase from SoundGrid to Native processing mode will result in additional automation lanes being displayed – Fixed in 11.0.65.145.
  • In some DAWs, disabling StudioRack while in ‘Input’ mode, will result in a stuck audio buffer – Fixed in 11.0.65.145.
  • When a Multiband or Parallel Split Rack is loaded in to another Split rack, the insert LED will be yellow and wrongly indicate that you are in SC mode – Fixed in 11.0.65.145.

 

Was this article helpful?