• jancsika

    It sounds like a regression. Please report it at

    https://git.purrdata.net/jwilkes/purr-data/-/issues

    posted in technical issues read more
  • jancsika

    Hi y'all,

    Purr Data 2.13.0 is now available

    Downloads:
    https://git.purrdata.net/jwilkes/purr-data#downloads

    Please report issues here:
    https://git.purrdata.net/jwilkes/purr-data/-/issues

    Changes

    • ported Vanilla's [inlet~ fwd] argument (reimplemented to avoid stack allocation and various other problems) (Thanks to Guillem!)
    • scrollbar fix for optimal zoom (Thanks Ico!)
    • avoid null selectors in core where trivial to do so, gracefully handle and annotate them when/if they happen. Also added an experimental [debuginfo] object so we can output a message with a null selector (and other methods in the future good for testing)
    • ported Vanilla patch for [pow~] handling negative samples in input
    • ported [savestate] from Vanilla
    • ported array, scalar "bang" methods
    • add base argument and inlet for [log]
    • add zcheckgetfn to m_pd.h for checking method signatures match before doing an end run around typedmess. This is used for the reimplementation of [inlet~ fwd]. (Thanks to Guillem for this)
    • port and re-implement Vanilla's "#ffffff" syntax for setting iemgui colors. Additionally, support the "#fff" short syntax. We're not currently saving the symbol colors in the Pd file format, yet. A warning is printed about this since it means we're still storing the lossy color format. A future version will save the symbol colors, but we want to ship a few releases supporting the new syntax before making this breaking file format change.
    • added "test-object" abstraction for doing more detailed testing of objects
    • fixed bug where the box width was wrong when editing certain objects (thanks to Guillem)
    • port "seed" method for [noise~]
    • throttle canvas_motion (part 1 of 2 of getting rid of exponential explosion when moving selections)
    • port [text] "sort" method
    • when clicking an error link, bring the relevant object into the viewport and animate it to make it easy for the user to find
    • add "-alsaadd" flag with pulse device for pulse support (Thanks to Sam!)
    • fixed some alsa bugs
    • ported from Vanilla: preserve phase in [clone] after [all( message, fixed a crasher
    • expand and improve the type hints for errors with edge case atoms (null selectors, null symbols, "floatlike" symbol payloads, etc.)
    • improvements to french translations (Thanks Joseph!)
    • update pd-lua compatibility with Lua 5.4 (Thanks Albert!)
    • port multi-step undo from Vanilla (Thanks Guillem!)
    • initial touch support in GUI (Thanks Albert and spidercatnat!)
    • zoom viewport fix (Thanks Albert!)

    posted in news read more
  • jancsika

    Hi y'all,

    Purr Data 2.12.0 is now available

    Downloads:
    https://git.purrdata.net/jwilkes/purr-data#downloads

    Please report issues here:
    https://git.purrdata.net/jwilkes/purr-data/-/issues

    Changes

    • vastly improved window sizing and scrollbar behavior. Now things like the help patches with content that fits in the viewport should load without scrollbars present. (thanks to Ico)
    • show current text name (if any) in text editor for [text define]
    • ported [text define] "send" method from Vanilla
    • ported [text insert] from Vanilla
    • ported [dac]/[adc] set method from Vanilla
    • added French translation and improve German translation (thanks to Albert and Joseph Gastelais)
    • ensure plot traces remain in the bounding box of the graph (thanks to Ico)
    • ported "symbol" method for [float] from Vanilla
    • added "type hints" for errors wrt unusual or problematic Pd messages. This includes
      • symbol atom which would be parsed as a float if found in a Pd file
      • same thing but with symbol messages, e.g., "symbol 43"
      • empty symbol messages "symbol"
      • empty symbol selector ""
      • null selector
      • symbol atoms/messages with weird "floatlike" data that would overflow/underflow if loaded by a Pd file.
    • ported "send" methods from Vanilla for [int], [float], and [value]
    • document the "tempo" messages for relevant objects
    • fixed a crasher with pasting from Pd patch file (thanks to Ico)
    • fixed a long-standing crasher where editing an open GOP window would hide everything except the patch cords under certain circumstances
    • an object/gop being edited now has the same size as one that isn't being edited (thanks to Ico)
    • fixed keyboard shortcut for dropdown that caused problems for some keyboard types (thanks to Albert)
    • fixed ggee/image border selection when on GOP
    • fixed long-standing bug with route where a bang wouldn't get sent to the reject outlet
    • fixed bug where nested gops erroneously showed a selection rectangle
    • fixed a crasher with resizing a nesting GOP when dragging with the mouse
    • custom scrollbars from Pd-l2ork 1.0 (thanks to Ico)
    • increased gatom character width to 160
    • fixed off-by-one problem with iemgui label positions
    • fixed bar graph display when graph has its own window
    • made a larger hitbox for xlet connection for easier patching (thanks to Ico)
    • make default CSS match pd-l2ork 1.0 style
    • different, "greyed-out" style for inlet hover (as an inlet can't begin a connection with a mouse, but an outlet can)

    posted in news read more
  • jancsika

    [r pd] receives pings

    That's an interesting hack. Garray display is so inefficient that it will typically send so many bytes to the GUI that "ping" is sent to ensure the GUI is still alive.

    However, GUI_BYTESPERPING is set to 1024 by default and I think small arrays will squeak underneath that limit and not trigger the ping message.

    posted in technical issues read more
  • jancsika

    If you mean by clicking or dragging on a "Put" menu array-- I believe Ico added this awhile back for pd-l2ork 1.0, and it's available in Purr Data as well:

    If you have an garray named "array1", you may set a [receive array1_changed] and it will output a bang when the array is changed with the mouse.

    posted in technical issues read more
  • jancsika

    Excellent use of the "Bar Graph" garray style!

    posted in patch~ read more
  • jancsika

    Hi all,

    Purr Data 2.11.0 is now available

    Changes:

    • fixed ambiguity in [select] where argument "bang" could match
    • both "symbol bang" and an incoming "bang" message (Thanks Zack!)
    • fixed graph label position to be consistent with pd-l2ork 1.0 (Pd
    • Vanilla positioning still available with "-legacy" flag)
    • display button for putting multiple arrays in a single graph
    • added color legend for array labels with multiple arrays of
      different colors inside one graph
    • fixed some multiply defined global variables that cause compiler errors
    • fixed potential memory leak with netreceive/netsend "disconnect"
    • fixed some segfaults with preset_hub and preset_read (Thanks Ico!)
    • fixed passing LDFLAGS to configure in the build scripts (Thanks Sam!)
    • added support for compiling on aarch64
    • fixed bug where wrap~ would default to old compatibility mode behavior
    • ported unauthorized/pianoroll (even though it's not really a piano roll)

    Downloads:
    https://git.purrdata.net/jwilkes/purr-data#downloads

    Please report issues here:
    https://git.purrdata.net/jwilkes/purr-data/-/issues

    posted in news read more
  • jancsika

    Hi All,

    Just a reminder that Purr Data is participating in Google of Summer of Code for 2020.

    The GSoC site has more details about the program.

    Check out our dev guide to see how to quickly get up and running as a developer.

    As in other years-- if you can write Pd patches, you can apply to do a project with us this summer.

    Deadline is March 31, so patch fast!

    Best,
    Jonathan

    posted in news read more
  • jancsika

    What is TimbreID and where is the code for it?

    posted in technical issues read more
  • jancsika

    Also, just skimming the source-- that object is set up so that at each dsp tick it schedules the work to be done at the next dsp tick. For Pd that means a delay of 64 samples. Without numbers on the output image in your link I have no idea whether that represents a significant proportion of the delay you measured or not.

    I also have no idea how the delay you measured compares to the delay you experience from the time it takes for the sound to hit your ears. That's why I mentioned rountrip latency above-- it's the only (per-device) measurement that doesn't carry with it the risk of getting caught inside a bubble of insignificant digits.

    posted in extra~ read more

Internal error.

Oops! Looks like something went wrong!