VCV Rack 2

[fmr]

Softube should think about upgraiding their Modular usability. Because not having VST is what held be back from VCV. And i think with VCV2, Softube will loose a good portion of users.

Why? Just because VCV looks analog doesn't mean shit. Softube actually uses analog emulation.

Lol. "Analog emulation" can mean literally anything from just adding noise hiss to output or some stage to using non-linear DSP.

Which brings us to how ridiculous this statement is: all of that depends on the people who make the plugins themselves. So whatever is your threshold for "analog modeling", you'll find that there's plenty of modules for VCV that will cross this threshold. Or maybe you won't, because you kind of imply here that you don't even know what you're talking about.

My threshold is circuit modeling, because that's what Softube does and it sounds better than any of the other "analog emulation" that I've tried. Do any of the VCV modules do that? Because otherwise VCV is just a fancy VST host in my eyes.

Yes , vult modules amongst others
https://www.youtube.com/watch?v=mfS50tbYQK4

Vult modules are among the best. And for the price of ONE module in Softube, we can buy a whole bunch of them. Softube are among the best plug-ins, but are way overpriced, IMO.

Sure, they probably have to pay royalties to use the original manufacturers labels, graphics and, above all, names, but for the users that doesn't add any value.

Personally, I would not trade 10 modules for JUST ONE, only because it has Buchla written in the GUI.

[anttimaatteri]

Vult modules are among the best. And for the price of ONE module in Softube, we can buy a whole bunch of them. Softube are among the best plug-ins, but are way overpriced, IMO.

Sure, they probably have to pay royalties to use the original manufacturers labels, graphics and, above all, names, but for the users that doesn't add any value.

Personally, I would not trade 10 modules for JUST ONE, only because it has Buchla written in the GUI.

yes, and its even better. for the price of not getting softube modules you get 2300 in vcv! amazing!

[cnt]

Suppressing any forking..its not good for the users nor developers.

Neither is quoting a single source as though they're authoritive.

Never said they were authoritive.
What about deleting any mention of the Apple forks, is that also false?

What was the reason behind removing thr VST version of VCV then, if you know the answer?

[Funkybot's Evil Twin]

I'm hoping that once this is properly commercialized and integrated into DAWs that some big name developers would be open to making modules for this. I know at least one VST/AU developer who is very well known for their analog models of filters who has expressed an interest in VCV builds. As far as I understand, there's nothing locking a developer to the VCV Rack store or library either so they could develop, distribute, and sell their own modules outside of the store if desired.

This could really be huge. It's a platform that allows for easy turning of DSP into a functional product. Because it's so easy to develop for, the quality of the modules really varies, but there's no reason others couldn't look to create VCV Rack modules of a much higher quality if the market existed for it.

[vurt]

id like to see "every module i own copied exactly" then i can do practice patches on the laptop at the missus house and have presets

[dayjob]

if the market existed for it.

that's the key really. unfiltered audio jumped in early.

many devs have their hands pretty full these days w/all the apple changes and their own workload of updates and all that.. but seems like carving off some code here and there for modules in VCV might be a solid revenue stream and fun to do if the market is there.

[antic604]

Yes, vult modules amongst others

Vult filters are wonderful indeed, but I don't think what he describes in the video is what it commonly referred to as "component level modelling"? He describes how he implements different filter architectures / topologies in his devices (in other word - algorithms), but he doesn't really seem to model particular resisors, capacitors, transistors, diodes, i.e. the "components"; and their physical properties - how they respond to signal of different strength or frequency and how that response varies over time or between two units of the same component?

In the end I'm not sure I'd be able to tell the difference (and his filters do sound amazing!) nor do I really care, but wanted to find out if the terms we use have the same meaning?

[fmr]

He describes how he implements different filter architectures / topologies in his devices (in other word - algorithms), but he doesn't really seem to model particular resisors, capacitors, transistors, diodes, i.e. the "components"; and their physical properties - how they respond to signal of different strength or frequency and how that response varies over time or between two units of the same component?

I think Vult's approach is modeling the circuits as they exist published (e.g. following the schematics) and using some sort of Tolerance Modeling to create some instabilities to model the behavior of those circuits in the real world.

He doesn't want to "copy" existing branded models specifically, rather the broad concept behind each type. At least, it's how I see them.

[whyterabbyt]

What was the reason behind removing thr VST version of VCV then, if you know the answer?

There was no removal. The code is still there.

Just for the record: Nobody drove me away from this project.

My original intention was to (slightly) modify / extend VCV Rack, post the contribution and be done with it.

As it turned out, this plugin version required a lot of modifications, not only to the Rack (v0.6x) core itself but also to the (3rd party) modules, rendering the plugin incompatible with the mainline Rack source tree and 3rd party module repos.

I never had any plans to update this fork forever (as mentioned in one of my early KVR posts).

It is what it is. Enjoy, make some music, and support VCV Rack, especially if you want the current Rack version in VST format.

[kobal]

imo it s not like one have a secret sauce.. softube i had higher expectation on some modules while Vcv i haden t any and got surprised.. i would say it mostly the patchs and module used, reaktor sofutbe vcv all can soound analog and all can also fall short vs analog

[Funkybot's Evil Twin]

He describes how he implements different filter architectures / topologies in his devices (in other word - algorithms), but he doesn't really seem to model particular resisors, capacitors, transistors, diodes, i.e. the "components"; and their physical properties - how they respond to signal of different strength or frequency and how that response varies over time or between two units of the same component?

I thubk Vult's approach is modeling the circuits as they exist published (e.g. following the shematics) and using some sort of Tolerance Modeling to crete some instabilities the lodel the behavior of those circuits in the real world.

He doesn't want to "copy" existing branded models specifically, rather the broad concept behind each type. At least, it's how I see them.

Here's Vult (Leonardo) himself had to say in the VCV Drums thread over on their forum:

Over the years, I have stated my approach of modeling to this community but I will reiterate it for new members. When doing a model, my first step it to create an over detailed simulation model in order to try to capture the sound of the original as close as mathematically possible. Once I have that over detailed model, I start making optimizations by removing the parts that are complex and have little impact to de sound. The next step is to play with the model or my custom circuit in order to personalize or “fix” quirks of the original, basically modding the thing. Last step is to create the DSP code.

In the case of the drums, the careful looker will see that these are not exact 909 drums, starting with the fact that these have more controls than the original 909 drums. These are my modded circuits. I always avoid using the word “emulation” because that’s implies that if you get a 909 and you compare the sound of mine it must sound exactly the same. But that will never be the case. Even my two snare boards that are made with the same components sound different. This is in part due to the tolerances of the components and the differences in the semiconductors. I have some measurements that I will publish at some point.

In conclusion, if you would like to have a version of the drum machine that I would have made in the 80’s, this is it. The analog drums are based on the 909 circuits but they are modded versions (check specially my Rim and Toms). The cymbals are custom and the 808 kick is modded as well.

There's more later on in the thread. He has a blog also.

https://community.vcvrack.com/t/vcv-drums/14030/25

[gentleclockdivider]

Yes, vult modules amongst others

Vult filters are wonderful indeed, but I don't think what he describes in the video is what it commonly referred to as "component level modelling"? He describes how he implements different filter architectures / topologies in his devices (in other word - algorithms), but he doesn't really seem to model particular resisors, capacitors, transistors, diodes, i.e. the "components"; and their physical properties - how they respond to signal of different strength or frequency and how that response varies over time or between two units of the same component?

In the end I'm not sure I'd be able to tell the difference (and his filters do sound amazing!) nor do I really care, but wanted to find out if the terms we use have the same meaning?

He uses wolfram systemmodeler ( wolfram mathematica )
So , yeah it's moddeled

[gentleclockdivider]

Good read
https://www.vult-dsp.com/post/making-of ... p8NBC6uPJo
And here's how he explains it on the wolfram blog
https://blog.wolfram.com/2020/07/23/dig ... m-modeler/


Where has coroknight gone ?

[StudioDave]

I've been building and testing Rack v2 and whatever plugins can be built for it at this time.

Lots of user-level improvements. Nothing earth-shattering to report yet but it is still a WIP.

Yeh, I'm sure the commercial developers can smell the money in the water, but VCV Rack has a big user-base, more intensive commercialization is inevitable.

[fmr]

I've been building and testing Rack v2 and whatever plugins can be built for it at this time.

Lots of user-level improvements. Nothing earth-shattering to report yet but it is still a WIP.

Yeh, I'm sure the commercial developers can smell the money in the water, but VCV Rack has a big user-base, more intensive commercialization is inevitable.

I read on thge FB that Squinky Labs < https://library.vcvrack.com/?query=&bra ... =&license= > do not have plans to update their modules to version 2.

IO hope someone is kind enough to pick them and take care of updating. In th meanwhile, I guess I will have to keep version 1, even after upgrading to version 2. I hope they can coexist peacefully.