Changing the tempo of AY music
ZXNet echo conference «code.zx»
Hello, Aprisobal
I did this once, not only with PT3, but also with PT2, ST, PSC and ASC.
When I get back from work, I'll dig around to see where things are.
It will be easier, of course, as Ronin suggested...
Hello, All
I don't understand AY music players at all. Is it possible to change realtime in them?
pace? Specifically the PT3 player. I independently found only where (address
player+$463/$464 (this is LD A,3)) the tempo value is entered during initialization
player, but simply changing this value when playing music does nothing
changes.
Hello, Aprisobal
Well, you can call less often or more often than once per int, for example :)
Hello Ronin
SAM> I did this once, not only with PT3, but also with PT2, ST, PSC and
SAM> ASC. When I get back from work, I'll dig around to see where things are.
SAM> It will be easier, of course, as Ronin suggested...
Yes, it’s easier, but the music sounds too fast/slow rather than changing the tempo +-1 in
editor
Hello, Aprisobal
Apr> Yes, it’s easier, but the music sounds too fast/slow rather than change
Apr> temp +-1 in the editor.
The source code for the pt3 player as edited by Alon is freely available (along with pt3).
Also on Sergei Bulba’s website you can find the source code for his version of the player, and
also decompiled versions of all sorts of pt2, Sqt, Stp, etc.
Hello, Aprisobal
Apr> is easier, but the music sounds too fast/slow rather than changing the tempo
Apr> +-1 in the editor.
But it’s more accurate, because it has long been known that sometimes musicians write themes in
instruments, and in this case there appears a rigid attachment to the tempo
playback.. and if you stupidly change the playback tempo - the sound is in separate
will float in the channels. The same thing will happen when used by a musician
slide commands..
Again... the musician can manually change the speed from the module...
Hello, Aprisobal
If you still need it, I found the addresses for the PT3.69 player;
+#462; - here is the basic tempo value
+#87d is a counter (it moves down to 0, then the value from +#462 is written there)
To ensure that changing the speed from the module does not affect the plan, it is necessary
constantly change +#462 something like this:
┌─- code ───
call PLAY
ld a,(player+#462)
sub n to speed up or add a,n to slow down
; then check that the value does not go beyond 2-255
; (I don’t remember exactly, but the player doesn’t seem to digest the too fast tempo)
ld (player+#462),a
└── code ───
something like this
You can also intercept tempo changes from the module - change the program to +#BFA;
┌─-; code ───
ld a,(de)
inc de
ld (+#462),a
ret
└── code ───
Hello, SAM style
SAM> To ensure that changing the speed from the module does not affect what was intended,
SAM> must be constantly changed +#462 something like this:
Thank you! Just what you need.