@Rondo249, Well… I think @AiDon was joking.
Like when the doctor says “If it hurts when you do that, then don’t do it.”.
Turning off Internet (on whole system), as I tested and described above, does stop the overhead and gives Studio it’s speed back, but is surely not feasible as we all need our Internet.
Personally I use my second “workaround” (firewalling just the Studio App from accessing the network), which still allow every other part of the system to see the Internet. It just makes the network calls from Studio FAIL locally, which it does not seem to care about. It works fine. (Just expect the Blue arrows “light” to be showing on your “Notification Bell” forever.
No…There is no need for Topaz to describe recommended network speeds, because there SHOULD BE NONE.
For this type of LOCAL App, there is NO Internet requirement other than once in a while checking for updates/notifications/… With no speed requirement imposed since those are purely asynchronous downloads. If you are not accessing the Topaz cloud to validate newly purchased Adjustments or upgrading the ones you have, it should have no requirement for Internet access or it’s speeds.
What I describe above is a pure bug… Not an expected functionality needing Internet access that way.
It is something that can and should be fixed quite easily. NO APP should be “syncing or talking to Mama in the clouds” for every single click a user does. It is caused by someone simply adding the sync call to the wrong code area (like calling the Sync to Cloud function inside an event handler handling my Mouse/Pen clicks… Or similar. Bad, Bad…
Replace it with a simple timed task that could “sync” as needed in the background once in a blue moon (check for updates, notifications, …, … say once every few hours, once a day, or as needed) , and all would be well.
That would not be affecting the front-end work in any way, as the current functionality does in the 1.5.3 version.