I'm having trouble playing music
Playback starts, but I don't hear any music
My newly-acquired JBL Charge 5 WiFi shows up in my audio choices, and I'm able to select it to play to, the icon shows as if it's playing, but no sound plays and the play-clock stays on 0:00 indefinitely
Roon supports AirPlay but not AirPlay2. Read also:
I noticed that thread, but the documentation for the Charge 5 WiFi only mentions Airplay. Additionally the general consensus seems to be that Airplay 2 devices are usually backwards compatible. But it seems likely that isn’t the case for the JBL products
To control this AirPlay 2–enbled speaker, …
You can safely add Samsung soundbars to that list:
Potentially many other recent consumer products may suffer from the same issue too.
Ugh - I wish they’d be clear about their products - this stuff matters.
Odd that they’re not shouting that it has the latest and greatest version. I checked their website and it always mentions Airplay - the Airplay 2 info is either not present (most pages) or hidden in smallprint.
What a shame. I picked it specifically for its Airplay capabilities because I thought it would work with Roon.
Does its ChromeCast-built-in not work (with Roon)?
Are we just guessing about this or is their any hard evidence to support this claim. Given its an unofficial Airplay implementation iin Roon its hard to tell. It would be strange for them to have a different API that is not backwards compatible anymore. You would expect this on thier own speakers to but doesnt seem to be an issue.
Just becasue it only says Airplay 2 doesnt mean much. Apple only refer to it all as Airplay and certificaion should work for either implementation. My JBL Link Music only mentions Airplay 2 and works fine with Roon. I think something else might be at play here. But without any hard evidence this is all a bit of guesswork, be good to try Airplay to it with an older version of iOs or MacOS that doesnt run Airplay2.
While this is fine in isolation (and works when I tested it) it’s not helpful when my house-wide system is built around being Roon Ready in the first instance and then Airplay ready as a backup, which means grouping becomes an issue when the product doesn’t comply.
First world problems, sure, but it’s still not a great experience for the consumer. Appreciate the help though!
Good idea - will look into it because I have an old MacBook Pro lying around which is extremely unlikely to be Airplay 2 compliant
I linked relevant forum threads, Roon Labs response and external sources. More sources may be uncovered by reading the linked threads or/and searching for other, similar threads on the forum. The affected users experience is also a hard fact I think. As I already mentioned, also recent products from other brands suffer from the same symptoms. Speculation: Maybe tied to a specific SoC (generation).
Maybe now that Roon is part of the Harman family, as well as JBL is, owned by Samsung, Roon Labs may investigate this matter (again?) and can come-up with a definitive answer.
That sounds plausible, maybe some odd implementation on some devices.