tracks stop before end

[besbax]

Hello Simon
With my MinimServer installed on QNAP and Synology NAS, after updating to version 2.2 265, some songs stop before the end. For example, a song lasting 3.48 minutes always stops at 2.58 minutes. When using other servers, such as Assett, everything works normally. Since MinimServer is indispensable for me, what can I do?

[simoncn]

Please provide the following information for one track that is stopping before the end so that I can investigate what is happening:

1) What is the filetype of the track (e.g., FLAC, MP3, DSF, M4A)?

2) Are you transcoding the file using MinimStreamer? If so, please post your MinimStreamer configuration settings.

3) Are there any error messages in the MinimServer log when the file is scanned or when the file is played? If so, please post the exact wording of the message(s).

[besbax]

Hello, thank you for your reply.
All tracks are FLAC, no transcoding with Minimstreamer.
These are the log messages during track streaming:

15:00:00.610 Thread-22: Monitor response: SaveProperty
15:00:00.610 Thread-22: ErrorMsg=
15:00:00.628 Thread-23: Monitor action: SaveProperty
15:00:00.628 Thread-23: version=2, adapter=192.168.1.123, uriPrefix=http://192.168.1.123:9791/7cf0caae-02e5-4713-8a19-6367402db5b8/Upnp/resource/, clientEndpoint=192.168.1.10:53285
15:00:00.628 Thread-23: ComponentName= PropertyName=logLevel PropertyValue=debug
15:00:00.628 Thread-23: saveProperty: compName=null propName=logLevel propValue=debug
15:00:00.628 Thread-23: getSaveValue: compName= propName=logLevel propValue=debug saveValue=debug
15:00:00.628 Thread-23: writeConfigProperty: propFullName=.logLevel propValue=debug
15:00:00.765 Thread-23: updateActiveProfile: propFullName=.logLevel
15:00:00.766 Thread-23: RootContextImpl: called writeActiveProfile
15:00:00.766 Thread-23: writeActiveProfile: activeProfile=default
15:00:00.766 Thread-23: writeProfile: default
15:00:00.800 Thread-23: writeActiveProfile: activeProfile=null
15:00:00.800 Thread-23: writeActiveProfile: activeProfile=null
15:00:00.800 Thread-23: writeActiveProfile: activeProfile=null
15:00:00.800 Thread-23: writeActiveProfile: activeProfile=null
15:00:00.800 Thread-23: writeActiveProfile: activeProfile=null
15:00:00.800 Thread-23: writeActiveProfile: activeProfile=null
15:00:00.800 Thread-23: writeActiveProfile: activeProfile=null
15:00:00.800 Thread-23: Monitor response: SaveProperty
15:00:00.800 Thread-23: ErrorMsg=
15:00:49.288 Thread-197: FileResource: waitForFull returned true
15:00:49.288 Thread-197: FileResource: close
15:00:49.288 Thread-197: ServerResourceBase: close
15:00:49.288 Thread-199: FileResource: waitForEmpty caught InterruptedException
15:00:49.288 Thread-197: HTTPConnection: completed request; socket=Socket[addr=/192.168.1.201,port=1079,localport=9790], keepAlive=false
15:00:49.288 Thread-197: HTTPConnection: writer thread interrupted
15:00:49.288 Thread-197: HTTPConnection: stopping connection
15:00:49.288 Thread-197: HTTPConnection: closing Socket[addr=/192.168.1.201,port=1079,localport=9790]
15:00:49.288 Thread-197: HTTPService: removing connection org.jminim.lib.HTTPConnection@3ac4a72f
15:00:49.289 Thread-198: HTTPConnection: connection closed by client
15:00:49.289 Thread-198: HTTPConnection: requestStop request=org.jminim.lib.HTTPConnection$Request@6c5530f8
15:00:49.289 Thread-198: HTTPConnection: stopping connection

the error occurs randomly in 30% of tracks.
Please help me.
Carlo

[simoncn]

Please create a debug log file that covers playing the whole track, starting from before you press play and finishing after the music stops unexpectedly.

Zip or compress this log file (this step is important) and attach the compressed file to a post here. Do not post log messages inline.

When I see the complete log file, this should help me understand what is happening.

[Shaun]

Hi I am having the same issue since the latest update to minimserver.
i have attached a zip file of the log file of the event happening
It does it on all file types and pretty much every track i try to play.
I am not transcoding

[simoncn]

(16-12-2025 18:16)Shaun Wrote:  Hi I am having the same issue since the latest update to minimserver.
i have attached a zip file of the log file of the event happening
It does it on all file types and pretty much every track i try to play.
I am not transcoding

I have checked the log file and I see that MinimServer is responding correctly to streaming requests from the renderer,. The renderer is closing the audio stream that MinimServer is sending, then requesting the stream again. The cycle repeats until the renderer gives up, then moves on to trying to play the next track.

This could be caused by a network issue or possibly by some change to how MinimServer is sending the stream. However, there have been no recent changes to how MinimServer is sending the stream. What was the previous version of MinimServer that you were using that worked correctly? Are you able to revert back to this version to produce a comparable log?

[Shaun]

Hi
After some more investigation the issue appears to being caused by the control app. i have treid 2 different ones on my iphone.
i have enclosed 2 log files:
1. not using the app at all
2. using the app to fast forward very slightly through the track (this causes it then to end early

[simoncn]

Thanks for these logs. The control app (or renderer, if this is different) is not functioning correctly. Instead of advancing a short way through the stream when you fast forward, it jumps to the end of the stream.

[besbax]

This is the requested file, from the beginning of the track until the stop.
I would add that after the stop, the app displays the message ‘another client connected, disconnect the other client and try again’, then I lose the connection to the network.
I use the Focal&Naim app to control a Naim NDS and a Naim Mu-So.

[simoncn]

Thanks for this. The log shows that the renderer requests the track and starts streaming it, then closes the connection part way through after about one second and sends another request for a later section of the file, which completes successfully.

I am not sure what the message "Another client connected" means. Do you have another control point or renderer that might be active and trying to stream this file at the same time?