Changes in the last Vult release

In the latest update of the Free Vult modules you will find that I have enabled the extra modes that were available only on the Premium versions.

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.

26 Likes

Let’s see if I got this right,

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 ?

Yes. The idea is that the process should be completely transparent for the users.

2 Likes

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.

1 Like

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.

2 Likes

Sounds like Andrew will build out the aliasing in Rack a bit, and then do an auto-subscribe in the library, 'a la:

if subscribed to vult premium but not to vult free
then subscribe to vult free

Hi @modlfo I was just playing with the Tangents Filter and noticed that The BP and HP don’t output any sound when Bypassed.

The LP works as it should.

I think if any change is to be made then none of the inputs should pass through to the output when bypassed. In order for all inputs to pass through while bypassed, Tangents would have to perform a unity mix of all inputs.

If you think about it, Tangents functions as a mixer in a way. I think most (all ?) mixers have no output when bypassed. It makes sense that a bypassed Tangents should perform the same as a mixer.

1 Like

Funny, I never looked at it like that, I thought the input was some kind of selector LP/BP/HP and I don’t think I ever combined any of those I just chose the ONE I want (mostly LP). But this is a weird one you normally have 1 in and multiple outs.

There are hardware MISO (Multiple Input Single Output) filters out in the real world. Besides LP, BP, and HP, you are supposed to be able to get band reject and all pass configurations by patching the same signal to multiple inputs. I suppose there are other unnamed mixing options.

4 Likes