Author Topic: Canon EOS M  (Read 1124864 times)

ZEEK

  • Senior
  • ****
  • Posts: 300
Re: Canon EOS M
« Reply #4575 on: October 11, 2020, 10:42:43 PM »
Enable 24fps when ratio 2.39:1 and 2.35:1 and set 25fps are set(yes, aware of contradiction set 25fps becomes 24fps). Will only work with framing preview. Realtime liveview will be frozen or else pink frames.
Thanks Danne, this is actually an amazing option for stills, cheers 😎👌🎥🔥
EOS M - EOS M2 - 5D2

bern047

  • New to the forum
  • *
  • Posts: 10
Re: Canon EOS M
« Reply #4576 on: October 11, 2020, 10:45:25 PM »
I have Canon 700D and Canon EOSM, 240mhz works fine on the 700D but I can only use 195mhz max on the EOSM, both cameras have similar processors and sensors which is fine for me as I can get all the settings and resolutions with the latest build so more than happy with both cameras

fer.psd

  • Just arrived
  • *
  • Posts: 1
Re: Canon EOS M
« Reply #4577 on: October 12, 2020, 09:16:53 PM »
I'm desperate...New EOS M ML user here, installed FD Lenses with the Pixco adapter, everything looks great on the viewfinder, settings, aperture changes etc....but when I hit the Red Dot Record Button NOTHING HAPPENDS... no recording. Anything that might help this newbie out?

ZEEK

  • Senior
  • ****
  • Posts: 300
Re: Canon EOS M
« Reply #4578 on: October 13, 2020, 10:28:12 AM »
There is a known issue on the EOS M, especially with the Latest Build [OCT,07]. When using HDMI with a monitor, the EOS M LiveView/Monitor Screen tends to "Lockup" or freeze after exiting the Canon or Magic Lantern Menu. A Reboot is required each time. Not sure what is causing this freeze in LV.
EOS M - EOS M2 - 5D2

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6968
Re: Canon EOS M
« Reply #4579 on: October 13, 2020, 10:39:02 AM »
There is a known issue on the EOS M, especially with the Latest Build [OCT,07].
Can´t really work wiith this info. If it´s known it´s new to me. The official build works better? Why especially with this build? What preset was used, how can we reproduce the issue. How can you avoid the issue? What presets are working better etc.

ZEEK

  • Senior
  • ****
  • Posts: 300
Re: Canon EOS M
« Reply #4580 on: October 13, 2020, 12:29:07 PM »
It happens in all presets, no presets work better than the other. Avoiding the issue would be to not use an external monitor in general, otherwise just live with rebooting the camera after exiting the ML Menu to fix the freeze. The issue will reproduce with any preset used and after exiting the ML Menu. Haven't encountered this in the last build with HDMI or the few previous builds. It's not a Huge deal as I don't use a monitor as often, just thought I'd raise this concern thinking what the issue could be.
EOS M - EOS M2 - 5D2

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6968
Re: Canon EOS M
« Reply #4581 on: October 13, 2020, 12:36:29 PM »
Don't think older builds works better. If so it would be good if you could present these two builds compared. Would be good also to test against an official build but right now there's simply too many variables not tested to draw any conclusions.
On a general level, thanks for feedback. If we want this fixed more work is waiting...

Kgncom

  • New to the forum
  • *
  • Posts: 18
Re: Canon EOS M
« Reply #4582 on: October 14, 2020, 07:29:33 PM »
Heya Danne, is it possible to enable the customized button functions in picture mode? Changing iso without going through touch menus is something I didn’t know I needed!
70D | EOSM

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6968
Re: Canon EOS M
« Reply #4583 on: October 14, 2020, 08:34:40 PM »
Yes, I was interested in this too but not a big priority and now I have no time.

canoneer

  • New to the forum
  • *
  • Posts: 37
Re: Canon EOS M
« Reply #4584 on: October 15, 2020, 06:09:04 PM »
Re Remote triggering the EOS M. I have way back in time managed to get the Triggertrap Audio remote function to work. Now I can see the volume peek when triggering on the iPhone but it seems impossible to get a reaction. Do I need to do more than activating the function in the ML menu? If you have time to throw a lifeline?

0xanon

  • New to the forum
  • *
  • Posts: 5
Re: Canon EOS M
« Reply #4585 on: October 16, 2020, 03:41:58 PM »
New user with a few questions:
  • Scott Torborg used to have an EOS-M teardown gallery at https://www.scotttorborg.com/canon-eos-m-teardown but it is no longer available. Does anybody have the high-res images?
  • Does anybody know if the SD card controller on the EOS-M is a separate chip from the main CPU or MPU? Is the touch screen controller a separate chip? What about other EOS cameras?
  • I've read the EOS cameras can go into thermal shutdown from heavy usage outside the specs, such as shooting raw video with ML and overclocking the SD controller. What chips are getting hot and causing the overheating?

Walter Schulz

  • Contributor
  • Hero Member
  • *****
  • Posts: 7616

0xanon

  • New to the forum
  • *
  • Posts: 5
Re: Canon EOS M
« Reply #4587 on: October 16, 2020, 04:27:56 PM »
Thank you, but I did check archive.org before posting, and none of the full resolution images (the useful ones) have been archived, and only very few any of the medium res ones.

I also emailed Scott Torborg, with no response.

Walter Schulz

  • Contributor
  • Hero Member
  • *****
  • Posts: 7616
Re: Canon EOS M
« Reply #4588 on: October 16, 2020, 04:51:30 PM »
Have you tried Twitter? https://twitter.com/storborg

0xanon

  • New to the forum
  • *
  • Posts: 5
Re: Canon EOS M
« Reply #4589 on: October 16, 2020, 04:54:26 PM »
Oh you young whippersnappers and your electric restroom wall, of course I haven't!

Guess I'll have to swallow my pride and make an account, thanks for the tip  :)

Walter Schulz

  • Contributor
  • Hero Member
  • *****
  • Posts: 7616
Re: Canon EOS M
« Reply #4590 on: October 17, 2020, 12:42:42 PM »
I'm desperate...New EOS M ML user here, installed FD Lenses with the Pixco adapter, everything looks great on the viewfinder, settings, aperture changes etc....but when I hit the Red Dot Record Button NOTHING HAPPENDS... no recording. Anything that might help this newbie out?

Try manual page 287: C.Fn-7 Release shutter w/o lens.

Janke

  • Freshman
  • **
  • Posts: 79
Re: Canon EOS M
« Reply #4591 on: October 17, 2020, 05:01:29 PM »
I'm desperate...New EOS M ML user here, installed FD Lenses with the Pixco adapter, everything looks great on the viewfinder, settings, aperture changes etc....but when I hit the Red Dot Record Button NOTHING HAPPENDS... no recording. Anything that might help this newbie out?

As Walter says, use the C.Fn-7 Release shutter w/o lens setting.

It is factory set to "off", meaning that you can't either without a lens, or with a lens that doesn't have the necessary electric contacts. According to eBay pictures of the adapter, it doesn't have the contacts.

This has nothing to do with ML at all...

theBilalFakhouri

  • Contributor
  • Hero Member
  • *****
  • Posts: 543
  • I am not active currently
Re: Canon EOS M
« Reply #4592 on: October 17, 2020, 09:17:30 PM »
Some EOS M users reporting flickering problem when using Dual ISO in 2.5K and other presets on MLV RAW ON EOS M Facebook group

I had this problem too in the past on 700D, it was from the generic code for ADTG registers, some ADTG registers present in 700D, EOS M which changes from video mode to another, a1ex included it because his graphs was showing it should change when increasing RAW resolution, using these registers or not using it *doesn't have any effect* on 700D and EOS M, I marked it as unnecessary registers for these cameras, why?

Because it's causing the flickering problem when using Dual ISO, I thought this problem was from some shutter blanking issues or the heavy 100/3200 Dual ISO, or even MLVApp, fortunately I made some tests in the past and narrowed down the following ADTG registers which caused this strange flickering problem, after commenting out these registers the flickering gone:

Code: [Select]
        //adtg_new[7]  = (struct adtg_new) {6, 0x8173, nrzi_encode(fps_timer_b - 1) }; /* PowerSaveTiming OFF (6D/700D) */
        //adtg_new[8]  = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 1) }; /* PowerSaveTiming OFF (5D3/6D/700D) */

        //adtg_new[11] = (struct adtg_new) {6, 0x82F8, nrzi_encode(readout_end + 1) }; /* ReadOutTiming */
        //adtg_new[12] = (struct adtg_new) {6, 0x82F9, nrzi_encode(fps_timer_b - 1) }; /* ReadOutTiming end? */

Some days ago I found there is another flickering problem when using Dual ISO in 1x3 Binning mode with real time correct preview @ 2.35:1, 2:1 and 16:9 Aspect ratios, not sure what causing this flickering in these presets But in 1x3 Binning 2.50:1 preset with real time correct preview there is no flickering, something is happening here when lowering width RAW resolution and increasing Vertical RAW resolution in x5 mode, I think some registers related to horizontal resolution or vertical resolution or both need to be tweaked

Tested Dual ISO in 1x3 Binning 2.35:1 preset in mv1080 mode with stretched preview, the flickering problem isn't there (it's gone), some registers here appear to control something which cause this problem, these registers are between x5 and mv1080 mode, happy catching

Some examples from EOS M users posted on the Facebook group:
https://www.youtube.com/watch?v=gnHAF1qKLhs
https://www.youtube.com/watch?v=xuZqeGWCL6k

You can see the flickering problem clearly in my old 2018 video, I was testing 1x3 Binning mode with Dual ISO:
https://www.youtube.com/watch?v=QmawA6qe-Dc

Edit: here is my old reporting for this problem:
https://www.magiclantern.fm/forum/index.php?topic=19300.msg207717#msg207717

..It's some kind of flicker(Low contrast frame/High constrast frame something like that) I thought it was from shutter speed bug or aggressive 100/3200 Dual ISO but using same Dual ISO and without crop_rec the problem is gone. That's how I found the problem wasn't from Dual ISO and shutter speed bug (shutter speed was set to lowest value so no flicker was happening) then I tried to comment out other ADTG registers and the problem has been fixed.

I didn't search to find out which specific ADTG registers causing this but the point is not to use unnecessary registers for all cameras maybe that isn't good thing. For small cameras (700D, 650D, 100D and EOS M) the necessary ones is 8172, 8178 and 82b6. I don't have my cam and laptop right now posting examples next week.
700D 1.1.5 | no more ISOless LV err 8 / SDR104 @ 240 MHz - Constant! | Fixed Scrambled LiveView in Higher resolution | Real-Time correct framing in the Way

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6968
Re: Canon EOS M
« Reply #4593 on: October 17, 2020, 09:35:11 PM »
1 - Check out Levas findings here:
https://www.magiclantern.fm/forum/index.php?topic=15088.msg226690#msg226690
2 - Do not process dualiso with Mlv app. Why. Code ported is old mlvfs code causing subtle bugs like flicker etc.
3 - Compile cr2hdr version from here with latest changes from a1ex code is used in Switch. Proven working https://www.magiclantern.fm/forum/index.php?topic=7139.msg227989#msg227989
Source
https://bitbucket.org/Dannephoto/magic-lantern_jip_hop_git/src/master/

Too bad these very hard to detect bugs have been coming and going totally made me, and probably others, leave the dualiso train when it comes to movie files. I think it would have been much more interesting still if we kept using a1ex version from the beginning.

theBilalFakhouri

  • Contributor
  • Hero Member
  • *****
  • Posts: 543
  • I am not active currently
Re: Canon EOS M
« Reply #4594 on: October 17, 2020, 09:47:18 PM »
Cool, so it might be only MLVApp problem after all that?!

I will make tests with cr2hdr to prove or not prove that since I dealt with these problems from two years ago
700D 1.1.5 | no more ISOless LV err 8 / SDR104 @ 240 MHz - Constant! | Fixed Scrambled LiveView in Higher resolution | Real-Time correct framing in the Way

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6968
Re: Canon EOS M
« Reply #4595 on: October 17, 2020, 10:35:38 PM »
Well, you need white level coherency through all files since it could vary depending on how cr2hdr converts every single file. This step is done with exiv2 in Switch.

sm105

  • New to the forum
  • *
  • Posts: 28
Re: Canon EOS M
« Reply #4596 on: October 18, 2020, 03:17:05 AM »
I've had strong flickering issues when using dual iso on the 5D3. I did try using Switch, as recommended by Danne, but the resulting files still had flickering. I should note that I was filming the full moon when it was high in the sky (very bright!), so when exposing for the moon (ISO 100), the rest of the shot (city buildings) was underexposed by at least 3 or 4 stops at ISO 1600.

In another thread a1ex hints that dual iso is not ideal in very underexposed shots (https://www.magiclantern.fm/forum/index.php?topic=24216.0).

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6968
Re: Canon EOS M
« Reply #4597 on: October 18, 2020, 07:12:14 AM »
Could you post a sample from that file? I filmed the moon and I think if exposed correctly it will also work. It did in my case.

70MM13

  • Senior
  • ****
  • Posts: 485
Re: Canon EOS M
« Reply #4598 on: October 18, 2020, 12:45:04 PM »
the attachment i provided in the original issue reported (and linked above by sm105) is still valid...

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6968
Re: Canon EOS M
« Reply #4599 on: October 18, 2020, 12:59:26 PM »
a1ex already pointed out this was not recorded with 14bit. Error starts there...