• patricio.tics

    Solved multiple bugs.
    It rounds to negative numbers, and it works with lower and upper limits.
    multiSliderV2.pd

    posted in tutorials read more
  • patricio.tics

    @willblackhurst I'm trying to have a multislider in a MaxMSP form (made in vanilla) for setting different delay values on audio grains.

    A continous array do not help me. This thing that I made is only a visual aid.

    posted in tutorials read more
  • patricio.tics

    I made a multislider with a quantization value but it is kind of unstable yet, Can you help me?

    multiSlider.pd

    posted in tutorials read more
  • patricio.tics

    it does not work for me either. PD 0.54.1
    What behavior changed?

    posted in abstract~ read more
  • patricio.tics

    • three years later
      +1

    posted in technical issues read more
  • patricio.tics

    SOLVED.

    In the OSChook v2.1.2 there is an advanced setting that combines the OSC messages in one (in order to save some latency). I don't know the depth of this, but I guess the 64 int combines several messages into one.
    So the solution is NOT sending combined OSC messages from OSChook.

    I hope this is useful to others.

    Thanks!

    posted in technical issues read more
  • patricio.tics

    Well, with the mrpeach library I get this error

    unpackOSC: PrintTypeTaggedArgs: [A 64-bit int] not implemented
    

    ddw_music is right...

    The data OSChook is sending is accelerometer information. I'm guessing now to work with another app. It's a shame, OSChook is super powerful.

    posted in technical issues read more
  • patricio.tics

    Thanks I'll try... and post an issue on github I guess

    posted in technical issues read more
  • patricio.tics

    I have a problem with incoming OSC data from OSChook.

    When sending accelerometer OSC from phone, I get two simultaneous messages in Pure Data

    oscparse: unknown tag 'h' (104)
    print: list oschook -0.002295 0.006195 0.983895 0 0
    

    Any hints?

    posted in technical issues read more
  • patricio.tics

    Excellent, thank you.

    The only thing I modified is the range of the probability slider. Noise values come from -1 to 1, so even if the slider is all the way down, we still get random modifications to the sequence. Another way could be using an abs object...

    Great patch.

    PS. Another change could be summing all the event sliders to correctly map the voltage outcome...

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!