JSR has already said that he did not wish to make this a standard FamiTracker feature (though he sees no problem with it existing in parallel with the main program).
Oh, okay, but exactly what was his motivation behind this? Before NSF Importer he said it is impossible to import NSFs, even it still is in FT help file, I think. But now someone proved it is possible. Also NSF import would make easier to make remixes of old NES game music, so why not?
//edit: Well, it isn't now, but I remember Q&A section being there and this was mentioned there. Will check readme too.
Here is the exact quote from a PM exchange that took place around January this year:
jsr wrote:
Regarding the [tracker/importer] fusion: I don't think that will happen, partly because it would involve more work for me when updating stuff, but I also don't think loading NSFs from other users should be supported officially. However I don't have anything against 3rd party support for that. (Actually I'm happy rainwarrior made it so I wouldn't have to) :)
The original line said "tracker fusion", but the importer was implied in the discussion.
Also, when you use the same N163 instrument in two channels, but a different wave with a lower volume using the Vxx effect, both of the channels used use the lower volume.
_______________________
[BURNING LOVE] YouTube Twitter (Stay off my lawn, kids)
Yes that's normal. Vxx doesn't affect memory position, and even though you're calling different waves, you're still using the same instrument so the same memory position is used.
The beta is updated, download it again from the first post. A list of changes since last beta is included, thanks everyone who reported bugs!
One major change is more authentic N163 emulation: this means that it won't sound as good anymore when using 8 channels, unfortunately, but that's how the real chip works. NSF exporting is also improved and should work properly on accurate players.
Another addition is a new high-quality resampler for the DPCM importer (contributed by Jarhmander), so it's no longer necessary to resample the samples manually for best quality.
im going to continue making this crazy stuff then after a while my style will be so sick that you will be like damn suuun that shit is so sick i dont even get it. i will be like bro its ok.. you dont have to.
there's a number of people who want this accuracy to be optional, let your opinions be heard!
There's this great thing called 0.3.8b3
_______________________
iGotno_scope wrote:
im going to continue making this crazy stuff then after a while my style will be so sick that you will be like damn suuun that shit is so sick i dont even get it. i will be like bro its ok.. you dont have to.
I sorta thought the same thing when the VRC7 patches were revised; the older ones were a more varied palette in my ears. But I came to terms with it, since one of the main goals in this project is accuracy (I'm assuming), so be it. Great work on the update jsr, can't wait to play around with it.
.png){kind=avatar}
