Call for testers - as lately I've been hunting various bugs on this branch, and noticed some of the changes introduced model-specific issues (for example, api_test.lua was failing on 60D on one of the earliest tests).

For every single camera model available on the Experiments page (lua_fix build), please run:

- api_test.lua (upload the log)- selftest.mo -> stubs tests (upload the log)- 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)

Looks like there is a problem with the Menu/GUI stubs? Also looks like this camera has some nunchucks -- I mean num_chunks issues.

NICE work on digital zoom. I have tried this vision, and I find that I can‘t take a photo with the Movie crop mode. One more question is that once the white balance is adjusted, it can't turn back to auto, and when taking photos, the liveview will change. Hope trap Focusing mode will come one day.

I've been merging in the great work that Danne has been doing on the EOSM. Don't expect it to work on the EOSM2. However, there are some tools in the builds I'm posting on my downloads page that should help us figure it out.

Wow, 17 downloads for the January 4 test build and no user reports? I didn't even advertise that one.

I re-enabled raw histogram because several modules weren't building without that feature enabled. In addition, I had LiveView screen freezes even with the non-raw histogram. I didn't want to mess around with the default settings so you'll have to disable the histogram then restart the camera to keep the screen from freezing up right away.

So--what's working and what's broken? I've been testing the arkanoid module for hours (instead of doing anything productive) and it feels pretty solid. Any other reports?

I re-enabled raw histogram because several modules weren't building without that feature enabled. In addition, I had LiveView screen freezes even with the non-raw histogram. I didn't want to mess around with the default settings so you'll have to disable the histogram then restart the camera to keep the screen from freezing up right away.

I second that. Thanks for the pointers. Also noticed I must turn off the cam frequently (or sometimes go into canon menu and/or simply half pressed shutter) which can also do the trick. Strange as to be expected. Love the boat loads of Modules that are included. Especially the tools that can helps dig through. Thanks @dfort!

So--what's working and what's broken? I've been testing the arkanoid module for hours (instead of doing anything productive) and it feels pretty solid. Any other reports?

I went ahead and tried a bunch of MLV's (both uncompressed & lossless in varieties of bits) to my surprise that most if not all had certain rumbling effects of its own. Seems I had to turn off Camera after each recording to try and unfreeze the LiveView. Upon reviewing files within MLVApp I managed to get at least 1 or 2 clean footage until halfway through of the file is when the jumbling dumplings came back. Though none of the lossless seem to work well. Uncompressed seem to spit out OK until halfway through the file itself.

By after this point I decided just to put the card back in and try to run some self tests (the 15 minute one) which seem to get stuck during the "photo taken during recording" part even after letting it run for 15+ minutes to no avail. So then I decided just to try simple things first such as Silent Picture to see if I could pull off FRSP on this toy. As expected, Simple DNG (even Lossless) spat out fine while not with FRSP. Heck even the Intervalometer works w Silent Picture which is a plus.

You probably already know this but I get 'ISOless PH err( 8 )' message on the LiveView once I enable Dual-ISO (disable module and turn off/on cam fixes it) while I also notice that it keeps telling me I have set 12-bit lossless in crop_rec.mo even when I have it off. Is this to be expected?

More to come... It definitely feels cheerfully sentimental to at least be crawling back into the swaps to be with you guys once again.

I re-enabled raw histogram because several modules weren't building without that feature enabled. In addition, I had LiveView screen freezes even with the non-raw histogram.

LV did not freeze with (RAW) histogram enabled in photo mode for the nightly builds between 14th of Dec 2018 and at least 27 of Dec 2018, but it was freezing for the ISO research builds during this time interval. Yesterday I was loading the latest nightly build from January 7th and now LV is dead again with RAW histograms enabled (I cannot tell for the builds between 27/12 and yesterday, I was off there).

This part let us record raw without freezes but the content is gonna be noise only. Anyway, that's how far I got. One thing to test is enabling fps override and push tha A-timmer and see if that also fixes raw histogram freeze.

Checking with the various RAW_DEBUG options it looks like yesterday's "fix" didn't fix anything. I'm checking the results from the EOSM2 against the EOSM and found another problem that needs to be tracked down.

I don't know. Ran raw_diag and it looks good to me. At least compared to the EOSM.

EOSM2

EOSM

EOSM2

EOSM

With raw histogram turned on and in photo mode the camera starts normally, screen is drawn and then between 1 and about 40 seconds the screen freezes. Going into the Canon menu and back to LiveView will "unfreeze" it but will freeze again in about the same timeframe.

With the raw histogram disabled the LiveView doesn't freeze, this is what the console shows:

EOSM2

Enabling the raw histogram will freeze LiveView in photo mode. Both the EOSM and EOSM2 show pretty much the same information on the console:

EOSM2

EOSM

One thing that might be a problem is the small size difference of the LV raw buffer between these two similar cameras, 0x48798100 for the EOSM2 verses 0x46798080 for the EOSM in this test. In any case it seems to point back to what running RAW_DEBUG back in Reply #440 turned up where the EOSM2 showed an LV raw buffer of 0x8798100 verses 0x6798080 for the EOSM on that test.

I've been trying to track down the issue with the LiveView freezing in photo mode when the raw histogram is active. I discovered that switching from RAW in the Canon menu to one of the JPEG options (except RAW + L) it will not freeze but then again we need it set to RAW for simple silent stills (FRSP is not working). I found some different PREFERRED_RAW_TYPE addresses by using the RAW_DEBUG_TYPE option that didn't freeze LiveView but then it wouldn't save valid silent stills. Took another look at the console with RAW_DEBUG enabled and things are looking pretty normal now--I think:

Danne reported that in movie mode, mlv_lite enabled and raw recording on he also gets the LiveView freeze. He discovered that with global draw turned off, FPS override set to 24fps and Timer A pushed to (FT+30) it will actually record raw video. Whew--took me a while to follow that but I tried it with the latest test build and yes, it does work.

The LiveView freeze is really bugging me but it is working--or at least limping. That's where we're at on this. Any other reports? Any hints on how to debug this?

...One thing to test is enabling fps override and push tha A-timmer and see if that also fixes raw histogram freeze.

Getting back to this -- it is also working in photo mode. In other words, turn on FPS override, set it to 24fps and push timer A to (FT+30) and no more LiveView freezes.

A while back fps-engio.c intentionally failed to build on the EOSM and 1100D because the timer values needed to be tested. I'm not exactly sure how it is supposed to work but I looked up those discussions:

The final frame rate is still 24 fps, or a bit lower? If it's still 24 fps, then it doesn't make much sense (i.e. why specifically +30).

Not specifically +30. However pushing timer A by a lot will have the positive side effect of freeing liveview from freezing thus giving the space to record lossless. It´s not fool proof. It sometimes freezes anyway but it´s way better than the starting point which is a complete ice age.What could be related to fps override timers freeing liveview?

Edit: Added the 100D timers. Freezing liveview. Enabling fps override to 23.976 and looking at the a-timer and it´s on 528. Testing simply enabling this and pushing canon menu button frees liveview after about 3 seconds. Pushing timer-a to 588 and timer b will be at 2265 and now 24.027 fps and liveview stays free for a minute or longer.

I was merging in Danne's latest EOSM changes but because there were so many branches merged into my M2 experiments branch it turned out that this branch wasn't working properly with the EOSM. After lots of trial and error I finally got it working on the EOSM so now we should be in a better place to continue debugging the M2.