Author Topic: Canon EOS M (Read 1169635 times)

kuchka94 · « **Reply #4050 on:** April 28, 2020, 04:07:02 PM »

hi guys, can you help me? in latest build i can't get working 1080hf in crop mode. i'm choosing 1080hf, full sensor works ok, but when i toogle to crop pressing SET button, picture becomes green/violet(different segments). i tried everything, changing bit, aspect rations, fps, etc. all menu tabs and different settings. but no luck in crop mode.
in previous builds it was ok by choosing slowmo 1080 crop mode from menu or slowmo 1080 + press set button.
What i'm doing wrong? thanks for advice!

Danne · « **Reply #4051 on:** April 28, 2020, 04:19:41 PM »

Canon fps is set to what?

kuchka94 · « **Reply #4052 on:** April 28, 2020, 05:35:53 PM »

i use 25fps in canon menu, but tried 24 and 30, nothing change

Danne · « **Reply #4053 on:** April 28, 2020, 06:02:57 PM »

Could you give me exact settings, preset, etc so I can try and reproduce. Preferrably a screen recording or printscreens to go with that?

kuchka94 · « **Reply #4054 on:** April 28, 2020, 07:12:39 PM »

video with settings, you can see all in 2 minutes, after i tried different settings.

Danne · « **Reply #4055 on:** April 28, 2020, 07:42:17 PM »

Thanks for the vid. Reproduced the issue. I will take a look.

Danne · « **Reply #4056 on:** April 28, 2020, 08:14:28 PM »

New version:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

- Fix for higher frame rate modes in x3crop. Issue reported by @kuchka94

~~Edit: Still notice some black level issues in x3crop. Not consistent. Might take a look. Related to black level automation as always I suppose.~~

cmh · « **Reply #4057 on:** April 28, 2020, 09:16:11 PM »

Thanks for the update.

Danne · « **Reply #4058 on:** April 28, 2020, 09:22:26 PM »

No problem.
Just pushed another build. Think the black level issue is fixed. Happened due to timing registry and only x3crop while in hf modes. Feel free to test and report back if working. Also look for pink frames. Maybe better timing now...

Danne · « **Reply #4059 on:** April 28, 2020, 09:53:12 PM »

Ok, tested new timer regs but the older ones seems better for non crop modes in higher framerate. Therefore I run the old timing regs for non crop mode but when in x3crop I enable new timing regs. Workaround. Not sure x3crop is even working good with higher framerates.
New build pushed again.

cmh · « **Reply #4060 on:** April 28, 2020, 10:13:22 PM »

I did a quick test with kuchka94's settings (high framerate, 3x crop on/off, etc). Everything's fine.

kuchka94 · « **Reply #4061 on:** April 29, 2020, 01:30:19 AM »

thanks! its perfect now

all 46/48/50 fps

critix · « **Reply #4062 on:** April 29, 2020, 08:59:47 AM »

Danne's latest changes, but for 2.0.3:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg224844#msg224844

Danne · « **Reply #4063 on:** April 29, 2020, 09:39:13 AM »

New version:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

- Decided to reduce x3crop to 47fps due to pink frames otherwise. Aiming to have 2.39:1 and 2.35:1 modes free from pink frames with higher frame rates. 16:9 is pretty much hit and miss here so leaving it for now.

critix · « **Reply #4064 on:** April 29, 2020, 10:07:37 AM »

Danne's latest changes, but for 2.0.3:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg224844#msg224844
with:
- Decided to reduce x3crop to 47fps due to pink frames otherwise. Aiming to have 2.39:1 and 2.35:1 modes free from pink frames with higher frame rates. 16:9 is pretty much hit and miss here so leaving it for now.

Disease · « **Reply #4065 on:** April 29, 2020, 01:21:17 PM »

How are you guys getting these high frame rates? Can you only do this in crop mode and in raw? With the cinematic aspect ratio? 2:35?
Is shooting in raw the only way to get rid of the horrible rgb noise and aliasing I get when in normal/codec/not cropped mode?

masc · « **Reply #4066 on:** April 29, 2020, 01:42:15 PM »

Quote from: Disease on April 29, 2020, 01:21:17 PM

How are you guys getting these high frame rates?

Select preset (1080p, 46/48fps), start recording.

Quote from: Disease on April 29, 2020, 01:21:17 PM

Can you only do this in crop mode and in raw?

Use RAW.

Quote from: Disease on April 29, 2020, 01:21:17 PM

With the cinematic aspect ratio? 2:35?

If you like you can setup this too.

Quote from: Disease on April 29, 2020, 01:21:17 PM

Is shooting in raw the only way to get rid of the horrible rgb noise and aliasing I get when in normal/codec/not cropped mode?

Reduce noise by proper exposure and enough light. Reduce aliasing e.g. with 5K modes or cropped modes (1x1 recording) and fast apertures.

ricardopt · « **Reply #4067 on:** April 30, 2020, 11:11:19 AM »

Hi everyone, i know i'm going to get "crucified" by asking this but here it goes... i got on the magic lantern bandwagon recently but i have yet to understand something that might be simple to understand to older people here in the community, in video mode i find the ratio option and when selecting the submenu raw video there's also aspect ratio option.

Why similar options in different menus? if i select 16:9 in movie tab what should i choose in the raw video submenu? i normally select 16:9 on both.

Danne · « **Reply #4068 on:** April 30, 2020, 11:32:54 AM »

Because I want the user to be able to use both. Not at the same time obviously.
Preferred way is to stick with those outside raw video menu cause they are customized to my presets.
It's impossible for me to have been working almost two years refining my eos m build, at the same time create explanatory pages.
My point of view. Any user must be able to do the work testing through on their own and simply make up their own mind and path on how to use this build.
Or simply ask here.

cmh · « **Reply #4069 on:** April 30, 2020, 12:24:56 PM »

I'm not entirely sure but to my understanding Movie Tab ratio is about liveview crop (it restrains the maximum resolution) but gives you the proper liveview and the raw video aspect ratio concerns the resolution, if not matched it might need a desqueeze in post. It is the way it is for technical and performance reason.
edit: matching both is perfectly okay.

Danne · « **Reply #4070 on:** April 30, 2020, 01:28:58 PM »

Under raw video menu there's a good automated code for calculating ratios for all presets. Not always working optimal with my crop rec presets.
The way I started doing it was to set raw video ratios at max setting then limit raw buffer directly or with skip offsets or combining the two. This way I have control what part of the sensor to use and not. This is by no means perfect but It will let me refine and have better control on my experiments.
I was having some discussions with jiphop about taking out raw video resolutions but then again people tend to experiment on their own with resolutions so it stays.

cmh · « **Reply #4071 on:** April 30, 2020, 01:50:58 PM »

Yeah I'd assume that it's too complicated to explain in details to non ML devs.
It's hard to find the right balance between usability, user experience and simultaneously satisfy power users.
That's one of the reason why a lot of open source softwares seems clunky for newcomers (but there's other factors, like budget and time constraints, the lack of bug/feature reports, stubborn dev team etc).
edit: I think you did a good job so far. I have my own little lua video presets that are just made off of the 5k anamorphic script (if I need 10 bits with a slight increase in resolution or 12 bits depending of the lighting conditions for exemple).

canoneer · « **Reply #4072 on:** May 02, 2020, 09:17:40 AM »

I got some assert file messages yesterday and soon after that "card full" reported from canon sw (I know since message is in the M language selected). The assert file reported about mlv lite packaging (deleted it as I tried to release space (silly me)). Now I wonder if I should go back to an empty card, then reload Ml and start up again. But if the messages are due to original parameters - I guess it will still be there, because the card is absolute not full - I must probably re-format and start from absolute scratch. Any advice is very welcome before I am back at the desk today.

nightly 13 jan eos m 202.

canoneer · « **Reply #4073 on:** May 02, 2020, 09:39:13 AM »

Re-card full-

None of the visible files on the sd card hold vast volume - disk say full with 31.9gb data, ML folder hold 36.7mb, EOSM 66kb, ML setup 98kb, auto exec 459kb. Thats all. Mac´s disk utility confirm full. So I guess I go back to start.

yokashin · « **Reply #4074 on:** May 02, 2020, 11:01:31 AM »

Maybe can help making the format SD card from the Canon menu with the option not to delete ml files?

News:

Author Topic: Canon EOS M (Read 1169635 times)