Mixbus, Mixbus32C v9.2 now available!

[Ben@Harrison]

@dh1340: I'm sorry to hear that you are having those crashes!

If you'll please write our support: mixbus@harrisonaudio.com and provide the exact details on your os version and which version of the BF plugin, we'll try to recreate the crash here.

-Ben

[Ben@Harrison]

@Subzero:

I assume that zooming in & out doesn't fix the issue?

As madmaxmiller eluded, it might be a color-preferences issue. If you visit Preferences->Appearance->Color and click "reset to defaults", does that fix it?

-Ben

[johne53]

Next try - tried to bring in the Harrisson bass Flow Plugin on CH 1:
Result : CRASH:

-------------------

Does this only happen with one particular session? I tried adding Bass Flow to a few sessions here but didn't see any problem.

Also (with regard to the Console 1 plugin) apparently it's available in both VST2 and VST3 format - so whichever format you've got, maybe give the other one a try..?

[Klaus]

Sorry to have to say...
MB32C9.2.105, Macos 10.13.6
Imported yesterday a live multitrack, made some adjustements, saved as snapshot.
Double clicked the .ardour file today and crashes...also after several attempts

Process:              Mixbus32C-9 [614]
Path:                  /Applications/Mixbus32C-9.2.105/Mixbus32C-9.2.105 .app/Contents/MacOS/Mixbus32C-9
Identifier:            com.harrisonconsoles.Mixbus32C-9
Version:              9.2.105 (9.2.105)
Code Type:            X86-64 (Native)
Parent Process:        ??? [1]
Responsible:          Mixbus32C-9 [614]
User ID:              501

Date/Time:            2023-10-12 10:41:24.791 +0200
OS Version:            Mac OS X 10.13.6 (17G66)
Report Version:        12
Anonymous UUID:       


Time Awake Since Boot: 670 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:      0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0  libsystem_kernel.dylib        0x00007fff58a34b66 __pthread_kill + 10
1  libsystem_pthread.dylib      0x00007fff58bff080 pthread_kill + 333
2  libsystem_c.dylib            0x00007fff589901ae abort + 127
3  com.harrisonconsoles.Mixbus32C-9 0x000000010fd2a97e StartupFSM:tart() + 238
4  com.harrisonconsoles.Mixbus32C-9 0x000000010f404ce2 ARDOUR_UI:tarting() + 418
5  libgtkmm2ext.dylib            0x0000000111fbfd38 Gtkmm2ext::UI::run(Receiver&) + 216
6  com.harrisonconsoles.Mixbus32C-9 0x000000010f83ea7c main + 2780
7  libdyld.dylib                0x00007fff588e4015 start + 1

Opened in v9.1.134, worked...
Restarted and opened again in v9.2.105 and now it seems to work

I have to say I had similar behaviour with previous versions - try till it works ? ...

Klaus

[nachoestasborracho]

Nice try - Installed - tried to put Console 1 in CH 1 :
Error occurred on Wednesday, October 11, 2023 at 11:26:50.

Mixbus32C.exe caused a Stack Overflow at location 00007FFE4CB4DBD5 in module TextShaping.dll.

AddrPC          Params

CRASHES all the time, even the Console 1 is disconnected in Preferences...

seems to me I have to go back to  9.0 as 9.1. doesnt work as well.... what a pitty
--------------------------------------------------------------------------------------------------------
Next try - tried to bring in the Harrisson bass Flow Plugin on CH 1:
Result : CRASH:

-------------------

{EDIT:   crash details removed by administrator }

This is my find as well, Console 1 vst3 plugin started crashing on load in the last few Mixbus versions, on Mac.
I reported the error to Nathan and Ben a few months ago, hope it gets solved soon.

While Console 1 native support as a controller for Mixbus is appreciated, the vst3 plugin is very important for those of us who rely on Console 1 for the fader unit or just for Console 1 software.

[Klaus]

Sorry to have to say...
MB32C9.2.105, Macos 10.13.6
Imported yesterday a live multitrack, made some adjustements, saved as snapshot.
Double clicked the .ardour file today and crashes...also after several attempts

 {some crash details removed by admin}

Opened in v9.1.134, worked...
Restarted and opened again in v9.2.105 and now it seems to work

I have to say I had similar behaviour with previous versions - try till it works ? ...

Klaus

Seems 'double clicking' the .ardour file crashes MB32C9.2.105
If MB32C9.2.105 is launched first, and the project opened from within the sel box @ launch,
it seems to work...
Sent supp mail to Mixbus support, hope the adress still works

Klaus

[Ben@Harrison]

@Klaus : I'm sorry that you had trouble!

Double-clicking the .ardour file is not part of our test procedure. The preferred method is to open it from the Mixbus "Open" dialog.

I'll investigate whether we can fix that crash, but in the interim you should launch the program first, and then navigate to the session you want to open.

Best,
-Ben

[Klaus]

@Klaus :  I'm sorry that you had trouble!

Double-clicking the .ardour file is not part of our test procedure.  The preferred method is to open it from the Mixbus "Open" dialog.

I'll investigate whether we can fix that crash, but in the interim you should launch the program first, and then navigate to the session you want to open.

Best,
-Ben

I think to remember that this was in early stages a problem and got fixed ... then

Thanks Ben
best

Klaus

[Dingo]

Did a fresh install of v105 ARM (no v8 reference) and find that Command+up / down arrow does not move tracks on the Edit page

[Ben@Harrison]

@Dingo : it "works for me" but I have seen occasional reports of this problem. Perhaps there is some obvious way to trigger this problem, and we are so stuck in our workflows that we haven't noticed it here. Let me know if you can find any other clues.

-Ben