Latest News: Bitwig updates Bitwig Studio to v5.1
VSTi unregistered after Bitwig Update - Anyone?
-
- KVRist
- Topic Starter
- 255 posts since 20 Jan, 2005
Hello @Bitwigers,
It's now the 3rd time I have to re-register most of my VSTi/Fx after updating Bitwig (from 2.3 to 2.4, etc.)
I e-Mail Support but they tell me it's nothing to do with them, but this issue only happens when I update Bitwig :/
I was wondering, does any one of you guys had this issue as well?
It's now the 3rd time I have to re-register most of my VSTi/Fx after updating Bitwig (from 2.3 to 2.4, etc.)
I e-Mail Support but they tell me it's nothing to do with them, but this issue only happens when I update Bitwig :/
I was wondering, does any one of you guys had this issue as well?
- KVRAF
- 8814 posts since 6 Jan, 2017 from Outer Space
What do you mean with re-register? They will be scanned again or you have to authorize again or what. And which are „most“? Never came across a most plug-in...; - )
-
- KVRian
- 909 posts since 7 Nov, 2017
Upgrades have always been seamless for me with regard to installed VSTs. I’ve never been prompted to re-register license keys with any VST (and I have many, from more than 30 different vendors).
-
- KVRist
- 266 posts since 20 May, 2018
I cannot even imagine what Bitwig would do to cause this for you. That's simply not how the plugin and host architecture works.
Creator of Bitwiggers, the place to share Bitwig Presets.
Advocate for Bitwish, the place to vote on Feature Requests and discuss Bitwig.
Advocate for Bitwish, the place to vote on Feature Requests and discuss Bitwig.
-
- KVRAF
- 2797 posts since 26 Jul, 2015 from Philadelphia
-
- KVRist
- 170 posts since 9 Sep, 2018
Highly doubt it's a DAW problem. Does it happen when you switch DAWs as well(like Ableton to bitwig back to Ableton).Why would bitwig even remember the state of authorization of your plugins,it's your plugin's job,isn't it? Please correct me if I'm wrong.
-
- KVRist
- Topic Starter
- 255 posts since 20 Jan, 2005
Thanks you all for all the help!
So, I'm on Windows.
Plugins concerned are all using the old VSTi 2.0 Kompakt with NI's Reg tool.
With other DAWs I don't get that issue but as soon as I launch them in BW, it's like the Registration subsystem detects a new "Machine" thus not the same Machine ID as last time I launched Bitwig
So, could it be because BW is running on some sort of Virtual Java Machine each time?
That's my guess. If so, I already mailed Support but they keep saying I just have to find an update for those (but there is none).
So I'm stuck with great Kompakt plugins that I can't use properly (East West / Quantum Leap plugins, and others I'll try to list here next time).
So, I'm on Windows.
Plugins concerned are all using the old VSTi 2.0 Kompakt with NI's Reg tool.
With other DAWs I don't get that issue but as soon as I launch them in BW, it's like the Registration subsystem detects a new "Machine" thus not the same Machine ID as last time I launched Bitwig
So, could it be because BW is running on some sort of Virtual Java Machine each time?
That's my guess. If so, I already mailed Support but they keep saying I just have to find an update for those (but there is none).
So I'm stuck with great Kompakt plugins that I can't use properly (East West / Quantum Leap plugins, and others I'll try to list here next time).
- KVRAF
- 8814 posts since 6 Jan, 2017 from Outer Space
You have to contact NI, its their bug. That is why its called Kontakt, the German word for contact...; - )
It might be sufficient to update the NI reg tool...
It might be sufficient to update the NI reg tool...
-
- KVRist
- 335 posts since 10 Apr, 2002
I very occasionally load a project and it says a VST is missing (not a version conflict), even though 1) there is another of the same on a different track 2) It IS there, I just delete the unloaded one and load it again.
- KVRAF
- 8814 posts since 6 Jan, 2017 from Outer Space
Most likely a UID conflict with the same name. Can happen if you upgrade a version and the new one has a different UID. The project which used the old version will complain, but if you load it freshly, it has no problem to load the new version...