From 656b0311388de02507caeebd326cd42c5cca6ffc Mon Sep 17 00:00:00 2001 From: Jaroslaw Grishunin <41283085+oslavdev@users.noreply.github.com> Date: Mon, 16 Mar 2026 10:15:05 +0100 Subject: [PATCH 1/3] fix: fix wording --- index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index bc5315d..80abdbe 100644 --- a/index.html +++ b/index.html @@ -146,7 +146,7 @@

Snare Drum

100–200 Hz

BOOST — body

-

Adds body ? and fatness to the shell. Makes the snare sound like a real wooden drum, not a tin can.

+

Adds body ? and fatness to the shell. Makes the snare sound like an actual wooden drum rather than a tin can.

300–500 Hz

@@ -330,7 +330,7 @@

Recommended Settings Per Piece

Threshold−6 to −8 dB
Attack30–50 ms
Release100–250 ms
-

Glues all drums together. Should feel like one kit, not separate pieces.

+

Glues all drums together. Should feel like one cohesive kit hitting the same room.

@@ -712,7 +712,7 @@

Mastering

EQ for Mastering

Gentle overall shaping -

Mastering EQ should be subtle. If you need more than 3–4 dB of any boost or cut here, the mix has a problem that should be fixed at mix stage — not masked in mastering. Think of it as fine-tuning, not surgery.

+

Mastering EQ should be subtle. If you need more than 3–4 dB of any boost or cut here, the mix has a problem that should be fixed at mix stage — mastering can't paper over it. Think of it as fine-tuning. Targeted adjustments, kept small.

Sub cleaning
< 30 Hz

High-pass: always

Even a well-mixed track has subsonic content from room noise or headphone bleed. A steep high-pass at 20–30 Hz protects woofer excursion ? and reclaims loudness headroom.

@@ -726,12 +726,12 @@

EQ for Mastering

Compression for Mastering

- Glue, not control + Cohesion over control
-

Mastering compression is used for glue ? and density ?, not loudness. The settings are extremely gentle compared to mix compression.

+

Mastering compression is used for glue ? and density ? — loudness comes later, at the limiter.

-

Ratio

1.5:1 – 2.5:1

Extremely gentle. At this stage you are barely touching the signal. 2:1 is considered aggressive for mastering. Above 3:1 and you're mixing, not mastering.

+

Ratio

1.5:1 – 2.5:1

Extremely gentle. At this stage you are barely touching the signal. 2:1 is considered aggressive for mastering. Push past 3:1 and you've crossed back into mix territory.

Threshold

−6 to −12 dB

Set to get 1–3 dB of gain reduction ? on the loudest parts. If you're seeing 6 dB+, you're overcompressing and will kill the life of the mix.

Attack

30–100 ms (slow)

Slow attack preserves transients. You never want to kill the punch of a kick or snare in mastering. Very slow attack = transparent glue that doesn't touch the impact.

Release

Auto or 200–400 ms

Slow release tracks the program dynamics ?. Most mastering engineers use auto release. Listen for pumping on loud-to-quiet transitions.

@@ -853,4 +853,4 @@

Glossary

- + \ No newline at end of file From cf9656b59ed5f77d3d1ec0b7874359f3c0f8f2d0 Mon Sep 17 00:00:00 2001 From: Jaroslaw Grishunin <41283085+oslavdev@users.noreply.github.com> Date: Mon, 16 Mar 2026 10:35:57 +0100 Subject: [PATCH 2/3] chore: fix body lint danger --- Dangerfile.js | 8 ++++---- package.json | 5 ++++- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/Dangerfile.js b/Dangerfile.js index b11baa4..8c9116b 100644 --- a/Dangerfile.js +++ b/Dangerfile.js @@ -97,9 +97,9 @@ if (!CONVENTIONAL_PATTERN.test(danger.github.pr.title)) { fail( `PR title \`${danger.github.pr.title}\` does not follow ` + '[Conventional Commits](https://www.conventionalcommits.org/) format.\n\n' + - 'Expected: `type(scope): description` — e.g. `feat: add reverb section` ' + - 'or `fix(tooltip): clamp position on narrow screens`.\n\n' + - 'This is required because the PR title becomes the squash-merge commit ' + - 'message that **semantic-release** uses to determine the version bump.', + 'Expected: `type(scope): description`\n' + + 'e.g. `feat: add reverb section` or `fix(tooltip): clamp on narrow screens`\n\n' + + 'The PR title becomes the squash-merge commit message that\n' + + '**semantic-release** uses to determine the version bump.', ) } \ No newline at end of file diff --git a/package.json b/package.json index c62ef8b..f5242cd 100644 --- a/package.json +++ b/package.json @@ -37,7 +37,10 @@ "commitlint": { "extends": [ "@commitlint/config-conventional" - ] + ], + "rules": { + "body-max-line-length": [0] + } }, "lint-staged": { "src/js/**/*.js": [ From 46465edd80f22b5af3526016cb9181b6423cb08d Mon Sep 17 00:00:00 2001 From: Jaroslaw Grishunin <41283085+oslavdev@users.noreply.github.com> Date: Mon, 16 Mar 2026 12:41:19 +0100 Subject: [PATCH 3/3] chore: add danger permission to write --- .github/workflows/main.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 7835449..94e7dba 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -62,6 +62,7 @@ jobs: contents: write issues: write pull-requests: write + statuses: write steps: - name: Checkout