Problem: when playing 24bit+ tracks converted to uncompressed by a MC server, the MC client shows (in the uppermost window) a track length which is always 3/4 of the actual track length (as shown in the track data in the bottom window).
To replicate, setup a MC server serving both WAV/FLAC files having a 24+ bit depth and configure the client to always convert audio to an uncompressed stream. If the file names on the server also make sense on the client (\\server\share\... or a share mapped to the same local letter), you also need to uncheck "play local file...".
Now, if you play one of the tracks, the bit rate shown by the client is correct (8467 kbps for a 24bit/176KHz flac file, for example), but the track length shown on the progress indicator is 3/4 of the real track length and, unfortunately, the playing stops when the wrong length is reached.
If you change client settings to "Don't convert audio", the track length problem disappears, but then WAV files exhibit another weird behavior: it takes 50 seconds to start a 6:19 24bit/176KHz track. Please note that manually copying the entire 383 MB WAV files from server to client over a SMB network share only takes 14 seconds.
With "Convert audio if necessary" you get both problems as expected: length problem with FLACs and start delay with WAVs.
All of the above applies to both MC 15.0.174 and 16.0.75
Author
Topic: Wrong uncompressed stream length calculation (Read 3060 times)