Sometimes you just have to realize you did something stupid that caused ripple effects. Back in mid-march, I created the following post Strange Heavy CPU Change in Rackspace .
In that post, I stated that I hadn’t changed anything on the MacBook in question since creating the two rackspaces in question which had gone out of control with CPU usage. I stand corrected. Apparently I upgraded to 5.0.40 in between the initial work on these rackspaces. That change alone would not have caused the issues I was seeing. I made the particularly stupid move by installing the Intel specific package on my Apple Silicon MacBook. The Rosetta conversion is what was causing the huge rise in CPU usage.
It had a number of other residual effects as well. I would consitently have GP simply crash when saving a gig file with changes, or crash with certain plugins. Last but not least, my Roland Zenology wouldn’t work and when entering credentials the authorize failed along with it hung on loading EastWest Opus unless I had an internet connection going. I would have to connect to my phone as a hotspot to get it to finish loading the gig file.
Note that all three of the plugin specific issues resulted in me opening support tickets with Korg, EastWest and Roland…
I seriously doubt I will make this mistake ever again, but if I do, I will catch it far more quickly than before. Note that Apple crash reports contain some valuable information. That was how I determined I was using the Intel version of GP (eventually).
My apologies to anyone I may have gotten terse with while I tried to work through the problems caused by my own ineptitude.
This is the BEST community in existence for any software ANYWHERE. I appreciate all of you.
ChatGPT: In the literal, supernatural sense—like casting spells, flying on broomsticks, or conjuring fireballs—magic as often portrayed in stories doesn’t exist according to our current scientific understanding.
However, magic does exist in other ways: the wonder of nature, the mysteries of consciousness, the beauty of art, and the awe of technological achievements can all feel magical. And of course, magic thrives in fiction, myth, and cultural traditions, where it plays a powerful symbolic and imaginative role.
–
Me: “Can something magically happen in a computer so it behaves unstable?”
–
ChatGPT: Not “magically” in the supernatural sense—but yes, computers can behave in ways that seem magical or mysterious due to unexpected errors or complex interactions. Here are a few real reasons a computer might act “unstably”:
Hardware faults – A failing hard drive, bad RAM, or overheating CPU can cause strange behavior.
Software bugs – A tiny mistake in code can trigger crashes or unpredictable results.
Cosmic rays – Rare, but real: high-energy particles from space can flip bits in memory, leading to errors.
Malware or hacking – Malicious software can deliberately cause instability.
Corrupted files or drivers – These can cause apps or the whole system to misbehave.
So while it’s not magic, it can sure feel like it when something breaks for no obvious reason.
–
Human error is one of the most common causes of computer problems. Some examples include:
Misconfiguring settings (e.g., wrong BIOS or network settings)
Accidentally deleting or modifying critical files
Installing incompatible software or drivers
Forgetting updates or applying the wrong ones
Typing mistakes in code or scripts
Even experts make these mistakes. Sometimes, the effects don’t show up right away, making the error harder to trace and feel “magical.”
