SNES MSU-1 Guide

Darksavior

@edale I tried both and made zero difference. I also didn't need to rename to the dx mod, I just renamed the rom to what I already had and it did play the music. Oh well.

edale

Then the problem's probably in the PCM audio itself. I can only suggest getting a different set of PCM audio from elsewhere.

Unless... are you using a what version Pi are you running? Because I doubt Pi Zero's will be able to handle MSU-1 mods easily...

Darksavior

@edale Pi3. I get slowdowns when there's transparencies even at 1.3ghz, so zero won't be an enjoyable experience..

NowArrivingHere

This is a good guide. I can confirm that this setup method works with the Link to the Past DX romhack. I can also confirm that this works with another Link to the Past romhack that adds the same music as Link to the Past DX and adds an FMV intro.

Also, if anyone is interested in the Satellaview expansion module for the Super Famicom and the three exclusive Zelda games that used that for live voiceovers, I can confirm that the English-Translated MSU-1 recreations all work with the guide from edale.

https://en.wikipedia.org/wiki/Satellaview_games_from_The_Legend_of_Zelda_series

Word of warning, these recreations do use FMV and voiceover narration, so with all files included they can get very large
BS Zelda no Densetsu (BSゼルダの伝説, lit. BS The Legend of Zelda) = 2.45GB
BS Zelda no Densetsu MAP 2 (ＢＳゼルダの伝説ＭＡＰ２, lit. BS The Legend of Zelda: Map 2) = 2.45GB
BS Zelda no Densetsu: Inishie no Sekiban (BSゼルダの伝説古代の石盤, lit. BS The Legend of Zelda: Ancient Stone Tablets) = 3.78GB

edale

@nowarrivinghere said in SNES MSU-1 Guide:

Also, if anyone is interested in the Satellaview expansion module for the Super Famicom and the three exclusive Zelda games that used that for live voiceovers, I can confirm that the English-Translated MSU-1 recreations all work with the guide from edale.

I've played Ancient Stone Tablets, which is great (was actually the second MSU-1 game I played; but quite annoying to transfer the save files for the next part on the Pi, unless you ftp to do it).

But those other 2 BS zelda games... I thought those were just remakes of Zelda 1 with updated graphics?

edale

@Darksavior in a few days I may have a new set of PCM files for you for that Zelda:LttP MSU-1 mod.

I've been working with Insidious611 on his Dancing Mad FFVI MSU-1 mod, there were a number of problems with his PCM audio, and in the process of helping him I taught myself how to encode MSU-1 compatible PCM audio.

Pretty much all his PCM audio tracks needed to be deamplified (I'm actually going through and manually normalizing most of his tracks, then using a hex editor to copy/paste the header/loop data back in). A few of his tracks needed to be completely redone (one even had the data for an entire second song in it for some odd reason, and one track desperately needed the intro cut out)

I've managed to develop a sox script to deamplify the PCM audio, and Insidious611 is making me a python script that'll copy the header data over for me, turning this overly complex process into quickly running 2 batch files.

Once Insidious611 codes the script for me, it'll only take me like 10 minutes to deamplify the PCM files for that Zelda MSU-1 hack, which should hopefully remove that distortion you were experiencing (won't help with the slowdowns though).

Guy-Sensei

Has anyone managed to get MSU-1 successfully working with network share?
Everything works fine when I run games directly from the SD card, but I only get original music and no videos (basically non-MSU-1 version of the game) when using network share.

Darksavior

@edale Nice, I'll try them when it's available, thanks. I believe all that amplified music from EVERY msu1 game does have some crackling of some sort. In mmx1, the msu1 audio is fine, but the sound effects are the ones that randomly have scratchy audio.

I guess these msu1 games were made for sd2snes and not for emulators.

edale

@darksavior Yea, most of the earlier MSU-1 mods had the audio normalized for playback on the SD2SNES, since playback on the original system is the biggest selling point of MSU-1 mods.

Prior to the fix being made in SD2SNES v1.7, there was a bug in the MSU-1 emulation chip that made it so the PCM audio needed to be really loud to play normally. This was obviously a detriment to emulation users. Most MSU-1 modders just made a second patch which tricked the audio into playing quieter for emulators.

Once the 1.7 upgrade went out for SD2SNES, MSU-1 modders can have their sound normalized normally, and it'll play right across all platforms.

edale

@Darksavior Insidious611 hasn't gotten me that script yet, but turns out I don't need it for this. In fact, I don't need to edit the PCM files at all. It's already been done by someone MUCH more qualified than me.

Qwertymodo, one of the leading authorities on MSU mods, the guy that coded pretty much the only tool that lets you create MSU-1 audio without having to hex-edit the header and loop info in, the guy that made the Zelda:LttP DX mod, the guy that coded MSU-1 support into Snes9x, along with a bunch of other MSU-1 related things I likely don't know about yet... He already did it.

Go to: https://www.romhacking.net/hacks/2483/
(you should recognize the link, I've sent it to you before, it's the same mod you're using)

Click download and grab that copy of the mod (97kb).

Open the .zip, and click the readme.

Towards the top of the readme, you'll see 2 download links labeled "Mirror 1" and "Mirror 2".

Grab either of those, they're the fixed PMC files (~500Mb).

You might need to re-patch the game with the updated .ips (best to do it to a fresh copy of the rom, rather than over an already patched one.), but not sure.

Darksavior

@edale That did it, thanks. That site should really change the links..

edale

@darksavior First time I looked at that patch page, I thought the volume fix mentioned was a .ips adjustment like in the "for emulator" patches, but it actually mentions the new .pcm files. When I noticed that, I downloaded and checked the files and saw they were already fixed. I should have noticed that days ago.

At least I didn't notice after I adjusted the audio on the original ones, lol.

Darksavior

@edale In surfing the zeldix site today, I did notice there's a thread with fixed audio tracks. I'll re-download the few games that have given me issues like introducing crackling into sound effects and the music just being too loud, but sounds fine.

edale

@darksavior It wasn't exactly easy, but I've found that thread too. In fact, one of the sets of tracks I was fixing for Insidious had already been fixed by qwertymodo, and me pointing that out to Insidious got qwertymodo himself to show up and help us out with the normalization. Insidious now has a bastardized version of qwertymodo's script for normalizing MSU-1 PCM audio.

I've also added a number of tracks, such as The Black Mages versions of Battle (the basic battle theme), Decisive Battle, and Dancing Mad, and getting some PCM audio to replace ambient sounds when there's a sound that's only called when no music is playing (MSU-1 chips can only stream one data line at a time, so you can't play 2 tracks of PCM audio at once), So far I've got some since white-water sounds going on the raft scenes, looking for other similar cases.

I'll post a link to the open-beta when the release with normalized audio comes out in a few days.

edale

Well... That took more than a few days... here's the "final" beta for the Dancing Mad FFVI MSU-1 mod.

https://github.com/Insidious611/DancingMadFF6/releases

edale

With the official release of Snes9x v1.55 a week ago, the first official release of Snes9x to support MSU, the lr-snes9x emulator core for RetroPie has also been updated.

I'd strongly suggest everyone update (from source) their lr-snes9x on their RetroPie setup.

The new version has fixes for a few MSU related issues, the biggest one I'm aware of is a fix on a bit of code that actually lets music resume properly (so after a battle when you show up on the worldmap, the music will continue where it left off, rather than starting over, as one example). It actually supported it before but wasn't reading the settings properly, so resume didn't work.

hooperre

Is there a way to launch a custom launch bash file so I can call the .sfc file from my /.Legend of Zelda, The - A Link to the Past (USA)[MSU-1] folder containing all the random files? Trying to do this for organizational purposes.

Both of the following work when called from the command line, but not from EmulationStation:

#!/bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _SYS_ "snes" "/home/pi/RetroPie/roms/snes/.Legend of Zelda, The - A Link to the Past (USA)[MSU-1]/alttp_msu.sfc"

or

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-snes9x/snes9x_libretro.so --config /opt/retropie/configs/snes/retroarch.cfg "/home/pi/RetroPie/roms/snes/.Legend of Zelda, The - A Link to the Past (USA)[MSU-1]/alttp_msu.sfc" --appendconfig /opt/retropie/configs/all/retroarch.cfg

Thanks.

mitu

@hooperre Is the command output depending on the starting folder ? I.e. you're in the /.alttp_msu folder when running that command ?

hooperre

@mitu I had the folder name mixed up and it has been updated in my original post.

The command is being launched from the ./RetroPie/roms/snes folder. The actual alttp_msu.sfc and all the .pcm files are located within the ./RetroPie/roms/snes/.Legend of Zelda, The - A Link to the Past (USA)[MSU-1]folder.

I don't think it depends on the starting folder. If I just (from the command line) ran the .sh file containing either one of the blocks of code written above:
sudo bash home/pi/RetroPie/roms/snes/alttp_msu.sh
the file runs correctly, and with all the correct RetroArch configs, but this doesn't happen when launching from EmulationStation. I'm not sure if launching it from ES changes the way that RetroArch handles it somehow or something.

mitu

@hooperre You can see the launch command used by Emulationstation by looking at the /dev/shm/runcommand.log - it should be the first line. That being said, the command you posted (using runcommand) seems like something similar to what Emulationstation would launch.
If the launching commands prove to be the same, try running with verbose logging when you launch from Emulationsation (by using the runcommand launch menu) and maybe there's some clue in the detailed log about what's missing.