Errors When Trying To Modify .brsar

[Kered13]

I'm trying to create a Project M ISO, preferably one that will work both on Dolphin and a Wii. I want the ISO to be as vanilla as possible, but with the 3.5 announcer. I might mess with other changes in the future, but for now I just want this to work.

To do this, I used the 3.6 Netplay builder (console version) as a base. I took the 3.5 smashbros_sound.brsar and used Super Sawndz to insert all the .sawnd files from the 3.6 hackless sfx folder, except the announcer files. This achieved the effect I wanted: I had the new 3.6 sound effects (for example, electrical sounds on shine) with the 3.5 announcer. However, after playing for a few minutes Dolphin displays errors like "Invalid read from to ...". Attempting to open the resulting brsar with BrawlBox gives an index out of bound error, and attempting to extract it with brsar_unpack gives a "don't know about" error. So the .brsar seems to be corrupt.

I've tried using both Super Sawndz and Sawndz, and I've tried using both the PM 3.5 .brsar and the vanilla Brawl .brsar (extracted from my Brawl NTSC ISO) as the base. All result in an apparently corrupt .brsar after inserting some .sawnds. Using either the 3.5 or 3.6 .brsar works without errors (but there are bad sound effects when using the 3.5 .brsar, unsurprisingly).

Is there a way I can fix this? Am I doing something wrong? How can I create a PM ISO with a modified .brsar?

 

[ECHOnce]

I really have no knowledge of sound file editing, but this seems like a pretty round-about method. If you want 3.6 sounds but with the 3.5 announcer, why are you using 3.5 as a base and transferring all the other files from 3.6? Why not just use the 3.6 sound files and replace the fewer announcer files? The more work you create for yourself, the more opportunities you'll have to screw up some mystery factor and not even realize it, and it'll be that much harder to figure out where you went wrong.

Again, not a solution, just some some advice in case it works out a bit cleaner lol. I'm sure a ton of others have already gone about this and done just what you're trying to accomplish, so hopefully someone will be kind enough to offer their build to download aha

 

[Kered13]

I agree that it seems pretty roundabout, but I don't think there is any way to remove a .sawnd (At least Sawndz and Super Sawndz can't do it). So as far as I know I have to start with a .brsar without the 3.6 announcer. I originally used the 3.5 .brsar because I already had it on hand. As I said, I later tried the stock Brawl .brsar after extracting it, but had the same results.

 

[Kered13]

I figured out how to extract a .sawnd, so I tried the following:

From vanilla Brawl I extracted 220.sawnd, 221.sawnd, and 222.sawnd. From 3.5 I took 223.sawnd. I then took the .brsar from the 3.6 Netplay build, and used Super Sawndz to insert the .sawnd's that I had extracted. However, after inserting them the .brsar was corrupt again (couldn't open in BrawlBox, couldn't unpack with brsar_unpack, didn't even try running it in Dolphin). I then tried inserting them one at a time, and found that all of them worked except 220.sawnd. Upon closer inspection, I noticed that 220.sawnd was being inserted into target group 7:

Inserting Sawnd 220.sawnd
Sawndz 0.13
2010-2011 Jaklub
2012 Agoaj

special thanks to mastaklo, ssbbtailsfan, stickman, VILE
Inserting the .sawnd file... Please wait.
target group: 7
7
Modifying Collections
Modifying Groups
Copying
Done.

However, it was extracted from the vanilla brawl group 220. The other sawnds don't do this. They insert into the expected group. I extracted 220 again for good measure, but got the same result: The extracted 220.sawnd inserted into group 7. It makes sense that this would cause corruption, but I don't know why this is happening or how I can fix it.

 

[Kered13]

Bump.

Can anyone help me get this working, please?

 

[Kered13]

I was able to get it to work by using Sawndz to extract the 220 group from the Brawl .brsar and then using Super Sawndz to insert it into my custom .brsar. I don't know why Super Sawndz couldn't extract the .sawnd correctly but Sawndz could, but at least it solved my problem. So now I've got a standalone ISO that I'm happy with.