how to control 40-pin extended GPIO on rasberry Pi 3
@davidborrao You might need to look at the raspberry forum to know how to wire the pins for that... drain current etc. Then you will need wiring-pi...... http://wiringpi.com/download-and-install/ ...... and then use [comport] to communicate with Pd..... https://forum.pdpatchrepo.info/topic/9997/gpio-raspberry-p3-and-pure-data
A quicker, easier, and maybe cheaper route would be to use a cheap android tablet with something like ...... https://hexler.net/software/touchosc ...... which is available for ios as well if you have an apple device already.
You can make your own controls and talk to Pd wirelessly (Wi-Fi dongle needed for the Pi of course)using OSC or Midi.
It will allow you to adapt your patch easily to other requirements as you go...... (volume, re-start track, select track, pause...... whatever you can imagine.....
David.
Getting Pure data to work on Raspbian Jessie (giving pure data permission to access device?)
@alexandros Thanks for your reply. I'm using extended as the PD file i am using requires a number of externals for it to work. PD-L2ORK would be great, but after a number of attempts, I can’t seem to get it working on raspbian Jessie, using step 3 on http://l2ork.music.vt.edu/main/make-your-own-l2ork/software/raspberry-pi/ (since I am not running it headless as I have a screen mouse and keyboard for the pi) the install seems to run smoothly but then after there is no trace of the program anywhere on my raspberry pi, just the download file sitting there. So I ended up settling for extended instead.
I should have the udev rules, since I installed teensyduino using the script here https://github.com/cmcmurrough/cse2100/blob/master/teensy/install_teensyduino.sh which also installs the udev rules.
Might the problems be with identifying/permissions for the correct output? In my case this is a USB to the teensy. I’m a newbie to both raspberry pi and PD, so don’t know if I need to/ how to pre-configure these (if I need to that is).
Thanks
Getting Pure data to work on Raspbian Jessie (giving pure data permission to access device?)
Hi,
I’m new to raspberry pi and am trying to run Pure data on it to control a teensy 3.2 using Open Sound Control which in turn controls some stepper motors for a pump just like here https://github.com/DropletKitchen/pumpsn17 (using the teensy code and PD files provided at the end of the page). I’ve finally managed to install PD extended on my raspberry pi 3 (Raspbian Jessie). But I don’t think PD is able to use the USB to communicate with the teensy, since if I try to run the PD file, PD gives me the error “could not open device /dev/ttyS0: failure(13): Permission denied. Could someone help me please to get PD communicating with OSC through my USB?
Also when I open PD I get this message
“/dev/dsp (read/write): No such file or directory
(now will try write-only…)
/dev/dsp (writeonly): No such file or directory
/dev/dsp (read only): No such file or directory”
and
“Audio I/O stuck… closing audio”
Do I need to do some further configuration to get Pure Data running properly?
Like I mentioned I am very new to using the raspberry pi so any help would be appreciated and please do explain as if I were an idiot, that would be very helpful.
Thank you
Receiving multiple variables from puredata in python
Hello everyone,
I've been working lately with puredata and python together using python as the brain of the system and puredata as the audio engine. For the moment I've been successfully sending messages from python to puredata thanks to this tutorial:
Make Python and Pure Data communicate on the Raspberry Pi
Now I want to reverse the process sending float values from puredata's vumeters to python and then represent them in led vumeters that are connected to the raspberry gpios.
One question is, how do I package the different vumeters values to connect them separately to the netsend object in pd? (Like the following screenshot)
I made a python script with the pdreceive command but I don't know how to take the message from the string concatenation:
I need to take each vumeter value separately from puredata and be able to identificate them in python.
Does anyone knows how to solve this problem?
Thank you!
Making an audio vst for raspberry pi
Hi everyone,
I've been learning and using pd lately cause I want to make with the raspberry pi a portable sampler and audio processor. The patch works pretty good manually triggered inside the patch but I want to make an external program for the raspberry pi with a nice user interface to be able to control the patch and make nice visual elements for it.
I've been reading about libpd and seems to be a good solution to make the program in c++ or python including the puredata in it as a library with libpd, but I didn't found specific tutorials aiming to the raspberry pi...
Has anyone made this on the raspberry pi? Any tips, tutorials or resources?
Thank you!
Help?! Implementing Pd into a hardware device
@whale-av yeah, being a portable effects processor for instruments, it needs to be very small and self-contained (in the sense that no peripherals should be sticking out like keyboards or audio interfaces) which is why I was wondering about implementing adc and dac with physical inputs and outputs into the actual thing instead of using peripherals.
@bmd the Axoloti core looks like pretty much exactly what I was going for with hardware! Although missing an extra input and output. That said, I plan on dealing with two mono signals so perhaps I could use the single stereo input and then separate left and right into input 1 and input 2... Having a quick look at this though http://www.axoloti.com/axoloti-patcher/ suggests that it isn't as versatile as Puredata with not many objects available but maybe I'm wrong again. Definitely going to research more into this. It also sounds like it has an easier solution to my problem of not knowing how to physically implement my patch onto some hardware. Thanks for showing me that.
Seeing as Raspberry Pi/Arduino/Puredata has a lot more support around it, plus the fact I wouldn't have to learn a whole new programming software for Axoloti, do you think I'd be able to make something very similar to the Axoloti Core using a Rasperry Pi? Or is this just overcomplicating things to the point where I might as well just learn how to use Axoloti? I'm struggling to find any appropiate ADC for the Raspberry Pi, but I'm sure there's got to be something high quality around, I mean, I find it hard to believe nobody has made a Raspberry Pi with at least 16 bit 44,1kHz audio input and output.
Also, @whale-av made me think... If I'm not having any peripherals sticking out of my signal processor, a touchscreen might be a reasonable idea for this to simplify things and not take up space. It looks a lot more difficult to do this on Axoloti than Raspberry Pi who have their own touchscreens conveniently available, or the Odroid @alexandros mentioned which has a HDMI port. A touchscreen might not be totally necessary but now I've considered it I kinda want it.
No sound from raspberry
@Congarou Do you get sound in other circumstances? If not then this might help........
http://www.nodepond.com/blog/758-puredata-on-raspberry-pi-useful-hints-and-links as it might be sending to the hdmi audio out......
Otherwise......https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=19155
or you could try Miller's optimised Vanilla.......https://guitarextended.wordpress.com/2014/03/23/update-on-running-pd-on-the-raspberry-pi/
David.
Join our kickstarter for the PiShield, a sensor interface for Raspberry Pi
We’d like to invite you to join our kickstarter campaign for the PiShield, which allows you to easily connect up to 8x analog 5V sensors and 4x digital I2C devices to the Raspberry Pi. See https://www.kickstarter.com/projects/infusion/pishield-sensor-interface-board-for-raspberry-pi
If you’re interested in this new way of working with sensors on the Raspberry Pi, please join in and help us make the PiShield a success !
Thanks for your support,
I-CubeX
PdModular
So I'm working on a project right now and I'm interested in getting some input on the project as I'd like to open source it when I finish. Its a similar idea to the Nord modular but implemented in PD, Python and C. I will try to keep this up to date as the project continues and if there is interest I would be happy to upload some of the code to git
Parts:
Python GUI for building synthesizer utilizing pyata and tkinter
PD objects for each module(VCO, VCA, ENV, MIX, VCF, MIDI, OUTPUT)
Raspberry Pi Cluster(1 conductor and 4 voices) connected via an ethernet switch a d voices ran through a passive mixer
C program for converting midi to OSC messages and sending them to each voice for polyphony as well as uploading your patch of choice
The main idea is that you build a synthesizer patch in the GUI which runs on the conductor which is converted to a PD patch. This patch is then chosen on the conductor raspberry pi when in play mode and is distributed to the 4 voice raspberry pi. All pi's are connected through a switch. This signal for each voice is sent through a passive 4 channel stereo mixer which is sent to a speaker or headphones. A midi controller is plugged into the conductor via usb and its knobs/sliders can be mapped to slider objects within the patch
Adding Modules:
A module consists of a pd object and a python array that represents the inputs and outputs and generates the module object within the application. This will allow for the simple addition of new modules as long as they adhere to the input and output specifications. I hope to add substantially more modules once I get the minimal set needed to build a basic synthesizer.
Would people be interested in something like this at all?
udpsend and receive
@toddak Ah!......... so I am sorry toddak, but I have a lot of questions......
So you still want to use the touch screens, and as you have a few Pi's you have backup cards so you have managed to get back to where you were before the update disaster? I hope so as that would make me feel much better!
You do not really want to use netsend and netreceive but in fact OSC objects (so you don't need MrPeach....... and a later vanilla will be ok as Alexandros suggested)? However, extended has many useful objects!
You are using an extra Pi as a router and you want to use [netsend] and [netreceive] on that?
I would think you would be better off with a dedicated router. I just bought another wrt54 on ebay for 99 uk pence.
Are you planning to stream audio to these 4 Pi's (in which case you will need extended) or are you just sending osc messages from them, or just receiving osc messages so as to start/stop playback?
I have not managed to make audio streaming to a Pi work reliably yet without occasional dropouts, and the sound will not work well at all unless you give Pd root privileges............. so remember.... for later...
sudo chmod 4755 /usr/bin/pd-extended
For audio on a Pi it should be run headless, so you should drop your touch screens in that case.
If you are using the Pi's with touch screens just to send osc messages you would be better off with some £40 android 7" tablets running TouchOSC (one licence for all of the android devices you own).
If they are receiving Osc to control their local playback then why do they have touch screens. Is it the touch screens that would not work with Jessie, or some other screen?
Jessie is not very different from Wheezy (it is not a huge update) but it is exclusively armhf. If the touch screens are needed and will not work with Jessie then you are stuck with the current wheezy that you have installed.
If you need to stay with armel then on one of your working Pi,s (armel) you should try this http://puredata.info/downloads/pd-extended-rpi version of extended and install pulse audio and the fonts (manually or with an apt-get) first. A lot of information you can find from here http://puredata.info/docs/raspberry-pi/?searchterm=raspberry
But if you have Rpi B2 (or anything other that an A or a Zero) you should really be running an armhf distribution.
David.