550D & 500D porting 14bit RAW DNG silent pics

Started by wolf, May 16, 2013, 12:22:47 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

mk11174

Quote from: Greg on May 21, 2013, 01:07:12 PM
You need to enable edmac.
https://bitbucket.org/Gr3g01/ml-500d-raw-dng3/commits/66619cd642ad311392882b5f3aaadc48a421c048

Turn on modules in the makefile.user

Copy raw_rec.mo to ML / modules / raw_rec.mo
Copy platform/550D/magiclantern.sym to ML / modules / magic.sym

960x480 24FPS works on 500D
Guess not fully ready for 550, when I enable that and the module all compiles fine but if start in movie mode it just keeps resetting cam then lcd goes blank and card light stays on.

If I try in M mode and go into ML before I turn on live view I can goto load modules now and it says at bottom.
tcc: error: undefined symbol raw_set_geometry
tcc: error: undefined symbol __aeabi_idivmod


I just tried same thing with 500D, I have both cams of coarse, I get same tcc errors except I just noticed when the error appears if I press the trash can a console of lots more tcc errors show and just like the 550D says failed to link module????

Fixed the TCC: Error, was just gawk needing to be installed. Raw_Rec seems to work on 500D, and now can enable module on 550D but only by going to M mode without turning on live view, if you try to start cam in Movie mode it starts and blacks out then red light comes on.
500D/T1i  550D/T2i  600D/T3i  700D/T5i

Greg

960x540 (20MB/s) is not enough to use it.
Even when scaled lanczos to 1920 does not look good.

We have to find a way to reduce the file size. Or buy new camera.
The 650D should work 1280x720 24FPS

internetjoke


Greg

Quote from: internetjoke on May 21, 2013, 06:45:26 PM
is it capable of 960 x 480 like the 600d?

500D can only 20FPS in full HD, this is a limitation.
So is 960x540 FPS raw.

internetjoke

can the 550d do 24fps at any resolution raw? what is the maximum resolution for 24fps raw?

Thanks

Greg

I do not know, I do not have a 550D.
It should be the same as the 600D.

CFP

Quote from: internetjoke on May 21, 2013, 07:36:04 PM
can the 550d do 24fps at any resolution raw? what is the maximum resolution for 24fps raw?
Quote from: Greg on May 21, 2013, 01:07:12 PM
960x480 24FPS works on 500D
Since 960 X 480 at 24 fps works on 500D and 600D I'm sure that 550D will handle it too :D

On my 600D I can shoot continuous at these resolutions:

- 720 X 720 = 0.52 Megapixel (1 : 1 aspect ratio)
- 960 X 540 = 0.52 Megapixel (16 : 9 aspect ratio)
- 1280 X 400 = 0.51 Megapixel (16 : 5 aspect ratio)

Higher resolutions will stop after a few seconds. I guess on the 500D and 550D you'll get very similar results.

Upscaling these resolutions to a width of 1920 will give you an image that looks fairly comparable to 1920 X 1080 H.264 in terms of detail and sharpness, but it'll have way more dynamic range and better colors then the default videos. I did a few comparisons and I have the impression that there's still a bit more sharpness in the 1920 X 1080 H.264 videos. But that was under bad lighting conditions ...

For those who want to do some comparisons on their own: Keep in mind that you have to change the focal length to get comparable results! Because the crop factor increases with these resolutions above. They are only crops of the sensor. Here are the crop factors you'll get with the raw resolutions:

Width | Cropfactor | Multiple of H.264 crop

1734 = 1.60 | 1
1280 = 2.17 | 1.36
960 = 2.89 | 1.81
720 = 3.85 | 2.41

So if you shoot a video in 1920 X 1080 H.264 at 55mm and you want to compare it with a 960 X 540 raw video you have to change the focal length to 30mm (55 / 1.81 = 30). At least if my math is correct  ;D

And btw. I wouldn't upgrade to a 650D if I would want more frames. The old but gold 50D takes CF cards and might be able to record 1592 X 682 (21 : 9) or maybe even 1592 X 895 (16 : 9)! That wouldn't even affect the crop factor since 1592 is the full width of the LiveView image :D

Andy600

@CFP - I'll tell you tomorrow re: 50d when mine arrives ;D It should (on paper) be an improvement on the 600d but it's an older sensor etc so I don't know yet. Hopefully I'll be able to post some comparisons if the card that's coming with it is fast enough.
Colorist working with Davinci Resolve, Baselight, Nuke, After Effects & Premier Pro. Occasional Sunday afternoon DOP. Developer of Cinelog-C Colorspace Management and LUTs - www.cinelogdcp.com

CFP

Quote from: Andy600 on May 21, 2013, 09:37:57 PM
@CFP - I'll tell you tomorrow re: 50d when mine arrives ;D
Great! Thanks a lot, I'm really looking forward to your results.

I guess the 50D Magic Lantern H.264 video will be a step back from the 600D Canon H.264 since the 18 MP APS-C cameras have a width of 1734 and the 50D has only 1592 ... So it needs more upscaling to become 1920. No issue with raws using something powerfull like Photoshop but inside the camera with its slooow DiG!C 4 it might look worse :(

As far as I know the older 15 MP sensor inside the 50D is better then the newer 18 MP sensor inside the 600D & 60D in terms of noise and dynamic range but worse in terms of detail ... Guess you'll see if that's right tomorrow  :)

Andy600

Yes, H.264 will likely not be as good as the 600d but if it can do fairly long takes without any cropping in raw (I'm only talking 30secs or so) there's no need for H.264 for me personally. The Digic 4 processor is the same as in the 600d no?
Colorist working with Davinci Resolve, Baselight, Nuke, After Effects & Premier Pro. Occasional Sunday afternoon DOP. Developer of Cinelog-C Colorspace Management and LUTs - www.cinelogdcp.com

ashtrai

Quote from: CFP on May 21, 2013, 09:31:11 PM

For those who want to do some comparisons on their own: Keep in mind that you have to change the focal length to get comparable results! Because the crop factor increases with these resolutions above. They are only crops of the sensor. Here are the crop factors you'll get with the raw resolutions:

Width | Cropfactor | Multiple of H.264 crop

1734 = 1.60 | 1
1280 = 2.17 | 1.36
960 = 2.89 | 1.81
720 = 3.85 | 2.41

So if you shoot a video in 1920 X 1080 H.264 at 55mm and you want to compare it with a 960 X 540 raw video you have to change the focal length to 30mm (55 / 1.81 = 30). At least if my math is correct  ;D


Is this for recording raw in 1080p mode? Does the cropfactor change when you use the 480p videomode to record raw?

CFP

Quote from: ashtrai on May 21, 2013, 10:17:53 PM
Is this for recording raw in 1080p mode? Does the cropfactor change when you use the 480p videomode to record raw?
No. In 1080p, 720p and 480p mode the cropfactor should always be the same like I posted.
Only the 5X crop and the digital 3X zoom (600D only) will increase the crop factor even more.

But in 720p you have less horizontal resolution then in 1080p and 480p mode.

mk11174

As of now the 550D can't do any raw video, once the build is set up with modules turned on, the camera will crash and restart once movie mode is on or live view is on. But you can turn on the module in Manual mode at least to at least see the module can be turned on, but once you turn on the lcd the camera reboots and then crashes. Anyone know what still needs to be configured? Are there things that still need to be coded for it to work or is it just a bug with the 550D?

Silent Picture Raw Burst seems to work nice though.
500D/T1i  550D/T2i  600D/T3i  700D/T5i

dlrpgmsvc

Quote from: mk11174 on May 21, 2013, 11:04:15 PM
Silent Picture Raw Burst seems to work nice though.

Unfortunately not ! Once in a while, there is a screwed up frame inside the burst ! See my previous report in this thread, and so I'm seeking someone that can help to iron out this problem, like the one you pointed out about the raw video rec ! Lets hope together !  :-\
If you think it's impossible, you have lost beforehand


dlrpgmsvc

Quote from: a1ex on May 21, 2013, 11:17:35 PM
This might be related: https://bitbucket.org/hudson/magic-lantern/commits/90309b750838

Good ! So, when your commits will be merged (or do it's yet merged ?) the problem of the screwed up frames in burst should disappear ? Or do we must integrate your commits in another module ?

Or are you referring to the LiveView with raw_video problem ? Or do your commits are related to both problems ?

Many thanks a1ex !!!  :)
If you think it's impossible, you have lost beforehand

mk11174

Quote from: a1ex on May 21, 2013, 11:17:35 PM
This might be related: https://bitbucket.org/hudson/magic-lantern/commits/90309b750838
No, doesn't seem to help, I was not seeing an issue with the silent picture raw burst because I was in 1920x1080 mode, when switching to 1280x720 or 640x480 I see ever few frames at the start of the capture during burst, those get that weird color noise to them. 1920x1080 seems just fine so far.

Also I noticed I only get 28 frames in 1280x720 and 640x480 and 17 frames in 1920x1080, what is weird, with this bin file, http://www.magiclantern.fm/forum/index.php?topic=5446.msg37751#msg37751  I got 31 frames and 19 frames???
500D/T1i  550D/T2i  600D/T3i  700D/T5i

dlrpgmsvc

Quote from: mk11174 on May 22, 2013, 12:17:44 AM
Also I noticed I only get 28 frames in 1280x720 and 640x480 and 17 frames in 1920x1080, what is weird, with this bin file, http://www.magiclantern.fm/forum/index.php?topic=5446.msg37751#msg37751  I got 31 frames and 19 frames???

I think A1ex made a good job, because now I can see no more problems at 640x480 in burst pics, and the bin file you refer to is mine, and was compiled before the A1ex modifications. So these modifications avoids the screwed up pics but you lose 2 or 3 frames, and this is probably due to the memory alignments and timings that prevent the pics malformations !

Please, mk11174, can you confirm this by compiling the very last sources with the silent pics raw dng burst modifications and then make you also tests with 550d ? Many thanks !

Also, I made a pull request about 550d burst pics, so we will be aligned also with the bins and the tests ! I hope it will be accepted fast !  ;)
If you think it's impossible, you have lost beforehand

mk11174

Quote from: dlrpgmsvc on May 22, 2013, 02:11:20 AM
Please, mk11174, can you confirm this by compiling the very last sources with the silent pics raw dng burst modifications and then make you also tests with 550d ? Many thanks !

No, I still get messed up frames occasional in both 1920x1080 and 640x480, but for sure happens more in 640x480, but not all the time either, sometimes it actually seems like the bug is gone but then it shows up again.

I do notice, it is always the 3rd and 4th frame that is messed up from each capture, the 3rd frame is only like a tiny section at bottom of image and 4th frame is full of colored noise, like a effect added to the image.
500D/T1i  550D/T2i  600D/T3i  700D/T5i

mk11174

Quote from: dlrpgmsvc on May 22, 2013, 02:11:20 AM
Also, I made a pull request about 550d burst pics, so we will be aligned also with the bins and the tests ! I hope it will be accepted fast !  ;)
He already has Silent Picture Raw Burst added a few builds ago for all cameras now. If you compile the latest build it will be in the menu. https://bitbucket.org/hudson/magic-lantern/commits/929adbf32a8ae0e5e65dcbe817b22b2a39355e96
500D/T1i  550D/T2i  600D/T3i  700D/T5i

dlrpgmsvc

Quote from: mk11174 on May 22, 2013, 06:22:03 AM
He already has Silent Picture Raw Burst added a few builds ago for all cameras now. If you compile the latest build it will be in the menu. https://bitbucket.org/hudson/magic-lantern/commits/929adbf32a8ae0e5e65dcbe817b22b2a39355e96

You are right ! Every day we learn something... one sees that the modifications are not there in the Platform-specific and thinks there aren't... ok.

They can however accept this pull just to sync the local 550D Platform files to the "all" section, for more clarity for who, like me, will dig only into the local Platform files to make modifications  :'(
If you think it's impossible, you have lost beforehand

Fauxto

I was thinking, isn't there a plugin that interpolates bad frames on a clip?

You know, if you just got like 6 pink frames in a ten second clip maybe there's a plugin in which you can mark those frames and the software then interpolates a brand new image from the adjacent ones.

If there's not much movement the result will get unnoticed by the accasional viewer...

mk11174

I would like to get Raw_Rec going like it is on the 500D, I know it is not the best cam for it, but just cool to have the features just for fun. It bugs me that the older 500D can do it but the 500D can't so far. I just wish I could figure out what else the port needs to get it going, I don't know if its something in the code that still needs to be added or if it is something we can debug to figure out. I just don't understand why live view won't load when turning on TCC and MODULES. Funny how I can load the Raw module if I don't turn live view on, so I am guessing it can't be the module. Hoping someone can guide us in the right direction so we can try debugging if possible.
500D/T1i  550D/T2i  600D/T3i  700D/T5i

Atrakt


Edmac work on 550D but I'm unable to compile the bin with TCC and modules, I have several error with TCC but I don't understand why.. I have Gawk installed.. So, wait and see for the moment ;)
For now, I'm going to play with the MKII and the raw feature :p

mk11174

Quote from: Atrakt on May 22, 2013, 10:59:39 AM
Edmac work on 550D but I'm unable to compile the bin with TCC and modules, I have several error with TCC but I don't understand why.. I have Gawk installed.. So, wait and see for the moment ;)
For now, I'm going to play with the MKII and the raw feature :p
I can compile when I turn on the TCC and MODULE, I am using the updated tip and setup my makefile and internal file for EDMAC, it all compiles with no errors, just warnings but same warnings I get on 500D compile and 500D raw_rec worked fine. Is there something I need to adjust somewhere else to try it since mine seems to be compiling?
500D/T1i  550D/T2i  600D/T3i  700D/T5i