Hello, one question about upgrading to Uhbik 2.0 (Bitwig Linux) : is this transparent to existing projects using the previous Uhbik version ? After upgrade, will there be a choice between Uhbik 1 and the new Uhbik 2.0 plugins ?
Cheers.
Upgrading to Uhbik 2.0
-
- KVRAF
- 3729 posts since 3 Nov, 2015
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
Next to the download button on the product page is a (a bit too tiny) info icon. If you hover over it, it shows a link to a pdf that explains (hopefully) everything you need to know before upgrading from version 1 to 2.
Please read through that pdf, and if you have more questions, either post them here or contact our support.
https://u-he.com/products/uhbik/
Please read through that pdf, and if you have more questions, either post them here or contact our support.
https://u-he.com/products/uhbik/
That QA guy from planet u-he.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Thanks. After mentioning that Uhbik plugins were renamed for version 2.0, it goes on with some 'IPluginCompatibility' that needs to be supported by the 'host app' (which I guess is another name for a full-fledged DAW in this context) in order to open projects that used version 1 once version 2 is installed. Does not seem that Bitwig Linux has anything to do at all with that 'IPluginCompatibility' (whatever that is - surely sounds like some iAppleStuff). So basically, it's not straightforward and it seems that it will be impossible to open projects that used Uhbik 1, even though the version 2 plugins were renamed so they are not overwriting the version 1 plugins I gather.
So it seems to be calling for a 'keep the running Bitwig as it runs now' strategy as a backup to open previous projects.
And yes, that info icon is really, really trying its best to no be there..
So it seems to be calling for a 'keep the running Bitwig as it runs now' strategy as a backup to open previous projects.
And yes, that info icon is really, really trying its best to no be there..
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
DAW is short for Digital Audio Workstation, which refers to your whole system, computer, audio interface, MIDI controllers and the software you are using. A plug-in host is the application you use to load (or host) plug-ins, Bitwig in your case.
IPluginCompatibility has nothing to do with Apple. It was created by Steinberg as a way to automatically replace VST2 plugins with their VST3 counterparts. This has to be supported on the plug-in and the host side.
As the pdf states, in your case, it's best to stay on the old Uhbik 1.3.1 version as long as you still need to work on old projects, since Bitwig does not support IPluginCompatibility yet.
Please contact Bitwig and ask them to implement this function. Host developers will only see a need for this if it's requested by users.
IPluginCompatibility has nothing to do with Apple. It was created by Steinberg as a way to automatically replace VST2 plugins with their VST3 counterparts. This has to be supported on the plug-in and the host side.
As the pdf states, in your case, it's best to stay on the old Uhbik 1.3.1 version as long as you still need to work on old projects, since Bitwig does not support IPluginCompatibility yet.
Please contact Bitwig and ask them to implement this function. Host developers will only see a need for this if it's requested by users.
That QA guy from planet u-he.