Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
FamiTracker
Problem: 2xx and 1xx messages cancel out any 3xx effects currently in use (ie. 100 or 200 will reset 320 to 300) -in the tracker-, but not when exporting to .nsf (some other weird funk happens in the .nsf instead.)
GetAround: after using any 1xx or 2xx message, set another 3xx message so that whatever you hear in the tracker will be what you hear on export.
Suggested Fix: make behaviour in the tracker the same as behaviour in .nsf export - that is, insist that 3xx messages need to be reset on their own accord, and have 1xx and 2xx independant of it. That way, you don't need to use a new 3xx message every time you've set a 1xx or 2xx message.
Example [url=http://lunar.shakal.net/temp/pitchconflicts1.ftm]FTM and [url=http://lunar.shakal.net/temp/pitchconflicts1.nsf]NSF.
--
#2
Problem: 2xx and 1xx messages don't reset properly if there's a 3xx value specified (say you have 315 set as a porta value, then using a 102 pitch effect, when you next put a 100 in it'll be ignored.) Again, this only happens on .nsf export. This doesn't happen in the tracker.
GetAround: if you're using a 3xx effect while also using 1xx or 2xx, you have to set another 3xx message when you next change either 1xx or 2xx.
Suggested Fix: same as before - make 3xx function seperate from 1xx and 2xx. These messages seem to disagree with each other at the moment.
Example [url=http://lunar.shakal.net/temp/pitchconflicts2.ftm]FTM and [url=http://lunar.shakal.net/temp/pitchconflicts2.nsf]NSF.
--
#3
Problem: Vxx works differently on the Pulse and Noise channels, and Vxx on the Noise channel works differently inside the tracker and in exported .nsfs. Vxx on Pulse channels only works for the notes you use it on each time, rather than being triggered and the effect carrying on across all subsequent notes until another Vxx message is used. This is the same for the Noise channel, however on the noise channel in exported .nsfs, the duty cycle doesn't revert upon a new note trigger.
GetAround: always reset Vxx messages after using them when using the noise channel. The tracker won't mind if you don't but exported .nsfs will.
Suggested Fix: the obvious thing would be to make Vxx work the same way on the Noise channel in the tracker and in .nsfs. However, I actually think the behaviour on the Noise channel in .nsfs is how it should act. So I would recommend making it so that Vxx is used once and stays set until a new Vxx message is set. The reason I recommend this as opposed to using Vxx on every note is that it's redundant and time consuming to put a Vxx message for every note. I understand that you could just create an instrument with a dutycycle in it, but that somewhat defeats the purpose of having a Vxx effect . Plus it means you have to switch to an instrument without a dutycycle parameter when you want to use Vxx in the tracker, instead of just using the one instrument all the time and using Vxx as you need it.
Example [url=http://lunar.shakal.net/temp/dutycycleissue.ftm]FTM and [url=http://lunar.shakal.net/temp/dutycycleissue.nsf]NSF.
--
Hope this makes sense! The FTMs and NSFs alone will probably make more sense than my ranting anyway.
I'm using the newest WIP - jsr fixed all these bugs now anyway I believe :D Vxx is an effect to change the duty cycle of a channel without having to create an instrument. Very handy for passages with dynamic duty cycle usage, eliminates need to duplicate arpeggio instruments for the sake of changing their dutycycle settings, etc.
Aha, I saw that on NSF the Yxx command doesn't change $4013 settings, so when playing a sample with an offset it is possible to hear the next sample a bit
Edit: oh I LOVE multi-select files when comes to load samples! :D
. Plus it means you have to switch to an instrument without a dutycycle parameter when you want to use Vxx in the tracker, instead of just using the one instrument all the time and using Vxx as you need it.
