Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Sound Engineer A/B Master Profile Block for React

A sound engineer profile as an A/B master compare: a segmented control that swaps a drawn waveform of the mix and the master, with integrated loudness, true peak and dynamic range and the difference in words, and three credits as ruled rows.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Let an engineer show what mastering did, without playing a note, with this sound engineer A/B master profile for React with Base UI. A compact header holds the title and one sentence, and the hairline frame under it opens on the engineer: initials, name, role and place. A Segment Group swaps between "A: Mix" and "B: Master" of one track, and a drawn waveform of forty-eight slices (a quiet intro, two verses, two choruses and an outro) changes with it: the master's slices are the mix's pushed up and held at a ceiling, so the loud parts flatten. Under the figure three readouts give the integrated loudness in LUFS, the true peak in dBTP and the dynamic range in DR, and one sentence says the difference, worked out from them: "B is 5.2 LU louder and 4 DR flatter than A." Three credits sit under it as ruled rows. Nothing plays: the figure says "Drawn waveforms; no audio. No audio in this demo." It's built from Segment Group, Data List, Badge, Avatar and Guides with CSS only. The engineer, the artists and the figures are invented. For a studio network, an engineer's own page or any profile that proves a result with numbers.

FAQ

How do I fill it with my own track?

Edit MIX_BARS (forty-eight numbers from 0 to 100, one per slice of the song) and the two Take objects: each has its loudness in tenths of a LUFS (-172 is -17.2), its true peak in tenths of a dBTP and its dynamic range. The master's slices are worked out from the mix's with a gain and a ceiling (GAIN, CEILING); in your app give each take its own measured slices instead. The differences in the sentence, the ruler and the counts are worked out from the readouts.

Is the waveform real audio?

No. It is forty-eight spans in CSS, drawn from typed numbers, and nothing plays or is decoded: the caption says so. Slices that reach 70 or more draw in full weight and the others in a lighter one, so the flat top of the master shows where it is held at the ceiling. In your app draw the real waveform from your audio's peaks, keep the segmented control and the readouts, and keep the text equivalent.

What do the readouts mean, and how is the sentence worked out?

Integrated loudness is how loud the whole track is on average (LUFS, and a difference between two of them is in LU), true peak is the highest level a converted signal can reach (dBTP), and dynamic range (DR) is how much the loud and quiet parts differ. The sentence subtracts the mix's loudness from the master's, and the master's range from the mix's, so it can never disagree with the readouts above it. The figures are examples, not a standard to meet.

Is it accessible?

The waveform is a picture and is hidden from screen readers; a caption beside it says what it shows ("Waveform of the master, 48 slices from a quiet intro to a quiet outro. 17 of them sit near the top.") and the readouts say the numbers. The segmented control is named by its heading, the status line is a polite live region present from the start, and the waveform and the ruler keep left-to-right order in a right-to-left layout because they are a time axis. The slices change height with a short transition that stops under reduced motion.

How does it look on a phone?

The segmented control sits under the heading and fills the width, the waveform is a little shorter, and the three readouts stay in one row with smaller figures. The sentence and the credits follow. The panel keeps the same height whichever take is shown.

What stays local?

Everything. Switching takes only changes the picture, the readouts and the status line; there is no audio, no file and no request, and the artists, credits and figures are invented sample data. The page's own text says so, and so does the caption under the waveform.

  • Pro

    A musician profile as a discography: a cover band of four drawn typographic covers over the musician, an accordion of albums, and for the open album its tracks with lengths, stream bars scaled to its top track and a star on the most streamed.

  • Pro

    A music listener profile with top artists by range: a start cell with the listener and facts from the history, and a segmented control that re-ranks ten artists in place with plays, a share bar and the move against the period before as a sign and an arrow.

  • Pro

    A film director profile as a filmography on a year axis: eight films as pickable bars of box office on a fixed axis with a star over award winners, a genre filter that dims the other films, and rows for the picked film's budget, earnings, awards and collaborators.

  • Pro

    An animator profile as a frame scrubber: a drawn stage worked out from the frame number, a slider through 96 frames at 24 a second with the timecode and shot name, shots as buttons that jump to their first frame, and the credits.

  • Pro

    An architect profile as performance targets: tabs for three projects, each with energy, carbon and daylight targets drawn as bars with a tick, the figure reached, and Meets or Misses in words with a glyph, beside a rating worked out from the targets met.

  • Pro

    An author profile as a look inside: four books with drawn typographic covers, a read-only rating and an award badge, and a reading pane with a drop cap, a text size group and Next and Previous between two pages, beside a Follow toggle.