Messages

Double quote! ;-)

The May 4 build has this commit that should give a warning if you have the camera set to movie auto mode.

Quickly tested Nightly.2018May04.1200D102.
When switching on the camera, a message now flashes by to set Exposure=Manual. It is gone very fast, so I only noticed it the third time.

Would it be possible to show the message a bit longer? Might get annoying after a while so you'll have to decide if that's a good idea...

It almost worked -- the only exception was when camera started with Canon overlays enabled - in this case, you had to press INFO to perform a full cycling of the overlays.

Cycling through the different layouts using the DISP button (is that what you meant for the 1200D; it has no INFO button) doesn't help. The image as shown above doesn't show all the time; only when I use the wheel to change any of the parameters does the canon overlay appear, first on top and then behind the ml overlay.

@dterrahe - other than the Canon overlay issue, how is the camera handling? The auto exposure in movie mode issue should be resolved with the latest update.

Sorry; it is still not working with the 2018May04 update.

Apart from this and overlay, I haven't encountered other issues so far. I've started experimenting a little with dual iso and raw video. They work, I think, but I'll need to learn more to get a real benefit.

Isn't it working?

The screenshot was taken with the 2018May04 build, so I'm afraid it isn't working.

In LV, when I have the ML overlay active in picture mode, when I turn the wheel to change aperture, the underlying Canon overlay shows the changing settings and briefly clashes with the ML overlay, which also shows the same parameters.





I think this was discussed earlier in this threat but not sure if it was resolved for 1.0.1 or if there was a manual workaround.

Quickly tested Nightly.2018May04.1200D102.

Q key now works to get into and out of sub-menus. Thanks!

In movie mode with exposure=Auto, the trash key still doesn't work.

When switching on the camera, a message now flashes by to set Exposure=Manual. It is gone very fast, so I only noticed it the third time.

Took some screenshots.

These two are in Manual Exposure mode. The first after pressing Trash, which opened the menu.



And the second after using Trash twice to open the menu and close it again. This shows more of the event log.




And this one is in Auto Exposure mode. Pressing Trash doesn't do anything.

Does the auto exposure setting change the key codes? (in particular, the last digit)

Hard to see the key codes coming by when the menu does come up. When I close the menu again, I see the following codes in the Event log: 4c 61 61 d 11 f 34 (this is when Exposure=Manual). If the first 3 are what calls up the menu, then it is the same as when Exposure=Auto (i.e. that also gives 4c 61 61, but no menu).

Movie mode: see replies #449/450. Maybe it matters if you use manual or auto exposure?

Thanks for referring me to those replies; they are very helpful. Maybe at some point I'll read the whole thread...

I'm seeing the same keycodes that Fredestroyer007 reported: 4c 61 61

Also, pressing&holding Trash and then pressing SET gets me into the menu.

The exposure settings indeed has an impact on this, but it seems the opposite from the situation as described in #460; the menu key works on its own if I change the exposure setting to Manual, but if exposure is Auto (the default) then I have to press Trash+Set.

Other quick question; when in movie mode, should I still be able to open the ML menu by pressing the AV/delete key? That doesn't seem to work, but only in movie mode. In M/Av/Tv/P mode it works.

Or do I have to use a different way to get into the menu when in movie mode?

OK; if the "didn't work" part was meant just for the lua_fix builds from dfort, then it starts to make sense.

Can there be differences between the lua_fix build and the build you put on the main page in this regard?

I just downloaded yours and it exhibits the same (lack of) Q key behavior in menus for me.

Your report ("I don't think it has ever worked") contradicts previous reports.

I'm sorry I should have phrased that much much more carefully; I did not mean to give the wrong impression or create confusion. What I meant was that I don't think I have "ever" used the Q button for submenus. With "ever" being since I started helping Dan to get ML to run on the second hand 1200D with firmware 1.0.2 that I only bought a few months ago. I'd never used ML before, so I'm just starting to learn how it works and what it can do. What I meant was that I didn't want to imply that the Q button broke with the latest build or with the 1.0.2 firmware update, because I don't know if it used to work before. But since it seems from other reports that it did, my best guess would be the 1.0.2 update... But you probably should stop paying attention to me :-)

The puzzling part is that previous reports reference submenu options that could not be opened without the Q button. So, it must have worked. How did you guys open the submenus on earlier builds?!

It seems that, within ML menus, the PLAY button does exactly the same thing as the Q button is supposed to be doing. So people may have been using that? Or are there subtle differences/things that only work with Q?

Works here in QEMU. You will also need the Q key to enter most submenus (some sort of right-click).

Hm, I sort of thought that's what it was supposed to do, but I don't think it has ever worked.

If it still doesn't work, enable Debug -> Show GUI events, and write down the button code.

I'm getting two key codes for each press of Q: 4C and 1C

However, I now also saw in the menu that Q and PLAY do the same thing? I tested the PLAY button and indeed it does seem to open submenus and go back as required.

That sounds like you have Continuous AF activated. More information on this post.

No, I already disabled that (switched to "One Shot").

That's weird. Ok--time to clear out the Canon settings, make sure to disable Continuous AF and try the new "official" build. I'm removing the unofficial 1200D build on my downloads page.

I didn't change anything apart from the AF setting above after the last time I restored all canon and ML setting to factory/default.

But I'll install the new official build, clear all settings, try to remember AF and then run everything again. Oh, and fully charge the battery. And watch the screen to see if I'm required to press any buttons ;-)

Ran the full lua test of the new build.

It spend quite a long time on the focus test again; since I didn't have that much time this morning, I half pressed the shutter once, which helped it get past that point.

It was then seemingly happily running the exposures test, feeding it random values, but suddenly (before it had asked me to do anything) it rebooted. Got back to the main screen with an overlayed message saying the camera had been uncleanly shut down and module loading was skipped.

A question:
I haven't used ML on any other camera so don't know what I should expect/what works and how.
In many menu's, for example the benchmark menu, when descending into it, it shows top right a back arrow and Q ("<Q"). Does that mean I should be able to go back/up/out of the menu by pressing the Q key? That does not seem to work.

Only saw now you've got a new build up, so this was still run with the old one.

- bench.mo -> memory benchmarks (upload the screenshot)
- overall sanity check (for example, if you decide to take this build out and use it for a couple of hours, please report back)

Won't have time this evening, but will run bench soon.

If you'd read the London weather report, you wouldn't have suggested taking this build out. Unless it magically waterproofs the camera?

So on one attempt it failed the LiveView test and on the other attempt it failed the exposure test. Hum, those are the tests immediately before and after the lens focus test.

Nope, both times it passed all the tests up to and including focus test. Its just that the log file didn't record it. When it hung at the screen I showed the picture of, the log file still didn't show the focus test results even though I had seen it being completed successfully on the screen: the log was identical to the one for the first run that I posted. Maybe the file buffer doesn't get synced/flushed when the camera crashes hard?

AF was set to "AI Servo". I switched to One Shot and now the lens focus test passed. Yeah!

However, the first time I had left the camera running unattended after it passed lens focus to complete the remaining tests and later found it switched off, with the log cut off after

Code Select Expand

Testing module 'lv'...
LiveView is running; stopping...
Starting LiveView...
Overlays: Canon
Overlays: ML


I had seen it run through the lens focus module completely, so the results simply did not get saved.

On a second attempt, I saw it hang for a long time with this screen

. I had to pull the battery because it was not responding to anything. The log was cut off at the same point.

The test_camera_exposure function had previously run on its own when I had commenting everything else out, so it only seems to have a problem when running after all the other tests. Or maybe I had some setting switched on at the time that helped it out somehow.

BTW--Did the 1200D pass all of the other tests, including the ones that come after the lens focusing test?

Yep, I previously already ran all the other test (commenting out the three that were giving me trouble) so only the last, step 1, focus test is giving problems. I'm charging the battery now to see if I can run everything in one go and provide you with a clean log.

But to be honest, I'm not sure what the value is of knowing whether focusing with step 1 works, depending on the lens, if it takes many minutes. In my book, that means it doesn't work :-)

The lens is supposed to focus back and forth during this test; doesn't happen? The logs suggest it actually worked, to some extent, but got stuck at step size 1. Maybe it has to do with the mechanical condition of the lens.

You are right; it is moving, even with the very last iteration of the loops where it gets stuck. It just never reaches the exit loop condition, whatever that is. It does the same thing with two different lenses, one of which is basically brand new so I hope it is not already broken :-)

I do not see the text "Lens moving", that appears on the screen while the test is running, anywhere in the lua script, so don't know where that's coming from. Is that within an API call that doesn't return until a "1" (accuracy?) is reached? All the Step 1s work except the last one. Strange?

So it looks like the only remaining issue is with the lens focus test. I put on the 18-55 to see if that makes a difference. It just keeps running endlessly.

At the start it asks me to do a half-press; after that is there any further interaction required?

It seems to run fine, but is on a loop showing lines typically like:

Code Select Expand

Lens moving (0, 0)
Lens moving (11, 0)
etc


This goes on for at least 10 mins.

The log shows nothing interesting to me.

Code Select Expand

===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-4-29 08:10:45
===============================================================================

Testing lens focus functionality...
Focus distance: 760
Autofocus in LiveView...
Please trigger autofocus (half-shutter / AF-ON / * ).
19...18...17...16...15...14...13...12...Autofocus triggered.
Autofocus completed.
Focus distance: 760
Focusing backward...
Focus distance: 655350
Focus motor position: 620
Focusing forward with step size 3, wait=true...
.............
Focus distance: 250
Focus motor position: -1273
Focusing backward with step size 3, wait=true...
..........
Focus distance: 655350
Focus motor position: 650
Focus range: 13 steps forward, 10 steps backward.
Motor steps: 1893 forward, 1923 backward, 30 lost.
Focusing forward with step size 3, wait=false...
.....................................
Focus distance: 250
Focus motor position: -1263
Focusing backward with step size 3, wait=false...
.......................................
Focus distance: 655350
Focus motor position: 655
Focus range: 37 steps forward, 39 steps backward.
Motor steps: 1913 forward, 1918 backward, 5 lost.
Focusing forward with step size 2, wait=true...
.................................................................
Focus distance: 250
Focus motor position: -1303
Focusing backward with step size 2, wait=true...
..................................................................
Focus distance: 655350
Focus motor position: 658
Focus range: 65 steps forward, 66 steps backward.
Motor steps: 1958 forward, 1961 backward, 3 lost.
Focusing forward with step size 2, wait=false...
...
Focus distance: 250
Focus motor position: -1269
Focusing backward with step size 2, wait=false...
...
Focus distance: 655350
Focus motor position: 675
Focus range: 158 steps forward, 173 steps backward.
Motor steps: 1927 forward, 1944 backward, 17 lost.
Focusing forward with step size 1, wait=true...
...
Focus distance: 250
Focus motor position: 10888
Focusing backward with step size 1, wait=true...
...
Focus distance: 300
Focus motor position: 11582
Focus range: 14282 steps forward, 273 steps backward.
Motor steps: 10213 forward, 694 backward, 10907 lost.
Focusing forward with step size 1, wait=false...
...
Focus distance: 250
Focus motor position: 11192
Focusing backward with step size 1, wait=false...
...

In the above, the forum code has truncated the ..... lines; some are very long.

I reran the key test but now without pressing the shutter button (which previously I mistakenly thought I was asked to do). Passed fine now.

Code Select Expand


===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-4-29 08:04:15
===============================================================================

Module tests...
Testing half-shutter...
Half-shutter test OK.