<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I've made a nice patch for secondary school pupils to learn how to
play live electronic music on a movie (what we call "ciné-concert"
in french, is there a word in english for this btw ?). It contains
three stereo sample players that can load, record, re-record, play,
pitch and add effects and save sets, all controlled by a joypad. I
wanted to be able to choose the order of the effects without having
to load all of them at startup and then rewiring. Plus i didn't want
the pupils to see a single wire, and the thing had to be modular and
evolutive. Plus i thought dynamic patching was cool and felt that it
was the proper way to do it. So now the patch can instantiate any of
the 8 effects in any of the 4 effect-slots by sampler, and save this
setting (thx to sssad) for the next session.<br>
In the end my biggest problem in this patch was not dynamic patching
but loading a sample into a visible array without audio dropouts,
which should be guaranteed to work and a legitimate practice.<br>
<br>
On 22/01/2012 05:30, i go bananas wrote:
<blockquote
cite="mid:CAO=D1cgEwRYuw+cKAjdXvFrEfu4i_VJQZmVB9mV20BSwo=N0BA@mail.gmail.com"
type="cite">what's the deal with dynamic patching these days? it
was always just a 'use at your own risk' type of affair, which was
never guaranteed to work. Has it graduated to being a legitimate
practice?<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated" href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list
UNSUBSCRIBE and account-management -> <a class="moz-txt-link-freetext" href="http://lists.puredata.info/listinfo/pd-list">http://lists.puredata.info/listinfo/pd-list</a>
</pre>
</blockquote>
<br>
</body>
</html>