![]() It's labelled for use with GR5, but will work with any sim that uses the standard TOGGLING CC#127(>63)=ON, CC#000(<64)=OFF. I don't really NEED the TEMPLATES setlist, so I backed it up and created a "general purpose amp sim controller setlist". OK, so I've been meaning to do it for a while. Presently it takes up a lot of floor space, what with the Helix and the FCB, but if I DID decide to dedicate a Helix setlist, I COULD run the whole thing from the Helix (and a Korg nanoKontrol for rotaries/sliders/extraneous buttons)." I like to think of it as "The World's Biggest Amp Simulator". " I have a Cantabile rack that contains all of the aforementioned sims AND Helix AND synths AND EZDrummer. WHY would I want to do any of that? Because I CAN! Also, it's the kind of programming puzzle an ex-IT guy like me enjoys. Presently it takes up a lot of floor space, what with the Helix and the FCB, but if I DID decide to dedicate a Helix setlist, I COULD run the whole thing from the Helix (and a Korg nanoKontrol for rotaries/sliders/extraneous buttons). I have a Cantabile rack that contains all of the aforementioned sims AND Helix AND synths AND EZDrummer. It's not worth it to me to dedicate a setlist to sims, even if one were enough to cover all of the minor differences between them, but I still have the FCB and when I feel the need, I can load up whatever configuration I need and I'm ready to go! In fact, using Cantabile, I've set up MIDI filters that allow me to use one FCB configuration for all of the sims. Today I mostly use Helix, but I had/have favorite presets in all of those sims. I currently have both latest versions as well as BIAS AMP and FX, S-Gear, and TH3. Had Amplitube whatever version was out around the same time. GR was one of the first MIDI controllable amp sims, LONG before hardware sims. Matching it up to GR5 presets is still a PITA, but a little less so. I messed around with it a bit more and found a simpler way to do the BASIC Helix configuration. *The Unnecessary step that I removed - (You need to assign a low DSP Helix effect to each of ten blocks (that can be saved and copied to all of the presets in that setlist). Should you choose to go down this particular rabbit hole, I'll be happy to answer any other questions that you WILL have! I've probably forgotten something, but as you can see, using the Helix to control an amp sim is, at best a PITA! If one TAG is sufficient, you can do that in each Helix preset OR just remember to switch to your MY PRESETS TAG when you open GR5. If you're planning to use more than one TAG in GR5 (requiring more than one setlist in Helix), you'll need to set the INSTANT COMMAND that calls the GR5 preset to also send MSB=OFF LSB=GR5 TAG #. In GR5, you need to set up a new TAG (MY PRESETS?). This is another thing that needs to be done individually if you use the second method (all GR5 effects available). Each footswitch needs to be assigned a TOGGLING CC# and the scribble strips customized with the name of the GR5 effect that it is assigned to. BTW - this is only a problem in GR5. Amplitube, S-Gear and TH3 work fine with the default behavior, which simplifies this considerably.Įach of the ten (or 8) footswitches in each Helix preset has to be saved ON or OFF to match the SPECIFIC GR5 preset to which it corresponds (so that it reflects the status of the effects and will be ready to TOGGLE the effects ON/OFF as required). Then you assign a PC# INSTANT COMMAND to each preset in the setlist (Helix preset#01A=PC#000=GR5 Preset #001), since PC SEND must be set to OFF in GLOBALS/MIDI to prevent Helix from sending the assigned TOGGLING CCs by default, which can produce unpredictable results in GR5. The advantage of the first method is that you can create ONE Helix preset with most of the required settings, customize the scribble strips with the ten effect names, then copy it to all of the presets in that setlist. Therefore, either you:ġ) decide on a maximum of ten GR5 effects to use in ALL of your presets, and assign them CC#s GLOBALLY (LOCKED) in GR5 orĢ) in each GR5 preset you individually LEARN the CC# for whatever effects you want to use in that preset. ![]() You have ten buttons on the Helix to which you can assign a TOGGLING CC#. Therefore, each Helix preset has to be totally custom created to match a SPECIFIC GR5 preset. GR5 responds unpredictably (if at all) to CC#s sent with Program Changes (PC#s), which the Helix does by default (for any footswitch assigned a TOGGLING CC#) when PC SEND is ON in GLOBALS. Each Helix preset has to be custom configured to match the ON/OFF status of the specific effects in a corresponding GR5 preset.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |