Waves Scheps Omni Channel - CPU issue ?

Rusty Falcon · 01-25-2018, 07:41 AM

New channel strip from Waves - Scheps Omni Channel.

Very flexible, sounds great.....

I'm running Intel I5-4570 3.2GHz with 16GB DDR3 memory, Win10x64, and Reaper 5.70 x64 with the VST3 x64 version of this and did a test with 16 instances inserted on separate tracks.

When the UIs are closed... almost zero CPU usage.

When I open 1 UI instance no audio processing going on... Reaper CPU goes up to 24% then settles down to under 10%.

Opening multiple instances of the UI doesn't seem to increase CPU usage.

Anyone using this yet and seeing similar CPU numbers on similar setups ?

citizenkeith · 01-25-2018, 08:13 AM

Quote:

Originally Posted by Rusty Falcon

New channel strip from Waves - Scheps Omni Channel.

Very flexible, sounds great.....

I'm running Intel I5-4570 3.2GHz with 16GB DDR3 memory, Win10x64, and Reaper 5.70 x64 with the VST3 x64 version of this and did a test with 16 instances inserted on separate tracks.

When the UIs are closed... almost zero CPU usage.

When I open 1 UI instance no audio processing going on... Reaper CPU goes up to 24% then settles down to under 10%.

Opening multiple instances of the UI doesn't seem to increase CPU usage.

Anyone using this yet and seeing similar CPU numbers on similar setups ?

VST or VST3?

I'm going to install this on my Macbook this afternoon and give it a test drive. Not that I need another Waves plugin!

Rusty Falcon · 01-25-2018, 10:34 AM

I use VST3 whenever available, VST2 only if there is no VST3.

So in this case I am using the Omni VST3 x64.

Thanks!

Rusty Falcon · 01-29-2018, 09:15 AM

So i finally had a quick mix and used the Omni in both mono and stereo modes.

It's a beast... so easy to use... CPU does not seem to be an issue after all as long as I don't have multiple Omni UIs open at the same item. It does of course use some CPU while processing, but doesn't seem to be that bad.

karbomusic · 01-29-2018, 11:36 AM

Quote:

Originally Posted by Rusty Falcon

So i finally had a quick mix and used the Omni in both mono and stereo modes.

It's a beast... so easy to use... CPU does not seem to be an issue after all as long as I don't have multiple Omni UIs open at the same item. It does of course use some CPU while processing, but doesn't seem to be that bad.

I grabbed it last week and though I haven't used it much yet, it seems like fine plugin and I like the features.

Finnish · 01-30-2018, 10:21 AM

Got it, my first Waves-plugin!

JamesPeters · 01-30-2018, 04:02 PM

I've noticed some plugins have this behavior. I pointed this kind of thing out with a Tokyo Dawn Labs plugin a while ago. It wasn't nearly as extreme as your example though; the CPU didn't increase that much with the UI open, but it was a significant increase.

I think it has to do with how the plugin's visual presentation (UI) is coded. Some plugins are significantly worse at this than others. In the case of that plugin I used, it had an OpenGL graphics rendering option which some people thought would help, but didn't (at least for this specific thing that I noticed).

karbomusic · 01-30-2018, 05:12 PM

Had a chance to do a quick test. It loads up @ 0.05%, after I turn knobs etc. for a few, it rises to 0.47% or so and holds FYI.

JamesPeters · 01-30-2018, 06:39 PM

Maybe it has something to do with the graphics processor. I use onboard graphics (Intel HD 530), and I noticed more of a difference in that Tokyo Dawn Labs plugin than others did (with presumably better graphics processors).

I don't have this Waves plugin so I can't say what it's like on my system.

viscofisy · 01-30-2018, 07:49 PM

I bought the Scheps Omni Channel too, mainly for the workflow and the zero-latency. With the discount it seems like a lot for the money.
My first Waves plugin too.

Haven't had time to try it out yet - hopefully it's not too hard on the cpu.
Then again, my projects don't have many tracks.
I'll report back if there's anything alarming!
_

bFooz · 02-17-2018, 05:53 AM

Hi, this may be a little offtopic, but not worty a new thred.

I don't use any Waves plugins, tried Scheps Channel, liking it but have a problem with their knob behaviour. It is accelerated and that is a pain to use for me.

How do you deal with these knobs? Is there any workaround or you just use it like that? Thanks.

TheMaartian · 02-17-2018, 06:44 AM

Quote:

Originally Posted by JamesPeters

Maybe it has something to do with the graphics processor. I use onboard graphics (Intel HD 530), and I noticed more of a difference in that Tokyo Dawn Labs plugin than others did (with presumably better graphics processors).

I don't have this Waves plugin so I can't say what it's like on my system.

Video drivers can definitely cause GUI issues and crashes. I was using an old ATI Radeon card that caused tons of issues after I updated to Win10. I replaced it with a modern Gigabyte nVidia card that gets almost monthly driver updates. Have had zero problems since.

So, definitely look at your video drivers. Make sure they're up-to-date. If they are, and you're still having problems, you may need to consider replacing the adapter.

That works for Windows. For Macs? No idea.

Rusty Falcon · 02-17-2018, 08:43 AM

Quote:

Originally Posted by bFooz

I don't use any Waves plugins, tried Scheps Channel, liking it but have a problem with their knob behaviour. It is accelerated and that is a pain to use for me.

Hi bFooz: I don't seem to have any 'accelerated' behavior in Reaper x64 Windows 10 x64 using this plugin. Perhaps you have a speed or acceleration setting turned on in a mouse control panel somewhere in Windows or other mouse control SW application ?

bFooz · 02-17-2018, 10:08 AM

Quote:

Originally Posted by Rusty Falcon

Hi bFooz: I don't seem to have any 'accelerated' behavior in Reaper x64 Windows 10 x64 using this plugin. Perhaps you have a speed or acceleration setting turned on in a mouse control panel somewhere in Windows or other mouse control SW application ?

Thanks. There seems to be something strange in play. I have all accelerating options in the OS (Win7 x64) turned off. I did not experience this in any other plugin. Also, the mousewheel is accelerated so I suppose it is a plugin issue (e.g. 3 slow clicks move by 3Hz, 3 fast clicks move by 30Hz).

Rusty Falcon · 02-17-2018, 11:18 AM

Might be worth contacting Waves support team.

viscofisy · 02-21-2018, 06:02 PM

Quote:

Originally Posted by bFooz

Thanks. There seems to be something strange in play. I have all accelerating options in the OS (Win7 x64) turned off. I did not experience this in any other plugin. Also, the mousewheel is accelerated so I suppose it is a plugin issue (e.g. 3 slow clicks move by 3Hz, 3 fast clicks move by 30Hz).

I get the same thing, even when holding down Ctrl. For precise amounts you can double click on the button and enter it manually, but I know that's tedious as there's no way (that I know of at least) to inc/dec inside the value box after entering an amount.

Re cpu use - I'm finding it pretty good. Around 1.4% with all modules active.
(That's on a 9 yr old Quad Core Q9400, Windows7 64bit)

_

karbomusic · 02-21-2018, 06:10 PM

I'm not seeing anything weird. One quick note that holding control slows the value changes and also click+mouse hover + up/down arrow keys changes values at the minimum value increment (at least it does here).

viscofisy · 02-21-2018, 06:51 PM

@karbo - bFooz mentioned the Hz values.

I have 1-number-at-a-time control with the other values - but with Hz it jumps in (iirc) 3s or 4s or more.

I noticed it's worse up the higher values end of the Hz ... down in the hundreds of Hz it's easier to control and gets progressively less accurate as you go into the thousands of Hz.

I'm not all that bothered tbh - my "mixing" isn't that precise ... or I wasn't bothered until I started messing around with it

_

karbomusic · 02-21-2018, 08:10 PM

Hmm... there are more hertz per octave as frequency rises in the real world, aka if the increments are "physically" equal on the knob it should increase hertz per click as the frequency rises because there are more hertz to be had per click. So... I'm not sure how they would pack 20000 individual increments into 220 degrees of rotation or whatever it is.

viscofisy · 02-21-2018, 08:36 PM

Like I said, I've no idea how it's supposed to work or what to expect, and your explanation seems reasonable.
That said, there's no way to spool through precise values above 1000Hz even using the up/down arrows ... you'd have to double click and enter a value each time.

I checked again to make sure - even the up/down arrows increase the amount they step by as the amount of Hz increases. Under 1000 Hz it goes in increments of 1. Above that it starts to step in 2s and 3s till eventually it's around 100 per step. At that stage holding Control and moving the mouse is the most accurate method of "spooling" (here anyway) and seems to be around 25 Hz steps.
_

karbomusic · 02-21-2018, 08:41 PM

I think the best for precise Hz would be to type it in as I have no idea how that would be scaled on a knob regardless of how we move the knob (arrow, mouse etc) - maybe it can though.

20-40 Hz = 1 Octave = 20 Hz
2000-4000 Hz = 1 Octave = 2000 Hz

So the vast majority of the individual frequencies are towards the right of the scale; if we attach a knob to that, something's gotta give or we will run out of knob range long before we hit 20000.

viscofisy · 02-21-2018, 08:52 PM

Yeah, I said that would seem reasonable it being a knob and all.

But I'd have expected that there'd be some way of spooling through individual frequencies.
That would seem to be an ideal use of the Control+drag or the up/down arrows, for precision.

I never get that precise myself.
_

karbomusic · 02-21-2018, 09:20 PM

Quote:

Originally Posted by viscofisy

I never get that precise myself.
_

Just thinking out loud... Neither do I nor our do our ears and is why it's divided up into octaves instead. Also, the visual scale comes into play, for example 1k is what we normally consider the middle so with it at 12:00 we have 1000 frequencies to the left of the mid point, and 19000 to the right, or... we (as humans) not worry so much about individual frequencies and lay it out to what is more sensible to our eyes and ears via octave etc. Those lines that bunch up and spread out on ReqEQ - that's what they are denoting.

bFooz · 02-22-2018, 04:57 AM

Thanks for sharing you experience.

I wrote Hz just as an example. What I mind is the interaction of the mouse movement with any knob or slider.

More general example:
I move the mouse by 2 cm slowly, the knob moves by 45 degrees.
I move the mouse by 2 cm fast, the knob moves by 90 degrees.

This is usually called 'accelerated' mouse and some people like me really cannot use it.