reported.
but clearly thats getting us nowhere
Latest News: Bitwig Updates Bitwig Studio to 5.2
Bitwig unusable at buffers lower than 1024 gfx related?
-
Mister karloff Mister karloff https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=398527
- KVRer
- Topic Starter
- 15 posts since 16 May, 2017
-
Mister karloff Mister karloff https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=398527
- KVRer
- Topic Starter
- 15 posts since 16 May, 2017
I think its about time for me to give ableton a try. The lack of response from the bitwig devs is shameful and telling. The feature set is awesome to bad the audio engine is so problematic.
-
- KVRAF
- 5756 posts since 29 Sep, 2010 from Maui
FWIW, I was having this problem under windows. For me, it turned out to be
a few VST3 plugins I use regularly, that were causing the spikes. I have since
switched to using them as VST 2.4 versions only, and that has eliminated my
problem completely. Unfortunately, VST 3 has for the most part, been more
trouble than its worth IME.
Just sayin...
-Cheers
*BTW: My VST3 issues have definitely seemed to be graphics related.
Ive seen this often, in FL Studio, Studio One, Reaper and Now
Bitwig. In every case, using the VST 2.4 versions, has solved
the problem.
a few VST3 plugins I use regularly, that were causing the spikes. I have since
switched to using them as VST 2.4 versions only, and that has eliminated my
problem completely. Unfortunately, VST 3 has for the most part, been more
trouble than its worth IME.
Just sayin...
-Cheers
*BTW: My VST3 issues have definitely seemed to be graphics related.
Ive seen this often, in FL Studio, Studio One, Reaper and Now
Bitwig. In every case, using the VST 2.4 versions, has solved
the problem.
