DX12: Added support for multi-display rendering.Asset Import: Importing is now supported for models with more than 100,000 objects. So I think I concur with Wavelab's error message: it seems like Stereo Tool is still functioning after the crash message appears, and has to be terminated by terminating Wavelab.5.4.0f1 (Release Candidate 1) Release Notes (FULL) Features Even when I uinload Stereo Tool, Wavelab continues to report CPU use even though I'm not asking it to do anything. There is ongoing CPU usage - Stereo Tool reports between 15% and 25% use - even though there's no render in progress. Maybe that's OK? Similarly, the plugin output on the Audio I/O settings page is set to "Send to Winamp Silence" which I would happily change to something that makes more sense, but none of the choices sounds like "send the output back to where it came from after processing it" which is what I'd want.Īfter I start to render and Wavelab reports a crash, the input bar on the Audio I/O page is pegged at 100% even with no audio playing in Wavelab, and the output bar keeps moving around. In the Audio I/O settings, there was no ASIO device set. I'm happy to provide input about the Beta, and maybe that should be in another thread? But for the moment, I do see something odd. This doesn't crash either Wavelab or Stereo Tool, but the audio doesn't render, either. Wavelab tells me that a "serious error has occurred" inside Stereo Tool. Still, when I click "render" in Wavelab, I get the same pop up windows. I also hear the "processed by Stereo Tool" message encouraging me to purchase and register. I'm interested in the declipping function and I can see that it's working by looking at the input v. As a VST3, Stereo Tool loads just fine and I can see it doing its thing. I installed Beta 10.02-055 and indeed the GUI is better, etc.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |