Today I upgraded the Apollo library for Padshop to the new Activation System.
In the eLCC the Apollo license appears as deleted, in the Activation Manager it is activated.
Everything works normally in Cubase 12 pro
However, I no longer see these presets in Cubase 11 Pro
Is it wanted like that???
It appears SB have decided to mark as ādeletedā elicenser licences when you upgrade them to SAM. This has happened on most of the recent āupgradesā - there are a few posts about it.
Latest Padshop works with the SAM Apollo licence but obviously C11 wonāt see the new SAM licence so it wonāt appear in mediabay etc.
Hi Steve,
thanks for your feedback.
After upgrading my Apollo license using the voucher code from MySteinberg, I have
activated the license in the SAM
found that Apollo is running in C12pro, that means, the library with all presets is visible in the mediabay
determined that this is no longer the case in C11pro: Apollo is not visible either in Padshop or in the Cubase 11 pro Mediabay.
Then I noticed that the license is marked as ādeletedā in my eLicenser, which I havenāt seen with any other upgraded license so far.
Thatās why I
downloaded and installed the current version of the eLCC
updated the eLCC database
and performed a maintenance on my USB eLicenser.
In the meantime I noticed that the eLicenser version is also marked as deleted in MySteinberg:
I see that as the reason why I (and other users) can no longer use certain upgraded licenses in a Cubase version prior to C12.
I hope that Steinberg will reactivate the licenses. It is clear that these are NRF licenses - upgraded to Steinberg Licensing.
I noticed the same when I purchased some Padshop 2 addons during the holidays. They were installed into the new Steinberg Activation Manger (SAM) and cannot be seen by Cubase 11 or lower. Of course, this fragments ones content between old & new Cubase and eventually forces, in a sneaky way, users to upgrade to Cubase 12.
I myself will not contact the support because I almost always use C12.
Only have C11 as reserve on my system, in case there should be any problems with C12.
But I know from colleagues that they are angry because they feel compelled to update to C12 in order to be able to continue using purchased libraries.
and I donāt use the stuff enough to go through the pain and frustration of attempting to deal with SB support
I can see why people would be annoyed though - I wouldnāt mind but I tagged a SB employee a couple of weeks ago on the other thread - but predictably, zero response.