Harrison owners check your email for the direct links to the downloads.
 
New feature:
 
 
Realtime export : Normally, Mixbus maximizes your CPU to perform the fastest-possible export. However, some users have external devices, such as rackmount analog gear or external MIDI synthesizers, which cannot be used at faster-than-realtime speed. In the past, we required these users to manually create a bounce track and mixdown to it, rather than using the normal Export features. Realtime Export provides all the same features as a regular export, but it limits the engine to run in "real time" so external gear can be utilized during the export. This new features is accessed from the "time span" tab in the Export dialog.
Improvements:

• Harrison plugins now wait 30 seconds before the control panel is locked. This provides more time to evaluate the plugins.
• In the past, the "session end" marker would move automatically in certain situations. For example: when you recorded past the "End" marker. This has been changed: once the user has grabbed and manually set the "End" marker, it will no longer move automatically.
• Improve the "spectrum analysis" window with better FFT resolution; and show the frequency under the mouse's location.
• The area underneath an automation curve is now filled with color. This makes it easier to see automation curves, and especially boolean automation (mutes, etc).
• Various fixes to stem exporting: provide more consistent latency offsets on tracks that are exported as stems.
• Transport scrub-bar has been re-enabled: Click and drag inside the scrub-bar to scrub the timeline forward and back at varying speed 
  
• OSX-specific fixes:
• AU sidechain fixes: plugin "pin connections" will show extra bus inputs even if they don't flag themselves as sidechain inputs.
• SoundToys plugins would cause a stutter each time they checked the iLok license file. This has been resolved ( in both Mixbus v3.5 and upcoming SoundToys release )
• In the Keybindings editor window, trying to assign a keybinding with the "Cmd" key would fail. This has been fixed.
• Further improvements to AU plugin drawing speed issues. The problem occurs when both Mixbus and the plugin use a specific Apple drawing function. The Mac OSX causes a serious delay in some specific drawing functions. Mixbus uses this function to draw the waveforms in the editor; some plugins also use this function; if both the editor and the plugin use this function excessively, then Mixbus and/or the plugin will draw slowly. Some solutions include: Zooming out on the timeline (so the playhead doesn't have to update as often), hiding the editor window while adjusting a plugin, or choosing a different plugin. The problem is noticeably worse on "retina" displays. Dragging the editor and/or plugins to a different monitor might improve performance on retina systems.

Got em both downloaded and installed this morning.

When you say both do you mean M32C as well you lucky man!
 
Anyway I have downloaded but not installed yet but would not mind knowing if it is playing nice. The last update seemed to play nice for me.

Yes Jeff, I have both.

Can someone splain the difference between the 2 Mixbusses ?
the web site blurbs don't really say much.
Mr. Baps ??

Apparently there is a bug in V3.5 not serious but some previous projects may open in V3.5 with some levels altered. Read here:
 
Oops!
 
Yesterday, we released Mixbus version 3.5. Today we found a significant bug, and we encourage all users to stop using v3.5 immediately. We have provided a newer version below.
 
Details of the problem: When you open Mixbus, the channel input trim values might be applied twice, so a 3dB trim value will result in a 6dB audible change. The wrong value is not written into the session file, so if you saved the session with 3.5, no permanent harm is done. However your session may exhibit very different levels when you audition it in v3.5. We apologize for not recognizing this problem in the final steps before we released v3.5.
 
This problem does not affect all users, but we suggest that everyone download the update, v3.6.
 
 

Haven't had that with Sonar in while ;-)
 
Mind you, support for Mixbus is very good. Just had an issue where some plugs did not show after plugin upgrades (and it was 100% user error, me not being able to give it the proper paths), but Ben from Harrison got back to me quickly ...

They are nice guys and extremely helpful and I like the program very much.  There are some great tutorials on it too.
 
In answer to timidi's question they are both very similar in many ways but for some reason M32C is quite a bit more expensive.  But what you are getting here is the EQ from the original M32 mixer.  It is a lovely EQ and has a very definite sound.  As someone who taught audio engineering for a while using a real Harrison console, the EQ is very lovely to use.  Silky smooth top end.  Amazing response in all parts of the spectrum.  So they plonk this on every channel. Mixbus has very useable standard EQ as well now on each channel.  Simple but effective and you can always insert plugins of course.  But the original channel EQ would be fabulous.
 
M32C has more buses.  They have included a virtual instrument in M32C as well.  Not sure how it sounds though.  There is quite a bit of info here:
 
http://harrisonconsoles.com/site/mixbus32c.html
 
I really like the idea of mixing in another DAW.  It is a very cool way to go.  Do all the arrangement stuff and pre mix parts of your mix in your fave DAW then mix stems and things in Mixbus.  It is also has a very nice GUI and has a very analog feel and layout.  Plus it does sound rather excellent and a little different to mixing in your normal DAW.  I like the way electronic music sounds in it as well.  When you are emulating a lot of analog fat sounding parts, Mixbus seems to bring it all out a little more in the final stages.  I use it to master in as well quite often.  The mastering plug-ins and track plugs are also excellent too.
 
I did not experience any issues with 3.5 but 3.6 is the way to go apparently.  It has been very stable for me on my system for quite a while now.  I have not handed my external midi system over to it yet though and sequenced any midi parts in it yet.  I am doing that inside Studio One but maybe I should and check it out for midi timing and feel etc.  I am pretty happy with how Studio One handles all that though.
 
They are still dangling the carrot in front of me for the offer of $149 for it instead of the advertised $299 and the more I talk about it the more I am interested.  Bapu is going to come along now and say buy it Jeff!

 
Thanks Jeff.
For me, the big question is, What is "Enhanced 4th generation DSP engine"?
Sounds like, for an extra $200, you get the Harrison Mojo. Otherwise, you don't.
I think I'm mostly interested in the emulated Harrison analog circuitry and tape and console sims (the mojo).
Sort of a cheaper way without an Ilok to match up to Steven Slate quality, maybe? 
You'd think for $300, you'd get unlimited busses though.
Anyway. Just thinking out loud.

mixbus already got the "Harrison Mojo". so that must be 3rd generation for whatever that means (although to me "next generation something" sounds really cheesy; I prefer proper descriptions to marketing buzz)
 
If you haven't got mixbus yet, I'd recommend to go straight for 32C because of the extra buses (which is the main drawback in the "regular" mixbus).
 
If you can live with fewer buses, want to check out the sound, intend to mix only stems, etc go for the cheaper version - you might be lucky to get a promo later (the used to run M32C for $149 for mixbus owners, but don't if they still do that)