2025-04-11, 04:34 PM
(This post was last modified: 2025-04-11, 05:58 PM by bitstream. Edited 3 times in total.)
After testing a bunch of combinations of clients with my two servers, it seems JF DLNA is a bit "picky" - some clients are working without issues (i.e. VLC, others have problems with limited functionality. The Synology Media Player is working with all clients I have tested without problem.
I couldn't find out why this is nor if the clients are implemented differently. I.e. I can imaging "next" could be implemented differently: It could be a "relative" command sent to the server, unstructing the server to play the next song in an album, but it also could be the client just stopping the current song and sending a play command for the next song in the song list the client has received before. I haven't tracked this down in detail, so I don't know if this is about different implementions. Fact is, JF DLNA is not fully working with every client.
--
Have to correct myself: VLC isn't fully working with JF. Browsing is buggy, listing does only work for "genres" and "albums", all other categories fail to list. So no browsing of trees and folders... Maybe it's a timeout problem? 420 Interpreters isn't that much, that should be read from an index within fractions of a second....
I couldn't find out why this is nor if the clients are implemented differently. I.e. I can imaging "next" could be implemented differently: It could be a "relative" command sent to the server, unstructing the server to play the next song in an album, but it also could be the client just stopping the current song and sending a play command for the next song in the song list the client has received before. I haven't tracked this down in detail, so I don't know if this is about different implementions. Fact is, JF DLNA is not fully working with every client.
--
Have to correct myself: VLC isn't fully working with JF. Browsing is buggy, listing does only work for "genres" and "albums", all other categories fail to list. So no browsing of trees and folders... Maybe it's a timeout problem? 420 Interpreters isn't that much, that should be read from an index within fractions of a second....