T2i Magic Lantern for 550D in progress!
- Thread starter ...
- Start date
Is there a way to log the iso value that Auto Exposure uses instead of labeling the column with a 0? I ask because Auto Exposure can be convenient at times and I like to use Neat Video to clean up footage. Having that iso number would allow me to quickly choose the appropriate noise profile for Neat Video.
DorianVasco
Member
Hmm, on todays shooting with newest ml build, I found one of my shots recorded only with a low bit rate of approx. 15 MBit/s. The others are just fine (~45 MBit/s) and the bitrate setting was set to FW default.
Well, there was not much movement in the shot, but it was looking very blocky...
Well, there was not much movement in the shot, but it was looking very blocky...
M. Gilden
Canon DSLR Moderator
A1ex- I was just enlightened about another feature Canon decided to leave out of the T2i (however existent on all higher-end Canon cameras): AF Microadjustment.
I was complaining about the auto focus of my Tamron lens being a bit off, and was informed that the 7D, 5DmII, and even the older 50D, etc, all have the ability to calibrate the focus if your lens seems off.
(This is news to me, I'm not familiar with the feature)
According to this thread http://forums.dpreview.com/forums/read.asp?forum=1031&message=34491550 apparently some people saw it as reason to avoid the t2i entirely!
If I understand correctly, Magic Lantern has access to the AF system- do you think such a feature is possible to implement? It sounds to me like it could totally be a software thing, simply adjusting the focus point to be a few steps further or closer.
UPDATE: It is apparently not included on the 60D as well ( http://www.fredmiranda.com/forum/topic/930979 ). I assumed that since the 50D had it, all xxD models were supposed to have it. Strange- all the more reason to want to implement it into a common ML build for both cameras?
I was complaining about the auto focus of my Tamron lens being a bit off, and was informed that the 7D, 5DmII, and even the older 50D, etc, all have the ability to calibrate the focus if your lens seems off.
(This is news to me, I'm not familiar with the feature)
According to this thread http://forums.dpreview.com/forums/read.asp?forum=1031&message=34491550 apparently some people saw it as reason to avoid the t2i entirely!
If I understand correctly, Magic Lantern has access to the AF system- do you think such a feature is possible to implement? It sounds to me like it could totally be a software thing, simply adjusting the focus point to be a few steps further or closer.
UPDATE: It is apparently not included on the 60D as well ( http://www.fredmiranda.com/forum/topic/930979 ). I assumed that since the 50D had it, all xxD models were supposed to have it. Strange- all the more reason to want to implement it into a common ML build for both cameras?
Last edited:
DorianVasco: there's a small bug, sometimes it does not reset the bitrate properly. Will be fixed in next build.
Mordy: I know about it, and looked for it in 50D firmware, but I didn't understand yet what's going on. ML can only focus in LiveView (the method is different).
chrisegg: no idea how flashes work... I only use the built-in flash for 1% of my shots (with EV around -5).
CF01: well... I can read auto ISO value only a few seconds after half-pressing the shutter (after that it reports 0).
Mordy: I know about it, and looked for it in 50D firmware, but I didn't understand yet what's going on. ML can only focus in LiveView (the method is different).
chrisegg: no idea how flashes work... I only use the built-in flash for 1% of my shots (with EV around -5).
CF01: well... I can read auto ISO value only a few seconds after half-pressing the shutter (after that it reports 0).
Last edited:
Thanks for looking into it. Maybe log the iso value when AE Lock is done?
I'm trying to figure out how to do AE Lock while in Magic Lantern. I think I did it once though I don't remember what I did and I can't seem to locate it in the wiki.
DorianVasco
Member
A warning about that would be good, we did a load of shots today and I almost got a nervous breakdown, while watching it... the first few shots were awful. You should have seen the face of the director sitting beside me...
Luckily, the following, important shots were changed to high bit rate again.
Is it fixed with the actual build?
DorianVasco
Member
I recognized this issue too and thought it could be my sd card. But it is a Transcend 16gb class 10 and I remember, that I recorded successful at 60-70 mbit/s some time ago.
And I could record at 50Mb/s steady and now I get breaks (the video stops)
DorianVasco
Member
Hi, here a few notes about the new build May05.550d.fw109.NewLiveVLoop-fix after a few minutes testing.
+ nice and clean menu
+ false colour selection with pic
- toggle false colours is gone
- short cut sensor+zoom only activates the magic zoom (sensor + focus deactivates it, but a simple toggle like before would be handier)
- af rectangle is not removed (only after going to canon menu and back)
+ nice and clean menu
+ false colour selection with pic
- toggle false colours is gone
- short cut sensor+zoom only activates the magic zoom (sensor + focus deactivates it, but a simple toggle like before would be handier)
- af rectangle is not removed (only after going to canon menu and back)
Which build works better for high bitrates? I didn't change the algorithm, so maybe something is eating the CPU. How it works in the latest build?
False color shortcut is gone because users want it for zebra and focus peaking, too. So I thought it's better to create a profile with whatever you use, and toggle profiles instead.
AF rectangle: confirmed. Another workaround: press one arrow key, and it will disappear.
Shortcut sensor + zoom should toggle it, I'll see why this happens... maybe it's toggling it twice
Latest build here: http://groups.google.com/group/ml-d.../fd57110b660eea64?show_docid=fd57110b660eea64
False color shortcut is gone because users want it for zebra and focus peaking, too. So I thought it's better to create a profile with whatever you use, and toggle profiles instead.
AF rectangle: confirmed. Another workaround: press one arrow key, and it will disappear.
Shortcut sensor + zoom should toggle it, I'll see why this happens... maybe it's toggling it twice
Latest build here: http://groups.google.com/group/ml-d.../fd57110b660eea64?show_docid=fd57110b660eea64
robotsound
Well-known member
Hi Alex,
First of all, thanks so much for putting in all this work into Magic Lantern. I think I speak for the entire internet when I say that we really really appreciate it!
I just tried out the new magiclantern-2011May05.550d.fw109.NewLiveVLoop-fix.alex.zip release. I love the Live View Q toggle in play mode, that's a great addition. I think the ISO->DISP display toggle is a lot cleaner than it was before just pressing display.
I may have found a small regression in this new release. It seems the Canon focus square shows up sometimes and doesn't always go away again.
Steps to reproduce:
1) Turn on the camera in movie mode
2) Press the DISP button a few times to cycle through. The Canon focus square will show up when the Canon menus show up, but when the Canon menus go away again, the focus square remains.
Pressing the shutter halfway down doesn't get rid of it. Toggling the Magic Lantern menu on and off doesn't get rid of it. However, toggling the Play or Zoom buttons does get rid of it.
Also, I noticed in the last release (magiclantern-2011Apr30.550d.fw109.fixes.alex) that when I was paging through the cropmarks in the LiveView menu, they were not in any kind of order. I suspect they are just being read off the disk inside a readdir() loop somewhere without being sorted.
I downloaded the 550 branch of the mercurial repository to see about adding a little in-place sorting routine, but then it dawned on me that these frequent daily builds are coming from you personally and the source doesn't seem to be posted anywhere, at least as far as I can tell. From the looks of the official repository, the version of the code there only read a single cropmarks file out of the root directory of the SD card, so there weren't any data structures to be sorted there.
I guess this would either be a feature request for having the files be sorted in ASCIIbetical order (low priority compared to everything else you're working on), or if you could point me toward either the data structure format being used to hold the filenames or a more recent source code repository.
Thanks again!
First of all, thanks so much for putting in all this work into Magic Lantern. I think I speak for the entire internet when I say that we really really appreciate it!
I just tried out the new magiclantern-2011May05.550d.fw109.NewLiveVLoop-fix.alex.zip release. I love the Live View Q toggle in play mode, that's a great addition. I think the ISO->DISP display toggle is a lot cleaner than it was before just pressing display.
I may have found a small regression in this new release. It seems the Canon focus square shows up sometimes and doesn't always go away again.
Steps to reproduce:
1) Turn on the camera in movie mode
2) Press the DISP button a few times to cycle through. The Canon focus square will show up when the Canon menus show up, but when the Canon menus go away again, the focus square remains.
Pressing the shutter halfway down doesn't get rid of it. Toggling the Magic Lantern menu on and off doesn't get rid of it. However, toggling the Play or Zoom buttons does get rid of it.
Also, I noticed in the last release (magiclantern-2011Apr30.550d.fw109.fixes.alex) that when I was paging through the cropmarks in the LiveView menu, they were not in any kind of order. I suspect they are just being read off the disk inside a readdir() loop somewhere without being sorted.
I downloaded the 550 branch of the mercurial repository to see about adding a little in-place sorting routine, but then it dawned on me that these frequent daily builds are coming from you personally and the source doesn't seem to be posted anywhere, at least as far as I can tell. From the looks of the official repository, the version of the code there only read a single cropmarks file out of the root directory of the SD card, so there weren't any data structures to be sorted there.
I guess this would either be a feature request for having the files be sorted in ASCIIbetical order (low priority compared to everything else you're working on), or if you could point me toward either the data structure format being used to hold the filenames or a more recent source code repository.
Thanks again!
DorianVasco
Member
Hi Alex, the build 2011Mar31.550d.fw109.LCD-sensor-option seems to be better. While with the actual build recording with 60 mbit/s stops after a few seconds, in the Mar32 build there was no problem (one of the buffer marks every few seconds)