• alexandros

    how about [list split]? Although you'll might have a problem as Pd doesn't like the curly bracket. Don't really know...

    If [list split] works and you don't really know where "lon" and "lat" are in your list, you can use [list fromsymbol] to convert the strings to their ASCII characters and compare with a message "symbol lon" passed through another [list fromsymbol] via [list-abs/list-compare] (or just make your own list comparison algorithm).

    posted in technical issues read more
  • alexandros

    If you're fine using externals, [canvasdelete] from iemguts can do what you need.

    posted in technical issues read more
  • alexandros

    3dPdModular is live on GoGetFunding! After a long time of development, this hardware modular synthesizer running on a single Raspberry Pi, programmed in Pure Data, has finally reached its release state!
    It includes many special features, like module cloning, cross-fading between patches, a patch-saving mobile app, and many more!
    The campaign will run for a month. Please share with people interested!

    Check the campaign here https://gogetfunding.com/3dpdmodular/

    Promo video:

    posted in news read more
  • alexandros

    @jameslo I should have thought of the space escaping myself :D Avoiding spaces in file names is nevertheless a good practice IMHO.

    posted in technical issues read more
  • alexandros

    The slash is no problem, the comma and the white space are though. What @whale-av says is correct but you can do the conversion to ASCII and back to a symbol all in Pd. Here's how (separate the two messages, and combine them with the ASCII white space in between - 32):
    osc2processing.png

    posted in technical issues read more
  • alexandros

    First off, remove any GUI objects (number atoms, sliders, bangs etc.). Replace all GUI bangs with the message "bang" or the object [bang]. If there are parts of the patch that don't operate all the time, it's a good idea to put a [switch~] in subpatches and turn their DSP on and off whenever possible.
    Replace all graphical arrays with the [array] object.
    About the crash when you turn on the DSP I have no idea. You could launch Pd via gdb to debug it, or launch it like this from the terminal:
    pd -open /path/to/your/patch -stderr 2>name_of_your_log_file.log
    And then read the .log file which will be in the same directory as your patch or the directory you launched Pd from, not sure which of the two.

    posted in technical issues read more
  • alexandros

    Nice one! Thanks for sharing!

    posted in pixel# read more
  • alexandros

    @EEight not a C -> Pd guru, but I have written a few externals. A Ninjam Pd external sounds fun. I have never used Ninjam before, I only recently heard about it. I could take a look at the code and see if it's possible for me to port it to a Pd external... I do have some time, but not much.

    posted in news read more
  • alexandros

    Most of the iem stuff are available through apt-get. Just type apt-cache search ^pd- and you'll get all the available Pd packages. Then install via sudo apt-get install <package-name>.

    posted in technical issues read more
  • alexandros

    with [oscparse] you should also se [list trim] to trim out any identifier. Then you can send the output to [route] and use the OSC addresses as arguments to [route]. If though you have an address that goes deeper than one work, e.g. /my/osc/address then you'll probably need three cascaded [route] objects where each takes one of these words as an argument.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!