You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Though with a risk of bloat, it may make sense to design/implement a plugin mechanism that would allow the injection of different variables (attributes/uniforms) into the shaders, for instance:
You may want to visualise a shader on the terminal that is consuming Jack Audio (or any other audio) samples and displaying the FFT or the waves itself
You may want to visualise different resource usage (CPU, memory, etc)
This data could be obviously made available through the existing mechanism, but this would mean that the client program would need to run continuously to feed the data and would put the burden of implementing the source of data on the client side.
The text was updated successfully, but these errors were encountered:
Though with a risk of bloat, it may make sense to design/implement a plugin mechanism that would allow the injection of different variables (attributes/uniforms) into the shaders, for instance:
This data could be obviously made available through the existing mechanism, but this would mean that the client program would need to run continuously to feed the data and would put the burden of implementing the source of data on the client side.
The text was updated successfully, but these errors were encountered: