Banana CPU usage

[jeffjohn1941]

Delighted by my experience of VB-Audio Banana, but mystified by its appetite for processing power. Currently idle but demanding up to 60% CPU

banana-cpu.png (15.73 KiB) Viewed 25078 times

with tangible effect on PC speeds. (Dell Vostro 220, Win 10 Pro)

[Vincent Burel]

Not usual.
does it change something when playing a sound or anything through Voicemeeter Banana ?
could you post your system settings dialog box ?

[jeffjohn1941]

Hi - thanks for prompt response. CPU remains high with or without sound. Settings attached. Cordialement, Jeff

banana-settings.png (202.95 KiB) Viewed 25050 times

[Vincent Burel]

ok, I see no reason for this high CPU load ...
the only strange thing i see , is the feedback loop with the VB-CABLE...
Seems you connected output A3 with hardware input 2 (labelled Skype)...
this is making no sense.

[jeffjohn1941]

Hi! Further interesting info.
Loaded VM App onto alternative PC with same settings and O/S, and CPU usage entirely normal at 6%, so I conclude that the observation is peculiar to my local setup. Can't imagine quite what!

(Yes, apologies for showing non-sensical A3 connection - I had been 'randomly' changing parameters).

Thanks for your great support, Jeff

[jeffjohn1941]

Reset all, rebooted PC and all is working well with 6% cpu; sorry to have involved you; we'll never know the problem! My apologies. Jeff

[geekgarage]

I can tell you if my assumption is right.

That E7 device in your output, I'm guessing it's these Bluetooth Headphones?
http://www.evolveo.com/en/supremesound-e7

Well if they are, and you have them as an outpout device in VoiceMeeter AND they are not connected you see this behaviour.
It's simply trying to route audio to a device that is not connected so it is routing it to the bluetooth dongle, but you dongle refuses the data and voicemeeter starts hogging the CPU, had the exact same issue a year ago with a Bose wireless headphone.

So only have wireless devices as an output IF thay are connected, else remove them

[Vincent Burel]

yes, we already have such problem with audio interface , but we have never been able to find out exactly where was the CPU load, possibly in the system interface, possibly due to unexpected waiting cycles in the driver, but it should not be...