1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
Q: I have PulseAudio, and I have playback problems (noise, distortion, wrong speed, no sound, etc)
A: Disable PulseAudio
A: Try to use OSS as pulseaudio backend
--
Q: I don't get it. Yes, indeed I have PulseAudio, but in Deadbeef I select ALSA output, and I get playback problems.
A: PulseAudio tricks applications by providing ALSA-plugin that routes sound from application to PulseAudio via ALSA API.
--
Q: Is it planned to support PulseAudio natively?
A: Yes.
--
Q: Occasionally I get following error: "alsa: snd_pcm_writei error=-32, Broken pipe". Is it bad?
A: Ignore it.
--
Q: Is it planned to support multiple playlists and EQ?
A: Yes
--
Q: Is it planned to make Windows and/or OSX ports?
A: No
--
Q: Playlist, settings, etc are not saved if I kill X session, shut down or restart computer, etc
A: That is not fixed yet. But it is work in progress. Please don't bother me with that unless you have a patch that fixes it.
--
Q: Deadbeef takes too much CPU% when playing mp3/ogg/flac.
A: Try to reduce SRC quality in preferences window
A: Try to check "Use software ALSA resampling" box
A: See the PulseAudio questions above
--
Q: Deadbeef takes too much CPU% when playing APE files.
A: That's normal. Consider switching to wavpack or flac.
--
Q: I have 50 ideas about what features must be added to the player!!!111oneone. Can i become idea-generator of the project, so that I tell, and developers do what I ask for?
A: No
--
Q: How do I make GDB backtrace after crash or hang?
A: Ensure that you have unstripped binary. Most packages are stripped. So you'll have to build yourself in most cases, if you haven't done so already.
Simply doing "./configure && make && sudo make install" is sufficient, but it's better to add export CFLAGS="-O0 -g".
1. install GDB
2. run "gdb deadbeef", and execute "r" command in GDB shell
3. reproduce a crash, or press ctrl+c in GDB after hang occurs
4. execute "thread 1" command, followed by "bt" command in GDB
5. repeat for at least 5 threads: thread 2<enter> bt<enter>, and so on
6. now, you can copy the output starting after 1st "bt" command into email/pastebin/textfile, etc.
|
