USP patch - utility to change FPS, timelimits, frame size

Joined: 06 Aug 2005 Posts: 233 Location: Arlington, VA

1) Download from http://osf1.gmu.edu/~rmansfi2/usppatch/
2) Extract usppatch.exe to some directory
3) Using Ops, download USP.BIN from your camera to the same directory as usppatch.exe
4) Run usppatch.exe
5) Using Ops, upload the new USP.BIN.patched file over your camera's USP.BIN
6) **IMPORTANT:** Click powerdown camcorder
7) Enjoy!

Joined: 21 Jun 2005 Posts: 58

sweet! Thanks@

Joined: 05 Aug 2005 Posts: 1554 Location: jacksonville, fl

very nice! so much easier not having to worry about messing up a field in a hex editor

Joined: 06 Aug 2005 Posts: 19

Excellent, sure beats mucking around in the hex editor.

Joined: 06 Aug 2005 Posts: 233 Location: Arlington, VA

Released version 0.2:

-Created a new serial number option that sets the serial number to a string that describes the settings in the file. For instance, the default camera settings generate this string:

320x240 30f 25hl

Which means the resolution is 320x240, it records at 30 frames per second, and the hard limit is 25 minutes. The soft limit, of course, can be seen at the normal idle screen.

The idea of this feature is to allow you to easily check your camera settings without hooking it up to the PC, downloading your USP file or a video, etc. All you have to do to know what resolution and such you set is to start the camera up with the nerve pinch.

-Included readme with the same instructions that are at the top of this thread
-Included source code. Should easily compile in any C++ compiler on any platform, but assumes a little endian machine. Not that that should be a big deal.

Joined: 01 Jul 2005 Posts: 1542 Location: is everything

Hey, that's a pretty good idea! (much more useful than a generic vanity serial)

BTW - your program seems to crash if you attempt to start it without a file. Not a big deal, but it might be worth trapping.

Joined: 07 Aug 2005 Posts: 282

Great! You should make an option

"Would you to replace the challenge/response key with 0's?"

Anyway, excellent work!

Joined: 13 Aug 2005 Posts: 49

great app. Thanks

Joined: 12 Jul 2005 Posts: 8 Location: Los Angeles, CA

very nicely done

Joined: 14 Aug 2005 Posts: 36

GWRedDragon wrote:

-Included source code. Should easily compile in any C++ compiler on any platform, but assumes a little endian machine. Not that that should be a big deal.

It is a big deal. There are lots of Macs. Sales figures are misleading
because Mac users don't often buy new computers. (less spyware,
fewer gamers...)

At least mark the places in the code that need fixing. You could do this
with do-nothing macros, like so:

#define CPU_TO_LE32(x) (x)
#define LE32_TO_CPU(x) (x)
#define CPU_TO_LE16(x) (x)
#define LE16_TO_CPU(x) (x)

Then I just need to change the definitions and I'm all set.

Posted: Wed Aug 24, 2005 11:53 pm

Or you could do it yourself and submit the patch to GWRedDragon. That's the beauty of having access to the source.

I haven't looked at the source, but it should be pretty easy to identify - basically look for any code that converts character strings into short ints (or equivalent), and visa versa. There won't be a lot of them.

Joined: 14 Aug 2005 Posts: 36

BillW wrote:

Or you could do it yourself and submit the patch to GWRedDragon. That's the beauty of having access to the source.

I sure know this, which is why I only really begged to have the spots
marked right. I can add the byte swapping code myself.

BillW wrote:

I haven't looked at the source, but it should be pretty easy to identify - basically look for any code that converts character strings into short ints (or equivalent), and visa versa. There won't be a lot of them.

Depending on the camera, some might not need conversion. I guess I
can assume that the USB protocol itself is little-endian, but I don't know
if it still is after it passes through the chipset, OS, and libusb.

Posted: Thu Aug 25, 2005 12:38 am

I took a quick look at GWRedDragon's source. The only endian specific code I see is...

Code:

//Make a descriptive serial number
string camid;
camid.clear();
camid+=tos(*((unsigned short *)(&buffer[0x1c8])));
camid+="x";
camid+=tos(*((unsigned short *)(&buffer[0x1ca])));

The short passed to tos may will be the wrong byte order on an endian-different machine. Using your macro scheme, this is what you want...

Code:

camid+=tos(LE16_TO_CPU(*((unsigned short *)(&buffer[0x1c8]))));
camid+="x";
camid+=tos(LE16_TO_CPU(*((unsigned short *)(&buffer[0x1ca]))));

Joined: 06 Aug 2005 Posts: 233 Location: Arlington, VA

Okay, I added big endian support and uploaded as 0.3. All you should have to do is comment out the line that defines "LITTLE_ENDIAN" at the top of the file.

Dang! Too late...I should have called it "FOLLOWER_OF_LILLIPUT".

Still no middle endian support Razz

Joined: 15 Aug 2005 Posts: 11 Location: LAS VEGAS

I used the utility to make the new bin file. It seems to work but not completely. When I let it record to the maximum time it will stop recording and say ready. After I down load the movie it will not play with windows player. It will play with the divx player. When I list the properties for the movie file it doesn't have any summary listing. It is like the file was not completed properly. Does any one else have this problem? I set the clip time for less than maximum time.

Chris

Joined: 24 Aug 2005 Posts: 8 Location: D.C.

HOLY SH*T!

Sorry for the semi-profanity but dangit. This little app just made my day. Makes me wish I remebered to stop at Radishack though to get a new soldering tip to resolder the USB cable back on.... Awesome though!