Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slimproto: Turn off Display and visualization by default #1318

Merged
merged 5 commits into from
May 28, 2024
Merged

Slimproto: Turn off Display and visualization by default #1318

merged 5 commits into from
May 28, 2024

Conversation

cociweb
Copy link
Contributor

@cociweb cociweb commented May 22, 2024

Turn off Display support and use None type visualization by default. This PR tries to resolves the periodical "unhandled grfe" messages in the player's log as defined in music-assistant/hass-music-assistant/issues/2118

Turn off Display support and use None type visualization by default
@cociweb
Copy link
Contributor Author

cociweb commented May 22, 2024

I'm still getting:

[23:25:03.913442] process:537 unhandled grfb
[23:25:03.931492] process:537 unhandled grfe

but only 1 time: at the startup of the client. - Maybe the display function is still called somewhere.
The periodical flood is resolved by this PR. - I think we can live with it. 😉

(Just for the record: grfb is for the brightness, grfe is for rendering)

@marcelveldt
Copy link
Member

Check the lint issues - otherwise good!

Copy link
Member

@marcelveldt marcelveldt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@marcelveldt marcelveldt merged commit f7ba09f into music-assistant:main May 28, 2024
4 checks passed
@marcelveldt marcelveldt changed the title Turn off Display and visualization by default Slimproto: Turn off Display and visualization by default May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants