Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Pacerx999

#1
Quote from: IDA_ML on November 04, 2020, 11:09:51 PM
Can someone please give me a link to the latest EOS-M focus pixel maps?  Thanks.

Latest focus pixel maps:
https://bitbucket.org/Dannephoto/mlv_app_compiler-git/downloads/
#2
Interestingly, I've had no issues with an external monitor on the EOS M.

But I'm set to 25p in the Canon menu
And MCM review set to 14 bit, 25fps, 1/50 (for 180 shutter)

But without having to do any FPS override (as my experience has been the FPS override sometimes causes odd issues).


SO potentially, it is about the shutter being EXACTLY 180, that means there is a lack of pink frames with using external HDMI.

More testing, but it seems like a reasonable hypothesis.
#3
Quote from: Danne on June 13, 2019, 06:51:38 PM
If you can share a version also with 3x1 anamorphic and how you alter it it would cool.

So it's pretty straightforward for the 3x1 desqueeze.

The code is stored in tweaks.c, around line 3545 you'll see this:

.name = "Anamorphic",
        .priv     = &anamorphic_preview,
        .update = anamorphic_preview_display,
        .max = 7,
        .choices = (const char *[]) {"OFF", "5:4 (1.25)", "4:3 (1.33)", "7:5 (1.4)", "3:2 (1.5)", "5:3 (1.66)", "9:5 (1.8)", "2:1"},
        .help = "Stretches LiveView image vertically, for anamorphic lenses.",
        .depends_on = DEP_LIVEVIEW | DEP_GLOBAL_DRAW,


So we have to a) update the max number of options, and add one to the choices. So it would look like

.name = "Anamorphic",
        .priv     = &anamorphic_preview,
        .update = anamorphic_preview_display,
        .max = 8,
        .choices = (const char *[]) {"OFF", "5:4 (1.25)", "4:3 (1.33)", "7:5 (1.4)", "3:2 (1.5)", "5:3 (1.66)", "9:5 (1.8)", "2:1", "3:1"},
        .help = "Stretches LiveView image vertically, for anamorphic lenses.",
        .depends_on = DEP_LIVEVIEW | DEP_GLOBAL_DRAW,


so we've updated the menu, but now need to add the actual maths for the desqueezing.

if we goto line 2833 we see:

#ifdef FEATURE_ANAMORPHIC_PREVIEW

static int anamorphic_ratio_num[10] = {5, 4, 7, 3, 5, 9, 2};
static int anamorphic_ratio_den[10] = {4, 3, 5, 2, 3, 5, 1};


which is the array for how things get tweaked, so we just need to add another choice like this:

#ifdef FEATURE_ANAMORPHIC_PREVIEW

static int anamorphic_ratio_num[10] = {5, 4, 7, 3, 5, 9, 2, 3};
static int anamorphic_ratio_den[10] = {4, 3, 5, 2, 3, 5, 1, 1};



The only thing that I've found in terms of getting it to work on the liveview is you have to turn it to realtime and turn off the crop-rec preview.

@Danne, I'm going to have a play with the registers for the raw video size. I think I actually typo'd the dimensions for 4k 2.39:1. According to this site: https://blog.chameleondg.com/post/111891072017/resolution-aspect-ratio-cheat-sheet

it's 4096x1716, so we can probably adjust down the 3x1 to: 1366x1716 which will probably be continuous.

I'll also have a look at the register values for the MCM rewire and see what I can start to figure out, but I may come back with some more questions about what is going on. My knowledge of the EOS M registers is still very low, so it would be great to get some more pointers once I've had a dive in.

Cheers

#4
Quote from: aulden on June 12, 2019, 07:13:10 PM
For correcting the real time preview of the rewired anamorphic modes. It only goes up to 2:1, would it be hard to implement a 3:1 mode aswell?

I've previously compiled a version with a 3:1 anamorphic mode. It's pretty straightforward in the code.

The issue is currently that that rewired anamorphic mode is not showing the full height of the image. It feels like it's only showing approximately half of the 1866 height (of the 1488x1866 4k anamorphic rewired).

@Danne, I've been through your previous repository, but I couldn't find how the MCM rewired happens/takes place/is controlled or even if it could be. If you have any pointers for trying to rewire the full height of the 4k anamorphic mode that would be great.

We could then look to test a 3:1 anamorphic liveview mode (and see the effect on CPU/pink frames) or I have an external monitor which can be set to anamorphic desqueeze, so that could also be an option.

Another couple of questions/thoughts

At the moment I'm getting continuous - Orange marker for most of the record, then green for a portion. But records over 5mins (with a sandisk extreme pro). This is, obviously, AMAZING (props to you Danne)
But my thought is that 4k 2.39:1 is normally thought of as 4096x1728 - which means we *could* lower the res to 1365x1728

@Danne - again if you could point me in the direction (of the raw code) that controls the height/resolution on the preset that would be great

Then potentially if we can get the whole image rewired to the liveview in realtime, means we can then figure out the desqueeze.

Interested to hear your thoughts. Feels like this could be another (ANOTHER) big leap for the EOS M.

cheers all
#5
Hi Danne,

Got the latest build (11 April) and saw the 4K anamorphic rewire.

Just wondering if this preset was hooked up yet to get a real-time, proper framed preview.

I'm well aware that it's probably a long shot, but I got excited when I saw the preset name.

If it is hooked up, could you share some working settings as I could manage to get a good preview without framing on, which is similar to previous builds/presets.

Not trying to be demanding, just got excited by the name. If there's something to help test:try just let me know.

Thanks
#6
Quote from: geroinnn on March 07, 2019, 11:42:26 AM
P.s.
Is nobody else using an external monitor on this camera?

So I'm a couple of versions out of date (using crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Feb25.EOSM202)

But re: using an external monitor, and checking for corruption. I used the eos m with an Atomos Ninja Assasin (https://www.atomos.com/ninja-assassin) and it worked for displaying the signal and allowing for easier focus. No weird flickering etc etc. It still appeared to be a 480p signal, but I couldn't verify using the monitor as it was only a quick test.

Also, if I turned off Global draw the signal was clean enough to use the focus peaking in built into the monitor

For reference i was on the MCM rewire preset.

On checking the file, no corrupt frames. To be honest, it was probably the nicest footage I shot as I wasn't hunting for focus on a tiny screen.

I would assume the reason not many are using external monitors is because the monitor probably costs as much if not more than the EOS M.

Anyway, on to play with the latest build!
#7
So utilising crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Jan07.EOSM202

I manage to get both 50fps with mv1080 and the 4k-24fps.

With the 4k-24fps, I was getting a similar colour artefacts to Loknar. I.e. blue/yellow oddness. Seems to be concentrated around horizontal lines

Also overexposure or anywhere close gets pink highlights when exposure is brought down. Highlight reconstruction in MLVApp doesn't help, but Resolve highlight reconstruction does help, but only using MLVFS, which currently doesn't remove focus pixels.

Obviously preview is slow, but finding and maintaining focus is v. difficult.

With all that said, when you get the exposure right (ETTR) and grab focus the quality of the shot is excellent, but the horizontal artefacts are affecting things. Just want to be clear, I think it's Amazing to get 4k RAW out of a 6year old camera, but would like to get this to a great user experience so it could be used for actual project.s

50Fps seems to be working fine, with SD Overclock, I'm getting approx 10sec, but it was a bright scene, so I think that's what limits it due to data rate. But it looks good when slowed down to maybe 80/90fps in Premiere using optical flow.

I see that there is a Jan9 build, so will go on to try that and report back any findings. If MLVs would be helpful for the colour artefacting, just let me know

TA!
#8
Ah ha!

Adjusting the shutterspeed back to 1/50 means that it now appears to be working as intended.

Will have a play and report anything else that I find back.

cheers
#9
Disabling FPS override, definitely got me more usable liveview, but still lots of pink flashing.

I'll wait for Danne to upload the new build he mentioned, then give that a go!

#10
I imagine it's that I'm doing something wrong, but I'm not getting much joy out of the latest 4k 3x1 squeeze.

I *think* I have the settings all correct, but mine are below:

Any pointers as to what I have set wrong? All I'm getting is pink screen/static in LV, even when set to framing.

cheers








#11
Camera-specific Development / Re: Canon EOS M
August 08, 2018, 06:53:45 PM
Also this helps for general mv1080 setup this guide helps:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg204144#msg204144

I find that with 1736x1120 I need a write speed of 44.6 MB/s which requires the SD UHS hack to  get 40+ MB/s speeds

The Framing preview is now un-stretched which is great, but obviously still not in realtime (which would be grand).

I've had a couple of issues where pressing half shutter to go realtime means that the camera doesn't go back to more accurate preview.

There also appears to be a difference in the brightness of the accurate preview vs realtime preview.

The realtime preview appears to have accurate top/left/right framing, just the bottom say 15%. I'll try and shoot some charts to see if I can get an accurate read on it.

In terms of the actual shooting, the files are coming out without corruption. I've shot for approx 1min continuous, but will see what the max limit it.

MLV app takes the footage just find and reads the metadata correctly so isn't applying any transformation.

More tests to come, but it's looking pretty solid. The icing on the cake would be getting a more realtime, accurate preview for monitoring etc.

But overall, thumbs firmly up :)

More to come.
#12
Camera-specific Development / Re: Canon EOS M
August 06, 2018, 11:38:47 PM
@danne any chance of a build with the updated preview for testing purposes.

I've been using the various EOS M builds in 4K crop rec on steroids, but I'm really interested in making mv1080 with the full sensor usable.

Happy to help with reports/logs if I can.