"Pulsar" demo (Page 5 of 15)

Yup, big problem.

I could, of course, release two versions of Pulsar, one that uses 8K SRAM, one that uses 32K.

The downside to that of course is that the amount of "objects" is greatly reduced in the (current) 8K version. Here's how the memory map is built for 8K;

TRACKS_PER_SONG        = $05
STEPS_PER_TRACK        = $40

NUMBER_OF_CHAINS        = $20
NUMBER_OF_PATTERNS        = $20
NUMBER_OF_INSTRUMENTS    = $20
NUMBER_OF_DRUMKITS        = $02
NUMBER_OF_ENVELOPES        = $20
NUMBER_OF_TABLES        = $10
NUMBER_OF_VIBRATOS        = $10
NUMBER_OF_DUTY_TABLES    = $10

STEPS_PER_CHAIN        = $10
BYTES_PER_CHAIN_STEP    = $02

STEPS_PER_PATTERN        = $10
BYTES_PER_PATTERN_STEP    = $04

STEPS_PER_INSTRUMENT    = $10
BYTES_PER_INSTRUMENT_STEP    = $01

STEPS_PER_DRUMKIT        = $0C
BYTES_PER_DRUMKIT_STEP    = $05

BYTES_PER_ENVELOPE        = $04

STEPS_PER_TABLE        = $10
BYTES_PER_TABLE_STEP    = $06

BYTES_PER_VIBRATO        = $04

STEPS_PER_DUTY_TABLE    = $10
BYTES_PER_DUTY_TABLE_STEP    = $02

Which uses just under $1900 of the $2000 bytes available.

Looks like the Repro-pak can support SXROM, which is nice. I can certainly see why you need 32kb of .SAV though. I'd say, go for it anyways.

That's very kind of you man.

I can't think of anything you could help with right now (apart from cloning myself so I can spend more time on Pulsar) but there will be a time I will need Beta testers again for Pulsar, it would be good if I can count on you for that.

Selecting areas of your Song/Chain/Pattern and copy-n-pasting is for pussies, right?

Noted.

Cloning is easy as there's nothing graphical to represent. Having the ability to mark sections of data is always a pain and makes drawing the screen a lot slower so at this stage I'm planning not to have it.

Got it making noise tonight (playing song/chains/patterns/notes, chain/pattern cloning , ADSR working). I have to say, this thing is going to be the shit!

You lucky, lucky people.