Here we will concentrate our efforts to port raw video recording to 550D, and continuously making it better and better !
Current 550D with RAW video builds (older ones are first, newer ones are the last towards the bottom of this post) :To install: install the latest ML stable version, then substitute (overwrite) the files into the card with these
--------------------------------------------------------------------------------------------------------------------------------------------------------------
MK11174The main thing is the ability to save RAW settings after restart.
Includes Magic and Tragic as well and Mem fix.
Anyone having hard time deciding which record module they like best out of Magic Unified vs the Tragic version, this will help you.
You will have 2 new option within Magic Lantern.
When you decide which you like best, just delete the other module or just keep both, your choice.
Obsolete link removed - Please use the official nightly builds //Audionut--------------------------------------------------------------------------------------------------------------------------------------------------------------
MK11174Anyone wanting to try out Alex's experimental variable buffer Raw Record, this build is all updated and has AUTO ETTR, File Manager and Pic View Module as well.
Obsolete link removed - Please use the official nightly builds //Audionut--------------------------------------------------------------------------------------------------------------------------------------------------------------
MK11174Alex disabled debug code and added a bit more speed as it says on the changeset.
Obsolete link removed - Please use the official nightly builds //Audionut--------------------------------------------------------------------------------------------------------------------------------------------------------------
MK11174Latest changes to everything. Includes modules, Raw_Rec, File_Man, Pic_View and ETTR, oh and a requested res of 1200 and aspect 2.42:1
Obsolete link removed - Please use the official nightly builds //Audionut--------------------------------------------------------------------------------------------------------------------------------------------------------------
REWINDraw_rec module from pravdomil's source:
https://bitbucket.org/pravdomil/magic-lantern-hack/commits/allRaw_rec has some tasty features like black bars and auto global draw off while recording.
I've noticed a tiny but consistent frame count increase with this. For example, with my previous build i've got about 500–510 frames with 1200x496 at 24 fps, now i'm getting 550-570.
Also, there is a small present for those of you, who dare enough to shoot the tv works on 550d — nice 3X4 cropmark (useful for PAL world ).
Other stuff is from unified.
Notice: I have removed a large set of resolutions (useless for my works), and added 1200 and 1.42:1
This build also includes ETTR, file_man, pic_view.
Thread about this module :
http://www.magiclantern.fm/forum/index.php?topic=5655.msg0#new--------------------------------------------------------------------------------------------------------------------------------------------------------------
MK11174Incredible milestone: all the previous raw stuff, plus the DUAL ISO feature for PHOTOS AND VIDEO !
Obsolete link removed - Please use the official nightly builds //AudionutCurrent state-of-the-art :Problem : Raw video recording works, finally ! Now we need to try to get more Buffer Memory like the other cams, even the 500D has 95Mb, while 550D only 75Mb as current development (68Mb was the memory available at the beginning of this development). With 500D, one gets higher res than on 550D, with no skip, thanks to the expansion of this memory.
You can see the status from the "0101" menu in ML : scroll down to "Free Memory", then press "Set" button on 550D and you will see the "shoot_malloc total" is 75mb : that needs to be al least 95mb (better if more, obviously). On 500D, this memory is native 95mb, without any intervention... we cannot understand why...
What to do :[1] It seems we must enable sRAW option, but while on other cams it works, on 550D and EOSM it gives a "err70" error (
http://www.magiclantern.fm/forum/index.php?topic=1746.msg6039#msg6039) that bricks the camera (can be un-bricked, however). We have to solve this problem.
[2] Some hints of past tryouts can be found here :
https://groups.google.com/forum/?fromgroups#!msg/ml-devel/AyPANkaXbp0/PMwkzwuVy14J[3] There are clues that, in order to make room for the raw_video_rec module, we used the shoot_malloc memory to put there the ML code, so shrinking it, so we cannot have more shoot_malloc memory anymore... look at this :
http://www.magiclantern.fm/forum/index.php?topic=5071.0[4] Anyway, the source file to play with about this thing, is: src/exmem.c
[5] Without using sRAW option, %1 user managed to expand (even if by very little) the shoot_malloc memory by using this system : This is where he got more memory.
https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/commits/60b04d7254cf8c5add9ee4a96822a1a7c81e1503[6] Following point [5], we can play with these values :
https://bitbucket.org/hudson/magic-lantern/commits/39d536e2b72c39b81855526fbd08f4281931ccbb[7] exmem.c - line around 147 -
hsuite = shoot_malloc_suite (max_size + backup_size - 8 * 1024 * 1024)
in this manner, the old version, we obtain 68Mb of shoot memory, good to serve as buffer for raw video (more memory, more resolution)
-----------------------------------------------------------------------------------------
hsuite = shoot_malloc_suite (max_size + backup_size - 1024 * 1024)
in this manner, the new and current version, we obtain 75Mb of shoot memory
-----------------------------------------------------------------------------------------
Our goal is to raise this shoot memory as high as possible, at least the 95Mb of 500D, but the maximum I managed to obtain is :
hsuite = shoot_malloc_suite (max_size + backup_size)
in this manner, we can have 76Mb of shoot memory
If you try even a :
hsuite = shoot_malloc_suite (max_size + backup_size + 1024 * 1024)
the result is 0 of shoot memory !
However, the interesting thing is that the autoexec.bin memory is not affected by the increase of the shoot memory.
-----------------------------------------------------------------------------------------
I have hitted a wall here...
[8] - Modifying the "backup_size" (by upsizing or downsizing it), doesn't sort any effect at all.
- Changing the probe size from 4 to 2 and then to 1 (just to dig out more memory chunks), doesn't sort any effect at all.
- Forcing "size" to zero into the shoot_malloc allocation function, just to force it to allocate the maximum size, takes the camera to stack
overflows and freezes that need to pull out the battery: no luck...
[9] By a1ex hint: use CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP, but it's defined as "dangerous" by a1ex himself (bricking camera risk ?)
