Does the latest version Mixbus 32C 8.2.170 work on others? It won't start after installation. Freezes Plugin scan at startup(vst). Plugin scanning should be disabled by default when starting.
AvLinux MXE latest version. The earlier Micbus 32C version works completely normally.
Works fine here on my Kubuntu 22.04-based system. Any output that can give you a hint if you open a console and start it from the command line?
(02-14-2023, 04:22 PM)Sojuzstudio Wrote: [ -> ]Does the latest version Mixbus 32C 8.2.170 work on others? It won't start after installation. Freezes Plugin scan at startup(vst). Plugin scanning should be disabled by default when starting.
AvLinux MXE latest version. The earlier Micbus 32C version works completely normally.
Ok here as well. Thought I have not done any plugin scan. Kubuntu 22.10.
Hi
Works on Ubuntu studio 22.04 so far.
Cheers
(02-15-2023, 04:08 AM)Jostein Wrote: [ -> ]Works fine here on my Kubuntu 22.04-based system. Any output that can give you a hint if you open a console and start it from the command line?
The long story ends as follows:
(mixbus32c-8.2.170:5565): glibmm-CRITICAL **: 21:51:25.629:
unhandled exception (type Glib::Error) in signal handler:
domain: g_convert_error
code : 1
what : Invalid byte sequence in conversion input
I'm no expert on this, but it looks like a language problem/bug. What happens if you first type this in your console (if you are not using English locale):
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
..and then run again from the same console window as the export commands?
You might even change all the LC_* environment variables as well.
(02-14-2023, 04:22 PM)Sojuzstudio Wrote: [ -> ]Does the latest version Mixbus 32C 8.2.170 work on others? It won't start after installation. Freezes Plugin scan at startup(vst). Plugin scanning should be disabled by default when starting.
AvLinux MXE latest version. The earlier Micbus 32C version works completely normally.
My setup is same, AvLinux MXE 21.3 and yesterday updated Mixbus 32C 8.2.170, normaly works.
I using default locales, because I had
Mixer save/recall settings
Pavol
(02-15-2023, 04:59 PM)Jostein Wrote: [ -> ]I'm no expert on this, but it looks like a language problem/bug. What happens if you first type this in your console (if you are not using English locale):
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
..and then run again from the same console window as the export commands?
You might even change all the LC_* environment variables as well.
Thanks for the answers. I'll look at this later today when I get to the machine...
(02-15-2023, 04:59 PM)Jostein Wrote: [ -> ]I'm no expert on this, but it looks like a language problem/bug. What happens if you first type this in your console (if you are not using English locale):
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
..and then run again from the same console window as the export commands?
You might even change all the LC_* environment variables as well.
Tested, same error message.
I installed the newly released Ardour 7.3.0 and it works fine here. There is something strange here.
Just a guess: you might be seeing an apparent hang due to the b0rken
LV2 plugin, installed by default on recent AVL versions. I have to skip over scanning it lots.