I’m attempting to use ReaRoute to route audio from GP to Reaper. How do you get your guitar audio input to work in GP though? If I select ReaRoute as my asio audio device I no longer have my guitar input from my ASIO audio interface (Axe I/O)
Sorry to resurrect this old thread. I found the answer to my question for anyone else that stumbles across this. To record your guitar output from GP to Reaper using ReaRoute, you need to set your ASIO driver to be ReaRoute in GP. In Reaper you set your ASIO driver to your audio interface. Then on 1 track you disable master send and send it directly to output ReaRoute 1. Then create another track in Reaper. Set the input to be ReaRoute 1/2.
This document goes into much better detail: Record Jamulus With Reaper - Google Docs
Very nice! I’m super excited for this. I’m running a trial of GP right now, and this was the one thing holding me back from considering it as a solution. I’m used to doing all my guitar work in a DAW (Reaper), this includes practicing, writing, recording, and even playing live. I was going to ask if GP would ever be released as a VST, but this solution should be just as good.
I need to be able to record my dry tone and tweak the sound after recording as well. I find working in a DAW to be most natural for me. But the reason I need something like GP is it is the only solution that allows me to create snapshots of my plugin settings and quickly switch between them with no latency. Reaper can do this, but it involves a lot of work to manually create the commands using ReaLearn. I was doing this but its a major pain and productivity killer. Reaper (and ReaLearn) also has snapshot capability but there is quite a bit of latency switching between snapshots, so its not a great solution for live use.
Hello @highway11 welcome here
I used to use Reaper like you but since I’ve been using GP my approach has been reversed: I start by working in GP because the workflow is much more responsive for creating and developing ideas and inspiration isn’t diluted by technical manipulations.
All the creative work I do to play live is done in GP, then I transfer my FX and VSTi to Reaper to record, mix and broadcast.
This way, I can still modify the sounds, instruments or effects if necessary.
The broadcast result will therefore be a similar replica of the live performance and vice versa.
It’s a much more efficient and enjoyable way of creating and working.
Interesting. So after working in GP to craft your tones, you manually recreate the signal chain in Reaper? I would prefer not having to manually recreate the signal chain, so I think my plan would be to use GP routed into Reaper. I prefer working on song ideas by quickly recording and playing along with drum loops and creating other parts, so I can’t see working without a DAW for very long periods of time at all.
Why? There have always been ways to route audio between GP and other DAWs, we even have some blog articles on ways to do this. With GP Relayer, we’re just going to make it even easier
The entire philosophy around Gig Performer is that it is part of your “sound”, not part of your recording process. We believe that the design of your sounds and your live performance should be completely different from the recording process.
The traditional analogy is the guitarist who shows up at the recording studio with his/her amp and collection of effects pedals. The recording engineer will stick a mic or two in front of that amp and/or perhaps DI it and then record what is being played.
The engineer might tweak the results a bit (compression, EQ, etc) to fit with the overall song being recorded but the sound itself is that of the player.
That guitarist can then go on stage and perform with exactly the same gear. In a live situation, FOH might similarly apply a bit of compression or EQ to fit with the band and the room but again the sound belongs to the player.
Gig Performer should be thought of in the same way.
It wasn’t until yesterday I found ReaRoute solved my issue. I had tried some other methods in the past from your blog that l struggled to get working as they added latency or had stability issues (ASIO4ALL). GP Relayer looks to be even better/easier for this purpose though, so that’s very cool to see
Your analogy makes perfect sense to treat GP like you would amp and pedals. However, I’ve been working in a DAW almost as long as I’ve been playing guitar. Being able to record multiple tracks of my guitar as I’m designing my sounds and adding other instruments is just part of my workflow. I then want to use these sounds live without reprogramming them. I think running GP into my DAW could give me the best solution towards that end. When playing live I would no longer need the DAW.
At home, whether I’m learning a song to perform, or coming up with original song ideas, I’m constantly looping sections of songs, recording multiple tracks, adding other instruments. All of which require a DAW.
Of course when creating in GP, I record as I go along my ideas (guitar, vsti, loops,…) through GP to Reaper but only as a reminder (using a loopback function in my audio interface which replaces Rearoute).
When I get to the point of definitively fixing the project, I work only in Reaper to record and finalise the project.
Is there an ETA when GP Relayer will become available?
If you want to have the more recent information about it, it is here