Closed al-gh closed 3 months ago
I need the two files that do not work with MPD
I might be experiencing the same issue, so I wanted to share my observations. I recently compiled from HEAD on a Raspberry Pi CM4.
Here are two royalty-free MP3 files I’ve been testing with: https://we.tl/t-TOLZBcc5Km
Mpd config
bind_to_address "/tmp/mpd_socket"
audio_buffer_size "8192"
mixer_type "software"
I run MPD with the following command:
./output/release/mpd ../mpd.config --stderr --no-daemon --verbose
my test script which I'm running against mpd:
#!/bin/bash
mpc clear
mpc volume 60
mpc crossfade 5
mpc mixrampdelay 1
mpc mixrampdb -17
mpc add /home/pi/song1-15sec-silence-ond-end.mp3
mpc add /home/pi/song2.mp3
mpc play
Running the script multiple times yields varying results, even on fresh starts of MPD. When it works, the console displays:
cross_fade: will overlap 557 chunks, 11.681043391359028s
With some debug statements I'm noticing that on this line: https://github.com/MusicPlayerDaemon/MPD/blob/41cc69584835dc57424612d0f260da53dcba426b/src/player/CrossFade.cxx#L111
mixramp_start
and mixramp_end
don't always carry a value. Making the If statement resolve to false
.
Bug report
Edit: Tried it again and it worked correctly sometimes, but still not consistently.
Describe the bug
Mixramp doesn't seem to work properly. The overlap duration is
alwaysoften equal to the crossfade duration instead of being based on the mixramp -tags and mixrampdb -threshold.For example, with setting
mpc crossfade 10
the overlap duration is 10 seconds, regardless of the mixramp tags or themixrampdb
setting (leading to songs being mashed together instead of transitioning smoothly).Expected Behavior
Overlap duration should be based on the mixramp -tags and the
mixrampdb
-threshold.Actual Behavior
Overlap duration is same as the crossfade duration (leading to songs being mashed together).
Version
Config
Logs
Start up after
mpd --stderr --no-daemon --verbose
Log when problem occurred (tracks overlapped by 10 seconds):
Log when mixramp worked correctly: