Problem compressing audio in Broken Sword 1

[paul0272]

I'm having problems with compressing the audio in Broken Sword 1

I've got the "Sold Out" BS 1&2 double pack.

I install the game using the installer from the DVD, then copy all the needed files from the installation folder to a new folder.

If I point SCUMMVM at this new folder everthing works perfectly.

I then copy "compress_sword1.exe" and "lame.exe" into this folder, and from a command prompt run

compress_sword1 .

The music files are in a "music" subdirectory and the speech files are in a "speech" subdirectory.

That all seems to work. All the WAV files in the music directory are converted to MP3, and the two speech files, sppech1.clu and speech2.clu, are converted to speech1.cl3 and speech2.cl3 (about 65MB each).

So I delete all the old WAV files, and the two CLU files, and run it from SCUMMVM again.

The music, sound effects, and cutscenes are fine, but when anybody speaks in the game, I just get a mixture of static and high-pitched screeching instead of the speech.

I've installed and compressed BS2 from the same disc using compress_sword2 with no problems.

Anybody have any idea what's going wrong?


Windows XP Home SP3
SCUMMVM 0.12.0
SCUMMVM Tools 0.12.0
LAME 3.98.2

[eriktorbjorn]

The music, sound effects, and cutscenes are fine, but when anybody speaks in the game, I just get a mixture of static and high-pitched screeching instead of the speech.

That's happening to me too, but I don't know why. It works with Ogg Vorbis encoding, so clearly extracting the sounds and putting the new file together is still working. Something seems wrong with the MP3 encoding, though. Maybe the LAME command-line parameters changed again. If so, an older version might work.

Could you file a bug report so that the issue isn't forgotten? It probably affects at least some of the other compression tools as well.

[eriktorbjorn]

Never mind, I think I found the problem. The compression tool uses the -x option to tell LAME that "this is little-endian data". But according to the manual page, it actually means "this is not native-endian data".

I've changed it to explicitly use --big-endian and --little-endian instead. That fix should be in the next daily Windows snapshot, I suppose. At least, I think it always includes the latest tools.

[paul0272]

I grabbed the latest SVN build of the tools and tried it again, and it works perfectly now. Thanks!