Mixbuss

I'm pretty excited about it too. Just having access to all the cores of my cpu now is worth the asking price. The only thing that concerns me is the fact it's built on Ardour 4... which I can't get working at all on my Windows machine. I'm most likely going to wait a while to see how it works out for other folks first. There's plenty of discussion about it at the Mixbus forum.

Hmmm. As long as it sounds the same I think I'll stick to the old version. It was perfectly stable on my mac, and I never ran out of memory or CPU. Considering $40 is more than twice what I paid in the first place, I don't personally have a reason to upgrade. Any ideas if they've changed the summing and/or tape sound at all?

I would only ever use it for mixing and possibly SOME audio recording. I won mine in a competition so I might break down and cough up the $40 anyway. I always liked it but there are limitations in 2.5

Any of you guys know if one can freeze and unfreeze tracks in Mixbus a la REAPER? Also curious if anyone has attempted to work with Nebula or Acqua plugins in Mixbus 3 yet, and if so, what is your experience?

I truly expected much more to be fixed and improved. I mean, this is HARRISON we are talking about, maker of some of the greatest, finest consoles ever!

Yeah I think that's prolly the case Matter of time I hope

Anyone fancy doing a null test to see if the summing and tape emulations have changed at all? :)

"Magic ID would be okay for me as long as neb setups handled it" Not sure what you mean about NebSetUps ... I hand-edit each custom XML file with a unique ID. NebSetUps uses your Master Nebula XML file as a template, carrying the same ID number to each custom setup. It would be nice if ZAB's app could maintain/manage a database of these unique ID's an auto-generate a unique one for each new custom Nebula ... would be handy ... till then, I save a NotePad txt file to keep track. BTW ... this has NO affect on Nebula performance. All it does is allow a DAW or Chainer to determine that each Nebula is a separate/unique plugin ... rather than treating them as one plug. Then you can only see/use the one. hope that helps.

REAPER does NOT use the ID to identify plugins. I believe it uses the actual VST name. I use BIDULE within REAPER. Reaper sees all, BIDULE uses the ID so I had to make unique ID's ... then everything worked.

Very disappointed... PDC still not fully supported!