Messages

Interesting.  I have seen this page before but under branches I do not see the 650D and never came back to look.  So  1) are you using the 60D for example and 2) where on this page is the modified raw_rec.

Not sure if understand you correctly.
1) 60D? No, i'm using this raw_rec for my 650D and in some cases for 550D.

2) This page is code source. You can clone it to your machine and compile for yourself just like you normally do with other sources. If you don't familiar with compiling, you can start from here:
http://www.magiclantern.fm/forum/index.php?topic=6783.0

Well even though I have no idea how would i do that, at least that gives a good explanation! thanks mate!

This version has some interesting features like various interface choices.
I also modified some things regarding resolution choices. Now I just choose vertical and horizontal resolutions separately (multiples of 16) instead of horizontal and aspect ratio.

I will perform some testing, and if the module will work stable, i then can share it with you.
(I just don't want to burn up any cameras other then mine)

Rewind the maximum i get with small hacks enabled is 38.1Mb/s. And I have the 32 GB SanDisk Extreme Pro® SDHC™ UHS-I Memory Card 95Mb/s.

How do you get 38.5?

Even 38.6 now at resolutions higher than 1536 (e.g. 18 secs of 1600x672 just like 6D )

I'm using modified raw_rec from pravdomil's source.
https://bitbucket.org/pravdomil/magic-lantern-hack/commits/all

Can you share what sd card you are using.  I think I might need to buy a new one

Currently, I'm using the Sandisk Extreme Pro 95MB/s like in this post: http://www.magiclantern.fm/forum/index.php?topic=7473.msg73048#msg73048

There's nothing special about this card (it's old and i suppose discontinued), you can use any of them, which bencmarks around 40MB/s
But if you'll get Sandisks 45MB/s, be careful to tell the difference between these two: http://www.magiclantern.fm/forum/index.php?topic=7473.msg72697#msg72697
The one on the right is slow. You should get one with red sticker, not gold.

Ok, another good news.
Thanks to mk11174, we found a timer address for 650D (0xFF527E38), and small hacks now fully working.

This gives us another tiny speed increase: 38.5 Mb/s vs previous 37.7
For example, now you can record 1504x640 (2.35:1) continiously.

When I'm using my favorite resolution 1536x640 now recording time before skipping is about 1.5 minutes, previously it was around 42-44 secs.

mk11174 just found it for 650D:
0xFF527E38

Guys would you mind to help me a bit?

Just turn the 700D on in video mode with raw_rec enabled, go to ML menu — Debug — Dump ROM and RAM, push it, wait until dumping is done, then go to your SD card — ML — LOGS, and just sed me the ROM1.BIN

Just a couple of minutes, PM me please. I need this for 650D port.

_______________________________________________________
UPD. Nevermind, problem solved (thanks to mk11174). Thank you.

Guys with 700D, I need a bit of help from you.

In order to small hacks works properly on 650D, we should find the timer address. We tried to do this by compare with 550d and 600d, but no luck. 700D is may be somewhat closer to 650D, so we need a ROM1.BIN from your camera.

Just turn it on in video mode with raw_rec enabled, go to ML menu — Debug — Dump ROM and RAM, push it, wait until dumping is done, then go to your SD card — ML — LOGS, and just sed me the ROM1.BIN

Just a couple of minutes, PM me please.

_______________________________________________________
UPD. Nevermind, problem solved (thanks to mk11174). Thank you.

Has anyone been successful with Dual ISO on the 550d yet?

We are shooting dual ISO on 550D's for about a couple of months.
http://www.magiclantern.fm/forum/index.php?topic=5582.msg69853#msg69853

Guys, I don't see the problem. You can always use older raw2dng, which saves camera name.

UPD. My bad. Some time ago I just hardcoded the camera name.

Found it for 550D cam_550d ? 0xFF2FE5E4

That's great. Would you mind to describe the process of this finding a little bit in order we can get this address for 650D?

UPD. thanks to mk11174, now we have the right one for 650D: 0xFF527E38

Found for 550D cam_550d ? 0xFF2FE5E4

mk11174, how did you do that? Give me please some clues, how to find that address for 650D?

what does AHD mean? i couldnt find anywhere

Adaptive Homogeneity-Directed interpolation.

When i open the dngs in ae, i have a problem... in acr, there is no profile aviable, it s only embedded showing up...how can i change that?

Probably you are using an obsolete version of raw2dng which saves 'wrong' exif data.
You can tell it by the name of the camera in the title bar:


If it says 'Canikon' instead of your actual camera, than this is the case.
You can use EXIFtool to write the proper camera information to existing dngs.

You can see the interpreted bitdepth here:


millions would be 8bpc
trillions, 16bpc
floating point, 32bpc

I don't know any plugin for AE to calculate the real bitdepth, but empiric experience shows, imported dngs are 16 bit (14 bit nested in 16 bit) indeed. You can compare things like banding in extreme grading in 8 bit and 16 bit files in say Photoshop to assure, as I did. But you just can believe that "trillions of color" — it means real 16 bit.

any progress with the pink dots in raw video?

The dots are still there )
We are still using PDR (which works for 650D quite fine), chroma smoothing and other workarounds.

These are the lines in raw_rec related to small hacks. In order to work them properly on 550D and 650D, we should know the timer addresses for those cameras:

Code Select Expand

/* change dialog refresh timer from 50ms to 8192ms */
        uint32_t dialog_refresh_timer_addr = /* in StartDialogRefreshTimer */
            cam_50d ? 0xffa84e00 :
            cam_5d2 ? 0xffaac640 :
            cam_5d3 ? 0xff4acda4 :
            cam_7d  ? 0xFF345788 :
            cam_700d ? 0xFF52B53C :
            /* ... */

Other way we get an error like
hackerror at 0
expected e3a00032, got 0

My question is, anybody knows these timer addresses yet for 550D and 650D?
Or may be devs can give us some clues to how to figure them out?

I think this is the section of raw_rec.c, where we should add the addresses for orther cameras:

Code Select Expand

/* change dialog refresh timer from 50ms to 8192ms */
        uint32_t dialog_refresh_timer_addr = /* in StartDialogRefreshTimer */
            cam_50d ? 0xffa84e00 :
            cam_5d2 ? 0xffaac640 :
            cam_5d3 ? 0xff4acda4 :
            cam_7d  ? 0xFF345788 :
            cam_700d ? 0xFF52B53C :
            /* ... */

But how we should figure these addresses out for 550D, 650D and others?

May I ask you please, what are these guys in DATA folder of ML, and what are they intended for?

APSC8P.LUT
APSC8R.LUT
FF8P.LUT
FF8R.LUT

The same behaviour with 650D and 550D (original raw_rec from latest nightlies)
What are the timer addresses for these cameras and where should we add them?

Has there been anything new on this issue of PDR?

What issue?

Well, actually CF = DIAG35mm / DIAGsensor.
But when you are shooting at sinemascope ratios (like 2.4:1) it is feels like Width is the only really matters.
It's lke... when you make decisions of framing and lens choices while drawing the sketchboards, the width of the frame is the landmark or... reference.
So it will be fine enough to see 35mm eq. related to W35/Wactual ratio.

Or may be just give user the ability to fine-tune this multiply factor?
Then, for my example, I just put in the 1.8 and be happy.

It might be useful, if the 35mm equivalent crop factor display takes the actual crop factor of raw_rec crop box.
Let's say, I usually shoot at 1536xNNN on 650D, so my actual crop will be 1728/1536*1.6 = 1.8

In this case, if my lens at 28mm, the actual 35mm eq. will be 50, not 45.

So, I was able to "record in RAW", but only at 960x540 at 14 FPS...but it stopped automatically after 10 seconds.   Booooo.....

My question is this:  What settings must I use for the RAW recording module to get 960x540, so I can record continuously at 24FFPS without stopping?

First, you should perform the card benchmark.
Go to ML menu — Debug — Benchmarks — Card R/W benchmark (5 min)

For me it's obvious, your card is too slow.

You shouldn't be able to boot the camera if you have the bootflag on the card set and ML is not on the card.  Check that you correctly set the bootflag.

If you have bootflag set, but SD card isn't bootable, camera boots fine.