Pisound (Raspberry Pi Audio/MIDI interface) is here!

nonsmeddy · 2020-04-25T15:38:51.952Z

I tried using a Pisound on a Pi 3B+ with Patchbox OS, in the case that Blokas sells for them, and the Pi would shut itself down due to overheating when I ran SuperCollider—not even doing anything, just with the server booted—unless I put it right in front of a desk fan. This was with X running, not headless.

I haven’t really experimented with it since then for various reasons, but nobody else on the Internet seemed to have this problem. Anyone have any suggestions? Try going headless? Don’t use a case? Try a different distro? Jam a tiny fan in there somehow??

cfd90 · 2020-04-25T18:19:17.636Z

No solutions here - but just wanted to say I’ve also experienced similar seemingly heat related issues with my Pisound Very often has trouble booting after being on for ~15 minutes prior, waiting another 5 minutes seems to fix it.

papernoise · 2020-04-25T18:25:06.727Z

Did you try posting this issue on the Pisound forums, or on github?

disquiet · 2020-04-25T19:41:20.372Z

Thanks for the reminder. I was getting a lot of noise, so mine has just sat on the shelf for a long time. I should give it another go.

mzero · 2020-04-25T19:54:24.007Z

I’m surprised at the overheating issue: I routinely run supercollider doing my effects chain (see other posts for how much that includes) - and all my MIDI processing - for hours at a time, in just the normal Blokas enclosure - no heatsink, no fans - It never overheats. I’ve also run this same set up with an X server running & VNC out to my Mac … again, works for hours at a clip.

Oootini · 2020-04-25T21:07:16.097Z

Also never experienced any overheating or anything like that. Running the stock patchbox os.

spqr6510 · 2020-04-26T13:21:50.444Z

No worries and thanks for the details,

Will try similar method for sure

S

wednesdayayay · 2020-04-26T14:19:24.275Z

in my experience with Pis I found that before I got a proper RPI power supply I was often running out of power when lots of things were plugged into it (webcam, mouse, keyboard, MIDI controller)

I haven’t had any of those pesky lightning bolts pop up since getting a new supply

I think 5.25v is the key the 5v ones I’ve used in the past will work but show signs of low power.

maybe something similar is happening here?

TheTechnobear · 2020-04-27T12:51:35.286Z

No overheating issues here either.

I’d echo @wednesdayayay comments, I found a decent psu with rPI is vital, before when I used an underrated one - I had no end of odd issues, and shutdowns.
( and seems to become more important with each successive pi model !)

nonsmeddy · 2020-04-27T19:31:43.382Z

@papernoise I have not posted on the Blokas forums on the Pisound Github. I guess I should. I neglected to mention that I had soldered header pins onto the Pisound (where it passes through the GPIO pins that the Pisound itself doesn’t use) although nothing’s attached to them. Maybe I damaged something in the process, although I don’t know why that would do this (and nothing else).

@wednesdayayay @thetechnobear I was using a Pi-branded AC adapter from Newark/element14 that’s nominally 5.1V 2.5A… for whatever that’s worth… using the HDMI port and a USB dongle for keyboard/trackpad. I think it still overheated when I SSHed in & wasn’t using either of those, but I don’t remember. Might try again.

Small shrug, big sigh.

cata · 2020-10-24T19:57:32.722Z

Anybody doing anything interesting with these things still?

Stumbled across this cool little gadget but alas, the pisound is no longer in stock. Spoke with a customer service rep on their page and they informed me they should be available again come November so I’ll be excited to get my hands on one then.

For now I’ll have to just make do with a basic setup but that still obviously allows for a lot of complexity, especially with the higher spec’d pi4

mzero · 2020-10-24T23:02:09.171Z

I have two pisound + RPi setups and I use them all the time… and still ever evolving my set up with them. They sound great, and “just work”. Blokas has even made this easier in the last year with Patchbox OS: You can just load that up, add the Modep module - and wham you’ve got a multi-effects box. Load up the PureData module and you can code that way if you like.

Of, if you’re more comfortable in code like me - I just use SuperCollider on it - with a mix of supercollider patches, and standard Linux MIDI utilities (ALSA) - and the box is the control center of my rig: Distributes MIDI, runs my final mix effects chain (EQ, Reverb, Delays) - AND records my sets.

Most recently I bought a Genki Wave ring for MIDI expression control over Bluetooth and was able to incorporate that right in!

cata · 2020-10-25T04:35:25.800Z

oh wow, that Genki Wave ring looks pretty cool!

One thing I’m wondering is if I will be able to use a MIDI over USB device. I was looking at the Beatstep which has a nice form factor with both knobs and pads but until the Pisound is available again I’m not sure if I’ll be able to use it. Seeing as its a MIDI USB device I don’t see why not unless the lag is just pretty awful…

I might just snag one and play with it over the next few days

mzero · 2020-10-25T06:05:20.398Z

RaspPi works with MIDI over USB just fine. I typically have the following connected to the RaspPi all at once:

MIDI over USB:
- Launchpad Pro mkIII for playing notes, and using it’s built in sequencer
- Boppad drumpad
- Digitakt synth & sequencer
- MicroMonsta synth
- Faderfox UC33 knobs & faders
MIDI over DIN on Pisound:
- Pulsar-23
MIDI over Bluetooth:
- Genki Wave
Audio in on Pisound: sub mixer out
Audio out on Pisound: to front of house
Wifi:
- running as access point
- distributing Ableton Link

I’ve done many live performances this way. In general, the lag of MIDI over USB is much less than over DIN. It is no different here. Also - I’m using a Raspberry Pi 3 - and it can easily handle all of the above.

Beatstep Pro + RaspPi should be just lovely! You can load up Patchbox OS, and plug in any class compliant USB audio interface and it’ll all just come up and work. You can decide later if you want to replace the audio interface with the Pisound card.

cata · 2020-10-25T08:59:50.607Z

thank you so much! i really appreciate it

nonsmeddy · 2020-10-25T18:20:42.101Z

I don’t have anything to demonstrate at the moment but I’m still intermittently working on using a Pi/Pisound/SuperCollider to process audio and send MIDI commands to effects pedals in response. I’ve been using Prynth’s distro and a Faderfox EC4 as a controller and finally making some progress (primarily thanks to Eli Fieldsteel and @zebra). And despite my upthread posts, I haven’t overheated the Pi 3B+ since then, so I’m about to try Patchbox again (and MODEP).

mzero · 2020-10-25T19:49:05.493Z

If you’d like to see/use/adapt/mangle my SuperCollider code for both audio processing and MIDI routing, it’s here: https://github.com/mzero/crunch-clockwise

nonsmeddy · 2020-10-25T20:33:11.343Z

Thank you, this should be very useful for reference/manglefodder. ETA: Or to adopt wholesale!

cata · 2020-11-17T19:38:05.719Z

Been lookin online quite a bit for a good answer to this but even after following a few different tutorials I’m kinda stumped on how to solve this.

Basically i want pure data to start at the boot up of my pi. I’ve seen some options that flag -nogui but I leave the GUI on just in case I have to open the pi back up to change settings (headphone out efc)

Has anyone found a sure fire way to get puredata to boot on reboot of the pi? I’m on a pi4, although I’m not sure if that really matters…just been stumped on this one for a few days

murray · 2020-11-17T21:39:26.480Z

i feel that you may be having trouble because your problem is part of a larger topic–starting up programs at boot from a linux system.

found a sparkfun article that goes through the different major methods available on the pi’s default linux distribution–replace the calls to python clock.py and python blink.py with the pure-data executable (i think it’s pd).

learn.sparkfun.com