Kontakt 8.0 was just released and now KSM/MyKVR is showing my Kontakt 7.10.6 as outdated.
This is also the case for these:
Wurli V3 ( 3.0.1.5024 » 2.12.0.3420 )
Wave Observer Pro ( 2.0.0 » 1.10.0 )
I believe paid upgrades shouldn't supersede the previous version, and should instead be tracked separately.
Paid upgrades supersede previous versions
-
- KVRer
- 1 posts since 15 Feb, 2018 from Texas USA
Agreed. Same happens for many large sets of plugins that get a new major version (Waves, Izotope, etc).
My side hustle is to make it easier for musicians and audio professionals to collaborate https://aliada.io
-
- KVRAF
- 1763 posts since 1 Aug, 2006 from Italy
I’v got mixed feelings on this:
- if the previous version is not marked as “outdated”, then how would you know there’s a new version? it would defeat the purpose of KSM… the “paid upgrade” things doesn’t really matter, because the software is actually out of date.
- on the other hand, if the new version of the plugin doesn’t automatically replace the instances of the previous one, both can be installed at the same time: the old one appears as “outdated”, but it’s just clutter in the list of the plugins needing attention.
I’d rather have some optional buttons/filters, like:
- marking the last version before paid upgrade (maybe colour those plugins in yellow?), but this would require vendors to provide that information, so it’s not easy to implement…
- adding an option to hide the plugins “out of date” if the new version is installed on the same computer (let’s say I have Kontakt 6-7-8 on the same system, version 6 and 7 would be hidden because there’s version 8; if I have only version 6 and 7 installed, then only version 7 would be displayed and marked as “outdated”); the hide button should have a counter of those plugins because, while you use a newer version for newer project, an os or daw upgrade may break those older ones making it hard to open old projects on that machine (which is probably the reason why you keep them installed); I’d like this to be an option so I can show those plugins only when I’m about to perform a major change on my computer. I can imagine this is not something straightforward to implement, so I don’t hold my breath on it either.
In general, I’d like options to show versions / filter depending on what I’m going to do with KSM (routine system maintenance vs system upgrade vs shopping planning), but my understanding suggests me those options/features wouldn’t be easy to implement.
- if the previous version is not marked as “outdated”, then how would you know there’s a new version? it would defeat the purpose of KSM… the “paid upgrade” things doesn’t really matter, because the software is actually out of date.
- on the other hand, if the new version of the plugin doesn’t automatically replace the instances of the previous one, both can be installed at the same time: the old one appears as “outdated”, but it’s just clutter in the list of the plugins needing attention.
I’d rather have some optional buttons/filters, like:
- marking the last version before paid upgrade (maybe colour those plugins in yellow?), but this would require vendors to provide that information, so it’s not easy to implement…
- adding an option to hide the plugins “out of date” if the new version is installed on the same computer (let’s say I have Kontakt 6-7-8 on the same system, version 6 and 7 would be hidden because there’s version 8; if I have only version 6 and 7 installed, then only version 7 would be displayed and marked as “outdated”); the hide button should have a counter of those plugins because, while you use a newer version for newer project, an os or daw upgrade may break those older ones making it hard to open old projects on that machine (which is probably the reason why you keep them installed); I’d like this to be an option so I can show those plugins only when I’m about to perform a major change on my computer. I can imagine this is not something straightforward to implement, so I don’t hold my breath on it either.
In general, I’d like options to show versions / filter depending on what I’m going to do with KSM (routine system maintenance vs system upgrade vs shopping planning), but my understanding suggests me those options/features wouldn’t be easy to implement.
-
- Mr KVR
- 1580 posts since 23 Oct, 2000 from UK
- KVR Audio
We do have a system in place to do this but of course many plugins do not have max previous versions set in the KVR PDB. We try to update them as we see them (and when problems are brought to our attention).
Wurli and Kontakt should be accurate already.
They should report older versions as up to date but with newer major versions available.
Wurli and Kontakt should be accurate already.
They should report older versions as up to date but with newer major versions available.