I have almost 50 unsupported plugins which 'appear to misreport their version numbers and cannot be compared to the KVR PDB'. I can see why some of the plugins are listed as unsupported, like the three XLN plugins, that somehow no longer report proper version numbers.
However, many of the version numbers appear to be correct and were listed correctly in the previous version of KSM. Is it because the numbers are too different?
I couldn't find any information in the log about this, so I took screenshots. It would be helpful if we could save this list as a text file or if this were also included in a (separate) log file.
It would also be helpful if there were a separate column for what's currently shown when you hover over the info icon.
KSM 0.3 Unsupported plugins
-
- Mr KVR
- 1580 posts since 23 Oct, 2000 from UK
- KVR Audio
I've fixed Softube Layers (that was incorrectly flagged as unsupported).
The Plogue and Orchestral Tools plugins do misreport what is supposed to be their version number.
The plugins that show blank or text version numbers will be marked as unsupported for obvious reasons.
Shreddage 3 Stratus FREE should now match and be shown as up to date.
All the others are, I believe, made with Maize Sampler ( https://www.kvraudio.com/product/maize- ... -maizesoft ) which has a weird quirk where the version number reported by the plugin is actually the version number of the version of Maize Sampler in which they were built. Therefore they can never match what is officially the correct version number.
The Plogue and Orchestral Tools plugins do misreport what is supposed to be their version number.
The plugins that show blank or text version numbers will be marked as unsupported for obvious reasons.
Shreddage 3 Stratus FREE should now match and be shown as up to date.
All the others are, I believe, made with Maize Sampler ( https://www.kvraudio.com/product/maize- ... -maizesoft ) which has a weird quirk where the version number reported by the plugin is actually the version number of the version of Maize Sampler in which they were built. Therefore they can never match what is officially the correct version number.
-
- KVRian
- Topic Starter
- 720 posts since 4 Feb, 2017
The AngelicVibes, FunctionLoops, and Audiolatry plugins are indeed based on the Maize sampler. In my case, the reported version numbers range from 2.8.3 to the most recent 2.10.4. So they DON'T misreport their version number as the info popup suggests.
What is wrong here is that there are different available version numbers and none of them is the most recent Maize version or even look like it could be one. If the available version number were correct, the plugins could be listed in the other categories.
I agree that they can never be updated because of the underlying sampler. However, if you keep them under Unsupported, it would be better to change the reason why they are there.
By the way, two Audiolatry plugins (Amurg 4 Lite and FunkBass 3) are still listed under KVR Newer. Both are Maize based.
Perhaps it's an idea to create a category for sampler-based plugins like these.
It's unfortunate that all Plogue plugins misreport their version numbers.
Where do you draw the line when it comes to misreported versions?
The few AAS plugins I have only report their main version instead of a full version ( for example, 2 instead of 2.3.4). They are still under KVR Newer. Other plugins do the same but add two zeroes to make it look like a complete version number (for example, 1.0.0 instead of 1.1.2)
What is wrong here is that there are different available version numbers and none of them is the most recent Maize version or even look like it could be one. If the available version number were correct, the plugins could be listed in the other categories.
I agree that they can never be updated because of the underlying sampler. However, if you keep them under Unsupported, it would be better to change the reason why they are there.
By the way, two Audiolatry plugins (Amurg 4 Lite and FunkBass 3) are still listed under KVR Newer. Both are Maize based.
Perhaps it's an idea to create a category for sampler-based plugins like these.
It's unfortunate that all Plogue plugins misreport their version numbers.
Where do you draw the line when it comes to misreported versions?
The few AAS plugins I have only report their main version instead of a full version ( for example, 2 instead of 2.3.4). They are still under KVR Newer. Other plugins do the same but add two zeroes to make it look like a complete version number (for example, 1.0.0 instead of 1.1.2)
-
- KVRian
- Topic Starter
- 720 posts since 4 Feb, 2017
What technique is used to retrieve the version numbers?
When I view the Info of the unsupported Igorski and XLN plugins in macOS Finder, the version number is listed correctly.
If macOS can read these version numbers, why can't KSM?
When I view the Info of the unsupported Igorski and XLN plugins in macOS Finder, the version number is listed correctly.
If macOS can read these version numbers, why can't KSM?