I have seen Plugin heavy workflows on YouTube so I'm pretty confident that mine is somewhere in the lower middle. I use mostly VST instruments in a moderate orchestra format with only my Bass Guitar recorded live. The CPU issue for me has been a real hindrance in my workflow for longer than I can remember but it has forced me to learn to work around and work around whenever I hit that CPU wall. In today's market there's no excuse, especially for a newer DAW with so called fresh code to exhibit this behavior. I'll check in here occasionally with the hope it gets sorted out.Īgain it's really a shame that such a promising DAW as S1 which in imo has the best workflow and GUI of anything yet on the market, is so compromised for some of us. The Reaper community had been friendly,helpful, and generous in helping me get a handle on issues. It's really nothing short of astounding considering the environment I'm coming from. Running plugins that will make S1 go to its knees in short order barely affects Reaper. The excellent stability and tremendous CPU efficiency has made it more than worth it. I'm finally getting a handle on it so it does what I need. It's a whole different methodology and is taking, for me anyway, time and readjusting ones mindset to get it setup. But for me personally it has been a deal breaker. For those who aren't using a lot of virtual instruments and don't need low latency it's more than likely it's not an issue. By addressing it I mean fix it! I really liked S1 and was hanging on hoping that there would be acknowledgement that it's a big issue for some of us.
It's really a shame Presonus and the developers don't address this problem that's been the impetus for me to migrate to Reaper.
0 kommentar(er)
