Ludicrous DSP issues, Please Help Me!!!
-
- KVRer
- 9 posts since 13 Sep, 2016
Hello Everyone and Anyone,
I have been using Bitwig for about two years now and sort of recently I have began to run into trouble.
One of my biggest likes about Bitwig was that it seemed very stable and used less system resources on my Mac. Yet recently, playback in Bitwig is unbearable and the DAW is becoming unusable.
Its a little strange, because when I check my systems activity monitor I am usually always around 25% to 35% but the DSP graph in Bitwig shows high DSP usage with multiple and continuous spikes that go up to 100%.
I've tried playing around with the audio settings in Bitwig and checked my audio interface to see if any settings aren't proper. My OS, Bitwig, and audio interface are all updated to the latest version as well.
Please help out, the DAW is almost useless right now.
Computer Specs:
Late 2014 iMac
4 Ghz intel core i7
32 GB 1600 MHz DDR3
AMD Radeon R9 M295X 4096 MB
DAW applications are on internal SSD
Samples are on another separate SSD
Write to disc is another separate SSD
Audio Interface Specs:
Universal Audio Apollo Twin Duo and OCTO Core Satellite
I have been using Bitwig for about two years now and sort of recently I have began to run into trouble.
One of my biggest likes about Bitwig was that it seemed very stable and used less system resources on my Mac. Yet recently, playback in Bitwig is unbearable and the DAW is becoming unusable.
Its a little strange, because when I check my systems activity monitor I am usually always around 25% to 35% but the DSP graph in Bitwig shows high DSP usage with multiple and continuous spikes that go up to 100%.
I've tried playing around with the audio settings in Bitwig and checked my audio interface to see if any settings aren't proper. My OS, Bitwig, and audio interface are all updated to the latest version as well.
Please help out, the DAW is almost useless right now.
Computer Specs:
Late 2014 iMac
4 Ghz intel core i7
32 GB 1600 MHz DDR3
AMD Radeon R9 M295X 4096 MB
DAW applications are on internal SSD
Samples are on another separate SSD
Write to disc is another separate SSD
Audio Interface Specs:
Universal Audio Apollo Twin Duo and OCTO Core Satellite
You do not have the required permissions to view the files attached to this post.
Last edited by BallofYarn on Sat Aug 05, 2017 6:49 pm, edited 1 time in total.
-
magickalmutagen magickalmutagen https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=370360
- KVRist
- 239 posts since 28 Nov, 2015
Not sure why it would behave like that, but finding out what you've changed recently such as hardware or software, or any related settings, could help as reverting those changes could fix the issue. It shouldn't start behaving differently out of the blue. Something must have changed. Perhaps one of the laptop's components is failing.
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
-
- KVRer
- Topic Starter
- 9 posts since 13 Sep, 2016
magickalmutagen wrote:Not sure why it would behave like that, but finding out what you've changed recently such as hardware or software, or any related settings, could help as reverting those changes could fix the issue. It shouldn't start behaving differently out of the blue. Something must have changed. Perhaps one of the laptop's components is failing.
Its a desktop model computer, an iMac. They usually hold their integrity longer and other than Bitwig the computer runs very well. I suppose it's not outside the realm of possibility.
The only hardware change that occurred was in December when I allotted my data to the different SSD's. There were no problems with that change at all during the immediate time afterwards. No problems with accessing data from the external drives, they worked just fine for Logic.
In my frustration I decided to update my software but that was yesterday and the issue has been occurring longer than that. So the issue was present before updating and still there after updating.
-
- KVRer
- Topic Starter
- 9 posts since 13 Sep, 2016
Yes, more or less. The last project I worked on the symptoms were there but not quite as grave as this project. The same choppy popping and stopping bullshit occurred but not as heavily..maki wrote:With every project?
When I started the latest project it seemed like it was off from the start but still very useable. The more I added parts and plugins the worse it got.
Initially I work with the clips view and then move on to the arrange view. When I was done in the clips view and starting to move clips into the arranger is when things become disgustingly hard to work with.
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
Sounds like a faulty RAM to me somehow. Wich Mac OS?
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRer
- Topic Starter
- 9 posts since 13 Sep, 2016
.maki wrote:Sounds like a faulty RAM to me somehow. Wich Mac OS?
macOS Sierra
version 10.12.6 (16G29)
Do you know of a way to check if RAM is not working properly?
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
-
- KVRer
- Topic Starter
- 9 posts since 13 Sep, 2016
.maki wrote:Is that an original iMac or a hack?
Its an original iMAC. I added third party RAM after purchasing it though, I don't think that qualifies it as a Hackintosh.
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
http://osxdaily.com/2011/05/03/memtest-mac-ram-test/
for example, could also be a faulty plugin or a faulty Os Update. Did you update via combo update or from the App Store in to 10.12.6?
for example, could also be a faulty plugin or a faulty Os Update. Did you update via combo update or from the App Store in to 10.12.6?
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRer
- Topic Starter
- 9 posts since 13 Sep, 2016
Simply through the app store..maki wrote:http://osxdaily.com/2011/05/03/memtest-mac-ram-test/
for example, could also be a faulty plugin or a faulty Os Update. Did you update via combo update or from the App Store in to 10.12.6?
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
Well, read that thread i'd say, do system tests, maybe create a new user Account just for testing, with just bitwig installed to see if it is a software conflict. Remove plugins one by one etc. lot's of stuff to proof, good luck!
Also send in the project to Support with detailed description of the issue.
Also send in the project to Support with detailed description of the issue.
JamWide - a cross-platform Ninjam client for DAWs
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
A combo update can be loaded from Apple, it is a full OS installer instead of just a few updated files from the App Store. People say it is supposed to be less error prone, and offen fixes weird issues.
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRer
- Topic Starter
- 9 posts since 13 Sep, 2016
I just did a hardware test through the Mac's native diagnostic tool. The test gave no negative results and stated the hardware was fine..maki wrote:Well, read that thread i'd say, do system tests, maybe create a new user Account just for testing, with just bitwig installed to see if it is a software conflict. Remove plugins one by one etc. lot's of stuff to proof, good luck!
Also send in the project to Support with detailed description of the issue.
I suppose I do have a lot of other things to test as well :/
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
Memtest does a real stress test, might be more helpful. Does it also happen with s fresh project and just bitwig devices?
JamWide - a cross-platform Ninjam client for DAWs
