Used up until 7….want to try again but I’d really like to see integration with maschine mk3 or push 2 both in terms of midi control over the mixbus software. If there is something that is out there on this I’d like to know. Meantime the simplicity of having everything like a desk is v refreshing
@@HarrisonAudio interesting, since i know to use push 2 in different daw's you have to have 3rd party software (shove). any chance of a tutorial with mixbus n' push 2?
I was wondering why my Komplete Kontrol A49 midi keyboard wasn't working in regards to the (transport) functions, ie start & stop the timeline. However the (sounds) do work across the key bed when I press the keys Was hoping as well I could make a more full transition integration wise with HMB10 & Maschine MK3 myself. It would behoove HMB devs to integrate N.I peripherals . Some kind of way to add a "mapping" directive so upon loading recognition everything is professionally, & cleaning connected to use more of the power in the KKA49 midi keyboard at least to be able to start & stop the software\engine without needing the mouse
Can you please do a video on how to map plugin parameters to a MIDI controller? I understand that we can't use the plugin GUI to do MIDI Learn but I'd like to see what the official "easiest" process is to get the Waves SSL EV2 mapped to a MIDI Fighter Twister in Mixbus 10.
After playing with it for a day, the plugin mappings don't stick to my MIDI controller when the plugin is removed and reloaded onto a new track. I even tried saving the preset after mapping and it still does not remember the mapping. I can't use Mixbus unless it can remember my mappings - and we can't use session templates as the work-around because we need to load a new insert on every future track that will be created (not a pre-created track from a template). To remedy this, do like the other DAWs do and make it create an XML file each time a plugin mapping is created. Then the plugin parameter mapping settings stick inside the XML file and this isn't an issue anymore.
Thanks Nathan. I always learn from your videos...
Glad to know someone is watching :)
-Nathan
Excellent
Thanks, let me know what other tips you would like to see.
-Nathan
Sounds really good
Thanks
thx Nathan. great vid. if you look about an other subject to teach. maybe rthyme ferret would be great to understand how it works. thx.
Great suggestion!
Used up until 7….want to try again but I’d really like to see integration with maschine mk3 or push 2 both in terms of midi control over the mixbus software. If there is something that is out there on this I’d like to know. Meantime the simplicity of having everything like a desk is v refreshing
the Push 2 works well with MIxbus and functions the same as it does with Abelton Live.
@@HarrisonAudio interesting, since i know to use push 2 in different daw's you have to have 3rd party software (shove). any chance of a tutorial with mixbus n' push 2?
I was wondering why my Komplete Kontrol A49 midi keyboard wasn't working in regards to the (transport) functions, ie start & stop the timeline. However the (sounds) do work across the key bed when I press the keys
Was hoping as well I could make a more full transition integration wise with HMB10 & Maschine MK3 myself. It would behoove HMB devs to integrate N.I peripherals . Some kind of way to add a "mapping" directive so upon loading recognition everything is professionally, & cleaning connected to use more of the power in the KKA49 midi keyboard at least to be able to start & stop the software\engine without needing the mouse
Can you please do a video on how to map plugin parameters to a MIDI controller? I understand that we can't use the plugin GUI to do MIDI Learn but I'd like to see what the official "easiest" process is to get the Waves SSL EV2 mapped to a MIDI Fighter Twister in Mixbus 10.
If I can get my Avid S1s working and my MIDI Fighter Twister working in Mixbus, I'd switch to Mixbus
After playing with it for a day, the plugin mappings don't stick to my MIDI controller when the plugin is removed and reloaded onto a new track. I even tried saving the preset after mapping and it still does not remember the mapping. I can't use Mixbus unless it can remember my mappings - and we can't use session templates as the work-around because we need to load a new insert on every future track that will be created (not a pre-created track from a template).
To remedy this, do like the other DAWs do and make it create an XML file each time a plugin mapping is created. Then the plugin parameter mapping settings stick inside the XML file and this isn't an issue anymore.
AVID S1 is HUI protocol so its not going to have a direct mapping. MIDI learn only applies to the element or plugin being learned and nothing else.
does ssl2+ includes mixbus10?
Possibly