Hacking NDSTokyoTrim - batch trimmer with wifi detection

[Grimalkin]

That's... pretty damn good.

 

[BrianTokyo]

443 games ran.

Trimming took 1146.67 seconds. (With compression in form of .zip)
Trimming took 1053.42 seconds. (No compression)


Original 16.3 GB (17,557,356,544 bytes) (no compression)
Compression 8.94 GB (9,604,091,286 bytes) (With of course)
Trimmed 13.7 GB (14,770,276,585 bytes) (After being trimmed)

Trim 2.6 GB (2,787,079,959 bytes) (Amount trimmed from original)

Thats an average of 2.4 seconds per game.

Not even sure of the point of doing this but oh well.

It should be 1-2 minutes max using the overwrite method with uncompressed roms. Did you specify a different output folder?

 

[Banger]

Yeah that was with choosing an output folder. Will be doing overwrite in a bit.




Edit:

Just retested 15.50 seconds same thing as before but with over writing.


Also I noticed a little glitch, nothing to major but seems to happen all the time, when it out puts the total savings it will become a negative number at a certain point. Not sure that exact turning point is but if you want I could make a video for it if you want. As of right now its -1438.03 MB when the amount trimmed is over 2500 MB, I was watching it and the turning point seemed to be after the 2000 MB mark.

 

[BrianTokyo]

Hmm right, I will fix that in the next version, dumb me, should have used 64 bit integers

(otherwise it caps at 2 GB)

 

[Banger]

Ahh, ok. Nothing major though. Still a very nice program, I am excited about the next version. Any estimated time? Or just a, it gets done when it gets done type of thing?

 

[BrianTokyo]

Probably this week to fix that problem.

 

[test84]

plz add a preview for each rom, so we know how much it will reduce size before trimming it, since i dont trim roms that get reduced less than 5mg, it doesnt worth the risk.

and context menu integrated right click for .NDS files are good, but should be optionally.

 

[BrianTokyo]

That doesn't sound very useful

 

[cpm]

Long time to load? it doesn't take half a second for me, what computer do you have?

The tray icon will be animated while trimming in a future version

i believe it comes down to me not using explorer as my shell... because it loads in the blink of an eye under explorer shell.

i guessing it needs to load some extra modules into memory that are normally present with explorer shell.

 

[betawind]

Wow...this thread is dead without Retman/Wii_DS...

Hows the new build coming along Brian? Not bugging ya or anything, just curious

 

[kellyan95]

I'm on Vista x64, and it's not working anymore >_<
The older version was

 

[BrianTokyo]

build for 64-bit vista: http://www.techsuki.net/64NDSTokyoTrim.exe no rar/7zip support, only zip

haven't worked much at all these days, but ill release something this month before I leave for Tokyo

 

[kellyan95]

It works! Awesome!

 

[betawind]

before I leave for Tokyo

Make sure to take lots of pictures!

 

[enigmaindex]

before I leave for Tokyo


Make sure to take lots of pictures!

Oh for sure. Cant wait for the new release either. Good work =]

 

[ackers]

I'd like to see when you right click a .nds file, 'Trim' would show up in the context menu. It'd be a lot easier than opening up the app and dragging and dropping it just for the one game...

 

[Banger]

I am about 2/3 way done with the "master" trim list which should show approximately how much you would trim with NDSTokyoTrim. Still unsure how I should put it out there. Because as of right now its in the following format.

0001 - Electroplankton (Japan).nds: 4579400
0002 - Need for Speed Underground 2 (USA) (En,Fr,De,Es,It).nds: 4031648
0003 - Yoshi Touch & Go (USA).nds (WiFi): 3213240

You are able to find how much is trimmed be dividing by 1048576

If anyone has any good idea's let me know and I will take them into consideration.

 

[Scalpos]

I am about 2/3 way done with the "master" trim list which should show approximately how much you would trim with NDSTokyoTrim. Still unsure how I should put it out there. Because as of right now its in the following format.

0001 - Electroplankton (Japan).nds: 4579400
0002 - Need for Speed Underground 2 (USA) (En,Fr,De,Es,It).nds: 4031648
0003 - Yoshi Touch & Go (USA).nds (WiFi): 3213240

You are able to find how much is trimmed be dividing by 1048576

If anyone has any good idea's let me know and I will take them into consideration.

Dividing by 1048576 ?? Well, trimming is not compressing. A trimmer removes padded data, because cartridges' size are power of 2 (8M, 16M, 32M, 64M, 128M, 256M, 512M, 1024M, 2048M and so on...). if a game is 33M big, you have to put it on a 64M cartridge, and for such a game, the gain will be important with a trimmer.
But abviously, bigger cartridges are more expensive so it only depends how developers filled the cartridge, but reach the size limit is the best.

So as far as I know, it is not possible to estimate how the rom will be reduced by a trimming tool, without trimming it. Looking at at the compression ratio of a archived rom can give you a rough estimation of the trimmed result, because padded data are, in most cases, redundant and non relevant data. The bigger is the compression ratio, the better will the result.

 

[enigmaindex]

I'd like to see when you right click a .nds file, 'Trim' would show up in the context menu. It'd be a lot easier than opening up the app and dragging and dropping it just for the one game...

Never though of that. Thats a really good idea. Will also keep all the people that bitch about the background quiet.

 

[BrianTokyo]

I'd like to see when you right click a .nds file, 'Trim' would show up in the context menu. It'd be a lot easier than opening up the app and dragging and dropping it just for the one game...

I will add a command line option so you can do "open with.."