purr-data issueshttps://git.purrdata.net/jwilkes/purr-data/-/issues2021-04-13T19:30:56Zhttps://git.purrdata.net/jwilkes/purr-data/-/issues/408please update soundfiler from 0.482021-04-13T19:30:56ZAlexandre Porresplease update soundfiler from 0.48Hi, I don't know if you have a list or awareness of all recent changes from vanilla to incorporate here, and if you're on it. Anyway, I'm just hoping the new [soundfiler] features get added here as well soon, as I have a couple of patche...Hi, I don't know if you have a list or awareness of all recent changes from vanilla to incorporate here, and if you're on it. Anyway, I'm just hoping the new [soundfiler] features get added here as well soon, as I have a couple of patches now that use these features, as well as the buffer~ object from cyclone 0.3 requires this as well.
Cheers3.0.0https://git.purrdata.net/jwilkes/purr-data/-/issues/531decrease recursion limit to 10002020-05-23T08:21:12ZJonathan Wilkesdecrease recursion limit to 1000The increased size of STACKITER to 10000 can cause crashes on Windows.
Decrease it to 1000 where it used to be.
Even though recursion in Pd is treacherous, this could possibly break patches which depend on the larger limit. So we'll ne...The increased size of STACKITER to 10000 can cause crashes on Windows.
Decrease it to 1000 where it used to be.
Even though recursion in Pd is treacherous, this could possibly break patches which depend on the larger limit. So we'll need to bump the major version when this gets changed.3.0.0https://git.purrdata.net/jwilkes/purr-data/-/issues/523Purr Data 2.8.1 crashes when loading subpatch with widened text box2019-09-09T21:48:04ZChristof RessiPurr Data 2.8.1 crashes when loading subpatch with widened text box[purr-data-crash.zip](/uploads/782cea6a541f40432abd8a8b3349bbe1/purr-data-crash.zip)
I'm on Windows 7. I've narrowed down the problem to a very simple patch (see above) which crashes Purr Data with a socket error (shown in the picture)....[purr-data-crash.zip](/uploads/782cea6a541f40432abd8a8b3349bbe1/purr-data-crash.zip)
I'm on Windows 7. I've narrowed down the problem to a very simple patch (see above) which crashes Purr Data with a socket error (shown in the picture). I've seen encountered the same error on other occasions. Is this a known issue? Basically, I can't open many of my Pd vanilla patches in Purr Data...3.0.0https://git.purrdata.net/jwilkes/purr-data/-/issues/429https://github.com/jonwwilkes/purr-data is out of sync2019-08-25T19:49:55ZAlbert Gräfhttps://github.com/jonwwilkes/purr-data is out of syncJonathan, you forked https://github.com/jonwwilkes/purr-data from my GH mirror at https://github.com/agraef/purr-data in order to upload your releases. Which is all good and fine, but you never sync that repo with upstream, and so your r...Jonathan, you forked https://github.com/jonwwilkes/purr-data from my GH mirror at https://github.com/agraef/purr-data in order to upload your releases. Which is all good and fine, but you never sync that repo with upstream, and so your release tags at https://github.com/jonwwilkes/purr-data/releases all point to the same long out-of-date revision 1f41004d. (In case you're wondering, that's also why it says on the overview page that "This branch is 366 commits behind agraef:master.")
I wouldn't be worried about this, but I see that your repo there has been forked at least two times already, so at least some people seem to think that it is the real thing, when it's just an out-of-date clone being used as a download area.
Fixing this is simple. In your local working copy of git@git.purrdata.net:jwilkes/purr-data.git, just add git@github.com:jonwwilkes/purr-data.git as a remote named, say, `github`. Then, whenever you're about to upload a release, just run `git push github`. Your fork there will be up-to-date and you can then create the release tag and upload your release on GH to the proper revision.3.0.0Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/530remove jessie builds from CI2019-04-25T04:40:39ZJonathan Wilkesremove jessie builds from CIThe way LTS works in Debian, they just drop the jessie-backports repo and cause apt-get update to output an error.
I removed that repo from /etc/apt/sources.list to get 2.9.0 to build successfully. But let's go ahead and take their erro...The way LTS works in Debian, they just drop the jessie-backports repo and cause apt-get update to output an error.
I removed that repo from /etc/apt/sources.list to get 2.9.0 to build successfully. But let's go ahead and take their error seriously and drop Jessie from CI and the release binaries.3.0.0Jonathan WilkesJonathan Wilkes