Mercurial > hg > xmms-sid

comparison FAQ @ 737:55e992b016a1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update FAQ.
author Matti Hamalainen <ccr@tnsp.org>
date Mon, 05 Nov 2012 14:07:38 +0200
parents f47c15614d75
children
comparison
equal deleted inserted replaced
736:c310c2a01a31 737:55e992b016a1
203 203
204 --- 204 ---
205 205
206 Q: XMMS-SID plays some tunes too fast / there are severe playback bugs! 206 Q: XMMS-SID plays some tunes too fast / there are severe playback bugs!
207 207
208 A0: GCC 4.0 (and perhaps GCC 4.1, too) produces broken code when 208 A0: Upgrade to later version of GCC, like GCC 4.6 or 5.7
209 compiling libSIDPlay2 (it is a bug in the optimizer). If your
210 distribution uses GCC4 and you have problems with libSIDPlay2,
211 there are few alternatives:
212
213 1) Use GCC3 instead.
214
215 2) Some people also report that disabling all optimizations on
216 GCC4 (by using -O0) will fix this problem, but other reports
217 say that it does not on 64-bit platforms. Also, disabling
218 optimizations will slow libSIDPlay2+reSID VERY MUCH, they
219 will consume much more CPU then!
220
221 3) Latest CVS version of libSIDPlay2 has some workarounds for
222 GCC4 bugs, but it is unknown whether all optimizer bugs have
223 been caught.
224
225 209
226 A1: If you are using libSIDPlay2 emulator engine, some SID-tunes in old 210 A1: If you are using libSIDPlay2 emulator engine, some SID-tunes in old
227 format (PSIDv1) are not compatible with it anymore and may play 211 format (PSIDv1) are not compatible with it anymore and may play
228 too fast or with some other audible glitches. Get new rips of those 212 too fast or with some other audible glitches. Get new rips of those
229 tunes in PSIDv2NG or RSID format, for example from recent version 213 tunes in PSIDv2NG or RSID format, for example from recent version
230 of HVSC. 214 of HVSC.
231 215
232
233 A2: Generally speaking this might be a bug in emulation-library or some 216 A2: Generally speaking this might be a bug in emulation-library or some
234 other component. Or it might be in XMMS-SID. Report and I'll see 217 other component. Or it might be in XMMS-SID. Report and I'll see
235 what can be done. 218 what can be done.
236 219
237 --- 220 ---