clintmartin
hmmm. I'm stuck at work and I'm waiting to get home and install MB3. Have any of you had luck getting melodyne to scan? I never got the 32bit to scan.
 

Clint,
 
I did get Melodyne to scan in but when I open it, it says it is not licensed and is in playback mode. Studio One v3 does the same thing to me though.
 
I can run Melodyne Editor in standalone mode and everything is fine there. Maybe something I'm doing wrong with the vst's.
 
What I can't get is Ozone 5 to scan in and there is no listing in the Black List folder and Ben is too busy right now with easier issues so I'll wait until he has time. I think Carl said he had issues scanning Ozone also?

I installed last night with no issues at first.  I first tried audio tracks and they worked great.  Then I added midi tracks, but that started crashing Mixbus after a few minutes, but then it got better like it was learning from the previous crashes.  However, I had one real head banging dilemma--I had the hardest time trying to figure out how to change the midi instrument in a track where midi was already installed.  It was clear when adding the midi track how to insert any instrument, but when I wanted to change the instrument for another one, I could not figure it out (at first).  So I read the manual, but that was no help at all.  In fact, the manual is anemic and insufficent; I would say that Harrison really needs to write a real manual that is more than a few pages long.  Finally, I learned to remove the instrument and to use the plugin manager to install an instrument on the already established midi track.  I know there is a learning curve, and I am willing to put the effort in.  Having worked with Sonar since its inception, and with Studio One for a couple year, I find Mixbus, well, different.  I love the console work flow, but the midi workflow seems strange, if not just different.
 
BTW, I honestly love the "character", that "Harrison sound", that this Mixbus gives to audio tracks.  They have that nailed down and absolutely have it right.  However, their newness to the midi instrument world shows in how they have documented it (or not) and how midi routing and instruments are added to tracks.  Perhaps this is a problem with Ardour as its platform; I do not know.  Still, it is nice to have midi as an option.  
 
Hopefully, a better manual will come, and the crashing will get less frequent, or some updates will arrive soon.  Just my 2 cents!
[[EDIT:  I need to make a correction.  I just found the pdf version of the Mixbus3 manual and it is 324 pages long.  So I apologize for misleading anyone.  The midi section (in my opinion) still needs a description of how to change instruments; it mentions how to load them when creating a midi track, but not how to change them.  Nevertheless, I was wrong about the length of the online manual; it is more than a few pages, actually 324 pages.  
Here is a link:  http://www.harrisonconsol...opic/about-this-manual]]

Thanx for the review Celius.

Most definitely they have "the sound" down...I also think that the stereo field in Mixbus
seems "wider" when I listen...but that may just be me...

In any event, MB3 can only improve with time...so that's good to know...

rtucker55
I just noticed something else on the Harrison website:
 
The initial release of Mixbus v3 is shipping with control-surface protocols disabled.
An upcoming release will re-enable the control protocols, which include MIDI controllers, Mackie fader protocols, and OSC ethernet control.
 
Guess I need to give them a call Thursday because if I can't use a MIDI controller (keyboard) it would not be very use full for me. 

I noticed this too, and had a brief exchange with Ben on Gearslutz about it. Midi keyboards are supported, it is just the protocols for control sufaces that are disabled. The wording was ambiguous in their FAQ.
 
I got an upgrade email today, but don't know if I want to bite. I had to abandon the previous version because of stability problems.  The console workflow was cool, and it sounded great. But this is of little use if it runs sporadically and unpredictably. So I'm sitting back watching.
 
Anyone reporting success or failure please include your OS specs. Thanks.

Mixbus 3 working great here. All plugins scanned in fine...no crashes so far. I haven't tried midi yet, just importing some wav files and looking around. I'm glad I used ardour for a few weeks to get familiar. If anyone has questions or wants me to try something...let me know.

Well, this is interesting. I must have done something wrong during the install and scan. I just checked my main 64bit vst folder and several of my vsts/vstis have a .fsi, or .fsb, or .err placed after the .dll.
 
So I see things like iZotope Ozone5.dll.fsb and iZotope Ozone5.dll.err   The ones with the .fsb and .err are the ones that do not show up in MF3. It appears that MF3 is marking my vsts vs. putting the blacklist info in the folder it belongs in.
 
It may be time for a System restore.

Yep, I'm seeing the fsi after my vst3 plugins too. I don't see where it's hurting anything, but it's strange.

Definitely an issue with Ozone. I haven't noticed the adding on to the end of the .dll but I'll check. I really would like to get Ozone working in Mixbus 3 but it may be interesting to see what can be done with just the tools in mb.
One other issue has reared it's head! I am running 2 Studio-Capture interfaces in ASIO. All my other DAWs see all the available inputs and outputs. Mixbus 3 only sees 1 interface. Mixbus 2 sees all of them! Why not 3? Anyone have a hint?

I was really wishing for control surface support with v3. Any idea why it's disabled?

I read a Harrison Mixbus 3 control surface (Hardware) is being made so I'm sure it will come on line at some point. So far I'm very pleased with it. I love the custom meter and the monitor thing.