The audio processing nodes that are available in the webpage are way out of date. So many new audio classes have been created in the Tympan_Library. All or some of those classes should be made available as nodes. My matlab scripts looks through the library and tries to auto-identify audio classes and auto-create the nodes. It depends upon specific comments that I would add to the Arduino to help it build the nodes. Probably, most of the new nodes are lacking the right comments. Possibilities:
It's possible that we might not want to do the auto-sniffing for new classes. Instead, we might want a table that specifies ("opt-in") which classes should result in nodes.
How do we possibly keep the help docs (html code for each individual audio class) in-sync with the Arduino/C++ code? Right now, they live in different files and in different repos. This seems like a bad idea, if keeping up-to-date docs are valued. Instead, can the html code live in the Arduino/C++ code somehow?
The audio processing nodes that are available in the webpage are way out of date. So many new audio classes have been created in the Tympan_Library. All or some of those classes should be made available as nodes. My matlab scripts looks through the library and tries to auto-identify audio classes and auto-create the nodes. It depends upon specific comments that I would add to the Arduino to help it build the nodes. Probably, most of the new nodes are lacking the right comments. Possibilities:
It's possible that we might not want to do the auto-sniffing for new classes. Instead, we might want a table that specifies ("opt-in") which classes should result in nodes.
How do we possibly keep the help docs (html code for each individual audio class) in-sync with the Arduino/C++ code? Right now, they live in different files and in different repos. This seems like a bad idea, if keeping up-to-date docs are valued. Instead, can the html code live in the Arduino/C++ code somehow?