Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Q&A, Tips, Tricks and Howto

Reply
 
Thread Tools Display Modes
Old 11-19-2018, 05:16 AM   #1
tonybeepbeep
Human being with feelings
 
Join Date: Mar 2018
Location: Norway
Posts: 239
Default A question about routing midi and good workflow

Hi all

As a confirmed drum VSTi masochist, I often like to experiment with routing drums like BFD3 out into Reaper using individual tracks.

My question is this:

When setting up receives as mono or stereo from the VSTi is there a way to show if I've used a channel already or not? Factor in visits from my five year old son and other disruptions and I often route something to the wrong track.

Obviously pen and paper is a therapeutic way of keeping track of sends and receives but is there a better, more automatic way?
tonybeepbeep is offline   Reply With Quote
Old 11-20-2018, 05:20 AM   #2
tonybeepbeep
Human being with feelings
 
Join Date: Mar 2018
Location: Norway
Posts: 239
Default



The suspense is killing me
tonybeepbeep is offline   Reply With Quote
Old 11-20-2018, 05:34 AM   #3
DarkStar
Human being with feelings
 
DarkStar's Avatar
 
Join Date: May 2006
Location: Surrey, UK
Posts: 19,681
Default

Hover over the Routing button?

__________________
DarkStar ... interesting, if true. . . . Inspired by ...
DarkStar is offline   Reply With Quote
Old 11-20-2018, 07:28 AM   #4
tonybeepbeep
Human being with feelings
 
Join Date: Mar 2018
Location: Norway
Posts: 239
Default

Quote:
Originally Posted by DarkStar View Post
Hover over the Routing button?

That's a great tip

I need to write that one down before my short term memory evaporates again
tonybeepbeep is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 05:17 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.