It's not so much undesirable as undefined, which is very different from the VRC6 saw, which has a very well defined operation.
Half of the registers are internal data that is not even fully understood, because the registers are write-only. Most emulators leave them blank, but it is known that they carry internal state variables.
Another issue is how to indicate to the user which part of his waveform is supposed to be overwritten by the audio registers? An advanced user may know already how it works, but you don't want regular users accidentally trying to use that part of wave memory.
The other thing is I have a good idea what it will sound like, and I am actually pretty certain no-one would do anything useful with it. If you want a reasonable approximation, just stick 16 to 128 random samples on the end of your existing sample; that's pretty close to what it will be like. I am doubtful that you'd discover any wonderful and exotic new waveforms in there if FamiTracker had the ability to use it.
When editing VRC7 instruments, or when entering notes with the keyboard, it would be better to use note-off instead of note-release.
I suggest this because note-release overrides whatever you put for the instrument's release setting with a value of 5, preventing you from being able to preview what the release parameter is actually doing.
Not sure if this was reported yet but I keep running into various crashes in the beta. Alot of times when I simply close Famitracker, a crash box pops up. Other times, it'll crash randomly as I am tracking. I already talked about this on #Famitracker and Danooct says it doesn't happen for him, so I am assuming it is because I am using XP SP3.
Here's a dump for the random crash while tracking. I don't know how to reproduce the crash while closing the tracker.
Also there is another issue. After some time, a popup saying something like "out of memory" or something like that will come up. It doesn't cause FT to crash or dump anything, but sometimes, I would have to close FT and re-open because it wouldn't let me input anything.
Here's a dump for the random crash while tracking. I don't know how to reproduce the crash while closing the tracker.
Also there is another issue. After some time, a popup saying something like "out of memory" or something like that will come up. It doesn't cause FT to crash or dump anything, but sometimes, I would have to close FT and re-open because it wouldn't let me input anything.
I dunno, whenever I exit, it does that. I use Windows 7.
_______________________
I have turned into a sausage.
I am...not sure if I like the N163 stuff at all! I always loved hearing it in other people's stuff...but wow. It sounds...harsh.
I guess it's the channel switching emulation thing.
Personally, I give kudos to jsr for going all the way with the authenticity, as I'm all about some authenticity. BUT...in this case, the authenticity is not easy on the ears!
I played with the thing for less than 20 minutes, and my ears are still ringing!
Maybe the thing will be of some more use when there is the option to turn that off.
(Hi everybody! I'm still alive! Just busy doing non-NSF-related stuff!)
MooT
EDIT: you can tell I'm sleep-deprived because I say "stuff" and "the thing" repeatedly. LOL.
Or you let me decide what's best for me like the grown man I am.
Or just all shut your butts everything is fine come on
_______________________
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 like both the "authentic" version and the "noiseless" version. They both have their uses and shortcomings. That's why a switch to turn it on/off is what I'd like to see.
given some consideration, I also think it would be wise to provide an option to turn it off.
As a composing tool, I think that Famitracker should be more focused on helping the user compose music for the hardware without limitations that may impair their ability to create it. The hiss should still be implemented so that the user may hear its effects on their music in the event that they wish to play back their song on authentic hardware, but for the sake of actually entering the notes and having a non-impaired ability to create what you wish to create, an option to turn it off is required IMO.
Think about how original N163 music was created for the chip's few respective games. Were the composers/coders creating that music exposed to a hiss when playing back the lines of code they wrote? I recall something about the hiss being cancelled out during the process of the A/V signal being sent to the TV. Of course, I know next to nothing about how chip music was created in the "old days" so to speak, but I doubt that the composers of the music used in the very few N163 games were exposed to an impairing hiss.
Bottom line is, if you want your music to have an accurate hiss, that's all well and good. But for the sake of creating the music in the first place there's no need to make it so challenging.
(Can anyone tell I finally got off my ass and tried to make something with Beta 4? :P)
Also, It's nice to hear your input on this moot. Great to have more people joining in on the discussion.
