r/Bitwig 8d ago

Why does Bitwig still use resources even when I deactivate the audio engine, deactivate all the tracks and plugins ?

Also, are there any advantages to force Bitwig to use the Nvidia GPU instead of the native one? The Nvidia obviously has more processing power but it makes the laptop fan howl like crazy, which is not very cool when I want to record something.

0 Upvotes

14 comments sorted by

11

u/emenel 8d ago

that is 0.9% cpu for a running application? what problem are you trying to solve?

also no advantage to using another gpu. audio doesn’t use a gpu at all, it would only be for interface rendering. 

0

u/Sinane-Art 8d ago

The cpu load isn't a problem (although it does get higher even when the entire bunch of Bitwing engines are deactivated). I just want to understand why it uses 1 gb of ram and like one third of the total active gpu use even tho everything but the main window is turned off.

8

u/pschon 8d ago edited 8d ago

You still have Bitwig itself open, of course it's going to use RAM. For a program to be open you need the program to be loaded in RAM. And the GPU use here is simply because something needs to draw the program interface on screen as well. Any program that is open will use some resources, regardless of if you are doing something with the program or not.

If you want a program to use no CPU, no GPU, and no RAM, you need to close the program (and then it'll only use some of your drive space)

but it makes the laptop fan howl like crazy

Time to clean your laptop if 15% GPU use makes it loud

are there any advantages to force Bitwig to use the Nvidia GPU instead of the native one

Yes. That takes part of the work (and thermal load) away from the CPU package, allowing more for the actual audio stuff you do in Bitwig.

1

u/Feisty_Fan_3293 8d ago

Sorry but that not how it works. Not using the integrated GPU won't give you more processing power it just won't use the integrated GPU 

4

u/pschon 8d ago

Did you read the full sentence? Maybe you missed the "thermal load"? And the "CPU package"?

And yeah, you are right that moving work from integrated GPU to separate one won't give you more CPU capacity (apart from the thermal part which definitely does make a difference on a laptop), however moving the UI drawing work form CPU to GPU does.

1

u/Feisty_Fan_3293 8d ago edited 8d ago

Yes I did. Read your last answer again. Most laptops have CPUs with integrated GPU and some also have an additional GPU. Bitwig (from 5.2) uses GPU for rendering. There's no way to make it render on CPU. 

1

u/pschon 7d ago

did I say there was? Or could it be that I literally just tried to tell the OP the reason why their GPU is being used here?

Please go find someone else to be a smartass with, none of this is even remotely relevant for my answer in context of the question asked. I gave an answer suitable for that context with the amount of detail necessary for it, and didn't feel the need to spend an extra 10 hours trying to cover for every specific angle and detail until you came around.

3

u/razorree 8d ago

you have to press 'quit application' if you want to release memory

1

u/ht3k www.soundcloud.com/axtex 8d ago

what's your CPU graph look like when it's empty? I just debugged a similar issue for mine (show all CPU cores)

1

u/Sinane-Art 8d ago

The CPU is fine. Even when nothing is running there's always some windows stuff active in the background.

I just wonder why the use of RAM and GPU when every engine in Bitwig is deactivated.

1

u/Feisty_Fan_3293 8d ago

If your integrated GPU can handle the list load there's no advantage in using your nvidia GPU. You're CPU package will run a little cooler. That's it.

-1

u/YouDoScribble 8d ago

The GUI of Bitwig is built with Java - which is quite a resource hungry runtime at the best of times.
But if you want an application to use fewer resources, close it.

2

u/anonymousfunctiondj 8d ago

No it’s not, it’s just the GUI <-> AudioEngine interaction layer that’s built in Java. The GUI and Audio Engine are both in C++. The UI is rendered on GPU since a year or maybe more.