Nembrini Audio - The Voltour Valve Enhancer (overdrive/distortion)

wim

@espiegel123 said:

@Slush said:
It’s not showing up in Cubasis, anyone can confirm this?

Have you rebooted?

Also, try running the standalone version once. Some apps need that to complete their installation.

spiteface

Thanks, I should have remembered to check Flo. This one is just not for me I think. Sounds like playing through a nice amp with a heavy blanket over the speaker to me.

@Schmotown said:

@spiteface said:
So, I bought this because I buy everything from Nembrini (not knowing anything about the original unit). Is this mostly used on synths or something? Cause on guitar I got nothing but flubby mud and other generally terrible tones. I assume I must be doing something wrong. Where would this go in the chain - before amp, in place of amp, post amp, not on guitars at all? Would like for this not to end up as a wasted purchase.

Here’s a demo from former forum member Flo. Worth noting that he makes everything sound great…

dendy

@spiteface said:
So, I bought this because I buy everything from Nembrini (not knowing anything about the original unit). Is this mostly used on synths or something?

You can find Culture Vulture HW in literally almost every serious production / mastering studio on this planet. It is used literaly for everything, from subtle ovedrive of master mix to brutal destruction of synths, guitars or even drums.

richardyot

I think this has become my favourite app for adding saturation. It’s not a replacement for a valve amp IMO, but it’s great for adding a little bit of grit or warmth to an already recorded track. Similar to Saturn for example, but so far I’m liking this even better than Saturn.

Birdpie

hows the cpu usage?

Luxthor

I bought this because of @dendy's excitement alone; I didn’t have high hopes; it’s after all another saturation fx. I almost thought, another 10€ went through the window. But on my first experiment, it aggressively became my future choice. I’m using it on synth leads. Thank you @dendy! 🫶

Birdpie

can someone tell me how it tax the cpu?

Birdpie

@Schmotown said:

@spiteface said:
So, I bought this because I buy everything from Nembrini (not knowing anything about the original unit). Is this mostly used on synths or something? Cause on guitar I got nothing but flubby mud and other generally terrible tones. I assume I must be doing something wrong. Where would this go in the chain - before amp, in place of amp, post amp, not on guitars at all? Would like for this not to end up as a wasted purchase.

Here’s a demo from former forum member Flo. Worth noting that he makes everything sound great…

pretty useless video. the distortion is there from the beginning.

Luxthor

@Birdpie said:
can someone tell me how it tax the cpu?

Edit: iPad Pro M2, AUM, 48kHz, 256 samples, iOS 16.6.1

dendy

@Luxthor said:

@Birdpie said:
can someone tell me how it tax the cpu?

To get proper test you actually need as much plugins as needed to get CPU into some very high load area (let's say 80%) and then just count number of plugins and compare it with other iPad with same host app and same buffer size, just different CPU. Let's say on iPad M1 it would be 50 instances of plugin, on iPad MINI 5 30 instances of plugin. Then compare instances and you get relative comaprison of plugin's CPU needs.

It is becasue when you add just few instances, it may be that just your CPU is not running on full power (CPU polling in effect) so it may show you 3.9% but that is just 3.9% from the part of CPU which is currently running - when you then add more plugins, in some moment it may jump to smaller value per plugin (unintuitively), just becasue CPU jumps on its FULL power so actually load of one instance in % value starts be less from whole CPU available power.

So you nee to force CPU to run on full power. Only meaningul compare is to push it let's say to constant 80% load (by addin as much instances of that plugin as needed, to get there) and then compare it with other iPad, where you do same (in same app host, with same buffer settings), how mich instances weere needed to get to those 80% of total CPU consumption.

Luxthor

@dendy said:

@Luxthor said:

@Birdpie said:
can someone tell me how it tax the cpu?

To get proper test you actually need as much plugins as needed to get CPU into some very high load area (let's say 80%) and then just count number of plugins and compare it with other iPad with same host app and same buffer size, just different CPU. Let's say on iPad M1 it would be 50 instances of plugin, on iPad MINI 5 30 instances of plugin. Then compare instances and you get relative comaprison of plugin's CPU needs.

It is becasue when you add just few instances, it may be that just your CPU is not running on full power (CPU polling in effect) so it may show you 3.9% but that is just 3.9% from the part of CPU which is currently running - when you then add more plugins, in some moment it may jump to smaller value per plugin (unintuitively), just becasue CPU jumps on its FULL power so actually load of one instance in % value starts be less from whole CPU available power.

So you nee to force CPU to run on full power. Only meaningul compare is to push it let's say to constant 80% load (by addin as much instances of that plugin as needed, to get there) and then compare it with other iPad, where you do same (in same app host, with same buffer settings), how mich instances weere needed to get to those 80% of total CPU consumption.

I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

dendy

@Luxthor said:
I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

yup will do

Luxthor

@dendy said:

@Luxthor said:
I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

yup will do

Fantastic! Please use ButterSynth, DaggerSynth, PhaseMonkey, and TeraPro so we can finally have a real CPU usage test! 🤩

Slush

Still have to check if I can get this thing working in Cubasis, otherwise I try a reinstall. Works in Apematrix and use it on some synths and percussion. I am not into heavy distortion but this is great for warmth and grit. It’s like using pepper and salt, just a pinch goes a long way.

bobbyj8866

Voltour is for sure now one of those secret sauce plug ins, much the same as Magic Death Eye, adds stuff that I like.

dendy

@Luxthor said:

@dendy said:

@Luxthor said:
I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

yup will do

Fantastic! Please use ButterSynth, DaggerSynth, PhaseMonkey, and TeraPro so we can finally have a real CPU usage test! 🤩

well for meaningful testing of Voltour, i must use ONLY voltour plugin in this type of test .. it makes no sense to combine plugins .. you want to know what is relative load of one particular plugin when compared to other devices so in this test you need to use just that one plugin .. i doesn't have infinite free time to try all possible plugins :-D :-D

Gavinski

@dendy said:

@Luxthor said:

@dendy said:

@Luxthor said:
I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

yup will do

Fantastic! Please use ButterSynth, DaggerSynth, PhaseMonkey, and TeraPro so we can finally have a real CPU usage test! 🤩

well for meaningful testing of Voltour, i must use ONLY voltour plugin in this type of test .. it makes no sense to combine plugins .. you want to know what is relative load of one particular plugin when compared to other devices so in this test you need to use just that one plugin .. i doesn't have infinite free time to try all possible plugins :-D :-D

Sounds like some version of hell for badboy Audiobus nerds 🤓

Luxthor

@dendy said:

@Luxthor said:

@dendy said:

@Luxthor said:
I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

yup will do

Fantastic! Please use ButterSynth, DaggerSynth, PhaseMonkey, and TeraPro so we can finally have a real CPU usage test! 🤩

well for meaningful testing of Voltour, i must use ONLY voltour plugin in this type of test .. it makes no sense to combine plugins .. you want to know what is relative load of one particular plugin when compared to other devices so in this test you need to use just that one plugin .. i doesn't have infinite free time to try all possible plugins :-D :-D

I thought you needed to unlock high-performance cores and then a number of Voltour instances just to be sure of variations. Also, I don’t have any idea how you will manage core clusters and all load balancing shenanigans between them, but you are the guru, and I have faith in you. 🤩

espiegel123

@Luxthor said:

I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

The situation is that those CPU numbers don’t really tell you anything reliably meaningful about cpu intensive need of a plugin when the CPU is not under a heavy load because of the way CPU throttling and real-time core reallocation work.

https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing

Luxthor

@espiegel123 said:

@Luxthor said:

I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

The situation is that those CPU numbers don’t really tell you anything reliably meaningful about cpu intensive need of a plugin when the CPU is not under a heavy load because of the way CPU throttling and real-time core reallocation work.

https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing

I know that, as does everyone else on the forum. I still think that values taken from normal projects and considering device age and power can help someone in need to know at least approximately CPU usage.
 
Or should we ignore those requests and move on?

Birdpie

is your cpu in stress with few instances?
thats all.

michael_m

@dendy said:

@gusgranite said:
First preset is ‘303 Distortion’ - lessssgooooo 🤟

I hear you !

I stood up and danced while flicking the light switch on and off.

The other people in my office were a little confused…

Luxthor

@michael_m said:

@dendy said:

@gusgranite said:
First preset is ‘303 Distortion’ - lessssgooooo 🤟

I hear you !

I stood up and danced while flicking the light switch on and off.

The other people in my office were a little confused…

The best commercial Voltour Valve on this forum will ever get! 🤩

espiegel123

@Luxthor said:

@espiegel123 said:

@Luxthor said:

I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one.

The situation is that those CPU numbers don’t really tell you anything reliably meaningful about cpu intensive need of a plugin when the CPU is not under a heavy load because of the way CPU throttling and real-time core reallocation work.

https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing

I know that, as does everyone else on the forum. I still think that values taken from normal projects and considering device age and power can help someone in need to know at least approximately CPU usage.
 
Or should we ignore those requests and move on?

The point is that those numbers aren’t meaningful. It isn’t that they give a sense of the cpu usage in non-heavy load situations. They don’t even give a meaningful sense on normal situations. So, yeah, I would say ignore those requests unless one has a meaningful comparison.

dendy

Test enviroment :

• iPhone XS Max (A12 Bionic CPU)
• Nanostudio2
• audio buffer “high” (equivalent to 512)

Tesults:

17 instances of Voltour
CPU load 73-74%, with occasional peaks to 90%, smooth playback, no audio dropouts

After i added 2 more instances:
CPU load 75-78% but occasional peaks to 96-98% with dropouts

Birdpie

@dendy said:
Test enviroment :

• iPhone XS Max (A12 Bionic CPU)
• Nanostudio2
• audio buffer “high” (equivalent to 512)

Tesults:

17 instances of Voltour
CPU load 73-74%, with occasional peaks to 90%, smooth playback, no audio dropouts

After i added 2 more instances:
CPU load 75-78% but occasional peaks to 96-98% with dropouts

thanks!

Slush

@espiegel123 @wim Reboot worked, it’s showing in my list now, thanks.

espiegel123

@dendy said:
Test enviroment :

• iPhone XS Max (A12 Bionic CPU)
• Nanostudio2
• audio buffer “high” (equivalent to 512)

Tesults:

17 instances of Voltour
CPU load 73-74%, with occasional peaks to 90%, smooth playback, no audio dropouts

After i added 2 more instances:
CPU load 75-78% but occasional peaks to 96-98% with dropouts

Can you give a point of comparison … say Saturn instances or some other saturation plugin?

dendy

.

dendy

@espiegel123 said:

can’t run saturn on phone .. and doesn’t have other saturation plugin .. if i try it with nanostudio build in satueation, i would be able to run probably hundreds of them lol

but will do same tests on my M1 air ..rhat would be good comprison of performance