Bug Report: DLNA Streaming Issue in MediaMonkey Android (with MediaMonkey 2024 Server)

[hanspeters]

Summary: When streaming playlists via DLNA from MediaMonkey 2024 (Windows 11) to MediaMonkey for Android (latest version), playback consistently skips two tracks after playing one, with a brief “Server inaccessible” message appearing. This happens on a local network, without Android Auto involved.

Environment:

Server: MediaMonkey 2024 (latest version), running on Windows 11
Client: MediaMonkey for Android (latest version)
Network: Local WiFi (5GHz), no VPN, same subnet
File format: MP3 only, 320kbps bitrate
Playlist size: Irrelevant — issue occurs with both short and long playlists

Other DLNA clients tested: BubbleUPnP works flawlessly with the same server setup

Steps to reproduce:

Open MediaMonkey for Android on the same local network as the MediaMonkey 2024 server.
Connect to the DLNA server and browse available playlists.
Start playback of any playlist.
Observe: the first track plays, then two tracks are skipped, then the third plays, and so on.
A “Server inaccessible” message briefly appears during the skips.

Additional notes:

The issue does not occur when using BubbleUPnP or other DLNA clients.
Local file sync to Android works fine, and playback via Android Auto is stable with local files.

The issue seems related to playlist parsing or buffering in the Android app.

This behavior did not occur with MediaMonkey 4/5 on Windows 10.

Request: Please investigate the DLNA playlist streaming behavior in the Android app when used with MediaMonkey 2024. It appears to be a regression or incompatibility that affects usability, especially for users relying on Android Auto integration.

[Lowlander]

Which Build (Help > About) of MediaMonkey 2024 are you using?

[hanspeters]

2024.1.0.3113

[Lowlander]

Can you please send in a log from MMA and reply here with the logID?