VCV Free (formerly Fundamental) 2.5.0 has been released, with dozens of improvements and a brand new user manual.
Very nice looking manual. Looking forward to trying out the modules.
Manual looks great!
From the manual:
2.5.0 (2023-05-31)
- Fade
- Add -3 dB pan law to settings.
- Quantizer
- Add āShift notes up/downā menu items.
- CV Mix
- When mixing mono and poly signals, apply mono signal to all poly channels.
- Improve performance with SIMD.
- VCA Mix
- Add settings for exponential channel and mix VCAs.
- Sequential Switch 1 to 4 & 4 to 1
- Add de-click setting to context menu. Disable de-click by default.
- When mixing mono and poly signals, apply mono signal to all poly channels.
- SEQ 3
- Generate step 1 pulse output when resetting from a different step.
- ADSR
- Redesign envelope display.
Iām not sure why Iād want to install Free when I already have Pro installed. When I opened VCV it showed updates and one of them was this version, can someone explain the benefit and how it compliments Pro or is this a temporary issue?
This is not the whole software, but a rebranding of the Fundamental modules that come āfreeā in everyoneās rack regardless of paid or free version. You want to update, because these smartly designed modules have gotten a few tweaks and upgrades and will be pleasing and familiar already. The manual is the real feature to me, documentation was spotty and non existent for a number of modules.
The manual is excellent, nice work.
Oh yeah! Happy to have the option to turn the slewing on/off when switching now
Yay! The manual is much appreciated.
Iāve updated John's "Gold Star for Documentation" Awards - #36 by john_rose with a new entry.
Thanks Andrew! Nice improvements. Iāll refrain from saying how the Fundamental manual was really embarrasing before, and just say that the new and completed manual is really great, nice work!
Edit: I think that perhaps you missed an opportunity to redirect VCV - Fundamental to VCV - Free Modules, if possible.
Itās great how you refrained from saying how the Fundamental manual was really embarrassing before. itās probably best not to mention how embarrassing it was before at all.
The new manual is a massive improvement - looks like Pyer probably had a hand in it. Well done.
I fear this rebranding of the Fundamental modules to Free will cause a lot of this type of confusion, initially at least.
āFreeā is how people tend to refer to the non-Pro version of the VCV Rack application - not the module set. Now as unity2k points out, Pro users are being asked to download the Free modules to use in the non-Free version of Rack. Itāsā¦ confusing.
When I first saw that VCV Free 2.5 was released, my initial reaction was āHuh? did I miss 2.4? Iām still on 2.3ā¦ and why release an update of the Free version but not the Pro version?ā This was because we are all used to thinking of Rack Free as the application.
The manual looks amazing, great job!
I kind of agree. But itās probably a ābrand alignmentā with the VCV Pro plugin, so thereās now a VCV Free and a VCV Pro plugin, that follows their Rack editions. Except of course that the Rack Pro edition also contains the VCV Free plugin But thatās not too unusual for an open-core product - the āfreeā edition contains the free components, and the āproā edition contains the free+pro components. I think itāll probably be alright.
Also, Iām not sure people are being asked to download the VCV Free plugin. When you install a new Rack now arenāt you then automatically subscribed to VCV Free? I hope soā¦
They are when that plugin is updated as it has just been. Iām in Pro, had the red dot, and was prompted to update VCV Free (the plugin) to v2.5. Meanwhile Rack Free (the application) remains at v2.3ā¦
Now when people mention āfreeā in the context of VCV, I predict a lot of ādo you mean the plugin or the application?ā questions.
Me too, but that might only be because I was subsribed to Fundamental, and Fundamental was simply renamed to Free. In the beginning the Fundamental plugin was not in the library at all, and was only updated with Rack editions. Then at some point the Fundamental plugin quietly showed up in the library, and I only happened to notice it by chance, and I remember making a mental note that it was strange that I was not subscribed to it automatically. So without trying to make a clean Rack install from a new VCV account and verifying it, I would not absolutely assume that people are automatically subscribed to VCV Free. But I donāt knowā¦
Yeah, I predict that too. But thereās a lot of that going around and people are terrible at names and concepts. Like plugins, collections, module collections, bundles, module bundles, etc. etc.
The manual is superb. Much impressed!
VCV Rack Pro includes both VCV Free and VCV Pro modules.
VCV Rack Free only includes VCV Free modules.
See VCV Rack 2 - Virtual Eurorack Studio for a comparison between the two Rack variants.
Thank you! You are correct, @pyer designed the graphs and block diagram graphics.
Yep - I think the ability to disable the de-click (crossfade?) for the switches may be my favorite new feature. I rarely used them before because most often I wanted the switch for CV, not audio. But I am worried that having the de-click default to off can ābreakā old patches. It would be better if the default was de-click enabled, so that old patches would perform the same. EDIT: false alarm - old patches properly default to de-click off - thanks Marc!
I also love the new ADSR display - it is fun and educational to watch the progression through the envelope. I still wish the ADSR timings were fixed to be precise, which probably would require a precision option in the context menu so that old patches are not broken. Or else abandon the absolute scale for the parameters and simply go from 0 to 1, without a time unit.
Like everyone else, I love the new documentation - it really is gorgeous and polished - befitting the quality of VCV Rack. I think there are missed opportunities for more details - especially polyphony behavior for example. But my heart no longer sinks every time I see the documentation for the Free (nee Fundamental) modules.
this should not be the case since: