A preset recalls a previously saved Rack including its Components, all individual parameter settings, and the options set in the Toolbar. In addition to the presets included in GUITAR RIG's extensive library, you can save, load, and import User presets. Furthermore Component presets enable you to save settings of individual Components. The following sections explain the basic workflows involved in using presets.
Guitar Rig 5 Preset Bank
Previous preset / Next preset: Switches between presets in the Browser's Results list. Clicking on the upwards arrow loads the previous preset. Clicking on the downwards arrow loads the next preset.
Preset name: Displays the name of the User preset. When placing the mouse over the name, a pen icon appears next to it that you can click to change the name. Alternatively, you can double-click the name to change it.
Filter tags: Displays all available Filter tags. You can assign Filter tags to your User preset by selecting them. Furthermore, you can add and assign your own User Filter tags. For more information, refer to Managing User Filter Tags.
Component presets contain all settings of a Component, enabling you to save and recall the state of a Component independently of the Rack. You can load Component presets from the GUITAR RIG library to quickly try new settings, or save your personal settings for later use. You can access Component presets in the Browser or in the Component itself.
You can also replace one or multiple Components by loading a Component preset in the same way Components can be replaced with a Component. For more information, refer to Replacing Components in the Rack.
Previous preset / Next preset: Switches between Component presets of the respective Component. Clicking on the leftward arrow loads the previous preset. Clicking on the rightward arrow loads the next preset.
Drop-down menu: Provides the Save As option to save a new User Component preset, and shows a list of all available Component presets. Clicking on an entry in the list loads the corresponding Component preset.
I had a look at your presets and found an issue. There is a requirement in Guitar Rig 6 that the filename of a preset has to match the preset name that is stored inside the file, if it should be imported. (Various reasons for that). And that is usually the case for all presets. Unless they have been corrupted, maybe during copying or altered manually.
But I did find a workaround to get your files imported into GR6. I imported them into GR5 via the "File->Import Preset" menu entry (you can also just drag&drop them into the GR5 browser). Then I used the right-click "Export selected preset(s)" to export all of them to my Desktop. Then I imported them into GR6 via the "File->Import..." menu entry from the Desktop. That made them show up in the GR6 browser.
If those presets are already in GR5 on your computer you could try just exporting them, but I'm not sure if that is sufficient. If not, then you have to first remove them from Guitar Rig 5, but make sure to have a backup copy of them somewhere! Users presets for Guitar Rig 5 on Mac are stored in Macintosh HD > Users > *your username* > Documents > Native Instruments > Guitar Rig 5 > Sounds.
sorry that you are having trouble with Guitar Rig 6. I'm not sure what's going wrong, we have not seen this issue during testing. Could you please send us two of the presets that don't import correctly so we can have a look?
A precision regarding my problem : my presets came from GR5 initially. I succeed on importing presets from GR5 to GR6 when I purchased the GR6 upgrade 2 months ago. But I found 3 days ago that 1 preset was missing when I switched from 5 to 6. I reseted the library on GR6 and imported once again all my presets thinking it was a bug, but now all my presets are missing.
Hi, I realized that these presets are pre GR5. I was attempting to import the original files from years ago. I installed GR5 on the PC imported the ones I really use. Shut GR5 down and opened GR6 and did the import! Perfect!!
On top of that, I'm running keyboard, guitar and vocal through Mainstage. All for me, as I switch what I'm doing depending on the song we're performing (and sometimes mid-song). However, this means I may sometimes want to change a guitar patch while keeping my keyboard the same, or vice versa.
So, to my question; is there a way to change AU presets without changing MainStage patch? I mainly need to do this with Guitar Rig 5 from NI, but I'd also quite like to do it with Massive and Reaktor too.
Not quite sure I've worded that very well, so an example:I have a MainStage layout set up, which has my vocal going through clean with maybe some EQ etc. I've also got a guitar running through Guitar Rig 5, and my keyboard into Massive. During a song, I start off on keys playing Fat Bass 1 on my keys in Massive for the intro, switch to a distortion for the verse with my guitar, then Fat Bass 2 for the chorus in Massive. Maybe later I'll want a clean guitar in a bridge or something too, with some string hits thrown in from Massive again.The way MainStage is set out currently, I'd need a patch for each combination, which would leave me with at least 3 "patches" for one song and three instances each of Massive and GR running. I'd much prefer to just send in a control message to change the presets in Massive and Guitar Rig.
I haven't been able to find a way to get it to work with Guitar Rig yet, but for Massive (and presumably Reaktor) I have found a solution. First, create an instance in MainStage, load it with Massive and load the presets you would like to use into Massive's preset bank. Turn it on so that it will respond to patch changes.
An additional benefit is that you can load up a single instance of Massive with as many presets as it can hold and use aliases of that instance for other songs. In this case you would create a new MainStage patch and populate it with an alias of your Massive instance. Set up a separate hardware input (I use logic remote) and rather than setting the number to a CC controller, set it to Any. By entering the same NI mapping parameters as above, it will send the correct PG info to Massive when you select the MainStage patch containing the alias. If you need to select multiple Massive patches from the new MainStage patch, simply assign the CC controllers to select new patch assignments. All that info is freely assignable and saved on a per MainStage patch basis, so your first instance could select the patch (say 0) and use three CC controllers to set patches 1-3. On the next MainStage patch containing the Massive alias, you could set the PG to select patch 4 and those same controllers can be set to select patches 5-7.
Here's the problem. Each Helix preset has to be custom configured to match the ON/OFF status of the specific effects in a corresponding 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. Therefore, each Helix preset has to be totally custom created to match a SPECIFIC GR5 preset.
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. 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. BTW - this is only a problem in GR5. Amplitube, S-Gear and TH3 work fine with the default behavior, which simplifies this considerably.
Each 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). 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. This is another thing that needs to be done individually if you use the second method (all GR5 effects available).
In GR5, you need to set up a new TAG (MY PRESETS?). 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 #. The GR5 Tags are numbered from 0. 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.
I hear ya. But I also get where OP is coming from. In the end, it's all just sounds. GR was one of the first MIDI controllable amp sims, LONG before hardware sims. People actually made albums using GR. Still do, believe it or not. I started with GR2 and an FCB1010/UNO. Had Amplitube whatever version was out around the same time. I currently have both latest versions as well as BIAS AMP and FX, S-Gear, and TH3. I've had others too. Today I mostly use Helix, but I had/have favorite presets in all of those sims. 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. I have a Cantabile rack that contains all of the aforementioned sims AND Helix AND synths AND EZDrummer. I like to think of it as "The World's Biggest Amp Simulator". 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). 2ff7e9595c
Comments