diff examples/puredata/xtract/xtract-help.pd @ 98:ca40a0dc29d6

Removed fftw_plan from xtraction functions. Created new init function xtract_init_fft() for creating plans, which have global scope. Updated examples to reflect the change. New configure option: --with-fft_optimisation (0 = FFTW_ESTIMATE, 1 = FFTW_MEASURE, 2 = FFTW_PATIENT).
author Jamie Bullock <jamie@postlude.co.uk>
date Sat, 06 Oct 2007 16:36:00 +0000
parents 1222cd753029
children
line wrap: on
line diff
--- a/examples/puredata/xtract/xtract-help.pd	Thu Oct 04 14:29:30 2007 +0000
+++ b/examples/puredata/xtract/xtract-help.pd	Sat Oct 06 16:36:00 2007 +0000
@@ -6,34 +6,37 @@
 \, for a full explanation of the library and the functions it provides.
 Only the operation of the PD external will be explained here along
 with a few use case scenarios.;
+#X obj 27 299 xtract~;
+#X msg 27 270 help;
+#X text 27 328 Other than this help message \, the data sent to the
+left inlet should always be a 'signal' (i.e. audio rate). This is the
+data from a which a given feature will be extracted.;
+#X obj 183 520 xtract~ mean;
+#X floatatom 133 616 10 0 0 0 - - -;
+#X floatatom 254 553 5 0 0 0 - - -;
+#X msg 183 552 list \$1;
+#X obj 133 586 xtract~ variance;
+#X obj 182 496 phasor~ 0.1;
+#X text 40 671 Below are some possible use cases (click to open):;
+#X text 27 382 The outlet may be a scalar (control rate) \, or a vector
+(audio rate) \, depending on the nature of the feature that is being
+extracted.;
+#X obj 43 695 f0;
+#X obj 84 695 mfcc;
+#X text 28 435 Any additional arguments that need to be passed to the
+feature extraction function must be provided as a list to the right
+inlet \, e.g.;
+#X text 24 231 A complete list of features may be obtained by sending
+the external a |help( message:;
 #X text 20 148 [xtract~] must always be called with one argument \,
 in the following form: [xtract~ <feature>] \, where <feature> is a
-feature supported by the LibXtract library. A complete list of features
-may be obtained by sending the external a |help( message:;
-#X obj 27 262 xtract~;
-#X msg 27 233 help;
-#X text 26 298 Other than this help message \, the data sent to the
-left inlet should always be a 'signal' (i.e. audio rate). This is the
-data from a which a given feature will be extracted.;
-#X obj 182 490 xtract~ mean;
-#X floatatom 132 586 10 0 0 0 - - -;
-#X floatatom 253 523 5 0 0 0 - - -;
-#X msg 182 522 list \$1;
-#X obj 132 556 xtract~ variance;
-#X obj 181 466 phasor~ 0.1;
-#X text 39 641 Below are some possible use cases (click to open):;
-#X text 26 352 The outlet may be a scalar (control rate) \, or a vector
-(audio rate) \, depending on the nature of the feature that is being
-extracted.;
-#X obj 42 665 f0;
-#X obj 83 665 mfcc;
-#X text 27 405 Any additional arguments that need to be passed to the
-feature extraction function must be provided as a list to the right
-inlet \, e.g.;
-#X connect 5 0 4 0;
-#X connect 7 0 9 0;
-#X connect 7 0 10 0;
-#X connect 10 0 11 1;
-#X connect 11 0 8 0;
-#X connect 12 0 7 0;
-#X connect 12 0 11 0;
+feature supported by the LibXtract library.;
+#X text 21 198 An optional second argument can be used to explicitly
+set the blocksize for FFT-based features;
+#X connect 4 0 3 0;
+#X connect 6 0 8 0;
+#X connect 6 0 9 0;
+#X connect 9 0 10 1;
+#X connect 10 0 7 0;
+#X connect 11 0 6 0;
+#X connect 11 0 10 0;