Re: [PD] FANN external for neural nets

2018-07-25 Thread Dan Wilcox
I would suggest adopting it and add it as an "ann" repository in the pd-externals Github group: https://github.com/pd-externals We can add you as a member. With pd-lib-builder included, it would then be easy for more people to experiment and keep up to date. I

Re: [PD] [PD-announce] Camomile v1.0.6 - LV2 support, PdStalFx, Audio Buses, etc.

2018-07-25 Thread Pierre Guillot
> > You had a video tutorial on how to generate > plugins before, I think this is also a nice feature to dedicate another > video showing how easier it is now ;) Here it is: https://vimeo.com/281661482. I will do the linux version of the video soon! Cheers, Pierre Le lun. 16 juil. 2018 à

[PD] FANN external for neural nets

2018-07-25 Thread William Brent
Hi all, I wanted to try out Davide Morelli's [ann_mlp] object, which uses the FANN library for neural nets, and found that some of the FANN functions it uses no longer work as of FANN 2.0. I decided to take it on and update things to get basic functionality going, and then went further to add

Re: [PD] recursive searching with [text search]

2018-07-25 Thread José de Abreu
Liam, there are many objects that change the number of inlets when is instantiated differently... so, when you give the -r flag, the text search could be, by default, give all the matches, but also create more inlets to set the range, and if you set a -1 to (bigger than max number of lines) range,

Re: [PD] [else/dir] leaks file handles (was: "too many open files" error in 0.48.1)

2018-07-25 Thread Roman Haefeli
On Tue, 2018-07-24 at 12:44 -0300, Alexandre Torres Porres wrote: > Sorry, I thought I had fixed this in the last update. I swear it was > working for me, but then... that reported bug came back :) The object > still works fine for me in my use cases. Anyway, I'll give it another > go in the next

Re: [PD] [else/dir] leaks file handles (was: "too many open files" error in 0.48.1)

2018-07-25 Thread Roman Haefeli
Hey Alex On Tue, 2018-07-24 at 12:44 -0300, Alexandre Torres Porres wrote: > Sorry, I thought I had fixed this in the last update. I swear it was > working for me, but then... that reported bug came back :) No need to be sorry. I'm not complaining, but simply reporting. > The object still