Quantcast
Channel: KVR Audio
Viewing all articles
Browse latest Browse all 4760

Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.) • Re: Beta Testing of Bitwig Studio 5.2

$
0
0
So I sent this second email to them:
On Sat, 17 Aug at 1:37 AM , Michael Gray <stipesvigilo@gmail.com> wrote:
Package update will not stay off. Controls won't respond after a few minutes and entire DAW "locks up". Must force "end task" shut down through Task manager and then get the same thing I get every time on reopening it. It seems this insist on updating packages (which I continually turn off) keeps popping up while doing other things and IDK, maybe it's choking the processes? It turns itself back on every time I try to add a track. And I think it's there every time it locks up. I also want to uninstall the one package that is there, but can't find any way to do that. This screen shot is what I get on reopening and after canceling or retrying the request to reload the crashed project. (Either way, same result.)
Finding this annoying to the point of it being unusable.

System is Win10 Xeon 4C CPU 32GB RAM on SSD Drive.
Bitwig has finally responded with this short email:
it looks like suddenly all your USB devices are gone. Are you using a hub and are they all connected to the same hub?
Really?
My reply:
The controllers are on a USB3 hub connected to a USB3 port. The Audio is connected directly to the computer (no hub) via USB port. But this is what happens after Bitwig Crashes and it will not allow restarting these with a complete reboot of the computer. But the initial problem is that Bitwig itself stops responding and locks even though the music controllers and audio still work. Keyboard/mouse move across screen but moving any volume slider in Bitwig doesn't. And this "nag" notification of installing/updating packages always shows as part of this lockup (even though I continually turn them off). Even after "end task" of Bitwig, trying to open any standalone or another DAW after shows the restarted Audio as "not available. This only happens in Bitwig 5 and not Cubase 13. It also did not happen in Bitwig 4.
Feels like they're trying to make this a hardware issue rather than fix the issue...

ICBW here, but I think it has to do with this persistent "nag to install/update packages" that I not only don't want, but want to remove the one that is installed as well.

Anyone here have an idea of how to uninstall a package and get this notification to stay off?

Statistics: Posted by BBFG# — Mon Aug 19, 2024 7:37 pm



Viewing all articles
Browse latest Browse all 4760

Latest Images

Trending Articles



Latest Images