<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>sauvachi — journal</title>
    <link>https://sauvachi.com/blog</link>
    <atom:link href="https://sauvachi.com/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Notes on releases, the studio and the site, written by sauvachi.</description>
    <language>en</language>
    <lastBuildDate>Wed, 05 Aug 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Why an artist website still matters when streaming exists</title>
      <link>https://sauvachi.com/blog/why-an-artist-website-still-matters</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/why-an-artist-website-still-matters</guid>
      <pubDate>Wed, 05 Aug 2026 12:00:00 GMT</pubDate>
      <description>Every platform you build on can change its rules overnight. A domain you own cannot. What a site is actually for in 2026, and what belongs on one.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>guide</category>
      <content:encoded><![CDATA[<p>The argument against an artist website is easy to make. Nobody types a domain into a browser any more. Discovery happens on platforms. A site takes work, costs money, and sits there quietly while the algorithm does the introducing.</p>
<p>All true, and none of it is the point. A site is not a discovery channel and it never was. It is the one address in the whole operation that cannot be taken away, rate-limited, deprioritised, or quietly redesigned around you.</p>
<h2>What you actually own</h2>
<p>Count what an independent artist controls outright. A domain. A mailing list. The files themselves. That is close to the whole list. Everything else — followers, playlist placements, monthly listeners, video views — is held on your behalf by a company whose product roadmap you do not see and whose terms you agreed to without reading.</p>
<p>None of that is a conspiracy. It is just the arrangement. Platforms are extraordinary distribution and terrible property. The lesson every artist learns eventually is to use them hard for what they are good at, and to keep the things that matter somewhere else.</p>
<h2>What a site is for</h2>
<p>Four jobs, in rough order of importance:</p>
<ul>
  <li><strong>Being the answer to “where do I find your stuff?”</strong> One link that leads to everything, rather than five that each lead to a fifth of it.</li>
  <li><strong>Collecting emails.</strong> The only audience list you can export, back up, and take with you.</li>
  <li><strong>Being the place press, promoters and collaborators land.</strong> A booking agent looking you up wants a bio, photos and contact details in ten seconds, not a scroll through your grid.</li>
  <li><strong>Saying things in your own words.</strong> A caption is not writing. A site is where the longer version lives.</li>
</ul>
<h2>What actually belongs on it</h2>
<p>Most artist sites fail in the same two ways: they are either a link tree with a background image, or a design project nobody can navigate. The middle is not complicated.</p>
<ul>
  <li><strong>A catalog page</strong> that lists everything you have released, each entry linking to every platform it is on. Not just the newest single.</li>
  <li><strong>A way to actually listen</strong>, on the site, without an account. If someone arrives curious, do not send them away to satisfy that curiosity.</li>
  <li><strong>An email capture</strong> that says what people are signing up for, and then only sends that.</li>
  <li><strong>A press section</strong> — bio in three lengths, high-resolution photos, logo, contact address.</li>
  <li><strong>A contact route</strong> that a human reads.</li>
</ul>
<p>What does not belong: an intro animation, a mailing-list popup that fires before anyone has heard a note, and social feeds embedded in a way that makes the page slower than the platform they came from.</p>
<h2>The maintenance question</h2>
<p>The real reason artist sites die is not cost, it is friction. If publishing a release means editing HTML in three places, you will stop doing it by the third release. That is why this site keeps its whole catalog in a single data file: a new track is a few lines of JSON, and every page that mentions releases updates at once.</p>
<p>Whatever you build on, apply the same test before you commit: <em>how many steps between “the song is out” and “the site says so”?</em> If the answer is more than two, the site will be out of date within a year, and an out-of-date site is worse than no site at all.</p>
<h2>The honest summary</h2>
<p>A website will not break an artist. Nobody has ever gone from unknown to booked because their domain resolved. But every artist who lasts eventually needs a place that is theirs — for the press request, the sync opportunity, the label that wants to hear more than three singles, the fan who wants to go deeper than the algorithm allows.</p>
<p>Building that place is cheap and boring and takes a weekend. Not having it is only a problem on the day it matters, which is exactly the day you cannot fix it.</p>
<p>If you want to see the version of this argument taken to its conclusion, the <a href="/listen">player on this site</a> is the whole catalog streaming without an account — the part most artist sites still send you elsewhere for.</p>]]></content:encoded>
    </item>
    <item>
      <title>The first 48 hours of a release: what actually moves</title>
      <link>https://sauvachi.com/blog/first-48-hours-of-a-release</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/first-48-hours-of-a-release</guid>
      <pubDate>Thu, 30 Jul 2026 12:00:00 GMT</pubDate>
      <description>Playlists, saves, shares and the algorithm — what genuinely matters in the two days after a track goes live, and what is just noise you can safely ignore.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>guide</category>
      <content:encoded><![CDATA[<p>Release day has a mythology around it. Somewhere in the first 48 hours, the story goes, an algorithm decides your fate, and everything you do in that window either unlocks or forfeits the next six months.</p>
<p>The truth is duller and more useful. Nothing is decided in two days. But the first 48 hours do produce the signal that everything downstream is built on, and most of that signal comes from a small number of things you can actually influence.</p>
<h2>What the platforms are watching</h2>
<p>Recommendation systems differ in the details, but the questions they ask are broadly the same, and they are questions about <em>behaviour</em>, not volume:</p>
<ul>
  <li><strong>Did people finish it?</strong> Completion rate is the closest thing to a universal signal. A skip at twenty seconds says more than a thousand plays.</li>
  <li><strong>Did they save it?</strong> A save is a deliberate act with a cost — it says “I want this again”, which is exactly what a recommender wants to predict.</li>
  <li><strong>Did they come back?</strong> Repeat listens across days beat a single burst on day one.</li>
  <li><strong>Did they add it to their own playlists?</strong> The single strongest endorsement an ordinary listener can give.</li>
</ul>
<p>Notice what is missing: raw play count, follower count, and how many people you sent the link to. Those are inputs at best, and easy to fake, which is exactly why they carry so little weight.</p>
<h2>What is worth doing</h2>
<p>Given the above, the sensible release-day plan is short:</p>
<ul>
  <li><strong>Tell the people who already care, first and directly.</strong> Email list, close friends, the group chat. They are the ones who will finish and save it, which is the signal that matters.</li>
  <li><strong>Give one clear instruction.</strong> “Save it” beats “check out my new song” — it is specific, it takes a second, and it is the exact behaviour the system reads.</li>
  <li><strong>Make the link work everywhere.</strong> One smart link that opens in the listener's own platform, not a Spotify URL sent to somebody on Apple Music.</li>
  <li><strong>Post more than once, differently.</strong> One announcement reaches a fraction of your audience. Three posts in different formats over two days is not spam, it is arithmetic.</li>
  <li><strong>Pitch before, not after.</strong> Editorial pitching happens in the weeks before release. On the day itself, that window is closed.</li>
</ul>
<h2>What is not worth doing</h2>
<p>Refreshing the stats page hourly. Buying anything that promises plays — the behavioural signal from purchased streams is uniformly terrible, and the systems are extremely good at spotting it. Emailing a hundred playlist curators you have never spoken to. Comparing your day-one numbers to an artist whose day one came after four years of touring.</p>
<blockquote>Day one tells you who was already listening. Day thirty tells you whether the song is any good.</blockquote>
<h2>The thing nobody says out loud</h2>
<p>The single biggest factor in how a release performs is the release itself. No promotion strategy rescues a track people do not finish, and a track people play twice needs remarkably little help. That is not a comforting conclusion when you have just spent a month on a rollout plan, but it is the one that survives contact with the data.</p>
<p>Which points at the actual strategy: release more often. Every release teaches you something, refreshes your presence, and gives the next one a slightly warmer start. Artists who put out six things a year learn six times faster than artists who put out one and promote it for a year.</p>
<h2>After the 48 hours</h2>
<p>The window that actually matters is the following month. Add the track to your own playlists. Send it to people individually as it comes up naturally. Write about it — a post explaining what a song is gives people a second reason to press play, and gives search engines something to index besides a title.</p>
<p>That last part is not incidental. Every release on this site gets written about in the <a href="/blog">journal</a>, and the writing outlives the release-week noise by a considerable margin.</p>]]></content:encoded>
    </item>
    <item>
      <title>Listen anywhere: the sauvachi player is live</title>
      <link>https://sauvachi.com/blog/listen-anywhere-the-sauvachi-player</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/listen-anywhere-the-sauvachi-player</guid>
      <pubDate>Fri, 24 Jul 2026 12:00:00 GMT</pubDate>
      <description>The whole catalog now streams straight from this site — installable, offline-capable, and with no account to create. Here is what it does and how to put it on your home screen.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>site</category>
      <content:encoded><![CDATA[<p>Every release on this site has always pointed somewhere else. You would find a track here, tap a logo, and finish the journey on a platform that decided what you heard next. That was fine for a link page. It was never the plan.</p>
<p>The player at <a href="/listen">sauvachi.com/listen</a> is the other half. The full catalog, playable in the browser you are already in, with no account, no install prompt you have to accept, and no algorithm rearranging the running order.</p>
<h2>What it does</h2>
<ul>
  <li><strong>Plays the whole catalog</strong> — singles, collaborations and remixes, in the order they were meant to be heard.</li>
  <li><strong>Keeps your place.</strong> Close the tab mid-track and it picks up where you left off, queue intact.</li>
  <li><strong>Works offline.</strong> Save a release once and it stays on your device — trains, planes, and the parts of the city where signal goes to die.</li>
  <li><strong>Installs like an app.</strong> Add it to your home screen and it opens full-screen, no browser bars, with playback controls on your lock screen.</li>
  <li><strong>Remembers nothing about you.</strong> Saved tracks, volume, repeat and shuffle all live in your own browser storage. None of it is sent anywhere.</li>
</ul>
<h2>Putting it on your home screen</h2>
<p>On <strong>iPhone</strong>: open <a href="/listen">/listen</a> in Safari, tap the share button, then <em>Add to Home Screen</em>. On <strong>Android</strong>: open it in Chrome, tap the menu, then <em>Install app</em>. On desktop, most browsers show an install icon at the right-hand end of the address bar.</p>
<p>Either way you end up with an icon that launches straight into the catalog. It is the same page, minus everything around it — and because it is a web app rather than a store download, it updates itself the moment something new goes up. There is nothing to reinstall and no version to fall behind on.</p>
<h2>Why build it at all</h2>
<p>Streaming platforms are the distribution, and that is not changing — new releases go everywhere on day one, and always will. Most people will hear this music on Spotify or Apple Music, and that is genuinely fine. But the place with the artist's name on the door should be able to do more than list links to somewhere else. If you came here to listen, you should be able to listen here.</p>
<p>There is a practical side too. A link page tells you nothing about what a body of work sounds like as a body of work. Fifteen singles released over two years are a sequence, not a shelf, and the only place that sequence can be presented deliberately is a site nobody else owns.</p>
<blockquote>The catalog belongs on the site with the artist's name on it. Everything else is a distribution channel.</blockquote>
<h2>Where to start</h2>
<p>If you have never heard any of this before, the two most recent singles are the fastest way in — <a href="/blog/again-out-now">“Again”</a> and <a href="/blog/that-part-out-now">“That Part”</a>, both from July, and both linked below. From there the <a href="/playlists">playlists</a> are sequenced runs through the catalog rather than one long alphabetical dump, which is what the release list on its own would give you.</p>
<h2>What is next</h2>
<p>On the list: proper credits on every track, lyrics where they add something, and downloads for the people who still keep a library. Longer term, the goal is that a new release lands here at the same moment it lands everywhere else, with the writing that goes with it.</p>
<p>If something is broken or missing, the fastest way to reach me is Instagram. And if you would rather hear about new music by email than by algorithm, the subscribe button at the top of this page is the whole mailing list — announcements only, nothing else.</p>]]></content:encoded>
    </item>
    <item>
      <title>“Again” is out now</title>
      <link>https://sauvachi.com/blog/again-out-now</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/again-out-now</guid>
      <pubDate>Sun, 19 Jul 2026 12:00:00 GMT</pubDate>
      <description>The newest sauvachi single is live on every platform. On the loop that started it, why it stayed under four minutes, and where to hear it.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“Again” is out now</strong>, everywhere you already listen. It is the second single in a month, and the one that took the longest to let go of.</p>
<h2>Where it came from</h2>
<p>It started as a loop I could not leave alone — four bars that sounded finished the first night and wrong every night after. That is usually the sign to move on. This time the loop kept pulling things towards it instead: a drum pattern that sits further back than I normally place one, a vocal take recorded quietly because it was late, and a low end I rebuilt three times before it stopped fighting the sample.</p>
<p>The title came before the lyric did. Once a track is called “Again” it starts telling you what it is about, and the writing gets a lot faster. Repetition as a comfort and repetition as a trap are the same behaviour described by two different moods, and the song does not take a side.</p>
<h2>What it sounds like</h2>
<p>Slower than the last two singles and considerably darker. The palette is small on purpose: one sampled figure, one bass, drums, and a vocal that stays close to the microphone throughout. Nothing arrives to rescue the arrangement halfway through — if anything, things leave.</p>
<p>If you have heard <a href="/releases/that-part">“That Part”</a>, this is the other end of the same month. That one is quick and blunt; this one takes its time and repeats itself until the repetition becomes the point.</p>
<h2>How it was built</h2>
<ul>
  <li>The first take of the hook is the one on the record. Every cleaner version afterwards sounded like someone describing the feeling rather than having it.</li>
  <li>There is no second verse in the traditional sense. The section that would have been one is the same words, arranged differently — which is the entire point of the song.</li>
  <li>The drums sit late. Quantising them to the grid made the track sound urgent, and urgency is the wrong emotion for this one.</li>
  <li>It is deliberately short. It ends while you still want the next pass, because the alternative is a track that outstays a two-line idea.</li>
</ul>
<h2>Listen</h2>
<p>“Again” is on <strong>Spotify</strong>, <strong>Apple Music</strong> and <strong>Tidal</strong>, and it is in the player on this site — you can hear it at <a href="/listen">sauvachi.com/listen</a> without leaving the page or creating an account anywhere. The release card below has every link in one place.</p>
<h2>If it lands with you</h2>
<p>The useful things are the ordinary ones: save it, add it to a playlist that is not mine, send it to one person who would like it. That is genuinely how these travel — there is no marketing budget behind any of this, and a single share does more than it looks like it should.</p>
<p>More is finished than released at the moment, so the gaps should stay short. The <a href="/blog">journal</a> is where each one gets written about properly, and the mailing list is the only place I say what is coming before it is out.</p>]]></content:encoded>
    </item>
    <item>
      <title>“That Part” is out now</title>
      <link>https://sauvachi.com/blog/that-part-out-now</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/that-part-out-now</guid>
      <pubDate>Mon, 13 Jul 2026 12:00:00 GMT</pubDate>
      <description>A faster, blunter single than the last one — written in two sittings and finished before it could be talked out of itself. Out now on all platforms.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“That Part” is out now.</strong> It is the quickest thing I have released in a while, in both senses: it moves faster than the last few singles, and it was finished faster than anything else this year.</p>
<h2>Two sittings</h2>
<p>The first sitting produced the beat and the hook. The second one was three days later and consisted mostly of not adding anything. There is a version of this track with strings, a bridge and a second half that answers the first — none of it made the cut, because every addition made the song more polite, and the song is not supposed to be polite.</p>
<p>Working quickly is not a virtue on its own. What it does is stop you negotiating with an idea until it agrees with everything else you have ever made. Three days was long enough to check the thing was good and short enough that I could still remember why I liked it.</p>
<blockquote>Most of the work on this one was deleting the work.</blockquote>
<h2>What to listen for</h2>
<ul>
  <li><strong>The drop-out before the last chorus.</strong> Everything leaves except the vocal, for slightly longer than is comfortable. That gap is the reason the last section hits.</li>
  <li><strong>The ad-libs are all first takes</strong>, recorded on the same pass as the lead. Comping them properly killed the momentum every time I tried.</li>
  <li><strong>The hook lands early.</strong> No long intro to earn — the first thing you hear is the thing the song is about.</li>
  <li><strong>No fade.</strong> It stops. Fades are for tracks that do not know how they end.</li>
</ul>
<h2>Where it sits</h2>
<p>Next to <a href="/releases/again">“Again”</a>, released six days later, this is the extrovert of the pair. Same month, same room, opposite instincts — one of them repeats an idea until it means something else, the other says it once and leaves. Played back to back in that order they make more sense than either does alone, which is roughly why both went out so close together.</p>
<h2>Listen</h2>
<p><strong>Spotify</strong>, <strong>Apple Music</strong> and <strong>Tidal</strong> have it now, and it is streaming in the <a href="/listen">player on this site</a> alongside the rest of the catalog — no account, no app to download. Every link is on the release card below.</p>
<p>There is more finished than released at the moment, so the gaps between these should stay short. The mailing list is the only place I say what is coming before it is out — the subscribe button at the top of the page is all there is to it.</p>]]></content:encoded>
    </item>
    <item>
      <title>“Lessons” with psydfx — out now</title>
      <link>https://sauvachi.com/blog/lessons-with-psydfx</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/lessons-with-psydfx</guid>
      <pubDate>Fri, 03 Jul 2026 12:00:00 GMT</pubDate>
      <description>A collaboration recorded across two time zones and a shared folder. What each of us brought, what we argued about, and how it ended up sounding like neither of us alone.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“Lessons” with psydfx is out now.</strong> It is the first thing we have put out together, and the first time in a while I have handed a track to someone else knowing it would come back unrecognisable.</p>
<h2>How a remote collaboration actually goes</h2>
<p>Nobody was in the same room at any point. The version that became the record is roughly the eleventh file in a shared folder, and the folder is a record of two people slowly converging: I sent a skeleton, psydfx sent it back with the harmonic content changed and the drums at half the tempo they started at, and the next four rounds were spent working out which of those two songs we were actually making.</p>
<p>Remote collaboration has a reputation for producing music that sounds assembled — two people politely leaving each other's parts alone. The fix, for us, was doing fewer rounds with bigger changes in each. Nobody nudging a hi-hat by three milliseconds and calling it a contribution; each pass had to justify itself by changing something that mattered.</p>
<h2>What each of us brought</h2>
<ul>
  <li>The chord movement and the vocal are mine, more or less from the first sketch.</li>
  <li>The rhythm section and the sound design are psydfx's, entirely — including the texture running under the second half that I still could not tell you how to make.</li>
  <li>The arrangement is the thing we fought over, and the released order is psydfx's. It was the right call and it took me two weeks to admit it.</li>
</ul>
<h2>The bit that nearly did not survive</h2>
<p>There is a moment about two-thirds through where everything drops to almost nothing before the last section. In my version it was four bars. In the version that shipped it is twice that, and it is the part of the track people mention first.</p>
<p>The lesson, appropriately enough, is that space is not empty — it is the thing that makes the loud part loud. I have a habit of filling gaps because a gap feels like an unfinished job. Watching someone else refuse to fill one, and being wrong about it in public for a fortnight, is a faster way to learn that than another year of doing it alone.</p>
<h2>Working with someone whose instincts differ</h2>
<p>The useful part of a collaboration is not the extra pair of hands. It is that every habit you cannot see in your own work is immediately visible to somebody else. Half the notes that came back on this track were about things I did not know I always do — start sections the same way, resolve tension too early, mix the vocal a little too far forward because I am used to hearing it that way.</p>
<p>None of that is a criticism of working alone, which is still how most of this catalog gets made. But a record that came out of an argument sounds different from one that came out of an agreement, and you can hear which this is.</p>
<h2>Listen</h2>
<p>“Lessons” is on <strong>Spotify</strong>, <strong>Apple Music</strong> and <strong>Tidal</strong>, and in the <a href="/listen">player here</a>. All the links are on the card below. Go and hear what psydfx does on their own too — this record makes more sense once you have.</p>]]></content:encoded>
    </item>
    <item>
      <title>“THE SPLIT” with NST — out now, with the video</title>
      <link>https://sauvachi.com/blog/the-split-with-nst</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/the-split-with-nst</guid>
      <pubDate>Fri, 19 Jun 2026 12:00:00 GMT</pubDate>
      <description>Two verses, two halves, one beat that changes underneath them. The single is out everywhere and the video is on YouTube.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“THE SPLIT” with NST is out now</strong>, and the video is up on YouTube alongside it.</p>
<h2>The idea</h2>
<p>The concept was in the title before either verse existed: one track, two halves, and a beat that does not stay the same underneath them. NST takes the first half over the version we started with. I take the second half over what that beat turns into — same key, same tempo, almost nothing else in common.</p>
<p>Songs with two names on them usually sound like two guests visiting somebody's track: verse, verse, everyone goes home. This one is built so neither half works without the other. Play the second half on its own and it sounds like an answer to a question nobody asked, which is exactly the test we wanted it to fail.</p>
<h2>The turn</h2>
<p>Everything hinges on one bar in the middle. We tried it as a hard cut, as a filtered sweep, and as a drum fill; the version on the record does the least of the three, and it is the only one that did not feel like a trick. If you are listening on something with real low end, that bar is where the track changes its mind.</p>
<p>Getting there took longer than writing either verse. A transition is the one part of a song where the machinery is visible — do too much and the listener hears the edit instead of the moment. Doing almost nothing turned out to be the loudest option available.</p>
<blockquote>Two verses, one beat, and one bar in the middle where it stops being the same song.</blockquote>
<h2>The video</h2>
<p>Shot in a day and cut to the same structure as the track: the first half is static and close, the second half does not sit still for more than a couple of seconds. There is no story and nobody is acting. Cheap, fast, and it looks like the song sounds — which is the only brief that ever matters.</p>
<p>It is worth watching once with the visual and once without. The cut sells the turn so hard that the audio version can feel understated by comparison, and the audio version is the one that is actually correct.</p>
<h2>Listen and watch</h2>
<p>“THE SPLIT” is on <strong>Spotify</strong>, <strong>Apple Music</strong> and <strong>YouTube</strong>, and it is in the <a href="/listen">player on this site</a>. Everything is linked on the release card below — the video is behind the YouTube button.</p>
<p>If you want the rest of the catalog in one place, the <a href="/releases">releases page</a> has all of it, and the <a href="/blog">journal</a> is where each new one gets written about on the day it lands.</p>]]></content:encoded>
    </item>
    <item>
      <title>Releasing a single independently: the full checklist</title>
      <link>https://sauvachi.com/blog/releasing-a-single-independently-checklist</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/releasing-a-single-independently-checklist</guid>
      <pubDate>Fri, 05 Jun 2026 12:00:00 GMT</pubDate>
      <description>Everything between a finished mix and a live release — masters, metadata, splits, artwork, distribution, timing — in the order it actually needs doing.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>guide</category>
      <content:encoded><![CDATA[<p>Releasing a track independently is not difficult, but it has a lot of small parts, and the parts that go wrong are almost never the musical ones. They are a mis-typed artist name, a missing credit, a cover that gets rejected two days before release, a feature who never signed off on a split.</p>
<p>This is the order I work in. Adjust it to taste, but do not reorder the first three.</p>
<h2>1. Agree the splits before anything else</h2>
<p>If more than one person touched the song, decide in writing who owns what before it goes anywhere near a distributor. Not after. Splits agreed while everyone is happy take five minutes; splits agreed after a song does well take lawyers.</p>
<p>Two separate things are being divided, and people confuse them constantly: the <strong>composition</strong> (the writing — melody, lyrics, chords) and the <strong>recording</strong> (the master itself). A producer might own half the master and a quarter of the composition. Write both down, get everyone to confirm by email at minimum, and keep it somewhere you will find it in three years.</p>
<h2>2. Finalise the master</h2>
<ul>
  <li>Get a dedicated master, whether from an engineer or a service. Do not upload a loud mix and hope.</li>
  <li>Keep the highest-quality file you have — deliver WAV, 24-bit, at the session's sample rate. Distributors transcode; you should never be the one who compressed it first.</li>
  <li>Ask for an instrumental and a clean version at the same time. You will want both later, and going back to an engineer six months on is its own small ordeal.</li>
</ul>
<h2>3. Get the metadata right</h2>
<p>This is the step everyone rushes and everyone regrets. Metadata is how your song is identified everywhere, forever, and some of it cannot be edited after release.</p>
<ul>
  <li><strong>Artist name spelled identically</strong> to your existing releases — capitalisation included. A different spelling creates a different artist profile.</li>
  <li><strong>Features credited in the artist field</strong>, not buried in the title, if you want them to appear on the other artist's profile.</li>
  <li><strong>Writer and producer credits</strong> filled in properly. This is what feeds the credits listing listeners see, and it costs nothing but attention.</li>
  <li><strong>ISRC</strong> — usually issued by your distributor. One per recording, permanently. A remix or a re-record is a new recording and needs a new one.</li>
  <li><strong>Explicit flag</strong> set honestly. Getting this wrong can pull a release from editorial consideration.</li>
</ul>
<h2>4. Artwork that survives being small</h2>
<p>Requirements are consistent across the major platforms: square, 3000×3000 pixels, RGB, no URLs, no social handles, no “out now” text, nothing you do not have rights to. Beyond compliance, the only test that matters is what it looks like at 60 pixels in a queue — which is where nearly everyone will see it.</p>
<h2>5. Pick a distributor and a date</h2>
<p>Distributors differ mainly on cost model (per-release, annual, or commission) and on how quickly they pay out. For a first release the differences are smaller than the internet suggests. What matters more:</p>
<ul>
  <li><strong>Deliver at least three to four weeks ahead.</strong> Editorial pitching windows close well before release day, and delivering late forfeits them entirely.</li>
  <li><strong>Friday release</strong> unless you have a specific reason not to — the industry's chart weeks are built around it.</li>
  <li><strong>Keep your rights.</strong> Read what you are signing. Distribution should be a service you pay for, not an assignment of your masters.</li>
</ul>
<h2>6. Register everything</h2>
<p>Distribution puts the song on platforms. It does not collect your publishing. Separately:</p>
<ul>
  <li>Register the composition with your performing rights organisation.</li>
  <li>Make sure a publishing administrator is collecting mechanicals, unless you enjoy leaving money uncollected.</li>
  <li>Claim your artist profiles — the artist-facing dashboards on the major platforms — so you can update photos, bios and pitch tracks yourself.</li>
</ul>
<h2>7. The week before</h2>
<ul>
  <li>Check the release appears correctly on every store as pre-save links go live.</li>
  <li>Set up one smart link that routes each listener to their own platform.</li>
  <li>Prepare the assets you will actually post: a short clip, a still, the artwork, and the sentence you will say about it.</li>
  <li>Write the email to your list. Send it on the day, not three days later.</li>
</ul>
<h2>8. After release</h2>
<p>Update your own site the same day — catalog entry, links, and the writing that goes with it. Add the track to your own playlists. Then start the next one: the most reliable promotion for a release is another release.</p>
<p>Two related pieces on this site go deeper on parts of the above: <a href="/blog/first-48-hours-of-a-release">what actually moves in the first 48 hours</a>, and <a href="/blog/smart-links-explained">why one smart link beats five platform links</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>“money gene” — out now</title>
      <link>https://sauvachi.com/blog/money-gene-out-now</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/money-gene-out-now</guid>
      <pubDate>Fri, 22 May 2026 12:00:00 GMT</pubDate>
      <description>The single that got the widest release of anything so far: every major platform, a video playlist, and a title that turned out to be about the wrong thing.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“money gene” is out now</strong> — and it went out wider than anything before it: Spotify, Apple Music, YouTube, Tidal, Amazon Music and Boomplay, all on the same day.</p>
<h2>The title was a placeholder</h2>
<p>Most of my files are named something useless — <em>idea 4</em>, <em>new one</em>, <em>bounce final FINAL</em>. This one got called “money gene” in the first session as a joke about a bassline that sounded expensive, and it stuck long enough to become true.</p>
<p>By the time there were lyrics, the title had already done half the writing. Songs are surprisingly obedient to their names. Call something “money gene” and it starts asking whether the appetite is inherited or learned, which is not a question I set out to write about and is now unmistakably what the song is about.</p>
<h2>What it sounds like</h2>
<p>Bigger and more open than most of the catalog. Where <a href="/releases/carbon">“CARBON”</a> and the tracks around it are close and compressed, this one has air in it — the drums sit in a room rather than against your ear, and the low end is allowed to move instead of being pinned in place.</p>
<p>It is also the most straightforwardly enjoyable thing I have released. That is not an apology. There is a version of this that hides the hook under three layers of texture to prove something; that version was worse in every measurable way and I deleted it.</p>
<h2>Notes from the session</h2>
<ul>
  <li>The bassline was written first, before drums and before any melodic content. Almost nothing else I have made starts there.</li>
  <li>The vocal was recorded twice: once properly, once quickly at the end of a session because the first one was too careful. The quick one is on the record.</li>
  <li>There is a full bar of near-silence before the last section. Everyone who heard the demo asked whether it was a glitch. It stayed.</li>
  <li>No key change, no dramatic outro. It stops where it stops.</li>
</ul>
<h2>Why the wide release</h2>
<p>Every platform, deliberately. There is a temptation to focus effort on the one service where the numbers look best and let the rest happen automatically — but the people who use Boomplay or Amazon Music are not a rounding error, they are just somewhere else. Being missing from where someone already listens is the easiest audience loss there is to avoid, and it costs nothing to fix.</p>
<h2>Listen</h2>
<p>Every link is on the release card below, and the track is in the <a href="/listen">player on this site</a> alongside the rest of the catalog — no account, no app.</p>
<p>If you want the mechanics behind releasing on that many services at once, <a href="/blog/releasing-a-single-independently-checklist">the independent release checklist</a> covers it end to end.</p>]]></content:encoded>
    </item>
    <item>
      <title>Smart links explained: why one URL beats five</title>
      <link>https://sauvachi.com/blog/smart-links-explained</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/smart-links-explained</guid>
      <pubDate>Fri, 08 May 2026 12:00:00 GMT</pubDate>
      <description>The link you post decides how many people actually hear the song. How smart links work, what they cost you, and the mistakes that make them worse than a plain URL.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>guide</category>
      <content:encoded><![CDATA[<p>Here is a small, extremely common way to lose most of your audience: post a Spotify link.</p>
<p>Roughly half the people who see it are not Spotify users. They tap, land on a page asking them to sign up for a service they do not want, and leave. The song was fine. The link was the problem.</p>
<h2>What a smart link is</h2>
<p>A smart link — you will also see them called pre-save links, landing pages, or by the brand names of the services that provide them — is one URL that shows the listener a page of every platform the release is on, and remembers which one they picked so it goes straight there next time.</p>
<p>That is the whole idea. One link in your bio, one link in the post, one link in the email, and every listener ends up in the app they already have.</p>
<h2>What they actually solve</h2>
<ul>
  <li><strong>Platform mismatch.</strong> The core problem, above.</li>
  <li><strong>Link rot in bios.</strong> One URL you update in place, instead of editing five profiles every release.</li>
  <li><strong>Pre-saves.</strong> Before release day, the same page can collect saves that fire automatically when the track goes live — which puts the song into people's libraries at the exact moment early behaviour is being measured.</li>
  <li><strong>Measurement.</strong> You can see how many people clicked and which platforms they chose. Modest data, but more than a raw platform link gives you.</li>
</ul>
<h2>What they cost you</h2>
<p>An extra tap. That is real, and it is why the advice is not “always use one”. If you are posting inside an environment where you know the platform — a Spotify-native context, or a message to one person you know uses Apple Music — link directly. Every unnecessary intermediate page loses some people.</p>
<p>There is also a dependency: your links now live on somebody else's service. If it disappears, every post you ever made points at nothing. Which is an argument for pointing at your own domain where you can, and letting your site handle the routing — the same reason <a href="/blog/why-an-artist-website-still-matters">the site itself matters</a>.</p>
<h2>Mistakes that make them worse than useless</h2>
<ul>
  <li><strong>Listing dead platforms.</strong> A page with nine buttons where four go to stores nobody uses is a worse experience than three good ones.</li>
  <li><strong>Leaving the default artwork and title.</strong> If the page does not immediately look like the song, people assume they mis-tapped.</li>
  <li><strong>Gating the music behind an email form.</strong> Asking for an address before anyone has heard a note converts almost nobody and annoys everyone.</li>
  <li><strong>Making a new link for every post.</strong> One canonical link per release. Fragmenting your own click data helps nobody.</li>
  <li><strong>Forgetting it after release week.</strong> The link lives in bios and old posts for years. Check occasionally that it still resolves.</li>
</ul>
<h2>What we do here</h2>
<p>Every entry in the catalog on this site carries both: the individual platform links <em>and</em> a single aggregate link, so the release page can serve someone who knows exactly what they want and someone who just wants to press play. The releases in the <a href="/releases">catalog</a> each have their own page doing precisely that.</p>
<p>And for the case a smart link cannot solve — the person who does not want to leave at all — there is <a href="/listen">the player</a>. No platform, no account, no redirect. Sometimes the best link is the one that does not send anyone anywhere.</p>]]></content:encoded>
    </item>
    <item>
      <title>“To Kojayi (Remix)” with Youngka — out now</title>
      <link>https://sauvachi.com/blog/to-kojayi-remix-with-youngka</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/to-kojayi-remix-with-youngka</guid>
      <pubDate>Fri, 24 Apr 2026 12:00:00 GMT</pubDate>
      <description>A remix that kept the vocal and rebuilt everything under it. On what a remix owes the original, and where this one deliberately disagrees with it.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“To Kojayi (Remix)” with Youngka is out now.</strong> The vocal is the original. Essentially nothing under it is.</p>
<h2>What a remix owes the original</h2>
<p>There are two schools. One says a remix is a service: keep the song recognisable, change the clothes, deliver it to a room the original could not reach. The other says a remix is a reading — you are allowed to disagree with the original, as long as the disagreement is interesting.</p>
<p>This is the second kind. The original moves one way and this version argues with it, and the vocal — untouched, in the same key, at a tempo it was not written for — has to carry the argument. That is the whole risk of the format. A vocal recorded to sit on top of one feeling has to sound intentional on top of a different one, and when it does not work, it does not slightly not work, it collapses.</p>
<h2>What changed</h2>
<ul>
  <li><strong>The tempo.</strong> Not dramatically, but enough that the vocal phrases land in different places against the beat.</li>
  <li><strong>The harmony.</strong> The chords underneath imply something the original did not, which shifts what several lines seem to mean without a word being altered.</li>
  <li><strong>The space.</strong> The original is dense. This is sparse for most of its length and dense exactly once.</li>
  <li><strong>The ending.</strong> The original resolves. This one does not, on purpose.</li>
</ul>
<h2>Working with someone else's take</h2>
<p>The strange thing about remixing a vocal you did not record is how much you learn about the singer. You hear every breath in isolation, every place they pushed and every place they held back, at a level of detail you never get from the finished record. By the end you know the performance better than you know most of your own.</p>
<p>It also enforces humility. You cannot ask the vocal to do anything different. Every problem has to be solved underneath it, which removes the easiest escape route in production — re-tracking until the arrangement is convenient — and leaves only the harder one, which is arranging properly.</p>
<blockquote>A remix is the only format where the hardest constraint is the part you are not allowed to touch.</blockquote>
<h2>Listen</h2>
<p>“To Kojayi (Remix)” is linked in full on the release card below, and it is in the <a href="/listen">player here</a>. The other collaboration in this stretch of the catalog is <a href="/blog/lessons-with-psydfx">“Lessons” with psydfx</a>, which was built the opposite way round — two people changing everything, rather than one person changing everything but the voice.</p>]]></content:encoded>
    </item>
    <item>
      <title>Recording vocals in a bedroom: the six things that matter</title>
      <link>https://sauvachi.com/blog/recording-vocals-in-a-bedroom</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/recording-vocals-in-a-bedroom</guid>
      <pubDate>Fri, 10 Apr 2026 12:00:00 GMT</pubDate>
      <description>Most home vocal problems are not microphone problems. What actually separates a bedroom take from a studio one — and the cheap fixes that close most of the gap.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>studio</category>
      <content:encoded><![CDATA[<p>Almost every vocal in this catalog was recorded in a room that was not built for it. That is not a hardship story — it is the normal condition for independent music now, and the results are fine, provided you are honest about which problems are worth money and which are worth attention.</p>
<p>Six things matter. In this order.</p>
<h2>1. The room, not the microphone</h2>
<p>The single biggest difference between a home vocal and a studio vocal is not the capsule, it is everything the sound hits after it leaves your mouth. A bedroom has parallel walls, a window, a wardrobe and a hard ceiling, and every one of them sends a slightly late copy of your voice back into the microphone.</p>
<p>You cannot fix that in the mix — reverb baked into a take is permanent. You can fix it with soft, thick things: a duvet on a stand behind the microphone, a wardrobe of clothes as the wall you face, a rug where the floor reflection lands. Cheap absorption in the right two places beats an expensive microphone in a bad room, every time.</p>
<h2>2. Where you stand</h2>
<p>Not in the middle of the room, and not facing a bare wall a metre away. Off-centre, facing into something soft, with distance behind you. Move two metres and re-record the same four bars — the difference is usually larger than any plugin you would reach for afterwards.</p>
<h2>3. Distance and consistency</h2>
<p>Close to the microphone gives you weight and intimacy; too close gives you plosives, proximity boom and a take that changes character every time you move your head. A hand's width is a reasonable default, with a pop filter to enforce it. The point is less the exact distance than holding it — most amateur takes are wildly inconsistent in level because the singer drifts, and no compressor fixes a performance recorded at four different distances.</p>
<h2>4. Gain staging, unglamorously</h2>
<p>Record with real headroom. Peaks around −12 to −6 dBFS are plenty; nothing is gained by pushing closer to zero, and a single clipped syllable in the best take of the night is an unrecoverable loss. Modern converters have more than enough range for you to be careful.</p>
<h2>5. Headphone monitoring you can actually sing to</h2>
<p>People sing better when they sound good to themselves. A little reverb in the monitoring path — not recorded, just in your ears — reliably produces more confident takes. Equally, if the beat is so loud you are shouting over it, you will get a strained performance and blame your voice. Turn the instrumental down.</p>
<h2>6. Takes, not fixes</h2>
<p>The most common home-recording mistake is treating editing as a substitute for performance. Tuning, timing correction and comping are all legitimate tools, but they are polish, not rescue. Four honest takes of a section beat forty repairs of one bad one, and they take less time.</p>
<p>Related: stop recording earlier than you think. Voices tire, and the take at hour three is almost never the one you keep. On <a href="/blog/again-out-now">“Again”</a> the take on the record is the first one, recorded quietly because it was late — which is a pattern I have stopped fighting.</p>
<h2>What actually needs buying</h2>
<p>In order of return on money spent: absorption (blankets count), a stand and pop filter, a decent interface, then the microphone. That order is close to the reverse of how most people buy, which is why so many home setups have a costly microphone in a hopeless room.</p>
<p>None of this is about achieving a studio sound at home. It is about removing the specific artefacts that make a recording read as amateur — room reflections, inconsistent level, strained performance — so that what is left is just the song.</p>]]></content:encoded>
    </item>
    <item>
      <title>“On My Way” — out now</title>
      <link>https://sauvachi.com/blog/on-my-way-out-now</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/on-my-way-out-now</guid>
      <pubDate>Fri, 27 Mar 2026 12:00:00 GMT</pubDate>
      <description>A track about motion that was written entirely while sitting still. On writing forward-facing songs from the middle of a flat period.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“On My Way” is out now.</strong> It is the most forward-facing thing in the catalog, and it was written during the flattest stretch of the year, which I have come to think is not a coincidence.</p>
<h2>Writing forward from a standstill</h2>
<p>There is a persistent idea that songs are reports — that you write what you are feeling as you feel it. Some are. But a lot of the most convincing music is aspirational rather than descriptive: you write the thing you are trying to talk yourself into.</p>
<p>This is that. Nothing in the weeks around it felt like momentum. The song is not lying about that, exactly; it is arguing with it. Which is why the production leans forward — a rhythm that pushes slightly ahead, a vocal that lands early rather than sitting back — while the words are considerably less certain than the arrangement is.</p>
<h2>The build</h2>
<ul>
  <li>Everything enters early. There is no long introduction to earn: the first eight bars contain most of the elements you will hear.</li>
  <li>What changes over the song is density, not material. The same parts, more of them, arranged tighter.</li>
  <li>The vocal doubles only in the last section. Held back that long, doubling reads as a lift rather than a texture.</li>
  <li>No breakdown. It was written with one and it dragged.</li>
</ul>
<h2>Tempo is a mood, not a setting</h2>
<p>The demo was slower by a noticeable margin, and every single thing wrong with it was fixed by speeding it up — which is not how it is supposed to work. Tempo gets treated as a technical parameter you settle early and leave alone, but it is closer to a key change in what it does to a song's meaning. The same words at 90 and at 100 are two different statements: one is resigned, the other is impatient.</p>
<p>The practical version of this: before you rewrite a section that is not working, try the whole track five BPM either side. It costs a minute and it solves a surprising proportion of arrangement problems that look like writing problems.</p>
<h2>Where it sits in the catalog</h2>
<p>Between the close, compressed tracks and the more open ones. If you want the version of this energy with the brakes on, <a href="/releases/autumn-leaves">“Autumn Leaves”</a> is the closest neighbour; if you want it with the brakes removed entirely, that is <a href="/releases/money-gene">“money gene”</a>.</p>
<p>It is also the track I would point a new listener at first. Not because it is the best one, but because it is the most representative — everything I tend to do is in it, and none of it is hidden behind a production choice you have to acclimatise to.</p>
<h2>Listen</h2>
<p>All the links are on the release card below, and it is in the <a href="/listen">player on this site</a>. The <a href="/releases">catalog page</a> has everything else in one place.</p>]]></content:encoded>
    </item>
    <item>
      <title>How streaming royalties actually work</title>
      <link>https://sauvachi.com/blog/how-streaming-royalties-actually-work</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/how-streaming-royalties-actually-work</guid>
      <pubDate>Fri, 13 Mar 2026 12:00:00 GMT</pubDate>
      <description>Why the per-stream number is the least useful figure in music, where the money genuinely comes from, and the payments most independent artists never collect.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>guide</category>
      <content:encoded><![CDATA[<p>Every few months a screenshot goes around showing an artist earning a disappointing amount for a large number of streams, and the conversation that follows is almost always about the wrong number.</p>
<p>Here is the structure underneath it. None of this is advice — it is the shape of the system, and you should check every detail against your own distributor and society statements, because the specifics vary by country, service and deal.</p>
<h2>There is no per-stream rate</h2>
<p>The most important thing to understand: the major services do not pay a fixed amount per play. They operate a revenue pool. Subscription and advertising income for a market is collected, a share goes to the service, and the rest is divided among rights holders according to their share of total streams in that market.</p>
<p>Which means your effective rate moves depending on things that have nothing to do with you: how many people streamed anything at all that month, what proportion of your listeners were on free tiers, which countries they were in, and what the exchange rate did. The commonly quoted figures — fractions of a cent per stream — are averages after the fact, not prices.</p>
<h2>Two different royalties, always</h2>
<p>Every stream generates money on two separate sides, and they travel by completely different routes:</p>
<ul>
  <li><strong>The recording (master) side.</strong> Paid to whoever owns the recording. If you are independent and distributing yourself, that is you, and it arrives via your distributor. This is the larger share.</li>
  <li><strong>The publishing (composition) side.</strong> Paid to the writers and publishers of the underlying song. It arrives through your performing rights organisation and a publishing administrator — <em>not</em> through your distributor.</li>
</ul>
<p>This is where most independent money goes uncollected. An artist who distributes but never registers the composition is leaving the entire publishing side sitting in a collection society's unmatched pile. It is not a large share of a small number, but it is your share of a small number, and it compounds across a catalog.</p>
<h2>What actually moves the total</h2>
<p>Given the pool model, three things matter far more than chasing a better rate:</p>
<ul>
  <li><strong>Catalog size.</strong> Income is roughly the sum of many small streams of income. Twenty releases earning modestly outperform one release earning well, and they keep earning while you sleep.</li>
  <li><strong>Repeat listening.</strong> A listener who plays a track fifty times over a year is worth vastly more than fifty listeners who play it once, and is also far more likely to buy something.</li>
  <li><strong>Everything that is not streaming.</strong> Merchandise, live, sync licensing, direct sales. For most independent artists these dwarf streaming income, and they are the reason streaming is best understood as distribution and discovery rather than as revenue.</li>
</ul>
<blockquote>Streaming is how people find the music. It is rarely how the music gets paid for.</blockquote>
<h2>The collection checklist</h2>
<p>If you do nothing else, do these:</p>
<ul>
  <li>Register every composition with your performing rights organisation, including the ones that seem too small to bother with.</li>
  <li>Get a publishing administrator collecting mechanicals internationally.</li>
  <li>Claim your artist profiles on each platform so the credits and metadata are right — mismatched metadata is a common cause of money failing to match to you.</li>
  <li>Keep your splits documented. Uncertain splits are the single most common reason payments stall.</li>
  <li>Read one statement properly, all the way through, once. It is tedious and it will teach you more than any article, this one included.</li>
</ul>
<h2>The honest framing</h2>
<p>Streaming pays badly per play and will keep doing so, because the pool is finite and the number of streams keeps rising. Treating it as a wage is a route to permanent disappointment. Treating it as the world's cheapest distribution — a way for anyone, anywhere, to hear your catalog at no cost to you — is both accurate and considerably more useful.</p>
<p>The practical response is the same either way: release more, keep your rights, collect what you are owed, and own the places your audience can reach you directly. That last one is why <a href="/blog/why-an-artist-website-still-matters">a site and a mailing list still matter</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>“Autumn Leaves” — out now</title>
      <link>https://sauvachi.com/blog/autumn-leaves-out-now</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/autumn-leaves-out-now</guid>
      <pubDate>Fri, 27 Feb 2026 12:00:00 GMT</pubDate>
      <description>The quietest thing in the catalog, and the one that took the most restraint. On writing a song that refuses to build.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“Autumn Leaves” is out now.</strong> It is the quietest record here and, by a distance, the one I rewrote most.</p>
<h2>A song that refuses to build</h2>
<p>Every instinct in modern production pushes towards escalation: add a layer, lift the chorus, double the drums, give the last section something the others did not have. Those instincts are correct most of the time, which is exactly why a song that declines to obey them is difficult to finish. You keep reaching for the lift, and every time you add it, the song gets less interesting.</p>
<p>This one ends roughly where it starts. There are four versions in the project folder with a proper climax in them and all four are worse. Eventually the discipline became the point: hold the level, let the writing carry the change, and trust the listener to stay without being shouted at.</p>
<h2>What is actually in it</h2>
<ul>
  <li>Very little. A sparse rhythmic bed, one harmonic idea, and a vocal that stays in a narrow range for almost the entire song.</li>
  <li>What movement there is comes from removal — parts leave and do not return.</li>
  <li>The reverb is short and dark rather than long and pretty; long tails would have made it sound like a ballad, which it is not.</li>
  <li>The last line is unaccompanied. Everything else exists to make that possible.</li>
</ul>
<h2>Restraint is a skill you have to practise</h2>
<p>Doing less is talked about as though it were the easy option. It is not — it is a technique, and it takes as much work as density does, just less visibly. Sparse arrangements expose everything: timing, tuning, the room, the decision to breathe where you breathed. There is nowhere for a weak part to hide, so every part has to be right.</p>
<p>Making this taught me more about mixing than anything loud ever has. When there are four elements, the relationship between them is the whole record.</p>
<p>It also changes what mistakes cost. In a dense arrangement, a slightly late note is absorbed by everything around it; here it is the only thing happening, so it reads as an error rather than as feel. Several takes were discarded for reasons that would have been completely inaudible on any other track in the catalog.</p>
<h2>The title, and what it is not about</h2>
<p>It is not a cover, and it is not really about autumn. The phrase arrived attached to the melody, the way titles usually do, and by the time I noticed it carried a hundred years of other people's associations it had already become the only possible name for it.</p>
<p>What the song is about is closer to the mechanics of that: how something ordinary and repeated — a season, a habit, a person leaving in the same way they left last time — stops being an event and becomes a schedule. Which is also why it declines to build. Schedules do not have climaxes.</p>
<h2>Listen</h2>
<p>The links are on the card below, and it is in the <a href="/listen">player</a>. If you want to hear the opposite instinct from the same catalog, <a href="/releases/money-gene">“money gene”</a> is as far the other way as this goes.</p>]]></content:encoded>
    </item>
    <item>
      <title>“Can&#39;t Complain” with Shameone — out now</title>
      <link>https://sauvachi.com/blog/cant-complain-with-shameone</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/cant-complain-with-shameone</guid>
      <pubDate>Fri, 13 Feb 2026 12:00:00 GMT</pubDate>
      <description>Two writers, one instrumental, and a title that started as a shrug. On how a collaboration finds its subject when neither person arrives with one.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“Can't Complain” with Shameone is out now.</strong> Neither of us arrived with a subject. The song found one somewhere in the middle of the second session, which is a slower way to work and, in this case, a better one.</p>
<h2>Starting with nothing to say</h2>
<p>The received wisdom is to come to a session with ideas — a concept, a hook, at least a direction. Good advice, generally. It is also how you end up with two people politely taking turns to execute two separate songs on the same beat.</p>
<p>We started from an instrumental and a phrase neither of us meant seriously. “Can't complain” is what you say when you do not want to answer the question — a deflection so ordinary that nobody hears it any more. Written down and repeated a few times, it stops being a shrug and starts sounding like something much less relaxed, which is the entire song.</p>
<h2>How two voices divide a track</h2>
<p>Most features are structural: your verse, my verse, everyone home by the third chorus. This is closer to a conversation. The sections trade faster than that, and there are places where the two vocals overlap deliberately rather than tidily handing off — which took a long time to mix, because two people talking at once is either a texture or a mess depending on decisions of a few decibels.</p>
<ul>
  <li>The lead alternates, but the ad-libs are always the other person. It keeps both voices present even when only one is singing.</li>
  <li>The hook is sung together, in unison rather than harmony — harmony made it sound like a duet, and it is not one.</li>
  <li>Neither of us gets the last word. It ends mid-exchange.</li>
</ul>
<h2>What I took from it</h2>
<p>That the useful part of a collaboration is being asked to justify things. Working alone, most decisions are made and forgotten in the same minute. With someone else in the room, every one of them briefly has to be defensible — and about a third of mine turned out not to be.</p>
<p>The other thing, less comfortable: two writers on one instrumental will always converge on the more obvious of the two available songs unless somebody actively resists it. Agreement feels like progress and often is not. The sections here that I like most are the ones where we did not agree quickly.</p>
<h2>Splits, and having the boring conversation early</h2>
<p>We agreed the writing and master splits before the second session, in a message thread, in plain language. It took about ten minutes and it is the reason this release exists rather than sitting unreleased in a folder — which is where a genuinely large number of good collaborations end up.</p>
<p>Nobody wants to have that conversation while the song is still fun. Have it anyway: the alternative is having it later, when there is money or credit attached and the friendship is doing the negotiating. There is more on how splits actually work in <a href="/blog/releasing-a-single-independently-checklist">the release checklist</a>.</p>
<p>The other collaborations in the catalog work differently again: <a href="/blog/lessons-with-psydfx">“Lessons” with psydfx</a> was two people rebuilding each other's work remotely, and <a href="/blog/the-split-with-nst">“THE SPLIT” with NST</a> is deliberately two halves that refuse to merge.</p>
<h2>Listen</h2>
<p>Every link is on the release card below, and the track is in the <a href="/listen">player here</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>From “finished” to live: what happens to a track in between</title>
      <link>https://sauvachi.com/blog/from-finished-to-live</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/from-finished-to-live</guid>
      <pubDate>Fri, 30 Jan 2026 12:00:00 GMT</pubDate>
      <description>The three weeks nobody documents — delivery, encoding, store review, pitching windows and the reasons a release can land wrong on one platform only.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>guide</category>
      <content:encoded><![CDATA[<p>A track is finished. Three weeks later it is on every platform. The gap in between is almost never described, which is why so many first releases go out with something subtly wrong that could have been caught.</p>
<p>Here is what is actually happening in that window.</p>
<h2>Week three: delivery</h2>
<p>You upload the master, the artwork and the metadata to a distributor. What they do next is convert your submission into the format the stores accept — a delivery package containing the audio, the artwork, and a large amount of structured data describing who made what.</p>
<p>Two things go wrong here more than anything else. The first is metadata: a name spelled differently from your previous releases creates a second artist profile, and untangling that afterwards is a support ticket, not an edit. The second is artwork rejection — text that reads as promotional, a logo you do not have rights to, or a resolution below requirement.</p>
<h2>Week three, immediately after: the pitching window</h2>
<p>This is the part with a hard deadline. Editorial playlist consideration on the major platforms happens through the artist-facing dashboards <em>before</em> a track is live, and once the release date passes, the opportunity is simply gone. Not reduced — gone.</p>
<p>Which is why the standard advice is to deliver three to four weeks ahead. It is not the distributor that needs the time. It is you, so that the release exists in the system early enough to be pitched, pre-saved and checked.</p>
<h2>Weeks two and one: store ingestion</h2>
<p>Each store takes the package and processes it independently. They transcode your audio into their own formats, generate artwork at a dozen sizes, run automated checks, and — at some services — put the release through review.</p>
<p>Because this is per-store, releases can and do arrive in slightly different states in different places. One platform shows the feature in the title, another in the artist field. One has the artwork, another shows a placeholder for a day. One goes live at midnight local, another at midnight in a different timezone entirely. None of that is a bug on your end; it is a dozen pipelines with different rules running the same package.</p>
<h2>The pre-release checks worth doing</h2>
<ul>
  <li><strong>Look at every store page</strong> as soon as pre-save links appear. Wrong artwork or a mis-attributed feature is fixable before release and painful after.</li>
  <li><strong>Play the preview clip.</strong> Some stores auto-select it; occasionally they pick something unrepresentative.</li>
  <li><strong>Check your artist profile</strong> is the one the release attached to, not a new empty duplicate.</li>
  <li><strong>Confirm the explicit flag</strong> matches reality in both directions.</li>
  <li><strong>Test your smart link</strong> on a phone that is not yours.</li>
</ul>
<h2>Release day itself</h2>
<p>Almost nothing happens mechanically. The stores flip the release visible on the date you specified, in each territory's local time, which is why your track can be live in one country hours before another. If something is broken at this point, the fix goes back through your distributor and takes as long as ingestion took the first time — usually a day or two, sometimes longer.</p>
<h2>Why this matters more than it sounds</h2>
<p>Every avoidable problem in this window costs the same thing: the release-week attention you only get once. A track that goes live with the wrong artwork on the biggest platform, on the one day people are actually looking, does not get a second launch.</p>
<p>The full sequence, including everything before delivery, is in <a href="/blog/releasing-a-single-independently-checklist">the independent release checklist</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>“LOST N FOUND” — out now</title>
      <link>https://sauvachi.com/blog/lost-n-found-out-now</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/lost-n-found-out-now</guid>
      <pubDate>Fri, 16 Jan 2026 12:00:00 GMT</pubDate>
      <description>Built from a folder of abandoned session files. On going back through two years of unfinished ideas and what survives the return trip.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“LOST N FOUND” is out now.</strong> Nothing in it was written for it. Every element came out of a folder of abandoned sessions, some of them two years old.</p>
<h2>The folder</h2>
<p>Everyone who makes music has one: dozens of projects that stopped somewhere between an idea and a song. Most producers treat it as a graveyard. It is closer to a warehouse — the reason those ideas stalled is usually not that they were bad, but that they arrived on a day when nothing around them was ready.</p>
<p>Going back through it is uncomfortable in a specific way. You meet a version of yourself who had a good idea and no ability to finish it, and the honest response is not embarrassment but salvage.</p>
<h2>What survives the return trip</h2>
<ul>
  <li><strong>Loops survive.</strong> Anything with a strong four-bar identity still works years later.</li>
  <li><strong>Arrangements do not.</strong> Every structural decision in those old files was wrong or irrelevant, without exception.</li>
  <li><strong>Sounds survive; processing chains do not.</strong> The source material was worth keeping, the twelve plugins on top of it were not.</li>
  <li><strong>Vocals rarely survive.</strong> A performance is tied to what the person meant at the time, and it does not transplant cleanly.</li>
</ul>
<p>So the method became: keep the four bars, throw away everything that ever happened after them, and write forward from there as if it were new. Which it effectively was.</p>
<h2>Why it is worth doing at all</h2>
<p>Because the alternative — always starting from nothing — quietly biases what you make towards whatever you are capable of in a single sitting. An old idea has no obligation to sound like the person you are this month. Half the appeal of this track is that it does not sound like the tracks around it, and the reason for that is simply that its raw material predates them.</p>
<blockquote>Unfinished ideas are not failures. They are material you have already paid for.</blockquote>
<h2>How to keep a folder worth returning to</h2>
<p>The salvage only works if the archive is navigable, and most are not. Three habits make the difference, none of them interesting:</p>
<ul>
  <li><strong>Bounce a rough audio file of every session you abandon.</strong> In two years the project may not open — plugins expire, software changes, licences lapse — but a WAV always will.</li>
  <li><strong>Name it after what it sounds like</strong>, not the date. “slow chords wrong key” is findable; “Untitled 47” is not.</li>
  <li><strong>Write one line about why you stopped.</strong> “Bored of the drums” and “could not sing it” send you back with completely different intentions.</li>
</ul>
<p>That is roughly ninety seconds of work per abandoned idea, and it is the difference between an archive and a landfill.</p>
<h2>Listen</h2>
<p>Links on the release card below, and it is in the <a href="/listen">player here</a> with everything else.</p>]]></content:encoded>
    </item>
    <item>
      <title>“HOLD UP” with Sadra — out now</title>
      <link>https://sauvachi.com/blog/hold-up-with-sadra</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/hold-up-with-sadra</guid>
      <pubDate>Fri, 19 Dec 2025 12:00:00 GMT</pubDate>
      <description>A track that survived being rebuilt three times. On knowing the difference between a song that needs more work and one that needs to be left alone.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“HOLD UP” with Sadra is out now.</strong> Three complete rebuilds separate the demo from the record — and the version that shipped is closer to the demo than to either of the two in between.</p>
<h2>Rebuilding is usually a symptom</h2>
<p>There is a specific trap in home production: when a track feels not-quite-right, the available action is always <em>more work</em>, so that is what you do. Change the drums. Re-record the vocal. Try it eight BPM faster. Each pass feels productive and the song gets steadily further from whatever made you start it.</p>
<p>What is usually wrong at that point is not the production. It is that a section is a bar too long, or the vocal is sitting in the wrong place emotionally, or you are bored of a song you have heard four hundred times and mistaking that for a fault in the song.</p>
<h2>How you tell the difference</h2>
<ul>
  <li><strong>Play it to someone who has never heard it.</strong> You will hear it through their ears for two minutes, which is worth a week of solo listening.</li>
  <li><strong>Leave it for two weeks, untouched.</strong> Problems that are real are still obvious on return; problems that were fatigue evaporate.</li>
  <li><strong>Check whether you can name the fault.</strong> “The second verse drags” is actionable. “It just needs something” means stop.</li>
  <li><strong>Keep every version.</strong> The only reason this record exists is that the original demo was still in the folder after two rebuilds had wandered off.</li>
</ul>
<h2>What the two of us actually changed</h2>
<p>In the end: the arrangement of the last third, the drum sound, and roughly four lines. That is a normal amount of work for a song. It took three months because we spent two of them doing considerably more than that and then undoing it.</p>
<p>Sadra was also the person who said, halfway through the second rebuild, that we had already made the record and were now making a different, worse one. That is the sort of thing that is very hard to say to yourself and very easy to hear from someone else — the same argument for collaboration as in <a href="/blog/cant-complain-with-shameone">“Can't Complain”</a>.</p>
<h2>The version-keeping habit</h2>
<p>Save a dated copy at every point the track is in a state you would be willing to release. Not at every save — at every <em>coherent</em> state. It costs disk space, which is free, and it buys you the ability to be wrong for a month without permanent consequences.</p>
<p>Almost nobody does this, and the reason is psychological rather than technical: keeping an old version feels like an admission that the work you are about to do might make things worse. It might. That is exactly why you keep it. Three of the tracks in this catalog exist because a superseded bounce was still sitting in the folder when we came to our senses.</p>
<h2>Listen</h2>
<p>All links on the release card below, plus the <a href="/listen">player on this site</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>What belongs in a press kit (and what quietly ruins one)</title>
      <link>https://sauvachi.com/blog/what-belongs-in-a-press-kit</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/what-belongs-in-a-press-kit</guid>
      <pubDate>Fri, 05 Dec 2025 12:00:00 GMT</pubDate>
      <description>Promoters, journalists and playlist curators all want the same six things in the first ten seconds. What to include, what to leave out, and how to make it findable.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>guide</category>
      <content:encoded><![CDATA[<p>A press kit is not a marketing document. It is a convenience for busy people who have already decided to take you seriously enough to look you up, and whose next decision depends on how long it takes to find what they need.</p>
<p>Assume ten seconds of patience. Design accordingly.</p>
<h2>The six things everyone needs</h2>
<ul>
  <li><strong>A one-line description.</strong> Who you are and what you sound like, in a sentence someone could paste into a listing without editing.</li>
  <li><strong>A bio in three lengths</strong> — roughly 50, 150 and 400 words. Different outlets need different sizes and none of them want to cut yours down.</li>
  <li><strong>Photos that can actually be printed.</strong> High resolution, at least one horizontal and one vertical, with the photographer's credit attached.</li>
  <li><strong>Music, playable immediately.</strong> A link that plays without an account. If a curator has to sign up for something to hear you, you have lost.</li>
  <li><strong>Contact.</strong> A working email address, on the page. Not a form, not a DM request.</li>
  <li><strong>The factual block</strong> — release dates, label or self-released, territory, and the exact spelling of every name involved.</li>
</ul>
<h2>What quietly ruins it</h2>
<ul>
  <li><strong>A download that is 400 MB of raw photos.</strong> Nobody is downloading that on a deadline.</li>
  <li><strong>A bio written in the third person about your “journey”.</strong> Describe the music. Three specifics beat a paragraph of adjectives.</li>
  <li><strong>Comparisons to enormous artists.</strong> They read as a claim rather than a description, and everyone discounts them automatically.</li>
  <li><strong>Unlabelled photos.</strong> If a publication cannot tell who took the picture, they cannot legally run it.</li>
  <li><strong>Numbers with no context.</strong> A stream count is only persuasive if it is genuinely persuasive.</li>
  <li><strong>A press kit that is out of date.</strong> A kit whose newest release is two years old says more than the kit intends to.</li>
</ul>
<h2>The format question</h2>
<p>A PDF is still the most portable option — it opens everywhere, prints, and can be attached to an email. A web page is easier to keep current and easier to link. The pragmatic answer is both: a page that is always right, and a PDF generated from it for people who want a file.</p>
<p>Whichever you pick, the important part is that it is <em>one</em> link you can send without preamble, and that it lives on a domain you control. This site keeps its press kit reachable from every page's header for exactly that reason, alongside the argument for <a href="/blog/why-an-artist-website-still-matters">owning the address in the first place</a>.</p>
<h2>The test</h2>
<p>Send it to a friend who does not work in music and ask them to find your email address, your newest release, and a printable photo. Time them. If it takes longer than a minute, the problem is not that they were slow.</p>]]></content:encoded>
    </item>
    <item>
      <title>“CARBON” — out now</title>
      <link>https://sauvachi.com/blog/carbon-out-now</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/carbon-out-now</guid>
      <pubDate>Fri, 21 Nov 2025 12:00:00 GMT</pubDate>
      <description>The densest, most compressed thing in the catalog. On making a track that is deliberately claustrophobic, and why the loudest record is rarely the biggest one.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>release</category>
      <content:encoded><![CDATA[<p><strong>“CARBON” is out now.</strong> It is the most compressed record in the catalog, in both senses — technically, and in the amount of space anything is allowed.</p>
<h2>Claustrophobia as a production choice</h2>
<p>Most mixing advice is about creating space: carve room for each element, keep the low end tidy, let the vocal breathe. Good advice. This track ignores nearly all of it on purpose.</p>
<p>Everything sits in the same narrow band. The vocal is pushed hard against the instrumental rather than floated above it. There is almost no stereo width, so the whole thing arrives from one place, close in. It is a deliberately uncomfortable listen for two and a half minutes, and it would be unbearable at four.</p>
<h2>Loud is not big</h2>
<p>The counter-intuitive part, which took me years to internalise: heavily compressed music does not sound powerful, it sounds <em>tense</em>. Power comes from contrast — the loud part is loud because the thing before it was not. Remove the dynamic range and you remove the mechanism that makes impact possible.</p>
<p>So the trick with a track like this is to spend that tension rather than just maintaining it. There is exactly one moment where everything opens, and the entire arrangement exists to make that moment land. Play it after something spacious like <a href="/releases/autumn-leaves">“Autumn Leaves”</a> and the effect roughly doubles.</p>
<h2>Notes</h2>
<ul>
  <li>Mixed almost entirely at low volume. Anything that survives being quiet will survive being loud; the reverse is not true.</li>
  <li>No reverb on the lead vocal at all — only a very short room, which reads as tightness rather than as an effect.</li>
  <li>The master is deliberately not as loud as it could be. Pushed further, the one open moment stopped opening.</li>
</ul>
<h2>Short on purpose</h2>
<p>Two and a half minutes is not a concession to attention spans, whatever the current argument about song lengths says. It is a structural requirement. A track built on sustained tension has a natural expiry: past a certain point the listener's ear adapts, the discomfort stops registering, and what was claustrophobic becomes merely loud.</p>
<p>You can hear where that line is if you loop the thing for ten minutes. Somewhere around the third pass it stops working entirely. Ending before that happens is not editing for the sake of brevity — it is the only way the idea survives being played twice.</p>
<h2>What I would do differently</h2>
<p>Very little, which is unusual. The one thing: the vocal could sit a decibel further back in the second half. It is mixed at the level that felt right while I was making it, and making it involved hearing the words several hundred more times than any listener will. That is a bias worth naming, because it recurs — the person who wrote the lyric always mixes it slightly too loud.</p>
<h2>Listen</h2>
<p>Links on the release card below, and it is in the <a href="/listen">player here</a>. Headphones, ideally, and once through without doing anything else.</p>]]></content:encoded>
    </item>
    <item>
      <title>Mixing on headphones without ruining the record</title>
      <link>https://sauvachi.com/blog/mixing-on-headphones</link>
      <guid isPermaLink="true">https://sauvachi.com/blog/mixing-on-headphones</guid>
      <pubDate>Fri, 07 Nov 2025 12:00:00 GMT</pubDate>
      <description>Most independent music is mixed on headphones now. The three failure modes that produces, and the checks that catch each one before release.</description>
      <dc:creator>sauvachi</dc:creator>
      <category>studio</category>
      <content:encoded><![CDATA[<p>Almost everyone reading this mixes on headphones, at least some of the time, because almost nobody has a treated room. That is workable — a great deal of released music is mixed this way — provided you know precisely what headphones lie about.</p>
<h2>Failure mode one: the low end</h2>
<p>Headphones deliver bass directly to your ears with none of the cancellation a room introduces, which usually means you hear <em>more</em> low end than a listener will on speakers — so you under-provide it — while simultaneously being unable to hear whether a sub note is actually in tune or in time.</p>
<p>The checks:</p>
<ul>
  <li>Reference against two or three commercial tracks you know intimately, matched for loudness. Trust the comparison, not your ears in isolation.</li>
  <li>Check on something small — a laptop, a phone speaker. If the track collapses into nothing, your bass is carrying too much of the arrangement's weight.</li>
  <li>Look at the low end, do not only listen: a spectrum analyser will show you a build-up your headphones flatter.</li>
</ul>
<h2>Failure mode two: width and reverb</h2>
<p>Headphones exaggerate stereo dramatically, because each ear hears only its own channel. Wide sounds spectacular on headphones and can nearly vanish on a phone. Reverb behaves similarly: the tail you carefully placed can be inaudible in a car, or turn to soup in a room.</p>
<ul>
  <li>Check the whole mix in mono, regularly. Anything that disappears was phase, not width.</li>
  <li>Keep the important elements — lead vocal, kick, bass, snare — centred and dry enough to survive mono.</li>
  <li>Judge reverb amounts at low volume. Quiet listening is where too much reverb is most obvious.</li>
</ul>
<h2>Failure mode three: your own fatigue</h2>
<p>Headphones are exhausting in a way speakers are not, and tired ears reliably reach for more brightness and more level. Two hours in, you are no longer mixing, you are gradually turning everything up.</p>
<ul>
  <li>Mix quietly. Genuinely quietly — quieter than feels satisfying.</li>
  <li>Take breaks on a fixed schedule rather than when you notice fatigue, because by then it has been affecting decisions for a while.</li>
  <li>Make the final call the next morning. Every mix sounds different at 9am, and 9am is right.</li>
</ul>
<h2>What actually helps</h2>
<p>In order: knowing your headphones well (one familiar pair beats three unfamiliar ones), referencing against known records, checking in mono and on a phone, and mixing at low volume. Correction software that flattens your specific model's response is genuinely useful and cheap; a second pair of expensive headphones is much less so.</p>
<p>None of this makes headphones equivalent to a treated room. It makes their specific distortions predictable, and a predictable distortion is one you can mix through. The rest is the same discipline as <a href="/blog/recording-vocals-in-a-bedroom">recording in an untreated room</a>: fix what is cheap to fix, learn what the rest is doing to you, and stop pretending the problem is gear.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
