-
-
alexandros
That's strange. What plugdata version is this? I have 0.8.3 and hovering the mouse over [line~]'s inlet doesn't show this message. I also checked Pd's source code and [line~] is not a mutlichannel object, which could explain such a message.
-
alexandros
The example in its help patch achieves downsamping. You might want to check out this thread https://forum.pdpatchrepo.info/topic/14648/downsample-experiment
-
alexandros
Well, this concerns the Python script, that's why I wrote that it's not Pd related. Never mind though. What's output_socket in your code? What does it try to connect to? Did you try to print your HOST "macro"?
-
alexandros
This is not Pd related as it concerns Python. Nevertheless, what's on line 32 in your script? The error message concerns this line where a connection you are trying to establish fails.
-
alexandros
[hilbert~] and [complex-mod~] are vanilla abstractions located in /usr/lib/puredata/extra (at least in Linux). Have you moved them to some other directory?
-
alexandros
Just a note that getting access to the GPIOs of the Pi is not an easy task, if I'm not mistaken. You'd be rather better off working on the Python script to smooth out the spikes, rather than trying to implement this to a Pd external.
Also, cyclone should be available for Pi 4, so why use Pd-extended that is long gone? -
alexandros
In Arduino you would use the pulseIn() function, where you have to toggle the trigger pin, and then get the output of this function, which you have to multiply by 0.034 and divide by 2. This should give you the distance in cm. You might want to search the source code of this function and try to translate it to Pd or some Python script that will control Pi's GPIOs.
-
alexandros
Check py4pd too, it's available through deken. It's still beta, but it's new, so not outdated. https://github.com/charlesneimog/py4pd
-
alexandros
@bklindgren I copied your makefile and compiled with the sources I have (I guess they are the same, since in GitHub they haven't changed in eight years), and [grambiman~] loads fine. I realized though the a [grambiman] compiles as well (no tilde), which indeed can't load. Did you forget to add the tilde character when you loaded the object?
I then changed the names of the source files, by adding the tilde character, and re-compiled. This time, only tilde objects were made. Maybe a bug of the makefile. I'll send to the Pd list or open an issue on GitHub. -
-
alexandros
Automatonism is not a program, it's a set of Pd-vanilla abstractions simulating a modular synthesizer. It does nothing to the audio device, Pd itself does whatever it is that it does.
A simple way to try to debug it is to load Pd with -noloadbang. It might be that some [loadbang] is causing some issue. Sending your patch is also helpful, because all we can do now is speculate. -
alexandros
@bklindgren you could try to compile it yourself. It's on GitHub https://github.com/rickygraham/grambilib/tree/master
There's Makefile, but I guess you could use Pd's pd-lib-builder https://github.com/pure-data/pd-lib-builder -
alexandros
Drawing arrays is definitely a lot of work. If you want to constantly have your array displayed, you could use [pd~] and split the drawing process from the audio one. You can have an [array define] object in the main process that runs the audio and a graphical array in the child process. Unless you can do with closing the array window when you want to redraw, but then you won't be able to have the slider the way you show in your post.
-
alexandros
@whale-av sure, but a second-hand laptop can't be easily embedded into an enclosure, and it's not that easy to make a little music box. I don't know though what the OP want's to build exactly.
-
alexandros
@FredIR you might want to check IOhannes' punish plugin. It can help solve a fan out connection. https://git.iem.at/pd/punish
-
alexandros
There's an experimental 64-bit version of Pd. Check its download page https://puredata.info/downloads/pure-data/releases/0.54-1-pd64
-
alexandros
@FredIR a piece of advice, always use [trigger] and never use fan out connections like you do here. Your [inlet] for example, goes to at least four other objects, and it's impossible to tell where it goes first and where it goes last. Besides, it is prone to error.
-
alexandros
@atux this message means that the connection between the first outlet of the third object in the patch env.pd failed to connect to the first inlet of the eight object in the same patch. The third object is an [inlet], I guess, and the three question marks mean that Pd don't know where this is supposed to go.
A possible reason is that you changed something in the original patch (an object name, or an object might have loaded from a different library, for example), and now the inlets/outlets table is not the same as it was, hence some connection might be sort of lingering. Don't know if my explanation is clear or not. -
alexandros
You can add this to your startup flags by going to File -> Preferences -> Edit Preferences, and choose the "Startup" tab. At the bottom of this window, in the "Startup flags:" entry, type "-audiodev 2" (at least this is what I had to type), and then relaunch Pd to see if it chooses the right device on startup. If it doesn't, experiment with the number, which should be the same as the position your device has in the list of your screenshot (I thought this was 1-based, but it appears to be 0-based, so the first item in the list is 0).
Even with this flag by default, if you want to launch Pd from the terminal with another device at startup, you can still do it, as the command line flag will override the one you have set in Pd's Preferences.