Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Mixbus 32C-9.1.153 crashes when creating new session
#1
Hi,
When I create a new session mixbus crashes and I get this in terminal:

(mixbus32c-9.1.153:9649): GLib-CRITICAL **: 22:05:11.489: g_main_loop_get_context: assertion 'loop != NULL' failed

(mixbus32c-9.1.153:9649): glibmm-ERROR **: 22:05:11.581:
unhandled exception (type std::exception) in signal handler:
what: std::exception

Sporings-/stoppunkts-felle (kjerne lagret i fil)


I've tried reinstalling, rebooting and updating my system but I've not had any luck. Has anyone else had similar issues?

EDIT: I get the exact same crash in Windows, so that's very surprising.. Could it be because I've got console 1 set up as a controller? Apart from that it's just a fresh install on both systems.
Reply
#2
Have you tried removing Console 1?
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Reply
#3
If it's a problem with Console1 adapter, try the recent library as I described in https://forum.harrisonconsoles.com/threa...l#pid64391.
I have it installed all the time and have no crashes.
MB 32C 9.1.324 / Ubuntu 22.04 LTS - KDE / Kernel 5.14.0 / AMD Ryzen 7 3700X 8-Core / NVIDIA GP108 Driver 390.147 / Focusrite Scarlett 18i20
Reply
#4
Thank you both. This was strange. Disconnecting Console1 made no difference but installing your library did, @Holger! Now I'm able to create new sessions. I haven't been able to test things properly but It doesn't crash atleast. So that indicates that, atleast for me, there is something broken with the regular console1 library that renders mixbus broken after Console1 has been selected as a controller.

@Holger, I'm still not able to select track 1 in my sessions. If I press track 1 on console 1 it still selects track 2 and so forth :/
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)