Re: [music-dsp] Recognizing Frequency Components

>>As a first main question, seeming a bit overly boring: how do we determine, >>or measure, >>the frequency of this component, and as accurate as possible or to a certain >>good enough >>error bound, the initial phase and amplitude ? "EVALUATION OF A STANDARDIZED SINE WAVE FIT ALGORITHM"; Pete

Re: [music-dsp] Recognizing Frequency Components

As things change hands, or go through multiple layers of translation and sanitation, sometimes < becomes < and then gets stripped by the next thing. Might try something like this hehe: < Let's be honest, the web is a mess :P On Thu, Jan 26, 2017 at 2:38 PM, Bjorn Roche wrote: > > > On Thu,

Re: [music-dsp] Recognizing Frequency Components

On Thu, Jan 26, 2017 at 2:40 PM, Martin Klang wrote: > try putting < instead of less-than. > That's exactly what I did last time. My impression is that Blogger doesn't have a canonical data representation. > On 26/01/17 19:28, Bjorn Roche wrote: > > On Thu, Jan 26, 2017 at 2:09 PM, Alan Wolfe

Re: [music-dsp] Recognizing Frequency Components

try putting < instead of less-than. Martin On 26/01/17 19:28, Bjorn Roche wrote: > On Thu, Jan 26, 2017 at 2:09 PM, Alan Wolfe > wrote: > > It's some HTML filtering happening somewhere between (or > including) his machine and yours. > > > It's Blogger. I've

Re: [music-dsp] Recognizing Frequency Components

On Thu, Jan 26, 2017 at 2:09 PM, Alan Wolfe wrote: > It's some HTML filtering happening somewhere between (or including) his > machine and yours. > > It's Blogger. I've fixed this before and apparently it comes back :(. I think Google's more or less abandoned Blogger. I'd switch to something else

Re: [music-dsp] Recognizing Frequency Components

It's some HTML filtering happening somewhere between (or including) his machine and yours. The less than of the for loop is being seen as the start of an HTML tag, or just possibly part of the start of an HTML tag and being stripped away. A common problem when providing code snippets on the web v

Re: [music-dsp] Recognizing Frequency Components

Original Message Subject: Re: [music-dsp] Recognizing Frequency Components From: "Bjorn Roche" Date: Thu, January 26, 2017 10:57 am To: "A discussion list for music-related DSP" -

Re: [music-dsp] Recognizing Frequency Components

Original Message Subject: Re: [music-dsp] Recognizing Frequency Components From: "Evan Balster" Date: Thu, January 26, 2017 12:36 pm To: music-dsp@music.columbia.edu --

Re: [music-dsp] Recognizing Frequency Components

I wrote a blog post a while ago about how to use FFT to find the pitch of an instrument. As I mention in the post, this is hardly the best way, but I think it's suitable for many applications. For example, you could write a perfectly serviceable guitar tuner with this. The post links to code and i

Re: [music-dsp] Recognizing Frequency Components

Philosophy rant: Frequency is a model. You can use tools that build on that model to describe your signal in terms of frequency, but none of them are going to be perfect. A pure 10hz tone is a mathematical abstraction which you'll not find in any digital signal or measurable phenomenon. But, *oo

Re: [music-dsp] Recognizing Frequency Components

At that length, you can count zero-crossings. But that’s not a valid answer, I’d assume. But I found a nice paper on determining frequencies with FFTs using a gaussian window. Pretty accurate results. Best, Steffan > On 26.01.2017|KW4, at 15:24, Theo Verelst wrote: > > Say the sample le

[music-dsp] Recognizing Frequency Components

Hello DSP list It's one of those subjects that interest me, even though there are lots of solutions around, some partial, some inaccurate, some elaborate, etc etc. Suppose it's given that we have a properly sampled sound file of 1 (one) sinusoidal component of frequency above 20Hz and at leas