Messages

Geez!!! I can't even find the dump for the cam, I read that there are tools for it, but I must be looking in the wrong place, cause am I wrong or do we use the canon firmware now? When I did on a3300 for chdk I had to dump the firmware and use that. I don't even know if I will figure it out, but I am trying for sure.

Or is the dump tool in debug.c? I remember something about ROM0.bin etc...? Anyone know?

I've just installed the version and switched to movie mode, when I zoom in camera crashed


here is the log;

ASSERT: dwDeadLine != 0xFFFFFFFF
at LVState.c:5842, task LiveViewMgr
lv:1 mode:20


Magic Lantern version : v2.3.NEXT.2013May26.550D109
Mercurial changeset   : b1b83dc89db7+ (unified) tip
Built on 2013-05-25 23:53:21 by magiclantern@magiclantern-VirtualBox.
Free Memory  : 265K + 1977K

Yeah, there will be errors till we can get more memory to turn on all features.

OK, here is the Raw Rec bin with more more features and Auto ETTR, may crash 1 st try or randomly cause memory filled, but I only had it happen once first time using it, but just expect, just trying to get as many features going as possible.

http://www.mediafire.com/download/37ag5vd6z7mm4vj/ML_Raw_fps_ETTR.rar

On this one Hack on seems to help get 960x408 going for me like it was before adding stuff back.

No, alex did not enable it for the 550D, I did to see if it worked, it seems to do something, but I don't know if it is accurate for this cam, but no, I kept it disabled for now, it will prob just use more memory anyway making Raw not work, we are at the very limit for sure, not good to turn on any other features with the Raw bin, it will crash for sure. But I got more features on at least so it feels like ML is back at least.

And no, I don't see a point to get a faster card, the controller in the cam is the limiter, no faster card will make any differ.

Update: I enabled AutoETTR and it worked, only in photo mode but it looks like it works, cam is for sure at mem limit, I did get 1 crash first boot after making new bin but have not been able to crash it again yet, But it is for sure at the limit. The BIN is at 444.2KB any bigger it crashes cam.

I am happy with everything that is enabled so far though. I will keep playing with ETTR enabled and if I dont get anymore crashed I will add it and send the link for it.

Anyone interested, I enabled a bunch more things, I think it is at its max though, but seems to run the same as before 

http://www.mediafire.com/download/akpnykdda78e9ua/ML_RAW_FPS_FIX2.rar

By the way, this is from the latest changeset as well so all up to date.

I used Windows 7 64bit and VirtualBox using the prebuilt setup from here.

The idea looks good. But the bandwidth speed of 550D does not allow long record with this quality.
Low resolutions: virtually no sense to use it. Large resolution: Maximum of 30-60 frames and then buffer is filled.
Missed shots will not be needed to use.
Here is small test:

Nice to see the detail you get compared to H.264 sux the 550D has a slow SD controller. 

Anyone interested in seeing the files I edited to get there build to compile to have same results as I got, here are the files so you can see the changes, I added a install.txt just so you know where the files are found or go if you just replace them.
http://www.mediafire.com/download/vff8h5omvl9qmio/ML_RAW_MODS.rar

I don't have anything to do with how the raw rec works, the developers here made it so they would be the only ones who could answer those questions, I don't have any knowledge how it works and am not a programmer, I just used trial and error to free up our memory to make it work for us, but no matter if they find the extra memory so we can use full use of ML and the raw rec, it wont change how Raw rec works, its the speed limit of our cam. We are stuck with it. And the Raw2DNG.exe is how everyone is extracting the RAW files, this is the way they built it. No idea if they plan to find a differ way.

For us it seems, if you want 24fps video, we have to just think of only getting standard def video and 720x480 or 640x480 not expect any more. or shoot 960x408 and blow it up to 1280x720, cause even blown up, it might get a bit softer, but the idea of being able to fix the overall levels of your video without messing the colors or brightness up like what happens when you try to fix up h.264 from the cam, well, that is so nice, and no compression artifacts to deal with either is nice as well. It just depends on what your using it for I guess. Just cool to have another feature to play with as far as I am concerned. 

Yeah, I would reccomend not bothering with playback cause so many features are disabled that might have something to do with it, just use for recording cause after extracting with the raw2dng.exe the clip sequence is fine. Main thing is we get to record in raw.

@mk11174: Thanks for sharing.
I can get max 720x406 resolution. Maybe more with a better card?
Well, it's better to blow up DNG then h264.

Great :-)

Yeah, you should be able to I guess, my best res is 960x408 and works steady I captured a 1200 frame clip and decided to stop it cause it worked fine. Panning worked fine to. The hack thing does not seem to help anything. I have a 45 MB/s Sandisk Extreme 16GB

For anyone else that wants to try anyway.
Just Raw_rec, no FPS  = http://www.mediafire.com/download/28yp9iaad5ep8qy/ML_Raw.rar
Raw and FPS added back = http://www.mediafire.com/download/b866nsqwokaeqq8/ML_Raw_FPS.rar
Raw and FPS added but took out a couple more things just to see if better results on capture. = http://www.mediafire.com/download/u8kdos53mkows9c/ML_RAW_FPS_FIX.rar

Remember, don't expect to see all of ML great features in the menus, the camera can't handle all at once yet so most are turned off to get this to work for now. So keep your other bin as a 2nd.

He probably meant the features. 

Alls I did was go into all_features in the/src and comment out anything not really needed and once it worked cause of having enough memory, I uncommented fps to get that going again.

This gets it working as good as it should be, but the only true fix is for someone to figure out how to get more memory available like 1% said so we can enable all of ML features with it.

But for now you can have fun and just use 2 bins, 1 with it and 1 without it.

There is nothing left to do really until someone figures the mem issue out.

Well, I was able to turn off a few more things to have enough juice to turn FPS back on.

So now we can get 1720x1156 @4fps for timelapse stuff or obviously you can play with FPS to get higher res.

I also can do 1280x720 @10fps no skips

I find that anything that is shows you need 16mb/s or more is to much and skips.

So thanks to the devs for the tweaks to the raw_rec file it gives us that nice info to make the right changes.

Oh, and that is with my card, I don't know what you would have to set to for slower or faster cards.

How to install modules? no menu "M"

I can share my bin with you to have fun with, but I feel it might be best to wait for a Dev to give the ok since ML is there code, they will know if it is safe for testing in cameras with all the things I had to disable in all_features to get the memory to load the raw_rec module.

But it is running stable with no crashing, just can't have all the other cool ML features enabled for now till someone finds a way to get more memory for the 550D to have all loaded at once. Maybe for now we can just keep 2 bins ready to go and switch back and forth till we get the memory for al features at once.

I successfully captured a raw video on the 550D, I had to go into /src/all_features.h and disable many features to get enough memory for it to allow live mode plus the Rec module, but at least it seems to work. So far I was only able to capture 720x406x23.976fps without a skipped frame though. But it does work for sure, I extracted the DNG files from the RAW file it made and these look fine so far, more tests needed for other resolutions though, just thought I would update anyone interested.

And I know its only a temp fix because obviously we need our other features turned on, like 1% said, we need memory from the correct places I guess for it.

I feel better though just seeing it work on this cam!

UPDATE: Best I got with no skipping was 960x408 @23.976
Other Max res I can do with no skip
In 1920x1080x24fps mode
720x540 4:3 @23.976
640x480 4:3 @23.976

In 1280x720x60fps Mode
720x172 3:1 @59.940

In 640x480Crop Mode
640x214 3:1 @59.940

I am using freshly formatted each time 16gig 45mb/s Sandisk Extreme

Im guessing the devs are very busy with this new 10bit / 12bit code and the 5d III I am sure eventually it will be set up for us, but probably going to be awhile, they look pretty excited about the new code which may benefit us SD card users if we ever get RAW going on our cam that is. I can use the feature on the 500D I have, just hate that I handed my 500D down to my kid when I got the 550D and now hers has a cooler feature, LOL!! But I am limited on what I know so I am done for now I guess since I don't know how to disassemble the firmware with these cams. Sorry guys!

I to would help, but the last time I disassembled a firmware was 2 years ago for the a3300is to do a chdk port which luckily worked out well, but it seems looking through a firmware for these cams are different, and I am not even sure if I would use IDA like I did for chdk. I wish I knew how to set it up though cause I would surely take the time and start looking. Only thing I have now is the prebuilt compiler with vbox. I was using my own setup with ubuntu with the directions online to install it manually but it was the old toolchain and seemed smarter to start using this nice up to date prebuilt version. These guys in here are awesome for making that up for us wanna be hackers, lol.

Look at what was done to boot-hack.c and 600D consts.h
https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/commits/all

Its booting into allocate pool and uses 640K bins. Just have to find the addresses in 550D firmware.

Ah! Thanks for finally clearing that up for me, finally a real technical reason why it crashes when loaded, thank you very much for that info. Plus it gives hope that it should be fixable if the correct addresses are found.

Memory is fixed? Registers are right?

Anything I can do to start checking?

No, not working on 550D yet, module can be loaded but that is it, camera crashes right away before you can do anything. So maybe something still has to be done in the code with addresses to enable it to load on this cam. Funny how not to long ago everything was all about the 550D and now even the 500D is winning this one. I wish I knew what needed to be done, I would do it, but I am not a programmer, but I can compile at least and if I am told what to do or guided I usually can get it done, but I guess we will have to be patient  till some developer with a 550D gets in the mood to finish it off. I just don't get why it is working on the 500D and the 650D but not with this camera, what can be missing?

Here we will concentrate our efforts to port raw video recording to 550D !

Current state-of-the-art : module loads but when live view is enabled, the camera hangs... 

Confirmed, hangs to black screen when trying to bring up live view in M mode or loading Movie mode. But module does load and shows up in menu, but cant set anything until live view is turned on, it just shows ON 0x0

Ok boys, I started a new thread for 550d raw video recording, just to keep this thread clean and only for on-topic (silent pics) : --> http://www.magiclantern.fm/forum/index.php?topic=5582.new#new

Please, lets converge all our efforts there ! Thanks ! 

Good idea, sorry.

What dou you mean by "I am using the updated tip" ? 

Just mean the latest changeset, sorry, the one where alex posted all the ETTL stuff.





See, loads module fine, but cant turn on live view or it crashes, and it does show up in other menu once loaded.