• Cmaj7

    Hi, I'm stuck in a simple exercise from Loadbang book, which is : "Create a glissando that we hear as linear and one that we hear as logarithmic from C3 to C6." That's my functional linear version:
    log.jpg
    However, about the logarithmic version (and other generalizations I can think about, like exponential, quadratic, etc...), is there an easier way than manually getting the parameters of a function like A*e^x + B and using expr?

    posted in technical issues read more
  • Cmaj7

    @Obineg Hi, I don't get how a loadbang would solve the issue in the original patch, even with the [t b b]. Where would it be connected?

    posted in technical issues read more
  • Cmaj7

    @ingox Nice, that solves an issue of the previous solution. The $1 was being initialized as 0.

    posted in technical issues read more
  • Cmaj7

    Oh, perfect, my mistake: I thought that every object with a $1 would be instantaneously updated with the value that comes from the first inlet, objects with $2 with the values from the second inlet and so on, even if isolated. And the [t f b] also makes sense, since it's like the number information is lost, transformed into a bang, leaving the creation argument $1 immovable.

    posted in technical issues read more
  • Cmaj7

    Why the left print never updates in this example, always showing 10 20, the creation arguments?

    doubt.png

    posted in technical issues read more
  • Cmaj7

    "Thus, the left-most [delay] will output a "bang" a fraction of a second sooner than the right [delay]. This causes the right most delay to reset its timer"

    Yes! Actually you did help me :D . That's exactly the point of my confusion: when the lower delay receives two bangs "at the same time" but in different orders. The delay is reset in one case but not in the other. The last section of your link was very helpful: visualizing it as a tree with its rightmost branch being executed first makes it clear to think about the order. Thanks.

    posted in technical issues read more
  • Cmaj7

    Hi, I thought I had completely understood how pd handles the order of connections, but I can't explain what is going on in this simple case:

    issue-pure data.jpg

    So, that's a beginner question. I know that I should assure the order from right to left using a [t b b], however I'm just trying to understand what's happening when I click the main bang, which is:

    1. Connecting the upper delay first: Upper bang flashes first, lower bang later.
    2. Connecting the lower delay first: Both bangs flash at the same time (lower bang receives a bang first), lower bang later

    My thoughts:

    1. Upper delay receives main bang and schedules it to 600ms later (600ms later it goes to upper bang and lower delay). Lower delay receives main bang and schedules it to 600ms later. 600ms have passed: Upper bang flashes; lower delay receives bang from upper delay thus overriding the message to the lower bang that should be flashing now (?) (because of the message from main bang) Why would that be the order? Finally 600ms later, lower bang flashes.

    2. Lower delay receives main bang and schedules it to 600ms later. Upper delay receives main bang and schedules it to 600ms later. 600ms have passed: lower bang flashes. "At the same time" (but later), a bang comes from the upper delay. Upper bang flashes. 600ms later: lower bang flashes.

    Could someone clarify how to think systematically about the order issue in general (and this case specifically) once for all or point me to a tutorial that handles the subject? Thanks.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!