Version 1.3.2 is now out in the wild. Includes source, project files, and

binaries for Pd-linux, Max-Win32 (4 and 5), and Max-OSX (4 and 5).

New version fixes stability issues on Max5 (Win32).

disis_munger~ (a.k.a. munger1~) is a flext port of munger~ granulator from

the Percolate library with additional features and enhancements.

http://ico.bukvic.net/Max/disis_munger~_latest.zip

Director, DISIS Interactive Sound & Intermedia Studio

Version 1.3.2 is now out in the wild. Includes source, project files, and
binaries for Pd-linux, Max-Win32 (4 and 5), and Max-OSX (4 and 5).

disis_munger~ (a.k.a. munger1~) is a flext port of munger~ granulator from
the Percolate library with additional features and enhancements.

Download from:
http://ico.bukvic.net/Max/disis_munger~_latest.zip

Ivica Ico Bukvic, D.M.A.
Composition, Music Technology
Director, DISIS Interactive Sound & Intermedia Studio
Assistant Co-Director, CCTAD
CHCI, CS, and Art (by courtesy)
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-6139
(540) 231-5034 (fax)
ico@vt.edu
http://www.music.vt.edu/faculty/bukvic/

ann-disis_munger-1-3-2-released

In the osx folder, the exernal is called "disis.munger~.mxo" and must be called "disis_munger~.mxo".

In the osx folder, the exernal is called "disis.munger~.mxo" and must be called "disis_munger~.mxo".
Otherwise it's great ! Thanks.


Oops, you're right. I just uploaded new version that fixes this.

> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com]

> Sent: Tuesday, January 27, 2009 2:50 PM

> Subject: [maxmsp] Re: [ANN] disis_munger~ 1.3.2 released

> In the osx folder, the exernal is called "disis.munger~.mxo" and must be

> -----Original Message-----
> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com]
> On Behalf Of Bertrand Fraysse
> Sent: Tuesday, January 27, 2009 2:50 PM
> Subject: [maxmsp] Re: [ANN] disis_munger~ 1.3.2 released
>
>
> In the osx folder, the exernal is called "disis.munger~.mxo" and must be
> called "disis_munger~.mxo".
> Otherwise it's great ! Thanks.


should the object in the help patcher (max4)

Am 28.01.2009 um 04:59 schrieb Ivica Ico Bukvic:

> Oops, you're right. I just uploaded new version that fixes this.

>> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com 

>> Sent: Tuesday, January 27, 2009 2:50 PM

>> Subject: [maxmsp] Re: [ANN] disis_munger~ 1.3.2 released

>> In the osx folder, the exernal is called "disis.munger~.mxo" and 

should the object in the help patcher (max4)
say:

> Oops, you're right. I just uploaded new version that fixes this.
>
> Best wishes,
>
> Ico
>
>> -----Original Message-----
>> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com 
>> ]
>> On Behalf Of Bertrand Fraysse
>> Sent: Tuesday, January 27, 2009 2:50 PM
>> Subject: [maxmsp] Re: [ANN] disis_munger~ 1.3.2 released
>>
>>
>> In the osx folder, the exernal is called "disis.munger~.mxo" and  
>> must be
>> called "disis_munger~.mxo".
>> Otherwise it's great ! Thanks.
>


I'm experiencing some "frustratingly silent mungers". That is, I can't seem to get any sound out of it, with any of the presets?

I'm on Max/MSP/jitter 5.05, OSX 10.5.6, Macbook Pro 2,4 ghz core2duo. There are no error messages in the Max window.

I'm experiencing some "frustratingly silent mungers". That is, I can't seem to get any sound out of it, with any of the presets? 

I'm on Max/MSP/jitter 5.05, OSX 10.5.6, Macbook Pro 2,4 ghz core2duo. There are no error messages in the Max window.


I was wondering, if munger~ is a multichannel granulator,

what does it do when you play it in a 2-channel environment?

Does it spread channels 1-4 evenly across the left side

I was wondering, if munger~ is a multichannel granulator,
what does it do when you play it in a 2-channel environment?
Does it spread channels 1-4 evenly across the left side
of the panning space?


The input stream is mono, the output on the disis_munger~ I think is

hardcoded to 64 channels. The spread is controlled through its parameters.

> Sent: Thursday, January 29, 2009 2:15 PM

> I was wondering, if munger~ is a multichannel granulator,

> what does it do when you play it in a 2-channel environment?

> Does it spread channels 1-4 evenly across the left side

The input stream is mono, the output on the disis_munger~ I think is
hardcoded to 64 channels. The spread is controlled through its parameters.
See help file for more info.

> -----Original Message-----
> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com]
> On Behalf Of Anthony Palomba
> Sent: Thursday, January 29, 2009 2:15 PM
> Subject: [maxmsp] Re: [ANN] disis_munger~ 1.3.2 released
>
>
> I was wondering, if munger~ is a multichannel granulator,
> what does it do when you play it in a 2-channel environment?
> Does it spread channels 1-4 evenly across the left side
> of the panning space?


Not really, the only panning option I see is "descretepan" but 

there is nothing that specifies how these eight channels are

panned. For example how do I tell munger I want a particular 

Not really, the only panning option I see is "descretepan" but 
there is nothing that specifies how these eight channels are
panned. For example how do I tell munger I want a particular 
grain to output on channel 2? 


It appears that flext externals compiled against Max5 SDK do not work on

Max4 (not sure if this is flext- or MaxSDK-related). For this reason, the

zip file now includes explicit versions of disis_munger~ for Max4 (both OSX

and Win32). Hope this fixes your problem.

> Sent: Wednesday, January 28, 2009 6:20 PM

> I'm experiencing some "frustratingly silent mungers". That is, I can't

> seem to get any sound out of it, with any of the presets?

> I'm on Max/MSP/jitter 5.05, OSX 10.5.6, Macbook Pro 2,4 ghz core2duo.

> There are no error messages in the Max window.

It appears that flext externals compiled against Max5 SDK do not work on
Max4 (not sure if this is flext- or MaxSDK-related). For this reason, the
zip file now includes explicit versions of disis_munger~ for Max4 (both OSX
and Win32). Hope this fixes your problem.

> -----Original Message-----
> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com]
> On Behalf Of Lut Lei
> Sent: Wednesday, January 28, 2009 6:20 PM
> Subject: [maxmsp] Re: [ANN] disis_munger~ 1.3.2 released
>
>
> I'm experiencing some "frustratingly silent mungers". That is, I can't
> seem to get any sound out of it, with any of the presets?
>
> I'm on Max/MSP/jitter 5.05, OSX 10.5.6, Macbook Pro 2,4 ghz core2duo.
> There are no error messages in the Max window.


Look at the "spatialize" option found in the bottom-right corner of the help

patch. It gives you per-channel resolution.

> Sent: Thursday, January 29, 2009 3:20 PM

> Subject: [maxmsp] Re: RE: Re: [ANN] disis_munger~ 1.3.2 released

> Not really, the only panning option I see is "descretepan" but

> there is nothing that specifies how these eight channels are

> panned. For example how do I tell munger I want a particular

Look at the "spatialize" option found in the bottom-right corner of the help
patch. It gives you per-channel resolution.

> -----Original Message-----
> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com]
> On Behalf Of Anthony Palomba
> Sent: Thursday, January 29, 2009 3:20 PM
> Subject: [maxmsp] Re: RE: Re: [ANN] disis_munger~ 1.3.2 released
>
>
> Not really, the only panning option I see is "descretepan" but
> there is nothing that specifies how these eight channels are
> panned. For example how do I tell munger I want a particular
> grain to output on channel 2?
>
>


It's working now. Thank you for a great external!

I think the problem ws that I did some stupid renaming of the files, but in the latest release this wasn't a problem;)

could anyone shed some (more) light on the issue of grain pitch, and more importantly grain pitch variation and the scale message (pitch sieves)

quite new to granular synthesis and would like to understand it more in depth.

Is it possible to route a continous signal to the grain pitch inlet (e.g. line~) ?

delaylength_ms reports back that the minimum delaylength is 30ms. Does that depend on some other parameter and what's the reason for that ?

This is in part tied to the sampling rate as munger's smallest buffer is 64

bytes. There is however something weird in that and other allied method that

> delaylength_ms reports back that the minimum delaylength is 30ms. Does

> that depend on some other parameter and what's the reason for that ?

This is in part tied to the sampling rate as munger's smallest buffer is 64
bytes. There is however something weird in that and other allied method that
might be a bug...

> -----Original Message-----
> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com]
> On Behalf Of Nick Laqua
> Sent: Friday, January 30, 2009 8:14 AM
> Subject: [maxmsp] Re: [ANN] disis_munger~ 1.3.2 released
>
>
> and another one:
>
> delaylength_ms reports back that the minimum delaylength is 30ms. Does
> that depend on some other parameter and what's the reason for that ?
>
> thx nick


> This is in part tied to the sampling rate as munger's smallest buffer is

> bytes. There is however something weird in that and other allied method

> > delaylength_ms reports back that the minimum delaylength is 30ms. Does

> > that depend on some other parameter and what's the reason for that ?

Upon further investigation, I found out that there is indeed a limitation of

the lower delalength_ms limit being 20 x 64bytes. It appears this may be a

leftover from the original munger~ code and for a good reason. In that range

you get pretty much noise anyways, making anything lower than that an

academic exercise at best... That being said, we've lowered now limit to 3 x

64 bytes which still leaves a tiny bit of wiggle room for grains to be

> This is in part tied to the sampling rate as munger's smallest buffer is
> 64
> bytes. There is however something weird in that and other allied method
> that
> might be a bug...
>
> Ico
>
> > and another one:
> >
> > delaylength_ms reports back that the minimum delaylength is 30ms. Does
> > that depend on some other parameter and what's the reason for that ?
> >
> > thx nick

Upon further investigation, I found out that there is indeed a limitation of
the lower delalength_ms limit being 20 x 64bytes. It appears this may be a
leftover from the original munger~ code and for a good reason. In that range
you get pretty much noise anyways, making anything lower than that an
academic exercise at best... That being said, we've lowered now limit to 3 x
64 bytes which still leaves a tiny bit of wiggle room for grains to be
varied...

As usual, you can get the external at http://ico.bukvic.net/Max

I get the exact same error using either version of disis_munger~ (max 4 or max 5 compiled version).

Roald Baudoux wrote on Fri, 30 January 2009 16:42

I get this message in Max 5.0.5/MacOS X Intel :

disis_munger~: unable to load object bundle executable

2009-01-30 16:40:09.054 MaxMSP[605] CFLog (21): Error loading / 

Applications/Max5/AdditionalExternals/Ivica Ico Bukvic-disis_munger~/ 

disis_munger~.mxo/Contents/MacOS/disis_munger~: error code 4, error 

number 0 (Symbol not found: _usleep$UNIX2003

Referenced from: /Applications/Max5/AdditionalExternals/Ivica Ico 

Bukvic-disis_munger~/disis_munger~.mxo/Contents/MacOS/disis_munger~

I get the exact same error using either version of disis_munger~ (max 4 or max 5 compiled version).
munger1~ does load.

Roald Baudoux wrote on Fri, 30 January 2009 16:42I get this message in Max 5.0.5/MacOS X Intel :

disis_munger~: unable to load object bundle executable
  2009-01-30 16:40:09.054 MaxMSP[605] CFLog (21): Error loading / 
Applications/Max5/AdditionalExternals/Ivica Ico Bukvic-disis_munger~/ 
disis_munger~.mxo/Contents/MacOS/disis_munger~:  error code 4, error  
number 0 (Symbol not found: _usleep$UNIX2003
    Referenced from: /Applications/Max5/AdditionalExternals/Ivica Ico  
Bukvic-disis_munger~/disis_munger~.mxo/Contents/MacOS/disis_munger~
    Expected in: /usr/lib/libSystem.B.dylib
  )

yeah I got the same error both on max5 ad max4...

yeah I got the same error both on max5 ad max4...
any help?


Any plans to release a new version of disis_munger that is compatible with Max6.1 or higher?

works fine here with latest max (32bit) on mac