Bitwig

echosystm · Post by **echosystm** » Thu Mar 27, 2014 2:16 pm

EvilDragon wrote:It's the same on Win.

I figured as such, but didn't want the wrath of KVR if I was wrong.

I'm getting 12% CPU and 747mb RAM at idle, with one instance of Massive loaded.

The same test with a competing product idles at 5% CPU and 300MB RAM.

So yes, it's not your imagination.

EvilDragon · Post by **EvilDragon** » Thu Mar 27, 2014 2:24 pm

Oh yeah, not to mention the RAM usage... 300 MB JUST for the GUI process? Crazy...

virtualmark · Post by **virtualmark** » Thu Mar 27, 2014 2:35 pm

EvilDragon wrote:Oh yeah, not to mention the RAM usage... 300 MB JUST for the GUI process? Crazy...

??

Maybe in 1990 lol!

EvilDragon · Post by **EvilDragon** » Thu Mar 27, 2014 2:42 pm

Well, compared to Reaper's idle RAM load of just... 70 MB, yeah, it is quite something.

virtualmark · Post by **virtualmark** » Thu Mar 27, 2014 2:45 pm

EvilDragon wrote:Well, compared to Reaper's idle RAM load of just... 70 MB, yeah, it is quite something.

I wouldn't let it worry you. Most computers these days come with a minimum of 4-8Gb of RAM, who cares about a few Mb? Will it stop you from making music?

There's far bigger problems with this DAW imo, such as the lack of multi outs or the PDC.

Mivo · Post by **Mivo** » Thu Mar 27, 2014 2:59 pm

EvilDragon wrote:Oh yeah, not to mention the RAM usage... 300 MB JUST for the GUI process? Crazy...

Most of us don't run Bitwig on an embedded micro-controller.

Here, Bitwig takes up 268 MB of RAM. In comparison, Skype currently uses 190 MB of RAM, and the average tab of Chrome (one instance per tab) is around 80 MB right now, totaling over 800 MB RAM for just eleven tabs. VLC, with a 10 minutes low-quality video playing eats 60 MB.

virtualmark · Post by **virtualmark** » Thu Mar 27, 2014 3:03 pm

My internet browser is currently taking up 370mb lol.

UncleAge · Post by **UncleAge** » Thu Mar 27, 2014 3:19 pm

(BWS1.02/ i7/ 4GB/ OSX-10.9.2/ CoreAudio)
Using the demo at startup, default project empty instrument & audio track it loaded @ 664MB. However, without any interaction on my part the memory has been steady climbing. The window has never had focus as I started the TextEdit session while it was still loading. A couple minutes later and I am up to 699.7 and it’s still climbing, ticking away like a clock.

What would do this? A memory leak or is it making a log of some sort even though nothing is visibly going on?

[edit] It seems to have stopped at 741M.1B

virtualmark · Post by **virtualmark** » Thu Mar 27, 2014 3:20 pm

It's probably indexing your plugins and samples.

UncleAge · Post by **UncleAge** » Thu Mar 27, 2014 3:26 pm

Maybe you're right. I closed it and reopened and it started @570MB and then climbed to 763MB immediately and then stopped. Strange as I have not addded or moved any plugins around since Blue2 came out.

Anyway, on with the show.

p.s. The above does not relate to the Bitwig audio engine process, that has remained constant (memory wise) on startup.

nexttrack30 · Post by **nexttrack30** » Fri Mar 28, 2014 3:06 am

ZenPunkHippy wrote:
nexttrack30 wrote:could you please explain what's the difference between global processing and independant processing?
i read manual but i don't know which is good for what?
english not my native language doesn't help.
I will try, but it's quite technical.

In a host like Logic, Live or Cubase the application (host) and all plugins run in the same "space". If one of the plugins in this space crashes, everything crashes including your host.

What Bitwig does is give a new "space" to each plugin. If one plugin crashes, only that plugin will crash. It will not cause Bitwig itself to crash.

Peace,
Andy.

thx.

Lesha · Post by **Lesha** » Fri Mar 28, 2014 7:36 am

When idle, CPU usage is 0%, but the other Bitwig process "engine-x64" is constantly at 6-7% (Win).

nori.lam · Post by **nori.lam** » Fri Mar 28, 2014 8:25 am

I wish it would only use 750mb.
Im stuck at 1.3gb with every single startup and it pins my CPU to well over 100%
http://www.kvraudio.com/forum/viewtopic ... 5#p5693295

Bitwig, please take a look at this!

spinlud · Post by **spinlud** » Wed Apr 02, 2014 7:32 am

Anyway any improovement on cpu performance will be very appreciated. Actually bitwig takes from 50% to 100% more of resources than other daws i use. I hope will be a nice imprrovement for 2.0! cheers

MKzero · Post by **MKzero** » Wed Apr 02, 2014 10:19 am

So.. I just started BWS to see how it behaves on Linux.. This is a fresh Install of the BWS demo, opened only once after installation.

I see a CPU load of about 15% and it has been like this for about 20 Minutes. When using strace on the Bitwig process that produces the load(BitwigStudioEngine), I see lots of timeouts for futex waits:

Code: Select all

futex(0x23f9ba0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {1396428972, 996143657}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0x23f9ba0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {1396428973, 11285999}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0x23f9ba0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {1396428973, 26591397}, ffffffff) = -1 ETIMEDOUT (Connection timed out)

HW: Arch Linux, Kernel 3.13.8, AMD A10, 16GB RAM

I've also seen really high loads on my with drops in Jack2, produced by simply one FM4 with 4 effects behind it and only one dynamic parameter from an LFO. The laptop also has an AMD APU, a 3.12 Kernel with realtime patchset and the drop-outs and clicks always occur, no matter to what extend the Bitwig and jack processes are niced. I really would like to buy Bitwig and play the first live set on a gig in May, but at the moment this seems impossible with that performance

Bitwig

KVR Audio

CPU usage is ridiculous