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
For some reason, Sonic Rush's music has 12 2sflib files in it. If you import the ROM into VGMTrans, lots of duplicate entries for some sequences (mainly the ones with "Blazy Mix" variants) will show up. The duplicate entries are blank, and usually when exported they will be empty. If you import the ROM and not specifically the 2sflib/mini2sf files, it will be very tedious to find the correct sequence to export, even though you can tell in the app that they're empty by playing them back.
For the "Blazy Mix" tracks and "Raisin' Me Up", in order to export the correct sequence with all the samples intact, you actually have to import the correct mini2sf file, because some of the samples/sequence data(?) are only included inside the mini2sf files.
Ideally, it wouldn't be so complicated to export the sequences correctly. The main pain points are the large amount of duplicate entries and the need (in the aforementioned cases) to specifically import the mini2sf file rather than the 2sflib file. Sonic Rush is the only game I'm aware of that has this issue, but I imagine that some other NDS games might also use a similar setup, and those might also benefit from the issues being fixed.
I first found out about this issue about 2 years ago, and at that time it produced a crash in some cases, but I forgot to write up a bug report for it. When testing today I couldn't reproduce the crash.
Steps to reproduce
Load the Sonic Rush ROM, or one of the "NTR-ASCE-USA_z…" 2sflib files from the game, into VGMTrans
Try to play back and export SEQ_1SONIC, SEQ_1BLAZE, ..., SEQ_7SONIC, SEQ_7BLAZE. There will probably be no audio, and the MIDI file generated will probably be blank.
Expected behaviour
VGMTrans should detect if sequences are actually empty/nonexistent, and should not display them in the list.
VGMTrans should (ideally) be able to figure out if a relevant mini2sf file does or doesn't contain additional sequence data or samples, even if that specific file isn't imported by the user. (In some other cases, such as for New Super Mario Bros., a sequence may match multiple mini2sf files, so the user may have to somehow be able to select, or at least be informed that they can select, which mini2sf file to get the additional data from.)
Environment details
Describe the bug
For some reason, Sonic Rush's music has 12 2sflib files in it. If you import the ROM into VGMTrans, lots of duplicate entries for some sequences (mainly the ones with "Blazy Mix" variants) will show up. The duplicate entries are blank, and usually when exported they will be empty. If you import the ROM and not specifically the 2sflib/mini2sf files, it will be very tedious to find the correct sequence to export, even though you can tell in the app that they're empty by playing them back.
For the "Blazy Mix" tracks and "Raisin' Me Up", in order to export the correct sequence with all the samples intact, you actually have to import the correct mini2sf file, because some of the samples/sequence data(?) are only included inside the mini2sf files.
Ideally, it wouldn't be so complicated to export the sequences correctly. The main pain points are the large amount of duplicate entries and the need (in the aforementioned cases) to specifically import the mini2sf file rather than the 2sflib file. Sonic Rush is the only game I'm aware of that has this issue, but I imagine that some other NDS games might also use a similar setup, and those might also benefit from the issues being fixed.
I first found out about this issue about 2 years ago, and at that time it produced a crash in some cases, but I forgot to write up a bug report for it. When testing today I couldn't reproduce the crash.
Steps to reproduce
Expected behaviour
VGMTrans should detect if sequences are actually empty/nonexistent, and should not display them in the list.
VGMTrans should (ideally) be able to figure out if a relevant mini2sf file does or doesn't contain additional sequence data or samples, even if that specific file isn't imported by the user. (In some other cases, such as for New Super Mario Bros., a sequence may match multiple mini2sf files, so the user may have to somehow be able to select, or at least be informed that they can select, which mini2sf file to get the additional data from.)
Additional context
No response
Logs
Click to expand log
The text was updated successfully, but these errors were encountered: