Forums > MaxMSP

Fiddle~ of a buffer~ ?

March 8, 2007 | 11:01 pm

Dear all, I’m looking for a solution to find out the pitch of a buffer~ (dividing it in "windows").
It would be something like fiddle~ or pitch~ but that works with a buffer~ instead of audio streaming.

Regards

Bruno

————————————————-
- http://www.brunozamborlin.com -
————————————————-


March 8, 2007 | 11:36 pm

Quote: Bruno Zamborlin wrote on Thu, 08 March 2007 16:01
—————————————————-
> Dear all, I’m looking for a solution to find out the pitch of a buffer~ (dividing it in "windows").
> It would be something like fiddle~ or pitch~ but that works with a buffer~ instead of audio streaming.
>
> Regards
>
> Bruno

just play the buffer = use "realtime" for your "offline" process.

thats how most programs work.

if you are impatient, play it at x4 speed …


March 9, 2007 | 11:27 am

Quote: Roman Thilenius wrote on Fri, 09 March 2007 00:36
—————————————————-
> just play the buffer = use "realtime" for your "offline" process.
> thats how most programs work.
> if you are impatient, play it at x4 speed …
—————————————————-

Thank you Roman for your attention.
Anyway, using this solution I’ve found some little troubles.

See that:

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P comment 22 61 90 9109513 1 – load an audiofile;
#B color 6;
#P comment 348 387 182 9109513 3 – see that anytime , results are different;
#B color 6;
#P message 282 358 33 9109513 clear;
#P newex 373 135 58 9109513 t 0 0 clear;
#B color 6;
#P button 373 65 15 6;
#P newex 210 340 51 9109513 pack 0 0.;
#N counter;
#X flags 0 0;
#P newobj 210 303 66 9109513 counter;
#N coll results;
#P newobj 282 385 65 9109513 coll results;
#P newex 210 274 87 9109513 t b f;
#P newex 174 224 46 9109513 sel -96.;
#P message 23 345 27 9109513 stop;
#P message 23 328 67 9109513 startwindow;
#P newex 97 375 29 9109513 dac~;
#P user gain~ 97 246 21 89 158 0 1.071519 7.94321 10.;
#P flonum 210 250 67 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 175 129 33 9109513 sig~ 1;
#P newex 174 199 126 9109513 loudness~ 250. 250. 250.;
#P newex 174 163 70 9109513 groove~ sound;
#P message 118 61 43 9109513 replace;
#P newex 118 90 67 9109513 buffer~ sound;
#P comment 389 65 98 9109513 2 – click to fill the coll;
#B color 6;
#P connect 5 0 3 0;
#P connect 7 0 8 0;
#P fasten 7 0 8 1 102 361 121 361;
#P fasten 3 0 7 0 179 189 102 189;
#P connect 3 0 4 0;
#P fasten 17 0 3 0 378 158 179 158;
#P lcolor 7;
#P connect 2 0 1 0;
#P connect 18 0 13 0;
#P fasten 17 2 13 0 426 379 287 379;
#P lcolor 7;
#P fasten 15 0 13 0 215 382 287 382;
#P connect 16 0 17 0;
#P lcolor 7;
#P fasten 12 1 15 1 292 335 256 335;
#P fasten 17 1 14 2 402 297 243 297;
#P lcolor 7;
#P connect 12 0 14 0;
#P connect 6 0 12 0;
#P connect 11 1 6 0;
#P connect 14 0 15 0;
#P connect 4 0 11 0;
#P fasten 10 0 8 0 28 364 102 364;
#P fasten 9 0 8 0 28 366 102 366;
#P window clipboard copycount 21;

Bruno

————————————————-
- http://www.brunozamborlin.com -
————————————————-


March 11, 2007 | 7:34 pm

Nobody?

:-D


March 14, 2007 | 10:45 am

Bruno Zamborlin schrieb:
> Anyway, using this solution I’ve found some little troubles.

This is to be expected, but should make no difference for your
interpretation of it. loudness~ is a fft process and thus will give you
values across fft frames. Where those start is arbitrary, could be
anywhere…
The size of a fft frame is about 23 ms and would give you 1024 different
results…
But the overal shape should remain the same…

Stefan

Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


Viewing 5 posts - 1 through 5 (of 5 total)