XCI-Cutter

Features:
- cuts off (trims) unused sectors
- optionally cuts in pieces (splits)
- batch processing


This tool reads the XCI-Header to determine the full cartridge-size and the actually used space.

By default, the tool checks if the sectors after the used space/gamedata are really unused (filled with FF).
It refuses to cut, if it finds any data in that area (this check can be bypassed by using "Fast Mode").

The tool can be used to restore these FF-sectors and expand XCI-files back to the full cartridge size.


@ChronoX_ compiled a list with actual datasizes over at:
https://wiki.gbatemp.net/wiki/XCI-Cutter


UPDATE 20.06.2018:
Trimmed and split games are now fully compatible with SX OS!

!!! Important Note: !!!
Dumps that were split with a version before v2.4.2,
have to be joined/uncut using that OLDER version.
And afterwards split again using the NEW version.
!!!

Download:
https://github.com/Destiny1984/XCI-Cutter/releases


Changelog:

v2.4.2:
- changed partsize to make split-dumps compatible with SX OS

v2.4.1:
- Bugfix release
fixed splitting which was broken in v2.4

v2.4:
- added "fast mode" to batch processing
(Direct trim of inputfiles / no safety checks)

v2.2:
Changes to batchprocessing:
- added recursive folder scanning (thanks to @RapidRaid aka getraid)
- add files and folders by Drag&Drop

v2.0:
- added batch processing with optional inputfile deletion

v1.5:
- fixed some exceptions
- implemented optional splitting

v1.0:
Initial Release

 

[MattKimura]

Question, if there's an option to uncut, why do I have to create a separate file and can't replace the original? It's a whole lot of writing to my HDD for no reason.
In the longrun, would exfat be better to use than fat32 for the switch?

 

[jakkal]

Can one good samaritan make a mac app?

Lol mac

 

[MHDestination]

Question, if there's an option to uncut, why do I have to create a separate file and can't replace the original? It's a whole lot of writing to my HDD for no reason.
In the longrun, would exfat be better to use than fat32 for the switch?

That's a safety measure.
The content always gets copied to a new file.
The original files won't get deleted, until the new file was successfully created.

That way you wouldn't risk data loss if something went wrong.

If you want faster processing and less disk usage, then you should use XCI Explorer

 

[DocKlokMan]

No need for alarms. Your tool is sound. BBB just released a PROPER'd Snipperclips owing to the garbage data at end of the first dump.

Haha, knew it. Thanks for the heads up.

 

[ChronoX_]

That's a safety measure.
The content always gets copied to a new file.
The original files won't get deleted, until the new file was successfully created.

That way you wouldn't risk data loss if something went wrong.

If you want faster processing and less disk usage, then you should use XCI Explorer

Maybe you could make it an option that people have to check if they want to modify the original file (at own risk)?

 

[DocKlokMan]

For anyone who is using the cross-platform python script I made for trimming roms, I updated it for much faster trimming. For those who don't know, it's a python3 script that can trim either the original file or make a trimmed copy. It can also re-pad the original or make a padded copy.

https://github.com/AnalogMan151/XCI_Trimmer

 

[snoofly]

Slow it maybe but I’m thinking just set it off in batch mode on yr piracy folder overnight (700 gigs around about, less without a few region dupes). Job done.

 

[Deleted User]

View attachment 125303

XCI-Cutter

Features:
- cuts off (trims) unused sectors
- optionally cuts in pieces (splits)
- batch processing


This tool reads the XCI-Header to determine the full cartridge-size and the actually used space.

Before cutting, it checks if the sectors after the used space/gamedata are really unused (filled with FF).
It refuses to cut, if it finds any data in that area.


@ChronoX_ compiled a list with actual datasizes over at:
https://wiki.gbatemp.net/wiki/XCI-Cutter


UPDATE 28.05.2018:
@garyopa and @AnalogMan confirmed that games trimmed/split by this
tool can be used with XS OS out of the box!


The process is reversable. The tool can be used to restore those sectors
and expand the XCI-files back to the full cartridge size.


Download:
https://github.com/Destiny1984/XCI-Cutter/releases


Changelog:

v2.0:
- added batch processing with optional inputfile deletion

v1.5:
- fixed some exceptions
- implemented optional splitting

v1.0:
Initial Release

Do you have any plans for recursive folder searching for the batch processing?

 

[MHDestination]

Do you have any plans for recursive folder searching for the batch processing?

Yes, uploaded new version with recursive folder scanning.
https://github.com/Destiny1984/XCI-Cutter/releases/tag/v2.2

 

[lordelan]

UPDATE 28.05.2018:
@garyopa and @AnalogMan confirmed that games trimmed/split by this
tool can be used with XS OS out of the box!


The process is reversable. The tool can be used to restore those sectors
and expand the XCI-files back to the full cartridge size.

So there's absolutely no downside?

 

[MHDestination]

So there's absolutely no downside?

none that we know of

 

[lordelan]

none that we know of

Then your tool will save me a lot! Thanks man!

 

[morrison22]

“Can one good samaritan make a mac app?”

Lol mac

I mean, I could benefit from an OS-X version as well so I don’t have to boot a virtual machine. Convenient for sure if it became a thing.

Thoughts?

 

[Maximilious]

On another note:
snip
Thoughts?

This isn't really the thread for your type of question, and it's been answered several (hundreds) other times in other threads on the site. In the end it all boils down to your own personal preference and if you can bear to wait for emuNAND or not. You already know the pros and cons, so the choice is yours to make. I'd recommend not responding to my comment as this discussion really doesn't belong in this thread.

 

[Deleted User]

Any reason why this is much slower compare to using XCI Explorer to cut the roms?

 

[cearp]

I mean, I could benefit from an OS-X version as well so I don’t have to boot a virtual machine. Convenient for sure if it became a thing.

Thoughts?

use this python tool python is alrady built in to mac os, so there's no setup involved.

For anyone who is using the cross-platform python script I made for trimming roms, I updated it for much faster trimming. For those who don't know, it's a python3 script that can trim either the original file or make a trimmed copy. It can also re-pad the original or make a padded copy.

https://github.com/AnalogMan151/XCI_Trimmer

 

[dsrules]

nvm...

 

[xXxSwagnemitexXx]

of course its related to nintendo switch
its under the switch forums lol

just wanted to say

woooooosh

 

[datahoarder]

For anyone who is using the cross-platform python script I made for trimming roms, I updated it for much faster trimming. For those who don't know, it's a python3 script that can trim either the original file or make a trimmed copy. It can also re-pad the original or make a padded copy.

https://github.com/AnalogMan151/XCI_Trimmer

XCI_Trimmer.py -t ittledew2.xci

========== XCI Trimmer ==========

ROM Size: 4 GiB
Trim Size: 2.63 GiB

Checking for data in padding...
Traceback (most recent call last):
File "S:\switch\test\XCI_Trimmer.py", line 165, in <module>
main()
File "S:\switch\test\XCI_Trimmer.py", line 158, in main
trim()
File "S:\switch\test\XCI_Trimmer.py", line 68, in trim
pad_a2 += b'\xFF' * (j)
MemoryError

edit: Do you not have another thread for this? I'm not trying to hijack this one.
Although I do wish it supported a straight cut without copy (in batch), so the tool above will work better for me.

 

[DocKlokMan]

XCI_Trimmer.py -t ittledew2.xci


edit: Do you not have another thread for this? I'm not trying to hijack this one.
Although I do wish it supported a straight cut without copy (in batch), so the tool above will work better for me.

I just pushed a fix to break the checks into smaller parts. Try again.