Question about MOD play routine

[prowler]

Originally Posted by Akira

Ah, talking to myself again!

Fear not, mate. I imagine there are many here who, like myself, are watching your progress in this thread with great interest, but have nothing to add.

Congratulations on your latest breakthrough, by the way.

[robinsonb5]

Originally Posted by Akira

Ah, talking to myself again!

I did actually download the source and have a quick look at it - that's as far as I got though. Glad to see you're some way towards find a solution, anyway

[Amiga1992]

Originally Posted by prowler

Fear not, mate. I imagine there are many here who, like myself, are watching your progress in this thread with great interest, but have nothing to add.

Yeah I don't mind talking to myself!
Getting through with a solution to this "problem" can end up in me being able to realize at least two applications for the miggy, whenever my coding skills are up to scratch.

[h0ffman]

Originally Posted by Akira

Ah, talking to myself again!

I tested this 1.2f version of ProTracker. Looks just like PT2.3d which is good.

The pitch function works rather well! I think it's just what I need to start with. I would have to play around with the source and make one single slider that would change both tempo and all 4 channels' pitch at the same time and it should be solved. I would have to add some sort of keyboard shortcut for this too because the mouse doesn't function really well as it is.

This would be a quick hackjob but it would be a good proof of concept regarding the possibility of making a stand-alone MOD player with this function. No need for AHI, no need for an audio stream, no need for a beefy Amiga. Ran perfect on my 68000 2MB A600.

;-------------- Sets hardware period value
SetPitchCtrl	macro
	move	PitchCtrl+((\1-1)<<1),d0	;read pitch offset
	sub	#PitchCtrlSize>>1,d0
	add	d0,d0				;scale pitch_ctrl range
	add	audchan\1temp+n_period,d0
	move	d0,$dff0a6+((\1-1)<<4)		;Set hardware period
	endm
SetNewPitchCtrl
	move.l	d0,-(sp)
	SetPitchCtrl	1
	SetPitchCtrl	2
	SetPitchCtrl	3
	SetPitchCtrl	4
	move.l	(sp)+,d0
	rts

THATS IT!! I think :S

[robinsonb5]

Originally Posted by h0ffman

;-------------- Sets hardware period value
SetPitchCtrl    macro
    move    PitchCtrl+((\1-1)<<1),d0    ;read pitch offset
    sub    #PitchCtrlSize>>1,d0
    add    d0,d0                ;scale pitch_ctrl range
    add    audchan\1temp+n_period,d0
    move    d0,$dff0a6+((\1-1)<<4)        ;Set hardware period
    endm
SetNewPitchCtrl
    move.l    d0,-(sp)
    SetPitchCtrl    1
    SetPitchCtrl    2
    SetPitchCtrl    3
    SetPitchCtrl    4
    move.l    (sp)+,d0
    rts

THATS IT!! I think :S

Yup, I should say so.

However, it's *adding* a constant to the period rather than scaling it, so (without having tried it) I think it's going to cause some pretty horrible tuning errors!

If you want to keep the pitch adjustment in sync with a tempo-change, then I think you want to be doing something more like this:

SetPitchCtrl    macro
    move.w  audchan\1temp+n_period,d0
    mulu    originaltempo,d0
    divu     newtempo,d0
    move.w    d0,$dff0a6+((\1-1)<<4)        ;Set hardware period
    endm

Where "originaltempo" and "newtempo" would be new word-sized variables you'd have to add yourself.