[blog] Be careful with updates

[npudar]

You can read the latest blog article here → LINK

–

Related:

• Painful Sequoia 15.2 update on an older Intel Mac → LINK
• At some point, the law of diminishing returns becomes a factor and although newer plugins may improve previous ones, unless there is a really dramatic difference, I couldn’t be bothered. → LINK, LINK2
• Some Windows updates can be rolled back the first 10 days after the update. You need to do this from the Settings app → LINK
• After macOS 15.2 update, plugin presets are missing → LINK
• Lost all of my MIDI mappings after Windows 11 update → LINK
• My iPad updated a few days ago and the update turned off the Bome Network “run in the background” option. Took me an hour or two to discover it → LINK
• Unless it’s broken, don’t upgrade! Seriously. I’m still running my live performance host on a 10.14 machine from 2019 and I have not updated any of the plugins I’m using on it in years. → LINK

[npudar]

Korg Collection Update

---

After the last update of:

• EP-1: 1.0.5 → 1.0.8
• ARP-2600: 1.0.6 → 1.0.9
• VOX Super Continental: 1.0.5 → 1.0.8

→ the ON/OFF parameter control no longer works properly with these plugins.

If you assign the FX1 enable parameter to a button, for example, you can switch the effect on or off once. After that it no longer works.
With the previous versions it still worked correctly.

(source)

[npudar]

David ran into a problem due to a faulty VMWare update.

LINK

–

[npudar]

Feedback from a Gig Performer user.

Apparently the newest Windows 11 24H2 update has created an Unknown Account under permissions (see photo).

From a quick search on the Internet this is a mess up from Microsoft’s part and many have this issue.

I have restored an old Windows 11 23H2 image, and all is well now!

[schamass]

Is it possible to just delete that account if it’s been created?

[npudar]

This guy just reverted to the previous Windows build. It caused permissions issues and therefore Gig Performer acted strange on reading/saving settings.

I guess one could try to remove it.

–

Crash: multiple versions of the same library used by different plugins. Happened after a plugin update.

@dhj

The crash is due to a file called libpianoprocessor.dylib and there are multiple versions of that file, all with different sizes (sigh)

(source)

[themaartian]

@npudar

I guess one could try to remove it .

That worked for me.

[npudar]

Thanks for reporting!

–

Another occasion:

[themaartian]

I should have noted that I got several meaningless error messages that I had to click through, relating to the folders on my C: drive (the one with bogus user account) being in use. Since the bogus account was only attached to the C: drive main folder, no harm, no foul. It was removed following the advice in the linked post.

[edm11]

Interesting. I’ve done 7 installs of 24H2 on Win 11 Pro machines and haven’t come across that issue.

[npudar]

Windows April Update causes BSOD.

Link: New BSODon Windows 11 (nothing to do with Gig Performer)

(I don’t update, so can’t check)

–

Sequoia 15.4 Kernel Panic

Link: Ongoing kernel panics with Sequoia 15.4 (nothing to so with GP)

[npudar]

Are Software Updates Necessary for Live Performance?

[npudar]

From Facebook:

John S. Hagewood

Thanks. Yes, I got burned recently when an Arturia update made Solina V complete SUCK ALL CPU available on my version of Sonoma, and it torpedoed a Pink Floyd tribute rehearsal until I could figure out which plug in was doing it! Bleeding edges do make one bleed, I suppose

[npudar]

(Don’t update anything before a show!)

[npudar]

Windows Update Catastrophic Issues

–

@Ipkz

I feel like Windows 11 is actively trying to sabotage itself at every turn . A few weeks ago, a Windows update locked me out of my system and messed up the boot entries with no chance of recovery (I had a restore point). A few days later, a friend of mine updated his Windows 11 and it bricked his Samsung 980 Pro SSD

Source: [Rackspace] NDSP: Gojira X (complete) - #20 by Ipkz

[npudar]

Tracktion Collective 2

–

If you upgrade to Tracktion Collective 2 and you still have v1 installed a weird situation will happen!

Namely, the developers named the v2 plugin internally as the same name as v1.
→ So, when you try to add the plugin in the Wiring view, it simply doesn’t instantiate or appear.
(Presumably due to the naming clash.)

Solution: Disable v1 in the Plugin Manager. After you disable v1, then v2 will be able to load.

Source: Tracktion Collective V2

[npudar]

Synthology Ivory 3 update issue

–

This plugin has problems with the update especially if you also have Ivory 3 grand pianos.
Their update may hang your system.

(source)