Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
recording speaker timings
60 views
Skip to first unread message
vi...@pianoman.cluster.toy
May 8, 2020, 11:50:09 AM5/8/20
to
Hello
I was working on replicating some sound effects from some games.
With AppleWin I can do this by putting a debug memory trap on $C030
and noting the elapsed cycle count between accesses. This is slow
to do manually though.
Do any emulators automate this? Where you could write out the speaker
access patterns, possibly so you could run the results through a player?
Vince
I was working on replicating some sound effects from some games.
With AppleWin I can do this by putting a debug memory trap on $C030
and noting the elapsed cycle count between accesses. This is slow
to do manually though.
Do any emulators automate this? Where you could write out the speaker
access patterns, possibly so you could run the results through a player?
Vince
David Schmidt
May 8, 2020, 12:53:26 PM5/8/20
to
On 5/8/20 11:50 AM, vi...@pianoman.cluster.toy wrote:
> I was working on replicating some sound effects from some games.
Thinking about solving the problem differently - what about recording
> I was working on replicating some sound effects from some games.
the audio coming from your PC while running the emulator? i.e.
https://www.howtogeek.com/217348/how-to-record-the-sound-coming-from-your-pc-even-without-stereo-mix/
Nick Westgate
May 8, 2020, 7:57:17 PM5/8/20
to
On Saturday, 9 May 2020 01:50:09 UTC+10, vi...@pianoman.cluster.toy wrote:
> With AppleWin I can do this by putting a debug memory trap on $C030
> and noting the elapsed cycle count between accesses. This is slow
> to do manually though.
It's a shame the cycles isn't logged in a trace file (type help tf).
> With AppleWin I can do this by putting a debug memory trap on $C030
> and noting the elapsed cycle count between accesses. This is slow
> to do manually though.
I would log an issue asking for this. Then you can grep it for C030.
Cheers,
Nick.
TomCh
May 9, 2020, 9:28:49 AM5/9/20
to
Taking this 'tf' cmd a bit further, it could be extended to only trace-out an opcode when a breakpoint/watchpoint is hit. Similar to Visual Studio's Tracepoint feature (but without the conditional support).
So in this mode, the "hit" wouldn't stop execution, but it would just emit a trace line for this opcode.
You could use this to create just a trace of $C030 accesses, or $C0En (for Disk II) or $C4nn (eg, for Mockingboard).
I guess you'd need a special "end tf" breakpoint too, or perhaps each breakpoint/watchpoint could have an extra attribute saying whether it behaves as a normal "break execution and enter debugger" or as a Tracepoint.
I'll have a think about the best way to add this, but personally I can see a use for this.
Tom
Michael AppleWin Debugger Dev
May 9, 2020, 1:57:00 PM5/9/20
to
That would be a great addition Tom!
Michael
Michael
0 new messages