Purr Data is finally released!
Purr Data inherits the goodness of Pd-l2ork and runs on Gnu/Linux, Windows, and OSX. Infinite undo, enhanced editing and 2d drawing, and most of the the externals from Pd-extended (plus more from Pd-l2ork).

[Edit]
2.2.4:

• fix [wrap~] inconsistency
• port mouse events from [hcs/cursor]
• fix bug with dollarsigns in struct names
• add some "legacy_mouse" classes to support externals that report mouse events: "legacy_mousemotion", "legacy_mouseclick" and "legacy_mousewheel"
• fix bug loading default libs on OSX

2.2.3:

• fixed overallocation bug that made loading soundfiles into arrays take up unnecessary amount of memory (4x-8x overallocation)
• fix some utf8 string handling routines
• port fixes for [soundfiler] from Pd Vanilla
• fix bug with "$@" that could cause invalid reads in some cases
• fix [initbang] functionality
• fix crasher in [pdinfo]

New in 2.2.2:

• fixed usability issues with the dropdown object

New in 2.2.1:

• fix stray GUI bugs
• fix some external libs that weren't building under Windows
• fix some OSX key event bugs

New in 2.2.0:

• fix GOP sizing algo to accommodate small GOP abstractions
• turn off anoying Gnome-keyring popup that appears on some systems
• bump nw.js GUI toolkit to 0.22.1
• fix arrow-key navigation-- use arrow keys for scrollbar navigation in runmode, turn off in editmode
• ignore iemgui label in bbox computation for "-legacy" mode
• fix OSCx library on arm builds
• guard against more out-of-order messages from Pd to GUI
• clean up and simplify build instructions
• leave enough space in GOP abstractions to accommodate all xlets
• fix search path bug
• update some of the documentation, removing old "messageoddness" patches that no longer apply to Purr Data
• update unauthorized library
• clean up and simplify the repository code/structure

New in 2.1.2:

• minor bugfix in the console (duplicate messages weren't printed after clearing)
• some minor fixes in the default startup configuration
• some cosmetic changes in the accompanying README and license information
• various bugfixes in objects and internal API functions (message boxes, dropdown atom, loadbang-related issues)
• updated lyonpotpourri to the latest 3.0 version to fix various 64 bit issues on Linux and macOS
• saving the preferences is much faster on the Mac now
• new animated "About Pd-L2ork" popup; also, the proper version is now shown in the generic "About" box on the Mac

New in 2.1.1:

• normalized range for [bendin] (keep old behavior under legacy flag)
• added "mouseenter" and "mouseleave" events for data structures
• fixed "Recent Files" under Windows
• cleaned up documentation in repo
• fix for [midiclkin] (#255)
• added "l2ork_version" message for [pdinfo]
• make loader search order the same as Pd Vanilla
• fixed cord inspector font size
• silence spurious error when autopatching a signal object
• added a [dropdown] object for choosing a value for an atom box (interface not stable yet)
• made gatom resizable by click-dragging in edit mode
• added "<ctrl-mousewheel>" for zooming
• added solarized and inverted solarized gui presets
• fixed mycanvas stroke color updates
• improvements to mode 4 of intelligent patching
• fixed "<Delete>" not deleting a selected object on some systems

New since rc5:

• fixed display bug with [vu] on graph-on-parent canvas
• fix documentation for timer-help.pd
• fix "open" method for [ggee/image]
• default to the user's home directory on OSX app bundle
• open the help browser file browser in the doc folder
• add a canvas "Print" menu item (under "File" menu)
• allow option to save the zoom level with the canvas
• fix a data structure crasher

please report lots of bugs to

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

Binaries:

https://github.com/jonwwilkes/purr-data/releases

Basically it was an intermittent problem of the top-pasted objects disappearing behind the GOP under certain conditions, such as when the patch or window was closed and opened again, or when the GOP was opened.

Pd-l2ork maintains consistent z-ordering across copying/pastng/undoing.

As for requiring the label to be within the GOP, I believe Ico did that specifically to deal with some buggy behavior in Pd-l2ork. But I cannot rememeber what the buggy behavior was.

@jancsika Hi, I was just replying to another thread about my Thumbwheel patch I noticed when changing the colour of a canvas with a message the size box colour does not change (in Windows 10 at least).
Cheers Balwyn

canvas-colour-bug.pd

@Balwyn said:

@jancsika Hi, I was just replying to another thread about my Thumbwheel patch I noticed when changing the colour of a canvas with a message the size box colour does not change (in Windows 10 at least).
Cheers Balwyn

canvas-colour-bug.pd

What color is it supposed to be?

@jancsika Sorry I was referring to the selection box, It retains the original selected colour when the colour is changed after it is created and is visible in performance mode, when it should be Invisible in performance mode or deselected in edit mode and a contrast colour when selected. This screenshot is in performance mode.

Ah, ok. I'll have a look.

@Balwyn this is fixed, will appear in the upcoming release

@Balwyn This is fixed in 2.1.1. I edited the OP to add the links to binaries of the new version

@jancsika That's great!, however I have another possible bug.
Create a GOP of 15 x 15 with name and args hidden add a 15 x 15 bang in the GOP square and save. Now open the patch and add an inlet or outlet and save, the GOP then grows to 19 x 15 with this warning:
"Warning: Adjusting canvas graph-on-parent area to accomodate its name. If you want to have a smaller graph-on-parent window, please hide graph text."

@Balwyn Thanks for the report. It has to do with the value of SCALE_GOP_MINWIDTH. I'll have to investigate what that value is supposed to do and why it is set to 12.

@jancsika Hello again,
I've been a fan of fluidsynth for a long time and really enjoy [fluid~], thank you!
I have noticed the generators 15 chorus send and 16 reverb send have no effect. Is there a message to enable them?
Cheers
Balwyn

@Balwyn said:

@jancsika Hello again,
I've been a fan of fluidsynth for a long time and really enjoy [fluid~], thank you!
I have noticed the generators 15 chorus send and 16 reverb send have no effect. Is there a message to enable them?

I don't know what those are. Can you point me to the relevant documentation?

Cheers
Balwyn

On the help page for [fluid~] at the bottom left is the section relating to generators. If I enter 16 for reverbsend and change the value even to 8192 nothing happens.
I took a liberty and downloaded the Purr Data source from your GitLab page and had a bit of look at the fluid~.c code (and C is really over my head) I found these 3 lines.

fluid_settings_setstr(x->x_settings, "synth.chorus.active", "no");
fluid_settings_setstr(x->x_settings, "synth.reverb.active", "no");
fluid_settings_setstr(x->x_settings, "synth.ladspa.active", "no");

I then wondered if this was by design, because in the FluidSynth 1.1 Developer Documentation they are on by default.

I don't know, I only ported Frank Barknecht's code from C++. You might want to ask him why he used those as default settings.

Thank you
I'll see how I go

Hi,

first of all: Thanks for your great effort! Purr Data's handling is very nice.

I played around with it today and tested some of my patches. Purr Data crashed every once in a while. I can't say, where exactly it happens. Is there a log file? I would send it to you.

And is there a feature list? Would be nice to see what exactly is shipped with Purr Data and where it has extra features. Also which parts of Pd-l2ork are integrated.

Regards,
Xaver

@xgr said:

Hi,

first of all: Thanks for your great effort! Purr Data's handling is very nice.

I played around with it today and tested some of my patches. Purr Data crashed every once in a while. I can't say, where exactly it happens. Is there a log file? I would send it to you.

What OS? 32-bit or 64-bit? Is it the most recent version?

Also-- do you know which externals you were using? Lyonpotpourri happens to have a crasher that we're in the middle of fixing.

And is there a feature list? Would be nice to see what exactly is shipped with Purr Data and where it has extra features. Also which parts of Pd-l2ork are integrated.

Most features from Pd-l2ork are available-- the exceptions are disis_munger~ and k12 mode.

Some features:

• $0 inside message boxes works
• infinite undo, preset_hub/node, iemgui anchors, and other Pd-l2ork features
• GUI presets (in the preferences dialog)
• zoomable canvases and Pd console, ability to save zoom level per patch if you wish (see preferences dialog for checkbox)
• new data structure visualization features-- click <ctrl-b> for Help browser, then scroll down to the second heading about data structures
• dollarsigns work correctly in iemguis
• introspection objects: [pdinfo], [classinfo], [canvasinfo], [objectinfo]
• experimental "dropdown" atom box (name/interface may change)
• multi-connection patching shortcuts (see doc/2.control.examples/25.intelligent-patching.pd)
• realtime find <ctrl-f> in Pd console, and step-find <ctrl-f> in patch windows

There are probably others. Those are just the ones I could think of atm.

Regards,
Xaver

I'm on win7 64bit. Downloaded Purr Data today.

I uploaded one patch which has an error. Because of my settings it adresses iemgui directly, so it isn't found in Purr Data.
The console told me room_sim_2d .... couldn't create.

When I go into that patch and try to delete the knobs, I get a crash. I have to close the nw.exes in the task manager of win7. The running pd process can't be killed at all.

You'll find the patch here (download the folder "crash" and start it from crash/test/test.pd
https://github.com/XRoemer/puredata

I got other crashes with a python programm of mine, which I started via pyext. But I'm not shure if pyext should be used with Purr Data, as I installed it manually.

Best,
Xaver

@xgr I can reproduce the crasher. Unfortunately Windows does not give me useful feedback, so I'll have to debug later from a Linux machine.

@xgr Got a trivially reproducible bug using only two objects now:

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

I think it has something to do with the GUI update queue ordering...

@jancsika I'm interested in moving over from Pd-extende to Purr Data. There are two things that would deter me at the moment though:

• Can I use the same externals that I am using in Pd-extended? Would I have to recompile them to get them to work or would it simply be a case of copying across the relevant .pd_darwin files?

• Is GEM working in Purr Data? This is one of the main things I am using Pd for at present. So I would not like to move across unless GEM is usable.