1. Sometimes the meters quit responding
2. The first time a 3rd party VST is inserted the activity meters etc show up just fine. Then once the project is saved and reopened they are not showing activity (within the VST). Case in point; Slate's FGX.
 
 

Overall I have not experienced buggy behaviour but there has been some strange happenings around saving or trying to save under a different name.
 
Rather than closing the project and re opening, try quitting the whole program first and then re open Mixbus again from scratch and re open the projcet. I have found that gets things back to normal again.
I also find that is the only way to change the buffer settings. You may need a higher setting too to stop it from falling over if you are pushing your system hard.
 
There were some plugs that did not play nice with it too and I have generally removed any from the scan. I found it better to make a special folder and only put a copy of the VST's in there you want to work with. Rescan again but only point to that folder. Then you will end up with a sane number of plugs preent. The Harrison ones and the ones you know work correctly and want to use.
 
 

Well, well; this gives me new resolve to resist temptation...

I haven't had a whole lotta time to play with it yet. Still trying to figure my way around it. I'm reading that control surface support is only for osx/Linux? That's kinda a bummer if it's true. Any windows users been able to use a control surface with it?

Leadfoot
I haven't had a whole lotta time to play with it yet. Still trying to figure my way around it. I'm reading that control surface support is only for osx/Linux? That's kinda a bummer if it's true. Any windows users been able to use a control surface with it?

Got an email response from Harrison about control surfaces. They said that once MIDI is available in the Windows version control surfaces will be able to be used.

DeeringAmps
Well, well; this gives me new resolve to resist temptation...

I should point out these behaviors were not show stoppers in any way just a niggle. I really meant the OP in a bit of tongue in cheek sort of reporting (i.e. no software is without some issue).

"a bit of tongue in cheek sort of reporting"

bapu

Leadfoot
I haven't had a whole lotta time to play with it yet. Still trying to figure my way around it. I'm reading that control surface support is only for osx/Linux? That's kinda a bummer if it's true. Any windows users been able to use a control surface with it?

Got an email response from Harrison about control surfaces. They said that once MIDI is available in the Windows version control surfaces will be able to be used.

Cool! Thanks Bapu!

Hey Leadfoot,
 
I was experiencing anguish over the use of a stereo VST on a mono track (it can't be done accroding to Harrison and their manual). 
 
What I tried was creating/inserting a stereo track and then routing the mono track to the stereo track. Then I inserted the stereo VST. All was goo until I tried to solo that stereo track and it mutes all tracks (including the mono track, which I wanted to hear with the VST).
 
After asking Harrison support if I had done something wrong they explained (in simpleton terms to a simpleton like me) that was normal behavior (DOH!!!! of course it is BAPU!!!!).
 
The said all I really needed to do was create the stereo track and then move the mono clip(s) to the stereo track and delete the mono track. Simples.

Hey that makes sense! I'll have to remember that trick. Thanks for letting me know! Sounds like Harrison has good support. That's good to know. Thanks Bapu!