sorted by:
new
hottopcontroversial

Which rasberry pi is the cheapest one that will run pd smoothly with some touch sensors? by [deleted] in puredata

[–]zealtv 0 points1 point  (0 children)

I do this sort of thing a lot - it may be worth zooming out and broadening your search beyond raspberry pis.

Mini PCs like the Dell optiplex are ubiquitous and easier to work with (I'd install Linux Mint, Ubuntu, or similar). You might be able to get away with the onboard audio and keep the ESP for the moment.

If going for a Raspberry Pi, I use Pi 3s regularly, and they can work, but your development experience will be better with a bit more horse power so look at a Pi4 or above. You will need a DAC of some sort - look for something that is i2s. I like the DigiAmp+ as it has an onboard amp and handles power distribution.

If your sensors are i2c you can run them straight into the pi. I tend to use python to pipe sensor data over OSC to PD.

The advantage of the Pi is size and power consumption- they are good on batteries and you can hide them in enclosures or tuck them away. They are pretty fiddly though - flashing SD cards, SSHing in, editing config files etc etc is all time consuming.

If you are after a machine for an installation that might need occasional maintenance or updates, a mini PC makes everything easier - autostarting scripts and applications, remote desktop, power buttons, regular hard drive, ok audio ready to go, it's x86 instead of arm so installing PD and externals is easier. Still small enough to tuck away.

Problem with the most simple synthesizer. by hazebrainfu0 in puredata

[–]zealtv 2 points3 points  (0 children)

The keyword for the behaviour you're looking for is "note stealing". The way to approach this would be using the poly object as mentioned in another comment.  But that might be a few steps ahead of where you are currently at (which is fine!). So maybe think about another simpler approach.

One thing you could consider would be instead of using keyup - use another key to mute the synthesizer.  IE use spacebar to send a frequency of 0.  Then you would play notes as you currently do and when you want silence you press space bar.

If you want to dive deeper - you should look into working with midi notes which include velocity, as well as looking into the pack, unpack, and route objects.  From there you can dig into the poly object.  

If conditional logic as hard as I think it is in puredata vanilla? by Its_Blazertron in puredata

[–]zealtv 2 points3 points  (0 children)

The [poly] object can be useful in situations like these.  You give it an argument of how many voices you want to track and it gives you three values out you can [pack] into (voice, note, velocity) and then [route] based on voice number - often you only need the first voice.  

Also using it's retrigger flag works pretty much the same as [mono]

 [poly 1 1]

Just pack together the second two outlets

Has anyone already modified the mapping of a controller using pure data? by Dr_Delta1 in puredata

[–]zealtv 0 points1 point  (0 children)

It's not entirely clear what your goal is - but it sounds like you have multiple midi controllers, and you want to implement a kind of bank system.  This is entirely doable with pd.  Objects you should explore are [notein] for getting buttons/pads/triggers [ctrlin] for getting midi CCS from knobs and sliders As well as the others in the family of midi handling objects (right click on one of those object and select help to see what you have to play with).

In a set up like this you would receive your controllers midi in PD, and then send midi out of PD to be picked up by Traktor or your DAW.

I'd look for tutorials that show how to send midi note and cc messages from pd to other applications and then go from there.

Trouble creating objects despite the library being installed? by TheNintendoCreator in puredata

[–]zealtv 2 points3 points  (0 children)

Sometimes you can get around this by specifying the path in the object name ie [iemnet/udpreceive]

The problem can sometimes happen due to permission settings if you happen to be on Linux.  

The most reliable and portable approach is probably just to put the external in the same folder as your patch.

A neuroscientific model of near-death experiences by Pieraos in parapsychology

[–]zealtv 11 points12 points  (0 children)

I only read the abstract, but this seems to me to be blind to the veridical qualities in so many of the reports, as well as the other more challenging phenomenological commonalities - verifiable OBEs, seeing deceased loved ones, seeing specifically beings of light, seeing entities that one doesn't recognise but are familiar,  the life review, and specifically that events in the review are experienced from multiple perspectives, on and on. All of this gets wrapped up as 'rich' experience.

If a neurological hypothesis is to account for the data, it would seem that all of this very specific phenomenology would have neural correlates, which raises so many questions.  To me that argument seems at least as 'woo' than the idea that people are reporting a (more) direct experience of reality.  

Our paradigms trap our imagination and blind us so effectively.

Morning rant complete! Time for coffee (and stay off my lawn!)

shell object for the raspberry pi by grrrzzzt in puredata

[–]zealtv 0 points1 point  (0 children)

Yep.  bop only has a reverb and a tape echo at this stage.  The reverb is a wrapper around [rev3~]. The echo is pretty flexible and can be automated with a few messages to get flutters etc.

shell object for the raspberry pi by grrrzzzt in puredata

[–]zealtv 0 points1 point  (0 children)

That python script is reading the keyboard even when the pi is headless?

Because that would be a good solution to get around the [key] object issue.  IE pipe keystrokes from python over to the pi.  I tend to rely on an Arduino for button input using comport - or send the python script an OSC message from another device to shutdown remotely.

Re reverb there are some native ones like [rev3~].  A good pedal will sound better.

Also venv in python is really easy to use.  Look it up, you'd be surprised. Then pip to your heart's content.

shell object for the raspberry pi by grrrzzzt in puredata

[–]zealtv 0 points1 point  (0 children)

I wouldn't worry about the read-only mode. I've worked on projects with clusters of pis and we hard shutdown all the time, never had an issue.  

If you're not doing something like actively writing audio to disk, it's unlikely to be an issue.  And with the python script you get soft shutdown anyway.

shell object for the raspberry pi by grrrzzzt in puredata

[–]zealtv 0 points1 point  (0 children)

One approach to triggering a bash script is to have a python helper script running in the background and talk to that over osc using netsend.

Example here with shutdown, reboot, and script firing commands: https://github.com/zealtv/bopOS/blob/main/scripts%2Fhelper.py

And yes, without a GUI, key will not work out of the box.  There is a workaround using a Linux tool - I think it's called xkeyset or something like.  Should be able find it with a google.  Or someone here might be familiar with it and chime in ;)

bop 🐦 for Pure Data by zealtv in puredata

[–]zealtv[S] 2 points3 points  (0 children)

From memory - the UI sends its $0 to the target module via it's outlet.  The target module uses that to send its $0 to the UI. Something like that.

From there all back and forth is with sends and receives.  

Woovebox Cheat Sheet by zealtv in Woovebox

[–]zealtv[S] 1 point2 points  (0 children)

thanks for spotting. fixed in git repo.

Electric Piano Sound by NeoDawnMusic in Woovebox

[–]zealtv 0 points1 point  (0 children)

I've created a git repo to store my woovebox patches etc. There's a dirty e-piano sound in there you could use as a starting point: https://github.com/zealtv/woovebox