<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[clicks management]]></title><description><![CDATA[<p>Hey all,</p>
<p>I'm working on a project where I'm taking accelerometer/gyroscope data from arduino into PD (vanilla) and using those data points to modulate sound parameters. For example, I may take acceleration along an X axis and apply that to a change in frequency or amplitude.</p>
<p>The accelerometer is attached to my hand and records a constant stream of my movements in space, which leads to a large degree of modulation of the sound parameter.</p>
<p>One issue I am having, is that this is creating a lot of clicks! I guess because I have a constant stream of rapidly changing data inputs, I'm frequently getting jolts in the movements. At the same time, I want to preserve that variability / intricacy coming from the constant data stream, but somehow without creating the clicks.</p>
<p>I've attached a patch that I'm experimenting with, would be great to get some advice on how I might adjust something like this to moderate the clicking</p>
<p><img src="/uploads/files/1607370138460-image.png" alt="image.png" class="img-responsive img-markdown" /><br />
Best<br />
Jess</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13173/clicks-management</link><generator>RSS for Node</generator><lastBuildDate>Sat, 17 Oct 2026 18:18:19 GMT</lastBuildDate><atom:link href="http://forum.pdpatchrepo.info/topic/13173.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 07 Dec 2020 19:43:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to clicks management on Mon, 07 Dec 2020 19:43:37 GMT]]></title><description><![CDATA[<p>Hey all,</p>
<p>I'm working on a project where I'm taking accelerometer/gyroscope data from arduino into PD (vanilla) and using those data points to modulate sound parameters. For example, I may take acceleration along an X axis and apply that to a change in frequency or amplitude.</p>
<p>The accelerometer is attached to my hand and records a constant stream of my movements in space, which leads to a large degree of modulation of the sound parameter.</p>
<p>One issue I am having, is that this is creating a lot of clicks! I guess because I have a constant stream of rapidly changing data inputs, I'm frequently getting jolts in the movements. At the same time, I want to preserve that variability / intricacy coming from the constant data stream, but somehow without creating the clicks.</p>
<p>I've attached a patch that I'm experimenting with, would be great to get some advice on how I might adjust something like this to moderate the clicking</p>
<p><img src="/uploads/files/1607370138460-image.png" alt="image.png" class="img-responsive img-markdown" /><br />
Best<br />
Jess</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13173/clicks-management</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/13173/clicks-management</guid><dc:creator><![CDATA[Jess]]></dc:creator><pubDate>Mon, 07 Dec 2020 19:43:37 GMT</pubDate></item><item><title><![CDATA[Reply to clicks management on Mon, 07 Dec 2020 20:05:57 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-a" href="http://forum.pdpatchrepo.info/user/jess">@Jess</a> use <code>[line~]</code> instead of <code>[sig~]</code>, and anywhere a message-rate input goes into a signal inlet. I usually use <code>[pack f 5]</code> or <code>[pack f 10]</code> into <code>[line~]</code><br />
also delete the arguments to your <code>[*~ ]</code> boxes and use <code>[line~]</code> for the right inlet of those as well. If you need defaults, just send them to <code>[line~]</code> when the patch loads with <code>[loadbang]</code></p>
<p>the clicks are a result of changing parameters too quickly. control-rate going into the <code>[osc~]</code> probably isn't too noticeable but if you suddenly multiply by a different value than the previous sample you'll get a click due to the sudden discontinuity.</p>
<p>edit: also, if you decide not to use <code>[line~]</code> to go into <code>[osc~]</code> (bc frequency discontinuities might not create a noticeable click) I would add an argument of 0 to the <code>[+~ ]</code> above the 2nd <code>[osc~]</code> and swap the stuff going into its inlets. Then the 2nd inlet will be message rate which will be a little more efficient.</p>
<p>edit2: changing delay times without artifacts can be tricky generally. With <code>[line~]</code> you might get a zipper/pitch-change effect, but just jumping to a different spot in the buffer will create a click.</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13173/clicks-management/2</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/13173/clicks-management/2</guid><dc:creator><![CDATA[seb-harmonik.ar]]></dc:creator><pubDate>Mon, 07 Dec 2020 20:05:57 GMT</pubDate></item><item><title><![CDATA[Reply to clicks management on Thu, 10 Dec 2020 07:27:34 GMT]]></title><description><![CDATA[<p>Great, thanks Seb, I'll try these out!</p>
<p>Best<br />
Jess</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13173/clicks-management/3</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/13173/clicks-management/3</guid><dc:creator><![CDATA[Jess]]></dc:creator><pubDate>Thu, 10 Dec 2020 07:27:34 GMT</pubDate></item></channel></rss>