$500 in Canada. I guess they figured out how to change the $79 paradigm. Good things never stay good. 

ampfixer
$500 in Canada. I guess they figured out how to change the $79 paradigm. Good things never stay good. 

This is no indication that they're abandoning the regular Mixbus though is it? 

Just got the mail and watched the video, but I'm quite confused and not understanding their marketing concept.
 
32C came out of nowhere and there is no clear picture what the difference to 3.3 is - is it just 4 additional buses and more EQ ?!?!? or is the core engine also next generation, etc.
 
I'd really like to see a feature comparison chart like Cake has for their packages ... and know if they will force users into upgrading by discontinuing the 3.x line. Not knowing the pros makes me think 149 USD is a bit steep.
 
Just getting 3.3 to work in my hostile Roland environment (which is a bit tricky) so I'd be quite keen to know what's changed under the hood.

Reading between the lines
 
Probably under the hood (MIDI, AUDIO and stuff) is the same (since they are both based on Ardour 4).
 
4 Extra buses can be (as one Harrison forum user said) either great or not enough.
 
What is (mainly) different is the whole concept of what the EQ's do. Mixbus3 is based on their digital console DSP engine whereas Mixbus 32C is based on the 32C analog console.
 
So I see it (32C) as a new console emulation option that adds 4 more buses (of which I was one of the early requesters that MB3 have more of). I only wish that MB3 will get back ported to have 12 buses too, but since I bit the bullet on 32C I can have the best of both worlds (as options that is).
 
The main "gotcha" is that if you took an unfinished MB3 project into MB32C it is (almost) like starting over since the EQs are different and can't transalte back and forth. So if I were to try and decide which I liked for a particular piece I would choose to import stems/track into both and approach like I was attempting a mix at two different "studios" or DAWs. 
 
Once I think I have a handle on MB3 vs. 32C I'll probably know which I'd do a particular project on and not go for both simultaneously.

After several hours on Mixbus 3.3 I see really stable behavior (given that I cycle the "buffered input" option every time I start).  I did not have a single crash while doing a " static mix" (i.e. without automation). All plugins I tried (Harrison, NI, WAVES, Overloud) worked fined.
 
A brief summary of thoughts and experiences (+/-):

• Sound quality is indeed different and it seems to give me what I'd like to hear with a lot fewer plugins in use than when I mix in Sonar (+)
• Very intuitive. Hardly any need for the manual; did read it but not really necessary (+)
• EQ knobs on buses really seem to fit the required needs. All lot you can do by adjusting bus EQ (+)
• EQ knobs are very tiny and little movement with mouse gives me a lot of dBs (-) which I hope to get better if I get the control surface to work
• Control surface support is there, basic functionality given straight away for my CS i.e. faders, mute, solo (+). Hoping to get access to EQ and compression via MIDI remapping
• Automation drawing by hand crashes Mixbus fairly quickly (plugin independent, simply the process of adding points to new automation track seems to do it). Some parameters in plugins I could not get to respond to automation (-)

For the "unplugged" session that I was mixing 8 buses were sufficient, for the usual projects it won't. So if I really start to like this thing I might have to bite the bullet and also buy Mixbus 32C - although the 4 extra buses might just get me there or still might be a few short of my usual needs
 
 

Has anyone found that when you select right click context options on plugins, they don't "take" and you have to select them a second time? For instance to delete a plugin I sometimes have to select "delete" twice. And sometimes the plugin pin connection manager won't appear until I've selected it a second time.

Another problem I occasionally see is when I double click a plugin in the strip to open its window, but a different plugin's window appears instead. Thought I was going mad a couple of times last night with that.

I have had to right click twice a few times to delete a plugin...that is a bug. I haven't ever seen the wrong gui for a plugin. I'll look out for that.