|[hatari-devel] Re: Interesting sound problems with Hatari?|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] Re: Interesting sound problems with Hatari?
- From: Douglas Little <doug694@xxxxxxxxxxxxxx>
- Date: Wed, 16 Apr 2014 19:05:44 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HaJq0AgKADEY/1DjKuVjUobZ+3h3awe6GmZwCg45hJA=; b=jrRalhUk7sXkCdHL9utbcfuJsaIlu1B/WOPY/joYX05dMHtq1lfpCX3XRaumfo/SKy Hzg0d9F53JewYAojF5TI3OeDJNDw5EwTMBvP6jnHFDk6R7XWczQnxPK7vNB/zVt2Fkj8 dikgQcH4Cd+3lgWcgTG5KQc8qN4zcZmEVXC87GK/bZVRgE80vz0A2wAQ6bUuE6R5aJ+B UZFhRMPbPhZ6YQCaI1e7zU0KoSwjyQzDTnhwFqptjIAbeTJWYPwQ3/8C6RXA6jLMgD2d aon7pNFk2lsIeZb1ajiYexMFsnftiZPz8gfmlSt1GuNaAxZS+H8eMxENpFMS8SuBXFLe 5Opg==
...have scraped a little more information on this one.
I dumped the DMA pages for the sample painted in memory, and performed a binary diff against the original sample data on disk, with the WAV header stripped off. The data is a perfect match, up to the first loop point (which is about 18k into the sample - quite far).. Beyond the loop point the deltas correspond to the original sample at the intended loop point.
So the source data being painted into memory is perfect.
This seems to leave 3 possible points of failure:
1) It is somehow being painted into the wrong place in memory, but not so wrong that it results in more than periodic glitches (this seems very unlikely, especially as the 'glitches' correspond to page swaps)
2) What has been painted into the DMA pages is not what is actually going to the 'codec'
3) What is going to the 'codec' is not what is going to the Windows sound system
I'm leaning towards #2 or more likely #3, which means a problem in Hatari or with the coupling of Hatari to the OS sound API, on Windows at least.
I'll keep digging though, just in case ;)