> I've been going through a few Fred disks and most of the time the music > sounds perfect, but I come across a tune now and again that seems to have a > clicking or juddering sound (perhaps at 50Hz?). The Fred 60 menu music is > one, but also the second part of Mnemodemo 2 - when the 'M' is spinning, the > music sounds fine but when it stops, the juddering is heard.
Si Owen's found and fixed some subtle timing bugs in WinCoupe and will be releasing an updated 'alpha' version of WinCoupe very shortly (tomorrow night maybe, but that's up to him entirely) I've played with his updated version, and come up with the following observations: o The stuttering sound that I described recently that I had encountered whenever SamMines tries to play audio samples appears to have gone. This was at 50Hz. So maybe your problem will have gone too? o The BEEP command timings were out slightly - timing loops that rely on 'inert' instructions like LD B,B will have been slightly out - so this means demo code and audio code especially. Maybe this will have fixed your problem? All I can say is, try it, see if it's fixed. Don't forget: everyone using SAASound.dll (WinCoupe users or SAAEmu users) should upgrade to the current latest version, 2.05 http://www.geocities.com/stripwax > This gave me > an idea. Could it be that when the 'M' is paused there's less work going on > => the eTracker code is being called at a different position in the frame. > At this state maybe the routine in WinCoupe that passes the sound info to > SAASound.dll is being performed part way through the eTracker code; maybe > even between an OUT to a sound chip address port and its corresponding OUT > to the data port. To be honest, this is totally lost on me. Subtle timing effects are very emulator-dependent. If anyone has MnemoDemo 2 or Fred 60 for me to have a play with, could they send me a **ZIPPED** .dsk image? Thanks. (anything else as well would be appreciated, particularly things with suspected audio bugs) Ta. D a v e
