• DubTak

    How do you create a function that will:

    1. Test if the given statement is true (I have this part as a [moses 12], since the statement is "< 12")
    2. If true, output to left outlet; if false, output to right outlet (again, [moses])
    3. Take the false statement, modify it, and send it back to be tested again

    Step 3) is what I'm having trouble with. I want the function to keep feeding the modified information back into [moses] until it gets a result that is < 12 (i. e. until it bangs left), but as far as I can tell I can only get it to bang once. The purpose behind all of this is to force one MIDI note within an octave of a second MIDI note, though I am sure that I could apply this method to anything else that needs a specific result (or range) to proceed. Please advise and/or link any relevant .pd patches. Thank you.

    posted in technical issues read more
  • DubTak

    I just learned how to make abstractions, but ran into a few odd problems that I could not figure out solutions to. When I set the path for finding abstractions to a directory (Edit->Preferences; New...; C:/...etc) certain objects (notably makenote) were no longer recognized by PD. Furthermore, the specified path clears every time PD boots. PD recognizes abstractions in the pd/ folder, but I can't tell it to look somewhere else without it losing some libraries, and cannot get the path to stick after PD closes. Please advise.

    I am using Pd-extended, if that makes a difference.

    posted in technical issues read more
  • DubTak

    To be clear, my method for testing if the two notes are within an octave is:

    [inlet (note 1)] [inlet (note 2)]
    | |
    [-]
    |
    [abs]
    |
    [moses 12]

    I am aware that this will send right if the interval is exactly an octave, which is by design. The goal is '< octave', not '<= octave'.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!