![]() Same goes if the file has to be enlarged by more than 529,200 bytes. That's pushing the limits, but if that much audio needs to be cut off, there's likely something very wrong with the wave to begin with. And finally, it will not resize the file such that by default, no more than 3 seconds of audio will be lost, which equals 529,200 bytes. Trailing bytes, should they be present, will be removed before the final resizing attempt. The header will be checked to ensure you decoded it correctly. Resizing ISO files is no sweat, but wave files are given extra special attention. So, with that info, this application will check your ISO and wave files in the folder you select against the verified TOC data and resize the files if necessary. With this data, I know exactly how many bytes in size each of your track files should be, both for wave and ISO. Now, how does TocFixer address this problem? Well, it's compiled with a TOC database of PC-Engine CD-ROMs collected by Squaresoft74 from original silver owners. But anyhow, there's your background information on why the vast majority of ISO/MP3/CUE archives suck as a means for archiving PC-Engine CD-ROMs. However, there are some games that will dynamically examine their own TOC at runtime when it's time to play the next audio track, but they're few and far in between such as "Ys IV: The Dawn of Ys." Such images would have none of the above aformentioned problems discussed so far. That's not the issue! The issue is that most game code has the LBA offset hard-coded, which is what's used when it wants to play an audio track. Never mind the lossiness of the encoding process. So what happens when you've decoded your MP3s to waves and now you've got your ISO/WAV/CUE image file set mounted with daemon tools or you try to burn it? Well, the offset of where every audio track begins will be different, again, since the waves don't have their original file size. That is, the size in bytes the wave originally had before it underwent MP3 encoding. The problem, however, is that when a MP3 decoder decodes the wave back, it doesn't restore the wave file's original size. This allowed for easy distribution over the Internet obviously. Early in the PC-Engine pirating scene, the idea of using lossy encoders such as MP3 for the redbook audio tracks took off like wildfire because of the huge compression ratios one was able to achieve. It crashes, and/or there are lip-syncing issues during the cinemas, etc. OK, so you've downloaded that crappy ISO/MP3/CUE archive from some site, IRC channel, or newsgroup, but after decoding the MP3s to waves, then mounting or burning the image thereafter to play it, you find it's unstable. ![]() This tool, using Square's TOCDB data, will resize MP3 decoded wave files back to their original file sizes, thus restoring the TOC of the image to what it should be. TocFixer v1.01 (for ISO/MP3/CUE archives)Ī joint project between Squaresoft74 and myself resulted in what we hope will be the mother of all solutions to the dreaded ISO/MP3 archives that have plagued us for so long. Tools for working with NTFS partitions.Downloads-> PC Engine/TurboGrafx-16 Related Utilities-> TocFixer v1.01 (for ISO/MP3/CUE archives).Tools to produce and corroborate FAT partition integrity.Move, dupe, produce, cancel, expand, and shrink hard fragment partitions.Format external and internal hard drives. ![]()
0 Comments
Leave a Reply. |