# Wavelab 11 Montage Pegging CPU at 96/24

**URL:** <https://forums.steinberg.net/t/wavelab-11-montage-pegging-cpu-at-96-24/775078>\
**Category:** WaveLab\
**Created:** [March 18, 2022, 8:00am UTC](https://forums.steinberg.net/t/wavelab-11-montage-pegging-cpu-at-96-24/775078 "2022-03-18T08:00:06Z")\
**Posts on this page:** 1\
**Showing post:** 15

<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:** [March 21, 2022, 1:29pm UTC](https://forums.steinberg.net/t/wavelab-11-montage-pegging-cpu-at-96-24/775078/15 "2022-03-21T13:29:09Z")

</div>

> [@bob99](#):
>
> Bypassed clip plugins did not add to render time or to playback dropouts or skipping like they do in Wavelab 11.

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.

> [@bob99](#):
>
> can it be made so that 9.5 montages open in WaveLab Pro 11 with the 9.5 “bypass” status converted to “disable” status

Sorry, no.

Philippe

---

_[View the full topic](https://forums.steinberg.net/t/wavelab-11-montage-pegging-cpu-at-96-24/775078)._