Jump to content

timmy_timmyc

Member
  • Posts

    5
  • Joined

  • Last visited

timmy_timmyc's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Well, that sounds very good to me If you get the chance to scroll through your old files one of these days, I'd be very curious to see how you pulled that one off!
  2. Hi again folks! I've been using that setup for a while now, and it's been working fine. However, there's a few improvements I'd like to make. I've tried different things, but didn't manage to make it work the way I'd like to. I'm not sure it's doable, but maybe someone here would know. So, here's how my concert is organised so far: I have set up one set per song, within which there are various patches. In each set, I navigate between patches with the 5 coloured buttons at the bottom, using Program Changes. These Program Changes are assigned at set level for every song. This works great, but visual monitoring would be much easier if the selected patch lit up the matching button (the controller I use for patch changes is a Launchpad X, which could reflect the currently selected patch button status. If that worked, I wouldn't need to watch the computer screen while changing sections) The buttons don't light up, I guess it is the default Current Program Number action behaviour. One workaround I've found is to use Jump to Patch or Current Patch instead. The buttons are then lit and it's great. However, when I do that, if I reorganize the order of my sets (which I need to do if the setlist changes), the patch numbers change but are not updated inside the buttons. Then my navigation is all messed up. If I can make this work, I also intend to use the two rows of eight buttons in the middle as direct access to every patch, assigned at concert level. But the issue is similar. I guess it all boils down to: is there a way to have an absolute patch addressing system, like Program Change numbers, which would still allow the patch selection button to be lit up as with Current Patch or Current Patch Number? I hope I make sense ^^ Cheers, Tim
  3. Thank you so much!!!! Yes it does help a lot, I managed to get it working and now I get a better idea of the logic of the thing. Many thanks for your time and your very detailed answer, that couldn't have been made clearer!
  4. Hi, thank you for your answer! Yes, it definitely is an option for me to organize the concert with one set per song. My buttons can send whatever I tell them to send, right now they send Program Changes. So far, I have set up my two first Sets as sketched in my previous post: Patches in Set 1 are assigned to Bank1 PC1 to 3, Patches Set 2 are Bank2 PC1 to 4. At the moment, I'm switching from one Set to the next one with CC 110 and 111 on channel 16 (that's the default assignments for the Track-/Track+ buttons on my controller, which Mainstage happily understands straightaway as Set-/+). What I can't figure out is how to handle my Bank changes. I was wondering if I should do something inside the Current Bank Number in the Screen Control Inspector, but I just don't know what.
  5. Hi everyone, I'm totally new to Mainstage (and got started with MIDI only a couple of weeks ago), so I apologise in advance for the noob questions. I read the manual, watched quite a lot of videos, read a bunch of posts here, mucked about with it and I'm starting to get a clearer picture of how to use it. However, there's one thing I still haven't managed to figure out, and I couldn't really find any info on how to handle it. I would think what I'm trying to do is a pretty standard thing, so maybe I'm not searching the right way and just missed it, or maybe the way I envision my workflow is wrong. I'd happily take any suggestions! I need to set up a live keyboard rig for a repertoire containing about 20-30 songs. Within each one of the songs, I'll use several different patches. For instance, in one song a Rhodes patch on verses, a synth patch on choruses. In another song, a B3 and a piano. Stuff like that, varying between songs. I'm currently trying to figure out how to switch between patches within each song easily, from my controller. Using Next Patch/Previous Patch is not an option, as I will sometimes need to jump very quickly between non consecutive patches. I saw I could assign each Patch to a PC message. That sounds good, but for what I'm trying to achieve it it looks like I would need some kind of bank change management as I'd like to restrict the number of buttons dedicated to this kind of operations to the minimum, and keep them always at the same location on the keyboard. A convenient scenario for me would be something like that : * For song #1, I'd like to assign patches #1, #2, and #3 to buttons C18, C19, and C20 on my controller. * For song #2, I'd like to assign patches #4, #5 and #6 to the same buttons C18, C19 and C20. And let's say #7 to C21 for good measure. And recycle an existing patch using an alias, too. * and so on So, I thought I might be able to use Sets in my Concert as some kind of banks, and then to assign my controller buttons to PC messages assigned to each Patch within these banks. But from what I understand, I'm not sure if I can really do that, or how. Or if it is the right solution. Something like that, for instance: * Set 01 (Bank 01 ?) * Patch 01 - Button C18 * Patch 02 - Button C19 * Patch 03 - Button C20 * Set 02 (Bank 02 ?) * Patch 04 - Button C18 * Patch 05 - Button C19 * Patch 06 (patch 01 alias) - Button C20 * Patch 07 - Button C21 So, I guess nothing new or unusual here. But I don't understand how to achieve that (if it's doable straight from Mainstage). Would anyone be able to point me in the right direction? Cheers from France, Tim
×
×
  • Create New...