this is the first time that I’m having massive problems with one of Steinberg’s own VST plugins, in this case it’s the newly updated Backbone v1.5 (which is being licensed via the Absolute Collection 5 package license on my USB dongle).
On one machine (Laptop, Windows 11 Pro), I can use Backbone 1.5 - as updated yesterday - in any version of Cubase installed (Pro 11, Elements 11, LE 12, Pro 8.5, Pro 10.5), as well as in Nuendo 12.0.30 (Trial). Only as long as the USB dongle is connected, of course, since the Absolute Coll. 5 package license must be “on”.
The eLCC is version 126.96.36.19911, also all other Steinberg utilities are at their latest version.
On another machine (an older PC, Windows 10 Pro) Backbone 1.5 is being rejected as a VST3 plugin, in any installed version of Cubase and Nuendo 12 (Trial) - and blacklisted. Re-activation (button below) failed every time I tried it.
As above, the eLCC is version 188.8.131.5211, also all other Steinberg utilities are at their latest version.
Only after rolling back to v1.1.10, Backbone worked again on this specific PC.
I’d installed the Backbone 1.5 update with admin rights, without admin rights.
I even deleted all older blacklist related XMLs.
Made no difference.
Also I made sure to check (by comparison with the working laptop installation) if all relevant files weren’t broken by comparing file sizes and if all the files were correctly installed in:
C:\Program Files\Common Files\VST3\Steinberg\Backbone.vst3\
Just if anyone might ask:
(1) did I also update the components during install? YES
(2) did I replace / re-register the 6 updated vstsound content files manually? YES
(3) did I re-download the update package (v1.5) via SDA? YES
Perhaps any idea, anyone?
[edited: headline, June 28, 2022, 14:57 and 18:02]