![]() ![]() what good is pretty integration when the Pad's (arguably the most important part of the controller)ĭoes nothing? I mean. it's more complicated than just MIDI+regular scripts because theres OSC involved and not just MIDI, it has more potential especially for the screens but. The way the controller talks to the OSC script handler is either baked inside the MK3's firmware or it's handled by some NI driver (probably NIHostIntegrationAgent) So. Return "Maschine MK3"It just calls for another main script in the "_NativeInstruments" folder and tells this second script which controller it is and opens an OSC connection. NIController._init_(self, c_instance, oscEndpoint) OscEndpoint = RemixNet.OSCEndpoint(remoteHost='localhost', remotePort=7579, localHost='', localPort=7580) Of course being a vivid Live user I'm also biased as heckĬode: from _NativeInstruments.NIController import NIController I got mine for a few months now (I've been using a "Max for Live expanded" APC40 before) and it's definitely something else. Still, in the end I don't think you'll get any better experience w.r.t. If you know Python you should be home free. Well, pretty much everything in the session view can be accessed and/or manipulated using Max for Live, so maybe that could be of some help?įortunately the specs for making controller templates are fully in the open so it shouldn't be too hard to study those. For example, I heard someone mention session & arrangement. ![]() Then I'll check the Live Object Model and we'll see where we can take this. If you guys have M4l then maybe you can tell me exactly which controls you're trying to reach. if there are specific problems (for example a specific control cc you can't access) then there's always Max for Live, though that becomes more feasible if you own Suite (it can be bought for Live standard as well I believe). But it is something to keep in mind it's not always the messengers fault Do note that I'm not claiming that this is also the case here, as said I don't know anything about Maschine nor do I know who made the templates which are included with Live. If the template was made by a 3rd party and said developer didn't properly follow the specifications of such a template because some other (undocumented) tricks "also work" then it's not Ableton who is to blame for templates which stop working but the developer(s) who neglected the official specs. earlier in the thread it got noted that if Live gets an update then some scripts / templates stop working and the 'blame' of what was aimed at Ableton. Please note that I don't know much about Maschine but all the more about Ableton Live.įirst a comment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |