43110 wrote:
For the functions that use fixed zero page locations (such as "snddatalo = 0" in pently_start_sound) I often assign them to a relocatable label called temp. Witch would be better to require? A 5 byte variable import or externally reserving specifically zero page 0 through 4?
I have externally reserved $0000-$000F in all my own projects, starting the ZP segment at $0010. But the next release will allow temporary ZP to be relocated.
Quote:
pently_resume_music and pently_stop_music were not found with the linker.
My bad. This will be corrected in the next release. Until I push it out, go down to line 156 or so and change
.proc resume_music and
.proc stop_music to have the prefixed names.
Quote:
I know this is not the case with every music engine (except maybe nerdtracker2), but i wonder if it's even possible to design the music data to be relocate without having to recompile the network of address pointers.
In NT2, all offsets are ultimately relative to the start of a song, and songs cannot share instruments or patterns. I don't know how instrument or pattern sharing is possible with that sort of relocation.
Quote:
I also wonder if it's easy to construct and play a pattern from RAM, so that there could be an option for the user to create and save some of her own music.
The
Sound Effects Editor included in Double Action 53 uses a subset of Pently 0.04 configured to store sound effects' envelope data in RAM. If you want to make something larger in scope, you could set it up such the tables are at fixed positions in WRAM ($6000-$7FFF).