Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Hello Monks!

I'm new to this forum and I need your help.

I've been in to perl for quite a while now but I'm especially interested in sound. Now to combine these two things, I want to start a little project, which I would like to introduce to you. And this is what it's about:

A FULL SPECTRUM ANALYZER for recorded sound and existing audio files (but mainly first). If you have no idea what I'm talking about http://en.m.wikipedia.org/wiki/Spectrum_analyzer .. just to get an idea. It's pretty impressive actually. And here is how I'd like to do it:

1 First get a sound input from our microphone. 2 Then analys the recorded data. We are supposedly going to have an array of numbers. A byte array. 3 Now we want this sound in a 'frequency domain' (not a time domain! ) So we need to transform our byte array to a frequency domain 4 and then in the end visualise it.

So this is just a brief overview of what the script is going to be doing. Hopefully! :)

If anyone has got an idea to any of these 4 points I'd be very glad to hear! Sadly perl is very poor concerning sound in general. So all help is very welcome. I'll probably be working on this for quite some time and if you guys are interested I'll be posting my process on the forum!

Cheers Rob C

PG8b5W4ebGA51

In reply to SPECTRUM ANALYZER in Perl by robcatow

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (2)
As of 2024-04-20 05:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found