Metatags

Note:

This is a Premium Feature

Metatags are special text tags that allow you to define some custom

settings per block.

• Metatags are defined inside the naming editor.

• You can set metatags for multiple blocks at once and

• You can define multiple metatags for one block, separated by a

  semicolon (;).

• Metatags will override default render settings.

Defining a metatag

• Make item selection (one or more blocks)

• Run  LKC - RenderBlocks - Enter metatag.lua

• Enter desired metatag using formula:

metatag=value

• Click OK or press ENTER

Available metatags (case sensitive):

• ch                 - number of channels (predefined config/custom

  number)

• tail                 - tail value (ms)

• ftail                - faded tail (ms)

• loudness         - desired output loudness value (-dB)

• limit         - limiter value (-dB)

<img src=“/docs/images/image14-13c907b9ff8b5204b3f961e6516ad329.png”

class=“img_ev3q” decoding=“async” loading=“lazy” width=“632”

height=“332” />

Channel Metatags

Warning:

Old channel metatags with ! prefix are deprecated but backwards

compatible.

Tip:

REAPER can actually render file with any number of channels (odd or

even) and you can define that inside render settings, or per block

using channel metatags.

| | |

|-----------------------------------------|-----------------------------------|

| Predefined | Custom (any number - odd or even) |

| ch=mono ch=stereo ch=quad ch=5.1 ch=7.1 | ch=1 ch=2 ch=3 ch=4 ch=5 etc. |

• Use channel metatags to override how many channels will be in the

  output file

• Make sure to fulfill these prerequisites for multichannel files:

• Tracks needs to be multichannel

• Folders needs to be multichannel

• Master track needs to be multichannel

Note:

Render settings will be handled automatically

<img src=“/docs/images/image28-56d3e49f78ab034b0cd144abc4530256.png”

class=“img_ev3q” decoding=“async” loading=“lazy” width=“632”

height=“332” /><img src=“/docs/images/image20-dc012564e63120fc7d511567b810dd12.png”

class=“img_ev3q” decoding=“async” loading=“lazy” width=“1879”

height=“822” />

---

Tail Metatags

Render Blocks will consider render settings window value <img

src=“data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAIkAAAAmCAYAAADwbrjyAAAB70lEQVR4nO3Z0W2DMBSFYe8U2fPcBbyFZYZgBD8xBS+RF3CG8AanD4GUVC0ulABOD9IvUSdSSPRxoYnKOYOxudTRB8DOH5GwYkTCihEJK0YkrBiRsGJEwooRCStGJKzYv0JyvV6rjUh2RFLjRiQHIDn6OJZUNZLL5bK4oz9wIjkAyZKtOiQpIaUN1olkPZIgCkp9k4T5144NjGkQt0KSOrS2RT9Z61sHax2ctXBtv3qdSDabJAGiBKH0miOOzZAkdM7CWgs7RZI6ONchPZ7j0KUV60RyAJKvWP6MZKx/niR9C/s0JSzafsU6kbwYSRCYxyXIQEL+YZIsA/YbJKlzcF16PD7+vXSdSF6NZNpXHC+eJLUh0VogoqGUgvYBXjSU0pAQkXNG9Ho42TTExzdCEhuIMZ83s0TyMxKl4WNGjv55X3vE6WcbPfSSy/q5kQSIMmiGM2HvSVLbPckdwxTGdD/CawWlNcQHxLjuGE6KRNAMbyg2suskqe2/m3kkw/PieBl6m0lyhzHeuBpjZpBsf+Oac13fk8wjCZDxEpQjvB73q0OyX+/4jWtpkkQv0MMJp4+4ceVvN6+vhGSP+CvwySOSnSOSdf1LJLVtRLIzklojEnbqiIQVIxJWjEhYMSJhxYiEFVO32w2MzcVJwop9AOIymUThCkPrAAAAAElFTkSuQmCC”

class=“img_ev3q” decoding=“async” loading=“lazy” width=“137”

height=“38” />for the tail and use it for rendered files by default.

Warning:

There is a bug currently for default tail and render blocks. Enable

tail while on region render matrix/ all project regions setting. After

that save render settings and then it should be fine. This bug does

not affect adding tail and ftail metatags.

Besides that you can define two custom tail metatag types - tail and

ftail. This is very useful for sounds that have long reverb tails.

<img src=“/docs/images/image76-55dbd0d99542130c2d4477341fffcf3a.png”

class=“img_ev3q” decoding=“async” loading=“lazy” width=“1743”

height=“495” />

The example shows the same sfx rendered with different tail settings.

| | |

|--------|-----------------|

| ORANGE | no tail metatag |

| RED |    tail=2000 |

| GREEN |  ftail=2000 |

Fade shape that is used for ftail is shown in the image below and for

now cannot be changed.