Once the render actually starts it’s a relatively short process (what I’m used to seeing) All I see is an increase in used RAM after I hit ‘render’, then a long wait before Wavelab flips over to the ‘progress’ bar. My DAW CPU is barely being tickled at 9% (across all 12 cores,) disk activity in minimal. Rendering is a far worse problem, hit render on a clip and there’s a seriously long wait (I’m getting 3-5 minute pause) before Wavelab appears to start the rendering process. When I it Playback and I can wait up to a minute before anything starts! My problem really comes to light when I end up with having 10 instances on Ozone8 (along with some other UAD plugins) across all the clips within the montage. Naturally the plugin count increases as I progress through the project/montage. With each song I master I’m inserting plugins on the ‘clip’ position. WAVELAB PRO 9.5.15 build 45 (Windows 10 pro)ĭuring a typical CD mastering scenario I’m using a Montage, I have all my audio assets (10 songs as stereo wav’s) sitting in one montage.
