Messages

Hi everyone, here's a video from 2nd June 2019, Danne build from beggining of May 2019, 1736x976, mcm rewired, mlvapp 1.7, film preset (small tweaks), resized to 4k... edited (no color correction or luts) in premiere pro.
I recomend to watch the video @2k or 4k.

Hi everyone, here's a video from 26 April, Danne build from 24/4/2019, 1736x976, mcm rewired, mlvapp 1.6, edited in premiere pro.

Hi everyone, here's a video from february, probably a build from the same month

Hi Luther, english is not my native language, by aliasing do you mean "jagged lines" or the "jumpiness" in the folliage in the first 16 seconds?

i've uploade the same video without any stabilizer effect added, the "jumpiness" goes away at the cost of stabilization.

25th April

Spot on!
Since that option was next to the fix focus options, i didnt try it as i didnt see that as focus pixels.
Thanks a lot!

I'm using a Kingston 64Gb (Canvas go!)
https://www.amazon.com/Kingston-Canvas-32GB-Memory-SDG/dp/B079SQBCWF?th=1

continuous recording at 1736x976 14bit, fills up the card in 30minutes.

Hi Walter.

1 situation - using EOS M and record a 16:9 (1920x1080) mp4 and crop it to 2:35 for whatever/cinematic reason.
2 situation - using EOS M to record a true 2:35 (1920x817) mp4 video

since the actual picture dimensions of a 2:35 video is smaller than a 16:9 video the video bitrate efficiency would be better and in theory should have better quality since no bitrate is wasted, lets say that the eosm records at 30mb/s using h264, the quality on the true 2:35 would be better than a 16:9 cropped to 2:35 using the same bitrate.

Since 2:35 is using 263 less height pixels the bitrate used on those (top and bottom)  in situation 1 IS wasted if you are cropping.

Im not a pro but i think i understand a little of the basics, sorry for any confusion...lets imagine that the EOS M has a 16:9 and 2:35 modes using h264, both use 30mb/s for video bitrate, if we crop the 16:9 to 2:35 and compare its quality to the 2:35 version we could see that the 2:35 has better quality, better bitrate efficiency.

but i could be completely wrong...this is my opinion based on what i learned reading several video forums over the years.

Hey guys is it possible to record mov files cropped  and save some cpu cycles?
I noticed i have less rolling shutter when im recording raw 2.35:1 compared to recroding 16:9 even in mov h264.
That pre recording crop for sure lets camera record faster when i use 2.35:1 so it doesnt have to sweat as much as when recording 16:9, so is it possible to record actual 2.35:1 to h264 mov files ? That improves rolling shutter and would be worthy from what i see.
What do You guys think ?

If that is possible it would be a nice addition to the magic lantern features, i think everyone in the past has cropped 16:9 mp4 video to 2:35 aspect ratio, if magic lantern could do 2:35 native mp4, the bitrate distribution/video quality would be better on 2:35 video since no bitrate is wasted on "future" cropped areas, only used on actual video.

HI everyone.

Using latest Danne build (24 March), mcm, 1736x976, to get rid of the focus pixels i have to select 3x3 smooth, the options in fix focus dots dont work, also i noticed when recording the sky some artifacts appear, i can only remove them by using a denoiser, mlvapp internal denoiser wont work, here's a sample:




Am i doing something wrong?
Thanks

Thanks for the advice!

New video test, timelapses were done by speeding up the video 3000%, photos were coming out purple, same settings as previous video.

Hi everyone

Been using my eos m more frequently and and it is quickly using a lot of space on my hardrive, i have a few 1tb internal drives already full with backups (noy just mlv) and recently bought a 4TB drive for all the mlv's and phone/gopro videos. I usually convert to prores before editing it, i dont really like to erase videos that dont look very good to save space as it kind of feels like erasing a part of personal history/memories.

By converting to prores 4444 i usually get half of the original file size, but im also kind of loosing that "raw" information if i ever want to use the video again, from what i understand prores keeps somes of that info but not as much as mlv for future edits.

What do you do? keep the mlv's or convert to prores?

Thanks for any advice

Danne thanks for the tip, i didnt have any problem with preview, i was more concentrated on getting the best focus with "magic zoom".

Thanks

About the drone footage, i live in Portugal and the area in the video was "destroyed" by a wildfire in October 2017, the video is from december 2017, the drone is a bebop 2... nothing high end 

 Hi Ilia3101.

i answered your questions in the previous comment, anything in particular you want to know? i'm not a professional only do this as a hobby but ill try to answer.

i had footage from my drone, gopro 5 and the eos m, and i try in vain to match the colour between them, but i couldnt do it and ended up not using any of the gopro footage record in "flat" mode.

For each second on the video i spend around 120 seconds on it, and at the end i gave up color matching and did just rec 709 because what usually was a hobby was turning out into a "nightmare"...so rec 709 was kind of a quick way out.

Hi Danne, im the one who needs to say thanks

im using the 13 february build
mv1080p 1736x1158 and then selecting 1736x976
24fps

using mlvapp (1.5) and adding a bit of sharpness, fix bad focus, chroma smooth 3x3, rec 709 profile.
premiere pro for the editing and warp stabilizer, only needed because of the warp stabilizer, otherwise not needed (only basic "cutting" and sync)

Another atempt with the EOS M and magic lantern, 1736x976, converted with mvlapp (prores 4444, rec 709), edited with premiere pro (no color correction), canon eos m footage from 35s to 2.05s.

Another test...

Hi everyone.

when doing a batch conversion using version 1.3 all the converted clips have only 8 seconds exactly, also is there a way of aplying a "recipe" to a whole lot of files at the same time? i tried importing a "recipe" with all clips selected but it doesnt work, only works individually.

thanks for all the work done in improving this app.

Another one....this time 1736x976 - small colour correction

Cool. Set it to 24fps for continuous action.

Will test it further this week

What's up with the black border on the left?

you mean both left and right? I forgot to adjust the width to 1920... 1920-1736=184.... 92px black bars were added to each side...i was in a hurry and only noticed it after render.

one of the things that i miss compared to the older build i was using is the ability to use magic zoom, i only use manual focus and magic zoom was very usefull to focus things...i tried pressing the zoom button but it doesnt do anything.

Here is a version with filled preview screen in mv1080p. Didn´t test so please report back.

Finally got around to play with this build, i didnt follow the "guide", i just selected crop_rec, mlv lite, lua and sd-uhs, selected mv1080p, 1:1 aspect ratio, 1736x1120 resolution, 14 bit and enabled the sd card hack under scripts...so far so good, sometimes i manage to get 2 seconds sometimes 12 seconds, i'm using the Kingston Canvas Go 64GB class10 UHS-I U3 v30 sdcard, got some purple flashe's artifacts on some clips.

just noticed that, only able to record 6 seconds, i only got into this whole "raw/magic lantern/eos-m boat" recently... i apologize for perhaps asking the same questions.

1- to get 1736x1120 i need to setup the aspect ratio to 1:1 or 1:2, thats the only way i can select that resolution that i'm aware.

2- Is there a difference between mv720p and mv1080p in a "x" resolution? For example 1728x736 is the highest i can select using an aspect ratio of 2:35 on both mv720 and mv1080.

Thanks

Hi Danne, thanks for the build...one quick question...do we need to follow the following steps to use mv1080p:

https://www.magiclantern.fm/forum/index.php?topic=9741.msg204144#msg204144

i activated crop_rec and mlv lite and it works...do i need to activate the sd uhs hack?