Messages

Question: How is dual ISO working on the 60D and now other 4 channel readout models? Don't get me wrong, I'm THRILLED. I just can't find any clear description on the dual iso thread. I see people talking about magically finding more registers?

There is no end to my amazement with the turns magic lantern has taken in the last several months. I am SO SO SO happy I chose to get an EOS camera now.

Sincerely, Confused in LA

Hello!
I have the same problem on Canon 60D. Does anyone found solution?
I have tried all possible varieties, changes frame rates, NTSC,PAL, resolution, - results always the same.
Becouse of this problem i can't get together video and external recorded sound. That is realy bad!
If anyone have any ideas how to fix it, please share!!!
Thank You!

Regarding the 24 fps problem:

Hi guys I had the same problem with my 60D raw videos but I found the fix:

First: make sure you do have framerate override on and set to 23.98 or 24fps just to eliminate any in-camera issues.

Second: It took me a while to realize that the problem was with a default setting in after effects. Unless you tell it not to, AE will interpret all imported files as 30fps (which causes the speed up to 24fps material). To fix, right click on your footage in the project bin and choose: Interpret footage > main. Then input the correct framerate depending on what you sent your override at. VOILA

Here is a visual example that I found:
the setting:
http://i.stack.imgur.com/JehOz.png

the dialog window:
http://i.stack.imgur.com/z7Yy0.png

About a month ago Bioskop Inc. was saying that he A1ex was hoping that there might be another 128mb of buffer memory that could be allocated. I have been following along the entire thread but it seems like there has been no news on this front for a while.

Does anyone know if it looks likely that more buffer memory is going to be leveraged in the future? Every bit is precious in this case

Does it seem even remotely possible that this type of functionality could later be accessed for stills in APS-C lines that share a cut down version of the same sensor (if not the exact same sensor) as the 7D such as T2i and 60D?

Whaaaa? If they did it on the 550D it will be done on the 60D! 

Fingers crossed! This could be a game changer! If that be around 75 seconds at just under 1280x720p would that mean around 30sec at the higher 1600x900?

Wow! Thanks! 0.12 makes a .mov of the RAW footage along with the DNG's!

Be careful though: the prores file that Raw2Dng 0.12 makes is not fit for using as an actual source file ( in a lot of scenarios). It makes for a great "check file" to keep track of your footage but it does not fix any issues with hot/dead pixels and it bakes in a strange white balance etc.

I have found that I still need to do pre-processing on my files upon import to After Effects. The actual DNGs do not show the hot pixels either. Even the default "as shot" white balance on import to AE is way way better.

Just my two cents

I believe I found the answer: on Preferences > import there is a frame rate option that was defaulted to 30fps. I changed it to 24fps and the first DNG sequence I imported since then is being read by the system as 24fps so I think I'm set.

Thank you JuanIrache!!! I did not know about the interpret function! It works perfectly!!! Finally beautifully correctly timed footage. Thank you so much!

One more question: Do you know how to tell After Effects to default to interpreting a particular frame rate so I don't have to tell it the footage is 24p every time? Thanks again for your help!

Hello All I was wondering if you could help me with an issue I am having with Raw video DNGs in After Effects CS5.5. The short version is this:

No matter what I can think to do, After Effects sees and treats my 60D raw footage as native 30fps.

Details:

I shoot in 1600x900 resolution mode so I get 134 frame clips on my 60D w/ the ML raw video module. I used the force frame rate option to set the camera at exactly 24fps. These clips should be 5.58 seconds long both on the AE timeline and upon export. Raw2Dng sees the correct 24 frame rate when it is auto-detecting the raw clip settings upon conversion to DNG. For some reason when I drop my converted dng sequence folder onto my project it reads it as 30fps.



Even when i set the project, sequence and render queue to 24fps, the software still treats the files as native 30fps and therefore plays the 24fps material back at the higher speed creating an unnatural jerky (almost old movie looking) motion.

Further evidence is the fact that the clips in the timeline are only 4.12 sec long:



Finally, I can see the problem is with after effects because when I use the newer version of Raw2Dng that automatically creates a prores file upon conversion, that prores plays back at 24fps and has natural motion and the full 5+ second runtime. The problem with this automatic prores file is that it doesn't have any pre-color/WB/etc correction so it is only usefully for a check file.

How can i get AE to read the files correctly and treat them at 24fps and render/export/playback at the correct speed? Thank you in advance!

Jon

Question for everyone: Is there a particular nightly build you would recommend that allows for a more frames than the most current one (maybe an older versions gets higher frame rates at the higher resolutions but has has some features removed or is more optimized)? In other words if I want to get maximum length without dipping down to 720p or less should I use the newest one or is there a milestone build that I should stick with?  I want to shoot some footage of my baby this weekend and I'm just wondering if people have seen any gains from the 5/27 build I still have.

Thanks!

Here are my first tests:

all @ 24fps, 2:3,5, S2 photo mode, global draw ON (magic zoom, working while recording
Transcend 32gb SDHC Class 10

  960x408  -  200% to HD  -  continuous *
  960x540  -  200% to HD  -  3163 frames - 131,8s @ 24fps
1280x544  -  150% to HD  -  644 frames  -  26,8s @ 24fps
1600x680  -  120% to HD  -  225 frames  -  9,4s @ 24fps
1728x736  -  111% to HD  -  173 frames  -  7,2s @ 24fps

It's so nice to finally see the grain of my camara, and not some blocky compression artifacts!
I'm so happy with my Tokina 11-16 in this croppy days

Thanks so much to all the ML community!!! God just build a special heaven for you guys!!!

* (15,6mb/s, SD-card LED even stops lighting every few seconds, stopped at 4gb, didn't try exfat yet...)

wow 225 frames at 1600x900? are you getting more than 134 frames because of the build you are using i wonder? what nightly build are you using?

Hi guys, does anyone have any tips or thoughts for increasing the malloc to squeeze out more frames on the 60D at higher resolutions? Right now I can get 143 frames at 1600x900 if I put the picture recording mode on jpeg (not raw or raw+jpeg) per the tip from several days ago (I am using the 5/25 build btw). Does anyone think that ultimately there will be other ways to inch closer to using more of the memory for raw recording bursts in the future either by disabling unneeded features or some other creative methods? 143 frames (5.9 seconds at 23.98) is certainly an improvement over where we were just a few short days ago. I'm Just trying to stay hopeful and positive for a future break-through that may allow us to get to 8 or 10 seconds of recording time if not more.

I had to remove some features because 60D has problems with booting of full ML package with modules enabled. You should to download normal nightly build, silent picture is included.

What was removed? Anything that should hold us back from installing this newest version? I am very excited about the idea of the raw histogram as the current one definitely does not work.

Thanks

Looks like the frame rate is too fast?

absolutely! See this is the same thing I am seeing in my footage. Does anyone know what causes this issue? It's like the camera (when set to 23.976 is actually recording a slightly lower framerate like 22fps. That would create this slightly jerky movement when sped up to 23.976 or 24.

Additionally this would also explain why it seems like the default shutterspeed of approx 1/50 is still (strangely) creating a slightly strobing high shutter speed look. If the frame rate is actually being recorded at around 20 or 22 fps then approx 1/50 of a second is too fast to create normal (180 degree) shutter motion blur.

While I haven't done a good side by side comparison to demonstrate dynamic range I can say from my tests that everything seems to be dramatically improved on my clips from roll off, to range to color depth to sharpness. These files are just so organic and lovely compared to the dumbed down h264 rolling off the camera.

Has anyone had a situation where it seems that there is a subtle timeshift going on in their raw footage? When I shot several small tests (all at 23.976) the shots of my baby seem to reveal that the footage is actually ever so slightly sped up even though it was shot 23.976, detected as such by raw2dng, the project and export in AE were also all 23.976. I need to shoot more tests but I wonder if anyone had this effect? Here is the example on vimeo (most noticeable in the 2nd shot): http://vimeo.com/66968797

Changing picture quality in the canon menu from RAW to JPEG (L/M/S) will give you a bigger shoot_malloc buffer. 276MB instead of 180MB.

'

Thank you VROEM, I am now getting 134 frames at 1600x900 where before I was getting something closer to 86. THANK YOU!

@ jamesstringer: Strange. I was getting really bad aliasing at 1720x968 but i don't see almost any aliasing so far at 1600x900.

My results from tonight's test:

60D from 2011. Nightly Build. Transcend Class 10 card.

I am getting 1720x968p for 2.66 seconds. (occasionally some test files will not open in after effects (after raw2dng). Most have.
I am getting 1600x900p for 3.12 seconds. (Note: no real aliasing found on 1600x900p. I may use this mode more if tests prove this. Still WAAAY more resolution that the H264 1080p in camera file.

1720x968 is very close to 1080p quality but there is a lot of aliasing. 1600x900p seems to be more stable. I will shoot some home movie tests tomorrow.

HUGE HUGE improvement over in-camera quality. Hopefully they can find ways to keep improving. I'm off to bed. I'll shoot more tests tomorrow.

Oh my god....the quality difference between 1720 x 960p video and the in-camera 1080p H264 is jaw dropping!!! Yes right now I can only record around 2-3 seconds but hopefully in the future we can find a way to get more. I will experiment with other settings but OH MAN!!!!

AMAZING!!!

UPDATE:

I use a transcend 32 gb Class 10 card.

I got 1920x640 for 185 frames, 1280x640 @ 375 frames and those imported without a problem. Videos play fine and the 1280x640 looks pretty good scaled up to 1920x1080.

I do have problems with other resolutions. 
When I shoot at Resolution  : 1734 x 726 I can get 173 frames.  The problem comes after converting to the DNG using the osx version of RAW2DNG.  I can't import them in any of my Camera Raw programs (After Effects, Lightroom, Bridge) they all say "the file format module could not parse the file. (45 :: 35)"

Do I need to use the most updated version of raw2dng?  I have an older version of it from a few weeks ago.

1920x640 for 185 frames!!! (7.7 seconds) Great scott! Do you have any trouble opening these?

I will try raw burst first and raw rec 2nd. It sounds like we can get slightly higher quality out of raw burst but slightly shorter record times.

Thank you SO MUCH Marekk! I feared the 60D was forgotten!!! I will test this weekend!

Are these DNG bursts always at 24fps or 23.98fps?

Thank you Bioskop! I installed the standard ML 2.3 last night. Tonight I will overwrite with the nightly build files and give it a try this weekend. Thank you for the link!

[1080p or M photo mode:]

No, sorry. I was only getting those resolutions with black bars (1888x1882 is the original frame size before they cropped it), which Marekk enabled in an autoexec.bin to see what my camera was doing - other 60D users are getting less frames but they are slightly larger @ 1734x1156.

I'm getting the following:

1080p or M photo mode:
1730x1152 @ 69 frames
2516x1076 @ 52 frames (in x5 crop zoom mode)

720p
1730x690 @ 112 frames (NB. the image is squashed so you just change 690 to 1152)
2516x1076 @ 52 frames

Not sure if the 720p frames are as good quality though, but much better than H264 - there is some noise/grain to image.

A good tip is to turn off RAW pic selection in photo mode (Canon Menu) & just set it to jpeg only (size doesn't seem to matter) - you get more frames this way.

Let us know if you get the same frames as me, since your camera is the same year.

Regardless: you are getting 2.9 seconds at almost HD, 2 seconds at 2.5k and 4.6 seconds at something close to 720p. That's amazing!

Just think if we can get closer to 5+ seconds at close to 1080p by the time we are done tweaking and testing? That would be a huge win for people like me that want to at least be able to grab short but high quality clips on vacation or for family movies. I cannot afford a 5D mk III under any circumstances so progress on the 60D is very exciting!

If you can point me to the appropriate download link for the best build to use I would be happy to try it out on my camera and let you know how my frame rate compares to you.