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
1. [File] --> [Configuration] --> [Appearance] --> [Colors] --> [Item] contains two typos: 'Higlighed background' and 'Higlighed background 2'.
2. On the toolbar there is an 'About' button and to the right of it is a 'Help' button that does nothing most of the time; 'Failed to launch help' even the help file is there. Press it and your cursor changes to the one with a question mark; click on the pattern editor, and FamiTracker will lead to the help index instead of the pattern editor's own page.
3. Triangle channel still allows channel volumes. (although I recently find myself preferring it and DPCM channel's to show up)
RE: Some bugs in 0.3.6. StablePosted: 2011-02-05 13:51
The triangle channel should allow channel volumes but only the values F and 0 (for on and off.) 0 currently doesn't do anything though. Here's why (attached) - you should be able to create the same effect either directly in the patterns or in an instrument, but currently the only way is using an instrument.
Go to [File] --> [Configuration] --> [General] and uncheck [Preview next/previous frame]. Use your mouse wheel to scroll upwards (PgUp won't trigger this bug). An error message appears:
[quote=FamiTracker]Unhandled exception C0000094.
A memory dump file has been made (MiniDump.dmp), please include this if you file a bug report.
Current module will be saved as crash_recover.ftm. (Please note that this operation might fail)
Application will now close.[/quote]
Here is the memory dump file. Just scroll up to another frame with that setting unchecked and you will always encounter this bug (at least it is true for me).
Go to [File] --> [Configuration] --> [General] and uncheck [Preview next/previous frame]. Use your mouse wheel to scroll upwards (PgUp won't trigger this bug). An error message appears:
[quote=FamiTracker]Unhandled exception C0000094.
A memory dump file has been made (MiniDump.dmp), please include this if you file a bug report.
Current module will be saved as crash_recover.ftm. (Please note that this operation might fail)
Application will now close.[/quote]
Here is the memory dump file. Just scroll up to another frame with that setting unchecked and you will always encounter this bug (at least it is true for me).[/quote]
I tried reproducing it (under WinXP SP3), but I couldn't. I tried with and without cursor wrapping, wrapping across frames, etc. but nothing wrong happened.
_______________________
Follow me on [url=https://twitter.com/jrlepage2a03]Twitter.
I record (some) NSFs on hardware. Feel free to [url=http://www.famitracker.com/forum/posts.php?id=3633]request a hardware render.
I found and fixed the mouse wheel crash bug. It doesn't happen everytime for some unknown reason, but there is a division by zero bug (exception code C0000094).
Btw, the latest version includes this custom exception handler that will handle program crashes. It will create a memory file that contains info about the crash and also attempt to save the module to a file before closing the program (so that crashes won't be as fatal, but I don't know how well it works in practice). This was added as an attempt to identify the unknown crashes that I've seen reported but so far haven't been able to find the reason for.
_______________________
Programmer and developer
Possible Bug/new user error in 0.3.6Posted: 2011-03-07 12:43
Hello, I'm a fairly new user of Famitracker.
Today I upgraded and for some reason my MIDI input isn't functioning correctly. When a key is pressed, it holds the note and won't release it. When other keys are pressed, it just starts arpeggiating between them and I have to kill the sound in order for it to stop. It doesn't happen with the qwerty keyboard input, and 0.3.5 still works fine with my MIDI keyboard.
Is this a possible bug, or am I missing something in the control functions?
Sorry about starting a new thread, should have looked around harder.
I'm using an Alesis Q25 USB/MIDI Keyboard controller.
It's still working for 0.3.5 like I said, and even in 0.3.6 it enters data into the tracker fine without error on the entry side, though it still won't release the sound of the key pressed, which means composing gets rather cacophonous very quickly.
Oddly, I noted when switching between the newer and older versions to test for possible user error on my part that changes in the settings made in 0.3.6 were maintained in 0.3.5 and vice versa. They're in completely different directories.
lautreamont: I think I know what's wrong. Some keyboards sends note offs as note on with velocity = 0 and some keyboards sends actual note off messages. There is a bug that prevents actual note off messages from working correctly (that appeared in 0.3.6), this will be fixed in next version.
Settings are stored in the registry so it's available in all directories.
[quote=jsr]lautreamont: I think I know what's wrong. Some keyboards sends note offs as note on with velocity = 0 and some keyboards sends actual note off messages. There is a bug that prevents actual note off messages from working correctly (that appeared in 0.3.6), this will be fixed in next version.
Settings are stored in the registry so it's available in all directories.[/quote]
I'll just stick with 0.3.5 in the meanwhile then. I'm a beginner, so I doubt I'll be pushing the envelope much, that's why I didn't bother to upgrade until now.
noticed a bug with Pxx on VRC6 square channels. seems like using P81 has a slight detune in the tracker but no effect on NSF export, and P82 in export has the amount of effect that P81 should have...etc.
example attached. exported nsf won't have detune.
it's worth noting that using P7F instead does not cause this problem
) 