- GUITAR RIG PRESETS COLLECTION PRO
- GUITAR RIG PRESETS COLLECTION PLUS
- GUITAR RIG PRESETS COLLECTION WINDOWS
I'm also sorry for such a simple question. I appreciate your help if you got any ideas how can i do this, adding more presets in reaper's fx window, that is. I got a friend to do this for me over TeamViewer, But after that there wasn't any new presets in the preset list of reaper FX window. I did some research, and it seems that you have to copy the presets files into your harddrive, then in guitar rig's interface, press option, then scan, to load up those presets.
GUITAR RIG PRESETS COLLECTION PLUS
(there is a plus "+" sign to the right of that combo box, and a button called "Param")
In reaper's FX window, (when VST is added), there is a combo box which lists some presets, which i can easily use them.
GUITAR RIG PRESETS COLLECTION WINDOWS
I'm launching guitar rig 5 within reaper, by finding and loading up the vst in the fx window.įrom there, i believe two windows open, one is the fx window of reaper, and the other is the guitar rig's interface which i can't work with it at all do to it's inaccessibility.
Well first of all, i'm Using a ScreenReader and navigate with a keyboard, because i'm visually impaired. Maybe your import solution will work, it's worth a try before I scrub the whole thing and start over.I'm trying to load some more presets to native instruments guitar rig 5, (in reaper) but it doesn't work for some reason. I'll post back with progress, and thanks for helping. I love Guitar Rig's basic concept, sounds and interface, it just sucks if I make a preset in the standalone version and can't use it on a track 'cuz the VST side can't read it. I want to play guitar, with all the cool amps and toys, not program my computer : ). At this point, spending too much time trying to fix this is more of a mental exercise than a practical measure. If that doesn't work, I am going to uninstall/reinstall the whole thing. Then I will try deleting a line in the registry and make it go look again ,as per the directions they describe. That is kind of a pain to manage them that way, but it beats creating them twice. I am going to first try importing all the files from the standalone's directory into he VST, per your link. I found a regedit solution in their knowledge base. If they were missing from one of the directories, I could say," AHAA! I know what's going on", but that isn't the case, which is what confounds me. The user presets are THERE in both directories, the user presets just don't work in the VST side unless I make them there. But, like I said, the user preset names are THERE, in the VST version. The VST seems to take it's presets from a folder in My Documents.(no idea why, unless I did something stupid, I never would have looked there) The standalone seems to draw from a programs / common files location. I just upgraded it from the version that came with my KOMPLETE6 Audio Interface (which is great btw).
anyone run into something like this? I already have logged a ticket with NI support, but they are half a world away, so the wheels of progress turn slowly across time zones. They show up in the VST interface, they just don't do anything. I'm tempted to just reinstall the whole thing from scratch, but am I gonna lose everything then? I know this is probably more of an NI question than a Sonar one, but you guys always seem to have experience with the same issues I encounter and always have a solution. The standalone works fine. The presets that were saved before I upgraded work, the factory presets AND the presets I make within the VST environment work, so huh? Either this is a shared directory or a unique one to the VST and standalone, not kinda both! and like I said, they appear to be there I found the preset files and everything. I mean I see them there, the interface looks the same, I click on them and nothing happens. It loads into Sonar, has all of my user presets that are in the standalone version, but they don't load up.
GUITAR RIG PRESETS COLLECTION PRO
Guitar Rig 5 Pro can't see some of my presets in VST Serious Wierdness
0 kommentar(er)
