[chuck-users] stupid n00bie question: Part III
algomantra at gmail.com
Tue Oct 16 10:37:05 EDT 2007
Joerg, I'll try your method in a week or so, when I have gone past the basic
Kassen...I had to install the latest version 22.214.171.124 to find that tracking
I never realised when that came up! Your various points are very insightful,
but obviously I tried the simplest looking option - the last. I just had to
add a line to
make it work:
<<< Tracking.the_freq >>>;
I am presuming this would be the frequency in Hertz? The mic seems quite
sensitive, I get a
reading of around 64.6 from the ambient noise, mostly traffic from the
nearby road. Hmm....
That's on the wish-list, Ge said it depends on garbage collection because of
Perry commented a while back that woodChucKs might be protected as well so
would further complicate matters. Obviously it won't be useful at all until
we have trees
which are generally a form of lists and we don't have lists (yet?).
Yesterday afternoon I was just sitting at my new office/studio, and in my
out Chuck versus PD, both of which I know very little. I was wondering which
invest time with to get fast results for my current experiment. Then from
sauntered in the sound of three kids playing cricket....the fat kid was
of the skinny boys.....
"That was a Chuck!"
For a moment, I thought it was an Omen.
(PS: In cricket, "chucking" is when you do not complete the circular
action while bowling, or bend your elbow weirdly. Its a form of cheating.)
1/f ))) --.
On 10/16/07, Kassen <signal.automatique at gmail.com> wrote:
> On 10/16/07, AlgoMantra <algomantra at gmail.com> wrote:
> > 1. What is the simplest way to detect the pitch
> > of an audio signal (from the mic) in Chuck?
> To add to Joerg's sugestion;
> Tracking zero crossings is a viable option, it gets used in a fair amount
> of hardware but due to it's limitations it tends to work best on simple
> signals and such hardware tends to be aimed at specific instruments (say
> bass guitar) because it helps if you can make a good guess what range the
> ouput should be in. Typically I'd only use zero-crossing for sub-octave
> Another option is a phase-locked loop which comes down to synthesising a
> sine, comparing it to the signal to be analysed, look at the difference in
> phase, then tweak the sine until this difference becomes as small as
> possible. It has some of the same weaknesses but should be more accurate
> most of the time, it's less simple.
> It kinda depends in what way you want it to be simple; FFT analysis is not
> at all simple on a fundamental level but it's simplified considerably if Ge
> & Rebecca do all of the hard stuff for you :¬). Have a look at
> /chuck126.96.36.199/examples/analysis/tracking/tracking.ck (I think that's your
> 2. How much wood could a woodChucK ChucK
> > if a woodchucK could chucK wood?
> That's on the wish-list, Ge said it depends on garbage collection because
> of the splinters. Perry commented a while back that woodChucKs might be
> protected as well so that would further complicate matters. Obviously it
> won't be useful at all until we have trees which are generally a form of
> lists and we don't have lists (yet?).
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chuck-users