[mythtv] Yamaha DLNA compatibility

[Chris Jewell]

Hi Rune,

Sorry for the delay — it’s taken a while to get a good packet capture with associated mythbackend log.  Thanks for your offer of help!  I’m not a packet capture specialist by any means, but it looks as though I’ve a slightly flakey wifi, possibly on the MythTV server itself.

Capture: https://lancaster.box.com/s/6tcmyop665rp8uwwpm0ahd1gguxvlnib
Log: https://lancaster.box.com/s/igdoz8uf5uz5scuwfs7zj1u0chfem2i8 <https://lancaster.box.com/s/igdoz8uf5uz5scuwfs7zj1u0chfem2i8>

Hifi: 192.168.1.103
MythTV server: 192.168.1.110

You can see that track id 2728 plays fine.  Track 2729 is then requested twice, due to a RST packet from the MythTV server.  Playback of 2729 is cut short by a TCP RST packet sent from mythbox to hifi, and playback moves on to 2730.

So, flakey wifi on the MythTV server, or intolerance of a flakey wifi by mythbackend?

Cheers,

Chris





> On 4/02/2017, at 11:22 PM, Rune Petersen <rune at megahurts.dk> wrote:
> 
> Hi,
> 
> I did some DLNA work some time ago, I may be able to help.
> 
> Can you provide a Ethernet capture of the interaction between the 2 devices?
> 
> 
> Rune
> On 04/02/17 20:15, Chris Jewell wrote:
>> Hello Developers,
>> 
>> I’m trying to debug an interesting problem with a new Yamaha CRX-N470D hifi system.  It has DLNA capability (specifically bought to interact with my mythtv mediacenter), and is able to browse my music collection on the mythbox.  However, it only seems to play the first 2’36” of whichever song I select, before moving on to the next song in the playlist.  My Android client plays fine.
>> 
>> From the mythbackend.log (link below), I suspect this is something to do with how the hifi is requesting the music files.  Firstly, there is no Keep-Alive header in the request (which there is with the Android renderer), and secondly, the request appears to have a range.  Is this expected?  Also, it looks like the HTTP connection is timing out — as though the hifi stops listening?
>> 
>> Annoyingly, the hifi works fine with other DLNA servers such as UMS.  I’d like to get a handle on what’s going on with myth, and possibly contribute to a patch.  Can anyone assist me in understanding what’s going on?
>> 
>> Thanks,
>> 
>> Chris
>> —
>> Mythbackend.log: https://lancaster.box.com/s/e1t249tol8rkpk4cqqnyc2vg9ogkb5w8
>> 
>> Server config (with hostname and address for logfile purposes):
>> Hostname: cobalt
>> Address: 192.168.1.110
>> OS: LinHES R8.4
>> MythTV version: 0.28-fixes from LinHES repo. (updated this morning)
>> _______________________________________________
>> mythtv-dev mailing list
>> mythtv-dev at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>> 
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20170207/453727ca/attachment.html>