• drlids

    Well, that's the thing. These are installed by scons, not by make, so it's the scons file that's the issue. The particular libraries or dependencies are indicated in the smspd doc file.

    posted in extra~ read more
  • drlids

    Sorry, should have specified OS X 10.6.8. (I was having trouble posting to the forum, and this was my third try, so I made it brief :-)

    The problem I'm having is with scons and the paths to the libraries. I know there's supposed to be a way to fix this, but haven't been able to figure it out.

    posted in extra~ read more
  • drlids

    Does anyone have any experience building these externals?

    http://www.mtg.upf.edu/static/libsms/

    THanks.

    posted in extra~ read more
  • drlids

    Hi, is anyone familiar with the Xth Sense pd software by Marco Donnarumma (http://res.marcodonnarumma.com/projects/xth-sense/#download)? I have built Xth Sense sensors, which work fine, but I'm having a problem with parameter mapping in the software. I'm a pd noob, so am quite at sea here.

    From the little I understand, parameter mapping is in Xth Sense is done using a graph-on-parent screen which accesses [sssad] abstractions in efx objects. I think the process is supposed to be:

    1. bang the desired control source

    2. enable a parameter control input

    3. touch a slider of one of the efx objects in the workspace

    4. activate one of the outputs

    5. & 2) seem to work fine, but when I do 3), I get the following kinds of error messages in the console (this one when I'm touching the mix slider of the pdelay efx):

    error: * routeOSC: invalid message pattern $1/pdel.mix does not begin with /

    and the parameter doesn't load in the mapping screen.

    I'm running this on OSX 10.6.8 and pd 0.42.5-extended (I tried installing pd 0.43.4, but that didn't fix the problem).

    The efx patches are in a folder called "xth-sense-lib" in my User/Library/Pd folder. In the efx patch (e.g., efx.gui.pdelay~.pd), there are a number of abstractions (I think) for the efx parameters, e.g., one called "xsssad $1/pdel.mix", which opens in a window titled ""xsssad.pd (\$1/pdel.mix)".

    I'm wondering if there's some issue with the $1 variable at the beginning of the (OSC?) message, and if the escape backslash in the window title has anything to do with it. Could there be something in the way my system or my pd install is configured that's causing this error?

    I've sent an email to Marco, but haven't had a reply yet. Of course, I only sent it last night, but I'm feeling some urgency here because I'm hoping to use this system for a short performance 3 weeks from now :-(

    I'd be most grateful for any suggestions.

    Thanks.

    dl

    posted in technical issues read more
  • drlids

    For any Xth Sensors out there, Marco has let me know that the issue has to do with the naming of the efx.gui objects you create in the workspace. Each has to be given a reference to the workspace and the number of its order of creation. For example, the first efx.gui.[something] created needs to be called:

    efx.gui.[something] /wp1/1

    "wp1" stands for the 1st workspace (so workspace 2 would be "wp2", etc.), and the trailing "1" indicates that this is the first efx.gui object.

    Hope this helps. Thanks to Marco (TheSAD on this forum, I believe) for clearing that up.

    dl

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!