-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Play timer runs way too fast up to 50 seconds #20
Comments
Never mind, I reinstalled lib 2.4.2 (from Arch repo) and recompiled the 2.4.1 player and this problem has gone away. Sorry for the noise. |
Just got the same issue on Arch. Library v. 2.6.0, player v. 2.6.2 |
Recompiling the player didn't help |
Dunno man, I saw this once and recompiling fixed it. Try it again maybe? |
Didn't mean to reopen this, apologies. |
Weird, it never occurred to me. What if you pass the |
That didn't help |
Hard to tell without reproducing... |
@drfiemost |
Tried recompiling with the same flags, except for -march set to x86-64-v2, with gcc 13.2.0 but no sign of the issue. |
Can you confirm this happens with the ALSA driver? |
How do I make sidplayfp use ALSA driver? |
Did the same thing Gentoo does to disable pulseaudio support ( |
Oops, did this on release version for some reason. Retrying on version from |
Do you have the same problem with pulseaudio? |
Nope, problem is gone with pulseaudio (did the |
Also, looks like sidplayfp prefers ALSA if built with both PulseAudio and ALSA |
getting the same issue here, in my case it seems to prefer pulseaudio when it has support for both, so i delete the libpulse section in configure.ac to force ALSA probably the worst way to do it, but whatever |
That should not happen, pulseaudio have the priority over ALSA, unless the initialization fails for some reason :/
We can add a --disable-pulse option, open a new issue if needed. Back to the problem, we have determined that it affects the ALSA driver and the effect varies with the sampling rate. |
Can you please try #32 ? The buffer size is now proportional to the sampling rate. It still eats the first frames playing at 8KHz but it seems a bit better than before. |
Hi there,
Wasn't sure whether to report this against the player or libsidplayfp, chose here (hope that's alright).
I've noticed a problem with the player (lib 2.4.2 and player 2.4.1) when you play a tune the timer counts super fast up to 50 seconds then appears to run normally. This causes tunes to not play to their proper length (tunes under 50 seconds end after about 3 seconds).
I've also tried the alpha lib and player for 2.5.0 and it does the same thing.
Cheers.
The text was updated successfully, but these errors were encountered: