In an attempt to solve this infuriating problem I bought a NUC and installed Rock. I also bought a new router, one recommended by Roon (Asus AC68U). Has it helped? Has it sausages!
I’m glad I finally pressed the button on a Rock device and I’m pleased with my new router but the fact remains that all this investment of money and much time hasn’t solved a problem which did not exist until the latest iteration of Roon.
My only remaining option is to buy a Raspberry Pi to use as my wireless endpoint. Or, perhaps, it’s not too much to ask that the code which got broken is finally fixed? This has dragged on for far too long and, frankly, smells of contempt towards those of us who have invested in a supposedly premium product.
Margaret, i have ended my subscription for Roon.
It’s really poor service when you mess things up for your users with a bad software update and leave it like that for 3 month. It’s so enoying with this bug that you stop using it efter a few day. No offer of a discount for a new subscription.
I don’t think this is a premium product, because premium gives you the support your paying for.
Hello Jonas. Yes, I very much understand! I would cancel my subscription, too, but there’s no comparable software to be had (more’s the pity). I’ve tried them all over the years and Roon has been the only one that allows me to enjoy my music collection in purely digital form and not miss the old days of simply choosing a CD from my bookshelves. I struggled for years with JRiver, which can do pretty much anything one asks but is a bloated, dated-looking mess and demands a ridiculous amount of housekeeping - fine for the types who used to enjoy stamp-collecting and train-spotting but not for me.
I continue to hope that Roon’s engineers will get to the bottom of this before long. A little reassurance would go a long way to soothing my discontent. Meanwhile, I am currently researching Raspberry Pies…
Same issue here all of a sudden with CCA and Qobuz. This bug only affects 44.1 kHz, everything else works. CCA works fine with other applications, just not with Roon (anymore).
(NUC 8i7 and Asus RT-ac88u. router).
I’ve tried around a little and can add a few details:
The issue only affects the Chromecast Audio dongle. Chromecast built-in still works perfectly for me with two devices.
The problem only affects 44.1 kHz.
48 kHz and everything above works without any problems.
I suspect that a Google Chromecast Audio update caused it.
I currently have CCA Cast firmware version: 1.42.172094 DE, Germany.
Problem did not come with Chromecast Audio update, it occurred with last Roon core update. A lot of people here are saying same thing, when updating core the 44.1 kHz tracks have problem after. And this only affects Roon and not other software streaming 44.1 kHz to CCA.
Hi Jonas,
couldn’t that be just pure
coincidence?
I myself had no problems after the last ROON update.
For months.
The problems only came yesterday, after the last CCA update here in Germany.
Regards,
Axel
I suppose a way around is to resample everything in roon to 48 or above.
Unfortunately it only works partially.
I found that it works for 44.1 kHz and 16 bit, but not for hi res files with 44.1 kHz and 24 bit.
My signal paths:
What is this? A more than 3 months old unfixed serious bug? That came with a new release that broke backwards compatibility. And no activity/dead silence from the staff? On a 700 dollar supposedly premium consumer software?
Until people start to cancel their subscriptions or claim refunds, this situation will not improve. More than anything it is a sign of the typical conformity and disinterest of so many software companies who have grown too quickly.
I suggest trying out Plex. They are riddled with absurd bugs themselves, but have come a long way lately, and at least they are not overcharging for a faulty product.
Hello everyone, @ask,
let us keep things in perspective please and
not allow ourselves to be carried away …
I have tried a few more things:
As an experiment, I disconnected my NUC 8i7 from the Asus RT-AC88U and connected it to my other LTE and 5G router, Huawei 5G CPE PRO 2 (H122-373).
And lo and behold, everything works out here with the other router!
Like it should and the way it worked right before.
But why the hell is that now?
And who can be blamed for the CCA not working right with Roon before?
A Roon update?
A Google update?
An Asus update?
Or an AVM update, because the Asus router hangs as an acesspoint behind a AVM FritzBox 7590?
Sometimes things are too complex to be decided so easily.
Let’s enjoy the music,
Axel
Yes Axel, of course it could be. But i find it most unlikely as it stoped working correct by the second Roon was updated.
And if it´s some kind of compatibility problem between Roon - CCA driver or Roon - Asus. Then i think Roon have a lot easier to find this problem and report it to Google or Asus. Me as i user can´t contact google and telling them that CCA driver is faulty because Roon doesn´t work, but everything else does.
Buying this product claiming to support CCA we should at least get the support to find out why it doesn´t work anymore. If then it´s a CCA driver problem, just let us know so and we can report it to Google.
I tested activating DSP and Sample Rate Conversion for 44.1 kHz 16 bit that doesn´t work. Set it to Max PCM rate (power of 2) and it will give you a 88,2 kHz 24 Bit signal instead.
Problem is gone!
So for know activating this function to all your CCA will let you enjoy music without interupt.
One small thing is that you should have your device setup and MQA Capabilities set to “Renderer Only”. Otherwise it well resample MQA also.
I just bought one of these Ethernet OTG adapter cables for my Chromecast Audio, and this seems to have fixed the playback pause issue. It also speeds up playback starting in general and stability etc. For just £9 I can highly recommend!
Joining and subscribing to this thread. Have been a long time regular Roon user. Hoping this is resolved soon. Reverted to mostly streaming from my phone to CCA directly, avoiding using Roon altogether for now.
They have usually been pretty quick to fix things broken with updates, which is why I had thought the problem was on my end.
