Editing Save disk space for ISOs
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | Disc images (commonly known as ISOs, but ISO is actually a specific format) are faithful software recreations of game discs (when made correctly). However, with disc sizes ranging from 700 MB (CD | + | Disc images (commonly known as ISOs, but ISO is actually a specific format) are faithful software recreations of game discs (when made correctly). However, with disc sizes ranging from 700 MB (CD), 1.4 GB (GC Mini-DVD), 4.7 GB (single-layered DVD), and 25 GB (Blu-Ray), they can get pretty taxing for storage, especially when newer generations of consoles games are getting bigger in file sizes. |
It wouldn't be so bad if not for the fact that the game data itself is often times only a fraction of the actual disc size - for instance, the ''Super Mario 25th Anniversary'' Wii disc itself is a 4.7GB, when really the actual game data is only a single SNES ROM (12 MB of useful data, to be precise) and nothing else. Naturally, one would want to trim this extra "fat" as much as possible, which is what this page aims to help to achieve. Most of the information here is based partially on this [https://www.reddit.com/r/emulation/comments/3g933n/guide_reduce_the_size_of_your_ps2_gc_wii_x360_ds/ guide]. | It wouldn't be so bad if not for the fact that the game data itself is often times only a fraction of the actual disc size - for instance, the ''Super Mario 25th Anniversary'' Wii disc itself is a 4.7GB, when really the actual game data is only a single SNES ROM (12 MB of useful data, to be precise) and nothing else. Naturally, one would want to trim this extra "fat" as much as possible, which is what this page aims to help to achieve. Most of the information here is based partially on this [https://www.reddit.com/r/emulation/comments/3g933n/guide_reduce_the_size_of_your_ps2_gc_wii_x360_ds/ guide]. | ||
Line 17: | Line 17: | ||
:* BIN/ISO is the full disc data, including Audio-CD sound data and game data | :* BIN/ISO is the full disc data, including Audio-CD sound data and game data | ||
:* CUE is the datasheet file | :* CUE is the datasheet file | ||
− | : '''Light Dump:''' ISO + MP3 | + | : '''Light Dump:''' ISO + MP3/WAV + CUE |
:* ISO is the disc data with only the game data | :* ISO is the disc data with only the game data | ||
− | :* MP3 | + | :* MP3/WAV is the sound data from the Audio-CD, but these formats take much less disk space |
:* CUE is the datasheet file | :* CUE is the datasheet file | ||
Line 27: | Line 27: | ||
* '''Gain:''' Several hundreds of MBs to just a few dozens, depending on how much this specific game relies on the Audio-CD sound format | * '''Gain:''' Several hundreds of MBs to just a few dozens, depending on how much this specific game relies on the Audio-CD sound format | ||
* '''Tools Used:''' Load the BIN+CUE using a virtual drive, then use a CD dumping tool | * '''Tools Used:''' Load the BIN+CUE using a virtual drive, then use a CD dumping tool | ||
− | * '''Can be reverted?''' Yes, just burn the ISO+MP3 | + | * '''Can be reverted?''' Yes, just burn the ISO+MP3/WAV+CUE again using a CD burner tool (ImgBurner) either to a physical disk or as an ISO+BIN file. Lossy audio formats will result in data loss. |
* '''Playable on Hardware?''' No, but can be reverted to be | * '''Playable on Hardware?''' No, but can be reverted to be | ||
* '''Playable on Emulators?''' Anything that supports loading from .cue files, or direct from the optical drive (if you use a virtual disc loader like CDEmu). Some aren't compatible with MP3, if that's the case, convert them to WAV with MP32WAV. You may need Sega Cue Maker. | * '''Playable on Emulators?''' Anything that supports loading from .cue files, or direct from the optical drive (if you use a virtual disc loader like CDEmu). Some aren't compatible with MP3, if that's the case, convert them to WAV with MP32WAV. You may need Sega Cue Maker. | ||
Line 49: | Line 49: | ||
===CHD Compression=== | ===CHD Compression=== | ||
− | * '''Archive-quality dump?''' | + | * '''Archive-quality dump?''' Yes (with CHD version 5) |
* '''Gain:''' Immediate | * '''Gain:''' Immediate | ||
* '''Tools Used:''' chdman (included with MAME) | * '''Tools Used:''' chdman (included with MAME) | ||
* '''Can be reverted?''' Yes, using extractcd (included with MAME) | * '''Can be reverted?''' Yes, using extractcd (included with MAME) | ||
* '''Playable on Hardware?''' No. | * '''Playable on Hardware?''' No. | ||
− | * '''Playable on Emulators?''' MAME, DuckStation, PCSX2 (since March of 2021) | + | * '''Playable on Emulators?''' MAME, DuckStation, PCSX2 (since March of 2021) and DEmul. Some libretro cores for other emulators are starting to add support. |
* '''Can process multi track bin files?''' Yes. | * '''Can process multi track bin files?''' Yes. | ||
− | MAME uses the CHD format for disc images in general and includes tools to convert back and forth. Before MAME v145, CHD was in version 4 and it bumped to version 5 from MAME v146 and further. The | + | MAME uses the CHD format for disc images in general and includes tools to convert back and forth. Before MAME v145, CHD was in version 4 and it bumped to version 5 from MAME v146 and further. The CHD v5 uses 7zip's LZMA compression on the game data and lossless FLAC compression for the audio data to optimize compression even further than using BIN+CUE+MP3/WAV data separation alone. CHDv5 is truely lossless. |
'''Instructions''' | '''Instructions''' | ||
− | Place | + | Place chdman.exe and extractcd in the same directory as the dumps you want to compress (dumps must be in BIN+CUE format or GDI). Open Command Prompt and navigate to the directory where you placed chdman.exe and input one of the following: |
− | * BIN/CUE-GDI to CHD: | + | * BIN/CUE-GDI to CHD: <code>for /R %i in (*.cue, *.gdi) do chdman createcd -i "%i" -o "%~ni.chd"</code> (Windows) |
− | + | * CHD to BIN/CUE: <code>for /R %i in (*.chd) do chdman extractcd -i "%i" -o "%~ni.cue"</code> (Windows) | |
− | |||
− | * CHD to BIN/CUE: | ||
− | |||
− | |||
Alternatively, if you only need to do one file you can use this: <code>chdman createcd -i "<FILENAME>.cue" -o "<FILENAME>.chd"</code> | Alternatively, if you only need to do one file you can use this: <code>chdman createcd -i "<FILENAME>.cue" -o "<FILENAME>.chd"</code> | ||
If you have one of the European PSX games that features LibCrypt copy protection, then you will have a .sbi file in addition to the .bin/cue file. You will still need to have the .sbi file in the same directory as the game file (in this case, the newly created CHD file) in order to run. | If you have one of the European PSX games that features LibCrypt copy protection, then you will have a .sbi file in addition to the .bin/cue file. You will still need to have the .sbi file in the same directory as the game file (in this case, the newly created CHD file) in order to run. | ||
− | Note that multi-track bin files will be combined | + | Note that multi-track bin files will be combined. |
==PlayStation 1== | ==PlayStation 1== | ||
Line 86: | Line 82: | ||
* '''Archive-quality dump?''' No | * '''Archive-quality dump?''' No | ||
* '''Gain:''' Immediate (ISO size decreases a lot). | * '''Gain:''' Immediate (ISO size decreases a lot). | ||
− | * '''Tools Used:''' [https://www.reddit.com/r/PSP/wiki/psx2psp PSX2PSP], Popstation MD GUI, [https:// | + | * '''Tools Used:''' [https://www.reddit.com/r/PSP/wiki/psx2psp PSX2PSP], Popstation MD GUI, [https://www.psx-place.com/threads/w-i-p-utilities-cdda-enabler-for-psx-eboots-on-ps3.23539/ CDDA-ENABLER] (optimized for PS3) ... |
+ | |||
* '''Can be reverted?''' Yes. For homemade EBOOTs it can be done by using the same tool to generate the BIN+CUE files. For commercial releases from PSN you will have to use [https://github.com/xdotnano/PSXtract PSXtract]. There's data loss, but it's negligible in terms of functionality. | * '''Can be reverted?''' Yes. For homemade EBOOTs it can be done by using the same tool to generate the BIN+CUE files. For commercial releases from PSN you will have to use [https://github.com/xdotnano/PSXtract PSXtract]. There's data loss, but it's negligible in terms of functionality. | ||
* '''Playable on Hardware?''' On PSP, not on PS1. | * '''Playable on Hardware?''' On PSP, not on PS1. | ||
Line 94: | Line 91: | ||
===CHD=== | ===CHD=== | ||
− | * '''Archive-quality dump?''' | + | * '''Archive-quality dump?''' Yes |
* '''Gain:''' Immediate (better than PBP). | * '''Gain:''' Immediate (better than PBP). | ||
* '''Tools Used:''' chdman | * '''Tools Used:''' chdman | ||
* '''Can be reverted?''' Yes, using the same tool (chdman). | * '''Can be reverted?''' Yes, using the same tool (chdman). | ||
* '''Playable on Hardware?''' No. | * '''Playable on Hardware?''' No. | ||
− | * '''Playable on Emulators?''' libretro Beetle PSX, Avocado, DuckStation, PCSX2 (since March of 2021 and also because PCSX2 now has PSOne emulation functionality as well, so two-in-one) | + | * '''Playable on Emulators?''' libretro Beetle PSX, Avocado, DuckStation, PCSX2 (since March of 2021, and also because PCSX2 now has PSOne emulation functionality as well, so two-in-one) and PCSX ReARMed. |
==PlayStation 2== | ==PlayStation 2== | ||
Line 134: | Line 131: | ||
* '''Tools Used:''' [https://github.com/unknownbrackets/maxcso#features maxcso], [https://github.com/ps2homebrew/Open-PS2-Loader/blob/master/pc/ziso.py ziso.py (requires python3 and pip install lz4)], [https://www.psx-place.com/resources/psxiso-compression-tool.1258/ PSXiSO (contains ziso CLI tool)] | * '''Tools Used:''' [https://github.com/unknownbrackets/maxcso#features maxcso], [https://github.com/ps2homebrew/Open-PS2-Loader/blob/master/pc/ziso.py ziso.py (requires python3 and pip install lz4)], [https://www.psx-place.com/resources/psxiso-compression-tool.1258/ PSXiSO (contains ziso CLI tool)] | ||
* '''Can be reverted?''' Yes, using the same tool. No data loss. | * '''Can be reverted?''' Yes, using the same tool. No data loss. | ||
− | * '''Playable on Hardware?''' | + | * '''Playable on Hardware?''' YES - Open PS2 Loader. |
− | * '''Playable on Emulators?''' | + | * '''Playable on Emulators?''' NO.<ref>https://github.com/PCSX2/pcsx2/pull/6594</ref> |
===CHD=== | ===CHD=== | ||
Line 143: | Line 140: | ||
* '''Can be reverted?''' Yes, using the same tool (chdman). | * '''Can be reverted?''' Yes, using the same tool (chdman). | ||
* '''Playable on Hardware?''' No. | * '''Playable on Hardware?''' No. | ||
− | * '''Playable on Emulators?''' Yes - PCSX2 (since v1.7.0-dev-1156 | + | * '''Playable on Emulators?''' Yes - PCSX2 (since v1.7.0-dev-1156<ref>Added in 1150 but wasn't built. 1156 is the first release with CHD support. https://buildbot.orphis.net/pcsx2/index.php?m=fulllist</ref>). |
==PlayStation 3== | ==PlayStation 3== | ||
Line 155: | Line 152: | ||
For a long time (before the availability of Cobra and Mamba) the only playable format for PS3 backups (relying on little more than "peek and poke" CFW-provided syscalls to mount the game's folder over the currently inserted disc) but also the least accurate one, with significant compatibility issues (varying on whether the backup is stored on an internal or external drive, whether an original game disc is currently inserted, various optional hacks such as "BDMirror" moving the files to the root of the external drive on demand, ...) | For a long time (before the availability of Cobra and Mamba) the only playable format for PS3 backups (relying on little more than "peek and poke" CFW-provided syscalls to mount the game's folder over the currently inserted disc) but also the least accurate one, with significant compatibility issues (varying on whether the backup is stored on an internal or external drive, whether an original game disc is currently inserted, various optional hacks such as "BDMirror" moving the files to the root of the external drive on demand, ...) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==PlayStation Portable== | ==PlayStation Portable== | ||
Line 188: | Line 178: | ||
Official format for digitally distributed PSP/minis (partially related to the one used for PS1 games), containing a compressed disc image and optionally a custom boot logo. | Official format for digitally distributed PSP/minis (partially related to the one used for PS1 games), containing a compressed disc image and optionally a custom boot logo. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==PlayStation Vita== | ==PlayStation Vita== | ||
Line 217: | Line 199: | ||
* '''Can be reverted?''' No. | * '''Can be reverted?''' No. | ||
* '''Playable on Hardware?''' Yes - with the NoNpDRM plugin. | * '''Playable on Hardware?''' Yes - with the NoNpDRM plugin. | ||
− | * '''Playable on Emulators?''' | + | * '''Playable on Emulators?''' ? |
NoNpDRM is a Vita plugin that generates decrypted licenses (valid for any console) when running an original Vita title, as well as allowing the system to accept those licenses, allowing for playing the encrypted files directly copied from a game card or memory card (by extension the name is therefore also used for such files, or the combination of the game's files and a decrypted license). | NoNpDRM is a Vita plugin that generates decrypted licenses (valid for any console) when running an original Vita title, as well as allowing the system to accept those licenses, allowing for playing the encrypted files directly copied from a game card or memory card (by extension the name is therefore also used for such files, or the combination of the game's files and a decrypted license). | ||
Line 380: | Line 362: | ||
Ideal format for game modding, less so for playing on console due to Loadiine's intrinsic modus operandi (appearing to the OS as the host title, with potentially different permissions) leading to poor compatibility. | Ideal format for game modding, less so for playing on console due to Loadiine's intrinsic modus operandi (appearing to the OS as the host title, with potentially different permissions) leading to poor compatibility. | ||
− | === | + | ==Switch== |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | See overview of formats [https://yuzu-emu.org/wiki/overview-of-switch-game-formats/ here]. | |
− | |||
− | |||
− | |||
===NSZ=== | ===NSZ=== | ||
* '''Archive-quality dump?''' Yes | * '''Archive-quality dump?''' Yes | ||
Line 400: | Line 373: | ||
* '''Playable on Hardware?''' No | * '''Playable on Hardware?''' No | ||
* '''Playable on Emulators?''' No | * '''Playable on Emulators?''' No | ||
− | |||
− | |||
==Game Boy Advance / Nintendo DS / Nintendo 3DS== | ==Game Boy Advance / Nintendo DS / Nintendo 3DS== | ||
Line 456: | Line 427: | ||
* '''Playable on Hardware?''' Yes. If the rebuilding process didn't damage anything vital. | * '''Playable on Hardware?''' Yes. If the rebuilding process didn't damage anything vital. | ||
* '''Playable on Emulators?''' Yes - Xenia. | * '''Playable on Emulators?''' Yes - Xenia. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
=Other Tricks= | =Other Tricks= | ||
Line 467: | Line 433: | ||
===NTFS Compression=== | ===NTFS Compression=== | ||
− | You can enable filesystem-level compression (like "NTFS Compression" in Windows) for the directory containing your ISOs/ROMs. This has a very noticeable space gain and doesn't affect the emulator's functionality. It's surprisingly effective. | + | You can enable filesystem-level compression (like "NTFS Compression" in Windows) for the directory containing your ISOs/ROMs. This has a very noticeable space gain and doesn't affect the emulator's functionality. It's surprisingly more effective than many people would like to give this credit. |
* '''Archive-quality dump?''' Yes | * '''Archive-quality dump?''' Yes | ||
Line 511: | Line 477: | ||
** '''Available compressors:''' None. | ** '''Available compressors:''' None. | ||
** '''Transparent?''' On Linux and BSD via kernel. | ** '''Transparent?''' On Linux and BSD via kernel. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* '''Archive-quality dump?''' Yes | * '''Archive-quality dump?''' Yes | ||
Line 537: | Line 495: | ||
Since this results, in most cases, in very noticeable detrimental effects in gameplay (if the game doesn't crash outright), this is nothing short of mutilating the game image. Sadly enough, some of these dumps make it to sharing sites. | Since this results, in most cases, in very noticeable detrimental effects in gameplay (if the game doesn't crash outright), this is nothing short of mutilating the game image. Sadly enough, some of these dumps make it to sharing sites. | ||
− | Avoid resorting to destructive modifications since it can lead to random crashes and unexpected behavior, especially in games with lots of shared assets. [[ | + | Avoid resorting to destructive modifications since it can lead to random crashes and unexpected behavior, especially in games with lots of shared assets. [[http://emulation.gametechwiki.com/index.php/File_Hashes Verify your dumps]] to make sure you don't have these, and if you still want to reduce size, prefer using other methods or uses decompression on demand. One reason to use a destructively modified dump is for burning your own Dreamcast games as GD-ROMs were over a gigabyte in size and CD-Rs top out at 850MB. |
* '''Archive-quality dump?''' No (Removes data) | * '''Archive-quality dump?''' No (Removes data) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=References= | =References= | ||
[[Category:FAQs]] | [[Category:FAQs]] |