Web interface to a ridiculous extreme!

I couldn't stop myself!! After learning from forum member Flavio in these two threads I ended up with this. Thanks Flavio. This is on an old iPad 1. Download: To install see Reaper User Guide 5.30 section 18.37, then unzip the downloaded files into the "\Plugins\reaper_www_root" folder. Then run reapad.html on your tablet's browser. I'm providing an idea, not a finished product. The choices of button functions are up to you. Brief details follow on how to use and modify. Not only do I use this to remotely control Reaper while recording in another room, I also use it when sitting at my computer as a touch pad at my left hand, providing handy access to many of Reaper's functions. It even works for me as a simple control surface by means of the Up/0 dB/Dn and L/C/R buttons etc., as well as the controls in the "track inspect" window.

The <style> (CSS) section 

The <style> (CSS) section I've added some comments to this section, but a brief discussion here is probably in order. This section contains class and ID definitions such as .ctrlbut which defines some parameters for most of the buttons you see. You can experiment with these. In the case of .ctrlbut the width of 7% (or 8%) works well when using 12 buttons across the screen. See the html section for usage. Button colours are provided via the definitions starting with .aqu2. See usage in the html section. (I have a male perception of colours, so don't expect too many fancy names!). The red lines you see separating the "groups" are provided via .emptyred. There are other colours provided here, but in the end I didn't use them. There's probably no need to describe the rest of this section here.

The <script> section 

The <script> section A few functions call for comment:- wwr_req() (search for it) – This handles calls to Reaper "actions" (see the Action list with "Show action IDs" turned on). See the html section for usage. mouseDownEventHandler() – determines what happens if a button is tapped in the track panel. This calls wwr_req(). mouseDownEventHandlerSlct() – a modified version of the above, making the Select buttons provide an "exclusive" select as I feel it's safer that way. If this is not your preference, just comment out the lines that make it different from the original function. show_div() – hides or shows groups. These will be buttons/controls contained within <div></div> in the html section. See that section for usage. This function is used by the wide buttons described in post #2. /* The following functions are like custom actions */ The functions following this comment provide another way of doing the same thing as custom actions you may have created in Reaper. e.g. Code:

The html section 

The html section This is mostly tables with rows of cells, where each cell is a button on screen. Examples of cells:- Code:

Toolbar buttons 

Apart from the obvious, e.g. Arm, Mute, Solo etc. the web interface doesn't provide feedback for all parameters. Therefore the Mono/Stereo, M/S buttons remain the same colour when toggled. So I made a set of double height/double width toolbar buttons for Reaper's main toolbar. These are all functional but the mono/stereo button also provides an obvious indication of its state. These are also provided for anyone who can live with my choice here :). Download:

Links revised. Should be working now.