2025-04-11, 01:38 PM
(This post was last modified: 2025-04-11, 01:39 PM by bitstream. Edited 1 time in total.)
I got a DLNA client A, a Synology DLNA server and a JF DLNA server. Both server are currently running in parallel while I'm testing JF with the intention to replace the Synology.
Testing with music media, Synology is supporting the whole functionionality the DLNA client is offering: Browsing, play, stop, pause, next, previous, reapeat modes, random, loading cover picture. Interestingly on JF only browsing, play, stop, pause, loading cover picture are working.
I was assuming that next, previous, reapeat modes, random are client functionality which have nothing to do with the DLNA server. Same for Random and Repeat modes. Form the observed behaviour, this does not seem to be the case, it seems the DLNA server is involved somehow (wasn't able to find more information about this yet).
Before i start digging deeper, does someone know if
My next steps would be to
Testing with music media, Synology is supporting the whole functionionality the DLNA client is offering: Browsing, play, stop, pause, next, previous, reapeat modes, random, loading cover picture. Interestingly on JF only browsing, play, stop, pause, loading cover picture are working.
I was assuming that next, previous, reapeat modes, random are client functionality which have nothing to do with the DLNA server. Same for Random and Repeat modes. Form the observed behaviour, this does not seem to be the case, it seems the DLNA server is involved somehow (wasn't able to find more information about this yet).
Before i start digging deeper, does someone know if
- this indeed is server side functionality?
- if this is supported by the DLNA plugin and known to be working?
- In case it is supported, where I could have missed something/why this is not working in my installation?
My next steps would be to
- try to find a DLNA specification
- tcpdump ing the communication