SDA 1.39.3 macOS doesn't install other software that it's supposed to

As per the website, SDA 1.39.3 should install other software, i.e. Activation Manager, Library Manager and MediaBay.

But - at least on macOS Tahoe - it doesn’t.

When launched it displays an error that leads to the website where each of these has to be downloaded and installed separately.

I don’t know if that’s the reason, but:

  • I don’t see my Cubase Pro 15 license (which I received for participating in beta)
  • if I try to install it manually, it shows me an error for every component and some of them I can download, but others - e.g. Retrologue, PadShop - aren’t available on the webiste so I can’t install them at all

No idea what’s up?! Everything worked great for C14, C15 beta. Now it doesn’t.

I’m not sure if you are having quite a similar problem which occurred to a friend of mine today, but basically he had a folder missing: Downloads/Steinberg/OSX. Creating back that folder he then could update what he had to with no further issues.

1 Like

Interesting. But if that’s the case then it means something’s wrong with SDA, as I never had to make this folder for the last 5+ years.

True, that happened to him with no clue why. Did you check if you had that folder?

No, I don’t have it. Creating it will probably help me install SDA properly, but it won’t change the fact that I don’t see Cubase Pro 15 license nor that installing it manually - from outside of “owned software” fails on every single component.

Hopefully the devs will figure it out :slight_smile:

Sometimes I wonder if they need assistance to eat breakfast.

What is wrong with that message?

You are about to update the Activation Manager and that means it needs to modify files that are in use by these applications. Just close them and let the update proceed.

2 Likes

What would you expect to happen instead? Close Cubase and Halion with unsaved work & patches? It’s up to you to decide that.

Also, why you’re posting this here - in this specific post?

1 Like

It is solved in previous millennium.

  1. It does not need to touch cubase to update it self. And it should not.
  2. When updating a file that is in use you rename it, and the remove it, write the new file. If it is a proper partial change you might need to copy it first. It will be kept in memory for the one that already have it open and new users will get the new version.

This is trivial for a simple app, with one file in the memory.

A modern DAW is a spider web of files, libraries, etc. It’s much safer - for the devs, and for the user - to force closing of it, than juggling what’s running now, what needs to be renamed & replaced in parallel, AND what needs to be THEN removed, renamed again & cleaned up upon next launch.

It’s like changing shoes while walking - technically possible, but not recommended :slight_smile:

2 Likes

The problem has been explained already by @antic604 , to add on what he said

  • Windows doesn’t even allow you to rename a file that is in use by an app.
  • MacOS, which has a Unix like filesystem, allows renaming, because the name is just an attribut for the inode (the real file id). However, if the app loads more files, now from an updated software, it has a real chance to run into crashes, because the new files do not match the code that is in memory.

Steinberg developers clearly do the right thing, in exactly the same way that lots of other applications do.

2 Likes

And, of course, the user complaining about this has absolutely no idea what operational dependancies exist. There could be (and most likely are) any number of license-related files open which, obviously, must be properly closed for the SAM to update. Of all the things for someone to complain about, this is a rather grand stretch. :slight_smile:

2 Likes

I dont think it is a wise decision to make Microsoft Windows limitations to be a limitation for Cubase on modern platforms.

On linux you can update everything running. For the kernel to run you need to reboot the machine but people are working on that too.

File locking is a base element of all platforms, not just Windows, and it is not a limitation, it is a very basic requirement.

Linux is not MacOS and not Windows. Even on Linux you need to be aware of running applications, in some cases the update systems (yum, apt, etc.) ask you to restart either the application or even the server.

So you think file locking is from the last millenium, I think your post here is also not really new.

1 Like

Is anyone from the dev team going to address this at all?

I know some people have taken the discussion of topic, but the issue is real and 100% replicable. It’s not a Tahoe related problem, because 14 Pro, 15 Beta and 15 final worked fine. It’s something that started happening with the current SDA.

It seems like it’s not a general problem–it’s an issue that’s specific to your system. If the issue could be reproduced on any system, there would probably be a lot of other users talking about it. Lots of people are using the current SDA–they don’t all have the same issue.

What error?

Did you ever get this resolved?

I have similar issue. On install of SDA it failed to install mediabay which I did manually. Since then it pretty much fails to install everything I download, Cubase, Wavelab, individual instruments. Just today I see an update for SDA installs when I open it and then I get a failed to install Activation manager message. And when it first happened I saw there were others posting similar issues so it is not isolated to Antic’s system.

FWIW I’m on Sequoia so it’s also not Tahoe only. Works fine on my W11 machine though.

I’m on Sequoia 15.6.1, and it works fine. What do you see in SDA “About” section?

I see exactly what you show with one exception…..the elicenser control version has just a hyphen as I don’t have it installed.

And for completeness my Sequoia is 15.7.2 but I suspect this is not particularly relevant as Antic has this behaviour on Tahoe too.