problem saving user presets in modules

Dimitri F.

Hello,

i'm experiencing a problem in Guitar Rig 7 Pro about the behaviour to save user presets in any block : amplifier, IR loader, various effects as Choral and so on.

Usually if you make a change to one or more parameters, small as it may be, for example a main parameter of an amplifier (presence, treble and so on) or the value of the faders in the IR loader module, you expect to be able to both "save as" and "save" that is, overwrite your preset that you have already created previously. Instead I realized that in certain unclear conditions the common "save" option is grayed out, and I can only create a new preset and obviously with a slightly different name. This can create confusion and in real life there is no time to go and delete the previous preset and rename the new one accordingly. Does this problem happen to you too? I recently reported it to support and I hope to find a solution soon or at least this type of behavior is corrected by the developers because for example in non-musical applications, let's say Word or Writer, both options are always available unless it is a new file and then the first time it must be saved with a name, but this is logical. What is not good is that saving to the same file is not available, it would seem to be a random condition but I would not even know how to reproduce the problem on video for assistance, it takes luck or more than one attempt admitted that serves to explain the origin of the problem.

thanks!

Dimitri

Uwe303

Hello,

it happens not on my end, all works as expected. If you load an amplifier it also loads a cabinet so you have two devices with it´s own device presets, maybe that´s the problem. I tried with a delay and the tweedman amp/matched cabinet combo. I saves a preset "test 1" for the amp (tweedman), i always could use just "save" to overwrite that template after moving all knobs, even the normally hidden ones. Only after i loaded another non user preset i had to use "save as" again, and i had to load the preset i want to overwrite again - not ideal for sure, that you can´t overwrite a preset if it´s not loaded.

Dimitri F.

Only after i loaded another non user preset i had to use "save as" again, and i had to load the preset i want to overwrite again - not ideal for sure, that you can´t overwrite a preset if it´s not loaded.

Hi, thanks!

Now I'm starting to understand where the problem lies! I did this experiment: after launching Guitar Rig I selected one of my presets and I changed the value of Brilliant channel of the High White, while my "neck" setting appears to be active ( only apparently? ) BUT "Save" is not available, only Save As.

Based on what you said then, that amp preset is not selected but I think it is still in memory (everything, even those of the other blocks, not just the setting for the amplifier) from the previous use of Guitar Rig (on the desktop PC): usually when I play live with the choir before starting to play I have to select one of my amp presets It depends on what song it is ... ok, but it is not said that I will select for example one for Choral and not even that I do it on the amplifier IF I already see the name of the correct preset, that's the point.

Guitar Rig has this clever feature of keeping the last used chain in memory even if it has not been saved in some way. So when you launch Guitar Rig again the next time you will see the last used chain then you can continue playing with that or select another preset. This feature can be a double-edged sword precisely because it almost certainly works the same way also for the presets of any single amp / effects block etc... and probably this is why you have to remember to select a preset / chain already saved before playing and so that you can overwrite one of your presets as you go along in any module it is necessary. I rarely need to overwrite a Control Room Pro or reverb preset but I often need to overwrite user presets for the amplifier, the Choral, and other effects blocks in another type of preset for both clean and overdriven sounds.

However I will do further experiments to better understand how to manage this behavior correctly.

In particular I also had problems with user presets disappearing on IR loader module that I currently use not for cabinets but a sort of simulator for some acoustic / classical guitars and perhaps even in that case the problem at least in part could depend on the fact that I couldn't save the changes but I don't remember exactly anymore. Surely the result of the strange behavior was a completely empty user preset (there were no more IRs loaded on the 4 channels), so I created another one with a different number (but the same name), same thing: preset became empty. And the next one, same story. Then at that point I closed Guitar Rig and restarted it and the problem disappeared.

Dimitri F.

I rarely need to overwrite a Control Room Pro or reverb preset but I often need to overwrite user presets for the amplifier, the Choral, and other effects blocks in another type of preset for both clean and overdriven sounds.

However I will do further experiments to better understand how to manage this behavior correctly.

and the experiments have unfortunately confirmed what I had hoped not to: and as you said, if I select a preset the user settings of each module are not actually loaded automatically and therefore if I need to make adjustments to both the amplifier preset and the Choral preset or other modules , to be able to overwrite them I must first load them each of them independently.
No, this is not a practical behavior expecially for live use: I would like to suggest the developers to kindly correct it so that when you select a user preset (an effects chain), if they have been saved previously, the user presets of each single module are already actually loaded so that you can make changes and overwrite them in any module. Otherwise I would like to know why this type of behavior was considered correct?

Uwe303

Absolutely - software should not work like this, maybe one way is to use a container and just save everything as a container preset but that would be just a workaround, if I don't forget it I will check gr5 and 6 too and see if it was a change or whatever