Processor Limitation indicated by VU meter? - Wiim Ultra

[Krabin]

When using the HDMI input for movies (stereo PCM) or Tidal Connect for 16bit 44.1kHz FLAC music, the VU meter works beautifully, but as soon as I play any hi res 24bit music, the VU meter is slow, delayed, no longer smooth, and stutters. The best way I can describe it is it looks like it's operating at like 6-12 fps with 100-300ms input delay instead of the usual 20-30fps and 20-40ms input delay. Can the processor not handle both hi res audio and accurate VU (digital dB) metering? If so, I'll just not use the VU meter anymore because I don't think it's a good idea for my Wiim Ultra processor to operate at 100% a lot. However, I do like the VU meter and it's a bit silly that a hifi device would struggle to process hifi. Or, maybe, it just allocates less processing for the meter to ensure the audio processing works right: that would be great.

 

[Krabin]

Videos showing this behavior:

WIIM Ultra VU Meter Indicating Processor Limitation? – Google Drive

drive.google.com

 

[Burnside]

Guess only WiiM can answer this - raise a ticket via the more/feedback section in the app referring to the videos and see what they say.

 

[Krabin]

Guess only WiiM can answer this - raise a ticket via the more/feedback section in the app referring to the videos and see what they say.

I did (before I recorded the videos). They said they couldn't replicate the behavior and asked if I could record it, so I did and sent them the link. I posted here to see if other people notice this or if it's just me.

 

[Krabin]

My concern is the processor working too hard and causing audio issues and premature wear and tear, not really the accuracy of the nice meter decoration. If it's just me, I hope my unit's processor isn't defective. If it's multiple people, maybe there's a processor limitation (in which case I just either wouldn't use the VU meter or just stick to 16 bit), optimization issue (that could be solved in an update), or maybe even an intentional design choice to ensure processing power is directed towards audio processing for 24bit instead of the meter, which would actually make a lot of sense and I could totally be ok with.

 

[Saponetto]

You are not alone on this concern...

 

[Wiimer]

My concern is the processor working too hard and causing audio issues and premature wear and tear, not really the accuracy of the nice meter decoration. If it's just me, I hope my unit's processor isn't defective. If it's multiple people, maybe there's a processor limitation (in which case I just either wouldn't use the VU meter or just stick to 16 bit), optimization issue (that could be solved in an update), or maybe even an intentional design choice to ensure processing power is directed towards audio processing for 24bit instead of the meter, which would actually make a lot of sense and I could totally be ok with.

24bit /192kHz track from Amazon music played on Ultra. No abnormalities were detected in the movement of the original VU meter.

View attachment 1000001791.mp4


Here is 16/44.1

View attachment 1000001792.mp4


#Audio and needle delays are caused by the phone.

 

[Krabin]

24bit /192kHz track from Amazon music played on Ultra. No abnormalities were detected in the movement of the original VU meter.

View attachment 24236


Here is 16/44.1

View attachment 24237


#Audio and needle delays are caused by the phone.

Nice, I couldn't tell much (if any) difference in yours. This could be a Tidal or Tidal connect problem. I don't think it's caused by the phone because I'm pretty sure it streams directly from Tidal via wifi, not through my phone like bluetooth. My phone is just the controller for Tidal connect. I actually don't even need my phone: I can close the app on my phone and it still plays, and I can play the songs straight from presets on the display. It's certainly not the internet because it's cable internet that's consistently over 300Mbps (often at 600Mbps, streams 4k dolby vision with no problem), and the ultra is 2 feet from the router that covers my whole house. Also, I need to correct my initial observation: mine doesn't actually seem to have much delay, it just gets choppy, like 6-10fps.

 

[Wiimer]

Nice, I couldn't tell much (if any) difference in yours. This could be a Tidal or Tidal connect problem. I don't think it's caused by the phone because I'm pretty sure it streams directly from Tidal via wifi, not through my phone like bluetooth. My phone is just the controller for Tidal connect. I actually don't even need my phone: I can close the app on my phone and it still plays, and I can play the songs straight from presets on the display. It's certainly not the internet because it's cable internet that's consistently over 300Mbps (often at 600Mbps, streams 4k dolby vision with no problem), and the ultra is 2 feet from the router that covers my whole house. Also, I need to correct my initial observation: mine doesn't actually seem to have much delay, it just gets choppy, like 6-10fps.

I would like to add that perhaps my statement was misinterpreted.

"Audio and needle delays are caused by the phone."

I mentioned that this was an audio delay that occurred when I filmed and edited the video on my phone. There was no actual delay

 

[Krabin]

I would like to add that perhaps my statement was misinterpreted.

"Audio and needle delays are caused by the phone."

I mentioned that this was an audio delay that occurred when I filmed and edited the video on my phone. There was no actual delay

Ohhhh gotcha, yes I did misunderstand, thanks.

 

[kwd0405]

Hello,
Since I saw this post I've been testing this.
I think you are right.
I'm using a Wiim Ultra, with Qobuz via WHA into an USB dac. I've made 2 comparison video's. Both recorded in 60fps. In this test I'm using the 2013 Hotel California remaster, both available in 16-bit 44.1KHz and 24-bit 192KHz. Here is the first clip. This is the intro of the track. The top one is the 44.1KHz version, bottom one the 192KHz version. Important: the clips and sound are not synced due to it being recorded on a phone:
View attachment 20250718_195448.mp4
Now, I have also made a second clip the same way, but this time in the more "busy" part of the track(this video has no sound, sorry):
View attachment 20250718_195845.mp4
I can see a clear difference in the VU-framerate between both versions of the track, with the 192KHz version being more choppy than the 44.1KHz version. I'm curious what WiiM thinks of this?

 

[Krabin]

Hello,
Since I saw this post I've been testing this.
I think you are right.
I'm using a Wiim Ultra, with Qobuz via WHA into an USB dac. I've made 2 comparison video's. Both recorded in 60fps. In this test I'm using the 2013 Hotel California remaster, both available in 16-bit 44.1KHz and 24-bit 192KHz. Here is the first clip. This is the intro of the track. The top one is the 44.1KHz version, bottom one the 192KHz version. Important: the clips and sound are not synced due to it being recorded on a phone:
View attachment 24289
Now, I have also made a second clip the same way, but this time in the more "busy" part of the track(this video has no sound, sorry):
View attachment 24290
I can see a clear difference in the VU-framerate between both versions of the track, with the 192KHz version being more choppy than the 44.1KHz version. I'm curious what WiiM thinks of this?

Glad to know I'm not going crazy lol. I'm super curious what they think because all they've said so far is that they haven't been able to reproduce the issue on their end. In the meantime, I'm just not using the VU meter.