A.D.A. Amiga Demoscene Archive

Stingray likes fixing prods so maybe he should have a go at it... :o)

Guess what I'm already doing. :D Keeping traditions and all (hi Loady :P).

Guess what I'm already doing. :D Keeping traditions and all (hi Loady :P)

Hurraayyy!!! :o)

news: it works on real hardware now, crashes/black screen problems fixed. :) now I'm gonna (speed)optimize the code a bit. expect a working version this weekend. ;)

@stingray: what the hell is loaderror putting in his code not to make it work on a real amiga? Must be pretty evil stuff... :o)

Anyway, great news!

z5: well, as he was lazy (kidding ;)) he used fpu instead of fixed point. this is all fine and dandy as long as you don't use fpu instructions in an interrupt. ;) now guess what loady did. :P the black screen was caused by an incorrectly set bplcon0 register. :)

We are getting seriously off-topic on Blueberry's original topic :o) Just going to conclude that whatever rload puts in there, the end result always rules my world. It's been two years since gin and tronic so i'm very curious/eager to see Alice Copper.

Well, if you just look at the title "My Amiga 4k synth" by itself, I guess discussing Loaderrors Amiga 4k synth and the things he makes with it isn't really that much off-topic, is it? :)

But to get back to the original topic: Has anyone actually tried making some music with my published synth yet? You know, you should all go and make an Amiga 4k for Breakpoint - that's what matters!

Anyway, Loaderrors synth truly rules! But next time you make a 4k intro Espen, remember to assemble again before writing the object. ;-p

I used the GUI for some samples I used in a protracker mod. Nothing special. :-)

You know, you should all go and make an Amiga 4k for Breakpoint - that's what matters!

word! =)

Anyway, Loaderrors synth truly rules! But next time you make a 4k intro Espen, remember to assemble again before writing the object. ;-p


Probably off-topic but this really made my day. ;)

hehehe :) well. before showing this on the bigscreen. I had to use the "honest, it was 4k the last time I crunched it" excuse. This 4k is not very polished stuff but it was fun to make. No fpu in interrupts ... check.. whatwas wrong with the bplcon?

There is no problem with using FPU in an interrupt as such (the synth which this thread is about uses lots), you just have to surround your interrupt with code to save and restore the FPU state:

fsave -(a7)
fmovem.x fp0-fp7,-(a7)

; Your interrupt code here

fmovem.x (a7)+, fp0-fp7
frestore (a7)+

; Clear interrupt bits, whatever

rte

what about instructions like fsin and fcos which generate an exception on 060? Are those ok to use too?

Not sure. But since these instructions take a lot of time, and with the usually quite tight time budget in an interrupt, it is probably best to avoid them in any case.

What would you do in an interrupt that requires such complex operations anyway? ;)

nothing. I thought I had an fsin or fcos in there, but I didn't.

@off-topic: to loaderror: it would be extremely cool if a new hacks for tracks came along with frequent, cheetah, zixaq and you doing some new tunes with the latest soundengine.

I'm trying to teach Frequent to use the synth, but he tends to crash into bugs in the code quite often and I'm really slow at fixing them.

I've tried making some music with blueberrys synth, but I haven't done a real song yet.

I have screenshots from Alice Copper ready. Damn, for once i would have been faster than pouet :o) I'll wait until it's officially released though unless Loaderror gives me permission to add it (without the download ofcourse).

Hmm. I have a fixed version here which I just altered from what I heard Stingray had done. He has made some speed improvements though so I would like that to be in the released version. I was thinking of changing the intro a bit too and improving some parts, but maybe it would be better to just make a new one instead.

I'm trying to teach Frequent to use the synth, but he tends to crash into bugs in the code quite often

hehe... I have a tendency of revealing "artifacts", when I work with various music software. I guess I cannot stay away the temptation of overloading the cpu when i get some new ideas.

I was thinking of changing the intro a bit too and improving some parts, but maybe it would be better to just make a new one instead.

Start a new one for Breakpoint 2008 and let jaws drop to the floor...