<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Use Examples on ebyte.org</title>
    <link>https://ebyte.org/tags/use-examples/</link>
    <description>Recent content in Use Examples on ebyte.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ebyte.org/tags/use-examples/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EByte Use Example Checking a Folder of Recordings in a Shell Script</title>
      <link>https://ebyte.org/ebyte-use-example-checking-a-folder-of-recordings-in-a-shell-script/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ebyte.org/ebyte-use-example-checking-a-folder-of-recordings-in-a-shell-script/</guid>
      <description>&lt;p&gt;Most of the time nobody opens a binary file by hand. Files arrive from devices, uploads and exports, and something has to decide which ones are fine before anything else reads them. EByte&amp;rsquo;s exit codes and one-line diagnostics are built for that job, so this example puts the released &lt;code&gt;ebyte&lt;/code&gt; 0.1.1 binary in a short shell loop over a folder of audio recordings.&lt;/p&gt;&#xA;&lt;p&gt;The folder holds seven &lt;code&gt;.wav&lt;/code&gt; files of the kind a small sensor setup might collect overnight. Four are good recordings made with Python&amp;rsquo;s &lt;code&gt;wave&lt;/code&gt; module, at three different sample rates, one of them stereo. The other three are the usual trouble. One upload was cut off at 5,000 bytes, one file is a text log someone saved with a &lt;code&gt;.wav&lt;/code&gt; name, and one has four extra bytes after the audio where a recorder started writing a metadata chunk.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
