Minim wishlist

[simoncn]

(24-06-2013 23:20)Alekz Wrote:  On both, but it's more common for Windows. It happens on a NAS as well, but only when there is another application that intensively uses the disks.

I always transcode to WAV, but I read some reports about FLAC as well. But I bet it was Windows with antivirus and other processes with sporadic activity.

I had similar issues some time ago, so I added some monitoring code to see what was happening. You can enable this monitoring code by playing a track using WAV transcoding and opening the log window and changing the logging level to Trace. You'll see log output like the following:

11:28:40.728 Thread-20: transcoding maxRead=0, minRead=0, maxWrite=73, minWrite=32, numReads=21, numWrites=43, avgWrite=46
11:28:42.763 Thread-20: transcoding maxRead=3, minRead=0, maxWrite=80, minWrite=25, numReads=22, numWrites=44, avgWrite=46
11:28:44.807 Thread-20: transcoding maxRead=4, minRead=0, maxWrite=64, minWrite=29, numReads=22, numWrites=44, avgWrite=46
11:28:46.849 Thread-20: transcoding maxRead=2, minRead=0, maxWrite=179, minWrite=0, numReads=22, numWrites=44, avgWrite=46
11:28:48.895 Thread-20: transcoding maxRead=3, minRead=0, maxWrite=164, minWrite=0, numReads=22, numWrites=44, avgWrite=46
11:28:51.015 Thread-20: transcoding maxRead=2, minRead=0, maxWrite=170, minWrite=0, numReads=22, numWrites=43, avgWrite=49
11:28:53.024 Thread-20: transcoding maxRead=3, minRead=0, maxWrite=169, minWrite=0, numReads=23, numWrites=46, avgWrite=43
11:28:55.070 Thread-20: transcoding maxRead=2, minRead=0, maxWrite=50, minWrite=42, numReads=22, numWrites=44, avgWrite=46
11:28:57.113 Thread-20: transcoding maxRead=2, minRead=0, maxWrite=51, minWrite=43, numReads=22, numWrites=44, avgWrite=46
11:28:59.155 Thread-20: transcoding maxRead=2, minRead=0, maxWrite=53, minWrite=42, numReads=22, numWrites=44, avgWrite=46

These messages are produced every 2 seconds and they provide the following information:

numReads: the number of disk reads (FLAC data) in the monitoring period (2 seconds)
numWrites: the number of network writes (WAV data) in the monitoring period
maxRead: the maximum elapsed time (in ms) for a disk read in the monitoring period
minRead: the minimum elapsed time (in ms) for a disk read in the monitoring period
maxWrite: the maximum elapsed time (in ms) for a network write in the monitoring period
minWrite: the minimum elapsed time (in ms) for a network write in the monitoring period
avgWrite: the average elapsed time (in ms) for a network write in the monitoring period

Ideally the minimum and maximum figures would be close to the average. In some cases when streaming over wireless, I was occasionally seeing a maxWrite figure of thousands of ms. These events corresponded to audible dropouts.

Can you try this under the conditions that cause dropouts for you and see what figures you are getting?