New Mac OSX Daw - Harrison Mixbuss

[taoyoyo]

Has anyone had any issues with the Live/Jack/MixBus combo with the APC40?

When I change Live's Audio Prefs to Jack (rather than my Duet) the APC loses connection with Live. When changing back to the Duet and relaunching, the APC is back up and running.

Also, the load time of Live is increased to about a minute with Jack as Audio device. (Part of this might be that I have 20 in's and outs selected for Jack).

Am using the latest versions of all software.

Cheers,

Alan

[supamonsta]

ok, as I'm since long times thinking about purchasing another DAW for the mixing stage, as I found Digital Performer much too much complex for just mixing stems coming out from live, and as DP, Logic pro or Cubase cost all more than 300euros, that I don't have,

I took the plunge (is that good english?), and purchased MixBus. You got to know they charge taxes for non american states. so, they first say 51 euros (!!!), then you validate the purchase, and they say you will charged about 62 euros (TVA / VAT !!!)

anyway, that's still a good deal...

if it worked.

I have Jack .82 installed. Mixbuss installed. System rebooted.

then launch Mixbus app ===>>>

Could not find installation directory / Please reinstall Sidechain Compressor

I knew there were problems with some audio unit plugins, but I didn't know it could prevent the app to even open itself!!!


"please reinstall sidechain compressor", WTF!!!!! ????

I've got at least 2 sidechain compressor plugins, and they work great in Live.


any idea?

[UKRuss]

Does it crash? Or start up and give you that message?

[supamonsta]

I click on the app icon, then a few seconds pass, then a little window appears with the text I quoted above in it.

I click on the "OK" button of this little window, and then, nothing. Mixbus doesn't launch at all.



I will give a test to their customer support

EDIT: Fuck the last smiley, I'm not finding this funny, in fact

[UKRuss]

yeah, i found them really good. Send them an e-mail including the 'crash report', they can tell you the score..almost certainly it's one of your compressor plugs though. I had to uninstall GR2.

[supamonsta]

well, I don't want to uninstall some of my plugins! no problem if I can't use this sidechain comp in mixbus, but I need it in Live... !!!!

fuck that

thanks for the answer, I sent them an email with the bug report.

Cheers



EDIT:

I dragged and dropped the Sidechain Compressor.component from the plugins directory to the desktop, and I'm now able to launch Mixbus.

It seems only ONE plug caused the bug, that's not so dramatic.

as I've got 3 different sidechain compressors in my plugins, I don't know yet if it's the one I use the most... I'll check this.

OK, now let's try Mixbus!!

cheers


EDIT 2 : well, In fact routing live tracks to mixbus thru jack isn't so easy... I can't manage to have jack virtual tracks as audio out's choice in live tracks...

feedback soon

[UKRuss]

You gots to make sure you've set up enough virtual ports in Jack, then they should be available in Live once you activate them in Lives prefs.

[supamonsta]

yes, I set 32 ins and 32 outs in the jack virtual tracks option.

but in Live, after setting jack for live's audio output, and enabling 1+2, 3+4, 5+6, 7+8 etc for the outputs, I still can"t choose the jack virtual tracks as audio outputs for live's tracks...

I'll try furthermore,

cheers


EDIT :

You're the man!...of course. Glad we thought out loud. Well played sir!

well, I may probably be good in theory, but I'm still stuck and unable to have jack virtual channels appear in live's channel's output choices...

[supamonsta]

After configuring jackpilot (soundcard, same buffer as in live, same sample rate as in live -44khz, 32 virtual ins and outs, connect to physical device : on), then starting jack, then I select "jackrouter" for live's output in live's prefs:


"Live does not support 0 as a sample rate for the device "jackrouter (32 ins; 32 outs)"

0 ???

shit I'm not gonna manage routing live's tracks to mixbus via jack for a while.... seems I'm really stuck.

any help?


EDIT : the same messager appears if I change

- sample rate to 48 or 44khz (always inputting the same sample rate in liv and jack)
- number of virtual channels (from 8 to 32)
- buffer size
- enable or disable connection to physcal device in jack prefs

[nuxnamon]

anyone have any luck in getting a Mackie Control in "logic mode" working in Mixbus.. i booted up the MCU in logic mode and kept getting errors.. I tried messing with the mixbus midi/preferences but couldn't figure out the midi ports.. it's not as straight forward as i thought it would be.. dang, i think it was easier getting the mcu to work with other DAWS.. i'm stumped.. anyone?


Error instantiating MackieControlProtocol: The Mackie MCU driver will not use a port with device=ardour
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: Error instantiating MackieControlProtocol: The Mackie MCU driver will not use a port with device=ardour
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: Error instantiating MackieControlProtocol: The Mackie MCU driver will not use a port with device=ardour
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: Error instantiating MackieControlProtocol: The Mackie MCU driver will not use a port with device=ardour
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: Error instantiating MackieControlProtocol: The Mackie MCU driver will not use a port with device=ardour
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as mmc port
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as mmc port
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as midi port
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as midi port
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as mtc port
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as midi port
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: Error instantiating MackieControlProtocol: The Mackie MCU driver will not use a port with device=ardour
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: Error instantiating MackieControlProtocol: The Mackie MCU driver will not use a port with device=ardour
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as mmc port
[ERROR]: control protocol name "Mackie" could not be initialized
[ERROR]: mcu already used as midi port
[ERROR]: control protocol name "Mackie" could not be initialized

[timothyallan]

All this farking around and you guys could have bought a copy of Cubase which everyone knows has a much warmer mix bus.

[alex.the.forge]

All this farking around and you guys could have bought a copy of Cubase which everyone knows has a much warmer mix bus.

yeah but only if you rub the dongle for a bit or stick it down your trousers for a while

the whole point of mixbus is you don't have to do that

[leedsquietman]

don't rub it too much, it might lose it's load .... which is not covered under the license and you must buy the software over again at 500 bucks

[fishmonkey]

anyone have any luck in getting a Mackie Control in "logic mode" working in Mixbus.. i booted up the MCU in logic mode and kept getting errors.. I tried messing with the mixbus midi/preferences but couldn't figure out the midi ports.. it's not as straight forward as i thought it would be.. dang, i think it was easier getting the mcu to work with other DAWS.. i'm stumped.. anyone?

i think this post might help you out:

http://ardour.org/node/3053

btw, you are probably better off asking about this stuff on the Ardour forums...

[nuxnamon]

just fyi... from harrison..

There is an error in one of the config files that causes this problem. We are going to fix it in the next release. For now, one of the ardour developers has created a program that you can run to fix this problem.

To apply this fix,

1. Quit Mixbus

2. Download the following file and run it http://misc.leviathan-avc.com/Mixbus/Mi ... ix.app.zip

3. Click the option to generate debug output and then send the contents of that file back to me (it will allow us to confirm that the correction has been made). You will notice that the setting device=ardour changes to device=coremidi

Please let me know the results.

Thanks,
Todd Naugle
Harrison Consoles