11 March 2016 - Forum Rules
Started by keisui, February 01, 2022, 07:08:42 AM
Quote from: FAST6191 on February 01, 2022, 10:56:39 AMI am not sure what you are doing.Are you replacing a sound and it is not playing or are you trying to add another sound that was never in the game (as opposed to simple replacement) and have the game play that?I can't say I have ever really messed with nitro studio 2 for DS sound related hacking purposes (usually manual, guided by tools like vgmtoolbox, maybe with the occasional fiddling with vgmtrans).For the former Usual guesses are1) Mismatch of audio styles. If it was originally 16KHz 8 bit PCM then has to be that (or you go through the hassle of making it work by editing everything down and up the line), even if the program nominally will import it and play back on PC.2) Some kind of pointer fun. Can you compare before and after in the edited file to see what changed? Sometimes an offset might be hardcoded and could be troubled if something has changed.For the latter. Yeah you are going to have to figure out how the game calls the sound and tell it to call your new one. If you know where the data for the third sound is in memory (should be the same as the file as seen in the SDAT) then search a memory dump for it and see where it is. Set break on read in a debugger for that area and somewhere a bit further back should be the call for the file, if 1 and 2 are already randomised then you might even be able to borrow code there rather than running off to find a reliably random piece of DS memory to choose between 3 and whatever your new one is, you may face some issues with memory if all three original sounds are there but it is probably going to be tightly controlled enough that you can be spared that.Possible alternative. I don't know if you can have a start position in the call, might be possible to instead have it randomise where in the base sound it plays (lazy man's genius cousin being maybe you abuse the suspect timings of SDAT/SSEQ setups to trigger a loop and ending depending upon something).
Page created in 0.036 seconds with 20 queries.