The track times are just track times, I believe. Where it says "Track 1" etc. it is just showing you that each track requires a time. (Red text is a description, not content.)
There's no multiline titles, but you should describe them in your comment, though that won't get seen until voting is over. You can try a title like "Song A / Song B / Song C". though it'll look ugly.
Okay cool, just one other quick question. Does anybody know which NSF player was used in previous comps?
It's just I'm having mixed results with my exported NSF in different players, although I just upgraded my FT version to 0.4.1 and the exported NSF was pretty much perfect in foobar2000. In 0.4.0, my high-ish pitched vibrato sounded way off and my low-toned bass wasn't very well received but all is now well in 0.4.1 now.
EDIT: Forget all that nonsense, patch notes are a wonderful thing >.>
Actually volume levels do matter when using different players, and that can really screw up nsfs with expansion chips... I usually try to balance them the same way they are in FT, and raising triangle and/or DPCM. In NSFplay for example, I have APU1 close to max level, APU2 at max, and N163 a bit lower than default
Oh that's fine, I normally listen to nsfs in VitruaNES unless I want to see custom waveforms and stuff so it's effectively the same. It's just that in NSFplay, the 2A03 is very quiet by default, especially the triangle and DPCM which are almost "inaudible" when you have any expansion chip in there.
Yeah, my 2A03 channels are just a tad quieter in VirtuaNSF and NSFPlay and my bass is a tad loud so I guess I'll have to go back into FT and change things around to my liking. Trial and error always perseveres!
Playback is good in both VirtuaNSF and NSFPlay so I guess that's a plus ^^. Thanks both for the suggestions
The more people optimise their NSFs for NSFPlay, the more people will use it in the future. That's how it works, and that's what should happen ideally (NSFPlay is objectively the most accurate NSF player right now).
A good idea is to check the most common players since the volume levels will vary, and it also varied among different games and famicom models so there are no correct levels. Famitracker is modeled after the games and famicom I have so it is accurate at least in that sense, even though NSF players may sound different.
I highly recommend this volume balance with NSFPlay. The reason is exactly what jsr said, because of all the variations of FC's and NES' out there, there is no true volume balance. Further, this volume balance I use here reflects the balance of VirtuaNSF very well, so you can have NSF's optimized for VirtuaNSF and it will sound equally good, or even better in fact with NSFPlay.
Also, with this mostly centered balance, even if it isn't optimized for these volume levels, it still gives a pretty fair balance for the everything, including all of the expansions.
.png){kind=avatar}
