550D/T2i raw video recording port official thread

[telecastDaveRI]

Here are 2 builds with the new Filemanager there working on. I added the Stub for SeekFile to get it going.

This is the build with Tragic-Lanterns more res option Raw Rec module:
http://www.mediafire.com/download/96zgrdjaubamjuh/ML_Fileman_Raw_Tragic.zip

This is the Magic-Lantern build with the regular Raw Rec module:
http://www.mediafire.com/download/411wvydehbwfxcw/ML_Fileman_Raw_Unified.zip

I'm still getting better results with the "fix2" build. Attempted similar/same resolutions and with the "fix2" build - it will indicate to me that I have continuous recording, and although I didn't write down the results, I attempted to keep the resolution around 1280 at an aspect ratio of 3:1 and it only worked with that build. I cannot recreate that success with these. Unsure if this helps, but I thought I'd mention it.

[mk11174]

I'm still getting better results with the "fix2" build. Attempted similar/same resolutions and with the "fix2" build - it will indicate to me that I have continuous recording, and although I didn't write down the results, I attempted to keep the resolution around 1280 at an aspect ratio of 3:1 and it only worked with that build. I cannot recreate that success with these. Unsure if this helps, but I thought I'd mention it.

Not much different other then the addition of file manger as far as I know, so not sure why there would be a differ in record ability, but I guess it is possible more stuff is not always better.

[telecastDaveRI]

yea, I'm unsure what it is. Possible side effect? I just found it odd that when I went to replicate what I did on the other build, I couldn't with these.

But again, just throwing it out there as informational.

[mk11174]

yea, I'm unsure what it is. Possible side effect? I just found it odd that when I went to replicate what I did on the other build, I couldn't with these.

But again, just throwing it out there as informational.

I am only able to use that 1280x 3:1 aspect at 21fps stable with no skips with this build, I will try Fix2 just to see what happens, you have me curious. 

Update: well still no 24fps but I am able to get 22fps with those settings with Fix2 so must be a bit better, but the only addition is Fileman so I can try this new build without fileman and see what happens.

Update2: No, fileman does not make a differ, results are totally random at 22fps for me sometimes it never stops till I stop it, sometimes I only get 66frames.

21fps works perfect either way at that res.

Tragic lantern version has a cool greyscale preview option while recording raw, it shows exactly what your recording, much nicer to see what is being cropped.

[telecastDaveRI]

sounds awesome.

Yeah, I apologize. I wasn't at 24fps either. I forgot to include that information. I only noticed it because I literally tried to use the same settings and that is when I thought "wait a sec....".   

[sonic]

I added the Stub for SeekFile to get it going.

Is this available on bitbucket?

[mk11174]

Is this available on bitbucket?

No, not yet, I dont know how to add to that, I just added it to build it myself for now till someone that knows how adds it.

If you try to build now from bitbucket and use Raw it will not work because of the Seek address not there yet.

line: 85
NSTUB( 0xFF1C691C, FIO_SeekFile)

If you know how to get it on there or pull it or whatever its called, lol

[telecastDaveRI]

Update2: No, fileman does not make a differ, results are totally random at 22fps for me sometimes it never stops till I stop it, sometimes I only get 66frames.

Yes, I just noticed that now, after testing it again, I'm getting different results also. Last night I had some 30 second footage at 1280 at 3:1 at 18fps (override) - and the files on my computer that I just checked to verify - and now I cannot even duplicate that, even with the fix2 build.

Very interesting.

[sonic]

If you know how to get it on there or pull it or whatever its called, lol

It's actually quite simple and fun (as long as the VCS doesn't start fighting with you ):

• Fork
• hg clone https://bitbucket.org/mk11174/magic-lantern


• Make your changes
• hg commit path/file.c
• Enter commit message
• hg push
• Press Pull request on bitbucket website
• Voilà

[mk11174]

It's actually quite simple and fun (as long as the VCS doesn't start fighting with you ):

• Fork
• hg clone https://bitbucket.org/mk11174/magic-lantern


• Make your changes
• hg commit path/file.c
• Enter commit message
• hg push
• Press Pull request on bitbucket website
• Voilà

Cool, thanks for the info, maybe I will try it next time I need to add something. Thanks!

Now we need to try to get more Buffer Memory like the other cams, even the 500D has 95, I just tried Raw on my 500D and I get high res then on 550D with no skip.

By the way 1280x400x24fps just fine on 500D

[sonic]

Now we need to try to get more Buffer Memory like the other cams, even the 500D has 95, I just tried Raw on my 500D and I get high res then on 550D with no skip.

I already tried to find sourcecode for the sRAW experiments from the past, but couldn't find anything yet. I'm also afraid of the permanent Err70 this seems to provoke.

[mk11174]

Ah really, permanant error 70, interesting, that is scary

[sonic]

Ah really, permanant error 70, interesting, that is scary

I just thought "what the heck" and tried

Code Select Expand

        if (should_run_polling_action(20000, &aux))
        {
set_pic_quality(PICQ_SRAW);
            guess_mem_running = 1;
            guess_free_mem();
set_pic_quality(PICQ_RAW);
        }
in debug.c
but still only 75 MB.

[mk11174]

I just thought "what the heck" and tried

Code Select Expand

        if (should_run_polling_action(20000, &aux))
        {
set_pic_quality(PICQ_SRAW);
            guess_mem_running = 1;
            guess_free_mem();
set_pic_quality(PICQ_RAW);
        }
in debug.c
but still only 75 MB.

I already enabled it a couple weeks ago but never knew about the err70 thing, lol, it seems when I did load it, I just got a red rectangle across the screen with some address in it, but like you, mem was still 68 back when I tried it.

[Greg]

NSTUB( 0xFF1C691C, FIO_SeekFile)

I need this to 500D how to find it?
Here it is, but I do not know how to do it - https://bitbucket.org/hudson/magic-lantern/commits/01e1e1c267d3396d6ddf6738a815754e28b9367d

[mk11174]

I need this to 500D how to find it?
Here it is, but I do not know how to do it - https://bitbucket.org/hudson/magic-lantern/commits/01e1e1c267d3396d6ddf6738a815754e28b9367d

NSTUB( 0xFF1968B4, FIO_SeekFile) is for 500D

[Greg]

NSTUB( 0xFF1968B4, FIO_SeekFile) is for 500D

ok, thank you 

[1%]

0 props need to be blocked out or it won't change, just give you the red square. Then you need to change mode to apply it. Hard writing the 0 props seems to change it right away but then you have these err 70 problems. EOSM just shut down when put into sraw.

[sonic]

0 props need to be blocked out or it won't change, just give you the red square. Then you need to change mode to apply it.

I commented out

Code Select Expand


        if (should_run_polling_action(20000, &aux))
        {
set_pic_quality(PICQ_SRAW);
            guess_mem_running = 1;
            guess_free_mem();
//set_pic_quality(PICQ_RAW);
        }

void set_pic_quality(int q)
{
    if (q == -1) return;
    prop_request_change(PROP_PIC_QUALITY, &q, 4);
//    prop_request_change(PROP_PIC_QUALITY2, &q, 4);
//    prop_request_change(PROP_PIC_QUALITY3, &q, 4);
}


and switched between Movie/Night Portrait and P/LV, but always 75 MB.

[dlrpgmsvc]

No, not yet, I dont know how to add to that, I just added it to build it myself for now till someone that knows how adds it.

If you try to build now from bitbucket and use Raw it will not work because of the Seek address not there yet.

line: 85
NSTUB( 0xFF1C691C, FIO_SeekFile)

If you know how to get it on there or pull it or whatever its called, lol

I dunno who made this, but your modification is already merged in the bitbucket unified ! Great !

I have, however, some questions, just to clarify things better, to me and to others that may come to help :

[1] Do there are Others stubs to search for (not for this specific memory problem, but for other purposes... just to know) ?

[2] Do someone knows what are the source files (and where are they located) that are involved into enabling sRAW feature and at what lines, inside them ?

[mk11174]

I dunno who made this, but your modification is already merged in the bitbucket unified ! Great !

Sonic took care of it 

[GregoryOfManhattan]

@Sonic, did you need a dump to get the correct FIO_SeekFile?
we need to get this for the 50D also.

what was the symptom of an incorrect RESTARTSTART - i see a1ex commit to reboot-all.c for 550D

[mk11174]

@Sonic, did you need a dump to get the correct FIO_SeekFile?
we need to get this for the 50D also.

try for 50D NSTUB( 0xff9829b0, FIO_SeekFile)

[pavelpp]

So what are you saying guys - raw is now enabled in unified builds for 550d?

[mk11174]

So what are you saying guys - raw is now enabled in unified builds for 550d?

No, you have to build yourself to get the M menu to load modules, if you cant build just use my latest build, it is up to date with bitbuckit.

But everything is added to 550D port now to make raw load and work, just need to build yourself to enable modules.

Only thing we need to catch up with the other cams is a bit more shoot_malloc memory, 1% got us from 68mb to 75mb, now we just need to get to 95mb like the 500D then it will help us get a bit higher res at 24p. The 500D is getting 1280x400x24fps