Homebrew What kind of photos is the DSi's camera capable of reading ?

[2444666668888888]

just wondering.

 

[RocketRobz]

.jpg files, but they must contain the DSi signature in them in order for the console to read them.

 

[ThisIsDaAccount]

just wondering.

They're jpegs that are signed by the system. If you're looking to add photos to the DSi, someone made this tool but I have not figured out how to use it.

In fact, if someone could tell me how to, it'd be great

 

[thom_tl]

They're jpegs that are signed by the system. If you're looking to add photos to the DSi, someone made this tool but I have not figured out how to use it.

In fact, if someone could tell me how to, it'd be great

Clone the git repo, and rum make on a linux system in the directory(Ubuntu subsystem for windows works fine) and then execute the file with ./sign
Edit: here is the executable compiled with windows linux subsystem
https://mega.nz/#!xSwhwaYa!FxknkkSSsIvfFF0K6JkF--Co1L3NWAXD4u3B0NuexJk

 

[ThisIsDaAccount]

Clone the git repo, and rum make on a linux system in the directory(Ubuntu subsystem for windows works fine) and then execute the file with ./sign
Edit: here is the executable compiled with windows linux subsystem
https://mega.nz/#!xSwhwaYa!FxknkkSSsIvfFF0K6JkF--Co1L3NWAXD4u3B0NuexJk

I did manage to compile it, I'm just not sure what the proper parameters are. Whenever I run the program, it says that the parameters should be this:

"Usage: dsi_sign_jpeg <in.jpg> <out.jpg> <key.bin> [iv.bin]"

I assumed in.jpeg and out.jpeg are the filenames the program will open and save to, and that key.bin is the dsi common key, but I have no idea what IV.bin is.

 

[thom_tl]

I did manage to compile it, I'm just not sure what the proper parameters are. Whenever I run the program, it says that the parameters should be this:

"Usage: dsi_sign_jpeg <in.jpg> <out.jpg> <key.bin> [iv.bin]"

I assumed in.jpeg and out.jpeg are the filenames the program will open and save to, and that key.bin is the dsi common key, but I have no idea what IV.bin is.

It worked fine without iv.bin for me. The files that it outputs are weird but that another thing.

 

[ThisIsDaAccount]

It worked fine without iv.bin for me. The files that it outputs are weird but that another thing.

Yeah when I ran it the jpegs came out all black, so I assumed that the iv.bin is important. I'll give it another go later with the version you compiled, but Im assuming that the iv.bin file is important for some reason

 

[thom_tl]

Yeah when I ran it the jpegs came out all black, so I assumed that the iv.bin is important. I'll give it another go later with the version you compiled, but Im assuming that the iv.bin file is important for some reason

When using a consoleID as iv.bin it changes slightly but it is still messed up.

 

[Apache Thunder]

FYI, I had to use Photoshop to save my JPG to get the correct JPG header format (most other software use a version of JPG that isn't compatible on DSI). Then used a program (jhead I think) to copy an EXIF meta data section from a donar JPG that was generated on a DSI. Then signed that resulting JPG. As a result the "thumbnail" of the JPG will inherit the donar JPG's thumbnail, but the full image will be what was intended. (and not a big deal either if you plan to use your custom JPG as the top screen graphic)

DSi expects 640x480 resolution JPGs. Will not display anything larger. You can use smaller JPGs, but there will be bugs in how it attempts to display that image.

Also when adding new JPGs, note the file names generated by the camera app. You need to use the same naming scheme and when adding new images you have to force the camera app to regenerate the photo database file as it caches what photos you have to a bin file.

You can find it on your SD card at this folder location:

SD://private/ds/app/484E494/pit.bin

That's the location for USA. Note that 484E494 folder name will be different if you are using a different region firmware. Usually there's only one folder in that folder tree anyways unless you also use Flipnote studio. The one that contains pit.bin will be what you need to delete. Delete the pit.bin file and add your new JPG files to the DCIM folder where the camera app expects to find them. It will then regenerate the photo management file and your new photos should show up assuming you signed them correctly.

If you want to use a JPG as your Launcher's top screen photo, you will need to copy your JPG to nand storage and apply the star stamp. Launcher will not show it if it's not starred or if it's not on NAND. Launcher will cycle through your photos randomly on each boot if you have more then one on nand with the star stamp applied.