@Il-pleut can you elaborate a bit more, or provide some link that explains what you say in a bit more detail?
How would it export it? In a .png file? Or maybe Gem or Ofelia?

Windows binaries are uploaded to deken, thanks to Lucas Cordiviola.

Version 0.2 is already up on deken and GitHub, as there was an issue with Windows, which is now solved. Please try the new version, especially if you're on Windows. Hopefully binaries for Windows will come soon, as there was already some help on GitHub by a couple of people. I hope macOS binaries will also be available soon, but again, I'll need help for that.

Sorry for cross-posting.

In an effort to understand a bit more about neural networks, I wrote a Pd external, by translating Python code to C, from the book "Neural Networks from Scratch in Python". After a couple of months of working on this, I ended up with [neuralnet].

This is an object written in pure C, without any dependencies, for creating densely connected neural networks for classification, regression, and binary logistic regression. You can choose among different activation and loss functions, optimizers, and other settable features. I've created some examples, trying to replicate some of the examples in the aforementioned book, and some examples of my own.

The code is on GitHub (https://github.com/alexdrymonitis/neuralnet), and Linux amd64 and armv7-32 (Raspberry Pi) binaries are uploaded to deken. I don't have a Mac or Windows machine, and I don't know how to compile for these architectures on a Linux machine (or if that is even possible). I would be grateful if anyone can compile for any of these architectures and upload to deken.

I would also love to get feedback both on how the object performs, and on the source code itself.

@oid that's nice and simple. I think you can also ignore the "$1 set 1" message, as the toggle will have been clicked manually, and won't be affected by "$1 set 0". In this case, you have to initiate [f ] with some value that doesn't exist in [route] below it, like -1, to avoid deactivating the first toggle, if this is the one that is being clicked at the very beginning ([f ] will hold 0 without any arguments, so the first time it will be queried, it will send a 0 to the first toggle). Of course that's what you're avoiding with the "$1 set 1" message in your version.
I'm sure you understand all the above, I'm just writing it for anyone else who need clarification.

@ddw_music but how is it different in your example? There's no change of the sampling rate, so essentially, you should be getting the same result, or am I missing something with your two patches here?

So this:

[r pd]
|
[route dsp]
|
[sel 1]

gives different results than this?

[r pd-dsp-started]

I guess this should be fixed as well? Shouldn't it?

This looks quite serious. Perhaps you should file a bug report.

Why is it slowed down by applying hanning windows? It all happens within the block size set for the FFT transform, doesn't it? You can also use [tabsend~] if you don't want to use [metro].

Its last update being eight years ago, and with the Android system having regular updates, I'm a bit sceptical as to if this can actually work in its current state. If all you need to getting your phone's sensors to control a Pd patch, why don't you install some app that sends sensor data over OSC, and control a Pd patch on your computer?