• 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?

    posted in technical issues read more
  • 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?

    posted in I/O hardware diyread more
  • 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.

    posted in I/O hardware diyread more
  • 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

    posted in technical issues read more
  • 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.

    posted in extra~ read more
  • alexandros

    I'll check when I have time and get back. Should be simple.

    posted in extra~ read more
  • 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.

    posted in technical issues read more
  • 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

    posted in extra~ read more
  • 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.

    posted in technical issues read more
  • 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.

    posted in I/O hardware diyread more
  • alexandros

    @FredIR you might want to check IOhannes' punish plugin. It can help solve a fan out connection. https://git.iem.at/pd/punish

    posted in technical issues read more
  • 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

    posted in technical issues read more
  • 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.

    posted in technical issues read more
  • 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.

    posted in patch~ read more
  • 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.

    posted in technical issues read more
  • alexandros

    Before attempting to install anything, like pipewire (I'm a Linux user and have never used it, TBH, it's the first time I read about this, didn't know it before), go to Media->Audio Settings, and try to choose another input and output device. It may be that the device Pd chooses by default is not working. It might also be that you get two devices with the same name. That's the case with my laptop, where I have two "HD-Audio Generic" entries (actually four, two tagged as "hardware" and another two tagged as "plugin"), but the first ("hardware" tagged) doesn't work, while the second (again "hardware" tagged) works fine.

    posted in technical issues read more
  • alexandros

    @jameslo while it is not necessary to add the forward slash, it doesn't really hurt adding it, so it is not necessary to remove it. Actually, I think it's good to be there as it explicitly shows proper OSC addressing.

    posted in technical issues read more
  • alexandros

    Do you really need to record at your baud rate? A high baud rate enables fast transmission of data between devices, but do your data really change that fast?
    Perhaps you can filter your data and save every time there's a big enough change in the values, or something like this.

    posted in technical issues read more
  • alexandros

    Paid gig. The publisher of my first book, "Digital Electronics for Musicians", has asked me to write a second edition of it, with updated software and all. This book is about interactive musical projects with Pd and Arduino. We are looking for a technical reviewer, that will read through and realize all the projects, to verify that what I've written is functional.
    Even though an introduction to both Pd and Arduino is made in the book, experience at least with Pd is highly recommended. Experience with the Arduino is desired.
    Please DM me if interested.

    posted in news read more
  • alexandros

    Actually, raising the window size should drop the CPU usage. I tried your patch on my laptop, and with a 4096 size, I got a 13% CPU. while with a 16384 size I got 10%. With a 2048 size I got around 17%. I didn't get any dropouts or crackling sounds at all. Are you outputting all the subpatches at the same time? If so, did you try to lower the volume of these sub patches? It could be that they are exceeding the audio range and there is distortion there, but I doubt that this is really the problem. Other than that, I think @whale-av gave all the help possible.

    posted in technical issues read more
Internal error.

Oops! Looks like something went wrong!