So would an easier way to explain this is that you have one buffer size for the ASIO Guard tracks, and another buffer size for the record enabled tracks? So like 2 independent buffers going on? …where the one you set for your project is the lower buffer?
So if I set my buffer to 128, I will get a nice low latency experience recording my piano VSTi… But the other tracks will play back as if my buffer is set much higher? … which I presume means that when you press record or play, you will still experience the larger delay before the actual project starts playing (which happens with larger buffer sizes), but you won’t experience the annoying latency when you’re playing your actual VSTi.
This would make the most sense to me from a software development standpoint, because you would want to try to figure out a way to separate the record-armed track from the huge latency issues that occur with large buffer projects.
But the question still remains, if ASIO Guard is preprocessing tracks, wouldn’t it help to wait to give it time? …or is it more like ASIO Guard does all the calculations for static tracks in the background and just saves that information into like a 2-track mix that just plays that mix instead of doing the processing in real time every time you rewind and play… ?
That would make sense. Just take all the non-record-enabled tracks, and preprocess them, and save them into a two-track mix that plays along with you while you’re recording a new track. That would allow ultra low latency. But see, as soon as you make one little change in one of those non-record-enabled tracks, ASIO Guard would have to then preprocess its mix again. So it would make sense after every tweak to wait for it to catch up.