bpa wrote: > I think the estimated duration is the correct method - when I play the > 45:13 URL in Chrome - it too shows 45:13. > > The XML value is plain wrong. > > The question now is understand where the other number come from. > Multiple the various duration times by 12,000 to get a byte count and > then see if resulting byte count can be matched or made up from other > numbers (e.g. http headers) > > Code: -------------------- > > > HTTP/1.1 200 OK > Date: Wed, 17 Jul 2019 21:29:19 GMT > Connection: Keep-Alive > Accept-Ranges: bytes > Cache-Control: public,no-cache,no-store > Content-Length: 32611627 > Content-Type: audio/mpeg > X-Megaphone-Payload: 61c70cca-3e95-11e9-a347-6764b931d67a#16818903,8075ebe8-6c29-11e9-b4d7-3feddd76c857#32611804@c6980e12-9c35-11e9-89d5-6377425b6bc0 > X-Megaphone-Payload-2: #0#pre#1,61c70cca-3e95-11e9-a347-6764b931d67a#16818903#mid#1,8075ebe8-6c29-11e9-b4d7-3feddd76c857#32611804#post#1@c6980e12-9c35-11e9-89d5-6377425b6bc0 > Vary: Origin > Content-Disposition: attachment; filename="NBCN2041603079.mp3" > X-HW: 1563398959.dop024.lo4.t,1563398959.cds002.lo4.shn,1563398959.dop024.lo4.t,1563398959.cds050.lo4.c > > -------------------- > >
My head is still spinning, but I'll give it a whirl tomorrow. But I still wonder: LMS changes/calculates the duration some seconds after the podcast starts. So it uses the calculated time from that point on and not the XML time. Why stop early? QLMS [email protected] x64 (digimaster) with perl 5.28 dedicated to me. :D / QNAP 469L QTS 4.3.4 ------------------------------------------------------------------------ dolodobendan's Profile: http://forums.slimdevices.com/member.php?userid=67663 View this thread: http://forums.slimdevices.com/showthread.php?t=109017 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
