<?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"><channel><title><![CDATA[Roy Merchant]]></title><description><![CDATA[Mix engineer / Music production / mentorship / Tutor]]></description><link>https://www.roymerchant.com/blog</link><generator>RSS for Node</generator><lastBuildDate>Thu, 16 Jul 2026 18:12:00 GMT</lastBuildDate><atom:link href="https://www.roymerchant.com/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Prepping for a mix session: Bars, Bit rate, and Knowing What to Print]]></title><description><![CDATA[The mix starts before any mixer opens the session, it starts with how the session was prepped. I've had files arrive in beautifully organised folders that take hours to untangle, and I've had "messy" sessions that took me ten minutes to get up and running. The difference is never tidiness. It's whether the person bouncing the tracks understands what a mixer actually needs. Here's the short version: export everything from bar 1, export both wet and dry (separate folders), and don't strip out...]]></description><link>https://www.roymerchant.com/post/prepping-for-a-mix-session-bars-bit-rate-and-knowing-what-to-print</link><guid isPermaLink="false">6a58e7ce38e05b9fea35b5a7</guid><pubDate>Thu, 16 Jul 2026 14:18:48 GMT</pubDate><dc:creator>Roy Merchant</dc:creator></item></channel></rss>