Messages

[Only one very important pray]

@xaint and @mk11174 : Very good work, boys !

Only one very important pray : do not erase your repos and modifications ! Don't think they are not useful because another programmer did it yet the same ! Keep all your work, because it may be useful to dig into the differences (if there are any) between your sources and the Others sources, in the case something wrong or bugs should arise in the next or long future !

Many thanks to all of you !! 

You too man! Without your posts things would have gone much much slower I am sure!

For all you guys that can't wait for the pull to be added!

Thank Xaint for the mem fix!

http://www.mediafire.com/download/145ctnwr5de524c/ML_Mem_All.zip

Hi guys, you can find the cache_hack i've made, in my repo, if you wanna try:
I think it is here: https://bitbucket.org/xaint/ml/commits/f3631da68349f1dda86ee136bbddc5a3c4efc9bc
Try it on your own risk (for me it's pretty stable) :D

Ahh, there we go, cool, thanks man!

Update: Yep, 640k cool!! Thanks again xaint

Have you done my last hint ? Do it works ?

not yet, Alex scared me when he came in at that point.

Why are you messing with this in the first place?!

lol, we have been trying to get more memory to make ML load all features with Raw rec so we don't have to disable features just to get it to load. Right now we are trying to figure out Hijack Cache

have you added also : #define HIJACK_CACHE_HACK_INITTASK_ADDR             0xFF018D1C       ?

That boots cam but ML doesnt load at all.

So, for us, we should have :
#define HIJACK_CACHE_HACK_BSS_END_ADDR 0xFF011CB4           <- Our address of the first instruction
#define HIJACK_CACHE_HACK_BSS_END_INSTR 0xE3A018C6   <- The machine code of new value (start value)
#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_ADDR 0xFF011CB8  <- Our address of the second instruction
#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_INSTR 0xE3A00833  <- The machine code of new value (end value)

That leads to no boot with just red flashing light.

I was able to get more memory going by adding the cach_hack code, but still believe we need 2 addresess from our firmware to make it work all the way.
By adding this code:

Code Select Expand

#define HIJACK_CACHE_HACK
#define HIJACK_CACHE_HACK_BSS_END_ADDR   0xFF01109C
#define HIJACK_CACHE_HACK_BSS_END_INSTR  0xFF010134
#define HIJACK_CACHE_HACK_INITTASK_ADDR  0xFF0110A8
#define ML_RESERVED_MEM (1024*1024 - BMP_VRAM_SIZE - 0x200) // see zebra.c, bvram_mirror_start initialization, and boot-hack.c

I think we just need these addresses to make it fit our firmware, if I am right?
#define HIJACK_CACHE_HACK_BSS_END_ADDR   0xFF01109C
#define HIJACK_CACHE_HACK_BSS_END_INSTR  0xFF010134

But whatever this does, it increases our memory in all places but our buffer mem of coarse, and I can enable a few more things but not much cause it still crashes.

Compare my screen cap to your cam and see.



I still cant look through the firmware.

I tried the disassemble.pl but alls that did was give me more files I don't know what to do with.

I do have full version of IDA advanced 6.1 which I did use porting the a3300 but they had idc scripts that found names for all the addresses auto, I am not finding any idc scripts for IDA to work with 550D firmware, if I am wrong, someone please point me in the right place?

here another test....

550d 2496*1065 4fps

download the orginal file

https://vimeo.com/67414198

wow!! that looks amazing! so clean and crisp!

Very strange, I don't have the M tab.

You are not using our special Raw rec build, those features in that menu are not enabled on it, plus no M, use the one I just posted link for.

Ok, new build with Waveform turned back on and added back in better Rec Mod with more settings in it like before.

Still no luck with Raw playback on cam, still crashes till you take out battery so avoid using it.

http://www.mediafire.com/download/7gh9d57nazw9jkb/ML_Wave_BetterMod_Raw_Rec.zip

You can disassemle them with disassemble.pl

Sonic, thanks! I actually figured out the dump a few days ago, but could nopt figure out the dissasemble part, I have IDA but looking through that was no help because much of it was garble because I did not have and scripts, so now I should finally be able to dissasemble it to maybe help in finding the proper addresses. I understood what 1% wanted us to do back in that post but was just stuck since I could not search the firmware. Hopefully we find it so we don't need these tricks to get our Raw Rec going everytime we want to update to the latest source.

Oh, and to clarify, I know the script is not for IDA, I will look use it with ipython if I am correct?

I'm cheesing on the features that have to be turned off are u talking waveform if I can have waveform and raw that would be the only features I'd need on to be honest. On raw how Mitch control will it give u? Is it true raw or some mimicking of it

Ok, I will see if it will still work with those turned on, no problem! 8]

btw, raw playback in camera crashes it - have to pull out the battery.

I am sure it will crash doing that, the new source added a few things that used up more of our memory so we are back at the border line again. But at least we get bigger size with Raw Rec!

Maybe when I add back in the last module from last build, maybe it will work better.

I would prefer a 1200 width option back, jumping from 960 to 1280 is a bit too much, maybe even something in between would not hurt.

No prob, I will try to add back in the raw_rec module from before and compile it in to get the other module menu for raw rec, I to thought it was cooler, better to test with source mostly left untouched first, but since it works I will try to add that back in for sure.

By the way, BIG thanks to 1% for getting more mem out of the main source! Only thing that help us with this build even if we had to lose a few features, but nothing important at least.

I kept on as many things as I could with the updated source with the flexinfo added, I wanted us to have the most recent updated source so I just made that one work for us, we will have the main features, at least the things I think we need with Raw Rec, if we want other features, those really have nothing to do with Raw Rec so best to use another Bin without Raw Rec.

If 960x480 does not work for you first try, dont give up, it usually works 2nd try and on.

Hacked mode does not seem to help.

Use Video mode, works best.

I notice wav recording does work in Raw Rec, it does create wavs fine even though we get a crash report, but this doesnt seem to be with Raw Rec, cause I see we get same error just trying to Record wav file in the Audio Menu without Raw Record on at all. I just kept recording with crash on screen, it still made new wav files, but probably best to not even use it, use a portable audio recorder like whats best for FPS feature.

The only Direct Draw feature that seemed to effect Raw Rec at 960x480 was focus peaking, but not always.

I see they still did not make a way to save Raw Rec settings like how other settings are saved.

http://www.mediafire.com/download/9agq38cf5mafb3c/ML_960x480_Raw_Rec.rar

Don't worry, I will share, I am just trying to get as many things activated as possible with the new source, I promise I will upload it soon with all the files you need.

Interesting results. With new stable build, after disabling the same features from I did in the other builds, the mem was not enough because with the new stable build they added in flexinfo, so I have to turn a few more things off to make raw rec work, but when it does work, I can now get 960x480 stable with no skips. I was only able to get 960x408 before, I also noticed the malloc mem is now 31M / 75M  not 28M / 68M anymore. So we have more me which makes us able to get 960x480 Not sure what was changed that effected our memory, alls I see new is the flexinfo stuff.

Ok, update: Well it is not stable build that changed the memory, U just tried it without an modifications and it shows 28M 68M so whatever gave more memory was one of the features I turned off to get raw rec to work with the new stable source/ aka Nightly build. So now I need to track down what is gave more memory.

The new nightly builds is not helping us much with Raw Rec though since we have to turn off more features to get it to run, so maybe I can stick with the source I have been using and see if I can get more mem from that one this way we don't lose anymore ML features then we already did.

Update:2 Well it seems it is in the source, something changed from the last nightly build, cause wth the last nightly we get lower memory, with the latest changeset we get more memory, so maybe the fix 1% came up with.

Ok, say we can thank 1% for his tweak to exmem which got us more memory to use 960x480 stable, I confirmed afte going back a few changesets to the one he tweaked that it is the one that did it.

Now to add this change to our old source so we dont lose more features.

Hmm, no issues in video mode, I just tested it and the rectangle is right on target for 960x408, is that the res you are using?

On target in photo mode as well at least while I have rectangle centered, did not try moving rectangle, but I know panning feature works when I use it to move rectangle and video recorded follows rectangle.

One thing I noticed, recording in video mode is more stable, very hard to keep from skipping frames in photo mode, I see no reason to use photo mode, video mode seems best while using Raw Rec. No skips using 960x408 except very 1st try.

Yes the white rectangle is the one I meant and that is the build I am using too. The rectangle matches recorded result in photo mode, but not video mode (I think).

I always use video mode, but your saying its there but does not match what your recording, I will have to check now. This kind of stuff I wont be able to fix if it is a bug cause this has nothing to do with memory or the features I have enabled, I have not messed with the Raw Rec module this is from the latest unified build from the stable release, alls I did was turn features off that are not used much to get more memory, non of that will effect how Raw Rec works.

For anyone wondering about the white rectangle and constant bitrate, these features are all enabled in the later release I posted with EttR and Crop in it, http://www.magiclantern.fm/forum/index.php?topic=5582.msg40875#msg40875  I see the Raw rectangle as I record Raw, if this is the rectangle you mean, maybe you need to clear your ML config file, it is loaded and works. Let me know if this is the one your talking about.

I also get 960x408 at 24fps regardless if I turn global draw and any other feature off, so you should be able to keep everything on that is enabled for the release. Hack mode does seem to stop the skipping with 960x408, it always skips after 72 frames 1st try but the 2nd and next tries till I reboot cam all are no skip. I use 45 MB/s sandisk extreme and yes, only get max 20-21 mb/s cause that is as fast as the cameras controller will record no matter how fast your card is.

I managed to get my camera to crash shooting RAW. Just dropped battery and I was good to go. I noticed that I have to setup the RAW feature in video shoot mode, then shoot in photo mode. At the end of a recording using 1:1 ratio the camera hung and created a error file. I guess I should pass this on, but I'm not sure if the core Devs are interested at this early time of 550D implementation.

I gather there is no way to get full FOV due to memory restrictions. So there are no additional line skips available? Grateful that there are at least an overlayed shooting box

No, cant really even worry about crashes using Raw Rec, cause this build is just a build for us to at least use it. The only stable release you can count on is the full build which does not include Raw Rec because of memory issues.

Thanks. Unfortunately it's a compiled version. I need the sources of this version, but i cannot find them inside the commits. Do this correction was already merged into the official ML nightly build ? If yes, I can check in the official repository current sources.

Same here, I see he included a bin file so I dont know if there are any changes that need to be done to the source too besides just replace the rec_raw.mo and magic.sys file included. I havent had a chance just to try it, I will try with the latest source once I get a free chance for sure.

And once you 550D guys get the "SRAW" option back, you'll get at least continuous recording in 960 X 540

I already tried to enable SRAW, our camera gets Assert errors with it on, that is probably why Alex has it disabled in the regular builds, it actually is still on in the regular builds, but it is used in the the feature AutoBurst Picture Quality, if you turn that on while set to RAW in canon menu you get an Assert error with our camera. And that is if I turn it on to be used like on your cam with this 550D Raw Video build or when I use it with the new nightly builds, doesn't help us at all.

2. It's great to have the overlays, raw histogram, focus peaking and crop marks then switch to clear overlays for recording. But is there any chance of keeping crop marks on, trying to judge where the letterbox is for keeping framing is difficult. :-)

http://www.mediafire.com/download/c5c07edkkdzfkjz/ML_Raw_Fps_Ettr_Crop.rar