Hi IOhannes, I read your other answer giving more info on why it could be outdated even if released a couple of weeks ago. I think I get, although I'd still assume or don't see why pd wouldn't be available at "apt-get" if it were up to date.

Anyway, the extra packages are GEM and other stuff, so not bonk~/expr~

Well, I got it from miller's site anyway, no problem with that, just need to know how to put it into the menu bar, and I'd appreciate if anyone could help me with the warning "*ALSA input_error (snd_pcm_open): no such file & director*"

thanks

2014-07-03 9:49 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

you are using an outdated (even if it's the official one) raspbian

I got the latest image from "noobs", released a couple of weeks ago, then I installed raspbian from it. So this is supposed to be out of date huh? And then... well, I did "apt-get update" and everything and was assuming this was an issue related to apt-get, not the image system.

cheers

2014-07-03 4:27 GMT-03:00 IOhannes m zmölnig pd-list@lists.iem.at:

On 07/03/2014 06:24 AM, Alexandre Torres Porres via Pd-list wrote:

...

...

Hi there, I was treating this in a different mail thread, sorry, but

let me

...

go ahead and start this one.

questions

1- Why can't I get vanilla 0.45 from "apt-get"? I get 0.43 :P

as said before: because you are using an outdated (even if it's the official one) raspbian, based on Debian/wheezy.

in addition to what i said before, i just noted, that there is also a raspbian version available, that is based on Debian/jessie, and this version will include Pd-0.45.5¹

if there are no images available for raspbian/jessie, you could try upgrading your current image by doing the following (as root):

1. in /etc/apt/sources.list (and probably /etc/apt/sources.list.d/*)

replace all occurences of "wheezy" with "jessie" 2. run "aptitude update" 3. run "aptitude full-upgrade"

this is utterly untested, but the standard procedure to upgrade a Debian based system.

mgfasr IOhannes

¹ http://archive.raspbian.org/raspbian/pool/main/p/puredata/

...

2- I downloaded from miller's site and have 0.45 extracting and alive,

I'm

...

running it from a folder at pi/home, but how do I put it in the menu

bar?

...

Really linux noobs here... 3- Pd 0.45 is complaining about "ALSA input_error (snd_pcm_open): no

such

...

file & directory, but it still works making noise and all. What does it mean, how do I fix it?

Thanks

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->

http://lists.puredata.info/listinfo/pd-list

...

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

On 03/07/14 22:55, Alexandre Torres Porres via Pd-list wrote:

Hi IOhannes, I read your other answer giving more info on why it could be outdated even if released a couple of weeks ago. I think I get, although I'd still assume or don't see why pd wouldn't be available at "apt-get" if it were up to date.

The meaning of 'stable' in debian is that it does not change, and apt-get fetches packages that you wish to install from this base (it would be possible for someone to maintain the latest pd as a raspbian package, but it is almost as easy to install from Millers site so no-one bothers ... the fact that pd is in debian means it gets tested on ARM and the version in 'stable' automatically gets built as part of raspbian with no extra work, which was especially nice when raspbian first came out). This system allows distributions like raspbian to have a predictable base that they can then take the time required to adapt for their purposes, and it allows sites like Millers to build the up-to-date versions within that known framework so that they 'just work' (and will still work a few weeks later) because all the stuff it depends on does not keep changing versions every day.

In the case of raspbian they have compiled debian with lots of modifications to suit their particular CPU and have added and keep working on lots of extra stuff that is specifically for their GPU and peripherals etc. They then maintain raspbian with all these added things updated from time to time but staying with 'stable' as the base. Presumably they will move to jessie sometime for their main version (probably not till they get it tested and running cleanly sometime after it is 'frozen' in advance of it becoming the new stable ... this freeze would be expected reasonably soon, debian does this on a two year cycle). But that does involve lots of work and lots of testing since they are building the whole of debian for an architecture which is halfway between the two official debian architectures (the CPU is a rather old version of ARM, but with floating point hardware). Chasing all the changes in the latest versions of everything all the time would be very hard work.

As for menus or desktop icons ... it is just a little text file called "puredata.desktop" containing something like:

[Desktop Entry] Name=Pure Data Comment=Visual dataflow programming platform for multimedia Comment[ca]=Plataforma de programació visual per aplicacions multimèdia Comment[de]=Grafische Datenflussprogrammierung für Multimedia Comment[es]=Plataforma de programación visual para aplicaciones multimedia Comment[fr]=Plateforme de programmation visuelle pour applications multimédia Comment[it]=Piattaforma di programmazione visuale per applicazioni multimedia Comment[pt]=Plataforma de programação visuais para multimedia Exec=pd -noadc %F Terminal=false Type=Application Icon=puredata.xpm Categories=AudioVideo;Audio;Video;Development MimeType=text/x-puredata;application/x-maxmsp;text/x-maxmsp; StartupNotify=false

using the appropriate "Exec=" line, and an appropriate file for "Icon="

if you add this file to the folder "/usr/share/applications" then it should turn up in menus, or if you put it on the desktop it should show up as an icon you can drag and drop to.

But the RPis are not very powerful, and running them without a desktop (using ssh or similar over ethernet and /etc/rc.local to launch stuff on boot) makes a lot of sense.

Simon

On 19/07/14 14:09, Alexandre Torres Porres wrote:

"RPis are not very powerful, and running them without a desktop (using ssh or similar over ethernet and /etc/rc.local to launch stuff on boot) makes a lot of sense."

are you saying it basically doesn't really work for live audio applications with the desktop system on and all?

cause, yeah, it seems it can'thandle, but I always thought you guys were doing it with the desktop system and everything

I just got into this for curiosity, I don't really need a RPi for anything, just wanted to play with it and see if it could run simple patches. I could eventually use it live, but it wouldn't make sense to run it over ssh with another computer (would rather just use the other computer).

Generally ssh is used to program and set things up without needing a desktop on the Pi, especially since Pd needs a GUI to edit but not to run and ssh lets you open the window on a laptop while Pd is running on the (screen- and X-less) Pi.

Then the RPi is finally set up to launch whatever program you want running when it boots ... and Pd is well suited to being controlled via buttons or pedals or some connection (say midi) to an instrument or some controller like a BCF2000, or perhaps do something more like an effects box that takes audio in and outputs processed audio. Or possibly it is the controller in some kind of interactive installation or instrument, there are accessible input and output control options for all kinds of sensors to be used and in this situation a screen and keyboard just get in the way ... make trouble and take up space.

RPis certainly are not very useful if you really need a laptop with screen, keyboard, desktop and such to run and control what you are using .. but they can be useful in this case networked so they are running say a projector or some speakers (or even lights or motors or whatever) and are being cued or controlled from a program on a laptop somewhere. Especially if you want several projectors or need to control things spread over a wide area from a single program. Maybe you have the laptop running audio and want several projections, or want to use the GPIO features which are not available on a laptop. Pis are a compact, cheap, low-power way to do this (if they are up to the task you have in mind ... Udoo or Beaglebone or such for a bit more $$ are much more powerful devices for similar needs if the RPi can't do it).

Simon

On 20/07/14 01:28, Jaime E Oliver wrote:

On Jul 19, 2014, at 3:34 AM, Simon Wise via Pd-listpd-list@lists.iem.at wrote:

...

Maybe you have the laptop running audio and want several projections, or want to use the GPIO features which are not available on a laptop. Pis are a compact, cheap, low-power way to do this (if they are up to the task you have in mind …

Just continuing with that thread, what are the best ways to send and receive messages with a Pi via UDP or similar?

Is it possible to connect them with an ethernet cable directly without a router?

certainly a Pi and a laptop can be connected directly by an Ethernet cable, that is an easy way to work on a Pi via ssh and just needs the two to have compatible manual addresses set. It is described in all the basic Pi how-tos.

That also works fine for a laptop and a single Pi, say with Pd running on each passing messages via UDP in the usual fashion.

For more than two devices and UDP over Ethernet you will need something connecting them all ... say a router, or a switch if they all have manual addresses, or if you just need cueing and latency isn't critical you could use wifi with the laptop running as the access point (but probably best to choose TCP in that case).

There are other ways to communicate if you want ... but they take a bit more effort ... they could be useful in some cases. You may want a bunch of Pis controlling a bunch of projectors and audio where they can be mounted close together ... if you wanted very tight sync you could connect them so they shared a clock and communicated with each other via one of their GPIO protocols, with pd on each and one of them connected via Ethernet to a laptop if required, or one of them running an interface with a screen or desktop and acting as the controller while the others dealt with the media, or something like that. The possibilities are endless.

Simon

best,

J

Thanks for the info on using the Pi as an access point; that sound awesome! I'd really appreciate a rough estimate of the latency one would get when sending UDP between the Pi and a laptop with this WiFi setup.

I'd love to build some kind of foot controller using the Raspberry Pi, but I wonder if the delay would be negligible enough for a looper (control from Pi, audio processing on laptop).

Exciting! -Brian

On Mon, Jul 21, 2014 at 5:01 PM, Chris McCormick chris@mccormick.cx wrote:

Hi,

On 19/07/14 17:28, Jaime E Oliver via Pd-list wrote:

...

Just continuing with that thread, what are the best ways to send and

receive messages with a Pi via UDP or similar?

...

Is it possible to connect them with an ethernet cable directly without a

router?

If you have a USB WiFi dongle, it's possible to set it up as an access point that other devices can connect to. That way you don't need a separate wifi hub/router. Can't remember which tutorial I followed but you should be able to find it with a search like "raspberry pi as access point" if interested.

With regards to sending messages over UDP - I've been working on a set of patches for doing LAN syncing of Pd patches - both timing and data. Will post when I have something solid to share.

Cheers,

Chris.

-- http://mccormick.cx/

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

On 2014-07-21 18:29, Brian Fay wrote:

Thanks for the info on using the Pi as an access point; that sound awesome! I'd really appreciate a rough estimate of the latency one would get when sending UDP between the Pi and a laptop with this WiFi setup.

I'd love to build some kind of foot controller using the Raspberry Pi, but I wonder if the delay would be negligible enough for a looper (control from Pi, audio processing on laptop).

I would think an arduino is more appropriate as a foot controller as it has real-time response, can connect via USB or MIDI(with 2 extra resistors and a connector) and uses less power. (or the teensy, which can operate as MIDI over USB and is even smaller than an arduino) The rPi would be better as the thing that's controlled by your foot.

Martin

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2014-07-03 15:16, IOhannes m zmoelnig via Pd-list wrote:

at least looking at [1], it is quite clear that the raspbian image is

[1] http://www.raspberrypi.org/downloads/