<?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[Cubie pd pedal]]></title><description><![CDATA[<p>Hi there,</p>
<p>I've been working on that for nearly two years and now it is done I find it soooo 2014  that the previous intentions to make a full wiki page seem now silly.  Anyway this could give ideas to other people so here is an abstract.</p>
<p>This is basically a lame-electronics simple-aggregate-of-common-parts version of a guitar pedal that hosts pd extended patches as effects.  It's based on a cubieboard 2, connected to an el-cheapo (this was intended as a proof of concept hardware) soundcard through usb, internally.  It boots a rt-patched version of debian from microSD card (never managed to flash sdram) in ... 50seconds <img class="emoji emoji-extended" src="http://forum.pdpatchrepo.info/plugins/nodebb-plugin-emoji-extended/images/frowning.png" title=":-(" alt=":-(" />, with autologin so no keyboard is needed.  After this time it behaves like a floor pedal, pd runs the stored patches responding to its hardware interface.  Anyway a keyboard, a mouse and a display can be plugged in and it behaves like a linux desktop, it's easy to edit patches on the fly.</p>
<p>The interface consists of three footswitches, three leds, a button switch, a clickable rotary encoder, four clickable potentiometers and a 4x20 lcd display.  The pots and the display communicate with the gpio pins (all of them digital) through i2c, the pots being read by a quadruple i2c adc.</p>
<p>I called it a pd pedal, but I have to confess it cannot be directly connected to a guitar amp, as the IO are two preamplified instrument inputs, two line in, two line out and a headphone stereo jack.  This can be solved when you have a digital pedal in your pedalboard that have line inputs.  Of course I knew it from the beginning, and could never work it around later as it would have taken more space and would have been tedious to implement for a beginner electronics fan like me <img class="emoji emoji-extended" src="http://forum.pdpatchrepo.info/plugins/nodebb-plugin-emoji-extended/images/grinning.png" title=":-)" alt=":-)" />.</p>
<p>I also wanted from the beginning to make a relatively small footprint on my pedalboard so it is rather tall (aluminium box is 160x125x76).  What a challenge to stack these components in such a box it has been, especially when it came with holes positioning, elements fixture, internal aluminium rounded edges to mill and file down...</p>
<p>The 1 ghz dual-core with 1 gb ram allows for decent dsp patches.<br />
The pedal automatically runs a predefined patch but interface allows for patch selection. (statically coded so far)</p>
<p>I initially wrote several externals that allow for interface i/o, but never got rid of audio artifacts when the interface was trigged.  As a workaround I now make the readings from outside pd, with a well-choosen rt priority and send values to pd using pdsend.  The workaround is only half of what it should be, as for outputting data (writing things on the display) I still rely on a homebrew pd external (too much work for me to take it out of pd).  The result is uncorrupted audio only when lcd display is not used, which is unreasonable (every pot controls a patch parameter and I love to see the values updated on the lcd).  But when the pedal is left untouched the audio is clean.</p>
<p>Here are two pics, one of the inside before the audio card is stacked and the other one showing it outside look.</p>
<p><img src="/uploads/files/1448753058887-re_p1010788.jpg" alt="re_P1010788.JPG" class="img-responsive img-markdown" /> <img src="/uploads/files/1448753058887-re_p1010755.jpg" alt="re_P1010755.JPG" class="img-responsive img-markdown" /><br />
Thanks,</p>
<p>Nau</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal</link><generator>RSS for Node</generator><lastBuildDate>Tue, 14 Jul 2026 21:54:18 GMT</lastBuildDate><atom:link href="http://forum.pdpatchrepo.info/topic/9692.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 28 Nov 2015 23:31:55 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cubie pd pedal on Sat, 28 Nov 2015 23:33:30 GMT]]></title><description><![CDATA[<p>Hi there,</p>
<p>I've been working on that for nearly two years and now it is done I find it soooo 2014  that the previous intentions to make a full wiki page seem now silly.  Anyway this could give ideas to other people so here is an abstract.</p>
<p>This is basically a lame-electronics simple-aggregate-of-common-parts version of a guitar pedal that hosts pd extended patches as effects.  It's based on a cubieboard 2, connected to an el-cheapo (this was intended as a proof of concept hardware) soundcard through usb, internally.  It boots a rt-patched version of debian from microSD card (never managed to flash sdram) in ... 50seconds <img class="emoji emoji-extended" src="http://forum.pdpatchrepo.info/plugins/nodebb-plugin-emoji-extended/images/frowning.png" title=":-(" alt=":-(" />, with autologin so no keyboard is needed.  After this time it behaves like a floor pedal, pd runs the stored patches responding to its hardware interface.  Anyway a keyboard, a mouse and a display can be plugged in and it behaves like a linux desktop, it's easy to edit patches on the fly.</p>
<p>The interface consists of three footswitches, three leds, a button switch, a clickable rotary encoder, four clickable potentiometers and a 4x20 lcd display.  The pots and the display communicate with the gpio pins (all of them digital) through i2c, the pots being read by a quadruple i2c adc.</p>
<p>I called it a pd pedal, but I have to confess it cannot be directly connected to a guitar amp, as the IO are two preamplified instrument inputs, two line in, two line out and a headphone stereo jack.  This can be solved when you have a digital pedal in your pedalboard that have line inputs.  Of course I knew it from the beginning, and could never work it around later as it would have taken more space and would have been tedious to implement for a beginner electronics fan like me <img class="emoji emoji-extended" src="http://forum.pdpatchrepo.info/plugins/nodebb-plugin-emoji-extended/images/grinning.png" title=":-)" alt=":-)" />.</p>
<p>I also wanted from the beginning to make a relatively small footprint on my pedalboard so it is rather tall (aluminium box is 160x125x76).  What a challenge to stack these components in such a box it has been, especially when it came with holes positioning, elements fixture, internal aluminium rounded edges to mill and file down...</p>
<p>The 1 ghz dual-core with 1 gb ram allows for decent dsp patches.<br />
The pedal automatically runs a predefined patch but interface allows for patch selection. (statically coded so far)</p>
<p>I initially wrote several externals that allow for interface i/o, but never got rid of audio artifacts when the interface was trigged.  As a workaround I now make the readings from outside pd, with a well-choosen rt priority and send values to pd using pdsend.  The workaround is only half of what it should be, as for outputting data (writing things on the display) I still rely on a homebrew pd external (too much work for me to take it out of pd).  The result is uncorrupted audio only when lcd display is not used, which is unreasonable (every pot controls a patch parameter and I love to see the values updated on the lcd).  But when the pedal is left untouched the audio is clean.</p>
<p>Here are two pics, one of the inside before the audio card is stacked and the other one showing it outside look.</p>
<p><img src="/uploads/files/1448753058887-re_p1010788.jpg" alt="re_P1010788.JPG" class="img-responsive img-markdown" /> <img src="/uploads/files/1448753058887-re_p1010755.jpg" alt="re_P1010755.JPG" class="img-responsive img-markdown" /><br />
Thanks,</p>
<p>Nau</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal</guid><dc:creator><![CDATA[nau]]></dc:creator><pubDate>Sat, 28 Nov 2015 23:33:30 GMT</pubDate></item><item><title><![CDATA[Reply to Cubie pd pedal on Sun, 29 Nov 2015 22:10:07 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-a" href="http://forum.pdpatchrepo.info/user/nau">@nau</a> Looks beaut!</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal/2</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal/2</guid><dc:creator><![CDATA[ricky]]></dc:creator><pubDate>Sun, 29 Nov 2015 22:10:07 GMT</pubDate></item><item><title><![CDATA[Reply to Cubie pd pedal on Fri, 08 Jul 2016 16:33:41 GMT]]></title><description><![CDATA[<p>That looks so damn good!</p>
<p>I threw together an Orange Pi One in a 1590BB enclosure a few months ago, and this post kind of inspired me to do so. I used an arduino nano for the I\O, a 2 dollar CM108 usb codec, and a 4 character LED display I had to write a driver for. With x-forwarding set up, I can just plug an ethernet cable in for full control.</p>
<p>I'm using armbian, and so far the audio works. Did you have to compile a RT kernel yourself? Thats the trick I'm currently stuck on. I can compile it but it wont boot.</p>
<p>It is also not nearly as pretty and well done as yours.</p>
<p><img src="/uploads/files/1467995396969-ce74m6oweaa9yss.jpg" alt="Ce74m6OWEAA9Yss.jpg" class="img-responsive img-markdown" /></p>
<p><img src="/uploads/files/1467995433782-pedalipaddress.gif" alt="pedalIPaddress.gif" class="img-responsive img-markdown" /></p>
<p>If you're curious, <a href="https://github.com/MitchRatquest/lil-toepopper" rel="nofollow">my github</a> has the rough draft of it. An install script to compile from source and drag pd-extended's externals into the right place, set up audio permissions and x-forwarding, With a vanilla kernel (no preempt) it works well without dropouts. The next step is to design a PCM2906 soundcard with 2 in and 2 out audio and correct buffering.</p>
<p>Where did you get that enclosure? It looks like it has tons of room for expansion!</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal/3</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal/3</guid><dc:creator><![CDATA[mitchdokken]]></dc:creator><pubDate>Fri, 08 Jul 2016 16:33:41 GMT</pubDate></item><item><title><![CDATA[Reply to Cubie pd pedal on Thu, 01 Sep 2016 22:37:40 GMT]]></title><description><![CDATA[<p>I'm so sorry!</p>
<p>I sort of missed your post.  The enclosure is very similar to <a href="http://befr.rs-online.com/web/p/general-purpose-enclosures/5287274/" rel="nofollow">this one</a>, but with the dimensions of <a href="http://befr.rs-online.com/web/p/general-purpose-enclosures/5287274/" rel="nofollow">this other one</a>.</p>
<p>I didn't compile the kernel by myself, I used the one found <a href="http://cb2.autostatic.com/images/" rel="nofollow">here</a>, that was released by autostatic, you can read <a href="https://autostatic.com/tag/cubieboard2/" rel="nofollow">this article</a> which is related (and the comments), even if it didn't mention his personal repository I pointed to before.  Anyway the guy is trying to stay at the cutting edge most of the time, and you'll find many interesting posts on his blog, like <a href="https://autostatic.com/2015/09/28/working-on-a-stable-setup/" rel="nofollow">this one for instance</a>.</p>
<p>Nau</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal/4</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/9692/cubie-pd-pedal/4</guid><dc:creator><![CDATA[nau]]></dc:creator><pubDate>Thu, 01 Sep 2016 22:37:40 GMT</pubDate></item></channel></rss>