Hi , im sonyfing some data converting it to waveforms that im using as waveshapers. I was wondering how could i organize those waveshapers . how can i analyze a waveform to extract features that can be used for selecting each waveshaper or for organizing them?
Are there are any approaches for something like this?
thanks
R
A good place to start would be to detect zero-crossing. I believe
rjlib has some simple zero crossing detectors. Then you can use some
of the variable feature extraction libs to get stuff like pitch, and
"pitchiness vs. noisiness". Otherwise, I think you'll need to expand
your explanation of what oyu are looking for.
.hc
On Oct 16, 2010, at 12:12 AM, ronni montoya wrote:
Hi , im sonyfing some data converting it to waveforms that im using as waveshapers. I was wondering how could i organize those waveshapers . how can i analyze a waveform to extract features that can be used for selecting each waveshaper or for organizing them?
Are there are any approaches for something like this?
thanks
R
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
As we enjoy great advantages from inventions of others, we should be
glad of an opportunity to serve others by any invention of ours; and
this we should do freely and generously. - Benjamin Franklin
You could also try to analyse the spectrum produced by a default signal like a phasor or osc. For harmonic generation, highest order harmonic and other things.
Am 25.10.2010 19:44, schrieb Hans-Christoph Steiner:
A good place to start would be to detect zero-crossing. I believe rjlib has some simple zero crossing detectors. Then you can use some of the variable feature extraction libs to get stuff like pitch, and "pitchiness vs. noisiness". Otherwise, I think you'll need to expand your explanation of what oyu are looking for.
.hc
On Oct 16, 2010, at 12:12 AM, ronni montoya wrote:
Hi , im sonyfing some data converting it to waveforms that im using as waveshapers. I was wondering how could i organize those waveshapers . how can i analyze a waveform to extract features that can be used for selecting each waveshaper or for organizing them?
Are there are any approaches for something like this?
thanks
R
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Mon, 25 Oct 2010, Hans-Christoph Steiner wrote:
A good place to start would be to detect zero-crossing.
a zero crossing detector is much the same as [>~] followed by [rzero~ 1]. Therefore, first it does a destruction on the signal as harsh as the harshest fuzz with the highest possible gain. This removes most timbral features of the signal and boosts some others by the maximum possible amount, in a way that isn't perceptual at all (e.g. it's very DC-sensitive, among other things).
I don't know why anyone recommends zero-crossing detection. But if it's after some kind of [rzero~ 1], that already makes more sense, but that detects the positive and negative peaks instead. If you use [hip~] before [>~] instead, it will pick something intermediate to those.
| Mathieu Bouchard ------------------------------ Villeray, Montréal, QC
On Oct 25, 2010, at 2:24 PM, Mathieu Bouchard wrote:
On Mon, 25 Oct 2010, Hans-Christoph Steiner wrote:
A good place to start would be to detect zero-crossing.
a zero crossing detector is much the same as [>~] followed by
[rzero~ 1]. Therefore, first it does a destruction on the signal as
harsh as the harshest fuzz with the highest possible gain. This
removes most timbral features of the signal and boosts some others
by the maximum possible amount, in a way that isn't perceptual at
all (e.g. it's very DC-sensitive, among other things).I don't know why anyone recommends zero-crossing detection. But if
it's after some kind of [rzero~ 1], that already makes more sense,
but that detects the positive and negative peaks instead. If you use
[hip~] before [>~] instead, it will pick something intermediate to
those.
zero-crossing detection is the basis of cheap pitch detection, and it
also useful for automatically find cut points in samples so that there
aren't clicks.
.hc
"It is convenient to imagine a power beyond us because that means we
don't have to examine our own lives.", from "The Idols of
Environmentalism", by Curtis White
On Mon, 25 Oct 2010, Hans-Christoph Steiner wrote:
zero-crossing detection is the basis of cheap pitch detection,
Yeah, but cheap like that is not worth buying into.
and it also useful for automatically find cut points in samples so that there aren't clicks.
Right... instead, the worst it can get is a click-like artefact of a different order, which is very much quieter, without any bass in it, and usually not very noticeable (but there are exceptions). It's that the waveforms have non-matching angles at the junctions. This is the kind of problem there is with stretching high frequency signals using [tabread4~], for example, whereas [tabread4c~] is fine.
In math words we'd say « zero-crossing splicing produces a C0 curve, but doesn't try to produce a C1 curve, and almost never does ».
| Mathieu Bouchard ------------------------------ Villeray, Montréal, QC
-
- -
Hans-Christoph Steiner -
Mathieu Bouchard -
ronni montoya