Still no fix…
Hi everyone,
We released an initial experimental fix for this that didn’t resolve the issue. This has obviously simmered longer than any of you would have liked. As soon as we have a conclusive course of action here, we’ll reach back out. Please hang in there just a little longer in the meantime.
Plenty of us prepared to try this out and help improve how it works
Another week and we’re still working on this, but I assure you I’ll at least provide more routine updates until we have something concrete to offer. Thanks again for everyone’s patience here.
Hi everyone,
The latest release did not contain any work related to this issue, but we’ve not lost track of it as an upcoming priority. I will post here as soon as we have more information to share on a timeline. Thank you again for your patience.
Hi everyone,
We don’t have an update on this ticket status this week, unfortunately, but I will post here as soon as we have additional information about an actual, realistic timeline to release.
Thank you for the regular updates.
Hi everyone,
The latest Early Access release contains some work related to this issue. This includes verbose diagnostic logging to help pinpoint the problem once and for all.
These changes will merge into the next public release, so there’s no need for anyone here to take action or migrate to the EA branch. That said, we may ask affected users to reproduce the problem once more in the coming weeks now that logging is enabled.
Thank you again for your ongoing patience.
Hi @connor I will try it a bit later and feedback.
More than happy for your to pull the logs from my server
Hi @connor I started sending a Chromecast display screen to the LG TV Shield CC device at about 23:19 if you want to have a check of the logs
It’s now into it’s second track and no waveform so far. Hopefully this helps with the investigation
Hi @Michael_Harris,
Thank you for sharing. The team wants to zoom in a little closer and has added some additional verbose logging. If you’re willing to give this (yet) another go, please reboot Roon Server twice and then attempt to use the Shield as a Chromecast display once more. This should be the final reproduction we require and we’re quite grateful for your help.
Hi @connor and thanks for that I am more than happy to do that.
I will do that in a while and send you an update later
Hi @connor I have restarted the Room App on my Mac Mini several times to make sure it’s all good to help you
I have tried a couple of display settings and the first track on the first device gave a waveform but it timed out after about two minutes and then subsequent tracks regardless of displays did not show any waveforms.
Hopefully you can get some decent log information from this
Hi @Michael_Harris,
Thank you again. Ultimately, we’re trying to pin down a constellation of different failure cases, so as many times as you’re able to test the waveform display (and have something with the waveform break), the more thoroughly we can document that particular failure pathway with this logging enabled. That said, if it’s truly outside your listening flow to rely on the display, you don’t have to keep toying around with the feature. We appreciate your help either way.
Hi @connor I am happy to test this in various ways and let you know the results.
Do you want me to feed back with time stamps and photos, or just let you know the results.
I understand the different constellations of issues as I have probably seen most of them across the different platforms of pure google Chromecast, Google Smart Display, LG TV and Nvidia Shield. I have mostly focussed on the Shield device as that is my main device connected to the TV. I will be happy to check others and feedback on those at a later point
Hi @connor I started a playback session at around 23:52 tonight and no waveform
A bit of late night atmospheric Icelandic Black Metal
Hi @Michael_Harris,
Thank you once again. To answer your questions above: the Shield is the ideal device for starting here. If you’re able to share the track name, that should be sufficient to find the event in logs, but photos are always fine too.
Thanks @Connor Probably not the best choice there.
I will pick something a little more pronounceable later tonight and save myself the screenshot by just typing the details in.
The Shield is my go to device so that is what I would normally use unless you want to see some other options
I am in Vienna for the next few days but when I am back, I am happy to help test this with my shield if you like addtional data?