/* global React, ReactDOM, LeftSidebar, SiteHeader, SiteFooter, Lenis, ConsoleVoices */ /* * Virtue Console — product page. * * ANNOUNCES. DOES NOT SELL. Rodney's decision, 2026-09-03: no price, no buy * button, no download. There is nothing to license yet, nothing signed, and no * build for a second platform, so a purchase path here would be a promise the * product cannot keep. * * EVERY CLAIM ON THIS PAGE IS PINNED IN FACTS.json and `npm run check:facts` * is watching six Console rules. Before editing a number here, read the rule: * * console-inserts-nothing "Opening Console inserts nothing" is TRUE and is * the best thing about the product. The old claim * that we contribute no processing of our own went * FALSE on 2026-09-03 and must never return. The * two are not the same claim. The rule lists the * exact wordings that are blocked - read it there. * console-oversampling 13.6 dB, from 1479 to 65. Not rounded, not a * percentage, and never described as abolishing * the problem. Latency is DECLARED, not absent. * console-vwide Widens above 150 Hz only. The origin of that code * is never named in site copy - standing policy. * console-vca-not-new REAPER has had VCA groups since v5. Better * presentation, never a new capability. * console-metering-honesty Implements the BS.1770-4 formula. Has NOT been * run against the Tech 3341 conformance files. * "Bit-transparent" is true of the METERING PATH * only, never of the product. * console-not-shipping No price, no purchase, macOS and REAPER only. * * NOTE FOR THE NEXT PERSON: check:facts scans this whole file, comments and * all. It cannot tell a warning from a claim, so a comment that QUOTES a * forbidden phrase fails the build exactly as the phrase itself would. That is * the right trade - it caught this header on its first run - but it means * warnings here have to describe the banned wording rather than repeat it. * * The feature list is the "Built" section of VIRTUE_CONSOLE/docs/REQUIREMENTS.md * and nothing else. The "Asked for, not built" table in that file - monitor * section, cue sends, MIDI learn, skins, VCA - must never appear here as a * page section. Neve owns that file; ask her before adding a row. */ const { useEffect: useEffectC } = React; const useLenisC = () => { useEffectC(() => { if (typeof Lenis === 'undefined') return; if (window.matchMedia('(prefers-reduced-motion: reduce)').matches) return; const lenis = new Lenis({ duration: 0.6, smoothWheel: true }); let raf; const tick = (t) => { lenis.raf(t); raf = requestAnimationFrame(tick); }; raf = requestAnimationFrame(tick); return () => { cancelAnimationFrame(raf); lenis.destroy(); }; }, []); }; /* A VU face drawn to Console's own geometry, not a picture of one. * Numbers from VIRTUE_CONSOLE/assets/templates/README.md, which is generated by * tools/make_vu_template.py - the same source drawVuMeter() reads, so the art * and the renderer cannot drift: * face 240 x 178, pivot (120, 231.4) - 53.4px BELOW the face, which is what * gives a VU its shallow arc - arc radius 186.9, sweep +/-27 deg from * vertical, 0 VU at 70.8% of the sweep because a VU deflects with rectified * average voltage rather than with decibels. That is why the ticks crowd * toward the top of the scale instead of spacing evenly. * Drawn, not photographed: there is no Console screenshot yet and a mocked-up * one would be a picture of something that does not exist. */ const VuFace = () => ( -20 -10 -5 -3 0 +3 {/* The needle takes the accent. It is the only live element on the face, which is the whole argument for what the accent is for. */} VU ); const Eyebrow = ({ children }) => (

{children}

); const Rule = () => (
); /* One built feature. Rules, not cards with shadows. */ const Feature = ({ title, children }) => (

{title}

{children}

); const Spec = ({ label, value }) => (
{label}
{value}
); const Section = ({ id, children, tone }) => (
{children}
); const Console = () => { useLenisC(); return ( <>
{/* ---- Hero ------------------------------------------------------ */}
Virtue Creative Systems · In development

Virtue Console

A mixer for REAPER with calibrated metering on every track, and a channel strip that stays out of the way until you switch it on.

Opening it inserts nothing into your project and changes nothing you did not ask it to change. That is a design rule, not a default.

Not released. No price yet. macOS, inside REAPER.

A drawing, not a screenshot. The scale is plotted from Virtue Console's own geometry — 54 degrees of sweep, 0 VU at 70.8 per cent of it — which is why the marks crowd toward the top: a VU deflects with average voltage, not with decibels.
{/* ---- The constraint -------------------------------------------- */}
The rule everything else is built around

Opening Console inserts nothing.

Placement happens when you open it

Never on project load. Opening an old session to find something new in the chain is the thing this rule exists to prevent.

Removing it is an instruction

Take the probe off a track and it is not put back. Putting one back by hand overrides the opt-out. Your decision holds in both directions.

The channel strip is off by default

It is opt-in, per track. Nothing is processed because you opened a mixer. If you never switch it on, it never runs — and it costs you nothing.

{/* ---- Built ------------------------------------------------------ */}
What is built today

A mixer, with the readings on it.

Everything on this list works now. Anything not on it is not built, and is not described anywhere on this page as though it were.

Every track's meter in one row, scrolling in lockstep with the channels beneath it, so the bridge and the strip never disagree about which track you are looking at. VU, PPM, K-12, K-14, K-20 and LUFS. Three sizes, one needle or two. A meter skin per track, with a global default, so the drum bus can read K-14 while the master reads loudness. The three most likely keys for each track, in order, each with a confidence figure attached. A guess that tells you how much of a guess it is. Empty drop slots, drag to reorder, and drag-and-drop straight from Virtue FX Manager or from the Finder. A plugin dragged onto a channel lands on that channel. The sends list, the routing row, phase, FX chain bypass and monitor cycling, all on the channel rather than three dialogs away. Reorder channels by dragging the scribble strip. Extra rows appear when the window is tall enough to hold them. Mouse wheel on a fader or a pan, double-click to reset, and REAPER's own transport shortcuts keep working while the window has focus.
{/* ---- The processing --------------------------------------------- */}
The processing

Switch the strip on and it is ours, all the way down.

Filters, dynamics and a four-band equaliser on the channel. Summing, tape and a channel voice across the desk. A stereo stage at the end. None of it runs until you ask a track for it, and all of it is built to a standard that is worth paying for — which is the argument below, with the measurements attached.

Every nonlinear stage is oversampled

A summing encode, a tape, a valve — anything nonlinear makes harmonics, and the harmonics above half the sample rate do not vanish. They fold back down and land on frequencies with no musical relationship to what you played. Harmonic distortion sounds like weight, because it lands on notes related to the note. Folded distortion sounds like grit, and it moves the wrong way: play a rising line and those products descend. That is most of why digital saturation sounds small next to the hardware it is copying.

So we measured it. A 6.5 kHz tone through a hard nonlinearity, summing the energy in every FFT bin that is not a harmonic of the input — everything produced that has no relationship to what went in.

At the session rate
1479
At 4x
65
Inharmonic energy
13.6 dB less

Reproducible, from the test suite, not from a listening session. Oversampling reduces this — it does not abolish it, and anyone who tells you otherwise has not measured it.

2x and 4x, and 1x is still there

1x is the original behaviour, it is a sound, and someone will want it. It is not the default.

The latency is declared

Exactly half the filter length, reported to the host, so your channels stay lined up. We tell you the number rather than pretending there isn't one.

Linear phase, stated stopband

A polyphase halfband filter, whose coefficients are derived at start-up rather than copied from a table — so the stopband is a number we can quote.

The stereo stage leaves your low end alone

Below about 150 Hz the ear places a sound by level and timing, not by the channel-to-channel relationship a widener manipulates — and a room's low end is ruled by its modes, not by where the sound is. So widening the bass buys no image at all, and it costs you the weight of the mono sum. It is the most common single reason a mix that sounds enormous on headphones falls apart on a club system, a phone, or a record.

So the stage splits the signal, widens only what is above the crossover, and returns the low band untouched. The crossover is fixed and has no control, deliberately: you cannot hear a crossover, only what it protects, so a knob here would be one nobody could set by ear. It is a gentle one-pole, chosen so the two bands sum back to the input when the widener is doing nothing at all.

It stays cheap in the quiet parts

Every filter on the desk decays toward zero when the music stops, and lands in the denormal numbers below the float format's normal range — where some processors run one to two orders of magnitude slower. The symptom is a plugin that is cheap while playing and expensive in the gaps, which is exactly the wrong way round: the gaps are where forty channels of reverb tail have nothing to hide behind. It never shows up on a CPU meter, because you read that while something is playing. One register write per block fixes it, and the host's own setting is put back on the way out.

{/* ---- The planned voices ----------------------------------------- Live as of 2026-09-04. It was behind ?voices=on while two of the nine renders were unusable - one carried a real manufacturer's badge, one had a typo on its nameplate. Both were retouched and checked, so the gate is gone. The framing has NOT changed and must not: these are nine PLANNED voices for an unreleased product. Artwork existing does not make any of them exist. */} {/* ---- Metering spec ---------------------------------------------- */}
Metering

Calibrated, and checked at five sample rates.

A meter is only worth having if you can trust the number on it. Here is exactly what was verified, and by what.

{/* ---- What it does not do ---------------------------------------- */}
What it does not do

The part most pages leave out.

You will find all of this out in the first ten minutes anyway. Better here.

The loudness engine is checked against the standard's formula. It has not been run against the EBU Tech 3341 conformance material, which is a different and stricter thing. Until that run happens we will not describe it as anything more than what it is.} /> REAPER has had these natively since version 5. What is on the roadmap is showing them properly, because they are awkward and invisible today. Presentation, not a new capability — the same goes for track colour on the name plate.} />
{/* ---- Close ------------------------------------------------------ */}

Want to know when it is ready?

Send us a line and we will tell you when there is something to install. No list you have to escape from afterwards.

Get in touch

Meanwhile, Virtue FX Manager is shipping, and it is the other half of the same idea: your tools where you can see them.

); }; const rootC = ReactDOM.createRoot(document.getElementById('root')); rootC.render();