All kind time of day. Today, faced with the problem. when trying to use raw_rec or mlv_rec with FPS override on eos 700d crashes error DETECT RAW ERROR . eos 600d everything works fine. tried to change different USB drive, to no avail.
Modules Debug -> Show Console
Any errors there?
(http://pp.vk.me/c633629/v633629093/39cb4/AmMZ13UzVhw.jpg)
(http://pp.vk.me/c633629/v633629093/39cbe/i_1EuUOdPLA.jpg)
rolled on magiclantern-Nightly.2016Feb24.700D114.zip , everything works fine
Upload a silent picture from LiveView, taken with the old version, at the FPS override setting that causes the error.
then better rollback to the old version )))
on magiclantern-Nightly.2016Feb24.700D114.zip everything seems to be working stably
Without the info I've asked, I'm not able to fix the new version, sorry.
sorry . I do not know much English. working with a translator. Don't quite understand what I need to do.
Load the 'silent' module, enable it (simple mode, default settings), go to LiveView, enable FPS override at the setting that causes the error, press shutter halfway to take a picture and upload the DNG.
https://yadi.sk/i/_sGkYNqutQxKY
https://yadi.sk/i/yMTxDZVVtQxKc
... and take the lens cap off or turn on the lights ;)
https://yadi.sk/i/qFRFCjnGtQy5F
Was this at 2.5 FPS as in your screenshot? There's nothing wrong with it...
yes, was. silent in the mode of a photo works normally.
and problems begin with raw_rec and mlv_rec together with fps.
everything works for magiclantern-Nightly.2016Feb24.700D114.zip well.
I cant repeat that RAW DETECT error on my cam, I tried with both mlv_rec and raw_rec on at same time, also tried one at a time, tried with default ML settings and also added cropmarks, just not giving error, not sure why he is getting it? I was using latest nightly.
matter in that. that there is only an error of DETECT RAW ERROR.
and in a debager in a cycle lines run
black 5/5:.................................................................
on eos 600d everything works remarkably at the last night assembly.
whether there can be it the hardware problem? or it is improbable?
though everything works at old assembly normally
Please try to update the native camera firmware and reset the loader.
I was testing with new firmware and latest nightly ML build, not old one, and am not getting any kind of Raw Detect Error.
@mk11174: can you compile a version with this enabled in raw.c?
if (0) // change to 1
{
/* for debugging: if black check fails, save the bad frame as DNG */
That way, developerphp will be able to save exactly the DNG frames that are causing trouble.
Then after work, do a hard reset, update the firmware loader re-set and accomplish your goal on the results.))
Ok alex, will, do
https://bitbucket.org/mk11174/700d114/downloads/magiclantern-Nightly.2016Jul19.700D114.zip (https://bitbucket.org/mk11174/700d114/downloads/magiclantern-Nightly.2016Jul19.700D114.zip)
I would like to learn more. when updating nightly build to newer or vice versa if you need to update the boot loader in the camera or not?
maybe the problem is that have not updated it. Only updated files themselves.
at frame rates of 10 and above all works. but if the frame rate is below 7, the recording does not start.
no other errors.
with the assembly magiclantern-Nightly.2016Feb13.700D114 also noticed that if you set the recording speed of 2.5 frames per second, but the debugger frame rate is 11, and the error (DETECT RAW ERROR) no.
Video frame rate is also higher than for the debugger 11, to put the 10 settings.
If I correctly understood,
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.
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
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.
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
whether different hardware on my 700d and above?
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/#/ (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?
@developerphp: waiting for bad*.dng files obtained with this build:
Quote from: mk11174 on July 19, 2016, 09:14:10 AM
https://bitbucket.org/mk11174/700d114/downloads/magiclantern-Nightly.2016Jul19.700D114.zip (https://bitbucket.org/mk11174/700d114/downloads/magiclantern-Nightly.2016Jul19.700D114.zip)
through silent and make a photo throw you.
or a course of action?
(http://s33.radikal.ru/tempfiles/822ebe9f9eaa496ca4ba77e79501cdab/-88693455.jpg)
new assembly is not checked, the camera only in the evening to be with me.
Can you reproduce the error with the build from mk11174?
If yes, look on the card and upload these files.
yes I can.
Coming home from work and throw off files to the forum.
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.
(https://2.downloader.disk.yandex.ua/preview/5263e8650858ae7418f12e2e408be0165e21b9940e3db373db58c4c3dbf17a8f/inf/BdEjc2iVYHyqrSz4rvyhLNLPT2LeQjkSkgjgwRwlBGMh6aVnbWr3fEwCCkbmw4koJcI56dBjsew66Ux6eNrSsw%3D%3D?uid=0&filename=%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg&disposition=inline&hash=&limit=0&content_type=image%2Fjpeg&tknv=v2&size=XXL)
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.
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.
Please zip individual files.
https://yadi.sk/d/xOEVJxj3tUbSz
Bump. Sorry, can't download large files.
https://yadi.sk/i/OI0WdxJVtZpEY
https://yadi.sk/i/e1Uhf2KjtZpEa
https://yadi.sk/i/MTh8E8ETtZpEc
https://yadi.sk/i/XABuUkn9tZpEe
https://yadi.sk/i/mqJ7UMq7tZpEg
https://yadi.sk/i/DdXCfT9dtZpF5
https://yadi.sk/i/rn5vhrH3tZpFT
Looks like the black level check fails because of some hot pixels.
I expect this issue on most other cameras, not just 700D.
on canon eos 600d everything works fine in the latest firmware . is there any solution to this problem in the new assemblies ?
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.
today confirmed the operation of the new firmware, now everything works without oshibok.ogromnoe thanks for fixing the problem.
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 ...
Indeed, the issue was not fixed.
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.
I was wrong, the problem persists. in low-light bug is still there.
Hi there,
I don't want to open a new topic, but I have the same Error on my 50D when I want to shoot RAW in Crop mode.
As soon as I am in crop mode and hit the record button, it shows me the "RAW DETECT ERROR" stuff and the green RAW in the info bar on the bottom of the screen turns into a grey RAW.
RAW shooting in normal mode (not crop) works great.
I am running the "magiclantern-Nightly.2016Aug24.50D109.zip" firmware.
Cheers,
Kate
Good evening. I would like to know if there is still a problem with the black 5/5: stdev foo large (19394/100, ref 2577/100)
Yes, see reply #44.
Hi! Have anyone with acknowledge had the chance to look into this issue?
If there is anything i can test and/or upload just let me know :)