![]() ![]() I'm saddened it works so badly when you have the network adapter enabled, but no Internet access, like in my case. But let's call this one a *workable case*, as you could possibly pre-load the Roland instruments you're planning to use with the project and get normal loading times with these. If you start a new project, the long loading time will appear at some point, not sure how. This is how it should be, and this is the *best case*.Ģ) When your network adapter is enabled, but there's no Internet access with it, as in my case, since I have Windows OS'es networked but no Internet access, loading times are incredibly long, actually I couldn't even load them, or maybe I wasn't patient enough? But this is the *worst case*.ģ) When your network adapter is enabled, and you have Internet access with it, as it will never be in my case from Windows, you will be able to load the project with Roland plugins, and the loading times for new instances of these plugins will be normal, but loading any different Roland plugins that are *not present in the project* will result in a very long loading time and a CPU spike. So I've tested three different cases:ġ) When you disable the network adapter completely, everything works perfectly and loading times are normal. Roland Cloud wants one present, as you might have guessed, otherwise Roland Cloud can't work when there's no *Internet access*. The problem seems to be the network adapter. In other words - not fixed, but they are perfectly normal in *some cases*. ![]() Here are my findings, in VM Windows7圆4 with Reaper 4.78: This might sound a bit too technical for some, but some will understand, I hope. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |