Messages

Hey Andy made us a new build  thanks, going to check it out asap. Can we already expect the new raw format (mlv) in this build?

https://bitbucket.org/andy600/andy50d/downloads/

Not just yet.

.mlv is still being developed by g3gg0. It's not yet as fast as .raw and post workflow is a little more involved but we will get it at some point.

For raw video there is no competition to the 50D at this price point unless you count the max 2 second 4k raw capability of the Nikon V1. The next 'capable' camera in line is a secondhand 5d MkII and that is in the BMCC Pocket price range. Judging by several reports/blogs the Pocket cam is not even shipping with raw capability and will instead be through a future FW update. I'm sure it will be worth getting when it's available but who knows.

If it's a simple choice between the 550d and 50D I know which one I'd have

@burton-fzz - The problem is with Resolve. It's demosaicing isn't great for ML DNG or CDNG. Try using Rawtherapee with the AMaZE algorithm. You'll still have moire issues but not the multi-coloured and obvious maze patterns. 

@araucaria - Press the INFO button a few times

Curious question I just thought about.

Would shooting with a 'flat' color profile on top of the Raw video help the grading process instead of shooting the Raw with the default profile, then making it flat via ACR or BMD Film on Resolve?

Raw is raw. There is no picture style. It's raw sensor data

You can apply whatever curve, LUT or look you want in post. 

If you are shooting low light scenes at ISO 100/200 you will of course get noise because you will need to boost exposure a lot in post just to get the mids into anything like a useable place. You wouldn't do that for stills, you would increase ISO which increases the light sensitivity of the camera and the same applies for raw video.

Don't be afraid to shoot at higher ISO values and let the camera do what it was designed to do. There will still be noise but it's not too bad and can be cleaned up in post. I've had nice looking shots at ISO 3200+ where the noise looked quite nice (especially when just the chroma noise was removed in post).

The 5D MkII's sensor is a lot more sensitive than the 50D so low light performance will be better but the 50D is still useable at higher ISOs. You just need to experiment 

@Araucaria - Tragic Lantern has a feature to auto-disable Global Draw when you hit record. You should be able to shoot with the histogram on without a big hit to performance. ETTR is a method of shooting. If you are referring to the auto-ETTR module, yes, it does work in the 50D but you shouldn't use it for video. Expose with the raw histogram.

LOL  I think the confusion was between ETTR as a method and ETTR the module

Don't use the auto ETTR module for raw video as it will alter shutter speed.

Manually expose to the right using the raw histogram.

Lads, I still get the zebra thing. I use histogram, but even thou sometimes overexposed areas must appear and I'm down. I tried resetting factory settings, reinstalling ML, bu no good. Of course global draw is off.

It's your conversion routine that's the problem. I just downloaded your dng and get the same issue but I also downloaded your raw file and converted with BATCHelor (v3). The issue goes away.

I think there is a big misconception among some users and some misinformation about Tragic Lantern (inc 2.0) that makes users more nervous about trying it.

I've never had any major issues with Tragic Lantern on the 600d or 50d, infact I only shoot with Tragic Lantern. It has some nice camera-specific optimizations and features that the Unified code doesn't have. The only reason it is deemed 'unsafe' (although I wouldn't use that word myself) is because some features leave the camera in a hacked state until it's rebooted. The new dual ISO feature is 'potentially' more dangerous than anything introduced in Tragic Lantern. It's all down to the level of risk you are personally willing to take with you camera.

Adding the pre-built modules does not work on the 50D (error linking modules). I think the problem is with the IME modules. I get compiler errors with ime_base.

If you set snap to 5x in zoom prefs and snap to center before you zoom, what you see on screen is what you get at 1080. Preview is in B&W

Not quite. In grayscale preview you see 5x zoom while the video will be 3x zoomed. You need to use the low-res hacked preview to see the full recordable area.

Yes... however I have read that 1% managed to dump 50D and found the values, for sure. So, you can ask him or disassemble by yourself the ROM. If you decide this latter option, I can assist you.

The values must be the ones 1% added (as I'm using Tragic Lantern source code). Probably best to wait for him to come back online then.

Thanks anyway

it is at start of "adtg_log.c" inside "src" and then "modules" directory

Ok, some values have been set for the 50D in adtg_log.c but must be wrong. I don't know where or how to find the correct values. Looked in stubs etc but cant see any cmos addresses. Does it mean dumping the FW to find the correct numbers?

When you enable adtg_log and then you exit from ml menu (back to liveview mode), you should see the 8 cmos values printed onto the viewfinder that change continuously. Do this happens ? It should. If you see the values unchanged and fixed at 0 value (on vf, not inside the menu), then it's a problem of start_cmos hardcoded value: are you sure it's correct ?

Ok, no they don't change. Where do you change the start_cmos value?

Do you see the cmos values running on screen (not zeroes values) ?

I see 8x cmos values. Not sure what you mean by 'running'? They don't change.

The 50D doesn't have a dedicated Movie mode so I switch adtg log on, enabled movie record and powered off. No logs on the card. I've tried recording a bit too and also tried with raw video enabled and disabled.

Sorry Riccardo, I misunderstood what you wrote previously.

Yes, I agree. The video is very dark and noisy. Maybe it was an intentional look and noise was added in post? but it still looks very underexposed to me. It could also be down to an uncalibrated monitor when grading.

...noise is at an insane level!
I can see it even in daylight shots
which were the settings of the camera?

If you're getting noise in daylight shots you're either seriously underexposing or your ISO is set very high. Use the raw histogram and expose to the right.

I've compiled adtg_log and it loads ok but I can't get it to save a log file on the 50D. Any ideas? 

Hi Araucaria,

On an APS camera using a 16mm Anamorphic adapter you can't go any wider than 50mm otherwise you'll get some serious vignetting. Any more than 100mm becomes difficult to focus due to Anamorphic Astigmatism. You could use your 28-70mm in the mid range using a step down ring and a Redstan adapter. Or you could pick up a helios 58mm for £20. Anyway, I'm gonna run before I get in trouble for going off topic!

Cheers

That's one thing I would like to see on this forum. A dedicated anamorphic section. It's even more relevant since the introduction of raw and selectable aspect ratios.

I dunno, there is something I really don't like about VAF's. They never completely eliminate aliasing and moire and can make the image look either soft or a bit fuzzy. I would sooner invest in a really wide lens and shoot at the same resolution in crop mode with no (or very little) aliasing and moire. A 6d with a Tokina 11-16 will still give you a nice 35mm FOV in crop mode. Plus I'm with xNiNELiVES on what he says regarding shooting stills. As you have both I would be interested to see an A/B at similar focal lengths if you have a 35mm lens to hand.

I'm so bummed I can't install ML on this card because of the 64GB+ limitation.

Anyone have any advice for 50D and MKII users? We don't have an SD slot to run / install ML from...

Buy the cheapest CF card you can find. Speed and capacity is irrelevant as you're only installing from it. You should be able to pick one up on ebay for under 5$ or borrow one from somewhere. You only need to to install once to set the bootflag. Then you can use your KB card.

rommex, please don't get me wrong.
I see a very hard-working community here and read all about the progress regarding the 50D with great pleasure. There are tons of people developing the firmware and it's simply unbelievable what came out so far. And this all because these people work for all of us, taking no money for it and releasing it free of any copyright. ML is absolutely free. But here's the issue that makes me concerned. Without ML, especially the 50D would not be of ANY interest to anyone of us anymore. And i can't believe, that the guys at EOSHD.com don't hesitate to make MONEY with it. Although the progress in developing ML is not made by them, they try to earn money with it.

And so are you. Please, by any means: PLEASE stop trying to make money with this FREE work and respect the hard efforts the developers give even YOU as a GIFT. Try to merchandize and sell your products anywhere. But PLEASE don't do it in this forums. Thank you for your understanding.

@Gekko - In what way does Rommex's app constitute trying to make money from, through or by Magic Lantern. His app, from what I can see is 1) FREE (he accepts donations) and 2) universally applicable to photography and video makers, regardless of what camera they use.

Though I can appreciate the sentiment, for a first post as a new member, you're not exactly well placed to make such a criticism really.

Just scanning the web to get a better understanding of debayering and came across this:

http://www.fastcompression.com/products/debayer/debayer.htm

http://www.fastcompression.com/products/jpeg/cuda-jpeg.htm

Might be of use for someone.

After about 55 sec of recording the camera stops, screens (LV & Top) go blank, and i have to press a button to wake it up. I guess i should contact komputerbay about a replacement.

On a side note, my sandisk extreme pro 16gb cf crapped out. camera cant read or format it. My pc doesnt see it in either my computer or disk management. Sandisk was so nice as to upgrade me to 32gb card for free.

Any info to suggest that ML can corrupt cards?

Umm, maybe go into the Canon menu and change the auto power off mode  It sounds like you have it set to 1 minute. Switch it off.