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
I've noticed that if I try to open the last STI file I've ripped via std while std is still open, Windows 10 complains about the file being used. Then I have to close (or perhaps rip another instrument) in order to access the file from SNES Tracker.
Ensure this problem is not present in the Tracker. Try getting two instances of SNES Tracker open to experiment with saving one of (song, instrument, sample) from one instance and immediately load it from another.
Compare SdlNfd usage in SNES Tracker with std. Remember that std doesn't autocomplete saved file extensions like SNES Tracker v0.2.3 now does. So std must not be using SdlNfd fully, I guess?
The text was updated successfully, but these errors were encountered:
I've noticed that if I try to open the last STI file I've ripped via std while std is still open, Windows 10 complains about the file being used. Then I have to close (or perhaps rip another instrument) in order to access the file from SNES Tracker.
This might be related to #138.
Ensure this problem is not present in the Tracker. Try getting two instances of SNES Tracker open to experiment with saving one of (song, instrument, sample) from one instance and immediately load it from another.
Compare SdlNfd usage in SNES Tracker with std. Remember that std doesn't autocomplete saved file extensions like SNES Tracker v0.2.3 now does. So std must not be using SdlNfd fully, I guess?
The text was updated successfully, but these errors were encountered: