• LiamG

    @Jona are those samples you used in the video? I'm not getting any sound out of the patch you uploaded.

    posted in patch~ read more
  • LiamG

    @danothedino, you are probably thinking of [osc~], which is supported on every Pd version under the sun. Forgetting the tilde is a an easy mistake to make.

    posted in technical issues read more
  • LiamG

    The Stack Overflow error is triggered by feedback. Using [until] solves the problem iteratively, not recursively, so it won't trigger the Stack Overflow.

    I've always wanted to know more about the Stack Overflow error and exactly what conditions trigger it. Maybe @jancsika can explain?

    posted in technical issues read more
  • LiamG

    @weightless [bytes2any] from the Moocow library is the same as [list tosymbol] but works with $0.

    posted in technical issues read more
  • LiamG

    Zexy works differently than other externals, in that the [zexy/...] method won't work and it has to be declared. This means including it in the 'libraries' list on top (the startup flags can be removed.) If it's not working like this, then it means that PD isn't find finding the right folder (sorry, I can't help with the Mac side of things.)

    With other libraries, I find it easiest just to declare them in the object name, and forget about the startup options. This will work so long as PD is finding the right folder.

    posted in technical issues read more
  • LiamG

    @ingox said:

    @Fauveboy Most of the time you can use Find > Find Last Error to find the source of the last error.

    Even better than this: Shift and click on the red error message. Works most of the time, but not with message boxes.

    posted in technical issues read more
  • LiamG

    Make sure that you have moonlib installed (go to Help --> find externals).

    Then, create the object [moonlib/mknob] and it should work.

    posted in technical issues read more
  • LiamG

    @Jona I think it's not working because a data structure will only respond if you click near its boundary. You'll have to find some way of sending a "mouse" message to the coordinates where it is already set, and then a "mouseup" to the coordinates you want (and maybe even a "motion" in between). This might be more trouble than it's worth.

    posted in patch~ read more
  • LiamG

    Context is very good at this sort of thing.

    https://github.com/LGoodacre/context-sequencer

    posted in technical issues read more
  • LiamG

    You're right, you can't send a mouse message into a closed subpatch. But you can open it, send a mouse message, and close it all at once.

    posted in patch~ read more

Internal error.

Oops! Looks like something went wrong!