Follow up to Mixbus 10 busses not showing plug ins

#1

My previous post above, I was unable to get the PROC (plug-in) window to show. I reinstalled linux, causing me to have a fresh install of Mixbus32C v10. I followed the suggestions from the setup wizard for the GUI scale, and now I can see the procs in Mixbus 10 on Linux.

Mixbus32C V10 was already installed on my Win10 machine, and I was also unable to see the PROC on the busses. I had already reset the scaling and that did not help.

@BenLoftis To fix this I ended up deleting the config file, and letting Mixbus do a fresh setup. I accepted the GUI scaling suggested. This fixed the problem on the Win10 machine. So now, Mixbus32C V10 works on my machine in Win10 and Ubuntu 24.04 LTS.

So my guess, is there was some setting from V7, V8, or V9 that was possibly causing the issue. I am posting in case there are others with a small res screen that have had the same issue with Mixbus.

#2

Nice find!

Do you perhaps still have the old config file/folder to compare settings?

#3

Yes. I saved the old Mixbus 10 Appdata folder. I could zip up the new and the old together and email them to you. Would that work ? I don’t know what sensitive data, if any, is located in that folder.

#4

There’s no sensitive data in there (except perhaps recently used session names).

but you can email it to robin@gareus.org

#5

They are sent. I am interested in what you find out.

Thank you.

#6

The most obvious difference is in ui_config

+    <Option name="mixbus-num-strip-elems" value="0"/>
-    <Option name="mixbus-num-strip-elems" value="1"/>

Is it OK to share your zip with @BenLoftis from Harrison who may have more insight into this?

#7

Please do. The OLD config was imported from V9(32c), V9 from V8(32c) , and V8 from Mixbus 7 ( not 32C )…which maybe was the culprit, going from non 32C to 32C and copy the settings ? If it allowed it…

#8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.