Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
starting Mixbus3 hangs.. ( Solved )
#1
Starting Mixbus sometimes hangs, till I get the open session dialog,... sometimes it comes up after a minute, sometimes not at all.. it s kind of weird.. then Mixbus works normally..

the console sais

Code:
Mixbus3
bind txt domain [gtk2_ardour3] to /this/cannot/exist
Mixbus3.2.23 (built using 3.2-23-gc1e46fe and GCC version 5.2.1 20151028)
ardour: [INFO]: Your system is configured to limit Mixbus to only 4096 open files
ardour: [INFO]: Loading system configuration file /opt/Mixbus-3.2.23/etc/system_config
Loading user configuration file /home/kalimerox/.config/mixbus3/config
CPU vendor: GenuineIntel
ardour: [INFO]: CPU brand: Intel(R) Core(TM) i5 CPU         760  @ 2.80GHz
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: Loading default ui configuration file /opt/Mixbus-3.2.23/etc/default_ui_config
ardour: [INFO]: Loading user ui configuration file /home/kalimerox/.config/mixbus3/ui_config
ardour: [INFO]: Loading color file /opt/Mixbus-3.2.23/etc/dark.colors
ardour: [INFO]: Loading ui configuration file /opt/Mixbus-3.2.23/etc/clearlooks.rc
ardour: [INFO]: Loading ui configuration file /opt/Mixbus-3.2.23/etc/clearlooks.rc
EngineControl::set_state
Found nothing along /home/kalimerox/.config/mixbus3/templates:/opt/Mixbus-3.2.23/share/templates
Announcement is:

any ideas? thanks! [/quote]
Reply
#2
You could start with various command line options like "--disable-plugins" or ""--no-announcements" (use "-h" to see all options) and see if any of these have an effect.
Reply
#3
Try
Code:
GTK2_RC_FILES=/nonexistent Mixbus3

see also http://tracker.ardour.org/view.php?id=5605#c15464 (site is currently down, dreamhost is having nightmares)
Reply
#4
(04-19-2016, 08:37 AM)x42 Wrote: Try
Code:
GTK2_RC_FILES=/nonexistent Mixbus3

see also http://tracker.ardour.org/view.php?id=5605#c15464 (site is currently down, dreamhost is having nightmares)

host is still down, i ll try later again! thanks!

yeah i tried various options, same results..
Reply
#5
Quote:EngineControl:Confusedet_state

Another clue. maybe some auto-connect to jack timeout/failure? Can you try to move the existing configuration out of the way

quit mixbus,
Code:
mv ~/.config/mixbus3  ~/.config/mixbus3.bak
restart mixbus.
Reply
#6
It s working again! I had to delete .config/Mixbus and start again, and it works again! It s strange that it happened on two machines simultaneously, so maybe it was messed up by a manjaro update somehow..
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)