It'll be PD and custom patches, midi controller, and some UI. Not a DAW, but probably drums and bass and loop pedal support

I put a POC together

https://seanbouk.github.io/midi-device-debug/

If you're reading this on something you've got a midi keyboard plugged into, I'd love it if you could try it and just tell me if it behaves oddly! I don't have enough hardware for decent testing

(Also, if there's something you'd want to see in a portable workstation - I'm taking suggestions!)

None of this code will make it into the final codebase!

A quick update to let you know the pre-order funding campaign has now launched !

The project has come a long way. Check the updated page !
https://www.crowdsupply.com/pipo-interfaces/pipo

If you like it, spread the word, your support will be key in bringing this project to life.

I'll post here as soon as I find out anything useful.

That makes sense, thanks! Though I'm having a hell of a time getting pd to load the hid external on the rpi. I've put the folder in /usr/lib/pd/extra and tried using the declare object but it just won't load...

i have spent entire day on this shit
here is what you need to add to PD command line,in my example was ELSE lib
-path /home/pi/Documents/Pd/externals/ -lib else

bests
K

Edit: Have you tried not using OS scaling and just configuring each application to work? Most application allow you to tweak all the interface settings/set a default zoom, I think pd is the only application I use which does not allow it, at least on linux, not sure what OS you use.

For me it is hard to know because information is missing:
This part I don't understand:

and also to trigger this sample as soon as there is something echoing the trigger at a distance inferior of 15cm using a Threshold~ object

but this works already, doesn't it?
In which condition you want the sample to stop?
What kind of sensor?
What is attached to pins 11 and 12?
What data does [adc~ 12] output when moving hand?
Is [print Distance (cm) : ] about correct?
Which Bela tutorial are you referring to?

[rzero~ 1] does some integration, I think. [dac~ 11] outputs ultrasonics? [line~] till 1000 and [adc~ 12] going into [samphold~] measures the time untill the reflected ultrasound is detected or sth like that?

Generally speaking, when developing something it is important to understand what is going on instead of blind copy&paste. And when asking, to provide all information you have to make it easy / possible to answer.

Hello, thanks for taking the time to answer my question, I really appreciate it; and sorry for having missed some important information.

This patch works as it will start playback when I put my hand on the sensor, but it won't stop playback when I remove my hand from the sensor range, and I'm still figuring out how to work this out. When I remove my hand the distance keeps going up, and thus the volume, until it reaches 25cm which is the limit I've put with [min25]. Your fade out patch makes sense but I still need something to bang it when I remove the hand from the sensor, putting a Threshold at 24cm for example kind of works, but it's not completely natural; imagine you're at 5cm and remove your hand, so the volume goes up to 24cm and then stops playback...

The sensor is the HC-SR04, pin 11 send triggers to ultrasonics every 60ms, echo receives feedback and sends it to pin 12, which with a time equation calculates distance. What [adc~ 12] outputs is a good question, I try to figure it out myself too, but it doesn't work with normal [print] command, not till it reaches [snapshot~] so then it outputs the distance in cm again. The distance is quite accurate, I think the real distance is a bit longer than the printed in console. The Bela tutorials are the official ones at https://learn.bela.io/tutorials/pure-data/sensors/distance-sensor/

What I've done at the moment is sample holding and snapshotting the distance so it stays in place, so if I want to "stop" the sample I just bring the distance near 0 with my hand very close bringing the volume near 0 and nearly unnoticeable, but the playback starts from the beginning with a [loadbang] is just that at any distance you'll put your hand the volume will go up. This works well in this case as the samples are standing notes, but it would be cooler if it starts from the beginning. I know there is some way to use this sensor as a trigger but I can't find any information.

Use the pico as a keyboard HID device (using MicroPython on the pico, and "HID" object in Pure Data), or

Use the "comport" object in pure data to unpack and read the sensor values over serial.

Does anyone have any thoughts about either way? Limitations or resolution(if that even applies). Someone please correct any of this- I'm thinking the HID might be a bit friendlier, both pi's and an audio interface are going in a Disney princess guitar I got from goodwill eventually, but I'm trying to get it functional first. I see values in pure data using a Logitech USB game controller and the "HID" object, and about 10 years ago I got sensor values over serial with the "comport" object in Pure Data with an Arduino Nano v3.1. I was reading a little about the u2if git repository that might be another option...and Just found out about the teensy boards... was thinking the teenzy 4.0 might be a better option. But- I haven't gotten this working, so that's first. I appreciate this space!

It's using a slower language than c/c++ to run Cpython however all OS needs have the potential to be run after audio. This makes the headphone jack the output (not ideal) so driver writing... eesh. But perhaps a solid solution?

Ready to begin hiring patch and script authors. FLOSS obv. If anyone is interested in this we can go deeper about the project, please message me if you have skills or the desire to contribute, can talk royalties, pay, etc.

I have been also using an old laptop with comport for a lot of projects in fact, comport is an old friend. I guess what I am trying to do, is get the most from these bits of technology rather than multiply them, and especially in a single project. I find myself using both raspberry pi AND arduino because I can manage the audio well on the pi (or well enough) and other stuff on arduino, but really I know the pins on the Pi can do that stuff too, so I just thought I would start to look for perspectives on how other people are doing these things.

I am going to explore your suggestion of doing the PWM in Pd and then sending this across the pins on the Bela to control things, I think this is the sort of very direct approach I was finding myself hazy about.
All the best,
Jorge

If it can help anyone :

Notein
expr (($f1-36)*0.01675)-0.201)
dac~

In the expression :

$f1 is the midi note number
0.01675 is the value for a semitone step. This is an approximation due to the fact that when I measured the voltage a the output of my soundcard, it wasn't consistent octave to octave, so I settled for this for now. I have yet to measure the deviation with a tuner.
-201 is a kind of octave switch. 0.201 is the value for an octave that I settled for that was giving me a steady division for a semitone step. If I substract it at the end of the expression, it allows for a lower octave range by offsetting the value. Example : do not put it in the expression, you get the straight value. -0.201 gives you an octave lower than the setting on your synth (16' becomes 32'). -0.402 outputs two octaves lower than the setting on your synth. Adding 0.201 gets you in the other way.

For anyone else...... the above patch sets the block size to 512 and the delay (msec) to 5....... etc.
So it is tailored to @KMETE's soundcard.
You will need to change some parameters at the end of the [audio-dialog x x x ( message if you want to use it to automatically select your card and set it correctly.
The values in the [audio-dialog x x x ( message are detailed in set_audio_parameters.pd
David.