8/24/2023 0 Comments Launchkontrol xlObviously that wouldn’t be practical in a live scenario. With FL, once one instance has been loaded the fire seems to lock itself to it, and the only way to change that is to go into the midi settings in the program and disconnect the hardware, then go to the new instance and reconnect. With maschine, there is a button on the software interface that will tell the hardware to connect to that instance, so it’s fixable, but thus why i would like to be able to pop up the plugin interface with single button press. Because the other rackspaces are still loaded in the background, the hardware focus doesn’t switch to the current rackspace when you load it. I thought i would just set up individual rackspaces with tracks built to work with the respective software/hardware and load through them in GP, but it turns out that that the dedicated hardware for each behaves in a slightly odd way. I have endlesss in the global rackspace for looping and mashing of sounds controlled via midi by a novation launch kontrol, but I want to run chunks of the set out of maschine and Flstudio. ![]() Says in the instructions to give full context, so here we go: What I’m trying to do is set up a live electronica rig using a maschine mikro, an flstudio fire and endlesss studio. ![]() Is there a way to assign a control in GP to pop up a plugin’s interface? Is there some way I’m missing to pass midi from the global to the local rackspaces? Clearly that’s clever behaviour that GP is doing in terms of loading efficiency etc, but is there a way to make it not? Is there a way to make GP completely dump a rackspace? Even with the limited rackspace mode set to minimum (3, only loads the one before and the one after the current rackspace) it’s still maintaining the connection to one of the plugins in an unloaded rackspace. I’m trying to rig a bunch of different stuff up for a live electronica project. The fader device either needs to offer 16 immediate channels of control itself, or be a smaller unit capable of being daisy chained in such a way that it presents multiples of itself or combinations of itself coupled to other controllers as a single device at a single MBP USB port.Finally upgraded to GP4. Ideally I need a single control surface, faders not knobs, (I’ll be getting a BCR32 when that comes out for all my knob twiddling needs). But I’m not sure it would be autorecognised by Ableton - a significant plus point for the current single XL - unless it directly connects to my MacBook - experiments attempting to use controllers via powered USB expanders attached to the MBP have been disappointing, and I’m all out of direct USB ports in my current setup. Or I could get another LaunchControl XL to use side by side with the one I already have. The very pricey but reputedly excellent Faderfox MX12 gets me to 12 faders. ![]() I have a LaunchControl XL which gives me the ideal live simultaneous control via usb MIDI of 8 channels of Ableton, and I can of course page through in sets of 8 channels, but as my workflow progresses, I find myself wanting more immediate hands-on of up to 16 channels at once, without having to page through, so I can record a dynamic mix of my stems as they play - a Launchcontrol XXXL would be the dream.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |