So what are we supposed to do when ...

[Naenyn]

... KSM claims a version of an app is newer when the version listed is actually correct? For example, I have some AIR Music Tech plugins that KSM claims the latest version for is "2024.0". However, the "2024 Update for Mac" download link for Hybrid, in this case, yields a file containing "3.1.1" in the filename, which matches what KSM thinks I have installed. This seems to me to mean "3.1.1" _IS_ "2024.0".

... KSM claims a plugin is unsupported? For example, the plugins from the Tracktion DAW Essentials Collection all show up this way. Can we submit them somehow?

... our local version is newer? Does KSM automatically attempt to verify when locally installed versions are newer than what it knows about and updates itself accordingly?

... a company's installer only installs a specific version that isn't the latest? For example, I own Arturia V Collection X. I have not updated to 11 yet. Arturia Software Center says I have 2.0.0.6106 of Augmented BRASS (and that no update is available). KSM agrees on the installed version, but says there is a 2.0.1.6138, which my Arturia Software Center seems to know nothing about. I've made sure I have the latest version of ASC and have re-synced my licenses, too. Is this update perhaps only available to V Collection 11 owners?

Thank you for the help and for the otherwise handy app.

Edit: And another one:
... plugins are "not found"? Can we submit them?

[Rivanni]

I see the same things and also would like to know the answers.

As for the Arturia minor updates, this could be betas. I also notice these differences with other plugins. I wish I could exclude beta versions. On the other hand, I also see newer versions for plugins where I'm a beta tester, so I'm not sure where these newer versions come from.

You always receive minor updates for Arturia plugins, regardless of the version of the V Collection you own. Only when they increase the major version (like CS-80 V3 to V4), you have to pay.
This leads to another problem I encounter. Some plugins, like the Arturia Piano V2 and V3 are seen as one plugin when they are not. I have the most recent 2.9 version, but KSM keeps telling me there is an update to 3.3. However, this 3.3 does not apply to V2. The same applies to the mentioned CS-80 V3 and V4.
A similar situation exists with Serum and Serum 2; both are distinct plugins that can be used side by side. The available upgrade for Serum 1 should not be 2.0.19.

[Rivanni]

I have a plugin with an installed version of 2.0.0018 and an update available at 2.0.0.018.
Why has the update added an extra dot?
Many other plugins don't report their version number correctly, like NI Battery (4.3 instead of 4.3.1) and the AAS plugins (which only show the main version). Yet the available updates are full version numbers.

Where do the numbers for available update versions come from? Is someone typing these in by hand?

[Ben [KVR]]

... KSM claims a version of an app is newer when the version listed is actually correct? For example, I have some AIR Music Tech plugins that KSM claims the latest version for is "2024.0". However, the "2024 Update for Mac" download link for Hybrid, in this case, yields a file containing "3.1.1" in the filename, which matches what KSM thinks I have installed. This seems to me to mean "3.1.1" _IS_ "2024.0".

Please report any oddities. Some developers/plugins are more problematic than others. Version comparisons are tricky when a dev changes from one system to another (e.g. year to a.b.c). ). I've updated Hybrid to 3.1.1.

... KSM claims a plugin is unsupported? For example, the plugins from the Tracktion DAW Essentials Collection all show up this way. Can we submit them somehow?

We don't usually added DAW bundled plugins to the PDB.

... our local version is newer? Does KSM automatically attempt to verify when locally installed versions are newer than what it knows about and updates itself accordingly?

We do monitor newer synced plugins and attempt to ascertain if they are publicly available versions and update the PDB accordingly. Some are easier to verify than others.

... a company's installer only installs a specific version that isn't the latest? For example, I own Arturia V Collection X. I have not updated to 11 yet. Arturia Software Center says I have 2.0.0.6106 of Augmented BRASS (and that no update is available). KSM agrees on the installed version, but says there is a 2.0.1.6138, which my Arturia Software Center seems to know nothing about. I've made sure I have the latest version of ASC and have re-synced my licenses, too. Is this update perhaps only available to V Collection 11 owners?

The Augmented series 2.0.1.6138 versions were available at https://www.arturia.com/products/softwa ... /resources when the PDB was updated. These appear to have been removed now so I've reverted the version numbers.

Edit: And another one:
... plugins are "not found"? Can we submit them?

We monitor the most common missing plugins (i.e. those that are synced by the most users) and add them regularly. If there is a plugin that you think we should add urgently please post the details in this forum.

[Ben [KVR]]

I also see newer versions for plugins where I'm a beta tester, so I'm not sure where these newer versions come from.

It depends, many developers manage their product listings so they could have added a newer version. Or it could be an error. Or many people could have synced the newer version triggering an update based on an assumption.

Which plugins?

You always receive minor updates for Arturia plugins, regardless of the version of the V Collection you own. Only when they increase the major version (like CS-80 V3 to V4), you have to pay.

This leads to another problem I encounter. Some plugins, like the Arturia Piano V2 and V3 are seen as one plugin when they are not. I have the most recent 2.9 version, but KSM keeps telling me there is an update to 3.3. However, this 3.3 does not apply to V2. The same applies to the mentioned CS-80 V3 and V4.

We have a system in place to cope with this. I've updated the older V collection plugin version numbers that I'm aware of.

A similar situation exists with Serum and Serum 2; both are distinct plugins that can be used side by side. The available upgrade for Serum 1 should not be 2.0.19.

Serum 2 is a free upgrade, but I've added the max v1 number to be more accurate if a user has both installed.

[Ben [KVR]]

I have a plugin with an installed version of 2.0.0018 and an update available at 2.0.0.018.
Why has the update added an extra dot?

Which plugin?

Many other plugins don't report their version number correctly, like NI Battery (4.3 instead of 4.3.1) and the AAS plugins (which only show the main version). Yet the available updates are full version numbers.

Yes, some plugins misreport their version number.

Where do the numbers for available update versions come from? Is someone typing these in by hand?

Various - by devs, by us, by automation when appropriate.

[Rivanni]

I have a plugin with an installed version of 2.0.0018 and an update available at 2.0.0.018.
Why has the update added an extra dot?

Which plugin?

Thump One by Toybox, a VST3. In the plugin, it says 2.0.0018.

[Rivanni]

I also see newer versions for plugins where I'm a beta tester, so I'm not sure where these newer versions come from.

It depends, many developers manage their product listings so they could have added a newer version. Or it could be an error. Or many people could have synced the newer version triggering an update based on an assumption.

Which plugins?

Life DAW Recorder 1.2.0 (as mentioned by KSM and the plugin itself) by XLN Audio is one I can say. The available update is 1.2.2.

You always receive minor updates for Arturia plugins, regardless of the version of the V Collection you own. Only when they increase the major version (like CS-80 V3 to V4), you have to pay.

This leads to another problem I encounter. Some plugins, like the Arturia Piano V2 and V3 are seen as one plugin when they are not. I have the most recent 2.9 version, but KSM keeps telling me there is an update to 3.3. However, this 3.3 does not apply to V2. The same applies to the mentioned CS-80 V3 and V4.

We have a system in place to cope with this. I've updated the older V collection plugin version numbers that I'm aware of.

The older and newer versions each have their own distinct numbers here. There are no more available Arturia updates in my list. (Below 50 updates now).

A similar situation exists with Serum and Serum 2; both are distinct plugins that can be used side by side. The available upgrade for Serum 1 should not be 2.0.19.

Serum 2 is a free upgrade, but I've added the max v1 number to be more accurate if a user has both installed.

Great.

[Rivanni]

Where do the numbers for available update versions come from? Is someone typing these in by hand?

Various - by devs, by us, by automation when appropriate.
...
It depends, many developers manage their product listings so they could have added a newer version. Or it could be an error.

Do you inform the developers that (some of) their plugins are reporting incorrect version numbers?

Another recent example.
Yesterday, I installed the KV331 Synthmaster One 2.6.1 update. The plugin itself says 2.6.1.16244, but KSM reports 2.6.0.16244 as installed.

[Ben [KVR]]

I have a plugin with an installed version of 2.0.0018 and an update available at 2.0.0.018.
Why has the update added an extra dot?

Which plugin?

Thump One by Toybox, a VST3. In the plugin, it says 2.0.0018.

This is now fixed.

[Ben [KVR]]

Where do the numbers for available update versions come from? Is someone typing these in by hand?

Various - by devs, by us, by automation when appropriate.
...
It depends, many developers manage their product listings so they could have added a newer version. Or it could be an error.

Do you inform the developers that (some of) their plugins are reporting incorrect version numbers?

Another recent example.
Yesterday, I installed the KV331 Synthmaster One 2.6.1 update. The plugin itself says 2.6.1.16244, but KSM reports 2.6.0.16244 as installed.

Yes, Synthmaster One VST3 misreports as 1.6.0 rather than 1.6.1. AU reports correctly as 1.6.1.

[Ben [KVR]]

Life DAW Recorder 1.2.0 (as mentioned by KSM and the plugin itself) by XLN Audio is one I can say. The available update is 1.2.2.

Is Life DAW Recorder bundled with Life? It's associated with the Life PDB entry, which is 1.2.2.

We can either disassociate it from Life and then mark it as unsupported or add it as a separate PDB entry.

[Rivanni]

Life DAW Recorder 1.2.0 (as mentioned by KSM and the plugin itself) by XLN Audio is one I can say. The available update is 1.2.2.

Is Life DAW Recorder bundled with Life? It's associated with the Life PDB entry, which is 1.2.2.

Yes, that's the one.

We can either disassociate it from Life and then mark it as unsupported or add it as a separate PDB entry.

I believe the latter option is the best, as they are two distinct plugins that can be installed separately. It would also prevent false 'available updates', now and in the future.

[Rivanni]

... KSM claims a version of an app is newer when the version listed is actually correct? For example, I have some AIR Music Tech plugins that KSM claims the latest version for is "2024.0". However, the "2024 Update for Mac" download link for Hybrid, in this case, yields a file containing "3.1.1" in the filename, which matches what KSM thinks I have installed. This seems to me to mean "3.1.1" _IS_ "2024.0".

I see the 2024 version numbers are gone, except for one plugin in my case: VacuumPro v1.1.1. The available update is 2024.

[Ben [KVR]]

... KSM claims a version of an app is newer when the version listed is actually correct? For example, I have some AIR Music Tech plugins that KSM claims the latest version for is "2024.0". However, the "2024 Update for Mac" download link for Hybrid, in this case, yields a file containing "3.1.1" in the filename, which matches what KSM thinks I have installed. This seems to me to mean "3.1.1" _IS_ "2024.0".

I see the 2024 version numbers are gone, except for one plugin in my case: VacuumPro v1.1.1. The available update is 2024.

All AIR plugins should now reflect version numbers rather than years.