Geometry-Nodes: We need more raw-data and list processing nodes
It sounds boring on the surface: Building lists, sorting lists, averages, largest number in list, etc. but these things are essential for building things like audio visualizers, complex simulations, and a whole host of other really cool things (currently building a spectrum-based audio visualizer is completely impossible without resorting to external tools).
2 Comments
if you select the node, and add keyframe, and go to graph, you bake into f-curves.
tutorial link showing how to create custom audio visualizer with geometry nodes. youtube.com/watch
I'm well aware of baking f-curves, however you can only bake a single frequency range. There are no intuitive tools built into blender to bake 4, 8, 16+ frequency ranges, nor any intuitive way to access them all (like you would need if you were to make an audio spectrum)
I tried using Python to bake the data, but then it becomes a challenge of actually getting that data into geometry nodes, hence the need for more list-processing type nodes.