DSP showed the same 50-ish.īy that time I was two hours in and the knock on the door came. Normally that's the sign I get, but in this case after a few minutes it seemed to settle itself back again. Likewise clicking a new location in the transport strip would lag. Clicking on a Buss routing button would have no effect for a couple seconds and then the light would come on. At one point during all this (I think the WavesTune UI was closed) I started getting the glitchiness - pulling a fader down using the mouse would get stuck for a few seconds and then lurch to the new setting. DSP up to 51% while it went through the scan, but MB was quite happy and I could modify pitching without any problems. Did a lot of transport moving about for about an hour and left the vst's alone, mainly tweaking fader balances and checking on mains, auratone, headphones etc. DSP the usual 46% on startup with audio tracks and my usual array of VST plugs. Before I launched however, I did also do a few OS tweaks (power settings, turned off system sounds, banned a few MS apps etc). However, in typical IT fashion, the problem wouldn't quite manifest except on one occasion. I spent a couple of hours yesterday evening before being informed my time was up The other thing I'll do is remove any unused tracks - I'll often have the bus stems muted as I'll be using the individual tracks to mix, but these will be taking up resource as channels (does the system offload them if they are deactivated, but still in the Editor selection?) I get about an hour before it's unusable typically. It's a weird one though - I have one track running with just under a 100 tracks plus processing, and another with less than half that number, but they both exhibit the same slowdown. I'll try out the ideas you've suggested (I haven't changed the undo history from the default). Good to hear in a way it's not a common issue. Hopefully this will provide additional clues about the problem, and we can investigate further!Ĭheers Ben. (but leave the plugin GUI's closed)Ĥ) locate around on the timeline, and perform the edits that you normally do.Īfter each step, allow some time for the problem to appear. (04-25-2019, 10:29 Wrote: Here are some troubleshooting steps you might try:ġ) create a NEW session, add some tracks.Ģ) add the plugins that you normally use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |