Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[alglove]

Looking at my MC20 Media Network logs, I notice when a DLNA renderer requests a WAV file from the DLNA server (renderer and server are both MC20), there are often multiple entries in the server log. For example:

#            Time        Status      Source          Resource                                                              Served   Time
----------------------------------------------------------------------------------------------------------------------------------
122003   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   192 KB   0:00.005
122004   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   576 KB   0:00.010
122005   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   192 KB   0:00.004
122006   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   192 KB   0:00.005
122007   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   192 KB   0:00.005
122009   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   1.9 MB    0:00.049
122010   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   36.0 KB  0:00.001
122014   1:24 pm   Finished   10.1.10.101   GET: http://10.1.10.100:52101/Music/F6886.wav   44.2 MB  0:00.511


Is this typical behavior for a WAV file, or does it show some sort of problem? FLAC files seem to have only one entry, getting sent as one large chunk.

[AndrewFG]

Does it play alright? If it does, then who cares how many GETs the renderer uses to fetch the file? Different renderers have different behaviours on different types of file.

[alglove]

It seems to play OK, but we have issues with playback to the renderer stopping at random places. That is, if we have a playlist of 100 songs, playback at the renderer might stop at song 74 for no apparent reason. It will finish playing the song, but never advance to the next one. However, most of our files are FLAC and are sent in original format. Playback seems to stop on those, as well.

In the process of troubleshooting, I looked through the logs and noticed that about the WAV files. I thought to myself, "Huh, that's weird. Is it supposed to be doing that, or is that a symptom of some sort of network problem?"

If multiple GETs is typical behavior (or at least not unusual), then I won't worry too much about it. It just struck me as odd.

Thanks.