asked Oct 27 '15 at 01:47 by mcphable (171)

4
4

Bitwig CPU usage is around 2x higher than the exact same plugins/presets in Ableton Live 9. I have no idea why and don't know if this is on Bitwig's radar for a fix. System info: Laptop - MacBook Pro (Retina, 15-inch, Late 2013), 2.3 GHz Intel Core i7, 16 GB 1600 MHz DDR3, and 500 GB SSD Hard Drive. DAWs - Bitwig Version 1.3.0 (I'm guessing 64bit but not sure how to find that), Ableton Live Suite 9.2.3 64bit.

When I setup an Instrument Layer in Bitwig with one instance of Pianoteq w/ a specific piano preset and one instance of Diva w/ a specific pad preset (multicore enabled), the DSP is at the halfway point (when I hold down the sustain pedal and play as many notes as it will process). If I do the exact same setup in Ableton w/ an Instrument Rack and use the same plugins and presets and play as many notes as possible w/ the sustain pedal, the CPU usage barely gets to 26%.

I manually adjusted the Buffer Size in Bitwig from 256 samples when on Auto, up to 2048 samples. Those are vs 256 samples in Ableton. Changing the Buffer Size in Bitwig helped get it closer to Ableton's CPU usage but it's still higher PLUS I play this setup with several additional tracks and lots of extra processing live. So, I'll be on the edge of maxing out the CPU in Bitwig PLUS that much latency makes playing live keyboards an unnecessary challenge.

Please help if there's something else I should try (aside from using an audio interface -- my new RME Babyface Pro is on order but I think that if this is a Core Audio driver issue or something else in the software, I'd rather get that looked at and addressed, rather than masking the CPU usage issue and/or possible software issue with RME drivers/hardware).

Anyway, I really do like Bitwig and am trying to make the transition from Ableton but I need this thing to be 100% ready for playing live. Thanks for your help!!

Did you try to use the 1.1 version? I have a dramatic performance drop starting with 1.2 on plugin usage (NI & Waves). Would be interesting if it's related to plugin processing. I'm using the late 2013 MAcBook Pro 13" Retina i7 2.8GHz 16GB 512GB SSD - so very similar setup.

  — (Oct 27 '15 at 18:52) durchgedreht

Thanks for the suggestion! That might be enough for Bitwig to pinpoint when the CPU usage got off track. FYI, I like the added features in 1.2 and 1.3, and so going back to 1.1 isn't of interest when I can keep using Ableton for a little while longer. Plus, I've created several projects in 1.2 and 1.3 that probably won't open in 1.1, right? Either way, thanks for the suggestion and hopefully Bitwig sees this and chimes in!

  — (Oct 28 '15 at 19:14) mcphable

Hi The indipendent hosting of VSTs in BitWig will take more CPU. If your computer is not up to the task you can change the settings for plug-in management in Prefrences:

If the Only as bit-bridge option were selected for a 64-bit operating system, then 64-bit plug-ins are loaded within the audio engine, and any 32-bit plug-ins are loaded within their own single process. (Within a 32- bit operating system, only 32-bit plug-ins are available, and they would 14. ADVANCED DEVICE CONCEPTS 310 all be loaded within the audio engine.) This option requires the fewest CPU resources.
  — (Nov 21 '15 at 17:10) Pop-I

I just did a "stress test" on my mac pro, osx el capitan, latest update

44100 HZ / 256 buffer on all tests / 120 bpm U-HE DIVA with same bass patch playing the same midi clip in arrangement view (looped 2 bars) then I duplicated the track until audio crackled

results

LOGIC PRO X 10.3.1 handled 107 tracks before audio cracking. chapeau. ABLETON LIVE 9.7.2 handled 77 tracks BITWIG 2.1.1 handled 83 tracks.

all legit software. all was identical in the 3 daws, just DIVA, no sends, no effects, nothing.

also, consider that, in case you, as myself, like to use a lot of modulators (not used on this test), ableton's maxforlive modulators are way more taxing on the cpu than bitwig's.

anyway, I've found the daws cpu meters pretty uninformative. the real deal is how many tracks you can play until audio crackles.

just try yourself and let me know the result here, I'm really curious.

link

answered Jun 08 at 22:20 by Cat3rer (41)

@drezz, you know you can click on that 'chip' icon on the left of the CPU meter to get a proper window with statistics and all? would be even better, if it would show utilisation per track & plugin, like e.g. Studio One 3 does.

link

answered Jul 13 at 11:52 by antic604 (174)

Believe me, Iam sharing your pain a lot. I also experience heavy CPU-related problems the last time. Even really small projects start to crackle or sometimes even freeze completely for a few seconds.

System: HP Pavilion g6, extended with i7 (4x) 2.2 GHz and 16GB RAM. Not a real"powerhouse" but I think it should not have such severe problems... and it has not with Live, ProTools and FL Studio!

Is there any known issue that will be fixed somehow or should we just get for some stronger computers? :P

Peace out! B.L.O.

link

answered Oct 28 '15 at 22:12 by B-L-O (11)

Super annoying! Dont´you test version updates properly? Tried to work with your software and it worked quite well so far. Now graphics lags heavily with just one 4 bar sample!!! Unusable like that. Can´t zoom into waveforms properly/smooth etc.

link

answered Nov 19 '15 at 02:05 by SUMTRAX (41)

Hi The indipendent hosting of VSTs in BitWig will take more CPU. If your computer is not up to the task you can change the settings for plug-in management in Prefrences:

If the Only as bit-bridge option were selected for a 64-bit operating system, then 64-bit plug-ins are loaded within the audio engine, and any 32-bit plug-ins are loaded within their own single process. (Within a 32- bit operating system, only 32-bit plug-ins are available, and they would 14. ADVANCED DEVICE CONCEPTS 310 all be loaded within the audio engine.) This option requires the fewest CPU resources.

link

answered Nov 20 '15 at 19:13 by Pop-I (41)

any chance the bitwig2 cpu meter can be made bigger. it's quite hard to read it really., and would be much more satifying if there was a bigger graphic readout and perhaps even a numerical indication % to see the current status of cpu used. cheers.

loving Bitwig2 in general though. Awesome update....... :)

link

answered Jun 08 at 19:12 by drezz (11)

edited Jun 08 at 19:13

Indeed @Cat3rer that matches my very limited testing, note that I think the original poster may have had a threading problem due to plugin stacking.

link

answered Jun 08 at 22:32 by ejgallego (76)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×16
×5
×4

Asked: Oct 27 '15 at 01:47

Seen: 3,471 times

Last updated: Jul 13 at 11:52