Messages

Thanks again Danne. Will check the new 1x3 mode asap.

Yes, true when HalfShutter is set in clear overlays real-time setting will not work as before.

hi Thank Danne for this info !
--> ML Menu / Display / Clear overlays OFF
After power up the cam next time, it turns back to --> ML Menu / Display / Clear overlays HalfShutter.

Will Do more testing with the 1x3mode later.

What settings did you use?
I also uploaded a new 16 january build. Might work better.

Hi , was previously using magiclantern-Nightly.2018Jul03.EOSM202_mv1080p,
used those settings - see my post #1595 in this thread.

testing Danne's Jan16 build, focusing on the 2,5k preset.
- what didn't change : after starting the cam, first have to go to ML Menu and out of it again to activate RAW video. (no need for this anymore if sd-uhs script set to autorun, this will do it automatically)
- what did change : halfshutter hold to temporaly switch from realtime to framing does not work anymore only the other way round. if activated sd_uhs  either way (run or autorun script) halfshutter (switch from realtime to framing) doesn't work
either. Also there is a haze of vertical greenisch lines in the croped display on the eos-m. this will not appear in the recording.

this jan16 build seems to be more stable, in terms of corrupted frames and videos.
with the 95MB Sandisk 128GB I can record continuously with sound @ 20Frames/sec.

Anyway, Thank You Danne, keep up the good work.

@AF-OFF


Now I just have to figure out the easiest post "workflow" in Linux.

Thanks!

I use MLVFS and Resolve and also the MLV APP by Ilia3101 , which is very nice! I wish You success with finding a solution which works for You.

https://www.magiclantern.fm/forum/index.php?topic=20025.0
https://ilia3101.github.io/MLV-App/

@Danne
Just tested again. works perfectly. sorry for that confusion.

@Danne (aspect ratio set to 1:2)

Yes.
After the initial loading of all modules - set 3x3crop and execute one of those 3x3 lua script. restart again and the set the aspect ratio to 1:2 and the res should change to 1736x1120px.

@All
please follow the instruction carefully and this should work for You too....#1595

sidenote - with MLVFS and Resolve everything seems fine. in MLV App the resolution is shown as in cam, when halfpressing the shutter for framing (1:2) has to be corrected under the Edit -> Transformation - Height Stretch shows 1.67x have to be 1.0x






 

@Danne
Autostart the script breaks somehow the whole setup. BtW do You use the PAL or the NTSC preset in Canon menu?

@Teamsleepkid
if You can't get over the 864px therefore there is the script used for. even if this seems ridiculous, restart the cam afterwards. hope You will catch it.

Af-off

@ tupp - I think the only difference between the two is the ISO - 100 - 800. So choose which one fits Your needs. You don't have to use the script every time you power the cam on. if you wish to change the iso, please do it in the ML menu, not in the canon one.
the script "enable SD overclocking" has to be used every time the cam is powered on.
( Sometimes I forget about it. )
af-off

Helo
maybe this may help You.
First, let's ensure You have something similar like the following -

eosM
Firmware v202
Camera in Videomode
64GB W50 R55 , Exfat
nonAF lens
a full battery

canon settings
PAL & 1920x1080@24

ML Version
magicklantern-Nightly.2018Jul03.EOSM202_mv1080p.zip
 
Put Your card in a card reader and Save Your data.
Start the cam and go to ML Menu -> Prefs -> Config files -> Restore ML defaults, then leave the ML menu.
Turn Your cam off and back on again.

Go to ML menu -> Overlay and turn GD off
Go to ML menu -> Modules and activate
                     crop_rec
                     lua
                     mlv_lite
                     mlv_snd
                     sd_uhs , then leave the ML menu.                     
Turn Your cam off and back on again.

Go to ML menu -> Movie -> Crop mode and select 3x3_mv1080_EOSM
Wait few seconds then leave ML menu and enter it back again.
Go to ML menu -> Debug and check Memory patches entry - it should be active (red) and show "1 ROM, 2 RAM" entry.
Go to ML menu -> Scripts and select one of the mv1080p_12bit scripts.
Press SET to load/run this script. Wait until it completes, then leave the ML menu.   Turn Your cam off and back on again.

Message visible after startup should be "FPS override : 24.002" *)
Go to ML menu ->  Movie -> Raw video and tap the screen . Inside it change the Aspect ratio value to 1:2 and the resolution should change to 1736x1120. Change the value of Data format to 14-bit lossless. Change the "Preview" to "Real-time".
Leave the ML menu.   Turn Your cam off and back on again.

Now Your cam is set up. The following step is necessary to allow higher speeds of the SD card. This step has to be repeated after each start of the cam.
Go to ML menu -> Scripts and select the "enable SD overclocking" script and hit "Run Script". Wait until it's done. Don't use the "Autorun" feature to start this script automatically at startup.
Activate GD if You like.
You should see an upper portion of an image. Press&hold Half-shutter for framing. 

My recording speed is around 50,8 MB/sec

So this works for me and I can record non cropped 3x3 mv1080 type video. The cam is responsive and the green recording sign jumps in right from start on. Disable GD, then record to check the actual speed, reenable GD after again.

The first picture is 50mm lens, the second a 28mm and the third a c-mount 12.5mm lens.   

Many Thanks to user "the associate" who motivated me and of course to Danne for this build and all other Devs and ML folks

Af-off   







 
                     
   *) Even thou this message is shown at startup, the frame rate shown under ML menu -> Movie -> FPS override is shown as 23,980