nesdev.com
http://forums.nesdev.com/

This fixes an issue with famitone
http://forums.nesdev.com/viewtopic.php?f=6&t=14876
Page 2 of 2

Author:  dougeff [ Fri Nov 04, 2016 8:38 pm ]
Post subject:  Re: This fixes an issue with famitone

OK, I had to share this. I've been working on rewriting the source code for famitone2's text2data.

Today I've been working on adding the 'volume column' into the data. And, big success!! I still need to rewrite famitone.s to accommodate, but the data is looking right. I'm so happy!!

Author:  dougeff [ Sat Nov 05, 2016 12:05 pm ]
Post subject:  Re: This fixes an issue with famitone

Also managed to add full note range today.

I had to sacrifice PAL mode and efficiency.

There is room for more effect support, but I likely won't be doing that.

Author:  Sumez [ Mon Nov 07, 2016 1:45 am ]
Post subject:  Re: This fixes an issue with famitone

Famitone 3 on its way? :3

Would love to see Famitone supporting more effect columns from Famitracker, since it would make it much easier to work with musicians who aren't happy about limitations. Especially pitch modulation would be a huge improvement, but I'm not sure it can be done without sacrificing a bunch CPU cycles?

As for PAL mode, we don't need that :P

Author:  dougeff [ Tue Nov 08, 2016 6:53 am ]
Post subject:  Re: This fixes an issue with famitone

I'm basically done with my first edition. Need to make a NESASM and ASM6 version.

Size differences... (data in a test song)
Original text2data - 505 bytes
My version with volume column - 615 bytes (22% increase)
My version minus all volume changes - 565 bytes (12% increase)

Need 6 more RAM variables.

Runs about [estimated in my head] 150-200 more lines of code per frame, that'd be about 500 cycles more per frame. [again, in my head estimate]. That's because I have to run a multiplication routine 3 times [Sq1, Sq2, Nz].

Author:  mikejmoffitt [ Tue Nov 08, 2016 6:50 pm ]
Post subject:  Re: This fixes an issue with famitone

You could implement the volume column without slowing anything down, at the expense of data space - have 15 variants created for every volume macro, pre-scaled, and variant instruments to point to them. Maybe that can work?

Page 2 of 2 All times are UTC - 7 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/