I come from decades in R&D environments where the normal case is always a very powerful machinery at disposal. Part of my motivation for reporting this problem, is to notify developers that customers may have less powerful machinery. The other part is to put my mac in a better mood. If evan gets a good laugh, that’s still great. Absolutely.
And throttling or not, please allow for a metaphor: I once owned a bunch of trotter horses; among them fabulous More Chips. This horse was in 2002 invited to run against the European elite. After careful consideration on whether our horse had enough “chips”, we accepted and went to Jagersro race track.
After a severe initial crisis with galopp, horse #1, More Chips came with lightening speed in the finish and was one tiny centimeter from top tree. Time was 1:10:5, and I believe this is still the Norwegian record. What an amazing experience. See the race.
We learned that More Chips had more than enough “chips” available. That day, he was the 4th fastest trotter on the globe, and this is what I tell the Mac running 1.8GHz + SSD; “Hang in there, maccy, while I lecture a little in the roon forum. DO NOT GIVE UP!”
It means there is hope also for Roon with the unintentional slight of a start galopp, doesn’t it?
Now seriously, @support, brute force “analysis” every time Roon is started demonstrates a lack of sophistication. Suggestions:
Do not automatically brute force re-analyze the whole system if previous Roon exit took place some seconds or minutes ago. Most likely, the user decided a restart was due. Create a timestamp upon exit and discover this upon restart. As an example, our Roon server is always up 24-7, except when the security paranoja features that was injected in immediate releases into OS X soon after the death of their watchdog-of-userfriendless, Steve Jobs, explodes. The remedy is OS X restart while either shouting or thinking “oh, shut the f … up” as decisive as you can.
Offer the globally accepted option to check or uncheck “Auto scan on startup”, below one example from the Android app “USB Audio player pro”. Isn’t this commodity?
Regardless, never conquer the cpu as shown in this thread, but rather, demonstrate consistency to your own terminology by offering “throttled” or “low priority” options, and also, inject intelligent algorithms that are considerate of the machinery power.
PS: Also from 2002, you can see our FreePad (a tablet type of forerunner) running MPEG2 quality video, wirelessly, on a 0.256Ghz kindergarten processor. It appeared very bleeding edge at the time, but the secret is that it was not that hard, we made efficient code. It is a matter of efficient use of technology.