<rss version="2.0">
  <channel>
    <title>Polgar</title>
    <link>https://polgar.uk</link>
    <description>Polgar - Noiselog</description>
    <generator>Zine -- https://zine-ssg.io</generator>
    <language>en-GB</language>
    <lastBuildDate>Thu, 16 Apr 2026 22:57:46 +0000</lastBuildDate>
    
      
        <item>
          <title>Tracking tracks
</title>
          <description>&lt;div id=&quot;2025-12-01T06:01:00&quot;&gt;&lt;h2&gt;&lt;a class=&quot;&quot; href=&quot;#2025-12-01T06:01:00&quot;&gt;Tracking tracks&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;The songwriting is going swimmingly. We’re writing — and recording via my template — a song each session. But one of our ideas is something we want to finish properly before we start tracking our debut EP. So while we plan to keep our songwriting routine going, we’re going to try and record Zombie Space.&lt;/p&gt;&lt;p&gt;I’m really quite excited — it’ll be good to release something of ours into the aether while we continue to hone what we want our first EP to be. It’s also a great chance to test how well a Reaper project can transition from my songwriting template into a more &lt;em&gt;“tracking friendly”&lt;/em&gt; state.&lt;/p&gt;&lt;p&gt;The first technique I’m using is dedicated tracking tracks — which sounds like silly wordplay but actually makes complete sense. For each instrument, whether it’s beatboxing, vocals, guitar, or even a MIDI keyboard part, I create a separate track where all new takes are recorded. Once we’re happy with that performance, the recorded or comped item gets moved somewhere more logical, freeing up the tracking track for the next idea from that instrument. It keeps the project organised and makes it quick to set up the right monitoring FX for a perfect take, whether that’s a hint of reverb or just rolling off the subs.&lt;/p&gt;&lt;p&gt;Having a dedicated track for tracking also makes it easier to set levels for monitoring mixes. I used to (in moments of haste) just duplicate tracks and rename them, but this new method is cleaner, faster, and far more intentional.&lt;/p&gt;&lt;p&gt;– Chris&lt;/p&gt;&lt;/div&gt;</description>
          <link>https://polgar.uk/noiselog/#2025-12-01T06:01:00</link>
          <pubDate>Mon, 01 Dec 2025 06:01:00 +0000</pubDate>
          <guid>https://polgar.uk/noiselog/#2025-12-01T06:01:00</guid>
        </item>
      
        <item>
          <title>Beatboxing mics
</title>
          <description>&lt;div id=&quot;2025-11-29T16:54:00&quot;&gt;&lt;h2&gt;&lt;a class=&quot;&quot; href=&quot;#2025-11-29T16:54:00&quot;&gt;Beatboxing mics&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Before we started our songwriting session today, Mike and I tried out a few different ways of recording his beatboxing. There are plenty more microphones I want to test, but in our whole collection it seems the humble SM58 handles it best — somehow sounding better than the fancier options.&lt;/p&gt;&lt;p&gt;To be clear, it’s not perfect. The low-end isn’t as full as we’d like, and it doesn’t capture every tiny detail, but it delivers a punch that nothing else managed. And for beatboxing, those natural percussive transients are the holy grail. After all, more bass can always be added later with triggered parallel pitch-shifting or layered synths.&lt;/p&gt;&lt;p&gt;So while we’re writing, Mike is just using the same setup we use for live shows with the loop-station. I simply track the main outputs and match the tempo in Reaper.&lt;/p&gt;&lt;p&gt;– Chris&lt;/p&gt;&lt;/div&gt;</description>
          <link>https://polgar.uk/noiselog/#2025-11-29T16:54:00</link>
          <pubDate>Sat, 29 Nov 2025 16:54:00 +0000</pubDate>
          <guid>https://polgar.uk/noiselog/#2025-11-29T16:54:00</guid>
        </item>
      
        <item>
          <title>Gotta’ get that toan
</title>
          <description>&lt;div id=&quot;2025-11-28T19:08:00&quot;&gt;&lt;h2&gt;&lt;a class=&quot;&quot; href=&quot;#2025-11-28T19:08:00&quot;&gt;Gotta’ get that toan&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;For this songwriting Reaper template, instead of firing up the old Voxes, I’m using my two favourite amp-sim plugins: IK Multimedia’s &lt;a href=&quot;https://www.ikmultimedia.com/products/amplitube5/&quot; target=&quot;_blank&quot;&gt;AmpliTube&lt;/a&gt; and Native Instruments’ &lt;a href=&quot;https://www.native-instruments.com/en/products/komplete/guitar/guitar-rig-7-pro/&quot; target=&quot;_blank&quot;&gt;Guitar Rig&lt;/a&gt;. AmpliTube offers a downright delicious recreation of the AC30, and Guitar Rig comes loaded with gloriously odd presets for ambient, textural, and effect-driven sounds.&lt;/p&gt;&lt;p&gt;There are a couple of little tricks I use to make these digital tools feel more natural while I’m playing through them. First, I always drop a modelled compressor between the power amp and the speaker sim. I usually reach for some flavour of 1176 when I want that funky, snappy bite, and a Vari-Mu (a tube compressor) when I’m after &lt;em&gt;“moar toan”&lt;/em&gt;. That’s a huge part of what a valve power amp does: warmly squeezing the signal into something that breathes.&lt;/p&gt;&lt;p&gt;The other trick — easily my most overused move in my entire plugin toolbelt — is sticking a good saturation plugin on the guitar bus. Usually FabFilter &lt;a href=&quot;https://www.fabfilter.com/products/saturn-2-multiband-distortion-saturation-plug-in&quot; target=&quot;_blank&quot;&gt;Saturn&lt;/a&gt;, because it just works.&lt;/p&gt;&lt;p&gt;All of this is purely for the feel of the instrument. I care very little about the supposed “authenticity” of a guitar tone, especially given that guitarists tend to be the only people who notice.&lt;/p&gt;&lt;p&gt;– Chris&lt;/p&gt;&lt;/div&gt;</description>
          <link>https://polgar.uk/noiselog/#2025-11-28T19:08:00</link>
          <pubDate>Fri, 28 Nov 2025 19:08:00 +0000</pubDate>
          <guid>https://polgar.uk/noiselog/#2025-11-28T19:08:00</guid>
        </item>
      
        <item>
          <title>Write space
</title>
          <description>&lt;div id=&quot;2025-11-27T21:06:00&quot;&gt;&lt;h2&gt;&lt;a class=&quot;&quot; href=&quot;#2025-11-27T21:06:00&quot;&gt;Write space&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;How can I create the best environment for us to write music?&lt;/p&gt;&lt;p&gt;Recently, the three of us have been on a proper songwriting streak. It’s been so productive that we’ve shelved all our other plans and thrown ourselves into making our first EP. Step one is simple: write more songs for it. We already have a healthy pile of individual ideas and half-finished pieces, but while we’re in this creative gear, it feels right to carve out time for fresh material that sounds like &lt;em&gt;“Polgar.”&lt;/em&gt;&lt;/p&gt;&lt;p&gt;I want to catch as much of that new music as possible the moment it sparks. To help with that, I’ve started building a template in Reaper. Plenty of producers swear by templates in their DAW (Digital Audio Workstation), but I’ve never been the biggest fan. There’s something romantic about opening a blank project with no blueprint and no expectations. Still, once multiple people are involved and momentum is precious, a bit of structure goes a long way.&lt;/p&gt;&lt;p&gt;So now I’m retraining my &lt;em&gt;“blank page”&lt;/em&gt; instincts. The template isn’t a cage; it’s more like staff lines to write on, or graph paper that lets you draw freely without losing the thread.&lt;/p&gt;&lt;p&gt;– Chris&lt;/p&gt;&lt;/div&gt;</description>
          <link>https://polgar.uk/noiselog/#2025-11-27T21:06:00</link>
          <pubDate>Thu, 27 Nov 2025 21:06:00 +0000</pubDate>
          <guid>https://polgar.uk/noiselog/#2025-11-27T21:06:00</guid>
        </item>
      
        <item>
          <title>Sitemap
</title>
          <description>&lt;div id=&quot;2025-11-26T09:17:00&quot;&gt;&lt;h2&gt;&lt;a class=&quot;&quot; href=&quot;#2025-11-26T09:17:00&quot;&gt;Sitemap&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Is it necessary to create a &lt;code&gt;sitemap.xml&lt;/code&gt; file for a static site in 2025? Probably not, but if we want to be good internet citizens, we should conform to all the things the little robots crave. This site already has a &lt;code&gt;robots.txt&lt;/code&gt;, so that box is ticked.&lt;/p&gt;&lt;p&gt;Creating a sitemap is easy once your site is online. There are websites and tools that iterate through all your pages — dynamic or static — and forge a perfectly serviceable file. But it took me far too long to find an offline, static-site sitemap generator, so I’m building my own.&lt;/p&gt;&lt;p&gt;The goal is that each time I deploy the site, &lt;a href=&quot;https://polgar.uk/blog/first-post/&quot;&gt;Zine&lt;/a&gt; will do its thing and generate the public folder, then my sitemap tool will scan it and create an up-to-date &lt;code&gt;sitemap.xml&lt;/code&gt;. Should be fairly simple to implement (famous last words).&lt;/p&gt;&lt;p&gt;I’m writing it in &lt;a href=&quot;https://ziglang.org/&quot; target=&quot;_blank&quot;&gt;Zig&lt;/a&gt;, of course. It makes sense to use the same toolchain as Zine, and I’m rather fond of the language. I’m naming it &lt;a href=&quot;https://github.com/sonro/pathwright&quot; target=&quot;_blank&quot;&gt;Pathwright&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;– Chris&lt;/p&gt;&lt;/div&gt;</description>
          <link>https://polgar.uk/noiselog/#2025-11-26T09:17:00</link>
          <pubDate>Wed, 26 Nov 2025 09:17:00 +0000</pubDate>
          <guid>https://polgar.uk/noiselog/#2025-11-26T09:17:00</guid>
        </item>
      
        <item>
          <title>Pick a colour
</title>
          <description>&lt;div id=&quot;2025-11-25T10:09:43&quot;&gt;&lt;h2&gt;&lt;a class=&quot;&quot; href=&quot;#2025-11-25T10:09:43&quot;&gt;Pick a colour&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Any new artist needs a recognisable art style, and it certainly helps to stay consistent across photos, logos, videos, fonts – even the way you write. These things can evolve, of course. Traditionally (since the 60s), bands have tied changes in their visual identity to album cycles. I’m not convinced the &lt;em&gt;“album”&lt;/em&gt; should be the milestone musicians organise themselves around anymore, but that’s a conversation for another day.&lt;/p&gt;&lt;p&gt;Once you’ve settled on a colour you like, building a palette around it has never been easier. You don’t need a degree in colour theory to open up &lt;a href=&quot;https://coolors.co/&quot; target=&quot;_blank&quot;&gt;coolors.co&lt;/a&gt; or &lt;a href=&quot;https://www.color-hex.com/&quot; target=&quot;_blank&quot;&gt;color-hex.com&lt;/a&gt; and happily experiment until something fits your aesthetic.&lt;/p&gt;&lt;p&gt;It didn’t take us long to land on the red we wanted. A mix of French New Wave posters, Tarantino’s stylised grit, and some striking Queen’s Gambit fan art nudged us towards the rather seductive &lt;strong&gt;&lt;span class=&quot;polgar-red &quot;&gt;#c60420&lt;/span&gt;&lt;/strong&gt;.&lt;/p&gt;&lt;p&gt;– Chris&lt;/p&gt;&lt;/div&gt;</description>
          <link>https://polgar.uk/noiselog/#2025-11-25T10:09:43</link>
          <pubDate>Tue, 25 Nov 2025 10:09:43 +0000</pubDate>
          <guid>https://polgar.uk/noiselog/#2025-11-25T10:09:43</guid>
        </item>
      
        <item>
          <title>Hello, World!
</title>
          <description>&lt;div id=&quot;2025-11-24T16:19:00&quot;&gt;&lt;h2&gt;&lt;a class=&quot;&quot; href=&quot;#2025-11-24T16:19:00&quot;&gt;Hello, World!&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;What the hell is a noiselog?&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;It’s like a devlog. So what’s a devlog?  &lt;em&gt;“A devlog is a blog or diary that updates an audience on the development progress of a project, typically a video game, website, or app.”&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://en.wiktionary.org/wiki/devlog&quot; target=&quot;_blank&quot;&gt;Wiktionary&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;&lt;strong&gt;Why do this?&lt;/strong&gt; I like microblogging, nerding out about music, coding, audio tech, and how musicians work behind the scenes. The more in-depth stuff will probably end up in the &lt;a href=&quot;https://polgar.uk/blog/&quot;&gt;blog&lt;/a&gt;. Also, with this outlet, I can avoid nerding out on social media… too much.&lt;/p&gt;&lt;p&gt;– Chris&lt;/p&gt;&lt;/div&gt;</description>
          <link>https://polgar.uk/noiselog/#2025-11-24T16:19:00</link>
          <pubDate>Mon, 24 Nov 2025 16:19:00 +0000</pubDate>
          <guid>https://polgar.uk/noiselog/#2025-11-24T16:19:00</guid>
        </item>
      
    
  </channel>
</rss>
