custom max. speed >586% makes SID engine crash
Versatile Commodore Emulator
Brought to you by:
blackystardust,
gpz
do this:
SID settings: ReSID, resampling (also fast)
now this :
maximum speed -> custom -> any value above 586
error dialog pops up:
sound: cannot initialize SID engine
what VICE version are you using? 2.4.18 what operating system are you using? Win 7 what did happen? error dialog: sound: cannot initialize SID engine
I think that this is by design, according to the comments starting ~line 464 in ...\vice\src\resid\sid.cc.
It's not actually crashing the SID engine, the SID engine is proactively refusing to initialize.
ok.
but then, why it doesn't happen on "no limit"? it runs at >1000% here.
also, once you get this error message, it's not possible to reactivate the SID engine at lower speed settings.
is this still a problem? i cant reproduce it on current trunk (although on linux)
still the same in winvice.
I cannot reproduce this problem
I can reproduce it.
I
1. ran x64;
2. used default settings;
3. set the Maximum speed to 587%;
4. set ReSID's sampling method to either "Fast Resampling" or "Resampling".
However, I can re-enable the sound if I change to a lower max. speed or a "lower" sampling method.
ehrr... again: the sound getting disabled is by design. this bug is about VICE crashing in that case.
ok. it's not VICE that crashes, just the SID engine.
same on both pokefinder and my own builds... on both my i5 and my i7 cpu
Last edit: Querino 2015-11-02
well, the problem is still there...
how do you even set it to that value? :)
In Gtk3: click on the %cpu/fps widget in the statusbar, then use 'maximum speed' -> 'custom'.
When I use either resampling/fast resampling ReSID indeed fails to init (no crash though) when using >= 587% speed.
When using fast/interpolation, I can set the custom speed to 1000% and ReSID still works. I would try higher values, but the UI doesn't accept values over 1000.
i see the log says
now - so is this a wontfix? why does it even happen? who added that message without updating this ticket?
the log entry is there since ages (checked right now)... i should have posted this.
even in v2.4 it is present.
strange detail: the max accepted value is now 638, not 586 as it used to be :)
let me guess, you change samplerate back to 44khz and its back to 586? :)
its probably simply hitting the limits of the resampler.... IMHO we should also disable the sound at those speeds (perhaps anything lower 50% and higher 200%)
@dqh what do you think?
ah yes, didn't even know the default was changed.
so it's 1278% at 96khz
only 106% at 8khz (but who cares?)