Messages

Cool, thats what I needed!

And wait, this was from simple?

This is what you want to select if your doing it right, but whatever you did, gave you the correct text on screen and image at one point. You by chance try with and without Exp Override to see if you have more success, or with histo and waveform and other things off, just to see if you have better luck, I will need another test when I set the settings in new build to make sure they are correct.

Well that stinks 

Thanks for trying at least.

Is Image Review off by chance in Canon, if so, try making it anything but Off, like 2 seconds, or Hold.

hmm, weird, if you in Photo Mode and switch to Live View, and have your knob set to M so camera can be in Manual control, and your have your picture quality in Canon set to RAW, or RAW+jpg, or jpg, Just RAW, and try a shutter of say 1/10 and aperture whatever and iso at 100, this should work, just press half shutter once and release, still nothing?

If still dont work, I am not sure what the deal is?

I was actually thinking that would make it easier to control the updated test builds, but School is starting here soon, so my efforts will probably have to end at that point, which is why I might seem rushy trying to get testers to help out sooner rather then later in case noone else can come along in the future to work things out.

I don't know much more I will be able to do at this point since I don't have this camera, I really just wanted to get this full res silent picture just so I can finally get those Raw Photo skip values in as maybe one last final deed to tidy everything up, I hate knowing something so simple to fix is incomplete right now just cause of one picture, LOL!

I updated build, can you download it once more and see if you still get raw_error for full res silent picture?

If someone can please send me a Full Res Silent picture so I can adjust the settings to align focus and zebra in photo review mode.

Instructions, get build here: http://www.magiclantern.fm/forum/index.php?topic=12627.msg170329#msg170329

Enable silent.mo and restart camera.

Go to Photo Live view mode, and go in the silent feature settings and set top one to Full Res, make sure bottom is DNG.

Now make sure in Canon, Review is set to something other then OFF, so you can see it took one.

Now just aim, expose at something even lit, and half press shutter button, it will tell you it took one.

Send me that image please? Only way I can fix it.

Looks like I need to come in just a tad more on the skip values, can you send me a decent silent DNG, the one I had to work with was hard to check. I got as close as I thought, but may of had to chop off a few more.

Before this thread gets crazy, I dont want this issue to get lost, lets focus on this: http://www.magiclantern.fm/forum/index.php?topic=12627.msg170413#msg170413

Here is my recommendation : http://www.magiclantern.fm/forum/index.php?topic=12627.msg170424#msg170424

Maybe, depends on buffer though, if it doesn't hold many frames, I think it has to write faster to keep up.

Refer to this post about silent trigger test.
http://www.magiclantern.fm/forum/index.php?topic=12627.msg170427#msg170427

No idea exactly, but from the bench test it dont look any faster then 21mb/s most time seems to be worse. but no lower then 11mb/s.  Seems to be like the 1100D.

Formatting with Exfat didnt seem to help either, I just think the hardware is very limited on this one when it comes to recording raw frames, or because of low buffer to hold frames before writing.

Try silent picture, use End Trigger, how many are being held in memory while holding half shutter, if its less then 41, thats not good, it would mean you would not faster writing speed to make up for it I guess, and your bench test does not show very good speeds.

Give an example, on my T5i/700D I get 41 frames held in buffer while holding half shutter in End Trigger mode with silent pictures, my writing speed is around 40mb/s so I just reach the limit for 1280x720@24fps Raw Video. I also use 95mb/s card, so shows card has nothing to do with it, its all in the hardware. You can see mine is 16M from picture.

I would not even try 1728 res, the card writing hardware in camera is was to slow, Raw video might not really be fun at all with the camera unless your maybe doing low fps timelapse video.

But anyways, we would need more info, like were you using complete default settings of ML or did you disable any features or enable any features before or during using it.

You would need to try disabling features one by one and keep testing same way until crash hopefully stops, then if it does, turn on other features besides the one that made it stop crashing and try to see if maybe its a certain feature making it crash, or maybe one to many features loaded while using it.

This camera runs out of memory fast, so dont turn any modules on unless you need them, like mlv_rec mlv_snd, dual_iso, lua, ettr turn set all these to off in the modules menu if your doing raw_rec only.

Try lower resolution, Canon should be set to 1920x1080 24p in canon menu for best results, my tester recorded fine setting the res in Raw Video menu to 1280x720 and in the FPS override menu he was able to set that to 10fps and it recorded for a good while.

Test with and without Dual ISO.

Also inside Raw_Rec, try disable small_hacks option, try with and without, see what happens, try mlv_rec, see if that one works with more success.

Also, after a crash, go to debug menu and go to free memory, so if any errors there, maybe get screenshot of it.

Thanks for testing!

For any Developers: I have the correct Dialog Refresh address set at same spot 550D, 600D, and 700D have it set to. In case you were wondering.
Highlighted in pictures.

Yes, use the boot1200D.fir file if you have not done so already, then for whatever card you use, use EOScard utility to make card bootable, then install ML from the zip file onto card.

It does not have the regular FIR file like the main model cameras have that does it all.

Moved forward since you guys decided to anyway, want to make sure the right things get enabled so when bugs are reported, you will have a build that is known, you can't report bugs on a custom build if you want help because it will be to hard to know where bug came from if random things are enabled and disabled on each build.

http://www.magiclantern.fm/forum/index.php?topic=12627.msg170329#msg170329

For Dual ISO video to work, you need to define Property Request at your own risk, this will give you EXP menu, you will then need to turn on Exposure Override feature and set the ISO with ML to say 100, then DUAL ISO in video mode will work, it needs Manual control of ISO to work.

And if your compiling, did you enable the correct things in Internals? Everything in the Repo is up to date with the build in here, except I didn't add the modules for RAW Video or MLV because Raw Video was disabled in Internals until we got this build stable, also did not include Dual ISO module because it could not be used without Property Request defined because of needing manual control of ISO, but property request is the last thing you want to enable on the list.

As far as not enough memory, just undefine some of the stuff your not interested in inside all-features.h  undef them in your platform directory in features.h. This will help.

Also you can just remove some of the scripts from the Scripts folder, this will def help, just add one at a time until it runs out of memory, then take 1 or 2 out.

Yeah, thats what it is suppose to do, not load ML, it does but basically not the menu, he wanted to see if the bug was a memory thing, barely loading stuff to not use memory as much, then switching modes to try to make it crash, if it doesnt crash this way, but crashes when everything loaded, that would mean it was a memory thing.

He is trying to narrow the bug down this way.

But if you cant reproduce the issue while magic lantern is fully loaded, then its not going to help track bug down. So hopefully Mathias will test more, and see if its crashing everytime when he switches modes, only testing using latest version in this forum, not older ones or custom ones he might be compiling himself, only way to track this down if its really a problem.

Try fully loading ML with features, use MZ on and off, play with FPS a bit, then while in PHOTO Live view mode, switch modes like M, TV, AV, etc.. see if it freezes LV image, if so, go back, take battery out restart, try again, loading ML, testing MZ a few times, then switch modes again, if it doesnt Freeze, could mean its something with FPS feature, if it does freeze, the FPS is not the issue since you did not touch it this run.

The do this all again to see if its a MZ issue, this time load all features, plat with FPS feature, but not MZ, if it doesnt freeze, means its probably MZ, if it does freeze still, it means its neither MZ or FPS features, could be another feature loaded, try loading everything, except Histogram, play with MZ and FPS, etc.. keep doing this, taking one thing out each time until something stops it from freezing, thats how you will track down the bug. But none of it will help, unless its something that can be reproduced everytime.

If this turns out to be not an issue, I will start loading other things to get this port moving for testing of RAW and Dual ISO.

Yes, very possible could of been an old build with wrong LV address, not sure, or that buggy July 27th version, I have no idea what was up with that build, should not of been buggy like that.

Maybe if Mathias can confirm this, and all is fine now, I will move foward?

Anyone get to testing what Alex said to track Image freeze bug? Maybe once this bug is figured out, we can move on if no more complaints with the build as is.

Confirmed Raw Video, Silent Pictures, Exposure override, and Dual ISO all working and ready for testing once we get this Image Freeze bug worked out.

I did update the repo with all the things needed to get MLV_REC, RAW_REC and DUAL_ISO, for personal testing, but would be nice to publicly keep this port moving and get rid of these bugs.

My personal tester and I are on opposite sleeping hours, we have been testing the cooler features to keep you guys pumped about whats to come with the port.

But I will have to work on this bug with him as we get time to connect, but don't know how much free time we will get to do this.

So if anyone can please go through the procedure alex mentioned here: http://www.magiclantern.fm/forum/index.php?topic=12627.msg170362#msg170362  that will be great.

PLEASE UPDATE in as much detail as possible, videos are useful as well.

Just for anyone curios, my tester and I just found out, that once we turn on ML Exposure Override, you will have manual control of ISO in Movie Mode even when your Exposure control in Canon is set to Auto.

So you wont need to worry about the ML Menu once Exp feature is added, because you can just leave Canon set to Auto for Movie Exposure control which is the setting you can get into ML Menu on.

This way you just use ML to change your ISO in Movie Mode, and we confirmed settings are really changing the Analog ISO, not digital.

I did jot down the gui events for the differ modes, maybe it can be coded to work regardless of what mode your in, but at least once exposure override is added to your build, you will have Manual control and be able to access menu.

So this at least is not a bug, just the way its coded for now.

These are the values changing per mode in case alex would like to look?

Code Select Expand

Manual Exposure  Movie Mode
61  = 1010006/75006098/25500301
61  = 3010006/75006098/25500101
4c

Auto Exposure  Movie Mode
61  = 3010040/0/0
61  = 1010040/0/0
4c


Here is code in gui.h

Code Select Expand

#define BGMT_AV (event->type == 0 && event->param == 0x61 && ( \
(is_movie_mode() && event->arg == 0xa) || \
(shooting_mode == SHOOTMODE_P && event->arg == 0xa) || \
(shooting_mode == SHOOTMODE_ADEP && event->arg == 0xa) || \
(shooting_mode == SHOOTMODE_AV && event->arg == 0xf) || \
(shooting_mode == SHOOTMODE_M && event->arg == 0xe) || \
(shooting_mode == SHOOTMODE_TV && event->arg == 0x10)) )

I wonder if the button was set on purpose like this so it did not interfere with manual aperture control, cause if its set for ml menu, how would you control your aperture, so maybe it was done on purpose. These values are copied from 1100D.

OK Alex, for public version, I disabled that feature that was causing green tint, and will do so with any other feature reporting green tint bug.

That can be left for a developer with camera.

Go here for latest build with features that cause green tint disabled. Please report any other features that cause green tint to live view.
http://www.magiclantern.fm/forum/index.php?topic=12627.msg170329#msg170329

Also, is anyone having issues in any mode, opening the ML Menu, turn your Knob to every mode and test to see if ML menu opens and closes.

When you guys fully test this version and feel no more bugs, I can add silent pictures and raw video for more tests, my personal tester already confirmed they are working, but I want to be sure the bugs are free from this version before it moves onto something new.

And then eventually you can have EXP menu added for manual control of ISO in movie mode, which will also allow HDR video to work, because you need manual control of ISO to use HDR feature, which does work, already tested, I just dont want to add features when other bugs are being reported.

Or you can compile yourself from this repo: https://bitbucket.org/hudson/magic-lantern/commits/branch/1200D and test that way, which is great.

Ok thank you, you can ignore selftest Fails, see here :http://www.magiclantern.fm/forum/index.php?topic=12627.msg170221#msg170221

So, now, as long as MZ is good with not causing cam to crash or do weird things, then right now, the Tint issue is the PRIORITY!

Would like more confirms about MZ, Time and Peaking though, making sure its not gonna be one of those random, it works it dont work deals.

New Build Here: http://www.magiclantern.fm/forum/index.php?topic=12627.msg170329#msg170329

What about the ML Menu issue??? Does it open in all modes?

Ok, Good, so there was no problem, just need to have modules in the folder to have it show menu.

Good time is OK now.

Ok, lets start fresh.

Here is a build where I just fixed LV addresses and turned on MZ, it also includes Calender Stub Fix.

Also for public release, best to disable features that cause green tint bug, leave that fix for developer with camera. see here: http://www.magiclantern.fm/forum/index.php?topic=12627.msg170332#msg170332

Lets see how this build goes for a bit, check for that green tint issue and what alex asked a few posts ago, making sure things are aligned on focus peaking, and any other crashes.

Hopefully MZ works in this version and time is good, and maybe tint issue not happening???

1200D Build July 27 2016: Correct LV Buffer Addresses, Enable MZ, Calender Stub Fix, Disable FEATURE_LV_BRIGHTNESS_CONTRAST(green tint bug) and added selftest and bench modules.
https://bitbucket.org/mk11174/1200d_new/downloads/Latest_Build.zip
This is NOT the latest build anymore just to be clear, see Below at UPDATE:

Not going to update anymore until this version is 100% stable, or unless a bug is found and fixable. It gets way to confusing not knowing who is using what build when crashes happen.

Lets all confirm exactly what build you use when there is an issue, this way we can keep tracked of bugs.

Also, if you run selftest, dont worry about the 2 failing tests, ignore them for now, more details here: http://www.magiclantern.fm/forum/index.php?topic=12627.msg170221#msg170221

Thanks!


UPDATE! Since users are saying they cant reproduce live view freeze, I will move forward  for you to play, but please remember this is still a new port, Bugs must be reported in detail, any issues, turn off camera right away and take out battery and start over.

Also best to start with cleaned memory card, delete any old ML folder and bin file first so no conflicts with module linking happen.
https://bitbucket.org/mk11174/1200d_new/downloads/Latest_Build_July_30.zip

do u have any modules in the modules folder besides t5_101.sym file

If not copy the self_test or bench module from one of the other builds to it

When ur modules tab dissapeared, was it telling you a message about not shutting down properly, if so, just restart, it will not load modules after a crash.

And I would assume you should be able to load ML menu in all modes if working properly. But there is some new button code for this cam and 1100D because of the combine of Trash and AV, that might need some tweaking?

Figured, but does anyone know if it did anything for the clock in this new build with stub fix for Alex?

http://www.magiclantern.fm/forum/index.php?topic=12627.msg170290#msg170290

Hmmm, wonder what the heck happened to that July 27 one, I better get that off there.

I guess it didnt help ur green tint issue by chance right, lol?