When I start playback of any track, whether to a joined speaker or to a single speaker, running Sendspin-cli, I hear an audible pitch warble or gradual increase over approximately 0.5 to 1 second, almost as though I dropped the needle before the record player was fully up to speed.
The main device I experience this on is a Raspberry Pi 4 running Raspbian 13/Trixie, with a HiFiBerry DAC Hat.
More in depth discussion on discord here but I believe the conclusion is that the Sendspin player implementation determines how clock sync mismatches are handled; so I suppose it's an issue with this player.
I also notice that a very brief portion of the beginning of a track is cut off, or perhaps inaudible due to some kind of volume ramp up or fade in. On tracks where there is audio immediately it's clearly missing the first fraction of a second. Not sure if this should be recorded as a separate issue.
Interestingly, starting playback of a new track for the first time from MA exhibits this issue; whereas restarting the track using the previous track button does not (the beginning of the audio is played in full). This makes the issue more easily detectable.
When I start playback of any track, whether to a joined speaker or to a single speaker, running Sendspin-cli, I hear an audible pitch warble or gradual increase over approximately 0.5 to 1 second, almost as though I dropped the needle before the record player was fully up to speed.
The main device I experience this on is a Raspberry Pi 4 running Raspbian 13/Trixie, with a HiFiBerry DAC Hat.
More in depth discussion on discord here but I believe the conclusion is that the Sendspin player implementation determines how clock sync mismatches are handled; so I suppose it's an issue with this player.
I also notice that a very brief portion of the beginning of a track is cut off, or perhaps inaudible due to some kind of volume ramp up or fade in. On tracks where there is audio immediately it's clearly missing the first fraction of a second. Not sure if this should be recorded as a separate issue.
Interestingly, starting playback of a new track for the first time from MA exhibits this issue; whereas restarting the track using the previous track button does not (the beginning of the audio is played in full). This makes the issue more easily detectable.