Session → Properties Won’t Open in Mixbus 11.2.27 on Ubuntu Studio 25.10

EDIT Now I created a new session and it seems to work ok. So the session might be somehow faulty.

I wrote the message below on the Mixbus forum, but I noticed that in Ardour 8.12.0 the Properties menu appears, while in Mixbus it does not. What could be the reason for this? I’m also asking here in case someone has information about this.

Hi,
I’ve noticed a small issue with Mixbus 11.2.27 (rev 11.2-27-g30ded6ecf6) running on Ubuntu Studio 25.10 (Intel 64-bit). When I try to open Session → Properties from the menu, the window doesn’t appear at all.
Other menu items work normally, but the Session Properties window seems to be hidden or unresponsive.
Has anyone else experienced this issue, or does anyone know how I can access the Session settings in this setup?
Thanks in advance for any help!

1 Like

Yes, I have.
Here: The Properties Window Doesn't Appear [SOLVED] - #11

The issue for me simply had to do with using ‘non-conventional’ characters in the project’s/snapshot’s name. Something about that tripped-up that part of Ardour’s code… (Which I don’t think the devs looked further into.)

So what characters do/did you have in your session name? :thinking:
Can you copy and paste it exactly?

-J

The name of the session had the Scandinavian letter Ä. I renamed the session without the Scandinavian alphabet and the problem disappeared.

It may be that the same thing confused something else, because initializing a new session caused the program to crash. Now it seems to work again. So at least Scandinavian letters should not be used in session names, and probably not anywhere else, for example in the names of tracks, this is how I think now.

1 Like

This should be fixed.
‘Special’/‘Odd’/‘Non-standard’ characters should not trip-up Ardour/Mixbus like this.

And if left unaddressed, this will no doubt continue to impact others.


( I’m looking at you @paul / @x42 O___o … :grimacing: :face_with_monocle:)

@Sojuzstudio You might want to submit a bug report about this over here:
https://tracker.ardour.org/my_view_page.php

I cannot reproduce this, otherwise I’d already have fixed this.

Works fine here with umlauts (on debian GNU/Linux):

image

Note that this system has support for the German locale in /etc/locale.gen, even though Ardour itself run using en_US.UTF-8.

To fix this a recipe how to reproduce this would be very helpful. There is also no reason why the Session Properties Widow is in any way special with regards to session-name umlauts.

Could you create a simple session with that letter, zip/tar it up and send it to me (robin @ gareus .org) or upload load it somewhere? It would be interesting to see if that also fails here or for other users.

Could you create a simple session with that letter, zip/tar it up and send it to me (robin @ gareus .org) or upload load it somewhere? It would be interesting to see if that also fails here or for other users.

I’ve sent you the download link by email for your convenience.

Thanks you. I can reproduce this in Mixbus (loading the same session in Ardour is fine). If you run Mixbus from a terminal you see:

unhandled exception (type Glib::Error) in signal handler:
domain: g_convert_error
code  : 1
what  : Invalid byte sequence in conversion input

so indeed some text encoding problem.
I don’t yet understand why only Mixbus is affected, but I’ll start investigation…

3 Likes

Fix underway, meanwhile you can also sidestep the issue by enabling translation (they’re off by default in Mixbus) in Preferences > Appearance > Translations.

2 Likes

It’s funny you bring this up now, as I was just working on a recipe, finally.
In testing, however, I couldn’t replicate the illusive issue in Ubuntu studio… : /

But, on macOS Mojave, simply using a name like “ÄⅨ - Name Test 1” (-notice how “Ⅸ” is actually a Roman Numeral character, also) still somehow prevents the Properties window from opening.

Thanks for jumping on the trail! :+1: :grin:

-J

1 Like

Good to know, thanks! I love that I can use both Mixbus and Ardour and be involved in the community.

2 Likes