July 4th Sale: $2999 Plugins + Instant Bonus Savings July 4th Sale: $2999 + Instant Savings | Shop Now

eMotion LV1 Live Mixer – Support Notes

Last updated on: 6/27/2022 4:40:03 AM

This page presents existing issues, some with workarounds, that we are working to solve in eMotion LV1. It also summarizes key improvements and main issues solved in the eMotion LV1 live mixer. 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.

Table of Contents:

Plugin Compatibility

Known Issues in eMotion LV1 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.

  • I/O device control panels will not auto-scale.
  • MyMon control panel will not auto scale.
  • In low resolutions, auto scaling may introduce some graphic artifacts such as blurry texts, un-even shapes of controls / indicators.
  • Running eMotion LV1 12.8. and above on an Axis One or Proton computer, or on any computer with Intel UHD Graphics, requires a graphic driver version update, follow these steps to update the graphics driver.
  • Side Chain output will not be muted, even if the source channel is muted.
  • The ‘Show Keyboard’ icon is not available in the Show, Patch and Setup windows.
    Workaround: Launch the on-screen keyboard via the ‘Show Keyboard’ icon in the Mixer or Channel windows prior to accessing any text field in the windows above.
  • BPM text entry field does not work in SETUP page.
    Workaround – access from any other page.
  • 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.
    Workaround: use “Local mode” instead of “Preamp mode” on channels that duplicate a preamp input.
  • High-latency plugins may produce small clicks when bypassed from a scene parameter change.
  • In Channel view, Scheps Omni Channel's gain-reduction will not show if eMo D5 Dynamics is inserted in the rack.
  • Moving plugins with high latency between channels may cause an audible artifact.
  • When setting an output delay on a channel’s physical output, the delay setting will ‘stick’ with physical output and not with the channel’s output.
  • ‘Save as Default Preset’ option for plugins does not work on presets named ‘PA Default’. Workaound,: using the ‘Preset Browser’ click ‘Reset to Default’.
  • When changing sample rates, the sync time for the new sample rate depends on the number of devices in the SoundGrid network.
  • The redundant server may take 3-10 seconds to take over, depending on session complexity.
  • Bucket View in the CLA MixHub plugin is currently not supported in eMotion LV1.
  • When mapping CLA MixHub to the Channel overview window, graphic errors may show in the overview display.
  • eMotion LV1 may freeze when moving between scenes with different GTR3 plugin parameter settings. How to Fix: update GTR3 to the latest version.
  • Fader functionality of Link group members may behave unexpectedly via FIT controller, after switching focus to another link group. Workaround: set link off, then focus on the desired link group and set link on.
  • In certain cases, when launching eMotion LV1 or loading a session, the network driver buffer setting may change, for example due to a system configuration change. These changes will affect the network performance.
    Workaround: When using an eMotion LV1 session on different computers and operating systems, it is advised to verify that network driver settings are within the current system’s requirements.
  • When a SoundGrid Driver shared by another system is assigned in the system inventory, or a pre-assigned SoundGrid Driver is set to be shared, the minimal network buffer will be 288 samples. Drivers set to lower settings prior to sharing will automatically change to 288 samples.
  • When loading a session, inaudible errors may appear in the routing view. This does not indicate a problem. To fix: click the Reset button in the routing view pane.
  • Audio streamed via the SoundGrid Driver WDM into a SoundGrid network may be distorted if Windows’ ‘High-Performance’ profile is not selected. Selecting ‘High Performance’ may require Admin or IT privileges.
  • SoundGrid driver sharing is possible only between two systems with eMotion LV1 v11.0.65.150 and up; or between a system with eMotion LV1 v11.0.65.150 and up, and another system with SoundGrid Studio v11.0.63.121 and up.
  • SoundGrid driver sharing is not currently possible between a system with eMotion LV1 (v11.0.65.150 and up) and another system with SuperRack (v11.0.59.49); it will be possible again once the next update of SuperRack is released.
  • If updating the firmware of your SoundGrid server or interface via a network switch results in errors, connect the unit directly to your computer and repeat the firmware update.
  • Performance of eMotion LV1 V12 and above may degrade when running for long durations on macOS 10.15 Catalina, due a memory leak in the ‘Metal’ graphic engine.
    Solution: If you have macOS 10.15 Catalina on a Macs with ‘Metal’ and use plugins for long durations (e.g. for broadcast), we recommend you update to any newer macOS version.
  • On Mac systems, when changing the number of driver channels, audio playing from the Browser tab will stop and will not resume until the SoundGrid Driver is unselected and reselected in System Preferences → Sound.

 

Additional Support Notes

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

  • Windows Only: eMotion LV1 12.8 now offers auto scaling of the application, per resolution. For best results, Windows scaling must to be set to 100% (in 4K - can be set to 200%).
  • There may be situations where a device is not managed by any SoundGrid host. It will continue to stream audio and can be used and patched, however, its specific settings cannot be modified until one of the SoundGrid hosts claims full management of this device. The I/O will appear orange in both host inventories.
  • For best performance of audio transport from the SoundGrid Core Audio Driver to the SoundGrid network, consult this page for up-to-date information on Thunderbolt to Ethernet Adapters for SoundGrid networking on Mac computers.
    Recording and playing back over 32 channels using your local Apple ethernet port is not recommended and may cause random audio drops.
  • For some systems it is advisable to use a secondary computer for recording/playback. This provides optimal CPU and disk performance on the primary computer that is running eMotion LV1.
  • The SoundGrid driver version is listed at the bottom of the Driver Control Panel window, Drivers installers of all versions are available for installation via Waves Central and once installed, in Waves/SoundGrid/Utilities folder.
  • Reassigning the management of a device will usually not affect the audio. In certain situations, however, changing the device management can result in routing override changes.
  • When using the cue buss as a matrix input with ‘entire mixer aligned’ setting, outputs may momentarily mute when engaging the cue, due to output delay alignment. We recommend ‘align by mix buss/delay group’ setting in this scenario. If all outputs must be aligned, you can assign all I/O outputs except for the cue matrix output to a single delay group.
  • LV1 supports up to 6 detached plugin windows simultaneously, in addition to the mixer’s window tabs.
  • On scene change, if different plugins are used in the Scheps Omni Channel or CLA MixHub insert slots, 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.
  • DiGiGrid D, Q and M Interfaces can function as the network SOE (clock) master only when they are the only interface/s in the SoundGrid network. If other SoundGrid interface/s are added to the same network, make sure to set a different SoundGrid interface (not from the D, Q & M product line) as the SOE master.
  • If the outputs of a DiGiGrid D / Q / M interface are patched to a Soundgrid Driver, audio will not pass if the Driver Network Buffer is set to 1024 samples in the Soundgrid host application.
    Workaround: change the driver’s network buffer to 512 or lower.
  • The latest supported firmware version for the XI-WSG I/O SoundGrid Card for Roland (1.17.14) is available only as part of the V11 offline installer and is supported with eMotion LV1 V11 and V12 only.
  • For IO and Driver sharing between multiple eMotion LV1s or eMotion LV1 and other SoundGrid applications, all applications must be aligned to the same major version.
  • The color of a selected channel in LV1 is white, if you set a channel’s color as white as well, it will not be identifiable as the selected channel.
  • Recalling a scene that changes the internal routing of a channel may cause an audio glitch if that channel has high latency values (due to routing or plugins).
    Workaround: Set internal routing to Recall Safe and/or remove it from the scope of a scene.
  • Sessions created in eMotion LV1 V10 and loaded on eMotion LV1 V11 and above show higher CPU usage.
    • This is mostly because in eMotion LV1 v11, the DSP meter displays the audio processing usage in proportion to the DSP resources devoted to audio processing only. By contrast, in eMotion LV1 v10, the DSP meter displayed the audio processing usage in proportion to the DSP usage devoted to all processing, audio and non-audio (e.g. network interface drivers). In other words, the CPU meter display in eMotion LV1 v11 is more accurate than in v10.
    • Another, more minor reason for the change is that the new mix buses added in eMotion LV1 v11 do require a bit more DSP resources than earlier versions. But this is just a minor contribution to the change in the meter display—the main reason is the change explained above.
    • The CPU meter may display slightly different values each time your session is loaded.
  • AVB systems using a SoundGrid BR1 (discontinued) unit connected to a JGS56 NetGear switch, will introduce audio drops and interruptions.
    Workaround: use a different supported switch.

 

Known Issues Fixed in eMotion LV1

  • When moving windows between screens with different resolutions, flickering or momentary discoloration or transparency may occur. – Fixed in V13
  • Restarting or shutting down your computer immediately after closing the eMotion LV1 V12.3.0.155 may bring up an “eMotion LV1 has recovered from an Unexpected Shutdown” message upon the next launch, even though the software was shut down properly. – Fixed in v12.8
  • In a shared setup, if an IO device used as the SOE master on system A is unassigned and then assigned on system B (which already has a master clock device) – the IO will use its internal clock instead of changing to ‘SOE slave’. – Fixed in 12.8
  • Bug in the ALL layer, causing channel selection from the mixer’s fader area not to work – Fixed in v12.
  • After updating I/O firmware, users may be asked to perform another update and power cycle. If you encounter this issue in eMotion LV1 V11, use the V12 hardware driver (available in Waves Central) to fix this issue. – Fixed in v12.
  • The ‘ALT’ and ‘CTRL’ quick-access keys of the Mixer and Channel windows are now momentary and will not latch – Fixed in v11.
  • On Mac OS 10.15.1, when scrolling through LV1 menus, there is no indication of what you are selecting in the menu or where the cursor is – Fixed in macOS 10.15.2.
  • In certain cases, when toggling quickly between scenes that change the layout of the detached plugin windows, eMotion LV1 may hang– Fixed in LV1 11.0.65.150 + latest V11 plugin updates.
  • No Scope or Recall Safe for direct output source selection, even though these can change with scene change – Fixed in v11.
  • Mono-to-Stereo plugins will duplicate their left output to their right output instead of providing actual left and right stereo output – Fixed in eMotion LV1 v11 + v11 plugins.
  • Filter "link" breaks when "Channel Filters" are assigned to Scheps Omni Channel – Fixed in eMotion LV1 v11 + v11 plugins.
  • On Windows, if a high contrast theme is selected, some controls may appear unresponsive – Fixed in v11.
  • Mac El Capitan and Sierra only: Controls and meters may behave sluggishly – Fixed in v11.
  • When changing scenes, the new settings may be slightly updated graphically after the audio change – Fixed in v11.
  • When 50 scenes or more are stored, audio and graphic load times may slow down – Fixed in v11.
  • No Scope or Recall Safe for direct output source selection, even though these can change with scene change.– Fixed in v11.
  • macOS users:
    • LV1 may freeze when left unattended for hours. In such a case, restart the LV1 software – Fixed in v11.
    • LV1 may quit when a primary or extension monitor is disconnected or shut down during operation – Fixed in v11.
  • 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.
  • 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.
  • 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.
  • 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.

 

Known Issues Fixed in eMotion LV1 v9

  • 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.
  • 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.
  • 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.
  • 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 Specific to eMotion LV1 V9

  • 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.
  • Using eMotion Lv1 v9 will require connecting audio sources with SoundGrid ASIO driver v9.99.175 (windows) or Core Audio v9.99.352 Mac.
  • 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.

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.
  • If you have a session created in eMotion LV1 v9.14 and up, and you want to load it on earlier LV1 versions (v9.9.0.284–9.10.0.6), follow these steps in order for the session to load properly. Not following these steps may cause the LV1 application to quit.

Was this article helpful?