<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Matt Culpin on Medium]]></title>
        <description><![CDATA[Stories by Matt Culpin on Medium]]></description>
        <link>https://medium.com/@Matt_Culpin?source=rss-2006546015bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*mMPzOAZSISKIvkPE0lhT_w.jpeg</url>
            <title>Stories by Matt Culpin on Medium</title>
            <link>https://medium.com/@Matt_Culpin?source=rss-2006546015bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:54:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Matt_Culpin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sample accurate, latency free MIDI.]]></title>
            <link>https://medium.com/@Matt_Culpin/sample-accurate-latency-free-midi-1d114f6d3ba?source=rss-2006546015bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d114f6d3ba</guid>
            <category><![CDATA[recording-studios]]></category>
            <category><![CDATA[midi]]></category>
            <category><![CDATA[synthesizers]]></category>
            <dc:creator><![CDATA[Matt Culpin]]></dc:creator>
            <pubDate>Tue, 07 Feb 2023 11:15:12 GMT</pubDate>
            <atom:updated>2023-02-07T11:15:12.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DuGD1IF5azaioz1359zeCg.jpeg" /></figure><p>When USB ports started appearing on modern electronic instruments such as synthesizers and drum machines in the late ’90s, I thought it would herald a new era for connecting devices with a protocol better than MIDI, with it not having seen any changes for over twenty years (now forty).</p><p>Alas, MIDI over USB became the norm. Without a deep technical understanding of how this all worked, I assumed that connecting all of my hardware via USB would reduce latency within my setup as via a USB hub; I could connect from my computer directly to each piece of hardware, rather than the daisy chain way of connecting multiple MIDI devices. I had tried the iConnectivity mio range of USB to MIDI interfaces and even used the CAT5 Ethernet connectivity without any real improvements in latency.</p><p>Using plugins within a DAW (Live/Logic etc.) and hardware over MIDI or MIDI over USB introduces latency, which is essentially an audible delay between what the DAW is playing internally and what is being sent over MIDI, then monitored. In addition, most audio interfaces include monitoring incoming audio signals rather than routing them back through the DAW, which would create even more latency. However, as my hardware setup grew, having anything more than a few hardware synths playing with anything running inside a DAW as a plugin would create unacceptable amounts of latency; often, I would need to record the audio to have it play in time. When writing, this can disrupt the flow of creativity.</p><p>With my modular setup, I had been using the ADAT and DC Coupled outputs on my UA Apollo interfaces to send sample-accurate signals to my Eurorack gear; this used a combination of the Expert Sleepers ES-3 hardware, their Silent Way plugins and the CV Tools available in Ableton Live. This way of connecting everything improved the latency to my modular gear and anything else that had a CV/Gate input. Anything polyphonic was still using MIDI over USB. I tried the Expert Sleepers USAMO, a box that also used a DC-coupled output to convert a sample-accurate audio signal to MIDI, also reliant on a plugin for a DAW. This proved quite tricky to set up, and as the UA Apollo interfaces weren’t cited as thoroughly tested and compatible, I gave up on this solution.</p><p>Within the Expert Sleeper’s range of hardware, the ES-40 SPDIF interface is pretty handy. I’d already started using this to hook up the UA Apollo’s SPDIF digital interfaces to get audio back from my modular and to also send 8 Gate/Trigger signals back to my module via the ESX-8GT, useful for drum triggering or sending a clock signal to a Eurorack sequencer, using two of the EMedium BlogS-40s expansion headers. I also noticed that Expert Sleepers have the ESX-8MD modules; these can also be added to the expansion headers of the ES-40, and using the Silent Way ES-4 controller plugin, you address up to 8 MIDI ports. I purchased two of these to add to the spare ES-40 expansion headers.</p><p>I now have all of my hardware synths being triggered via MIDI via the Expert Sleepers solution, a real game changer for me as I now have zero timing issues between my DAW and hardware.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d114f6d3ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lockdown studio prep]]></title>
            <link>https://medium.com/@Matt_Culpin/lockdown-studio-prep-6bb1fcc82f87?source=rss-2006546015bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bb1fcc82f87</guid>
            <category><![CDATA[mixing-and-mastering]]></category>
            <category><![CDATA[recording]]></category>
            <dc:creator><![CDATA[Matt Culpin]]></dc:creator>
            <pubDate>Tue, 26 May 2020 11:02:25 GMT</pubDate>
            <atom:updated>2020-05-27T06:40:33.605Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lockdown Studio Prep</h3><p>I’ve had my studio space for a little over two years now. During that time, I’ve mixed a dozen or so tracks with varying degrees of satisfaction. Mixing is always my Achilles heel and the process I’m most critical of as I don’t particularly enjoy the process, it just feels like admin once the fun creative process has finished. I can see why bands and even producers hand the mixing stage over to high in demand mixers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ppOMXk-x5CbwB-AEoZj2Xw.png" /><figcaption>Sonarworks Reference 4 Screenshot</figcaption></figure><p>My preferred way has been to rely on feedback during the mastering process; the engineer I use would typically recommend things for me to fix. However, these were likely to be things that prevented him from doing the best job he could with the mastering. Translating my mixes across different devices has always caused me the most grief.</p><p>As with most home producers, the idea of a forced lockdown offered up the prospect of increased productivity, even if it was just the two or so hours back each day from not having to commute. I had several tracks pending completion, so I reached out to my mastering guy to book his time. Bad news, he was at home with no plans to go into his studio space to work until the lockdown was over.</p><p>Of course, I could have patiently waited with a bunch of unmastered tracks; however, the prospect of having to revisit songs to tweak them didn’t particularly thrill me, I prefer things to be finished and forgotten about, a clean break as it were.</p><p>I started to look at the various mastering tools, also getting recommendations from fellow producers. Ozone 9 from iZotope seemed to get the most thumbs up from people, so I took the plunge via Splice.com who offer a monthly rent-to-own scheme which is pretty handy.</p><p>To start with, I compared an old pre-mastered track with one that my usual goto engineer had done. Ozone 9 did a pretty good job with levels using its AI-based analysis, but I still wasn’t happy with how it was translating to other listening devices. The bass sounded boxy, and I remember getting detailed feedback from my engineer when he had been initially mastering this track, asking me to boost quite a chunk of the bottom end which in my studio sounded way too much. I started to get a little disheartened by my DIY approach and thought I might have made an unwise investment.</p><p>After a few days of watching a ton of videos and reading lots of articles, I came across a product called Sonarworks Reference 4. This product promised to analyse my space and compensate with an EQ curve that would aim to flatten out the frequency response of my room. Reference 4 includes both a software and hardware element in the form of a Microphone. The software takes you through the process of room calibration and takes around 20 mins and involves standing in precise locations dictated to by the onscreen instructions. The method uses a kind of echolocation by pinging noises between each speaker which it interprets in a 3D space. The software then generates an EQ curve for use within a VST/Plugin for your DAW as well as a calibrated output device for your computer to use system-wide.</p><p>The results so far have left my new tracks sounding a little drab, but that’s a good thing! After a few EQ tweaks to get them sounding decent in my room, the translation of these tracks to other listening devices is now much more consistent. I’ve also now been using Ozone 9 to master old tracks which when compared with the professionally mastered versions sound pretty good. So a forced investment of £300-£400 has now left me the serious prospect of not using a mastering engineer again (sorry Justin). I’ve also found new confidence in the whole mixing/mastering process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bb1fcc82f87" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>