then there's performance, you can take your preset banks and modulate and morph them against one another. This way I can click off cool sounds, and be able to recall them exactly from the moments they occurred. with PPTC you toggle a button, and the entire device chain is saved parametrically into a preset bank (each bank can have 16 presets). When I'm noodling on synths, I often get into a groove where I'm getting a string of good sounds, rather than recording the whole string. PPTC (Performance and Production Tool Chain) is a killer preset management tool, and enables going totally meta-modular w/ Live. Lastly, for me, is the PPTC script by Hollyhook, a dev team that joined Isotonik just a few months ago. I can remap the order of the device parameters, add new devices, put spaces between mapped parameters, create new banks, reorder banks, copy to new banks etc etc. XXL Script + PrEditor does the trick - and I learned along the way how to extend the Community Mapping of Live to 128 parameters w/ the options.txt file - with the 2 scrips in place, I get the first 128 parameters of a live device (or multiple devices) auto-mapped to 6 banks of 24 on the LCXL. make any change, same deal - this is default Live behavior for preset management. not create 1500 maps for Synthmaster's presets, then when I change them, have to save a preset anew, with a new name.add a device, change a macro. I also wanted to be able to modify default mappings, and have dynamic presets (i.e. same "blue-hand" control as a native control surface, but with 24 parameters, instead of 8. I wanted to be able to use all 24 knobs on device parameters, and I wanted them auto-mapped i.e. The other two rows of knobs are mapped to track sends, sliders to volume. For me though, only having access to the 1st 8 parameters of an Live device, doesn't work for me. It's a native control surface for Live, and if your a fan of that workflow, it's solid. One thing I'll mention, I would have been unhappy if I hadn't gone in for it knowing about the xxl script from Isotonik. I mentioned my most common workflow above. So what all do you like/dislike about this combo? I imagine they work well with Ableton too. I have the XL sitting next to a Launchpad Pro, and it is a killer combo!Īha! you have my dream setup! So does the launchpad app allow you to use the Launchcontrol XL to control fx/filter/volume and the Launchpad Pro to trigger the pads at the same time? I have the Launchpad Pro now, and would like to pick up the Launchcontrol XL if they work well together. Launchpad, LaunchControl XL and Launchpad app all running together, you are very BAD people for making all this stuff. I lost 5 hours of my life last night thanks to you guys, Circuit. When using the LaunchControl XL with Launchpad app, would it be possible to map the unused rotaries to any of the performance effect parameters ? Is it possible when using LaunchControl and Launchpad app to have the app ignore the LaunchControl XL if I want to use the LaunchControl XL with something else, circuit for instance ? Same question for Launchpad as well ? Is this only the case if powering the unit directly from ipad ? If I am using powered hub for instance, should I leave it in Normal power mode (which I did and it works) ? If I put it in low power mode would I then need to switch back to full power mode if connecting back to powered hub or PC ? In the getting started guide it says that if using the LaunchControl with an iPad you need to put it into low power mode. I would like to disable this behaviour, and only select XL Templates manually.Īnyone else seen this? Or can confirm this behaviour? I'm going to get in touch with Novation on Monday, but I thought I'd ask here too.Received my LaunchControl XL yesterday and have a couple of questions about its use, thought I'd ask the questions here cause I'm sure others will have the same questions. Only CC#1 (mod wheel) sent on the six above MIDI channels causes the XL to scroll through it’s Templates. I have the Snoize MIDI Monitor app active, and I can see that when CC#1 (mod wheel) on one of the above MIDI channels comes in, the XL responds with a burst of sysex data, and the XL Templates change. This is undesirable behaviour! How can I make it stop? Here’s my problem: Whenever I send CC#1 (mod wheel) from the Remote on MIDI channels 5, 8, 9, 12, 14, or 16 to control something in Live, the XL scrolls through it’s Templates - first the 8 User Templates, then the 8 Factory Templates. I have a ReMote25 SLMk2 connected to Live as well, to control various instruments/tracks etc. In Live’s MIDI preferences, MIDI Input is activated for Track and Remote for the XL, and in MIDI Output, Remote is activated for the XL, so that the XL can receive feedback from Live and update it’s button LED statuses etc. I am using it it in manual MIDI mapping mode (not Control Surface mapping). I have a problem with my Launch Control XL (which I’ll abbreviate to XL)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |