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
Couldn't find this anywhere, apologies if it's already reported and known.
In 0.3.6 Stable, when I select a different instrument (either by clicking one in the list or by using Prev / Next Instrument keys) the newly selected instrument is heard while auditioning or entering notes, but any new pattern data is recorded using the old instrument's number. Typing the desired instrument number manually into the instrument column will cause it to be "picked up" properly.
Example:
1) Pulse 1 currently using Instrument 00
2) Insert note: C-5 00 . ...
3) I hit "Next instrument" key, selection shows as Instrument 01.
4) Insert note: C-5 00 . ...
5) Yell at screen, type "01" into instrument column
6) Insert note: C-5 01 . ...
Also, the US * key (next to "/ (US)" on the Numpad) is no longer recognized. There is an entry for *, but apparently it isn't the correct scan code, because pressing this key in the pattern editor (or highlighting the "Key" dropdown box and pressing it) does nothing, whereas in 0.3.6 b3 it was correctly detected.
Seconded, this bug has made me scare off back to the beta because I just couldn't cope with it. Really would like to make the jump to the new stable since a lot of the requests I'd made before have been added and I'm super grateful for that! So if this gets fixed soon, that would be fantastic.
Interesting bug, although I've always selected intruments by just clicking them manually (which I suppose is a bit inefficient).
_______________________
- A Czar Dolphin
[url=www.youtube.com/user/DukeOnkledNukem]Main YT Channel
[url=www.youtube.com/user/IroncladAlt]YT Music Alt
[url=http://chipmusic.org/ironclad]Chipmusic
I wasn't aware of that bug, it was a special case only in the IT-mode that caused it (where I guess I tried to emulate some behaviour and failed). I've done a number of bug fixes now and have nothing more planned so I think there will be a new version available soon, I will have time to upload a beta tomorrow hopefully.
I don't know what happened to the '*'-key. Just to be sure before I check anything, have you checked that the key (labeled "Num *" in the list) isn't assigned to some other function or the keys list in general configuration by mistake?
And by the way, have you had any more problems with release sequences disappearing since the stable version? I haven't been able to trigger it since the bug in 0.3.5.
Thanks for your report!
Edit: The updated version is available here: [url=http://famitracker.shoodot.net/forum/posts.php?id=1976]http://famitracker.shoodot.net/forum/posts.php?id=1976.
Yo!
Perfect. Instrument bug fixed. Thank you, now we're back in business.
More info on the shortcuts bug:
No, it's not assigned anywhere else.
I've played with it a bit more, and Num * works fine, if I assign it to something else OR assign it to an octave key WITHOUT also assigning Num /.
It seems that I can't have BOTH Num / and Num * assigned at the same time, or only the * will work.
I've tested different key assignments, here is what I've found:
Setting ]} (US) and [{ (US) to octave up and down, respectively: Works as expected, but in reverse (the key for "up" actually goes "down" and vice-versa.)
Setting Num / and Num * to octave up and down, respectively: * Increases octave, / does nothing
Setting Num * and Num / to octave up and down, respectively (reversed order): * Decreases octave, / does nothing
So basically, at the most basic level, octave down and up are reversed in the shortcut editor, but there is also some other problem with Num * and Num / being exclusive, so only one is usable.
Okay, I've sorted it out.
The problem is actually fully with Num / not corresponding to the right keypress in the Shortcut Editor.
When I highlight the key assignment field and press / on my numpad, "/ (US)" is selected. This is actually not the correct key. Num / is the correct key. If I manually scroll through the list and select Num / (and Num *, of course), both octave keys function perfectly, though still in reverse.
So now, the only bug is:
Octave up / down keys are reversed in the Shortcut editor!
You might also consider putting a warning somewhere about selecting key assignments by typing the desired key into the dropdown list directly -- it often doesn't select the keycode you actually typed, so be sure to manually select the desired key by scrolling through the list.
Great. I'll switch the shortcuts, and probably change the behaviour of the key box to receive key-presses instead of only reacting to letters. That's a good point.
on the Numpad) is no longer recognized. There is an entry for *, but apparently it isn't the correct scan code, because pressing this key in the pattern editor (or highlighting the "Key" dropdown box and pressing it) does nothing, whereas in 0.3.6 b3 it was correctly detected.
