Hi,

I'm trying to make an app for iOS using libpd. I want to use this patch: http://www.lubbertdas.org/pd/guitar1.html as part of the app.

Unfortuantely, [expr~] isn't compatible with the license of the app store, even though it will be a free app (madness)

Is there a way to rewrite an [expr~] using other objects? I am finding it difficult to deconstruct it myself. The objects should preferably all be from vanilla because there is some jiggery poker involved in Xcode if using externals.

The [expr~] in question is:

[expr~ if ($v1 == 0, 0, (if ($v1 < 0, -1, 1)))]

In the patch below it is in: guitar1/pd stringunit/pd gopluckyourself.

Thanks!

http://www.pdpatchrepo.info/hurleur/guitar1.pd

something like this seems to work for your case:

[inlet~]
| \
| [abs~]
| |
[/~]
|
[outlet~]

I think technically it should give a divide-by-zero error in the case where the input equals zero, but for some reason it seems to just give a zero out, which is what we want.

For what it's worth, I think there is a ==~ object somewhere, but possibly not in vanilla.

I think [abs~] is part of zexy, isn't it?

[==~], [>~], etc. are vanilla, though. So you could just do this:

[inlet~]
| \
| \
| \
| \
[<~ 0] [>~ 0]
| |
[*~ -1] [*~ 1]
| /
| /
[+~ ]

Forgot [abs~] wasn't vanilla. But [==~] and similar objects don't seem to be in my version of PD - do you know what the problem is there, by any chance, or how to fix em? They'd be handy objects to have available!

By the way, [*~ 1] is redundant in your patch, but I guess you already knew that and were maybe just doing it for the sake of clarity/symmetry.

@Stutter said:

Forgot [abs~] wasn't vanilla. But [==~] and similar objects don't seem to be in my version of PD - do you know what the problem is there, by any chance, or how to fix em? They'd be handy objects to have available!

They don't work out-of-the box on Pd-extended because of some naming issue or something. If you add hexloader to the startup preferences, they will work. I think it has to be at or near the top of the list, but I'm not positive. I always just use [expr~].

By the way, [*~ 1] is redundant in your patch, but I guess you already knew that and were maybe just doing it for the sake of clarity/symmetry.

Yeah, I did it more for clarity. Basically, whatever value you want should be in the [*~ ].

You might want to take a look at the pd-list, there is a fairly recent discussion about the license of [expr~]. Or was it [expr] ?

if by 'recent' you mean the end of last year, then the issues are still all unresolved.

I will send some emails around this week and see if we can get the ball rolling again.

Has there been any progress on releasing [expr] and [expr~] under BSD license?

I hope that the ball started rolling again!

@Maelstorm said:

They don't work out-of-the box on Pd-extended because of some naming issue or something. If you add hexloader to the startup preferences, they will work.

Oh my... this is magic... thanks