eMotion LV1 Live Mixer – Support Notes

Last updated on: 3/4/2019 12:37:46 PM

This page summarizes key improvements and main issues solved in the latest version of the eMotion LV1 live mixer. It also presents existing issues, some with workarounds, that we are working to solve:

We will update this page on an ongoing basis as more issues are solved. We encourage you to contact Waves Live Support and report any issue you may encounter.

Fixed issues from Earlier LV1 Versions

Devices and Network

  • Following a firmware update, some devices (I/Os or servers) were not automatically assigned after restart. Their status displayed FREE instead of ON – Fixed in v10.
  • Control surfaces using Mackie protocol may have shown a status of N/A while they were actually working as expected. Some control surfaces may have lost focus while toggling OS focus to another supporting host application - Fixed in v10.
  • I/O devices did not always sync when sessions with multiple device assignments were loaded – Fixed in v9.14.
  • Second control surface sometimes showed a mismatch between labels and faders – Fixed in v9.14.
  • The wrong master clock device was occasionally selected when a session was loaded, or when a device was reassigned – Fixed in v9.14.


Sessions, Scenes & Presets

  • When recalling scenes, internal routings and the on/off settings of auxiliary sends may not load correctly as saved. New audio routings will not be activated and will not pass audio – Fixed in V10.0.57.88.
  • When toggling through multiple scenes, some channel parameters may not be recalled correctly – Fixed in V10.0.57.88.
  • Specific scenes appear to be locked; new scene parameters cannot be saved using the ‘Store’ function – Fixed in V10.0.57.88.
  • Some sessions created in LV1 v9 did not load in LV1 v10 – Fixed in the latest v10­ update.
  • Plugins may have not loaded from a rack preset on a talkback channel – Fixed in v10.
  • When loading a session created in the LV1 32- or 16-channel configuration onto a 64-channel configuration, the Matrix channels may have not reset from their previous state – Fixed in v10.
  • Session notes did not load on Mac El Capitan and Sierra – Fixed in v10.
  • Some sessions loaded with wrong mixer settings (fader positions, Sends on/off etc.) – Fixed in v9.14.0.354.
  • Input channels and sidechains occasionally lost their patching after a session was loaded – Fixed in v9.14.
  • Aux busses occasionally failed to pass audio after a session was loaded – Fixed in v9.14.
  • Talkback assignment presets were occasionally lost after a session was loaded – Fixed in v9.14.
    Please note: eMotion LV1 v9.14 will recall only the last active talkback assignment preset from sessions originating in earlier LV1 versions.
  • "Recall Scene” would change all preamp settings for a device, even if only one preamp channel was modified – Fixed in v9.14.
  • Rack Preset files saved in MultiRack or StudioRack can’t be imported into LV1 – Fixed in v9.14.0.113.
  • The most recent channel parameters will not be not saved in the session if the channels are not in the scope of the most recently loaded scene or are in ‘recall safe.’ – Fixed in v9.14.0.113.
  • External inserts may lose their patching after a session is loaded – Fixed in v9.14.0.113.



  • CUE bus output could distort after recovering from a crash. (Mac Only) – Fixed in v10.
  • Collapsible/expandable plugins were not automatically centered in the Plugin Pane after collapsing/expanding the plugin interface – Fixed in v10.
  • Rack Mode graphics could disappear after you toggle the layers while aux sends are in ‘sends on faders’ mode – Fixed in v10.
  • Using multi-touch within the Scheps Omni Channel interface could have led to unresponsive interface) – Fixed in v10.
  • Delay compensation did not always function properly on mix busses following routing or patch – Fixed in v9.14.
  • Memory and system resource overflows sometimes led to sluggish control behavior and application hangs – Fixed in v9.14.


LV1 Software Freezes or Quits

  • Rapidly instantiating one of the plugins (Stomp Volume/ Stomp Octaver/ PS22) on multiple channels (alt + instantiate), may cause a server crash – Fixed in V10.0.57.88.
  • In some cases control surfaces using Mackie protocol became unresponsive. LV1 could crash when removing the device from the Inventory. (Mac Only) – Fixed in v10.
  • While GTR Stomp 6 or GTR ToolRack were open for editing, they covered a part of the plugin rack. Clicking on another plugin in the chain could cause the LV1 to quit – Fixed in v10.
  • Using a user-assignable key to view a specific channel while a control’s value box was open for text entry—on a plugin or on a Mixer/Channel view— could have caused the LV1 to quit – Fixed in v10.
  • Engaging both the ALT and the CTRL keys at the same time on the Mixer window caused LV1 to freeze – Fixed in v10.
  • Fast toggling between Scenes in a session containing Scheps Omni Channel plugin could cause the Server or the Lv1 Application to stop processing or unexpectedly quit – Fixed in v10.
  • Disabling Scheps Omni Channel in a channel rack while eMo D5 Dynamics was used as an insert of the Scheps Omni Channel, LV1 may hang or crash. (Mac Only) – Fixed in v10.
  • Re-launching the LV1 right after it was closed may cause the application to quit upon startup – Fixed in v9.14.0.113.


Known Issues in eMotion LV1 – Fixes TBA

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


Sessions, Scenes & Presets

  • Recalling a scene that changes the internal routing of a channel may cause an audio glitch if that channel has latency (due to routing or plugins).
    Workaround: Set internal routing to Recall Safe and/or remove it from the scope of a scene.
  • No Scope or Recall Safe for direct output source selection, even though these can change with scene change.
  • When an input preamp is assigned to more than one channel, a Gain control value change will affect a channel that is set as Recall Safe if any of the other channels are not set as Recall Safe.
  • High-latency plugins may produce small clicks when bypassed from a scene parameter change.


LV1 Software Freezes or Quits


In all the following cases, audio will continue. Once the LV1 software recovers, a recovery message will appear allowing the user to time when re-connection occurs. Re-connection will cause the LV1 to mute for a few seconds.

  • Adding or enabling multiple Flux plugins (using Alt or Link) may cause the LV1 to quit. We recommend that you avoid multiple operations on Flux plugins.
  • Mac El Capitan and Sierra only:
     -  LV1 may freeze when left On unattended for hours. In such a case, restart the LV1 software.
     -  LV1 may quit when a primary or extension monitor is disconnected or shut down during operation.



  • Filter "link" breaks when "Channel Filters" are assigned to Scheps Omni Channel.
    Workaround: For "link" operation, link the plugin's controls rather than the channel controls.
  • In Channel view, Scheps Omni Channel's gain-reduction will not show if eMo D5 Dynamics is inserted in the rack.
  • V10 Mono-to-Stereo plugins will duplicate their left output to their right output instead of providing actual left and right stereo output.
  • On Windows, if a high contrast theme is selected, some controls may appear unresponsive.
    Workaround: Windows' High Contrast themes are not supported in LV1. Under Settings > Ease of Access > Color & high contrast select 'None' as the 'High contrast' theme.
    If color adjustment is necessary for operation, work with ‘color filters’ (like grayscale, invert, etc).
  • If a third-party plugin is opened for editing before any Waves plugin on the same channel has been opened, the Channel window display will appear corrupted in the Channel window.
    Workaround: To edit the plugin, go to Channel view, open any Waves plugin for editing, and then toggle to view the third-party plugin. If GUI corruption has already occurred, you will need to restart the LV1 software in order to restore the GUI.
  • Mac El Capitan and Sierra only: Controls and meters may behave sluggishly.
  • When changing scenes, the new settings may be updated graphically slightly after the audio change
  • When 50 scenes or more are stored, audio and graphics load times may slow down.
  • Moving plugins with high latency between channels may cause an audible artifact.
  • Changing sample rate may take not occur instantly, depending on sample rate and number of devices
  • The redundant server may take 4-12 seconds to take over, depending on session complexity.


Additional Support Notes

The following are not bugs. Rather, they are features you should be aware of when operating the LV1:

  • If you have a session created in eMotion LV1 v10.x , and you want to load it on earlier LV1 v9.14, follow these steps in order for the session to load properly. Not following these steps may cause the LV1 v9 to load a corrupt session.
  • Only 64bit 3rd party plugins can run in Lv1 v10. 32bit 3rd party plugins are not supported.
  • Any computer that connects to eMotion LV1 v10 as an audio source or destination should be using the latest SoundGrid ASIO/Core Audio Driver v10.x.
  • Using eMotion Lv1 v9 will require connecting audio sources with SoundGrid ASIO driver v9.99.175 (windows) or Core Audio v9.99.352 Mac.
  • The SoundGrid driver version is listed at the bottom of the Driver Control Panel window, v9 and v10 Drivers installers are always available at Waves/SoundGrid/Utilities folder.
  • On scene change, if different plugins are used in Scheps Omni Channel Insert slot, DSP load will change accordingly and may cause a short audio drop.
  • LV1’s Mute All function is instant. There is no prompt or audible warning asking whether you are sure you want to mute all channels.
  • Loading a preset with a new plugin rack configuration (different plugins or different plugin order) will override and propagate the settings to all the scenes.
  • Dugan Speech’s per-channel On/Off state does not change with scenes. Use Dugan Speech’s Auto Control On/Off to toggle per-channel operation with scenes.
  • Assigning to mono Matrix from a source channel in the Mixer, Channel or Patch windows will always assign L+R, even if it was previously set to another option from Matrix mixer. When specific routings are required for Matrix "left only," "right only," or "all (L+R)," they can be set and muted only from the Matrix mixer on the Channel window.

Was this article helpful?