Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 12, 2015 4:22:29 GMT -6
Hi guys, finally, the control surface support of Mixbus 3 has been released in form of the last interim release between 3.0 and 3.1. The guys at Harrison do awesome work to fix bugs and bring the software forward to be a very mature software. I am already using the latest interim release available and am impressed by the stability, features and optimization in comparison to Mixbus 2. For those who have not updated yet or have no license and waited for this feature, it is there now for registered Support Forum users. I consider this a game changing feature, though....
|
|
|
Post by keymod on Dec 12, 2015 5:28:09 GMT -6
This is really good news. I am looking forward to using it more, once I finally get settled into the new digs. I imagine that the proposed Harrison Controller is not far behind?
|
|
|
Post by popmann on Dec 12, 2015 16:17:37 GMT -6
Talk to me about what "support" for controllers means in Mixbuss. Cubase had a VERY unique implementation on MCUs....which is why I bought MCUs....I'd like to try Mixbuss now that they're using CA/ASIO...the Jack Install is what never really got installed/configured right in the demo....
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 13, 2015 10:43:04 GMT -6
Ah, i see. I had no chance to check this out by myself yet and it will probably take a while. The implementation is not complete and seems to concentrate first on the MCU fader and button automation. Since it is an interim release it is not meant to be complete or an official release candidate now. So the implementation is incomplete. From my experience with 2.5 that had control surface support on linux, it had on one hand the standard MCU implementation, faders, buttons, jog shuttle....and on the other hand the console elements with midi learn, so you could fit the control you have to the harrison console elements. This wasn't available on windows. I was in the middle of testing and configuring, but it worked, while the new version 3 came out and i stopped working on this, i might go for it latest with the arrival of 3.1 for the implementation of US-2400 for MCU and 2 extenders emu and BCF and BCR Behringer control surfaces for console elements most probably. I am not sure i can dig deeper into this before christmas now, the first interim with CS support came today in the morning, but will report back as soon as i have more personal experience with the new Harrison version. Btw, the hidden jack install with the 2.5 installer worked pretty good in XP, 7 and 8.1, no problems here.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 13, 2015 10:57:26 GMT -6
This is really good news. I am looking forward to using it more, once I finally get settled into the new digs. I imagine that the proposed Harrison Controller is not far behind? AFAIK the Harrison Mixbus team really concentrated on the software and completion of the feature set and bug fixes to get a product as stable as possible and set this high on the priority list. This is understandable, because, if people buy a (fairly) expensive controller, they want the software that is meant to be controlled with it to be stable and perfectly usable. Also note that the DAW is really cheap and most probably the most money will come from the optional subscription and the additional plugin sets. I bought the "essentials" package, and the reverb and delay are quite nice and a really good deal for the price i paid. But they already had begun to evaluate the possible microcontroller chips to use with the upcoming controller. This is no big developer team as it seems, and they are highly productive in the moment to get the new mixbus up to speed. Making literally thousands of changes to the code from each interim release to the next. Also they are highly responsive in terms of customer service, which is absolutely not to be taken for granted with DAW companies nowadays.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 13, 2015 23:03:35 GMT -6
Some more information on how Control Surfaces are handled in Mixbus 3:
There are right now 4 possibilities to use control surfaces with Mixbus. These can be enabled in the preferences with or without parameter feedback to the control device. 1. dedicated predefined Presonus Faderport binding 2. Generic MIDI 3. Mackie 4. OSC (Open Sound Control, interesting for those using control surfaces over network that support this protocol e.g. some mobile/tablet apps)
You can enable these methods independently from each other, so you are not restricted to use only one, so it's possible to use the Mackie AND the Generic MIDI option the same time. These both options /Mackie and generic MIDI/ already worked in the 2.5 in Linux, when i tested. To fully enable your controller, it is in most cases done best with the Generic MIDI option. There you can use MIDI Learn, which is as easy as pressing CRTL+middle mouse button and then moving the controller knob/encoder/fader... And you can use predefined binding maps, that are essentially XML text documents, that you can edit with a text editor to create full control presets for an individual controller. Several popular devices are already available in form of binding maps and can be selected in the Control Surfaces settings or you can use your own, predefined ones are from BCF2000 and DDX3216 to e.g. the Korg NanoControls, several M-Audio Keyboards, Roland SI-24 /V-Studio 20 or Yamaha KX25...
AFAIK most of these options are inherited from the Ardour DAW. Therefore i don't know how much the predefined modes and binding maps make use of Mixbus' extended features. But i already saw that the midi learn can be used on every control of the console channels and busses, EQ, gain knobs, mute, solo, arm for recording, bus assignments, sidechain assignments, filters etc. Only thing that i found not be midi learnable right now is the type of dynamics selection knob (leveler/compressor/limiter). Otherwise it seems completely assignable. which is what makes it most interesting, esp. for me, because it opens up everything to be more console-like than every other DAW (soundwise and from workflow and gainstaging it already was before). As said, i will check out these features in depth at a later point.
This is an essential part of the usability of a DAW to me as well, so i understand that people want confirmation if and how it works. OTOH....for $79 it is worth more than it's price for the EQs and filters alone.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 13, 2015 23:28:18 GMT -6
A Tip for the interested ones who did not jump on the Mixbus 3 release yet:
Officially, there is no demo for public download. But, if you register to the forum, you get access to interim releases in the Mixbus forum at Harrison.
Everyone can register there and get this access. (Subject to change after Mixbus 3 to be only available for subscription members)
If running without license, AFAIK although not officially supported the installed mixbus tells you it runs in an unlicensed demo mode with intermittend noise burst or silence, maybe save features probably disabled. S.t. like this. It might be good enough to test things like the status of control surface support for your controllers and general workflow etc prior to purchase.... Ran into this when i forgot to put the license files in the appropriate folder after Mixbus 3 install.
|
|