often, the config values aren't strings, bit ints or other types. instead of converting this after getting the string, it should be possible to convert them before. this reduces redundant code.

this class should be able to edit settings of other components at runtime, like changing the shader
additional classes are needed to make manager accessible to the user, e.g. by keyboard or network

for configuration of color schemes etc. by receiving messages from node-red

update: debugging the existing code seems hopeless. thus, a new version of the renderer should be build which isn't based on a webgl implementation.

rework current code to adhere to:

• code styles defined by microsoft checks (should not have warnings on build)
• own code styles

the outputs don't seem to have the correct resolution when multiple are used. tested with one output with size 30x30 and one with size 5x30.

Replacing the visualization would remove the beat detection

Implement logger providing support for multiple log levels

the returned image always contains the whole frame

if the audio device specified isn't available, the user is asked to choose a new device. but since the audio setup failed previously due to the unavailable device, the library is partially set up already, and a new attempt to set it up always fails.

Once the key features are done, some sort of documentation should be added, at least a quick start guide.

the visualization should be able to switch to a new shader while running

move some of the settings/values declared in the source code to the config file. this reduces the number of magic numbers.

see this checklist which is completely empty: https://github.com/lukaswagner/AudioReader/community

https://youtu.be/YJa-BcpPkow?t=2m

The project probably won't compile with travis, since it is windows only. Thus, we should use appveyor.

Allow turning modules on/off using the config file.

it seems the resolution uniform isn't set correctly. this may happen due to the new way uniforms are set.

Library can be found here. We should probably use the local library. It doesn't require authentification and provides easy access to the album art.

Possible features:

• basic playback control (play, pause, skip, ...)
• using the album art and song data in shaders
• react to events (e.g. switch shaders on new song)

Use USB to transfer data without relying on wireless connectivity, check out existing protocols and implement one

this would allow for blending shaders together, e.g. to add a flash-on-beat effect to existing shaders