BowsAndArrows
Senior Member
final note on testing - EQ doesn't seem to work when using DLNA out. i'm assuming this is probably the desired/expected behaviour? but worth noting nonetheless...
Have you submitted a ticket to support yet? Mine has been "Pending Eng Review" for 4 days now, so hopefully there will be an improved DLNA Cast Beta released soon.this is exactly what i hear when trying to play via audiophile UPnP renderer... maybe the cause of the issue is similar?
some more reports on testing:
all sources tested seem to work fine with JRiver UPnP renderer. e.g. chromecast, WHA, UPnP from LMS/audirvana. haven't tested airplay yet.
also noticed that the software renderers sometimes do not appear in WHA when you click on pair for DLNA out... this tends to happen during playback and especially when switching sources - e.g. from playing audirvana via UPnP to wiim then switching to qobuz within the WHA. this persists despite restarting the software renderer apps on my windows PC. even a reboot of the WiiM pro does not seem to resolve the issue. i can't seem to reliably demonstrate what causes it, and the only fix is rebooting the windows PC, it seems.
when the DLNA out gets disconnected - this causes music to start playing from the previous output selected. which probably shouldn't be the default behaviour. it should revert to the previously used source - but imo it should pause by default - not continue playing...
#506456 is the number corresponding to the crackling noise issue.Have you submitted a ticket to support yet? Mine has been "Pending Eng Review" for 4 days now, so hopefully there will be an improved DLNA Cast Beta released soon.
I believe WiiM are restricting the amount of data they're delivering to renderers in an attempt to keep things in sync, as best they canalso noticed that sometimes streams randomly need to buffer in JRiver - even though my LAN/WLAN/WAN bandwidth shouldn't be an issue.
#506457 - update on the volume control. this does not work as expected when using UPnP as a source (LMS or audirvana in my case). the volume on my PC just goes to 0 whenever i try to change the volume from audirvana, LMS or WHA.i've tested this with a couple software UPnP renderers on windows 11.
getting garbled audio and really distorted loud sounds when using audiophile renderer.
working ok with JRiver media center UPnP renderer on windows, although I've noticed some odd behaviour... when listening to any kind of track from qobuz- the WHA shows the track quality as CD - 16bit/44.1kHz although with slightly different kbps numbers ranging from 800kbps-1100kbps (regardless of the actual bitrate of the source tracks - even 24/96 tracks show up the same). However in the JRiver MC - they all show up as 320kps. when playing.is this for compatibility reasons??sorry just seen the compatibility note from WiiM team. how are all the tracks all showing up as CD quality in the WHA but with different bitrates that don't match the source quality??
play/pause button in WHA is not always working when using JRiver as renderer and when it does there is a delay. although volume control is fully functional and changes my windows system volume from the WHA when playing via UPnP?? didn't even know this was possible... how is the UPnP controller able to take control of my windows systems main audio volume so easily??
It’s already been said that 24/48 is the limit for DLNA cast, with it currently being constrained to 320kbps MP3I hope DLNA / UPnP output can work
And up to PCM 192kHz
Please @WiiM Support @WiiM Team
I signed to beta 2 weeks ago but still not enabled - i used the forum
My support ticket #506208 is Still "Pending Eng Review" for 9 days now, I was hoping for a new beta to fix my issues.Have you submitted a ticket to support yet? Mine has been "Pending Eng Review" for 4 days now, so hopefully there will be an improved DLNA Cast Beta released soon.
I’m on that beta too and not too concerned that it hasn’t yet been updated. It might get updated this week or next, who knows. However, if you don’t wish to wait, I’m sure WiiM will put you back on the public firmware.Thanks Brantome. It doesn't say Beta, just 4.8.621028 as of this morning. So I did just submit a ticket...
I would appreciate your thoughts on following though:
The reason I want to leave the Beta is that although the Wiim Pro Plus of mine that I entered into the DLNA Cast Beta program (and shows the DLNA Out) updated itself only once over two weeks ago to 4.8.621028 and has been on that version ever since. My other Wiim Pro Plus on the other hand, which is not in the Beta (shows no DLNA Out), is now at a higher version as of this morning at 4.8.622549.
I wouldn't want one of my Wiim Pro Pluses to get stuck in a "non-functional Beta but not Standard either" limbo state, not updating either way. Can you confirm these version numbers as being current?
Why can't they correctly label the beta firmware as beta? This isn't the first time it has happened.I’m on that beta too and not too concerned that it hasn’t yet been updated. It might get updated this week or next, who knows. However, if you don’t wish to wait, I’m sure WiiM will put you back on the public firmware.
My Pro Plus is on that version, which isn't marked as a beta, but I have removed my other three devices from the DLNA Cast beta, because it isn't useable for me in the current version.I’m on that beta too and not too concerned that it hasn’t yet been updated. It might get updated this week or next, who knows. However, if you don’t wish to wait, I’m sure WiiM will put you back on the public firmware.
It was correctly labelled on the versions for the Amp, and Pro, but not the Pro Plus.Why can't they correctly label the beta firmware as beta? This isn't the first time it has happened.
Were your three devices that you removed marked as Beta and you used the Remove button to remove them as Brantome said, or did you open a ticket?My Pro Plus is on that version, which isn't marked as a beta, but I have removed my other three devices from the DLNA Cast beta, because it isn't useable for me in the current version.
Hopefully a fixed version will be released soon, and I can continue to test it on my Pro Plus.
It was correctly labelled on the versions for the Amp, and Pro, but not the Pro Pl
Ok, I get it now. Yes, looking forward to the Remove button on the Wim Pro Plus...It was correctly labelled on the versions for the Amp, and Pro, but not the Pro Plus.
Yes, they were correctly labelled as Beta, and I was able to switch to the stable release firmware.Were your three devices that you removed marked as Beta and you used the Remove button to remove them as Brantome said, or did you open a ticket?
Other DLNA players that I am used to allow the user to set the maximum sample rate when sending to a DLNA renderer. Anything higher than that level is then down sampled to the specified rate. And, not being able to send a 16/44.1 at its original rate it not the action I would expect. Hopefully at some point the user will be able to set the maximum sample rate to send and lower rates will not be resampled.Guess it doesn’t have a way of finding what resolution target speakers can play and maybe then play the lowest common denominator, so it’s pitching the resolution at 24/48 that you’d expect most targets to support. Plus, I must admit, I’ve often argued that 24/48 is sufficient for multi room / “party mode” playback anyway, but the other side of me still likes to see bigger numbers