Woah, peace and love, my brothers and sisters!
@TinywandererJay, I think your phrasing is coming off here a bit … abrasive (“major buggy” … “acts like a glorified cd player of yesteryear”) which is triggering some readers. We’re both new to each other; there are a ton of people here who use and love the app, you’re having some issues, let’s meet in the middle in friendly fashion and figure out how to introduce you properly to the app.
As far as I can tell here, there are two issues.
-
It seems, as best I can tell, like you’re not getting loudness data computed for the initial set of albums you scan in, but you ARE getting it for any subsequent ones added. Can you verify this indeed seems to be the case?
-
If you have Sweet Fades enabled, and you’re playing non-consecutive_ tracks (not an album, say) between two tracks with loudness data, you will get a fade. Technically speaking, this is an overlap of the end of song A with the start of song B. It is NOT a cross-fade. Sometimes the effect can be quite subtle, other times less so.
As for issue (1), my suspicion is it’s a regression in the server, which will be investigated. Any further clarifications or validations of the theory would be appreciated.
As for issue (2), now that you know that it’s overlapping ends and starts, pick 2 tracks which have loudness (show the waveform while playing), and add them one after the next (make a playlist, e.g.). After playing it, upload Plexamp logs and I’ll tell you what the overlap time was, which might help explain what you’re hearing vs what you think you should be hearing.
Make sense?
(Also, your device/OS details are probably useful as well.)
