• tomatoKetchup

    @lacuna said:

    To avoid duplicates, rename your arrays with $0-arrayname

    I've seen load of examples and people's patches using $0-xxxxx as array names, never quite understood if there was any reason why. Could you expand on what that does exactly or point me to some documentation explaining about this tag?

    EDIT: nevermind, found it.

    posted in technical issues read more
  • tomatoKetchup

    @whale-av Alright! I've misunderstood what bound messages did. Though they limited the actual values to be computed. Thanks for clearing this up.

    posted in technical issues read more
  • tomatoKetchup

    If you create an Array and change its size using [array size] messages, the canvas (or "graph") is also rescaled accordingly so that it displays the new range of values from the array along it full width.

    However when you tie more than one array to the canvas and resize both arrays, the canvas does not rescale anymore. I understand this is to deal with the fact that the 2 arrays might have different sizes and this design makes sense.

    In this case, knowing that my 2 arrays will always both have the same size (even if I'm to change said size as part of my code), is there a way to resize the canvas separately then?

    posted in technical issues read more
  • tomatoKetchup

    So here's my issue.

    I'm working on a patch and have been saving versions of it. On V3 things started becoming glitchy and I want to figure out what part of the patch causes that. So I made a return into V2 which has a lot less code and is working fine. I want to have then both opened and start adding the bits of code from V3 to V2 one at a time to isolate the culprit. But in order to do this I need PD not to process V3 at all because it obviously does not like that all my arrays are duplicated.

    Is there a way to tell PD to open a patch but not process it (and I mean not only having DSP OFF for the patch but also ignore things like missing arrays and such) while still having another patch open and processed normally?

    Thanks for helping!

    posted in technical issues read more
  • tomatoKetchup

    @ingox Ah yeah, thanks!

    posted in technical issues read more
  • tomatoKetchup

    @ingox I'm trying to decipher your code. What does the "const 0" in the message box do exactly? Never come across that and can't find it in the documentation.

    posted in technical issues read more
  • tomatoKetchup

    @ingox I see, thanks for the clarification. :+1:

    posted in technical issues read more
  • tomatoKetchup

    @ingox You are right on this one, this would save some computing resources. I'll try your idea.

    EDIT: I see you have posted 2 slightly different versions. Which one is more optimised?

    posted in technical issues read more
  • tomatoKetchup

    Oh nice one! Works like a charm with a [bang~] for real-time control.

    This was my attempt but it was way too sluggish...
    image.png

    You're a star! :+1:

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!