Mixland releases VIRELIA
by jesserayernster   1 day ago

Originally Posted by nigelgod ➡️

Congratulations on the release and can't wait to try this out!

I humbly second the request for stepped controls (as an option). I find that I move much more quickly with "curated" steps and it helps to combat whatever mental issues prevent me from sticking with a value of 6.02 as opposed to spending 30 seconds trying to finesse it back to 6.0

Originally Posted by RoundBadge ➡️

Nice!Miss my old VT4's
On the demo are the drums heavily Sample augmented?
I like to hear what this stuff does to natural sources.

Originally Posted by jesserayernster ➡️

Definitely some samples going on!

Here's a longform 30min mix/demonstration I did on a very stripped down live band arrangement. Acoustic Guitars, Piano, B3, etc. I had a lot of fun with this one too.

Originally Posted by djrustycans ➡️

Watched it this morning over breakfast

Looking forward to trying this vs Mixwave VT-7...

Originally Posted by jesserayernster ➡️

Hi! Ha yeah we're excited too. This one has been tough to keep a secret for a while now

I'll say this: We never set out to create a 1:1 recreation of these units (there are a few tremendously compelling offerings already out there that do that). But if you want to be somewhere in the ballpark of the original unit's compression behavior, then the stock settings that VIRELIA loads with will get you close to that, and then you can dial away from there!

As far as adding stepped notches back into the EQ, we would absolutely consider it if we got enough requests for it! In my opinion as a mixer, I find that it can be quite limiting to have stepped frequency selection; for me it's comparable to using a D-Pad on a gaming controller versus a full-range joystick. I do see the argument that stepped controls help to combat decision fatigue, but I feel like 95% of the time, I'd choose a slightly different frequency if given the freedom to. Stepped controls were a bi-product of the hardware era's limitations, and were a means to ensure recallability. But hey, I'm open to hearing people's thoughts !

Originally Posted by Thermion ➡️

The format of a thread is this...

First is the whooos and aaaahs followed by sucking sounds of lips and thudding knee caps hitting the ground in whatever mortals do.
Then comes the part I care about. Actual evaluation, expectations, critique of the plugin.
Followed by page after page of irrelevant babble. By then I already own the plugin and is tuned out.
Let's begin.

Originally Posted by mucmusic ➡️

...curated by a guy who doesn't like 'curated steps'

IMHO there isn't a single frequency better or worse than all the other neighboring frequencies for a given task. Imagine per song or per chord or per instrument or range or part or note ...

but yeah, nothing beats 217,59Hz on drums

You guys could easily use 2-3 curated presets as starting points

Originally Posted by jesserayernster ➡️

Hi! Ha yeah we're excited too. This one has been tough to keep a secret for a while now

I'll say this: We never set out to create a 1:1 recreation of these units (there are a few tremendously compelling offerings already out there that do that). But if you want to be somewhere in the ballpark of the original unit's compression behavior, then the stock settings that VIRELIA loads with will get you close to that, and then you can dial away from there!

As far as adding stepped notches back into the EQ, we would absolutely consider it if we got enough requests for it! In my opinion as a mixer, I find that it can be quite limiting to have stepped frequency selection; for me it's comparable to using a D-Pad on a gaming controller versus a full-range joystick. I do see the argument that stepped controls help to combat decision fatigue, but I feel like 95% of the time, I'd choose a slightly different frequency if given the freedom to. Stepped controls were a bi-product of the hardware era's limitations, and were a means to ensure recallability. But hey, I'm open to hearing people's thoughts !

Originally Posted by nigelgod ➡️

Looks like you are starting the irrelevant babble part early!

Originally Posted by Lazoo ➡️

"Light on CPU, heavy on tone."

well the tone part is correct, but the cpu part, nope.

this plug is a cpu killer... especially if you use the over sampling.

i have vac attack (which i love), and that's a cpu walk in the park compared to this guy.

maybe a bug?

win10, ableton 12 at 96k, rme ucxII, i7 14700kf, 64gb.

as it stands, i would not be able to mix with this plug.

but it does sound good.

Originally Posted by Ricky Garage ➡️

We’ll probably have to get used to the fact that plugins with this level of quality and modeling depth consume a fair amount of CPU. That’s the case with many new plugins. Especially those developed with neural networks or machine-learning algorithms are extremely computationally intensive, but also extremely accurate. So the cat-and-mouse game between resource hunger and CPU performance has been going on for about 20 years, and it’s going to continue.

Originally Posted by Lazoo ➡️

"Light on CPU, heavy on tone."

well the tone part is correct, but the cpu part, nope.

this plug is a cpu killer... especially if you use the over sampling.

i have vac attack (which i love), and that's a cpu walk in the park compared to this guy.

maybe a bug?

win10, ableton 12 at 96k, rme ucxII, i7 14700kf, 64gb.

as it stands, i would not be able to mix with this plug.

but it does sound good.

Originally Posted by Lazoo ➡️

well, one can justify this till the cows come home, but to me, it's excessive.

makes the old ik tape plugs look friendly. lol

and to advertise it as "light on cpu"?

is just a straight up lie.

unless it's a bug...

Originally Posted by i_mightBEWRONG ➡️

With no OS, CPU usage is super negligible.

Originally Posted by Lazoo ➡️

here are my cpu numbers for one instance...

17% at 0 os
34% at 2x os
66% at 4x os
131% at 8x os
261% at 16x os

eight instances on eight separate tracks...

30% at 0 os
40% at 2x os

since i run at 96k, i usually just use 2x os, but with these numbers, it's just unusable for me.

unless it's a bug...

Originally Posted by i_mightBEWRONG ➡️

If you look at Jesse's video he posted in this thread called "MIXING AN ENTIRE SONG WITH ONE PLUGIN" at time 29:30, he shows running 25 instances in Pro Tools, with no OS, and averaging around 22% CPU on playback.
Granted I don't know what the session sample rate is.
So some variables we don't know, session rate, if he has every module enabled in every instance, etc.

But it does sort of sound like it "could" be a bug?

Maybe Jesse can chime in at some point.