Does anyone have an A600 / A500 they can test this on?

[h0ffman]

Hi Guys

I've just put together a scope protracker player. I need it speed testing on a real A500 or A600 (i.e. a 68000).

I've uploaded an Amiga exe file in the zone, any help would greatly appreciated.

Cheers

[Dreedo]

Damn my A600 is in storage and i can't get it out. :P

Doubt it would run anything much anyway, only has 1MB of RAM, that doesn't run anything except commercial games usually.

[h0ffman]

On the contrary Dreedo, the music disk I'm working on is aimed at A600 1mb chip and above. So you could run it once its finished

[pmc]

That looks the bollox h0ff.

I'll see if I've got time to dig out my A500+ from the loft and run it on that. Unless someone else beats me to it in the meantime...

How does that scope code work? What do you patch into in the replay code and how do you manipulate the sample outputs to plot / draw the scopes?

I for one would be interested to know.

[thomas]

Originally Posted by h0ffman

On the contrary Dreedo, the music disk I'm working on is aimed at A600 1mb chip and above. So you could run it once its finished

You should aim it at 512k chip and the rest of any RAM, otherwise most A500s are out of luck.

[pmc]

I'm guessing but I suppose 1Mb chip might be required depending on the size of the tunes h0ffman wants to play...?

[StingRay]

Originally Posted by h0ffman

Hi Guys

I've just put together a scope protracker player. I need it speed testing on a real A500 or A600 (i.e. a 68000).

I've uploaded an Amiga exe file in the zone, any help would greatly appreciated.

Cheers

I can check on my A500 later this evening. You btw still have the VBR bug in your code. Nag nag. Since you are using my startup code you can call the "GetVBR" routine and it'll return the VBR in d0.

Originally Posted by pmc

How does that scope code work? What do you patch into in the replay code and how do you maniulate the sample outputs to plot / draw the scopes?

There's no need to patch the replay routine, it has an info structure for each of the 4 channels which you can use for the scopes. To draw the dots you can f.e. read the sample byte, multiply by volume and use that as offset to draw the dot on screen.

[h0ffman]

@Stingray - Don't worry mate, it's on the to do list

@PMC - There was a small amount of patching to my protracker replay routine, just n_samplenum and n_trigger.

Theres still a couple of bugs in it though. The 9 command seems to over shoot on the scope and not draw it for the correct length! Which is really annoying as that command is used LOADS!

Notes with E commands on aren't triggering the scope to play, but that I'm sure thats an easy one to fix. Just need a better or additional trigger point

@Thomas - Sorry dude, no way on earth I'm gonna fit that much music in memory at once. Its a long player music disk so needs to contain two modules in memory at all times. I thought the slow to chip mem hack on the A500 was par for the course?

[h0ffman]

No worries guys, someone just got back to me, its running within about 2/3 a frame, which should be ok as I haven't buffered or blitter cleared it yet.

[Amiga1992]

It's running great on my A600. The top is covered by a bar, up t the middle of the screen, if that's of any help.

Nice little test tune!

[pmc]

The moving red bar is intentional Akira - it's just h0ffman testing how many raster lines his routine takes to execute.

[h0ffman]

Just tripple buffered this today, one plane displaying, one plane cleared by the blitter while the thrid is drawn by the cpu! Whoooop!

It does seem to drop a frame now and then.... just will check on proper hardware as it may just be my laptop running winuae!

[pmc]

You're steaming ahead with this one h0ffman - I'm really looking forward to seeing it. It's gonna be quality! \o/