I don't know how hard this would be, but when I browse between patches I never know when I'm going to run across say, a Roland Cloud patch that takes f o r e v e r to load. I know I could rename a patch so it's easier to see that it's a "long load" patch, and I could skip over it if I didn't want to wait.
At first, I was thinking of suggesting a column showing the company behind the patch but of course, that falls apart as soon as you use multiple layers from different companies, which is a big feature of Unify.
What I'm thinking of here, is that Unify would track (at least the first time) the time it took to load a patch and put that number in a new column next to a patch. Thoughts?
That's a VERY interesting idea!
It's a little tricky, because some plug-ins (e.g.Β Kontakt, Omnisphere, Keyscape) take a certain amount of time to "load" a patch, but sometimes many seconds more to finish loading associated resources (mostly samples) before the patch is actually ready to play. Unify can measure the former, but not the latter.
Even a simple "slow load" icon on patches that take longer than a second or two could be mighty useful, though.
So the biggest time sink is actually the time you can measure then. It's the time to load the instrument. With Omnisphere and Roland Cloud instruments, that's the biggest time spend right there. Usually it's authentication (my theory as to why RCM stuff takes so long) or a heavy synth (Omnisphere). I think the actual patch load time after that is minimal.
I think the actual patch load time after that is minimal.
I'm guessing you haven't triedΒ Keyscape, then 😆 .
@getdunne Fair enough. π Yeah, I have some Spitfire stuff that takes a long time to load after Kontakt loads initially. But at least for some instruments it would help; I would skip by them more often. Also I hope Roland decreases the load time of their instruments some day in the future. They're not heavy instruments, which is why I attribute the delay more to their authentication system as a theory.
