Author Topic: Canon 1100D / T3 (Read 1084271 times)

dmilligan · « **Reply #1075 on:** February 18, 2014, 01:38:23 PM »

Quote from: mad.eos on February 18, 2014, 01:19:49 PM

So... What is the sollution?

Finding the problem and fixing it. You can help find it.

Reset all canon settings, custom function settings, and ML settings (and disable all modules). Does it still happen? If not, then you should be able to narrow it down to a spefic set of settings and/or modules that are causing it. Start enabling things one by one until it happens. Please be as specific as you can, some small thing that you think is too insignificant to mention could be just the clue that a dev needed to diagnose/solve the problem.

If it still crashes with everything reset, try older builds and see if you can find one where this doesn't happen and then try to narrow it down to a specific build (use binary search).

mad.eos · « **Reply #1076 on:** February 18, 2014, 01:48:44 PM »

Okay!

Thanks once more, I'll try later on resetting ALL Canon and ML settings. Yesterday I just tried to reset the ML setting and the problem persisted. As I said, this only happens in Movie Mode.

mad.eos · « **Reply #1077 on:** February 18, 2014, 09:25:25 PM »

Found something kinda interssting. Shoot_malloc is the only one with 0 blocks allocated. Don't know if this helps or if it's normal. I've reset all settings and even uninstalled ml and installed again, still persists, am I the only one?

a1ex · « **Reply #1078 on:** February 18, 2014, 09:40:11 PM »

Show us the screenshot.

Yes, shoot_malloc is used as a last resort.

mad.eos · « **Reply #1079 on:** February 18, 2014, 09:54:22 PM »

Hi alex, we finally meet!

Screenshot not working :-( it hangs...

a1ex · « **Reply #1080 on:** February 18, 2014, 09:55:14 PM »

You may use a second camera in this case.

mad.eos · « **Reply #1081 on:** February 18, 2014, 10:10:45 PM »

Here we go!

Taken by our old sx100is

a1ex · « **Reply #1082 on:** February 18, 2014, 10:25:50 PM »

Ah, so the benchmark routine expects 2x16MB blocks, but you probably have only one.

I'd say limiting it to 8MB would have more chances to run the test.

mad.eos · « **Reply #1083 on:** February 18, 2014, 10:33:50 PM »

Sooo... It's dev time?

Will this solve the freezing problems? And also, have you ever detected a flashing white pixel in a video which was recorded with cbr mode at 1.2x ;-)

nanomad · « **Reply #1084 on:** February 18, 2014, 10:48:41 PM »

Does it freeze in movie mode with global draw OFF?

mad.eos · « **Reply #1085 on:** February 18, 2014, 10:57:01 PM »

Just tried it out, and yes, it freezes with global draw off as soon as I turn the camera off, shutter closes and screen freezes :-(

I've uninstalled ML for the time being, will be trying out everyday new Nightly Builds though

So still in the testing mood as allways, just don't want it to freeze on me in the field if you know what I mean

Cheers and keep up the EXCELENTE work!!

mad.eos · « **Reply #1086 on:** February 19, 2014, 04:30:15 PM »

While driving to work today, (as always I'm wonder about enoumerous things...) I was wondering...

Is it possible CPU/MEM wise for our 1100D (T3) to process a 3 to 6 Frame HDR Picture Automatically via some module? Am I speaking some impossible nonsense or... Is it really possible?

Example: Select module_autohdr
Choose from 3 to 6 Exposure intervals, Point, Shoot and Process and Voilá! A HDR RAW!

47Crows · « **Reply #1087 on:** February 19, 2014, 05:01:18 PM »

Quote from: mad.eos on February 19, 2014, 04:30:15 PM

While driving to work today, (as always I'm wonder about enoumerous things...) I was wondering...

Is it possible CPU/MEM wise for our 1100D (T3) to process a 3 to 6 Frame HDR Picture Automatically via some module? Am I speaking some impossible nonsense or... Is it really possible?

Example: Select module_autohdr
Choose from 3 to 6 Exposure intervals, Point, Shoot and Process and Voilá! A HDR RAW!

If I remember correctly, someone already asked this and the answer was something in the lines of: "we could, but we won't, because it's something you can do in post(-processing)"

However, anyone is free to write any module, so someone ought to get tired of manually creating HDRs.

That was for MAKING an HDR file. The auto-HDR sequence shooter (with frame number decider) already exists

.

a1ex · « **Reply #1088 on:** February 19, 2014, 05:16:11 PM »

You could implement the ZeroNoise algorithm, which is really easy (simply take the pixel from the brightest shot as long as it's not clipped). I expect it would take around 30 seconds or so on the camera (based on raw_diag processing times).

Or you could just batch-process with CeroNoice: http://www.magiclantern.fm/forum/index.php?topic=9581

mad.eos · « **Reply #1089 on:** February 19, 2014, 05:42:14 PM »

The main idea is to have a preview of the HDR Picture in the field without going later on, on the PC and Post-Process it. I don't mind doing PP, it's just to not have the kind of situation that you get home from a photo shoot, after PP you see one or two pictures and go "Damnn... I Should of..."

You guys know what I mean, I don't want to be lazy, just precise!

Do you guys also notice a white pixel flashing in video mode using the CBR method? $:-\$

dmilligan · « **Reply #1090 on:** February 19, 2014, 07:00:14 PM »

Quote from: mad.eos on February 18, 2014, 10:57:01 PM

I've uninstalled ML for the time being, will be trying out everyday new Nightly Builds though So still in the testing mood as allways, just don't want it to freeze on me in the field if you know what I mean

Just press SET on startup to not load ML

Have you tried older builds to see if there is one without this problem?

mad.eos · « **Reply #1091 on:** February 19, 2014, 07:04:10 PM »

Thanks for the tip dmilligan!

Will do!

How far should I go back? January? I'll try later on then and see if I can find which Nightly is the culprit, I'm just amazed that it only happens with me

Audionut · « **Reply #1092 on:** February 19, 2014, 07:04:51 PM »

Quote from: mad.eos on February 19, 2014, 05:42:14 PM

"Damnn... I Should of..."

Taken 2 exposures 4 EV apart and called it a day.

mad.eos · « **Reply #1093 on:** February 19, 2014, 07:15:08 PM »

Quote from: Audionut on February 19, 2014, 07:04:51 PM

Taken 2 exposures 4 EV apart and called it a day.

LOL! Good one Audionut... I have no argument to counter attack on that one!!

But, wouldn't it be nice to have a preview? It was just an idea

dmilligan · « **Reply #1094 on:** February 19, 2014, 07:16:55 PM »

Quote from: mad.eos on February 19, 2014, 07:04:10 PM

How far should I go back? January? I'll try later on then and see if I can find which Nightly is the culprit

If you do a binary search you should be able to go back 6 months and only have to check at most 8 builds.

Audionut · « **Reply #1095 on:** February 19, 2014, 07:26:44 PM »

Quote from: mad.eos on February 19, 2014, 07:15:08 PM

But, wouldn't it be nice to have a preview? It was just an idea

Not really. Raw histograms/zebras provide all of the exposure feedback needed. These don't lie. JPG based rendering on the LCD only looks pretty, it adds nothing useful with respect to exposure.

The highlight exposure is super easy, ETTR with raw based exposure feedback
The shadow exposure is simply a matter of increasing exposure 4 EV.

mad.eos · « **Reply #1096 on:** February 19, 2014, 08:42:07 PM »

Okay, I'll analyze carefully my silly me ideas next time ;-) anyway, I'll go back a few months and check if I can find the nightly culprit ;-) i have to ask this again, sorry, white pixel flickering using cbr movie method, anyone else?

a1ex · « **Reply #1097 on:** February 19, 2014, 08:52:01 PM »

Quote from: mad.eos on February 19, 2014, 08:42:07 PM

i have to ask this again, sorry, white pixel flickering using cbr movie method, anyone else?

Yes, I've noticed you are flooding with the same question 4 times.

mad.eos · « **Reply #1098 on:** February 19, 2014, 09:48:51 PM »

Sorry alex, felt that it kinda got lost in the middle there amongst other topics. 4x is a charme, sorry for the flood.

mad.eos · « **Reply #1099 on:** February 20, 2014, 01:29:32 AM »

Okay then, in an attempt of being some what productive, I can say that the Nightly build from February 1st down, doesn't freeze anymore. So, these problems may occur on more recent Nightlys! I'm staying with this one for the time being, startup even seems snappier and the whole "messing around" seems more stable!

Interesting facts:
.shoot_malloc now has 1 block and detects memory
.benchmark still shows shoot_malloc error (but who cares now that it won't hang anymore? still a fact though)
.screenshot works (yeeey)
.no freezes when I turn the camera off (got so happy I jumped up and "woohooed!")
.movie mode that I used was CBR @ 1.7x with a Cinema "effect" FPS @ 23.976

Video test can be viewed here:

Feast your eyes on ye' screen shot! arrg!

Edit: AND ... No flickering white pixel of death in movie! FWPOD be gone!!

PS: Thanks for everybodys Help! ML Back online for me!

News:

Author Topic: Canon 1100D / T3 (Read 1084271 times)