canon eos 700d RAW DETECT ERROR

Started by developerphp, July 18, 2016, 10:28:41 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

mk11174

If I were you, I would start fresh, format card on PC, restore CANON factory settings, then try newest nightly and update firmware again just to be sure, but that part should be fine since its clearly loading your autoexec.bin file. But you need to run firmware update anyway to make card boot once formatted.

But see how that works first.

Because I am from US, tried exactly what you did while NTSC, then saw you use PAL, so I tried PAL, I cant get it to do that error, or any error.
500D/T1i  550D/T2i  600D/T3i  700D/T5i

developerphp

all did, to no avail. Problem If only I then can close the topic, I will shoot on canon eos 600d

I did a firmware update, sblos. nothing helped

mk11174

Ok, so u say an old version works, why not go back and download and try each version after the good one, until you start getting error,  that will make it much easier to figure out because we can then see the changes made that may have caused it. But you need to look at every version up until it starts. Maybe to go quicker you can start by skipping every 5 builds, then if error happens work your way backard.

Also, what modules are you loading with mlv_rec,  do u have any other modules enabled and what other settings have you changed from default.
500D/T1i  550D/T2i  600D/T3i  700D/T5i

developerphp

all I tried to standard settings only raw_rec or mlv_rec.

on Date: 2016-02-13 04:12:35 +0300 there were no errors, but the frame rate at a value of 2 frames per second 11 frames vseravno remained on the debugger.
I come home, check it later.

and I wanted to find out what these words mean in the cycle?

black 5/5: stdev foo large (19394/100, ref 2577/100)
black 5/5: stdev foo large (19394/100, ref 2577/100)
black 5/5: stdev foo large (19394/100, ref 2577/100)
black 5/5: stdev foo large (19394/100, ref 2577/100)
.................................................. ......

as soon as this begins the cycle, after which the error occurs (DETECT RAW ERROR)

loop occurs when setting the value 8azy and below.

such vchechatlenie that is a ban on below 11 fps.


h 264 writes properly without errors

developerphp

whether different hardware on my 700d and above?

mk11174

You said earlier that FEB 24 was working, you rolled back to it? Now you say FEB 13 works as the latest, I need you to go here https://builds.magiclantern.fm/#/ select the 700D.114 for your camera and choose Show older builds. At the top of list is the newer ones of course, I need you to find the newest one that works without error. I dont even see one in the list that matches your date and time. This is really important to find the newest one that you can use without error so we know the exact build that the error starts?
500D/T1i  550D/T2i  600D/T3i  700D/T5i


developerphp

through silent and make a photo throw you.
or a course of action?

developerphp



new assembly is not checked, the camera only in the evening to be with me.

a1ex

Can you reproduce the error with the build from mk11174?

If yes, look on the card and upload these files.

developerphp

yes I can.
Coming home from work and throw off files to the forum.

developerphp

Good day to all. I'll start from the beginning.
1. take off your bad files https://yadi.sk/d/u_RDmldQtUJpR
2. assembly magiclantern-Nightly.2016Apr11.700D114.zip no errors, and since Date: 2016-04-12 03:12:20 +0300 fly error.

3. have a lead. If the scene is bright, everything works just fine. But if the light cycle appears in the frame is small, the debugger and the error takes off
black 5/5: stdev foo large (19394/100, ref 2577/100)
black 5/5: stdev foo large (19394/100, ref 2577/100)
black 5/5: stdev foo large (19394/100, ref 2577/100)
black 5/5: stdev foo large (19394/100, ref 2577/100)

once in the frame appears more light, the error disappears.


developerphp

in magiclantern-Nightly.2016Apr11.700D114.zip firmware do not appear line black 5/5: stdev foo large (19394/100, ref 2577/100)

and it works in all lighting conditions.

a1ex



a1ex

Bump. Sorry, can't download large files.


a1ex

Looks like the black level check fails because of some hot pixels.

I expect this issue on most other cameras, not just 700D.

developerphp

on canon eos 600d everything works fine in the latest firmware . is there any solution to this problem in the new assemblies ?

a1ex

The solution requires robust estimators for black level and noise (for example, median and MAD instead of mean and stdev) in autodetect_black_level_calc (raw.c). Any help regarding their implementation is welcome.

developerphp

today confirmed the operation of the new firmware, now everything works without oshibok.ogromnoe thanks for fixing the problem.

Walter Schulz

I'm a little bit confused. As far as I can "decipher" change logs there was no change for autodetect_black_level_calc in raw.c ...

a1ex


developerphp

interesting. today I come home from work one more time to test the new firmware and the old. On the results will unsubscribe. A few hours today tested the new firmware. everything works fine.

developerphp

I was wrong, the problem persists. in low-light bug is still there.