Created attachment 3835 [details]
here's what it looks like after a half second...

Triode: Could this be related to change 22669

Are you using my MusicInfoSCR screensaver for the alternative volume display? Triode mentioned on campfire it might be broken.

I do have it installed... but I wasn't actually using the screen. Do I automatically get the different Volume screen with it? 

Yes, I think default for the alternative volume screen is on.

So the normal volume screen does show dBs for the transporter, but the display you have here is from MIS - its the custom volume control.

I don't believe the recent volume display changes will impact this as they are now an optimisation of the lines function for input bar.  Just tried MIS and it appears to work ok.

Can you disable the custom volume display in the Music Info settings Matt and see whether it looks ok?  If so we need to debug why you get this display but it is potentially MIS only (and doesn't happen for me!)

Ping matt.  Still an issue?

FWIW: I see it now with my MIS screensaver too. But I only see it when pressing the Volume front panel - using the remote is ok. Maybe still a FW issue. But surely not a Boom bug.

With player-display logging on, I get this when pressing TR's front panel volume button:

[08-08-22 11:39:49.2035] Slim::Display::Display::curLines (487) lines Plugins::MusicInfoSCR::Plugin::volumeLines [Slim::Buttons::Common::pushModeLeft(962)]
[08-08-22 11:39:49.2036] Slim::Display::Display::curLines (488) {
  fonts   => {
               "graphic-320x32" => {
                     line => ["standard.1", "MIScrVolumeSB2.2"],
                     overlay => [undef, "MIScrVolumeSB2.2"],
                   },
             },
  line    => ["Volume", "\1ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`a"],
  overlay => [undef, "-98413920.0\2"],
}

And after a second it clears up:

[08-08-22 11:39:50.9093] Slim::Display::Display::curLines (487) lines Plugins::MusicInfoSCR::Plugin::volumeLines [Slim::Display::Display::update, (eval)(198)]
[08-08-22 11:39:50.9134] Slim::Display::Display::curLines (488) {
  fonts   => {
               "graphic-320x32" => {
                     line => ["standard.1", "MIScrVolumeSB2.2"],
                     overlay => [undef, "MIScrVolumeSB2.2"],
                   },
             },
  line    => ["Volume", "\1ABCDEFGHIJKLMNOP"],
  overlay => [undef, "-27.5\2"],
}

So, yes, I guess, it is an uninitialized variable somewhere.

Ok, is this something we need to fix in the SC release or is it a third-party plugin issue?

I'll take some time to fix my plugin. IMHO it doesn't show anywhere else.

Created attachment 3876 [details]
fixed MusicInfoSCR plugin

Matt - fwiw: my plugin needed a fix. Triode changed the way custom volume functions are called a while back. I missed that change. This version should fix this issue. Please give it a try.