won’t work or is unreliable “on some machines”, for no easily understandable reason. and my roll back to version 1.1.10, all strange side effects like all Cubase versions starting with weird errors (licensing “old” and “new”), or Cubase not starting at all, don’t happen any more.īackbone 1.5. Until now, I’ve never ever had so many problems with any Steinberg product - with Backbone 1.5 being the sad exception.Īlso, after deinstalling Backbone 1.5. version to both relevant places (System32, SysWOW64), but this changed nothing. The file api-ms-win-shcore-scaling-l1-1-1.dll wasn’t present (Win10Pro - 21H2 - Build 19044.1766), so I found and copied a Windows 8.1. Yet the PC in question isn’t using Win11, but Win10. Just read something about that on Microsoft’s support pages. 3311, at least this time the eLCC installer didn’t “kill” the existing eLicenser software container.Īnyway, that whole thing is getting very annoying.
Backbone one update#
Last night I could finally update the (temporary) eLCC build. Only positive change on that same machine: etc.Īll installed Steinberg VSTs, presets and content had been working perfectly before, and the Media Bay had always been configured carefully enough so everything relevant was accessible.īackbone is being marked (twice) under VST Sound in Media Bay, all content is visible, yet just doesn’t play, since the corresponding VST plugin is being blacklisted.Īlthough I had de-registered and newly “registered in place” (manually) all six vstsound files within Library Manager (multiple times, and of course the updated versions v8 and v2, not the older ones). ( C:\Users\Administrator\AppData\Roaming\Steinberg)Īfter restarting CP11, I even removed all manually entered VST plugin search paths, re-scanned multiple times, restarted CP11 again, restarted the PC, temporarily deactivated Windows Defender, etc.
Backbone one pro#
I also temporarily renamed the XML presets folder of Cubase Pro 11.0.41.
Backbone one registration#
Were you referring to Windows Registry issues, or to any XML registration issues? That scenario you mention really doesn’t seem to be the reason for VST plugin scanner’s faulty behavior. Nevertheless, I did re-download and re-install SAM and it still shows the latest available version / build number.Īll local license registrations are working, dongle is connected. (3) did I re-download the update package (v1.5) via SDA? YESĪs I’d written above, “ all other Steinberg utilities are at their latest version”.
(2) did I replace / re-register the 6 updated vstsound content files manually? YES (1) did I also update the components during install? YES I even deleted all older blacklist related XMLs.Īlso 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:Ĭ:\Program Files\Common Files\VST3\Steinberg\Backbone.vst3\ I’d installed the Backbone 1.5 update with admin rights, without admin rights. Only after rolling back to v1.1.10, Backbone worked again on this specific PC. Re-activation (button below) failed every time I tried it.Īs above, the eLCC is version 6., also all other Steinberg utilities are at their latest version.
Backbone one windows 10#
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. The eLCC is version 6., also all other Steinberg utilities are at their latest version.
Only as long as the USB dongle is connected, of course, since the Absolute Coll.
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). 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).
0 kommentar(er)
