You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Beta 10 is definetly more solid than Beta 9 but I've still found a few minor bugs or weird issues, thought I'd compile them and list them:
Pressing the Test octave buttons during driver playback causes poking error windows to appear, maybe having a safecheck for the buttons to see if playback is going on would fix it.
When using a display scale other than 100% in Windows 11, certain things such as the subpattern row number are displayed incorrectly/off view (Funnily enough, setting the scale back to non-100 after opening up hUGETracker sort of fixes it temporarily)
Update 02/05: I noticed that if I start a new song (File > New), this bug fixes itself and the row of numbers displays correctly.
When using the hex notation option in the settings, subpattern jump commands are still in decimal while the row counter is in hex, which can be a bit confusing.
Trying to close a file right after saving still displays the Would you like to save before closing message, perhaps comparing hases between the last saved file and the current data might help with knowing when to display that.
The text was updated successfully, but these errors were encountered:
Beta 10 is definetly more solid than Beta 9 but I've still found a few minor bugs or weird issues, thought I'd compile them and list them:
Pressing the
Test octave
buttons during driver playback causes poking error windows to appear, maybe having a safecheck for the buttons to see if playback is going on would fix it.When using a display scale other than 100% in Windows 11, certain things such as the subpattern row number are displayed incorrectly/off view (Funnily enough, setting the scale back to non-100 after opening up hUGETracker sort of fixes it temporarily)
Update 02/05: I noticed that if I start a new song (
File > New
), this bug fixes itself and the row of numbers displays correctly.When using the hex notation option in the settings, subpattern jump commands are still in decimal while the row counter is in hex, which can be a bit confusing.
Trying to close a file right after saving still displays the
Would you like to save before closing
message, perhaps comparing hases between the last saved file and the current data might help with knowing when to display that.The text was updated successfully, but these errors were encountered: