Ever wanted to see only the drums or vocals in a project?
This tutorial shows how to set up some custom toolbar buttons in the mixer to show only specific groups of tracks.

Using a combination of a custom toolbar, custom actions and the console this is an easy way to really speed up mix workflow.


Posted

in

, , ,

by

Tags:

Comments

15 responses to “Show/Hide tracks in the mixer with custom actions”

  1. Maurice Petit Avatar
    Maurice Petit

    How do you do that in Windows??

    1. Admin Avatar
      Admin

      exactly the same

      1. Smudger83 Avatar
        Smudger83

        Is there a specific folder to save the txt file in Windows?

        1. Admin Avatar
          Admin

          in the resources folder.

  2. prezbass Avatar

    What are the actions to your “Show All” button?

    1. Admin Avatar
      Admin

      SWS: show all tracks in MCP
      Xenakios/SWS: scroll track view to home
      Xenakios/SWS: select first of selected tracks.

      Probably would work fine with just Show all tracks in MCP.

  3. prezbass Avatar

    I figured it out right after I posted that. Merely adding the Show All Tracks in MCP did the trick

    Couple of other items I found interesting and of note:

    • You can chain different selections together by adding a comma between the items:

    example: S*Keys*,*Piano*,*Rhodes*,*B3*

    This could be used to hide different permutations of keyboard tracks if you don’t follow a totally strict naming convention.

    • I also found it handy to add “Show selected tracks in TCP and hide others” because I got confused on what I was looking at with the TCP that much different from MCP. This had an extra added benefit of making SWS Snapshots pretty handy, too, since I could snapshot a smaller set of tracks to edit and configure.

    • If you plan to edit the reaconsole_customcommands.txt file, just make sure that you don’t remove lines in the file. Apparently, the lines are parsed by ReaConsole by the index line, not the command itself. If you do remove lines, your custom actions will get messed up and you’ll just have to re-edit them and add the correct behavior.

    • If you edit the reaconsole_customcommands.txt file and add an action there, you won’t see that new item unless you close and reopen Reaper. ReaConsole only loads that file on start, with no way to reload the file.

    1. Admin Avatar
      Admin

      Awesome, I was actually trying to do that before settling on selecting the child tracks. I wanted to do kick + Snare + drum + toms etc but didn’t know where the comma should go.

      The removing lines comment was something I cut out of the video at the end because I didn’t explain it well. Custom actions use the action ID and the reaconsole commands go in order 1 per line.

  4. Eric Zang Avatar

    Note that creating the console commands in a text file is no longer necessary. The cycle action editor has replaced this and is more convenient to work with.

  5. Curtis Avatar
    Curtis

    Q: How do you get your custom toolbar to display nice and neatly to the left of all the faders in the MCP?

  6. Fernando “Tachi” Franco Avatar

    I don’t have that file “reaconsole_customcommands” in my resources folder. I tried inserting one and it didn’t seem to work. I do have the latest version of the SWS extensions. Could it be because I have my reaper install in Applications/Reaper/Reaper instead of Applications/Reaper ?

    1. Admin Avatar
      Admin

      have you done a portable install or standard?
      If not portable then it should be in Mac HD/Users/Your User Name/Application Support/REAPER
      and the file should be “reaconsole_customcommands.txt”

Leave a Reply

Your email address will not be published. Required fields are marked *