<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Classifying audio files in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Classifying-audio-files/m-p/599124#M80263</link>
    <description>&lt;P&gt;&lt;A href="https://community.jmp.com/t5/Uncharted/Working-with-WAV-files/ba-p/29469" target="_self"&gt;This blog entry&lt;/A&gt; &lt;EM&gt;might&lt;/EM&gt; get you started.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Feb 2023 16:01:27 GMT</pubDate>
    <dc:creator>Jed_Campbell</dc:creator>
    <dc:date>2023-02-09T16:01:27Z</dc:date>
    <item>
      <title>Classifying audio files</title>
      <link>https://community.jmp.com/t5/Discussions/Classifying-audio-files/m-p/599057#M80257</link>
      <description>&lt;P&gt;Is there a way to process raw audio files with or without metadata? Having a microphone installed to detect noise is a cheap way to protect equipment and personnel from damage. However, it would be much more efficient if the sound is classified (as being false alarm, object loose etc). Can a model be trained in JMP for that purpose?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jun 2023 16:37:39 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Classifying-audio-files/m-p/599057#M80257</guid>
      <dc:creator>Sop</dc:creator>
      <dc:date>2023-06-08T16:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: Classifying audio files</title>
      <link>https://community.jmp.com/t5/Discussions/Classifying-audio-files/m-p/599124#M80263</link>
      <description>&lt;P&gt;&lt;A href="https://community.jmp.com/t5/Uncharted/Working-with-WAV-files/ba-p/29469" target="_self"&gt;This blog entry&lt;/A&gt; &lt;EM&gt;might&lt;/EM&gt; get you started.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 16:01:27 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Classifying-audio-files/m-p/599124#M80263</guid>
      <dc:creator>Jed_Campbell</dc:creator>
      <dc:date>2023-02-09T16:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: Classifying audio files</title>
      <link>https://community.jmp.com/t5/Discussions/Classifying-audio-files/m-p/599151#M80265</link>
      <description>&lt;P&gt;or &lt;LI-MESSAGE title="FFT and DTMF" uid="28974" url="https://community.jmp.com/t5/Uncharted/FFT-and-DTMF/m-p/28974#U28974" discussion_style_icon_css="lia-mention-container-editor-message lia-img-icon-blog-thread lia-fa-icon lia-fa-blog lia-fa-thread lia-fa"&gt;&lt;/LI-MESSAGE&gt;&amp;nbsp; which is close to what you describe. So is &lt;LI-MESSAGE title="FFT Video" uid="21017" url="https://community.jmp.com/t5/Uncharted/FFT-Video/m-p/21017#U21017" discussion_style_icon_css="lia-mention-container-editor-message lia-img-icon-blog-thread lia-fa-icon lia-fa-blog lia-fa-thread lia-fa"&gt;&lt;/LI-MESSAGE&gt; .&lt;/P&gt;
&lt;P&gt;Are you opening a file or looking at a never-ending stream, maybe over a socket connection?&lt;/P&gt;
&lt;P&gt;I've been through several iterations on wav files with JMP; it is a complicated format. If you constrain the wav file input to 44.1kHz stereo, for example, you can simplify some things. You might even get away with skipping several hundred bytes and treating the rest of the file as samples. You could also use Python to read the samples and pass them back to JMP.&lt;/P&gt;
&lt;P&gt;I've never gotten serious about training models, but I imagine using the FFT to move the signal from time domain to frequency domain would be a good first step. The FFT lets you think about the frequencies that were present during a time slice.&lt;/P&gt;
&lt;P&gt;Sounds like a fun project, be great to hear more about it!&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 16:36:41 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Classifying-audio-files/m-p/599151#M80265</guid>
      <dc:creator>Craige_Hales</dc:creator>
      <dc:date>2023-02-09T16:36:41Z</dc:date>
    </item>
  </channel>
</rss>

