<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Caleb McElroy</title>
    <description>The latest articles on DEV Community by Caleb McElroy (@calebmcelroy).</description>
    <link>https://dev.to/calebmcelroy</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1314266%2F4d0d8a4c-1bb7-4db4-a160-c8df3f4d6675.jpeg</url>
      <title>DEV Community: Caleb McElroy</title>
      <link>https://dev.to/calebmcelroy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/calebmcelroy"/>
    <language>en</language>
    <item>
      <title>Unpack X32 X-LIVE SD Card Recordings into Individual Tracks</title>
      <dc:creator>Caleb McElroy</dc:creator>
      <pubDate>Wed, 25 Sep 2024 12:09:37 +0000</pubDate>
      <link>https://dev.to/calebmcelroy/unpack-x32-x-live-sd-card-recordings-into-individual-tracks-4006</link>
      <guid>https://dev.to/calebmcelroy/unpack-x32-x-live-sd-card-recordings-into-individual-tracks-4006</guid>
      <description>&lt;p&gt;&lt;a href="https://www.pexels.com/photo/tilt-shift-photo-of-acoustic-drum-set-995301/" rel="noopener noreferrer"&gt;Cover Photo by Josh Sorenson&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you're someone who has recorded on the Behringer X32 X-LIVE to an SD Card, you’ve probably ran into that they are 32-channel WAV files broken up into 4 GB files. So you end up with a bunch of separate 32-channel files, which is difficult to manage. Drew Brashler has a &lt;a href="https://drewbrashler.com/2017/behringer-x-live-file-handling/" rel="noopener noreferrer"&gt;good article&lt;/a&gt; explaining why that format is necessary. At my church we use this every week so extracting and seaming together these tracks for editing can be time-consuming.&lt;/p&gt;

&lt;p&gt;That’s why I built a tool called wav-extract. This tool simplifies the process, taking multi-channel WAV files from your X32 X-LIVE recordings and unpacking them into individual mono or stereo tracks. In this guide, I’ll walk you through how to use it. This article will be geared towards Mac because that's what I'm using but Windows is also supported.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Install
&lt;/h2&gt;

&lt;p&gt;Install the tool using the instructions on this page: &lt;a href="https://github.com/calebmcelroy/wav-extract?tab=readme-ov-file#installation" rel="noopener noreferrer"&gt;github.com/calebmcelroy/wav-extract&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Open you're &lt;strong&gt;Terminal&lt;/strong&gt; app. And copy and paste the command that matches the type of mac you have. If you have a mac with M-series CPU use the Apple Silicon command.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;macOS (Apple Silicon):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;curl &lt;span class="nt"&gt;-L&lt;/span&gt; &lt;span class="nt"&gt;-o&lt;/span&gt; /usr/local/bin/wav-extract https://raw.githubusercontent.com/calebmcelroy/wav-extract/master/bin/darwin/arm64/wav-extract &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;sudo chmod&lt;/span&gt; +x /usr/local/bin/wav-extract
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;macOS (Intel):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;curl &lt;span class="nt"&gt;-L&lt;/span&gt; &lt;span class="nt"&gt;-o&lt;/span&gt; /usr/local/bin/wav-extract https://raw.githubusercontent.com/calebmcelroy/wav-extract/master/bin/darwin/amd64/wav-extract &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;sudo chmod&lt;/span&gt; +x /usr/local/bin/wav-extract
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvunrcevtg1t3sd7fa90t.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvunrcevtg1t3sd7fa90t.png" alt="wav-extract download screenshot"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Windows:&lt;/strong&gt;&lt;br&gt;
If you're on windows follow these instructions: &lt;a href="https://github.com/calebmcelroy/wav-extract?tab=readme-ov-file#windows-1" rel="noopener noreferrer"&gt;github.com/calebmcelroy/wav-extract?tab=readme-ov-file#windows-1&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 2: Verify Install
&lt;/h2&gt;

&lt;p&gt;Within your &lt;strong&gt;Terminal&lt;/strong&gt; app run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;wav-extract
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see this output.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo9xtmt26ap6f84id3kmj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo9xtmt26ap6f84id3kmj.png" alt="wav-extract verify install screenshot"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Yay! You successfully installed it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: How to Use
&lt;/h2&gt;

&lt;p&gt;Here's some examples of commands to run in your &lt;strong&gt;Terminal&lt;/strong&gt; app run. I'll example each one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;u&gt;Tip:&lt;/u&gt;&lt;/strong&gt; if you copy a folder in finder on mac you can paste the path into the &lt;strong&gt;Terminal&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fuoc58wo5qjo6zn61wug9.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fuoc58wo5qjo6zn61wug9.gif" alt="copy and paste folder into terminal"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Export all channels as mono:&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;wav-extract --in /path/to/x-live-session --out /path/to/output&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Export all channels and extract certain tracks as stereo:&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;wav-extract --in /path/to/x-live-session --out /path/to/output --stereo "1/2,5/6"&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The &lt;code&gt;--stereo&lt;/code&gt; parameter accepts comma-separated pairs, with the number before the slash representing the left channel and the number after the slash representing the right channel.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Export only certain channels:&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;wav-extract --in /path/to/x-live-session --out /path/to/output --channels "1/2,3"&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The --channels parameter allows you to specify either stereo pairs or mono channels to extract. Only these channels will be extracted. For stereo pairs, use two numbers separated by a slash like "1/2", where the first number is the left channel and the second is the right channel. Mono channels are specified by a single number like "3". You can separate multiple channels with commas, such as "1/2,3/4,5,6".&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Running:&lt;/em&gt;&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F70dsi184kpb1hiymsl9j.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F70dsi184kpb1hiymsl9j.jpg" alt="wav-extract command running screenshot"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Output:&lt;/em&gt;&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fw0xe0kp8lj9aq7rutgos.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fw0xe0kp8lj9aq7rutgos.png" alt="wav-extract output folder screenshot"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Feedback &amp;amp; Contribution
&lt;/h2&gt;

&lt;p&gt;This tool is open source and continuously evolving. If you run into any issues, feel free to open an issue on GitHub or contribute to the project. I’m always open to feedback and suggestions for improving the tool! If this helps you, shoot me a comment. I'd love to hear from you.&lt;/p&gt;

&lt;p&gt;I built this tool to save time and make the X32 recording process easier for myself and others. I hope it helps you as much as it has helped me! Let me know if you have any questions or ideas for improvement. Happy mixing!&lt;/p&gt;

&lt;p&gt;GitHub Link:&lt;br&gt;
&lt;a href="https://github.com/calebmcelroy/wav-extract" rel="noopener noreferrer"&gt;github.com/calebmcelroy/wav-extract&lt;/a&gt;&lt;/p&gt;

</description>
      <category>go</category>
      <category>opensource</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
