Messages

BTW 960x408 @ 23.976 fps seems to be very stable, I just recorded almost 7GB(~11 000 frames) file.

I'm using Sandisk Extreme 45MB/s card.

But... how the 4Gb limit problem was solved here ?!?!? 7Gb file ?!? Are you sure ?!? 

which bin are you using? On my camera I am getting only broken DNG's, like the one you posted

I'm using the last nightly build, not the official one... and you ?

I was trying out the new magiclantern-v2.3.NEXT.2013May26 build with silent pics and didn't get any screwed up images (which always happened before). I took 500 pics and all of them were ok :-) The resolution was 1734x1156.

The screwed-up frames appears among the Others when shooting in silent pic BURST mode... try this feature, and you will notice that at least one burst every 5 will show a screwed-up DNG image inside... Tell me if it appears also to you (try more than 5 bursts...) Many thanks for your next tests !

On my EOS 600D it's only in the Magic Lantern menu. It's in the "Shoot" tab. The setting is labeled "Pic Quality".

Many thanks ! Unfortunately this menu item is not present in ML on 550D, full version (not the ripped-one for raw video).
Perhaps it's a feature useable only on 600D and other models, or it's simply not enabled on 550D... do some experienced developer can shed light on this ? Many thanks !!

I don't have adobe after effects. Is there another option?

If you have Windows, then -> RAWanizer ! --> http://www.magiclantern.fm/forum/index.php?topic=5557.0 
If you have other systems, I dunno 

canon main dial on video mode - 640x480x50fps video settings by canon menu - 1734x694 actual dng resolution - 24fps ml video override - 31 frames burst recorded - ml global draw off - canon record audio on or off no difference

if canon main dial is on M mode, only 19 frames are recorded

[1] Canon video settings are no-influent over the DNG RAW burst resolution: how we can set it in order to increase or decrease it so it can record more images and so for more time ?

[2] Once in a while (once every 2-3 bursts), a single screwed-up DNG is recorded inside the burst sequence, like this -> https://dl.dropboxusercontent.com/u/46130896/screwed_up.jpg    the borders of the subjects are barely visible.
How we can solve this ? Perhaps the other ports have already solved this... 

Full resolution frame example on 550D (1736 x 1156 pixels) (1 second fixed exposure, independent of the exposure time you set) -> https://dl.dropboxusercontent.com/u/46130896/sample.jpg

Max speed is about a frame every 2 seconds on 550D with a 30 MB/s 8Gb Sandisk SD card

To take silent dng, go to camera settings on ML menu and enable silent pics (ON), then put the rotating knob of the camera into M (manual), then push the liveview button (the red one) then keep half pressed the shoot button to start silent-shooting. Release it to stop the sequence.

All interested into porting DNG silent pics only on 550D, please converge here -> http://www.magiclantern.fm/forum/index.php?topic=5718.new#new     

[Current state-of-the-art]

In this thread we will concentrate our efforts to port DNG silent pics feature (normal and burst mode) to the 550D

Current state-of-the-art : Simple & burst mode works, but from time to time there is a screwed-up frame (pink noise where you can guess some subjects contours) inside a BURST sequence, at least one DNG wrong inside the burst every 30 or so burst, as a mean value

I can confirm also: no more playback problems with the latest "ettr enabled" (and Others features enabled inside) release from MK11174 ! I updated the "state-of-the-art" head post of this thread. Great, guys ! 

I get the best results with the following settings:

- "Pic Quality" set to "SRAW"

Maybe the "Pic Quality" trick doesn't work on the 550D? It should increase your "shoot_malloc total" if you set it to "SRAW" and then reboot your camera.

The Canon 600D had 74 Megabyte buffer for shoot_malloc. A1ex did something ... Now it's only 68 Megabyte - Without "Pic Quality" trick!
With it set to "SRAW" it's 96 and it was 104 once. If you want to know how much your 550D has, go to "Debug" menu and press "Q" on "Free Memory". As far as I know "shoot_malloc total" is what you're looking for.

Where is to set this "SRAW" parameter ? Canon or ML ? And where ? Many thanks !

But I think on the 550D you haven't reached the limit yet. On my EOS 600D I'm able to get these results:

- 1280 X 400 at 24 frames/s: Up to 4 GB file size limit
- 960 X 540 at 24 frame/s: Up to 4 GB file size limit
- 720 X 720 at 24 frame/s: Up to 4 GB file size limit

[With this SD-card: SanDisk Extreme 16 GB SDHC Class 10 UHS-1 | 45 MB/s]

Since the 550D and the 600D are nearly the same camera and both have a max. write speed of 21.3 Megabyte/s you should be able to get similar results.

The max performances are the ones you see here, confirmed by many 550D users. What parameters do you use, beside the ones you described, lilke: main dial position, Canon menu video mode, inherent ML menu settings, and so on... Perhaps 600D has more buffer memory ?

May I ask which OS you are using for compiling, and how you set up your tool chain (pre-built toolchain, VM, or DYI)? Cheers!

I advice you to use the VM: fast, easy, hassle-free, no other configurations needed !

So as far as I can think of, it shows the actual exposure values of the RAW, not of what the camera thinks it would be in a JPEG, right?

And what does the brownish-red and grey area in the left quarter of the histogramm mean?

Thanks,
Tobi

Yes, your first thinking is correct.

For the red area, I think it means: higly underexposed area, and the grey means: warning, this area is moderately underexposed. However i dunno for sure, so I wait for the programmer that implemented  this to confirm my toughts... anyone that knows this, is welcome to knock here ! Many thanks !

What I know for sure is that each vertical line correspond to a 1 Ev value, and this is from the sources comments, so it should be sure ! 

Bad news. As expected, the bottleneck is the SD controller inside 550D ! I tried with a Sandisk Extreme Pro Class 10, 16Gb, 95Mb/s : same results: max res without skipped frames is 960x408 at 24fps ! Sorry boys ! However a great achievement !

Bad news 2 : when playback the latest movie capture, my 550D shows a messed-up flickering screen then no more commands are accepted, you must switch off, but red led is on, and if you switch back on, camera is frozen with red led on, you must put out the battery and then reinsert it, then switch on again and all is ok. Do you experiment the same problem ? How to solve it ?

These are the modifications I have done: what is wrong or what is missing ? Many thanks to all that would help ! 

https://bitbucket.org/dlrpgmsvc/magic-lantern/commits/3c7ce12b6ec26a796be0030d70aa837783e91ee2

He probably meant the features. 

right ! thanks ! 

@mk11174 : can you share with me your latest modifications and procedures on how to enable raw video and disable modules, so I can help you to solve the memory problem ? Many thanks !

Then, you need to intercept the raw image buffer from Canon's state object (this is the task that develops the image). The state machine is just like 5D2 one.

SDS_FRONT3_STATE ? It seems it is this ! I tried to duplicate the 5D2 codes snippets, but nothing... the review histogram is still not raw, but normal... I used 52D as reference like you said
And where I have to put the raw photo EDMAC ? In which file ? Raw.c ? It is already there the 550d edmac for raw photo...

Between sarcastic comments of who don't know ever what programming is, and unpolited newcomers with ever worse comments about what Others MUST do freely and FAST for them... i think that thin air is flowing very well for nothing through their mouths 

I hope I'm not sounding too greedy, to wonder how/if you have progressed on the RAW video capabilities as yet? It's kinda ironic that the poll reveals sooo many users of the 550D, yet it seems to be the last to get code ported!

Unfortunately not, I have not progressed for raw video 
I'm "making my bones" on more simple things like this, just to get aquainted with the system. Then, if no one will port the raw video, I will pass to it... even if I hope someone will port it before waiting for me 

Yes, you are right: it's so ironic and sad your consideration about how many people have a 550D and it's Always the last to be ported... but perhaps all the users in the poll are simply users and not programmers... so ... I'm trying to be their "Robin Hood" coder ! I have surely more followers than for 5DMK3 and company ! This is for sure ! 

One question: why, if raw histogram enabled, the live view shows raw histo and then the quick review show the normal histo ? Do this is normal ? Do we must enable some option to have raw histo ALSO on the quick review ? Many thanks in advance for your replies !

Whoa ! A little step for a programmer... a giant leap for 550D Magic Lantern !

I managed to enable the RAW HISTOGRAM on 550D ! 

The pull request is yet sent and sitting, waiting to be merged in the next nightly build ! 

Check states in photo mode.

Do you mean the file "state-object.c" inside "src" directory ?

Can you tell me more precisely the source files and the lines where there are the addresses to find ? These hints are still so Smoky, at least for me... so I can be of the address-seekers squad !