To Pd list -
I'm leaving on a strenuous trip (BIFEM in Bendigo, Australia, then DAFX in Edinburgh, Scotland) and back Sept. 10. I won't be able to upsh any official releases till sometime that week. At that point I'll try at least to fix the following bugs:
jack support in macOS keyup problem in MacOS deleting trailing backslash in message box crashes Pd TCL errors when closing certain GOP sub-patches bug in line~ - will need back-compatibility version control back compatibility for wrap~ bug fix
(Some are already fixed and just need merging and testing). I don't plan to add any features - just fixes, hoping to get everything stable.
cheers Miller
2017-08-28 12:01 GMT-03:00 Miller Puckette msp@ucsd.edu:
I don't plan to add any features - just fixes, hoping to get everything stable.
great, let me remind you of a fix that didn't make into 0.48-0, maybe we can include it now? https://github.com/pure-data/pure-data/pull/106
thanks
On 08/28/2017 07:02 PM, Alexandre Torres Porres wrote:
2017-08-28 12:01 GMT-03:00 Miller Puckette msp@ucsd.edu:
I don't plan to add any features - just fixes, hoping to get everything stable.
there's the update/0.48-0 branch (PR#191]), which includes a number of bug fixes, including:
format specifiers)
binaries on 64bit OSs)
there's also the attempt to fix the memory leak in netsend/netreceive, though this is not finished yet.
afaict, most things in this branch are really major bugfixes. there are some minor things though, which you might want to exclude (e.g. setting the bug-tracker link to https://bugs.puredata.info, which currently directs to the sf-tracker; but might be used to point to another ticket system (e.g. github) whenever this is appropriate)
great, let me remind you of a fix that didn't make into 0.48-0, maybe we can include it now? https://github.com/pure-data/pure-data/pull/106
wasn't this scheduled for "the next release"? i was under the impression that this actually meant 0.49-0
gfmdsar IOhannes
2017-08-28 15:58 GMT-03:00 IOhannes m zmölnig zmoelnig@iem.at:
wasn't this scheduled for "the next release"? i was under the impression that this actually meant 0.49-0
I am not sure, that's why I asked there. But I also got the impression that Miller is open to bug fixes "any time", but feature additions "not always", like now.
IOhannes m zmölnig wrote:
2017-08-28 12:01 GMT-03:00 Miller Puckette msp@ucsd.edu:
I don't plan to add any features - just fixes, hoping to get everything stable.
there's also the attempt to fix the memory leak in netsend/netreceive, though this is not finished yet.
hi, two questions about this:
1.) how does this memory leak show in a patch that has a lot of net traffic (i.e. sends many numbers fast to sync video to a timecode) ?
2.) would it be better to use "iemnet" objects instead ?
best
oliver
On 08/29/2017 10:08 AM, oliver wrote:
hi, two questions about this:
1.) how does this memory leak show in a patch that has a lot of net traffic (i.e. sends many numbers fast to sync video to a timecode) ?
the memory leak is about leaking connections, so it is only relevant if you do *lots* of (re)connects. the actual transmitted data does not leak.
2.) would it be better to use "iemnet" objects instead ?
as the author of iemnet, i'd say "of course". as a Pd-purist, i'd say it's *far* better to to fix the *vanilla* objects.
at least, with Pd-0.48 you can use iemnet together with fudiparse/fudiformat to build a fully compliant wrapper for netsend/netreceive, so you can have a temporary workaround until the core objects are fixed.
btw, the error in netsend has been fixed in the update/0.48-0 branch, but netreceive still leaks some memory on each reconnection...
gamrds IOhannes