i must have been blind. now i can find it on the listed publications.
sorry for the noise.
m.
Am 25.02.2012 um 19:59 schrieb Miller Puckette:
It's on http://crca.ucsd.edu/~msp/Publications/icmc98.ps ..
the exact URL doesn't appear on the Pd vanilla help file for bonk~, which
just points to my
Shall i remove the reference to the paper mentioned in the bonk~ helpfile or
does it still exist somewhere?
m.
Am 15.02.2012 um 05:59 schrieb Miller Puckette:
.. one small comment - the 'minvel' message might not be functioning in
recent versions - I have to check this.
cheers
Miller
It's on http://crca.ucsd.edu/~msp/Publications/icmc98.ps ..
the exact URL doesn't appear on the Pd vanilla help file for bonk~, which
just points to my home page.
cheers
Miller
On Mon, Feb 20, 2012 at 04:26:16PM +0100, Max wrote:
Shall i remove the reference to the paper mentioned in the bonk~
Hi Joe,
When you're searching for a good minvel setting, you should watch
the 2nd number in the list from bonk's right outlet. Then play a few
sample notes on the instrument you're trying to track to get a sense
of typical velocities.
The threshold setting is a little less intuitive. To find
.. one small comment - the 'minvel' message might not be functioning in
recent versions - I have to check this.
cheers
Miller
On Tue, Feb 14, 2012 at 11:47:49PM -0500, William Brent wrote:
Hi Joe,
When you're searching for a good minvel setting, you should watch
the 2nd number in the list
Another small comment: there's a missing [list-drip] in the patch I
just posted. Here's the right one :)
On Tue, Feb 14, 2012 at 11:59 PM, Miller Puckette m...@ucsd.edu wrote:
.. one small comment - the 'minvel' message might not be functioning in
recent versions - I have to check this.
Le 2012-02-08 à 03:14:00, Max a écrit :
additionally i was wondering why bonk~ detects different amounts of
attacks when fed with the same soundfile at each time.
Because your hop size is bigger than your block size ?
Then your beginning of soundfile happens at one of the block boundaries
So do I understand right that, when you simply type bonk~ into an object
box without arguments, you're getting the error messages?
Also, I'm wondering how your old patches can't find the bonk~ object at
all. Could you try this patch:
#N canvas 0 0 448 298 10;
#X obj 97 65 bonk~;
and see what
An object is not in a red dashed contour in my patches and your patch
creates a bonk objected.
Previous situation was rain of bangs no matter what threshold (or
other) parameter I set. An old file objects work from now on. I opened
a patch retyped object name [bonk~] with no change and wrote to
It's a measure of brightness -- the balancing point of the loudness distribution
over the filterbang (nominally 11 filters).
cheers
Miller
On Mon, Jan 11, 2010 at 08:41:04PM -0800, Jonathan Wilkes wrote:
The current help patch for [bonk~] says the output from the right outlet
is the
Sounds like some argument that was allowed in the old version no longer
works in the new one... Could you post the text of the bonk object so I
can check it?
thanks
Miller
On Thu, Jan 14, 2010 at 07:09:50PM +0200, Gintaras Lau. wrote:
Hello,
I'm a pd Vanilla user and since I upgraded to
11 matches
Mail list logo
