System crashed, freezing Bitwig and Scaler 3

Scaler 3 Support Bug Reports
1

But this time, instead of killing Bitwig as I am usually forced to do, I reasoned a bit

Scaler and Bitwig were frozen, but the audio was unstoppable… :thinking:

So I run the Task Manager, un-hidden the Bitwig processes chain, and I just killed the Audio process: bingo!

I had my project live again and working, so I hope to have nailed the issue enough

I remember that Scaler 2 had a log to send to devs after crashes; I hope that Scaler 3 has one as well; If I find it, I’ll upload it there

In the meanwhile a few data:

OS: Windows 10 64bit Pro
Bitwig Studio Producer: 5.3.13
Scaler 3 latest release
Hardware:
Processor: Intel(R) Core™ i7-3770 CPU @ 3.40GHz 3.40 GHz
RAM: 32,0 GB
Graphic card: NVIDIA GeForce GT 1030 (2 GB)
Audio card: Komplete Audio 1

Windows events:
Nome dell’applicazione che ha generato l’errore: BitwigPluginHost-X64-SSE41.exe, versione: 5.3.13.21983, timestamp: 0x6891f044
Nome del modulo che ha generato l’errore: ntdll.dll, versione: 10.0.19041.6456, timestamp: 0x7ec9c15d
Codice eccezione: 0xc0000374
Offset errore 0x00000000000ff489
ID processo che ha generato l’errore: 0x24e0
Ora di avvio dell’applicazione che ha generato l’errore: 0x01dcdc06355adaa2
Percorso dell’applicazione che ha generato l’errore: C:\Program Files\Bitwig Studio\bin\BitwigPluginHost-X64-SSE41.exe
Percorso del modulo che ha generato l’errore: C:\WINDOWS\SYSTEM32\ntdll.dll
ID segnalazione: 5a330974-bbcf-4990-83b6-feb57a47a17c
Nome completo pacchetto che ha generato l’errore:
ID applicazione relativo al pacchetto che ha generato l’errore:

2

Now I am reasoning about this post

I’ll try to have both Scaler, Bitwig, and Komplete audio panel set to “Run this program as an administrator”

I used the Windows Compatibility test and found that they consider my Bitwig more suitable for Windows 8, but they have the same opinion about Scaler 3, so I think that their tool is not exactly reliable :thinking:

3

I found that after I tkill he Audio process, Scaler 3 return to the default (empty) state

I can clearly upload the state I saved, but having Scaler less absent-minded :grin: could be useful, if I forget to save its state