I found Reaper made almost no difference to the CPU load whether it was loaded and recording or not.
ok, key points as follows
MOTU
- All audio channels (around 10) physically come into my Motu Ultralite mk4 which is also the live mixer for the band.
- Channels are routed direct into the Motu mixer software (so that if the PC dies, the mixer carries on working)
- Channels are also routed (pre fader, pre everything) to audio channels on the PC for simultaneous consumption by C3, Reaper etc. No need for virtual audio cables. Not sure if your Motu is the same.
Cantabile
- Binding to send Song program number and bank to Reaper.
- Bindings to send midi messages on song load and unload (these are used to start and stop recording). These messages go via a different route that I can enable and disable. This allows me to prevent Reaper auto recording on every song change if Iâm not at rehearsal.
- Bindings to buttons on my control surface to send to Reaper and enable and disable Record Arm.
Reaper
- The Reaper project has all the individual channels mapped and ready to record at any time.
- All the songs are set up as regions which are 4 minutes long with 5 minute spacing. Doesnât matter what order they are in, and it doesnât have to match Cantabile or the set list on the day.
- All regions are numbered - doesnât matter what number.
- Then I use the âSWS Go to Region numberâ actions and learn the song changes from C3 to the correct region.
In Use
Whenever I change to a different song in C3, Reaper stops recording, moves the cursor to the start of the correct song, and then starts recording again. It doesnât matter which order the songs are in, either in Reaper or C3. It doesnât matter if the song overruns or we play it twice. These are just recorded on the timeline, or as 2nd takes.
I did experiment with sending the C3 auto record binding to Reaper to start and stop the recoding, but found that I was sometimes missing the start of songs.
The nice thing is that once the songs are in Regions then Reaper can then render each region as an mp3 stereo mixdown, and wav stems all from one screen.
I use the same recordings to play along to as practice in between rehearsals with my keys track muted. With Record Arm disabled, then reaper simply plays the tracks back on song change. Really easy.
I will say Iâve only just set it up like this - first recording rehearsal will be on Sunday. Before, I recorded all songs in one long session in Reaper. I then used to have to take the 30 to 60 minutes after rehearsal to move all the regions around into their correct places. This way I have a rough recording ready to play back or export straight away, which is often good enough for our purposes.
Playback - MOTU Ultralite MK4 specific
I mentioned that I can play back from Reaper instantly through the SAME mixer channels we just recorded from. I like this because we can go to FOH and check levels and mixer fx from the audience perspective.
To do this means rerouting the specific instrument mixer channels on the MOTU so that the audio comes from the PC audio channel, and not from the physical input jack.
I have 2 batch files assiged to a button that do this rerouting for me using the MOTU API, so that to play back a song we just recorded takes about 5 seconds.
The batch files contain commands like this. Each line changes a mixer channel routing.
curl --data âjson={"value":"0:0"}â localhost:1280/0001f2fffe006030/datastore/ext/obank/6/ch/0/src
curl --data âjson={"value":"2:2"}â localhost:1280/0001f2fffe006030/datastore/ext/obank/6/ch/1/src