Whenever you have found a bug/glitch in FamiTracker 0.3.5. beta, post it here so that it will be easier for jsr to check and fix. There are a few rules, though:
1) Do not post anything not related to bugs here. No "ZOMGLOL N106".
2) Do not report a bug which has been repeated by someone unless the conditions are different.
3) Do not spam here.
4) No forum bugs/glitches here; create a new thread yourself or directly send a PM to slize106.
5) If you can distinguish, then post no issues here.
And because this is a beta release, more bug reports means (probably) more bug fixes in the future releases.
Note: In chronological order of the first report the members have posted.
I just found a bug in the VRC7 in which when you try to make a change to the custom instrument (for any channel), the preview sound and/or the whole custom patch itself just seems takes a huge crap at random. O_o' As this is a beta, I wanted you to be aware of this bug (if you aren't already). Yet the preset instruments stay intact and play in preview and patch, so I know this is a custom patch issue. That's funky, a little...
I can't wait for the finished product, as this thing is turning out nicely. ^_^ I am glad you've implemented the VRC7 and it works in sequences. The beta is quite wonderful and it seems the FDS is OK for now, sans exporting issues for both chips which is not something I really pay attention to much myself. The only gripe I have so far is the one above. Otherwise, it's all golden and I'm happy for now. -_-
Edit: It may be that my perception of the slide-bars used for control is a little iffy. The bug I mentioned might not even be a bug at all because I was able to create custom instruments just fine. If it happens again I will add an "edit" to this post.
Edit 2 (here it is): When one reloads anything with custom VRC7 instruments and one attempts to edit the instrument, the instrument shuts off. This must have something to do with the instrument options resetting themselves after a load, but I doubt it because the options reset themselves when I made these instruments and they were still editable. This was done in one session of FamiTracker 035 and not edited after saving it. I am now convinced the issue above has more to do with editing the instrument in sessions after saving it. Case in point: try editing any of the custom instruments in my song below.
_______________________
You now process Dracula's Rib. Good luck processing it...
erm. there were billions of bugs posted in the 0.3.5 thread on the other board. are you going to collate them all in this thread? i don't think people will feel like reposting everything.
I've got a lot of bugs, something like this mass is not rare.
1. Gxx and Sxx don't get along very well. See gxxsxx.png for more information.
2. Sxx resets the status of most effects, such as Vxx, channel volume and Pxx. Have a look at mm1_stage_select.ftm - compare song #1 and #2.
3. Most bugs from 0.3.0. are still here, just to name a few:
- Speed, Tempo, Rows, Frames don't refresh after switching to another song in a single module unless the cursor moves over the control panel.
- Import MIDI function. Oh well, this is the only feature I won't be glad to hear that it will be fixed. It is nearly useless!
- Certain actions (e.g. importing a MIDI) will make anything east to "Create NSF" on the toolbar unless the cursor moves over these settings. This includes Octave, Follow-mode, Row highlight and 2nd highlight.
Dave wrote:
erm. there were billions of bugs posted in the 0.3.5 thread on the other board. are you going to collate them all in this thread? i don't think people will feel like reposting everything.
Resetting the effects of the channel is a good idea, but shouldn't be applied to the Sxx effect. Maybe perhaps a different effect could be used to obtain the same results (I'm so tired of having to reset everything by hand)
Saving instruments en masse makes FamiTracker bug out and close. Not to mention, sometimes it attempts to save an instrument you don't have highlighted
This happened while working with FDS instruments, by the way
here's one not listed: for the FDS channel, 1XX and 2XX are more sensitive in NSF export than they are in the tracker (not sure which is the correct behaviour.)
Which NSF player are you using? I tried NSFplay and the sensitivity is the same as FamiTracker.
Or could you post an example?
Bug.Start attached file,open VRC7 instrument and press any key. The sound does not stop. But it not on all patches. However on the image of the keyboard the button remains pressed.This all is true for the specified order of instruments. If to change instruments places, all in norm.
Create a multi-frame soundtrack. In the final frame, use the code Dxx (where xx is any code other than 00).
The Dxx effect would jump to line XX in frame 00 properly within the tracker. However, when you export the project to NSF & play the song, the track will become corrupted once it starts to loop.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
It sounds normal in the program; just the way I like it but in the NSF the expansion chip's music is so loud that it sounds like it could blow out the speakers. I'm not sure about it restricting the VRC7 I don't get what you mean by that. Other than the instruments being too loud in the NSF it sounds great. I use VirtuaNSF.
