Messages

Wow, Danne, congratulations!!!
Greatly appreciate your efforts, you get something new and interesting to experiment with.
Shoot "Battleship Potemkin" remake for example
This is what I like about ML most: a big journey could be started just by uncommenting a couple of strings in sourcecode

Wow, you ask me as if i know, what it's all about
This is why i can to some extent be sure, that the "strength" is the source of problem:
First, I experimented with precompiled version, and has no any problems.
Than i compiled the version from repo, and got the corrupted filesystem.
I commented out all the SDR104 testing  - and no more corruptions.
I have only one SDR50 card, it records fine at 120Mhz. 12bit FHD losless continuous.
For now, i'm happy with that.
If you eventually will deсide to reimplement card spanning, that would be fantastic

I want to find the answer on my question
And i want to warn others, experimenting with code from sd_uhs:
1. Card overclock and reinitialisation should be performed when there is no card activity.
2. Last version corrupts filesystem(record several files with one filename) when "driver strength" is changed.

This is the starting point of my message: by running that code at startup you risk to corrupt your card.
I did.

And how do you run that Lua script? Manually? What the point of that script then?
There is no problem to run some code.
The problem is to choose right time to do that.
And, by the way, no need to disable RAW video mode to enable overclock itself.
Problem with allocating buffer for write tests only. 

How to safely activate some default preset (without any testing) during camera startup?
I mean, to place that code at the module initialization is bad idea (I tried ).
Need some delayed activation, when everything is loaded and no more card activity...

How to get 1x3 binning on MKIII?
I compiled "bleeding-edge" 700D crop_rec - it's not workig on MKIII, as advertised
Then, I uncommented 1x3 preset in crop_rec from the crop_rec_4k_mlv_snd branch -
yes, it already has one for MKIII, just commented out.
And it works!!! But, vertical resolution is wrong!!!
It shoots 1920x1258 - 1920x419 after resizing.
I tried to increase target YRES in crop_rec settings - no difference.
It looks like I need to fix mlv_lite code - it doesn't recognize that binning and don't let to choose correct resolutions...

I think this thread is the best place to keep notes on shooting with Canon's AutoISO.
Reminder: Currently Canon's AutoISO is the ONLY way to shoot RAW video scenes with drastically changing exposure over time during one shot, if you want camera exposure changes too.
All the information hereafter relevant to magiclantern-crop_rec_4k.2018Jul22.5D3113 build.
Preparation: Need to put camera in Av or Tv mode, ISO Auto, of course.
Disable "Exposure Override" and "Small hacks".
Use RAW histogram and/or RAW zebras to evaluate exposure, use exposure compensation to manually ETTR scene.
Usually, +1.3-+2.0, depends on the Dynamic Range of the scene.
Shoot 14 bit, lower bit-depths confuses AutoISO.
Camera disables AutoISO at all at x5/x10 zoom, so no 3.5K crop mode  
Often, not only exposure, but DR changes drastically too.
For example, you want to shoot the sunset, than the promising look of your girl holding your hand attracting you towards the sun
Use more conservative settings(less compensation) in such scenes.
Postproduction. If you shoot timelapses, use the same deflickering workflow to compensate exposure shifts.
Alternatively, it's possible to manually compensate in Resolve with keyframes and primaries wheels (keyframes not affect Camera RAW settings, no easy way to change exposure during one clip). Or, cut the clip into several ones.
Regarding bit-depth and zoom modes limitation: It's possibly no way to get AutoISO working correctly with redused bit depths.
But, maybe it's possible to enable AutoISO at zoom modes?
Moreover, I remember discussion about AutoISO with exposure compensation in M mode.
That will be the best option to shoot this way...

Ok, Thank you, finally, if ETTR lost anyway, I found simple working variant: Av, autoISO, mlv_lite, crop_rec, Full-res LiveView, FPS override. Works pretty well, except everything gets slow(and autoISO) the less FPS you choose.

Hello, guys, I want to participate in "full-res LV in video mode" discussion.
My ultimate goal is to solve 2 main (for me) silent timelapse shortcomings:
1. No aperture control on USM/STM lenses.
2. Long exposure limitation.
And "full-res LV in video mode" looks as the best solution for rise the timelapse capabilities of ML: Video mode brings control for aperture on its own. And full-res LV adds exposure control. That was my idea.
Spoiler: After spending all day i come to conclusion, that full-res LV is very interesting proof of concept, but barely usable in it's current stage. It need correct exposure readings, integration with intervalometer and Auto ETTR.
Details. I loaded crop_rec, ettr, silent and start experimenting in manual video mode. crop_rec_4k.2018Jul22.5D3113, EF 35mm f/2 IS USM
1. Auto ETTR disabled due "This feature requires you shooting raw". So no Auto ETTR.
2.I dial to shortest exposure - 1/33 and press half shutter - and got brighter image with 1/7 on preview. Preview has no histogram, no way to estimate exposure.
1/50 corresponds to 1/11, 1/130-1/29, 1/1000-1/310.
3. I started intervalometer. It takes pictures, but if canon's image review is "hold" you need to press half shutter yourself every time, and if you make image review "Off" intervalometer gets disabled  - "Auto ETTR: enable image review". But keeps working, even with preview.
4. Ok, exposure is wrong, but controllable, is it possible to get longer than 1/7 exposures? I started to activate crop mode "Full res LiveView" and FPS override in various combinations. Crop mode always makes preview distorted. FPS override affects only on preview, but not actual image taken with full-res LV.
5. Finally, I unloaded crop_rec and changed silent mode on full-res. Yes, it warns that works only on photo mode and not works with half shutter. But, works via intervalometer. Surprisingly, Auto ETTR with intervalometer works too, and histogram on preview. Sadly, it looks like silent full-res in video mode suffer from all the shortcomings: no long exposures due to video mode and no short exposures due to silent full-res limitations.

Hello,
I am very new to video (been a RAW still photo shooter for years, however) and am having difficulty with scenes that are shot in one take and have drastically different lighting from origin to end point.

1. Use Canon's autoISO with compensation according to RAW histogram(For me +1.3 works good in any scene).
2. Use David Milligan's bridge script or any other deflicker software to compensate exposure shifts.
3. Bingo!!!
IT would be great if Auto ETTR keeps working during take. RAW histogram keeps updating, though...

Need to warn that this batch erases all the mlv files but keep only last one renamed to "ORIGINALS"
if executed on media without free space(card recorded till last byte).
It happens because it unsuccessfully tries to create "ORIGINALS" folder
and than commands to move to that folder
just renames files with same name, while the only last one remains

[the only thing that can really influence the color science on a CMOS is the bayer filter / color filter aray (CFA) in front of it.]

the only thing that can really influence the color science on a CMOS is the bayer filter / color filter aray (CFA) in front of it.

Bingo!!! And, by the way, this is why sony can't do 15000K WB as Canons...

...
1. Export from Raw to ProRes 4444 12 bits via FFmpeg

Sadly, there is NO 12 bits ProRes in FFmpeg.
But You, as a software developers, can help to fix that:
https://trac.ffmpeg.org/ticket/7163

... I can upscale to 4K and get acceptable results (little bit soft).
...
I want shoot a project on an iPhone X and wanted to complement it with some footage shot with longer lenses on Canon

Maybe this is better suit you project, dude:

Great, you did the job. Seems it takes about half year for you - pretty good.
Congrats!

Shot in FullRes with 4 fps.
Heavily stabilised with lots of artifacts.
Than twixtored, almost without artifacts.
I'd rather to shoot with higher fps, but lower resolutions.
It will be more easy to stabilise and no need to twixtor.
But who knows that hyperlapse technik, used to work very well from boat, will fail on air baloon?
Animated photo on thumbnail.

Hallo, guys! Thank you for your work!
Maybe I'm too late for this party, but until now I used this incredible mode only in FullRes for timelapsing and hyperlapsing.
Now I plan to make some videos of people, with sound and made some tests.
Now feedback:
1. First of all, thanks g3gg0 for 2018-06-26 23:36 build: sound is great, imports to DR automatically in sync.
I didn't shoot anything with sound with mlv_lite before, so i'm unsure, is it fixed, or simply works.
But, need to say, i didn't even used last mlv_dump, but "mlv_dump on steroids".
It has feature to analyse every frame for stripes.
So, i didn't tested last build of mlv_dump, but what i have for converting MLV, works perfectly.
2. Need to be very careful whether to use compressed formats, if you plan to shoot something fine-grained
The fun part, the camera keeps shooting after glitch and video continues,
it's just no possible, due to messages on screen.
3. Canon AutoISO works correctly only in 14bit. In other modes it should be disabled with notice for user.
4. Exposure shift in 3.5K 1:1 centered mode. maybe it discussed, i didn't find, sorry.
Look at video from OP: https://vimeo.com/217313287 at 05:35:
as zoom button is pressed and x5 mode entered, exposure changed from 1/50 to 1/35.
It need to be manually corrected every time? Nobody noticed that?
And only this mode supports compressed with reduced bitdepths thus allows maximum resolutions!

... Since there is some effort done to high speed imaging @ 120fps with Magic Lantern...

Whaaaaat? I missed something?

Could anyone guide me in what step I should to the upscale in ACR in AE?

To be honest, AE, (not ACR), has "Detail preserving upscale" for a long time.
And on topic:
No, Adobe is not a garbage they are very mature and feature reach set of tools,
but too hungry for money and ACR is painfully slow with RAW.
And Resolve is on pair in quality with RAW since v12 but chews it in realtime on good GPU.
And the core functionality is Free!!!
Yes, and Adobe development is completely stalled, while Resolve evolves rapidly.
Literally, every time i read description for the new Adobe release, i only yawn.
On the opposite, for example, as long as i start to include VFX in my projects, BM added Fusion functionality.
Simply incredible.

...lens or/and body parts can get very hot, can brick or melt.

In the case of nuclear explosion:
To prevent the severe and permanent damage to the state boots by the melting iron,
the soldier must hold his rifle in outstretched arms.
(USSR army regulations)

@Dmytro_ua: you should be in photo mode.
In video mode FRSP works too(and you even can manage aperture of STM lenses!!!), kinda not documented " full-res LiveView", but with video limitations on exposure.

Very strange, coz i have device that actually works - here is my quote from "Remote follow focus." theme back in 2016:
"
...That Aputure V Grip USB Focus Handel V-Grip have just arrived and I make a quick test: it works, but...
Not from the first attempt and i several times freezes camera,
finally i realised that it's important to first connect and switch on the device, just after that turn on the camera.
And even this way sometimes it just not works. I need to restart camera several times.
It has 3 speed presets selectable by button, two of them seems too slow for me.
It can control aperture too, has focus/aperture switch button.
Zoom button activates x5/x10 view....
"
So, what so special with this one?

I've shot a lot of timelapses with sun in the frame, and never worried about sun itself.
Saltwater, waves, sand, rocks, wind tilting tripod... and so on - this is the real pain.
But i use wide lenses and polariser.
As far as I understand, the longer your lens, the more dangerous the sun. And at F22 you can damage not the sensor, but the aperture blades:
https://petapixel.com/2017/09/01/photos-cameras-lenses-got-destroyed-solar-eclipse/

Sorry, what is this all about?
5 years ago gone bug in DR, or lens artifacts, or what?
Can you please share one DNG?