So again, all things being equal, someone should be getting lower latency with ASIO Guard. Because all tracks, even ones you didn’t care about monitoring would be tapping into the limited, low-latency fountain. Right, but you’d have that issue even more, all things being equal, without ASIO Guard. Yeah, go for that multi-track monitor when you are at 95% ASIO load. I haven’t tested yet, but suspect it works that way.ĭid you have monitor enabled for all those tracks? I’m pretty sure if you set monitor on for all those tracks in question they’d get the low latency in those editing scenarios (and CPU requirements would go up, probably). Monitor can be enabled for more than one track. It also doesn’t work (under certain editing scenarios) when you have multiple tracks open in the Editors. Although the new ASIO Guard is significantly better at catching ASIO Spikes. I’ve also found that C8 performance is actually marginally worse overall than C6 and 7.
However, when the project gets loaded you still have the same old problems.
Yes, it is a distinct advantage to no longer have to go back and forth with the buffer size so often. It is adding buffers/latency with all of the gotchas that come with it. It also doesn’t work (under certain editing scenarios) when you have multiple tracks open in the Editors.Īs I’ve said many times, ASIO Guard 2 is nice … but don’t get confused about what it is doing. If you are pushing the project you won’t be able to do that on all the tracks you want to automate. Then just press the monitor button on those tracks and go into “performance mode” so to speak, if it matters, right? What am I missing here? Only on tracks you’re not currently monitoring live (monitor enabled and/or record enabled).Īgain, I disagree … you will absolutely notice using editors and making automation and loop adjustments, especially as you get to a loaded project and start increasing the base latency.
0 kommentar(er)
