Not sure why some people would have false positive with sm4shexplorer... specially with windows defender lol.
Did it happen in 0.04 as well? could be the plugin thing? I really don't know.
Also gonna release a 0.06.4b (I keep making small changes that forces me to update the core) along with sm4shmusic v0.6b.
Im calling it b and will switch automatically to non beta after a few days, but there is a few changes that requires some more testing. Just figured I would share it here since it solves some well know problems:
- fix for libvgmstream: Some people claim they didnt have the bug after this version, so hopefully that'll work for everyone.
- fix for sound desync that some people who removed a song (or blank) were having. Sadly I don't really see a way around starting from scratch, unless you know how to edit the saved xml, but that's seriously gonna take longer.
- unsigned values have been changed to signed (4294967295 will be shown as -1 now), please understand that it breaks the deserialization of any saved xml config.
- Rarity changed to 100 by default
- Unk5 is now known as Play Delay thanks to @Pib
- BLANK files are now automatically removed when loading the list. This is to avoid a lot of confusion. Instead when you click Add, Sm4shMusic will now automatically fill the gaps in IDs (like in a config from scratch, the first ID to be created will be 15)
- MSBT variables names are now sync to the ID of the song, base 36 (so like ID 10 will be SOUNDA, ID 11 will be SOUNDB, etc). It means that the xml doesn't have to hold the information about the label anymore, making it smaller.
Again, this comes with changes that break a xml generation prior to this version. No worries though. if you have working Sm4shMusic compiled files (without warning showing up and all) you will be able to load it with this version and save an xml for this version.
Hopefully there won't be too many changes like that anymore.
Oh also, Ive been asked a few times, so here's how you "reset" sm4shmusic:
Sm4shExplorer loads and extract files in that order:
Modded files (workspace) > Patch files (288/whatever) > LS (vanilla files).
Which means, if you have a file in the workspace folder, it's all sm4shexplorer is going to see.
So, in order to reset the sound dbs, all you have to do is remove the files modified by sm4shmusic in your workspace ( data/param/ui/ui_sound_db.bin (multi-region), data/sound/config/bgm_mymusic.mmb, data/sound/config/bgm_property.mpb and data/ui/message/sound.msbt (multi-region))
Did it happen in 0.04 as well? could be the plugin thing? I really don't know.
Also gonna release a 0.06.4b (I keep making small changes that forces me to update the core) along with sm4shmusic v0.6b.
Im calling it b and will switch automatically to non beta after a few days, but there is a few changes that requires some more testing. Just figured I would share it here since it solves some well know problems:
- fix for libvgmstream: Some people claim they didnt have the bug after this version, so hopefully that'll work for everyone.
- fix for sound desync that some people who removed a song (or blank) were having. Sadly I don't really see a way around starting from scratch, unless you know how to edit the saved xml, but that's seriously gonna take longer.
- unsigned values have been changed to signed (4294967295 will be shown as -1 now), please understand that it breaks the deserialization of any saved xml config.
- Rarity changed to 100 by default
- Unk5 is now known as Play Delay thanks to @Pib
- BLANK files are now automatically removed when loading the list. This is to avoid a lot of confusion. Instead when you click Add, Sm4shMusic will now automatically fill the gaps in IDs (like in a config from scratch, the first ID to be created will be 15)
- MSBT variables names are now sync to the ID of the song, base 36 (so like ID 10 will be SOUNDA, ID 11 will be SOUNDB, etc). It means that the xml doesn't have to hold the information about the label anymore, making it smaller.
Again, this comes with changes that break a xml generation prior to this version. No worries though. if you have working Sm4shMusic compiled files (without warning showing up and all) you will be able to load it with this version and save an xml for this version.
Hopefully there won't be too many changes like that anymore.
Oh also, Ive been asked a few times, so here's how you "reset" sm4shmusic:
Sm4shExplorer loads and extract files in that order:
Modded files (workspace) > Patch files (288/whatever) > LS (vanilla files).
Which means, if you have a file in the workspace folder, it's all sm4shexplorer is going to see.
So, in order to reset the sound dbs, all you have to do is remove the files modified by sm4shmusic in your workspace ( data/param/ui/ui_sound_db.bin (multi-region), data/sound/config/bgm_mymusic.mmb, data/sound/config/bgm_property.mpb and data/ui/message/sound.msbt (multi-region))
Last edited by deinonychus71,