Lol it's not dos, just a console script

Here's a little mod to the script if you don't want the command window to stay open.

set VST_PATH=C:\Plugin Files\MixBusVSTs
cd C:\Program Files\Mixbus\bin
start Mixbus2-32.exe

Cheers.

I exchanged a few emails with Ben from Harrison. He was very responsive to some problems I was having. I don't think he'd mind sharing this:

How is this app for CPU consumption ????


I have an older laptop ( would you beleive only ONE core !!! )

That I wouldn't mind doing some remote tracking with ...

Did you see this?


http://www.harrisonconsoles.com/mixbus/website/requirements. html

Dam!!

http://www.murga-linux.com/puppy/viewtopic.php?t=72402

There is a link to a fast small linux preconfigured audio studio
in the top post, it has ardour, reaper in wine, and a range of instruments
and fx, using a fast realtime kernel.

Burn the .iso (less than 400 meg) to a cd or dvd, and reboot using
the early boot menu, or change the bios boot-order to put
hard-disk after the cd/dvd.

This will run in ram, and on first shut-down,
will prompt you to allow a save-file to be created for you,
in C:\

Cheers

Hi All,

We are almost ready to launch our first update for Mixbus on Windows! This update will add VST path management, speed up importing, and recognize more soundcards, among other issues.

We'd love to find a few testers who can take time to try out the new package. We are interested in users who had one of these issues:

1) Windows systems that are installed on drives other than C:
2) Windows systems using non-Latin characters in the username or other folders
3) Systems with 64bit audio drivers who were unable to see their soundcards in Mixbus without using ASIO4ALL.

Testing should only take a moment. It should be fairly clear whether the new version fixes your issue or not. We aren't looking for general testing at this time; only users who had problems starting up and/or finding their soundcards.

Please send us an email if you are interested: mixbus@harrisonconsoles.com


Best Regards,
Ben Loftis
Harrison Consoles

The update (2.0.6) is out. Downloading now and about to test it.

I think they might have been listening to me as the Linux version now includes Reverb (based on GVerb I think). Hopefully it will reach all versions. Now for a Dither option too?

Cheers

So, when I try the demo on Windows 7 it is completely unusable/unintelligible. There is absolutely no text anywhere except for little boxes in places where text would have been. This makes me think that maybe I'm running at a different screen resolution than the program is expecting? Or maybe something to do with missing fonts, etc.???

I tried it on an older XP machine just to compare and to see what it might look like. However, the Win7 machine is where all my music software and music files live. The Win7 machine also has the audio card.

Uninstalling the demo for now.

Hi Sequent,

Sorry about the inconvenience. We've found a "permissions" problem in our installer that might cause this problem on some systems. Mixbus can't find your system fonts so they all show up as "boxes".

If you can write us at mixbus@harrisonconsoles it might help us solve the problem faster.

Will post here when we have a fix.

Best,
Ben Loftis
Harrison Consoles

Ben, thanks! I didn't write to support before because usually demo versions are not supported. So I was hoping to get some tips here... didn't expect to hear from the company itself! No inconvenience on this end.

I thought it might have something to do with my fonts or video settings as per my original post.

I'm unable to get to my studio computer at the moment, but I will try installing again asap and advise. The concept of Mixbus is great and it's nice to get away from all the extra bloat of your typical all-in-one daw and just focus on the mix.

Cheers!

@Sequent: we have a new package which will likely fix your problem. Please write us at mixbus@harrisonconsoles.com to get the fix.

I have updated the packages on the store so all new Demo users and purchasers will get the new version.

-Ben

Trying demo now. Well... was trying until I got my Win7 BSODed.

First, there's some problem with (I think) releasing ASIO device. When I run Mixbus for the first time after reboot, it loads and works OK, but if I will close it and run again, it will hang with "Starting audio engine" on a splash screen. And just right after that I've got BSOD.
I'm on Win7-x64 with E-MU 0202 ASIO (Yes, I know that the driver is beta, that E-MU 0202 is not officially supported on Win7... but it works rock solid with Reaper).

Second thing, that I didn't understand is routing. Just a simple task: I have kick drum channel (that is mono, why do I need it to be stereo?) and I want to put Tessla PRO plugin on it. The plugin is stereo (has 2 ins and 2 outs), so Mixbus tells me that it can not insert that plugin on this track. Maybe I was in Reaperland for too long and I forgot that there's such things as mono/stereo plugins, but... that looks kinda nasty for me.
But that was just a first try, so I will download manual and try again if there will be not so much BSODs

Mixbus 2.0.6
(built from Ardour svn 11499)

It still doesn't quit jack properly when MixBus exits. That's probably why it hangs on the starting audio engine splash, the next time you run it. Also, it is very sensitive to ASIO drivers so I wouldn't use it with beta versions.

I've had no luck getting past the starting audio engine splash on XP. Even ASIO4ALL now doesn't work with it.

I'm testing it on Win7 today.