Amazon Music -> Shairport-Sync + Metadata -> OT only shows first song played and never updates after that song ends #1358
Comments
|
This seems mostly related to the metadata pipe. As mentioned in issue #1357 the implementation of the metadata pipe has changed since 28.2, so I would have to ask you to try updating to that. |
|
Okay, I'll try to do that.. Which of course means I need to figure out how to rebuild the RPM from git instead of a release tarball (unless there is a 28.3 coming "soon") ;-) |
|
As I mentioned in #1357 the master tarball appears to solve the metadata overload issue. However this issue is still there, so I need to turn up the logging, which I've just done. I'll let you know what I see shortly. |
|
Hmm. I set But now I don't see anything more. SO.. Either shairport isn't sending anymore metadata, or something else is going on. Indeed, just running: ... and that's the end, which is from 3 minutes ago, even though music is playing right now through the system and the metadata page in the OT shows 7:54/4:05 (and counting). I sat there for a while and eventually (without me doing anything) the logging continued: But no metadata in these logs, even though there was yet another song change. |
|
One more piece of added information: If I stream Amazon Music my wife's iPhone then the metadata updates properly across songs, so it's probably on the source side and not on the OT side. Although that still doesn't explain why logging stops for 6 minutes. |
|
You can verify whether OwnTone is reading and processing metadata correctly by simply writing to the metadata pipe like shairport-sync does. You can, for instance, run this command, which will change the title (provided OwnTone is playing the associated audio pipe):
I will close the issue for now, but let me know if there is an issue on OwnTone's receiving end. |
|
I wonder if there is an incompatibility somewhere. I'm doing: This shows me that there is a change... I can see the change from Wait to Bad Habits to When I Was Your Man, but OT isn't reading it or updating itself with the data.. I wonder if the metadata changed between Airplay1 and Airplay2? Let me capture some raw data and upload it manually and see what happens... |
|
UGGH.... So it worked manually... And then I restarted shairport-sync and it's all working now... UGGH! |
|
Are you using a permanent pipe or is shairport-sync creating it on the fly? If it is the latter, do you then know when the pipe is created? I'm thinking if there could be a timing issue, i.e. 1) sps start writing audio, 2) ot detects audio, looks for metadata pipe, doesn't find one, 3) sps creates metadata pipe --> too late. |
|
I've tried it both ways. While it could be a race condition, I suspect it's something else... MikeBrady suggested that it might have been an issue going between AP1 and AP2. It's certainly the case that AP1 only supports metadata when the stream starts; updating in-stream is an AP2 feature. However when I first started testing with AP2 it hadn't changed behavior, but then I stopped testing for a while (several hours) and when I came back to it, it worked. So the current theory is that the Mac was caching info about the AP endpoint and had to wait for the cached data to expire before it acknowledged that the endpoint was AP2. Regardless, it seems to be working now. The only thing I need to check is that it continues working on system reboot / restart. |
I was using Amazon Music on a Mac to drive OwnTone via Shairport-Sync. I have the metadata pipe enabled.
When I start AmazonMusic and send the output to SP-S that sits in front of OT, I get the metadata for the first song. During that first song I get a progress bar and everything. However, I never get anything for any subsequent songs. The OT UI always shows that first song and never updates after that song ends.
If I pause play and way for a bit, when I restart play of Amazon Music, I get the
Source is not providing sufficient data, temporarily suspending playbackerror, and then if I try to play again it fails and falls back to Internal speakers; when I restart Airplay to Whole House it sends the current metadata over (song title/artist/playtime).If I click into the metadata popup on the OT WebUI, right now it's actually still counting up. So it's displaying the "first" song title and length, but it says "6:01 / 3:54" (and the "6:01" is counting up as the next song goes).
If I pause play, count to three, and then restart (so it doesn't empty the pipe), the music pauses for a bit but the metadata doesn't update to the new song (but it does keep counting up).
Similar to my other issue, is there a good way to turn on metadata debugging to get OT to print out the metadata it's receiving?
The text was updated successfully, but these errors were encountered: