An R1 project in, remote views out: overview, delays, EQ, faders, strips and floorplans. Early preview
Open a d&b R1 project, say which groups are the sections, and the R1 Layout Builder builds remote views from them: a Master overview, time alignment, EQ and tuning, faders with linked Left/Right pairs, a page of strips per group and a floorplan with the controls over a picture of the room. They go into a copy of the project for R1 to open.
It runs in the browser and the project is never uploaded. A .dbpr is a SQLite database, so the page reads the groups and amp channels straight out of it and writes the new views with field values copied from what R1 3.46.1 writes itself. It's the browser twin of the r1-views scripts. R1 hasn't opened a file made by this page yet, so open the copy in R1 (Configuration mode, offline) and look at every view before it goes anywhere near a show. Not made, checked or endorsed by d&b audiotechnik.
01
Master has the whole system at a glance, a Master card and a row per section. Timing gives each channel a row with its delay and the generator. EQ and tuning puts a system EQ on Master, one on each section, and each channel's level, CUT, CPL and EQ switches under it. Then Faders, Strips and Floorplan. Build any of them, under names of your own.
02
R1 can't tie two fader controls together, so each Left/Right pair becomes a group of its own, in a folder beside Master rather than inside it, where a channel listed twice would be moved twice. The pair's fader drives that group, so both sides follow it like a console's stereo link. The Master fader (and a fader per section, if you want them) is relative, so it keeps the balance.
03
The strip designer builds a channel or group strip out of R1's own controls: meters, mutes, lamps, delay, the generator, faders, CUT, CPL and EQ. The Strips page then lays it out once per channel in each section, in Left and Right columns or in as many columns as you like.
04
Upload a picture of the floorplan and drop strips onto it where the speakers actually are, a card per channel and a tile per group. The picture becomes the background of the page in R1.
05
Before it offers the download, the page compares the copy with the original. Nothing outside the new views may change, every control has to point at a real channel or group, and every control has to be one R1 offers for that property. It's the same check as the scripts' check.py, and the tests run both on every page.
The Python scripts it was ported from have been: R1 3.46.1 opened a file with their Taps and linked Faders views (a D20 and D6 rig) and saved it back with every control and group intact. This page writes what the scripts write for those two pages, and the tests compare the two row for row, but no file made here has been opened in R1 yet. Nobody has pressed anything on any of these pages with amps attached.
D6 and D12 channels stop at 340 ms and other amps at 10 seconds, and a group's relative delay spans the smallest limit under it. That comes from reading projects AutoCreate made, not from anything d&b has published.
Only projects from R1 3.46.1 have been tried. It adds views and never edits or removes the ones already there, so rebuilding a page means deleting the old one in R1 first or giving the new one another name.
There's no container for R1 Layout Builder (preview), so the hosted copy is the one to use.
