Messages

For two months this thread was completely dead and now in three days I'm already way behind.

Update danne on the issue I mentioned.

For recap. I was on May 2022 3123

Fresh install. 60fps preset. Global draw off. Small hacks on, af off, lvface +aewb

Getting only 60-65mbps on a 0.0 exposed scene.

After seeing your update I decided to test all three builds, April, May, and now December under the exact same settings on the same scene.

April was ~85mbps
May was still ~65mbps
December was ~85mbps

Whatever you changed clearly made a difference. If there is anything specific you'd like me to test let me know. I am going to probably be going through a lot of the settings exhaustively over the next month since I recently got some new lenses and a tripod anyway. I'll update if I find anything.

I don't know if this has already been reported, but I'm getting a massive difference in write speed on the april 07 3.123 build that bilal linked vs the may 15 3.123 build.

This is present in the 1080p 60fps preset. Clean install on both. Global draw off, card spanning off, small hacks and aewb+lvface on both builds.

I get around 60mbs without any hacks on for both builds, but 88mbs on the april build with hacks on and only 66mbs with the may build. Is the write speed indicator reading correctly? I haven't tested aggressively, but I've shot the same scene with both and there is a clear difference in write speed, even if maybe the indicator isn't accurate.

Is this happening for anyone else?

When recording you can press the magic lantern menu button (trashcan) and see a current recording speed as well as a max recording speed. How accurate is that using the 3.5k preset?

Edit: Tested it myself, what I'm talking about is if you move your selector over the RAW module, and then exit the ML menu and start recording, you can press the ML button during recording, and it overlays the ML menu, with the selector still over the raw module, showing the current record speed. It doesn't seem to be as accurate as the recording indicator that pops up when recording though.

For reference with an estimate of around 163mbps from the ML menu, I can record continuously at 12bit. In case anyone else records 12 bit regularly. Actual speed is around 135mbps. I haven't experimented with the quality 10bit produces, but I am going to test that next since 10bit seems to be continuous in almost all exposure scenarios.

I don't know what you're trying to say, but the important thing is the increased writespeed. And the latest build can only 3840x1536 (continuous recording too).

-> we got never more than 131mb/s

I didn't want to overstate anything but it seemed to me also that the write speeds were faster than I expected them to be in 3.5k. Thanks for actually checking!

I think there is something about the 3.5k preset that the 5d just handles extremely well. Less system load or something.

Whatever makes the camera freeze. Don't do it.

Hahhahahahha. Good advice,

We are currently at a rough limit of 6 megapixels at 24fps or 144 megapixels per second.

I'm not sure if it's possible to squeeze any more out of the 5d mkiii, but for reference we are just 10% away (3840x1920) from this camera being viable for producing Netflix content! Well like 15% away if you count total resolution area but it's amazing how much you guys have managed to push this camera

I see. I think I need to shave down a few more pixels then. Let me test some.
EDIT. What resolution are you using?

I was reducing resolution to allow for continuous recording in each case. From 2.8k to max. I got one error at a lower resolution with global draw on, and also at max resolution with all settings checked and global draw off.

@danne just tried the new build and in the 3.3k preset I got compression errors at roughly 1.5 minutes of recording a few times, but I can't seem to reliably reproduce the error.

I tried going down settings in order:

- card spanning on, nothing else
- bit depth on, nothing else
- overclock and card spanning, nothing else etc.

I had an error with card spanning, overclocking, and bit depth and global draw on, as well as global draw off. It's possible it returns errors with other settings. I tested roughly a minute and a half for each trial.

Unfortunately, when I found an error, restarting and trying again with the same settings did not reliably reproduce the error. I will try more later my camera is currently cooling off.

I will also test the 3.5k preset more vigorously, since I'm eager to use it for product demonstrations for work, so it will get a lot of testing over the next few days.

Hello Danne.

Thanks for the build. I'm on firmware 1.13 and with your latest build I have a flashing liveview, alternating from parts of what is in sight with strange colors to full colored pixel view (like a TV without a channel).

Whatever the mode set it's not working and generating corrupted messages and asserts logs if I try to record.

I've tried numerous settings (spanning on/off, various résolutions/bitdepth), no one working.

@70mm what firm are you using ? 1.13 ? Have you wiped the SD before putting the new build ?

Weird, I ran it on 3.113 and didn't run into any issues, are you seeing this in all presets, and not just the 3.5k 5x? I formatted my sd card in camera before installation.

[New builds:]

New builds:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899

- Expanded 3.5K 1:1 centered x5 preset height to 3584x1730
Why this. Now we get cropped real time preview and framing instead of only framing preview when using 3K 1:1 preset for instance.
For 24fps you can use full 3584x1730 but for 25fps I had to reduce height to 3584x1660.
Needs some testing. Now we can get 16:9 3152x1730 with cropped realtime preview. Nice.

I am already finding the ability to see real time focus (albeit cropped) extremely useful, and I have also found the 3.5k x5 preset to be the most stable whenever I've tested anything before (even with a knock off SD card) in general. Very excited.

I just tested it using a variety of settings on 3.113 (card spanning on, off, overclocking on, etc). I have yet to run into any issues. Seems very stable.

The inclusion of a "preferred card" toggle in the raw video menu was a nice touch. I tried just SD card using that setting in 14 bit 1080 and it also worked well with no issues.

The new 2.07 - 1 max aspect ratio in 3.5k is really nice. I may start shooting this aspect ratio a lot. Gives me a clear foreground, middle ground, and background without the feeling of too much vertical space. Anything between 1.77 - 1 to 2.4 - 1 is really up to taste, but this feels like just right to me. I can't wait to start designing some shots and feeling it out more.

Also at 3584 x 1730 we are getting a whopping 6.2 megapixels, which is even higher than UHD 3840x1536 at 5.9 megapixels. And with the ability to see focus with global draw off I can actually shoot that resolution continuously in a lot of lighting conditions!

This is a very big update. Ability to check focus in real time with global draw off means I can shoot at high resolutions and still take full advantage of the overclocked write speeds without being totally blind. Awesome.

Thanks Danne. I'm going to be playing with this new build all week.

Oh I missed that you converted to the BMD log in resolve.

I have a question about how that works. When you export a cinema dng from MLVAPP, what happens to the color space? The standard setting is just tonemapped rec709, but when exported as a cinema dng it doesn't seem to make a difference what color gamut was selected.

Does the color space just get interpreted by Resolve and the cinemadng file contains all of the original RAW data?

Shots are very nice looking. I am not an expert with post processing but it sounds to me like you're doing things right. I personally have compared log vs rec709 in mlvapp before exporting and found dramatic differences in shadow and highlight detail. Log files seem a bit more complicated to grade but it's worth playing with if you'd like to experiment.

Were you really able to get 3.8k 12bit continuous shooting with a 16-35? I tested a lot and settled on 3440x1440 as being "continuous in virtually all conditions," regardless of scene dynamic range, field of view, etc. Maybe I'll go higher. How wide did you shoot most of these shots?

Cut the blue in your shadows!!
Looks very amateurish and I would highly recommend starting with some LUTs instead of getting everything done by curves, especially if you're new to grading.

If you take some time, u can find a lot of really good workflow breakdowns in some of the posts in this forum...

Thank you for the feedback!

I graded all the images neutrally before I applied the "creative" look. I thought I did okay:



(blacks are crushed in that still so "mostly neutral") And then I added a blue overcast to the shadows and mids! It just seemed more fun. I am really happy that I actually know what you're talking about though. At first it was really confusing.

I have been reading everything I can in the forums and I actually was going to post a question, maybe you can help!

In resolve, when do you apply a technical lut? I know you're "supposed" to apply it at the start of your grade so you're working in a different color space, but in practice resolve's tools seem to work really well with log files and I have been able to make adjustments seemingly more easily with a lut at the end of my workflow. How do you do it and why?

Online there is supposedly some heavy discussion about this and a certain answer was confusing to settle on.

Thank you Danne.

For everyone's reference I found that:

14 bit lossless with the bit depth menu off,

or 12 bit lossless from the raw video menu with 12 bit selected via the bit depth menu,

Both appeared to have the correct gain, so I would try those settings first if you're trying to record without the crop modes.

12 bit lossless via the raw menu (nothing bit depth menu) appears to be underexposed, and 14 bit with 12 bit from the bit depth menu appears overexposed.

@Danne

I was so excited about the amazing anamorphic mode and card spanning, I forgot to mention something I noticed a while ago.

In regular raw recording without using any crop modes, I get different exposures while using the same exposure settings if I change bit depth.

Switching between 14 bit lossless in mlvlite, 12 bit lossless, or 14 bit lossless in mlvlite with 12 bit in the bit depth menu all return different exposures. I haven't tested any other combinations.

You can't see it in liveview, but when you play back with mlvplay in camera or bring the files onto a computer, the differences are obvious.

I remember this build originally started with you editing the ISO settings, maybe something left over? Or maybe it's a feature not a bug!

Thank you!

Neat video seems to work very well. I am using the paid version. It's much more capable than the various tools in resolve or MLVAPP in my testing. I didn't add any extra sharpening. "Sharpness" in your footage is going to tend to go down in the shooting conditions that would require noise reduction, so that's something to think about, but Neat Video derives its denoising calculations from noise samples that you take from the footage, so it does a very good job of preserving detail.

I'm not sure if there's a freeware equivalent, but I don't think I would try to deliver serious work shot in low light without something like it.

I spent the last two weeks going over old footage with the intention to finally learn how color grading works, instead of just turning dials at random until something looks okay.

Shot in really dark conditions with a 5D MKIII and a Canon 50mm f1.8 STM. Most shots around ISO 1600 at 1920x960 48 or 60fps (did not know how to use the settings at the time really). Because it was a paid gig, I had the foresight to bring two very strong high CRI Zebralight led flashlights with diffusers in both warm and cool color temperatures. It made shooting possible in the conditions.

Converted to Alexa log via MLVAPP , exported as Prores 422HQ and then put into Resolve for curves adjustment. Denoised with Neatvideo. Did not use any presets, which I'm very proud of. I mostly relied on the curves adjustment tool.

I still don't really know how to stitch footage together in a cohesive way so that's the next thing I'm going to be working on.

Here is the before and after -

Log:



Graded:




Log:



Graded:



Log:



Graded:

Bender@arsch I get a similar error when recording higher framerates (either 1920 @ 60fps or 1050 @ 48fps) while using card spanning. I am currently using a 95mbp/s sandisk 32gb card. I haven't tested the error aggressively so I'm not sure if it conflicts with other settings.

Hi Danne, thank very much for your build. It's amazing !
Today I installed your latest from today I guess. I have the 5D3 with 1.2.3.
I work with the 5.7K Anamorphic but I have some issues with the global draw I think. When I record with the global draw my "speed record" is always in the orange and after 30-40seconds the record stop automatically. If I disable the global draw everything works and my speed record is green and around 90Mb/s, and I can record without limits.
I record only on my CF Card Sandisk Extreme Pro 160Mb/s. Do you have an idea if it's possible to fix this ?

Thank you

It sounds like you're describing normal operation. Global draw will reduce recording speed, I believe because it uses up system resources. Also recording in higher frame rates reduces speed, as well as the firmware build you're using. 3123 is slower than 3113 in my testing and seemingly in general.

Is it just that speed is reduced when using global draw? The speed reduction should be around 10%.

The great thing about dannes build is that you can turn on card spanning, which will let you record to both SD and CF cards. That should get you back to normal speeds, or even faster with global draw off.

What are your exact settings for the 5d Mark iii? I have the 128gb A2 v30 170

That model is a micro sd with adapter right? I'm using a SanDisk 128GB Extreme PRO UHS-I SDXC (but it might be a knock off). Firmware 3113. All global draw overlays set off, but global draw on. UHD mode with 12 bit set to on in the external menu. Card spanning on. SD overclock on. If I turn on any cropmarks or histogram or anything else in global draw it will return a "failure to create file" error when I try to shoot, and it will continue to shoot just using the cf card.

Sometimes it works, but if I turn the camera off and on it will usually return an error on the second start up.

I'm getting a lot of "file create error"s when using the sd overclocking, mostly in UHD mode. It seems to happen if I enable anything in global draw. It will also happen randomly, but it happens consistently if I enable something in global draw, then restart.

Edit: I purchased my card off of ebay, and while it benchmarks correctly and does function with ML, I have reasons to be suspicious that it's not authentic so I ordered another one from B&H and will update if this error persists with that card.

Hi again everyone I just wanted to update that I did receive a Sandisk 128gb Extreme Pro 170mbps card, and the patch is working correctly and I can record at 125mbps without global draw or 115 with.

This is further confirmation that the 128gb cards seem to work consistently.

It's awesome! Thank you guys again it's like I have a brand new camera.

Thanks Volumetrik I am pretty excited to get a 128gb and test it out. I'll update when it arrives.

This seems like it could be relevant.

https://i.imgur.com/nS2MvTZ.jpg

I can link pictures of the rest of the red ones if this is anything.

I am not sure what is going on here and don't have my camera here but if it's not working giving card full etc it's better to stay off the patch on this particular card. I expect this patch to either work fully or not at all, no in betweena.
Not sure what coredump is caused for in this case but just stay off patch on that card.
Please remember. It is bleeding edge. I tried to prevent serious errors but nothing is finished.

I purchased this card with free amazon 1-day shipping to keep me busy until my 128 170mbps sandisk arrives Monday. It was $13. So I don't mind destroying the card if it helps debugging. So long as there's no risk to the camera itself.

Same error after low level format. First I tried formatting the card with magic lantern still installed. Then reinstalled magic lantern and tested it. Same error. Then I formatted the card on the computer, then low level formatted it again in the camera. Same error.

This time I tried again but without the CF card.

The error read "card full," followed by "audio failed to stop recording: state 3"  or something like that. So I disabled sound recording. Returned "card full," with no other error.

Then I went into the magic lantern menu and navigated through the various tabs to see if Magic Lantern can show what it thinks the available memory on the card is, and while simply scrolling (no change to any settings) I got an error that said "please send coredump.dat to the devs" or something along those lines.

I was expecting the card 95mbps Sandisk Extreme Pro 32gb to work with latest sd uhs patch.
Could you tell me what ml version you are using? Full name or link to exact build?

Hi Danne! I have been having so much fun testing this build and exploring the new creative options. You and everyone should be really proud of how much you've put into it.

I have tested these two builds:

crop_rec_4k_mlv_snd_isogain_1x3_presets_2020Jul15.5D3113
crop_rec_4k_mlv_snd_isogain_1x3_presets_2020Jul15.5D3123

I did most of my testing on 3113, before briefly changing to 3123 and getting the same error. It looks to me like I'm having a similar issue as IDA_ML.

I just did it again to see exactly what was happening. Here's how it goes, I apologize if this is an annoying amount of detail, but I know you guys are troubleshooting so I'll try to describe everything:

- turn on camera, wait for it to load.
-turn on overclock module
-turn off camera
-receive patching notification
-patching done!
-go to live view, press record
-"recording has stopped automagically" "flushing buffers" "nothing recorded to card"
-turn off camera
-light stays on significantly longer than usual, about 6 seconds
-turn camera on
-"magic lantern was not shut off cleanly, skipping module loading"
-turn camera off
-light normal
-turn camera on
-receive patching notification
-patching done!
-go to ml menu and turn off patching
-turn off camera
-notification light stays on too long again
-turn on camera
-"magic lantern was not shut off cleanly"

and at that point I'm stuck in a loop and have to format the card.

This error has been consistent.

Edit:

@has_abandonment_issu

This is a knowing issue. Try low level format in Camera (SD card) and have fun

I will try this right now.