[PD] Advice on creating an external object for controlling a DAC breakout board

Alexandros adrcki at gmail.com
Sun Aug 16 09:31:46 CEST 2020

Actually you're right, signal rate could be an overkill for something
like that. I'll go with control rate. Does your object use wiringPi? If
so, I'd go for creating a new object as wiringPi is now deprecated as
stated here http://wiringpi.com/news/ since the developer got bullied
about support and all. I'll try the pigpio software. Still, I'll give
your object a try and peek into the code, thanks!

Anyway, thanks for the hints!


On 15/8/20 10:02 μ.μ., Martin Peach wrote:
> Hi Alexandros,
> I made an external  [pii2c] which should be available via deken along
> with the source code. You could use that to talk to the dacs, but not
> at signal rate. What you want is already done by any 4-channel USB
> audio interface for much less hassle, and better resolution with [dac~
> 1 2 3 4]. The 4-DAC board could be used to provide control voltages
> for an analog synth or something like that at control rate (once per
> 64-sample block).
> Martin
> On Sat, Aug 15, 2020 at 2:25 AM Alexandros <adrcki at gmail.com> wrote:
>> I want to create an external object to control a quad DAC board with a Raspberry Pi, namely this one. As the object should run at signal rate, I'm confused as to how I should control the rate of values sent to the DAC.
>> Since all signal objects in Pd work on DSP ticks, processing as many samples as the block size as fast as possible, how should I go about sending values to the DAC on a one-sample based clock? Is resampling the way to go? If so, how can this be done? I'm checking the source files, specifically d_dac.c and m_pd.h, but can't make much out of it. My C skills are very limited, hence all the questions above...
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

More information about the Pd-list mailing list