2CAudio B2: Full Body. Maximum Attitude.

[Echoes in the Attic]

First, the dual engine is very cool... as evidenced by some of the examples people have been posting. Another thing that I noticed (at least on this end) is that the cpu usage is extremely reasonable. Much more so than Aether.

Can't say I agree with this. It ranges from just under Aether to three times more than Aether depending on what you're using. To be less than Aether you usually need to be using one engine.

[Sushimaster]

Hey,

the coupons don't work for me, I replied the mail which points to the shop@ mailadress. I hope that's the correct one!? =)

[Sequent]

Note the little bit: "at least on my end". Unless my cpu meters are lying! Well, I probably need to play with it a little more in any case. But that's the one thing that immediately struck me. Your mileage may vary and obviously does.

First, the dual engine is very cool... as evidenced by some of the examples people have been posting. Another thing that I noticed (at least on this end) is that the cpu usage is extremely reasonable. Much more so than Aether.

Can't say I agree with this. It ranges from just under Aether to three times more than Aether depending on what you're using. To be less than Aether you usually need to be using one engine.

[dorremifasol]

Hi!

I'm seriously thinking about buying B2 reverb but I'm concerned about the processing delay, which according to Cubase is 64 samples (a lot IMHO).Aether and Breeze don't have (or report) such delay, so I wonder if this is something inherent to the design and unavoidable, or perhaps there will be an option in the future for realtime operation.

Thanks and cheers!

[cyphersuit]

in STudio One, when switching presets it nearly kills my cpu.

also it eats more cpu than anything i have ever seen on my pc.

[cyphersuit]

with some presets i can not even run two instances on an i7 2600 k, 16 gb ram. one instance takes up to 85% cpu. that does not seem right to me..

[cyphersuit]

hm, it has many nice things going for it. but cpu is like crazy

when switching from 'incoming tide' to preset 'cronos' it almost blows my speakers.. has this tool been tested in studio one v2?

[cyphersuit]

in comparions all waves reverbs, EAReverb, Toraverb take less than 5 % cpu power (1 instance each and 1 instance nexus² as soundmachine).

ok, so from my impressions: would love to buy B2, but it's not there yet (as far as S1V2 is concerned).

[Echoes in the Attic]

with some presets i can not even run two instances on an i7 2600 k, 16 gb ram. one instance takes up to 85% cpu. that does not seem right to me..

It has cpu rising problems in other DAWs as well. I've seen similar things happen in Ableton Live on OSX. That's not normal cpu usage. I'm not sure how to reproduce it, I just use it for a while, change presets, might delete it and reload. The cpu climbs more and more after use and sends my i7 macbook pro cracking away.

Galbanum asked for details but I'm not really sure what others details to give other than that cpu often goes up and up and up to far more than it was using when first loaded.

[cyphersuit]

i have deleted the demo now. even had already organized the money
its easy to make a list of high cpu presets since they stay that way in s1v2.... it's reproducable.

[Andrew Souter]

First, the dual engine is very cool... as evidenced by some of the examples people have been posting. Another thing that I noticed (at least on this end) is that the cpu usage is extremely reasonable. Much more so than Aether.

Can't say I agree with this. It ranges from just under Aether to three times more than Aether depending on what you're using. To be less than Aether you usually need to be using one engine.

CPu usage in B2 varries drastically depending on preset. It depends on (in order of importance):

0) single vs dual engine
1) current oversampling ratio
2) density/diffusion mode (nano, lo, hi, xtrm: each is roughly 2x as heavy as the previously)
3) modulation density mode (lo, med, hi)
4) density knob (negative values use less CPU)
5) attitude (some choices are heavier than others)
6) dynamics processing on/off
7) eq and damp filter choices

Xtrm density/diffusion mode is quite heavy on the CPU. Particualrly with oversampling. If you want to use it I recommend setting modulation density to med or lo to compensate.

Of course when various parameters are in the disabled state they consume no CPU power so this is a factor as well.

The range between min and max CPU usage is quite drastic. It might even approach 100:1 or so... More is not always better. Use your ears before just setting everything to max.

More details later when I am not writing from an iPhone/iPad. (I'm on vacation this week)

[cyphersuit]

the problems i described are there with the presets out of the box.. i didn't change a thing.

edit: if it helps i can reinstall the demo and you could see for yourself via teamviewer.

[Andrew Souter]

in comparions all waves reverbs, EAReverb, Toraverb take less than 5 % cpu power (1 instance each and 1 instance nexus² as soundmachine).

ok, so from my impressions: would love to buy B2, but it's not there yet (as far as S1V2 is concerned).

We did not test s1 v2 directly ourselves. I am unsure if any beta testers tried it or not. We did have a few reported issues with s1 v2 since public release on aug 1. We have since received s1 v2 to check internally. We found that it handles channel handling in an unexpected manner.

At the moment B2 will not work on mono tracks in s1 v2. You must always use stereo tracks in s1 v2 at the moment.

Regarding CPU usage in s1 v2 specifically, perhaps there is some denormal issue caused by unexpected channel handling.

Anyway, thanks for the report. We will look into it and we are in communication with Presonus.

[Andrew Souter]

with some presets i can not even run two instances on an i7 2600 k, 16 gb ram. one instance takes up to 85% cpu. that does not seem right to me..

It has cpu rising problems in other DAWs as well. I've seen similar things happen in Ableton Live on OSX. That's not normal cpu usage. I'm not sure how to reproduce it, I just use it for a while, change presets, might delete it and reload. The cpu climbs more and more after use and sends my i7 macbook pro cracking away.

Galbanum asked for details but I'm not really sure what others details to give other than that cpu often goes up and up and up to far more than it was using when first loaded.

If you see anything odd please try to take note of when/how it happened and let us know. Please save the current settings as a new preset and send to us to evaluate. We are happy to investigate anything and evertything reported (even if it is only experienced by one or two people). We just need to know what we are looking for.

This kind of thing sounds like maybe some form of denormal issue. In this case changing the preset should make it go away. Does it?

Anyway, we are happy to explore anything reported and thank you for your help in making our products even better.

[Echoes in the Attic]

This kind of thing sounds like maybe some form of denormal issue. In this case changing the preset should make it go away. Does it?

No, changing presets doesn't make it go away. Nor does deleting it and reloading. However it is definitely not normal cpu use as the presets I've tried should normally be much lower. I'm not testing it a lot but I'll give it another whirl sometime and see if I can catch it happening again.

You want the preset sent? I think it's happening just using factory patches, but then again maybe I tweaked things a bunch first. So save the preset and send it? Can I save while in demo mode?