The main reason is that I want to make the modules that are duplicated in the Free and Premium packages to be identical. In a couple of releases I would like to remove the duplication and all the free modules part of the Premium package will be removed. In principle, you should not notice it because Rack internally replaces the modules. However, if you have any of the Vult modules disabled or hidden, you may have issues until you re-enable them.
This last version is one that I have have on hold for a long time. Internally, I changed the Vult Compiler from version 0.x to 1.x. This is a big change in the generated code and according to my measurements, it results on a small performance improvement in some modules.
If you find problems in any of the modules, feel free to reach me and report the bug.
The 47 modules of the paid version will go to 8 modules, and in an old patch where I used a paid module, it will automatically be replaced by a free one ?
Thanks Leonardo! Remember to remind people, when you remove the duplicates from the premium plugin, that they need to now also subscribe to the free plugin if they haven’t today, which many probably haven’t because it’s not needed.
After talking a bit with Andrew, it looks like this step will be done automatically. There was an issue as well with loading presets e.g. a preset of the Free modules cannot be loaded in the Premium. But this issue will be resolved in Rack before these changes are released.
If you can come up with other scenario that may be problematic, please let us know in order to find a solution before the update.
