You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is a little problem I face when cross-developing using MAME: activating the CPU trace triggers horrendous noise, as heard in https://www.youtube.com/watch?v=BSJyvu5AT78
It may be due to the fact my computer can't run emulation at 100% speed when tracing. Still, it would be nice to be able to keep sound on when tracing :)
apple2 driver sound output has a DC offset. Another way to hear it is by pausing/unpausing (F5 key), or (at least on Windows) by resizing or dragging the window. This will happen on any MAME driver with sound DC offset.
Hiccups with emulation speed when doing something taxing like tracing the CPU can't be helped.
The audio pops: perhaps it's possible to resolve by writing the last known value to the sound output instead of 0. IIRC holub opened a PR or issue for this problem? I can't find it, so maybe he wrote about that on the chat and not here on github.
Audio problems are unavoidable when MAME can't run 100% speed. The specific DC offset cited is due to the AY-3-891x on the Mockingboard. On a slotted II you can remove it and things are much better, but there's not a great way to do that on the IIc, in part due to MAME architectural limitations (you can't read machine config switches at machine configuration time, which is problematic when emulating hard-wired peripherals like the Mockingboard 4C). You can always run -sound none when debugging.
MAME version
0.263 (unknown) (0.263+dfsg.1-0ubuntu1ppa1mantic1)
System information
Linux Ubuntu 23.04, x86_64, en_US.UTF-8 locale.
INI configuration details
Emulated system/software
apple2c0
Incorrect behaviour
Hello,
Here is a little problem I face when cross-developing using MAME: activating the CPU trace triggers horrendous noise, as heard in https://www.youtube.com/watch?v=BSJyvu5AT78
These clicks also happen when tracing while the emulated machine does not access the speaker at all: https://www.youtube.com/watch?v=XFSnVqK_GcI
Sorry about the video quality, I hadn't noticed how out of focus this was. I'm using the following trace command:
It may be due to the fact my computer can't run emulation at 100% speed when tracing. Still, it would be nice to be able to keep sound on when tracing :)
Expected behaviour
The sound would be clear
Steps to reproduce
In the debug window:
trace test.tr,maincpu,noloop,{tracelog "A=%02X,X=%02X,Y=%02X,P=%02X ",a,x,y,p}
Additional details
No response
The text was updated successfully, but these errors were encountered: