Dorian

Hi, I want to learn how to build a glitch aplication on Max/MSP and the theory about glitch. Someone know where can found that kind of information and resources?

maxmsp-glitch

http://aranar.blogspot.com/2008/11/glitches-and-gremlins.html

Here's a few links I collected when I was looking into this.

Vade is king:  http://abstrakt.vade.info/?p=48


Thanks cap10subtext, I will look, thanks for your time!

I'm looking for build a simple glitch, but talking about music and their theory.

You may also want to look into Nick Collin's bbcut. Here is

http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.65.4876&rep=rep1&type=pdf

You may also want to look into Nick Collin's bbcut. Here is
some theory for you...
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.65.4876&rep=rep1&type=pdf


I unfortunately cannot share my source patches, but take a look at my Major Malfunction (built as a Pluggo plug in in Max 4) for ideas:

http://defectiverecords.com/majormalfunction

One of these days, I plan to port it to MFL....

[stutter~] is a good stop to some form of glitching...

Thanks Dan, lewis for your posts, I found this patch for a simple glitch, But I want to understand how works, my idea is built step by step my own glitch patch, I want to learn.

http://www.youtube.com/watch?v=jkNk31XSNBM

this's the patch running: http://www.youtube.com/watch?v=jkNk31XSNBM

well, [drunk] is the mainly culprit here, to allow it to 'glitch'. it is wired in a way that a clean [drunk] is connected to the start time of [groove~]. there is also another [drunk] with extras on connected to the end time of [groove~], to allow it to stay ahead of the first one, by using [+ ].

you can then use the number boxes to change the step size and range of the [drunk]'s.

its quite a simple patch for glitching, because it just controls the start/end points of the sample, though you can construct way better and more controlled ones. [stutter~] really is a good option for glitching/stuttering.

have a check in the help files, they are more than useful...

well, [drunk] is the mainly culprit here, to allow it to 'glitch'. it is wired in a way that a clean [drunk] is connected to the start time of [groove~]. there is also another [drunk] with extras on connected to the end time of [groove~], to allow it to stay ahead of the first one, by using [+ ].
you can then use the number boxes to change the step size and range of the [drunk]'s.

have a check in the help files, they are more than useful...


Thanks Lewis for your information, thanks so much!

no worries man, thats what this max communities for :).

have fun in your search for glitchy goodness...

Max/MSP Glitch