# WaveLab 11 GUI Lag with Certain Plugins

**URL:** <https://forums.steinberg.net/t/wavelab-11-gui-lag-with-certain-plugins/754600>\
**Category:** WaveLab\
**Tags:** wavelab-11\
**Created:** [December 14, 2021, 8:42pm UTC](https://forums.steinberg.net/t/wavelab-11-gui-lag-with-certain-plugins/754600 "2021-12-14T20:42:01Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![PG1](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/pg1/32/51201_2.png) [@PG1](https://forums.steinberg.net/u/PG1)\
**Post date:** [April 13, 2022, 3:36pm UTC](https://forums.steinberg.net/t/wavelab-11-gui-lag-with-certain-plugins/754600/17 "2022-04-13T15:36:54Z")

</div>

> [@AlexBarton](#):
>
> I used to bypass the offending plugin while tracking, and the lag would stop,  
> on 11 I need to delete from wherever it is (

As mentioned there, there will be a solution for this in WaveLab 11.1 :

> [@Wavelab 11 Montage Pegging CPU at 96/24](https://forums.steinberg.net/t/wavelab-11-montage-pegging-cpu-at-96-24/775078/15):
>
> This will be fixed in WaveLab 11.1, ie. bypassed plugin will not consume CPU during rendering. Moreover, a new On/Off option will be added to WaveLab 11.1 (like already available for Master Section plugins). When a plugin is Off, it won’t consume CPUs. Sorry, no. Philippe

---

_[View the full topic](https://forums.steinberg.net/t/wavelab-11-gui-lag-with-certain-plugins/754600)._