Pro Plus: Chromecast & Qobuz

Joined
Oct 25, 2022
Messages
12
When I Chromecast Qobuz to my WiiM, I started seeing 16 bit, 44.1khz as max Chromecast quality even though I have my Qobuz app set for 96/24. Is there a setting I messed up?
 
Then i said that? I just stated fact that problem not only with qobuz, and what is most important, this problem not about wiim.
I'd love to understand what you're saying.

Edit:
You did literally say:
At the same time, same thing happened with Tildal.
Assuming that Tildal was meant to read Tidal, there is now way Google Chromecast would interfere with Tidal Connect in any way. Please clarify your point.
 
Last edited:
Yes, it does! I can Google Cast Qobuz 24/96 to a Wiim Pro and CA Evo 150.
That's interesting. As I said, I cannot talk about Qoboz, but using Tidal hi-res files I see my Tidal App on Android flipping from 24 bit 96 kHz to 16 bit 44.1 kHz immediately if I start streaming to a Chromecast group made up of the WiiM Amp and the WiiM Amp Pro. My 1120 is currently not in use so I can't add this to the group.

PS:
Looks like 24 bit content at 44.1 or 48 kHz is playing fine.
 
You did literally say:
Don't read it literally.
Of course, we are not talking about the fact that I am trying to listen to both chromecast and tidal-connect at the same time. The point is that previously, both tidal and qobuz allowed chromecasting in 24/96 resolution and at about the same time this became impossible, and both of these services can now only chromecast in 16/44 resolution. But this does not mean that chromecast in principle no longer allows the use of hires, and evidence of this is bubbleupnp from which you can still chromecast hires without problems. By the way, the desktop application qobuz also allows you to use 24/96 with chromecast.
 
Of course, we are not talking about the fact that I am trying to listen to both chromecast and tidal-connect at the same time.
Nobody said you would.
... both tidal and qobuz allowed chromecasting in 24/96 resolution ...
How did you manange to chromecast using Tidal?

Things would be a lot easier if you mentioned how exactly you are using your 1120 and WiiM Pro Plus. One more time: Even if there was an issue with the latest Chromecast API (which I cannot confirm) it wouldn't affect Tidal Connect. Qobuz on the other hand does have well documented issues (right in this thread) with Chromecast.

Are you using a Chromecast group consisting of your 1120 and Pro Plus or not? Please be really clear this time.
 
How did you manange to chromecast using Tidal?
Looks like you trolling me.... But its ok....
1)I disable tidal in Lyngdorf settings.
Screenshot_2024-10-28-08-16-19-565_com.android.chrome.jpg

2) Open Tidal app and choose Lyngdorf as endpoint:
Screenshot_2024-10-28-08-09-36-871_com.aspiro.tidal.jpg

3)Open album with hires tracks:

Screenshot_2024-10-28-08-11-49-544_com.aspiro.tidal.jpg

4) Start playing and now i see, what cast resolution is 16/44
Screenshot_2024-10-28-08-11-54-315_com.aspiro.tidal.jpgScreenshot_2024-10-28-08-12-27-988_com.android.chrome.jpg

Another option is to use desktop Tidal app. By the way, with desktop app i can choose Chromecast option in wiim and I will get the same result. Hires tracks will be casting as 16/44. I need to be "more clearly" in this case too?


Even if there was an issue with the latest Chromecast API (which I cannot confirm) it wouldn't affect Tidal Connect.
It don't. And I'm not saying what.


Are you using a Chromecast group consisting of your 1120 and Pro Plus or not?
No. I'm not using Chromecast group. But this does not relate to this issue in any way. As before DRC say, groups can be used with 24/96.

Qobuz on the other hand does have well documented issues (right in this thread) with Chromecast.
Can you point me there in this thread is "well documented"? I read whole thread and i only see what someone has reported about 16/44 max resolution with Qobuz Chromecasting, and some other trying convince them, what its only wrong displaying issue. But its don't. Qobuz mobile and Tidal apps have really limited resolution to 16/44 while using Chromecast and this happened not only with wiim. That's all.
 
Last edited:
Its last Lyngdorf firmware(April 23, 2024) with Chromecast built-in version 1.56.310669
Thanks, so it is nothing to do with Google Cast 2.0. The Chromecast version is the same as my Wiim Pro, which I can use to cast Qobuz at 24/96. I am having difficulty understanding the problem which seems to be a Lyngdorf problem.
 
Can you point me there in this thread is "well documented"? I read whole thread and i only see what someone has reported about 16/44 max resolution with Qobuz Chromecasting, and some other trying convince them, what its only wrong displaying issue. But its don't.
As the person who was “trying to convince” (with a rather extensive table of test results I must say) that it’s only a display problem in the Qobuz app, I can confirm that in my case that’s all it is - I can still Chromecast from the Android Qobuz app to my WiiM devices at 24/96, as confirmed by the Qobuz app now playing page and the display on my amp to which the WiiM devices are connected.
 
Thanks, so it is nothing to do with Google Cast 2.0. The Chromecast version is the same as my Wiim Pro, which I can use to cast Qobuz at 24/96. I am having difficulty understanding the problem which seems to be a Lyngdorf problem.
I've come to understand that taravasya is not asking for help in solving a problem but just wanted to inform us about his findings.
 
I have really offended the community and I apologize.

It seems that as a result of several coincidences, I got confused yesterday.

In short, qobuz does indeed correctly cast via the chromecast protocol in resolutions up to 24/96, and the only problem here is displaying the maximum possible resolution when selecting a playback device in the mobile application.

But! Tidal really seems to have completely limited the ability to cast via the chromecast protocol in resolutions higher than 16/44.
Yesterday I really had some problems with playing high resolution from Qobuz (I tried several different releases and all of them was play 16/44 instead of 24/96), and at the same time I discovered this limitation in Tidal, as a result of which I decided that the problem is globally with the chromecast.

In general, I again ask you to forgive me for my excessive persistence, or more precisely, stubbornness 🤦‍♂️
 
Last edited:
I have really offended the community and I apologize.

It seems that as a result of several coincidences, I got confused yesterday.

In short, qobuz does indeed correctly cast via the chromecast protocol in resolutions up to 24/96, and the only problem here is displaying the maximum possible resolution when selecting a playback device in the mobile application.

But! Tidal seems to have completely limited the ability to cast via the chromecast protocol in resolutions higher than 16/44.
Yesterday I really had some problems with playing high resolution from Qobuz (I tried several different releases), and at the same time I discovered this limitation in Tidal, as a result of which I decided that the problem is globally with the chromecast.

In general, I again ask you to forgive me for my excessive persistence, or more precisely, stubbornness
Thanks for posting that - hopefully you’ll appreciate that this is by and large a very helpful forum where a significant number of members go out of their way to relay their experience and offer their help. Cheers :)
 
With the last update, transmitting Qobuz from Wiim Home sounds like garbage, I also discovered that the Wiim equipment in the previous update in which the wiim pro plus acted as an Air Play 2 transmitter, that function was useful for transmitting to speakers of different brands compatible within the different rooms of the home, without synchronization problems and with the same audio quality, because grouping different wiim devices degrades the quality of the music in all the grouped devices except the one that transmits, very bad on the part of wiim, They should prioritize the multiroom hi res playback they are planning in the future.
 
On the other hand, I want to raise a ticket for this issue but wiim has changed its menu and I cannot find the option to raise a ticket, it seems that they do not want customers to request a solution to the problems they generate with updates, can someone help me with the route to raise a ticket?
 
On the other hand, I want to raise a ticket for this issue but wiim has changed its menu and I cannot find the option to raise a ticket, it seems that they do not want customers to request a solution to the problems they generate with updates, can someone help me with the route to raise a ticket?
Take a breath...

You should find the 'Send us feedback' option in the '... Settings' option in the bottom menu bar.
 
Back
Top