Welcome to Smash Boards, the world's largest Super Smash Bros. 64, Smash Bros. Melee, and Smash Bros. Brawl community! Over 110,000 Smash Bros. fans from around the world have come to discuss these great games in over 4 million posted discussions!
You are currently viewing our boards as a guest, which gives you the ability to view most discussions and articles. By joining our FREE community you will be able to post new topics and reply to threads, communicate privately with other SmashBoards members (PM), sign up for Smash Bros. tournaments, and access many other special features. Registration is fast, simple and absolutely free, so please, join our community today!
If you have any problems with the registration process or your account login, please contact support.
You see where it says "Snapshot" in the grey box ? Well, with this image, the word is different (I can't read it, it's Japanese). The word also changes with downloaded images. I think the word might be "traded image" or something like this. This means, somewhere in the .bin file, the "author" of the screenshot must be written. But I'm just speculating.
Well noticed.
I have found three different types of images.
写真 (photograph) for normal photos you take yourself, サンプル (sample) for the snapshot that comes with the game (btw, do we all get the same one? - mine's Wario biting ZSS's sideB midair), and はいしん (distribution) which I am guessing includes both those sent from Nintendo and those sent from friends (going by the description found in the stage creator).
Those marked with はいしん (distribution) cannot be deleted, sent, submitted, or copied/moved to an SD card. Photos copied to SD are marked as 写真 (photograph) wether originally from the Wii that's viewing them, or added by computer.
If somebody would like to prove/disprove the theory on photos from friends being marked as distribution, feel free to add my Brawl and Wii codes (PM me with yours, so I can add you). Or, of course, if you've already got photos from friends.
Also, I uploaded a peculiar image : it came with the game, so I suppose every Brawl copy has it. When selecting it in the menu, one of the word is different :
You see where it says "Snapshot" in the grey box ? Well, with this image, the word is different (I can't read it, it's Japanese). The word also changes with downloaded images. I think the word might be "traded image" or something like this. This means, somewhere in the .bin file, the "author" of the screenshot must be written. But I'm just speculating. This is the link to download the image.
I'm going to upload stages soon.
Hey that third screenshot's link is broken, try reuploading.
Fixed. the three links were not correct actually, because I did not copy paste the correct link. >_<
Quote:
Originally Posted by holizz
サンプル (sample) for the snapshot that comes with the game (btw, do we all get the same one? - mine's Wario biting ZSS's sideB midair)
Yes, mine is also Zamus, who just caught a Wario fish.
Quote:
Originally Posted by holizz
If somebody would like to prove/disprove the theory on photos from friends being marked as distribution, feel free to add my Brawl and Wii codes (PM me with yours, so I can add you). Or, of course, if you've already got photos from friends.
I could try this with you, but I don't have my Wii number right now. I'll have to check tomorrow.
I've been gone all day. To summarize, decryption can be done and decompression can be done (some images are compressed using a LZSS, or similar, method), but I need to finish figuring out the decompression thing. Two of the very small images (black and white) didn't work. I haven't tried any of the new images besides pikachu (which worked). I'm about to start again...hopefully I'll get a breakthrough.
Blargh. I stared for hours at the nearly black and nearly white image hex code, but I can't figure out why those don't decode properly. The program seems to work on every other image .bin I tried it on, however. If I knew how to add attachments, I'd put one on this message, but as it is I'll just upload it to rapidshare. :P
What it is: a .zip file. It contains two command-line .EXE utilities, a DLL, and a .BAT batch file. Please don't try to use them if you're not at least somewhat comfortable with the command line. Hopefully I can come up with a more user-friendly interface once I figure out the last file quirks.
Of course, you should never run .EXE's from someone you don't know. I promise that they don't contain anything harmful as far as I know, but it's always a use-at-your-own-risk thing. :P Oh, and please only run it on actual image files. Other files might cause the decoding thing to go nuts (tons of errors, or a really huge output file, or worst-case, maybe an infinite loop...if it freezes, CTRL-C it!).
You can also run the bin2jpgall.bat batch file, which will convert all .bin's in the current directory, provided bindecrypt and out2jpg are in your current directory as well. The output names are a little ugly though.
ALSO, make sure that cygwin1.dll is in the same directory as bindecrypt.exe and out2jpg.exe. Or you can just copy cygwin1.dll to C:\Windows, which will make it always able to be found.
So what's left to be done: Figure out what's wrong with the algorithm for a small portion of images. I'd appreciate if you could try running this on various images, especially maybe some with hardly any color variations, and see if you get any error messages from the out2jpg program. If you find such a .bin, please send it my way.
Also, this doesn't automatically detect widescreen or non-widescreen. I just looked, and apparently in the decoded, decompressed output (one of the bytes I stripped), one byte is 1 for widescreen and 0 for non-widescreen, so I guess I could work that into a resize. But if anyone has any ideas for filtering methods (a Python program using PIL or whatever), let me know. I feel that's a little less urgent though.
What it is: a .zip file. It contains two command-line .EXE utilities, a DLL, and a .BAT batch file. Please don't try to use them if you're not at least somewhat comfortable with the command line. Hopefully I can come up with a more user-friendly interface once I figure out the last file quirks.
That's very nice for those running Windows, and who don't want to write their own tools.
So, some source, please? I'd be happy with just a description of how to do it.
That's very nice for those running Windows, and who don't want to write their own tools.
So, some source, please? I'd be happy with just a description of how to do it.
Not to be rude, but the source for decryption will not be forthcoming. Someone was very kind to provide necessary information, and that information is not going to be spread by me.
If you want a Linux version of the decryptor, I may be able to provide that.
As for the image decompression, I'd be glad to let someone else look at it since maybe they can figure out the issue with certain images not working. My code is sloppy, of course, so put on your style goggles.
Anyway, maybe I'll get time to post the image decompression code tomorrow, along with what I've found out/been told about the compression. I hope it will be helpful.
Anyway, maybe I'll get time to post the image decompression code tomorrow, along with what I've found out/been told about the compression. I hope it will be helpful.
I'll certainly look at it when you do, and see if I can help.
Note that the LZSS compression is used on more than just the JPEGs (it'd better be, since it's pretty much ineffective on those). I've only checked the first stage in the zip holizz uploaded, but it appears to use the same compression, and in fact out2jpg gives the same error on it as on white.out and black.out.
Quote:
Originally Posted by GTCoder
But if anyone has any ideas for filtering methods (a Python program using PIL or whatever), let me know. I feel that's a little less urgent though.
ImageMagick is a good set of command-line image processing utilities that might be suitable. They also have libraries for various languagues, if you'd prefer to use those.
Linear Mode
