Mixbus, Mixbus32C v9.1.153 now available!

[Ben@Harrison]

Our store has been updated with a new software update for Mixbus and Mixbus32C:  version 9.1.153

Due to high download volume, we use the FastSpring download service to provide you with localized, fast downloads of the Mixbus software.  You will be prompted for your email address and area-code so FastSpring can provide you a fast download link.

Mixbus software installer: Mixbus-v9-demo

Mixbus32C software installer: Mixbus32C2c-v9-demo

There is no charge for this software update.  If you have a v9 license, then the new software will find your license file without needing any steps to re-authorize it.  If you do not have a license, you may choose to update to the newest software, but it will continue to work in 'demo' mode.

version 9.1.153 provides several hotfixes for both Mixbus and Mixbus32C since 9.1.95:

• Fixed the 'green background' appearing in some parts of the mixer window, when first drawing or resizing
  
• In addition to "Editor->Cut/Copy Range Section" there is now a "Delete Range Section" which removes the selected Section of the timeline (shortcut: shift+ctrl+delete to trigger "delete section") including all markers, automations, and playlists
  
• Selecting a playlist for a Track(s) is now undo-able
  
• Fix Opaque MIDI regions so they are really opaque (block the notes in lower regions) ... this bug was introduced in 9.1.96
  
• Fixed a few issues with setting the initial tempo, and the popup tempo dialog, and hot-plugging midi devices for the 'tap tempo'
  
• After copy-dragging some midi notes/chords, the copied notes will now all be selected so they can be copied again
  
• In sessions with multiple tempo changes, BPM-aware plugins were being given the wrong bbt position or tempo value, in some cases.  This has been fixed.
  
• Likely fix for an occasional shutdown crash, related to the audio engine
  
• Windows:  Fixed a bug in MIDI device latency-compensation which resulted in MIDI recordings being 'early' on the timeline (Windows MME only)
  
• Mac: Likely fix for an occasional crash on Mac related to midi input
  
• ...and several more minor fixes and improvements
  

As always, feel free to write us (mixbus@harrisonconsoles.com) with your thoughts on this new update!


Best Regards,
-Ben Loftis
Harrison Mixbus product manager

[Andy76]

Amazing work as usual, thanks!

[Klaus]

V153...Mac
Editing markers will not place them 'in line' top to bottom...timewise

I remember to have reported this with earlier versions...
Thanks

Klaus

[Stephane Morisse]

Mixbus32C 9.1.153 hangs up and freezes every now and then and uses more computer resources. Going back to Mixbus32C 9.1.96. 

As usual, this is useless for others if you don't specify the platform and OS...

[Holger]

Mixbus32C 9.1.153 hangs up and freezes every now and then and uses more computer resources. Going back to Mixbus32C 9.1.96. 

As usual, this is useless for others if you don't specify the platform and OS...

Windows 11, 8 cores i7, 32Mb ram, 1G SSD

Just a note: I don't see this behaviour on Linux. So it really seems to be OS or installation specific?

[Klaus]

V153...Mac
Editing markers will not place them 'in line' top to bottom...timewise

I remember to have reported this with earlier versions...
Thanks

Klaus

Reopening the project seems to place the markes in the right order in the location view...

[Klaus]

Mixbus32C 9.1.153 hangs up and freezes every now and then and uses more computer resources. Going back to Mixbus32C 9.1.96. 

As usual, this is useless for others if you don't specify the platform and OS...

Windows 11, 8 cores i7, 32Mb ram, 1G SSD

Just a note: I don't see this behaviour on Linux. So it really seems to be OS or installation specific?

I had freezes to in OSX
And leaving the project open as is ...seems to create augmenting cpu use...
Klaus
OSX Yosemite - High Sierra

[davidg25]

Thank you!

dave g.

[jeff_sloan]

Sadly, now EVERY time I re-open MB, I have to re-connect the metronome to the outputs.
What gives?

[Nathan@Harrison]

Sadly, now EVERY time I re-open MB, I have to re-connect the metronome to the outputs.
What gives?

I am not seeing this issue.  Can you email support with screenshots/video showing the issue?