pouët.net

Crackling SID 8580 issue in WinVICE 3.1

category: general [glöplog]
 
I get this issue in this version of VICE that I never had before, but turning the SID Filters off gets rid of the crackle. But then again, filters in SID are important, so should I be turning them off?
added on the 2017-05-28 15:04:12 by Foebane72 Foebane72
No.
added on the 2017-05-28 15:14:28 by noby noby
I think this is getting more than ridiculous.
What is, Stahl?
added on the 2017-05-28 15:43:32 by Foebane72 Foebane72
Quote:
I used to have horrible cars that would always end up broken down on the highway. When I tried to flag someone down, nobody stopped. But if I pushed my own car, other drivers would get out and push with me. If you want help, help yourself - people like to see that.
added on the 2017-05-28 16:55:08 by tomaes tomaes
I solved the problem by going back to version 3.0 of VICE.
added on the 2017-05-28 21:07:13 by Foebane72 Foebane72
put out the bonfire first!
If none of you can hear a crackle in the SID audio in 3.1, then that could be because you're on Win10, whereas I'm on Win7. Maybe that's not it, but the crackle issue I had went away when I went to 3.0a (the x86 version, so the 7-Zip filename says).
added on the 2017-05-28 22:44:16 by Foebane72 Foebane72
A more likely explanation would be that you simply don't really know how to properly configure the emulator
added on the 2017-05-29 06:39:23 by britelite britelite
I tried various settings, but seeing as I have little experience with the C64, I would not know the ideal settings to use.
added on the 2017-05-29 09:31:55 by Foebane72 Foebane72
I have this crazy idea, if everything works fine in 3.0, you could configure the SID- and Sound-settings in 3.1 to be identical.
added on the 2017-05-29 09:46:44 by britelite britelite
Or, you know, you could file a bug report. Even if it turns not to be a bug but a configuration issue or something, that would still be better compared to being stuck with 3.0 forever.
Check your sound buffer size first though; if for some strange reason this value is way below 100ms, it's the most reliable way to butcher your audio. And FWIW, 3.1 works fine on Windows 8.1, I just updated myself. They _did_ work on the filter code, and you can check the reSID settings (gain etc.), but it's unlikely to distort audio output in the way you describe it.
added on the 2017-05-29 12:45:45 by tomaes tomaes
Quote:
I have this crazy idea, if everything works fine in 3.0, you could configure the SID- and Sound-settings in 3.1 to be identical.


I took my 3.1 configuration and simply moved it into 3.0 - problem solved.
added on the 2017-05-29 13:01:33 by Foebane72 Foebane72
Quote:
Or, you know, you could file a bug report. Even if it turns not to be a bug but a configuration issue or something, that would still be better compared to being stuck with 3.0 forever.


I'd still be on 3.0, until they fixed the issue and release 3.2.

And what's wrong with 3.0, anyway? The latest version of an emulator is not always the best.
added on the 2017-05-29 13:03:07 by Foebane72 Foebane72
It's polite to file a bug report if you find an issue in a product you care about.
added on the 2017-05-29 13:03:57 by Preacher Preacher
Quote:
Check your sound buffer size first though; if for some strange reason this value is way below 100ms, it's the most reliable way to butcher your audio. And FWIW, 3.1 works fine on Windows 8.1, I just updated myself. They _did_ work on the filter code, and you can check the reSID settings (gain etc.), but it's unlikely to distort audio output in the way you describe it.


My sound buffer is 150msec, I increased it a while ago as I noticed that VICE always stuttered in a window with 2.4. What does Sound Fragment Size and Synchronisation Method do?
added on the 2017-05-29 13:07:01 by Foebane72 Foebane72
What Preacher said, and if you don't report a bug, there is a change that it will never be fixed if it's specific to your setup or workflow. That applies to any software. Eventually demos will be released that will break in 3.0 but work in later versions (such demos may already very well exist) and you will still be stuck with an essentially broken version if you don't report the issue.
Quote:
It's polite to file a bug report if you find an issue in a product you care about.


I've just filed a bug report with SourceForge, and I'll see what they say or recommend.
added on the 2017-05-29 13:25:12 by Foebane72 Foebane72
Quote:
Eventually demos will be released that will break in 3.0 but work in later versions (such demos may already very well exist) and you will still be stuck with an essentially broken version if you don't report the issue.

Actual breakage (on the same major OS version) is very unlikely in the case of an emulator for 35 year old HW that in large parts itself is almost 20 years old and has been mature for a long time. Unless it's a SCPU demo or concerns some weird/new/unproven HW extension/card, I wouldn't worry much. :)
added on the 2017-05-29 13:37:25 by tomaes tomaes
I didn't want to say it before, but I wasn't even aware of a crackling sound issue until I played this demo (http://www.pouet.net/prod.php?which=64281) with 3.1, and there is a definite annoying crackle on the beat of the music from 4:16 onwards, the skyscraper sequence. I don't get it with the same configuration in 3.0, and yes, I tried the default 3.1 configuration (no vice.ini file present) and it still crackled. The demo is not to blame.
added on the 2017-05-29 18:44:34 by Foebane72 Foebane72
The bug has been confirmed, they're looking into it.
added on the 2017-05-31 19:45:59 by Foebane72 Foebane72
See, and this is why you need to report bugs and not rely on other people doing the same.

login