Found a minor bug: when opening a file directly from the file menu (in the recently opened ftms section), if a "Save Changes?" prompt appears and you click "Cancel", the file you were trying to open disappears from the file menu.
I believe in a real VRC6, the clock is driven by the NES CPU, so it would probably be appropriate to use PAL pitch tables for a VRC6 chip on PAL NES with an audio expansion mod. So... this is possibly a bug, but still outside the realm of the NSF format. (Simplest "fix" is probably just to force NTSC when using expansions.)
I'm not sure it is a bug, because aren't the pitch tables contained in the chip itself? If it's being driven by the slowed down CPU of a PAL NES then it makes sense that it would go flat. I think the only reason the PAL NES's own sound wasn't detuned is that it had slightly different pitch tables to compensate for the fact it was running slower. That's presumably the whole reason there was a PAL version of the chip.
I believe in a real VRC6, the clock is driven by the NES CPU, so it would probably be appropriate to use PAL pitch tables for a VRC6 chip on PAL NES with an audio expansion mod. So... this is possibly a bug, but still outside the realm of the NSF format. (Simplest "fix" is probably just to force NTSC when using expansions.)
I'm not sure it is a bug, because aren't the pitch tables contained in the chip itself? If it's being driven by the slowed down CPU of a PAL NES then it makes sense that it would go flat. I think the only reason the PAL NES's own sound wasn't detuned is that it had slightly different pitch tables to compensate for the fact it was running slower. That's presumably the whole reason there was a PAL version of the chip.
jsr wrote:
Expansion chips was only available for famicom which was NTSC, so I haven't bothered with period tables for PAL. It worked earlier (unintentionally), but not now when I changed some things (to make it easier to create period files without messing up).
Exported files are forced to NTSC if an expansion chip is enabled, so that should probably happen in the tracker too.
I think I'm right in saying "case closed", aren't I?
All the hardware does is take the CPU clock and divide it by the number the software provides (via its pitch table), and that's the frequency you get out.
So, what I was saying is that since I believe the VRC6 is controlled by the CPU clock and doesn't have its own internal clock, a VRC6 jury-rigged into a PAL NES would actually play at PAL pitch speeds (requiring PAL pitch tables).
All the hardware does is take the CPU clock and divide it by the number the software provides (via its pitch table), and that's the frequency you get out.
So, what I was saying is that since I believe the VRC6 is controlled by the CPU clock and doesn't have its own internal clock, a VRC6 jury-rigged into a PAL NES would actually play at PAL pitch speeds (requiring PAL pitch tables).
Ah! Sorry for contradicting you when I evidently had no idea what I was talking about. :P
So Famitracker has it's own pitch tables for the 2A03, VRC6, etc.? So the detuning discrepancy is caused by FT switching to its PAL pitch table for the 2A03 (or rather 2A07) and using the (out of tune at 50Hz) NTSC pitch table?
I suppose that means a lot of PAL NES games were flat (I can't imagine many developers going to the trouble of putting in PAL pitch tables). Oh well, slightly flat music was the least of a PAL gamer's worries back then.
Exactly! Besides, it was in tune relative to itself... a much bigger problem was the slow and squashed looking game IMO but that's something that's been discussed to death...
I found a small bug (not sure if this happens for anyone else), but when I was importing .WAV files for my Sonic Spinball FTM, they would only get quieter as I moved the volume slider up in the importer. The peak volume was at around 6, then it would degrade into silence past that. This works as it should in 3.6, which is what I used to get louder samples.
If you click on certain places in an instrument editor window while playing back a song while it is using DPCM, the DPCM channel "clicks" (or resets, I guess).
_______________________
Everything moves real slow when it's 40 below.
Currently having quite a bit of a headache, I wasn't able to read every post but I tried to search for a few key words and didn't seem to see that this had been posted before...
......ANYWAY!
This is just a tiny little nitpick, but I've noticed that the little visualizers frame rate has dropped from 60+ fps to around 15-20 fps. Is there any reason why this would have happened? I have a fairly fast computer, so I couldn't see it being that the program is using too much CPU or something... I'm sure this is bottom priority, but I figured I'd say it anyway.
