Ludicrous DSP issues, Please Help Me!!!

Official support for: bitwig.com
RELATED
PRODUCTS

Post

Maybe before you go into twisting every stone you should consult bitwig support and send in the project. Those spikes are something they are looking to solve afaik.
JamWide - a cross-platform Ninjam client for DAWs

Post

What plugins are used in the dramatically effected projects? I've been having similar issues on macbook pro, so far I've found 2 plugins that if instantiated cause spiking/lags/crashes here (vst3 versions of softube modular and heartbeat) as long as I don't use them (possibly others, i've not tested everything, just all vst3 instruments) things are more stable, there's still an optimisation issue beyond these strange plugin problems but at least the ui doesn't hang etc.

Post

That is to say, I don't think you have a hardware fault. There appears to be some bug. I've given up for now tbh, gone back to Logic till next update at least. Though, a bit of trial and error should figure out which plugins not to use. If there's a vst2 alternative that works, great, there's the temporary 'fix', if all versions break bw then, treat as none compatible I guess and if required for workflow might have to work elsewhere at least in part. Support have been very unresponsive, no suggestions for a week then just a generic 'further clarify your system and all version numbers', I replied instantly, that was 3 days ago. :roll:

Post

well, it's weekend now.
JamWide - a cross-platform Ninjam client for DAWs

Post

kingslim wrote:... there's still an optimisation issue beyond these strange plugin problems but at least the ui doesn't hang etc.
do you swap memory on your harddisk?
JamWide - a cross-platform Ninjam client for DAWs

Post

I saw your thread re. memory swapping, noted with interest, I've not tested, disabling sys integrity protection to disable virtual memory is a bit of a leap, was hoping for others to chime in and confirm as viable fix (or explain why I shouldn't), or for the devs to investigate and address the conflict in an update or something. As I said, I've stopped trying for now. Hopefully you're onto something, time (and someone else) will tell. I only added my 2 cents to save OP from pointlessly 'twisting every stone', I know how frustrating that can be.

Post

I have CPU spikes as well with just 20-30% CPU load on a new 2017 15" Macbook PRO.
Last edited by Enrize on Sun Aug 06, 2017 8:36 pm, edited 1 time in total.

Post

wich vsts are causing the trouble?
JamWide - a cross-platform Ninjam client for DAWs

Post

Now, I'm no mac expert, but I wonder if, for any reason this is related to another piece of hardware?

For example, even macs have wifi issues. Also, have you tried running things w/o the Apollo ?

Post

Enrize wrote:I have CPU spikes as well with just 20-30% CPU load on a new 2017 15" Macbook PRO.
before you edited the post you said it is some vsts that cause this. So now you say it is any cpu load? Also with just native devices?

If not please specify wich vsts make trouble. Try to help at least a little if you bother posting at all.
JamWide - a cross-platform Ninjam client for DAWs

Post

Try setting your display resolution to 1080

Post

.maki wrote:
Enrize wrote:I have CPU spikes as well with just 20-30% CPU load on a new 2017 15" Macbook PRO.
before you edited the post you said it is some vsts that cause this. So now you say it is any cpu load? Also with just native devices?

If not please specify wich vsts make trouble. Try to help at least a little if you bother posting at all.

There is no need to post individual VST. Bitwig in general is very 'spiky' performance wise. I'm comparing with other DAWS I own and jump between such as Reaper, Cubase and Ableton (all most recent versions)

... and for the record the best performance seems to be had with Reaper.

If the devs are looking into cpu spikes then great, it gives me hope, because it's my fave DAW.

EDIT: Performance with BW2 native stuff is great, it's when adding VST that CPU spikes appear, even from low CPU use.

Post

arrakeen wrote:I'm comparing with other DAWS I own and jump between such as Reaper, Cubase and Ableton (all most recent versions)... and for the record the best performance seems to be had with Reaper.
That's the price of having a quasi-modular DAW where modulators can change the parameters of the plug-ins at an audio rate, you can swap plug-ins on the fly or alternate playback from two sources (arranger and clip launcher). As a result in Bitwig (and in Live) there can be much less buffering and drop-out protection compared to 'traditional' DAWs like Reaper, Cubase, ProTools or Studio One.
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

Enrize wrote:I have CPU spikes as well with just 20-30% CPU load on a new 2017 15" Macbook PRO.
Just a thought, check your CPU not set to throttle when plugged-in in power settings. (I don't know MAC)

I found my 'overclocked' setting from PC builder allowed just 5% power... I set it to always be 100% and it removed much of the spiking.

Post

Hi guys. I am getting crazy CPU spikes also. I can't figure this out either. The CPU monitor shows that it's not spikeing but it's choking. It starts to choke. I have tried getting rid of certain VST plugins. . Ok actually the only new VST plugin I bought was bx ssl e plug in alliance. I'm not using VST 3 because they are not working properly in BITWIG yet. Anyone shed some light here. This version is really bad. I have contacted tech support also.

Using MacBook quad core 2.8 ghz Turbo Boost 2015 Sierra
BitWig 2.1.3.
Last edited by Pprimo on Sun Aug 13, 2017 7:06 pm, edited 1 time in total.

Post Reply

Return to “Bitwig”