Messages

I had a 60D since I got it new in 2011 but never did much with ML on it until a few weeks ago thought I would try it out and realized one could shoot RAW, but I couldn't get more than a few seconds of RAW before it stopped. Also, there was the (lack of) auto focus.... so, I was able to trade up to the (3 year) newer 70D, and after past week of trying some ML builds, reading things on forum and here, I am happy to report that the in development ArcziPL's crop_rec_4k experiments for 70D (magiclantern.fm from March 2021 appears to be working for me. I haven't shot seriously yet, but with this build I do find I can record at least over 1 minute continuous, as 1280 res, 12 Bit RAW using SanDisk Extreme 200mbps (ML Benchmarks r/w just over 40mbps). The only issue with this build I seem to notice is when in the ML menus, they jump between ML and Canon (I have seen this reported by at least one other 70D user in forum (with video showing it). Even with that issue, I am very happy with this build on my 70D! Thank you for this work.

Do try SD overclocking, you will get twice the speed.

This is just guesswork on my part, but LR needs to have proper EXIF metadata to interpret the RAW file. Take, for example, camera model. If the tag is missing, erroneous, or somehow clashes with LR's built-in camera profiles (which can happen if an image is not, in fact, a straight out-of-the-camera photo, but rather something converted or generated by a 3rd party app), LR can 'display' the file in a different way. I have this issue with DNGs generated from DualISO files by cr2hdr (I need to manually change the camera model tag from my 70D to, for example, 60D to make the resulting DNGs have correct 'brightness' in LR). Perhaps there is a similar LR camera profiles bug with your model. Do try changing the camera model EXIF tag to some other, similar camera.

Отправлено с моего SM-G960F через Tapatalk

Oh, I knew there was Canon crop on select models. I just wasn't aware it was a ML feature separate from crop raw recording for rest.

Okay, next question: was there ever ML crop mode without raw? 'Cause I can't imagine anyone shooting pro videos with aliasing either.

Отправлено с моего SM-G960F через Tapatalk

Ah. It's just that, coming from a stills background, I kind of think of non-raw as JPEG. And I can't imagine shooting photos in JPEG any longer. If I see another one of those unrecoverable 8-bit blown highlights...

This bit of feedback leaves me confused. He used ML, but not for shooting raw video? What gives?

Отправлено с моего SM-G960F через Tapatalk

And your lens model, too.

Отправлено с моего SM-G960F через Tapatalk

Presumably, because it's lossless *compression*.

Отправлено с моего SM-G960F через Tapatalk

Thanks for the explanation, masc! I am a sucker for ETTR, so overexposed highlights is something of a job hazard.

I am curious about 11-bit vs 14-bit highlight recovery in MLVApp, though. Why is 14-bit material so much more accommodating in this regard (at least out of the box, without tweaking RAW white level first)?

Guys, I've a question about highlight recovery and bit depth. I just reread https://www.magiclantern.fm/forum/index.php?topic=24933.0 and was mightily surprised by the findings, because in my 70D experience with MLVApp highlight recovery for 10-bit material is vastly inferior to 14-bit (to the point that I stopped shooting in anything other than 14-bit).

Is ACR's highlight recovery so much more advanced (or MLVApp's so much more... the other thing) that the latter can recover almost nothing from blown highlights in 10-bit (I just get pink areas), while the former can?

Отправлено с моего SM-G960F через Tapatalk

I don't really know what to think. On the one hand, it is April Fools Day. In the other hand, ML devs seem have a tendency to announce mind-blowing breakthroughs on precisely that date.

Отправлено с моего SM-G960F через Tapatalk

One more thing to keep your expectations low: if you're looking forward to shutter wear-free FRSP timelapses, the thing is only sort of half working as intended. I ended up getting a separate 60D body just for that (but then again, has found that the AETTR wasn't really working for FRSP).

I can go as high as 2560x1072, not higher. Actually, not always continuous rec. even with this setting, so maybe one should consider 2240x938.

You definitely CAN achieve 2560х1313 at 11-bit lossless (I have, and it was continuous for 15 minutes), but it takes a scene that is not very busy (well, it works for a pond with water ripples, for example - just not some panning shot).

But keep in mind that 70D will likely always lag behind other Digic 5 cameras in terms of ML development precisely because of it's unique DPAF. It might even end up abandoned altogether if the devs get more excited about cracking DIGIC 6 and newer cameras instead.

Sure. As far as I know, you can focus manually whenever you like (provided your lens supports it), it does not matter if it's with ML running or without it.

Unfortunately, until a 70D-owning (or sufficiently interested to buy one) dev comes along, or some of the active devs gets their hands on a body, waiting won't change anything. That is, if changing DPAF behaviour when cropped is even possible...

The answer is, sadly, no.

Отправлено с моего SM-G965F через Tapatalk

Guys, I've a really dumb question: I know that crop mode is superior in terms of aliasing (and resolution), but how do you feel, artistically speaking, about the fact that it compresses the perspective (when using a shorter, but cropped, focal length lens at the same shooting distance)?

Отправлено с моего SM-G965F через Tapatalk

You're like those PGP etc. users: you just don't get it that using certain technologies is a red flag that will get you into trouble. They (PGP etc, can't say anything against this proposed plugin) are developed precisely for you to advertise the fact that you've something to hide. Pro tip: learn about anti strong encryption laws in whatever 'non-fascist' country you end up in. Will likely save you a lot of legal troubles, too.

P.S. You got screened at the airport and got spooked, right? Now, what would've happened if your camera WAS checked containing encrypted material? You would've been regarded legitimately suspect, detained, and given a proper Israeli-grade (just an example of a country taking its security very seriously) interrogation. A several days-long one, I'd wager.

It's either a cash machine, or 'at the moment'. Suppose it's the latter here, though a 'cannot assist you-type ATMs' may soon become rather common, too :⁠-⁠)

Отправлено с моего SM-G965F через Tapatalk

Indeed. FRSPs all suffer from this effect.

Отправлено с моего SM-G965F через Tapatalk

 Make sure you are staying within FRSP's very narrow shutter speed range. You will most likely need an ND filter.

Отправлено с моего SM-G965F через Tapatalk

See the answer to a similar question here: https://www.magiclantern.fm/forum/index.php?topic=26593.msg239861#msg239861

Отправлено с моего SM-G965F через Tapatalk

Did you find a solution for this one?
I got the exact same problem.

All the best

No, unfortunately.

[Universal SD Overclocking module]

New Universal SD Overclocking module version for DIGIC 5 models:

Wait, what? 'Universal' as in 'will work with other people's builds on other DIGIC 5 cameras, specifically 70D'?