Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Chucho

Pages: 1 [2] 3
Archived porting threads / Re: Canon 5D Mark III
« on: October 18, 2012, 01:23:49 AM »
I remember when a1ex first join the google mailing list. There was already an Alex in the mailing list, so he added the 1 so he wouldn't be confuse with the other Alex.

General Chat / Re: GoPro Hero 3
« on: October 17, 2012, 09:51:23 PM »

I wonder how much hero 3 differs from the original hero.

It's also a great way to see which camera can fly the farthest. I'm using a buffer and I really like the images that I'm getting.

Tutorials and Creative Uses / Kaleidoscopic acid trip with magic lantern
« on: October 12, 2012, 09:57:56 PM »
Great idea from Oscar Lhermitte. You will need a electric drill or a buffer. Set fps to 15fps. And start spinning. Some great example of what you can do from Oscar Lhermitte web page

Reverse Engineering / Re: (M)JPEG encoder
« on: October 07, 2012, 05:14:09 AM »
From function 0xff14b1d8 PtpPropMovie R1 = 0x80020009 R0= pointer 5BD4 --> 0x44E002C Off (not connected to EOS Utility), 0x2B6002C On (connected to EOS Utility). How do I test this? Off topic how can I use NSTUB(0xFF010BA4, memMap) and NSTUB(0xFF010C20, objInfo)

China vendors might actually do it, especially the shadier ones. But then docs and support is nil.

But no reason why 5DIII/600D can't get close to this quality. 5dIII especially close to pulling off raw with CF speeds.
The digital bolex is just a modded prosilica gx2300. There's documentation on the sensor and processor. There no documentation on anything canon made. It's hard enough with the right documentation. And to build a camera you have to built it around your sensor and processor needs. Look into if you want a open source camera.

I don't see how you can use a canon camera. There no documentation on the sensor or the processor. I have been working on my own private project for a year now, it's based on this flow chart I'm using a 1/2.3 sensor for testing. I want to get a Cmosis sensor but I ask them for the specs and prices but they are asking me for the company I work for. I told them is for a private project and I never heard for them. Building your own camera is not simple. It's a great learning experience even if you fail.

Reverse Engineering / Re: (M)JPEG encoder
« on: October 02, 2012, 11:24:41 PM »
What exactly needs to be worked on? Except the enabling LV jpeg buffer in some models.

Reverse Engineering / Re: (M)JPEG encoder
« on: October 02, 2012, 08:42:04 AM »
your right, here is a stream from the 600d. Lets start with frame 1 0x42100070 just above this frame there is a line with 2 addresses and other information, the addresses are 0x42100010  and 0x42310110. here's a table with the address of the frame and address just above the frame.
Frame1 0x42100070               0x42100010, 0x42310110
Frame2 0x42130080               0x42100060, 0x42190090
Frame3 0x42160090               0x42100060, 0x421c00a0
Frame4 0x421900a0               0x42100060, 0x421f00b0
Frame5 0x421c00b0               0x42100060,0x422500d0
Frame6 0x421f00c0                0x42100060, 0x422500d0
Frame7 0x422200d0               0x42100060, 0x422B00f0
Frame8 0x422500e0               0x42100060, 0x422B00f0
Frame9 0x422800f0                0x42100060, 0x422e0100
Frame10 0x422B0100               0x42100060, 0x42310110
Frame11 0x422E0110               0x42100060, 0x42371030
Frame12 0x42310120               0x42100060, 0x42370130
Frame13 0x42340130               0x42130070, 0x42370130
Frame14 0x423d4160               0x42130070, 0x42404160
0x42100010               0x43fffff0, 0x42100060

Reverse Engineering / Re: (M)JPEG encoder
« on: October 01, 2012, 07:11:48 PM »
1%, yes I wanted to do that but I found it hard. The jpegs are aways different sizes. And closing the file doesn't give enought head room to create a new file and staying in sync. Alex mention using memcpy it should work for something like that. Also in 720 60fps the frames alternate in size for example frame 1 would be 0x4404F and frame 2 would be 0x4004F. Maybe just scanning for FF D8 FF E0 and cutting just before might work.

Reverse Engineering / Re: (M)JPEG encoder
« on: October 01, 2012, 05:37:49 PM »
1%, no not yet. I was working on the 600d yesterday connected to my PC. I was looking for the right combination of frames and msleep and them it just stop writing AVI files. I don't know why. My AVI don't play back in any player. I think I'm missing to many tags. I'm still working out the header. I prase the jpegs out of the AVI and check for bad frames.

Reverse Engineering / Re: (M)JPEG encoder
« on: October 01, 2012, 08:48:05 AM »
I was getting to many bad frames in 1080 so I changed it to 720 and over wrote the frame rate to 24. I'm getting less bad frames now and the resolution are the same in both modes, in the 600d the resolution in 1080 is different then in 720. I just notice all the grammar and spelling mistakes in my last post sorry.

Reverse Engineering / Re: (M)JPEG encoder
« on: October 01, 2012, 07:00:53 AM »
It's easy to get 24 fps in the 500d. First I over right fps in 720 mode to 24fps, 720 and 1080 have the same buffer size. And then I create a AVI file File * f = FIO_ CreateFile(CARD_Drive "test.AVI); if (f != (void*) -1)
And then I loop the write file FIO_WriteFile(f, (void*) 0x42004070, 0x41349); msleep(25);
When I'm done with me loop I slap a RIFF AVI header and FIO_CloseFile(f);
I'm still getting some bad frames but It seem to be getting less then before. The 600D is a little harder, there is a row of about 12 frames. And I can't find the right msleep to sync them together.

Reverse Engineering / Re: (M)JPEG encoder
« on: September 27, 2012, 09:43:35 AM »
There already jpegs, all you have to do is prase them out of ram with the .jpeg extension. 0x42100070 is frame 1 plus the size 0x5c010 = 0x4215c80 which is frame 2 and so on. I don't know how many frames they are stored in ram but when you reach the end just loop back to the frame 1.

Reverse Engineering / Re: (M)JPEG encoder
« on: September 27, 2012, 09:05:26 AM »
Connected to EOS Utility I dumped ram and got a stream of jpegs starting @ 0x2100070. The jpegs come one after another all are 0x5c010 size and 1056x704 in dimension.
At 0xa030c0 there were two jpegs, 160x120 in dimension.
Edit: I may have dumped the 0x42100070 region by mistake.

Reverse Engineering / Re: (M)JPEG encoder
« on: September 26, 2012, 07:17:48 AM »
Only works when connected to EOS Utility. How to trick the camera to think it's connected? 0xff14b1d8 maybe?

Reverse Engineering / Re: (M)JPEG encoder
« on: September 26, 2012, 07:00:53 AM »
600d firmware 101 FA_GetJpegSizeForLV pointer --> 0x4FE2B FA_GetJpegBufForLV pointer --> 0x42100070

Reverse Engineering / Re: (M)JPEG encoder
« on: September 22, 2012, 11:54:13 PM »
1%, I don't use IDA, I use good free program. Pel is also a good programmer, photographer  and friend.

Didn't I post this 2 weeks ago in the 5d3 thread? ??? I wouldn't trust anything Andrew posts on his website. :-*

Reverse Engineering / Re: (M)JPEG encoder
« on: September 20, 2012, 08:45:10 PM »
%1, info on WriteEDmacPackMem can be found here

Reverse Engineering / Re: (M)JPEG encoder
« on: September 20, 2012, 05:26:32 AM »
In 0xb40318 FA_GetJpegSizeForLV has flags 0xb402f0 --> 0x18 0xb40308 --> 0x2c
0xb4035c FA_ GetJpegBufforLV 0xb40334 --> 0x18 0xb4034c --> 0x2c
I don't know what this means? I'm working with firmware 101 still haven't updated to 102.
Dumped 0xb3f0e0 to 0xb444b8 found some new function names.

Edit: it looks like 0xb4035c -->FA_GetJpegBufForLV is some how connected to 0xb4250c -->mvrSetD_HD, I don't understand the structure links in this area.

Reverse Engineering / Re: (M)JPEG encoder
« on: September 19, 2012, 10:41:44 PM »
There wasn't any jpeg in ram but I didn't check when recording. I can only dump 8MB at a time of ram when recording before buffer gets filled and this is with the lens cap on.

Reverse Engineering / Re: (M)JPEG encoder
« on: September 18, 2012, 06:27:41 AM »
FA_GetJpegBuffForLV seems to be null in the 600d, going to start dumping VRAM and look for the magic jpeg numbers FF D8 FF. 5d3 has the same problem but with the 5d3 you still can make a movie with uncompress YUV 422 files with the right CF card, SD cards are not fast enough:(

Archived porting threads / Re: Canon 6D support?
« on: September 18, 2012, 05:39:18 AM »
6D model ID number 0x80000302

Camera-specific Development / Re: Canon 40D
« on: September 14, 2012, 02:46:30 AM »
In 2008 dataghost teased the world be getting video from his 40d. Now it looks like it might just happen for other 40d users. Congratulation on your hard work!!!

Pages: 1 [2] 3