What’s happening?
· Other
How can we help?
· None of the above
Other options
· Other
Describe the issue
Tracks above 44.1khz do not play
Describe your network setup
Silent angel z1 plus
@Serkan_Emsal
Can you tell us somewhat more details, like if you are playing local files or streaming? If streaming, Tidal; Qobuz, …?
What type is your streamer? How is it connected? …
Kind regards, Frank.
Dear Frank,
Thanks for quick reponse,
I am using qobuz and one hour ago there was no problem.It is weird now track above 44.1khz do not play.
Qobuz
Silent angel Z1 plus
Samsung s24 ultra
Denafrips pontus2 12th dac
Regards,
Please share a screenshot of the Signal Path when this occurs.
Roon is clearly playing the 96 kHz 24-bit recording, and this is sent to the Rhein Z1. What happens after this is not shown in the signal path, but you can see clearly what Roon is doing (or not doing in this instance.)
My guess is that you have inadvertently changed a setting in the streamer or DAC.
Did you go to Muse and turn Sample Rate Conversion off?
Check your DAC. Not sue why it would reject these files.
If all fails you can simply just set Roon to upsample everything to 96k. I know this is not ideal coverting 44.1 to 96k, you could set sample conersion of everything to 88.2 or 96 if it plays 88.2k files
I did check all chain, everything is ok, I could not understand
I did it:(
Roon is already sending 96 kHz to the streamer, so this isn’t going to help, unless you mean to downsample everything to 44.1 kHz.
Can you play these files in another zone? Furthermore, try rebooting the server, and restarting the streamer and DAC. Since Roon is playing the file, i.e., sending a PCM stream to the network streamer, and it’s not playing through the zone, it is unlikely to be Roon. Testing Roon on another zone, even a mobile device, will confirm this, so you may focus on other items in the chain, i.e., the Denafrips audio device, which appears to be running Linux.
Hi @Serkan_Emsal,
Thank you for your post. According to your screenshot, Roon is delivering 96KHz audio to ALSA successfully - do you see any error messages presented by Roon? RAAT has no control over how the DAC will handle audio once it’s been passed off in the chain.
The failures in this case appear to be downstream of Roon and within the endpoint firmware. Verify your firmware/drivers are up to date. Please also review the steps suggested just above by @mjw.
Thank you so much, I found the problem at last ; i2s cable.
But now I saw red alert on roon; qobuz login failed retry or edit
Hi @Serkan_Emsal,
Thanks for the update! I’m sorry to say, but unfortunately, the server you’re using - the Rhein Z1 is not a Roon-supported device, and therefore we’re not able to offer any official troubleshooting support while it’s in use.
I’d check out your Roon Settings>Services>Qobuz and attempt to re-login. If that doesn’t help, rebooting your server device and router may help.
Outside of this, we’ll move your thread over to our Tinkering section, where others from the community who also use similar servers may be able to help further. Thank you for your understanding! 
Thank you, what does it mean; not roon-supported, we can not use the z1 plus as roon core anymore?
I guess it means that it may or may not work. As it is not supported by Roon.
The same thing is true for my little computer. It isn’t supported by Roon. But it runs Roon Rock great.
Roon has a “hardware library” of all Roon Ready and Roon Tested devices, so they are able to provide support. This is one aspect of the certification programme.
Unfortunately, the manufacturer of the Rhein Z1 has chosen not to get it certified.
Regarding the login issue, I suggest using a mobile device to perform the login, making sure that the OS default browser is used. A common reason OAuth fails is that the token isn’t shared between the app and web browser
I’ ll try it, thx a lot
1 Like
AJ
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.