Hey, openmeters an indeed cool software and pretty mature right now, but there are some limitations with newcomers 🫤
The biggest is the linux-only, currently only PipeWire + Wayland is supported.
After taking a look into the project structure, there are some points worth decoupling:
Universal
visual: the ui rendering part
persistence: configuration, window layout, window state, theme, etc.
core: dsp algorithms and abstractions
ui: display the app ui, with WM-specific layouting abstractions
Platform-specific
app: the frontend implementation for Audio backends with specific configuration and WM interaction
Note that the window handing on different OS can also be very different, abstracting the configuration might also be necessary.
Maintaining downstream forks for can lead to lag (AI slop forks are NG), so I'm asking for comments //w//
If everything looks good, I may take a look into the Windows and macOS support and implementing those parts afterwards.
Hey, openmeters an indeed cool software and pretty mature right now, but there are some limitations with newcomers 🫤
The biggest is the linux-only, currently only PipeWire + Wayland is supported.
After taking a look into the project structure, there are some points worth decoupling:
Universal
visual: the ui rendering partpersistence: configuration, window layout, window state, theme, etc.core: dsp algorithms and abstractionsui: display the app ui, with WM-specific layouting abstractionsPlatform-specific
app: the frontend implementation for Audio backends with specific configuration and WM interactionNote that the window handing on different OS can also be very different, abstracting the configuration might also be necessary.
Maintaining downstream forks for can lead to lag (AI slop forks are NG), so I'm asking for comments //w//
If everything looks good, I may take a look into the Windows and macOS support and implementing those parts afterwards.