Messages

I just don't know why you're arguing with me over this... 

There is a reason things work they way they do.  I'm not trying to annoy the developer and I think what he has been able to get out this camera to do is insane!

I'm not special at all, but I'm willing to offer my experience to the developers to help them shape this into something even more awesome.

Honestly, I could be like every other professional and say "psshhh... shoot with the F55", "Yea, but it'll make your camera explode"...

I even went as far as to test this on a paid, 5 day job... had it failed, I could have been sued.  But it worked perfectly, and I've been singing it's praises ever since!

It's great!  Amazing!  I can't believe this quality is THIS accessible for SO CHEAP!  But... the display covers actors faces, and sometimes the images look like vomit before you CC then in Resolve.  I think those issues need to be solved before spanning the data across 2 cards.

Why is that such a threat to you?

You went on a job with no backup? sheesh.

Hi Devs,
Was wondering about the frame flush and GOP parameters, under video hacks. Do they actually work? or do I need the build from the Halloween bitrate monster thread? ( http://www.magiclantern.fm/forum/index.php?topic=3404.100 ) I've been doing experiments and have read about the ISO-bitrate relationship and all that. I've read the threads and all but am wondering if it actually does anything. I am using VideoSpec to see the details but according to it the GOP is no different even when I change it. Further, I seem to get higher bitrate per ISO with it turned of all together.

Or is it only with VBR i get to see the diff?

And another thing, are nanomod's nightly builds for the 7D? I see in the change log pelican's update to 7d stubs.

So to answer my own question. The Autoload version of the 7d alpha2 doesn't do the GOP or Frame Dump. I understand the push for RAW but I honestly think the ability to shoot all I frame is impressive as well, more impressive even than the 41 frame raw burst. That being said, I think that the 7D once unlocked will be quite a beast. Of particular interest here is the N=1 followed by no M meaning that I am shooting a 1 Frame GOP which is by definition an I Frame. Beautiful boys, beautiful.

And before anyone starts asking I am using the non Autoload version here. And of interest is that I have not removed the boot flag from my 7D so I can still load the autoload version, just thought you all would like to know.


Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 324 MiB
Duration : 46s 129ms
Overall bit rate : 58.9 Mbps
Encoded date : UTC 2013-08-07 03:07:53
Tagged date : UTC 2013-08-07 03:07:53

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : N=1
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 46s 129ms
Bit rate : 58.9 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Original height : 1 088 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.184
Stream size : 324 MiB (100%)
Language : English
Encoded date : UTC 2013-08-07 03:07:53
Tagged date : UTC 2013-08-07 03:07:53
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.601

Hi Devs,
Was wondering about the frame flush and GOP parameters, under video hacks. Do they actually work? or do I need the build from the Halloween bitrate monster thread? ( http://www.magiclantern.fm/forum/index.php?topic=3404.100 ) I've been doing experiments and have read about the ISO-bitrate relationship and all that. I've read the threads and all but am wondering if it actually does anything. I am using VideoSpec to see the details but according to it the GOP is no different even when I change it. Further, I seem to get higher bitrate per ISO with it turned of all together.

Or is it only with VBR i get to see the diff?

And another thing, are nanomod's nightly builds for the 7D? I see in the change log pelican's update to 7d stubs.

noone knows?!

Push record and you'll see em (make sure audios enabled in canon menu obviously). as far as the beep. still havent found it.

bitrate hack works. Just make sure you know what you're doing. It can crash the camera needing battery pull.

Yeah, I know the bitrate hack works. It's not what I'm taliking about. I'm talking about the GOP and frame dump hack.
Did you even read my post? Because you didn't answer my question. You seem to just make up some other question and answered that instead. Do you think you where being constructive? What exactly did you contribute by your answer? Did you even think about what you blurted out?

Hi Devs,
Was wondering about the frame flush and GOP parameters, under video hacks. Do they actually work? or do I need the build from the Halloween bitrate monster thread? ( http://www.magiclantern.fm/forum/index.php?topic=3404.100 ) I've been doing experiments and have read about the ISO-bitrate relationship and all that. I've read the threads and all but am wondering if it actually does anything. I am using VideoSpec to see the details but according to it the GOP is no different even when I change it. Further, I seem to get higher bitrate per ISO with it turned of all together.

Or is it only with VBR i get to see the diff?

And another thing, are nanomod's nightly builds for the 7D? I see in the change log pelican's update to 7d stubs.

ISO question >> http://magiclantern.wikia.com/wiki/ISO << Here the answer

Nice. good read.
Thanks

Hi guys

I spent the entire weekend filming a custom bike builder out in Brooklyn and used this opportunity to test the RAW functionality on the 5D Mark III . It was a great experience and i learned a lot, but i also realized quite a few downsides while shooting. I hope you guys might have some tips/tricks to the following issues.

1. It's really annoying that its not possible to playback the recorded video in full color and FPS - Is this something that will be possible in the future or is the camera just nu strong enough?

2. I'm still trying to find a good way to set exposure. I was using an ND filter, but it takes time to adjust ND, ISO and f/stop. I try to expose -1 and it works fine. How do you guys expose and do you have any tips/tricks here? I heard some only adjusting the ISO and f/stop. My friend shoot on the Black Magic Camera and kept the ISO to 800 and only adjusted f/stop and the ND filter. I guess there is a lot of ways, but how are you doing it?

3. CF Cards - I bought 3 cards which was not enough at all! I had to bring a computer and constantly unload the footage to a harddrive while shooting. This was a big hazzle that i hope will be improved. How do you guys handle the media?

I really want to keep using the 5D Mark III cause i think the overall image quality is better, and i really like the weight of the camera, but with the issues above i'm starting to look at the Black Magic 4K.

So.
1. I don't know about the playback, but using a monitor to shoot with helps to eliminate to a large degree the uncertainty of an awkwardly placed 3 inch screen. I'd recommend at least 5 inches with peaking and a blue only function.
2. A light meter is indispensable, when you can see the light numerically you can better understand your light in ratio. usually one would fill to bring exposure up to a reasonable aperture pull, or conversely scrim to lower light values for the same reason. Also, graduated neutral density filters are indispensable, You can make your own ND with clear plexi or lucite and RiT dye (check it out) great for making sun spotters and such. And lastly, is your grade, you can shoot for the grade as well to some extent.
3. The 5D mkIII is a differrent animal than the BMCC4K, and quite frankly I believe such a comparison is unrealistic. In digital camera years it's 50 years older. Think about it. Also, why would you use the 5dmk3 to shoot some beta experimental footage, when you could just as easily record your HDMI signal into an AJA ki pro mini which you can rent for 125 dollars and which, at the end of the day, is shooting the res you need? i haven't met anyone with a display that could handle more then 1920x1080. what do you need 4k for? You must want to buy new computers too. cause i don't have the pipe to handle 4 frikin k. Do you? Do you think you do? You don't. Believe me.

Lastly, get an camera assistant, one who knows how to pull focus and aperture. His/her knowledge and experience will, not only, add to your production value. But, they are an extra set of hands to do the complex aperture pulls and focus moves, while you can focus on your story and framing.

BTW. The AJA Ki pro records prores422HQ @ 10 bits. from your 4:2:0 8 bit hdmi out.

funny, i just bought a refurb 7d because i believe very much in the ML team of developers. I was gonna get a 50d instead, but the potential of the 7d is just too tempting, and formidable.

Hi,
About the pink frame phenomenon that I was experiencing. What I did is, I took a fresh copy of ML2.3 Unified Stable release. added Next ML from nanomod but I keep original PDFs and all. then I add update 11. I do this on a fresh 3x format card. 1x in camera remove ML. then format in disk utility to mac os extended, then put it back in the camera and format low level once more. Then I put the new ML files. I am not getting any pink frames. I am shooting 12 fps exact, 1600@ 2.35:1. Camera is 60D , nikon lens, Extreme pro 95Mb/s card, S2 jpeg. 1920x1080 24fps is camera settings. @ 400 iso and 800 iso. I roll for 1.4gb. Before I wold get pink frame within 40 frames and then every 100 or so. Now I don't see it. So, try, make a new card with the ML 2.3, Next 60D and Update 11. remember to remove ML and reinstall with the new fresh stuff on your card. ( I know I am lazy and I wasn't updating NEXT and NIghtly 60d or Updates from the front of the post, probably loose bits messing around on a fragmented card, remember, copying your files from drive to drive is the same as defrag.)

Marekk mluvite cesky? Ste cech? ja taky.

Am I the only one getting "Out of Memory" errors in EOS Utility?  Is there a fix for that?  Prior to installing 2.8.1 everything worked fine...  Is there a fix for this? 

Me too.

I've been doing some tests and such regarding the random corrupt frames with pink errors. I don't know if anyone else is experiencing the phenomenon but, what I've discovered is that the june 27, nightly build doesn't have this behavior. I've been keeping a pretty consistent catalog of raw nightly builds for 60d for the last 2 months or so and have noticed these corrupt frames come up every now and again in previous builds and not at all in others. In the latest builds, including update 11 and nightly builds of late the pink frames are pretty persistent. In the june 27 nightly build. 
https://www.dropbox.com/sh/1kitzbmanifb6sf/Tr-k0D5_Oq/ML-RAW-60D-hourly_2013-06-27_18-30.zip doesn't exhibit the phenomena.
I am no programmer nor do I know anything but to follow directions and do research when it comes to this stuff. But, If someone can take this info and do what you do to determine what's changed. As for the hot pixels, if you use Lightroom or PS to process your DNG's to tiff files ACR will remove them. But, as with the pink frames, even the amount of dead pixels has increased with the latest builds.
As for the frame rate issue. I might suggest making yourself a new ML card. Start with the stable release and build up.
I usually use http://nanomad.magiclantern.fm/nightly/ to get the latest goods and then put the appropriate raw auto exec.bin and modules folder from the raw nightly build.

Update: I took my own advice and rebuilt myself a fresh ML and put the 11th update files: 60d_111.sym and raw_rec.mo into the modules folder along with that autoexec.bin from update 11 onto the card and ran a test. and. no pinky frames hooray.
 

hi Marekk,
is it possible to integrate the changes from update 11 into the unified tree, because I like the black frame and lv_af switch in the raw menu but it doesn't exist in the unified ML Nightly 60D builds.
Thank you,
JK

I asked here cause i saw someone commenting about bad behavior of sandisk with the 60d raw footage. i know the limitation of the 60d but it doesn't change the fact that some cards behave better than others, thus my request for some indication in a good direction specifically for this model.

Well that's a different question isn't it? To answer that I'd say. From my experience the Sandisk 95Mb/s pro cards do give consistent 21.3 Mb/s on the 60D where as the Sandisk 45Mb/s top out at 20.9Mb/s I know it's not much but every little bit counts. As far as any other manufacturer, I don't have any experience with hence, I don't know.

can someone help me to choose a good sdcard for raw recording?

You can do it yourself by reading the information available to you in this forum.
http://www.magiclantern.fm/forum/index.php?board=40.0

And you'll also find, once you do some more research that the 60D is limited by it's own buffer to 21.3mb/s , therefore a fast card isn't needed.

hi Marekk,
is it possible to integrate the changes from update 11 into the unified tree, because I like the black frame and lv_af switch in the raw menu but it doesn't exist in the unified ML Nightly 60D builds.
Thank you,
JK

hi tool.
yeah i shoot @ 11.986 fps. FPS override. Peruse the forums and you'll discover that the 60d is limited by it's buffer, so you must do some juggling to get the resolution you want. namely juggle resolution, aspect ratio and FPS. have fun. also your 60D will likely top out @ 21.3Mb/s, so if you'll notice on the bottom of your camera display in yellow it tells you what you can expect in terms of pipeline.
Have fun.

Now it should be ok:

raw_rec.mo
https://docs.google.com/file/d/0B-HdscXfsKpgOU5ueFdHTjRIYTQ/edit?usp=sharing

LV_AF_RAW is a tempoary solution. We should to find memory address where raw type is stored. Then we can set correct raw type like on 5dmkIII, 600D etc.. Unfortunately disassembling is to difficult for me.

I don't even know what you said just then, disassembling memory address raw type? bro  , but, I'm testing the module now....And it works. Siiiiick. And my 60D is rolling @ 21.3Mb/s. 2948 frames @ 1600 @ 2.35 @ 11.986. That's not bad at all. Awesome. Thank you

Hey John can't see the screenshot.

I can. the black box with the white rectangle is the screenshot.

What it looks like:

Ok, So I checked with the external monitor, set force VGA over HDMI and recorded 1600 @ 2.35 @ 11.986 and works great. (except of the flicker of the meter for the frames and size). I'll put up a screen shot in a few minutes.

Hi Marekk,
So as the other user said, the only issue is the meter flickers, and the frames and size info are cut off at the border with the frame.  Otherwise it's awesome, I like very much the lv_af on/off, it's good, nice touch. I recorded at my usual 1600 @ 2.35:1 @ 11.986 and ran the result through rawmagic 0.7b and looks good, really good. especially with lv_af on, as you know. also, i will test with my monitor and see what happens, because I checked with my friends 5dmk2 and used the monitor with this function and force VGA and it worked, i had acurate preview on the monitor and no corruption so i'll see what is results. Otherwise, this is fantastic, makes framing very nice and it looks nice when you shoot to have all black around the frame. Maybe it's also good for battery life?
Any way. Thank you.

here is a raw_rec code for 5DMKII builds.
https://bitbucket.org/pravdomil/magic-lantern-hack/src/4c786d285287d28e4c7cc9ab72a82753f2fc7a2f/modules/raw_rec/raw_rec.c?at=unified

I'm going do add black borders and automatic disabling of global draw during recording to 60D build (till the end of this week).

Wow. Awesome. Thank you.

Here's the screenshots:





Thank you for all the work you've done here. And A1ex and nanomad and everyone else I have no Idea who you are but thank you, all of you

I think global draw should be ON to do it..

With the 5dmk2 the option to have black border is only available when global draw is off, it's in the RAW rec submenu. I recently shot a short film with my friends mk2 saw the feature and think it's fantastic. I know maybe you don't have the mk2 I'll post some screen grab in an hour or so.