The Zynthian project has tackled this problem. Might be some code there (it's all open source).
https://discourse.zynthian.org/t/ecoders-directly-to-the-gpio-of-the-pi-4/47...
https://discourse.zynthian.org/t/encoder-mapping-for-direct-i-o-connection/4...
Cheers
On Wed, Nov 8, 2023, 10:11 AM Dan Wilcox danomatika@gmail.com wrote:
I believe there was a basic [gpio] object, perhaps from Miller but I don't find it on his site now.
If someone has the source code, maybe we can put it up separately on github.com/pd-externals with a pd-lib-builder makefile. It should be a simple C object, so easy to compile.
On Nov 8, 2023, at 6:57 PM, pd-list-request@lists.iem.at wrote:
Message: 1 Date: Wed, 8 Nov 2023 15:14:21 +0100 From: Yann Seznec yann@yannseznec.com To: pd-list@lists.iem.at Subject: [PD] Current best practice for GPIO pins on Raspberry Pi? Message-ID: 9052D80B-1595-4402-92D3-066B5A4D3AD7@yannseznec.com Content-Type: text/plain; charset=utf-8
Hello,
I?m wondering what the best option is nowadays for using the GPIO pins on a Raspberry Pi in Pure Data.
Wiring Pi seems to be no longer available, as far as I can tell. I?m not sure what other options there are?
One option suggested elsewhere for inputs was to use the ?retrogame? script to turn GPIO pin activity into keyboard presses and use the [key] object in Pd, but I can?t seem to get that script to work properly yet.
Any suggestions would be great, thanks in advance.
Yann
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com robotcowboy.com
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list