Messages

i did not dig into the 60D binary yet, where to add the hook poins.
will tonight look into it if its the same and then add the addresses.
(per model we need 3 values. two memory addresses and one size)

Ah, alright, that makes sense. I don't know much about the specifics of the ML coding so forgive my ignorance. Either way I will await your update and be sure to test it out once it is up.

One of these days I will find the time to dig around in the ML code.

Ah ok. Is that due to system specs or just not enough development done yet for the 60D?

thanks

but i need testing and feedback.

It seems as if nightlies are now being updated again for the 60D so I will test it out after work today and post the results.

While I am not an active participant on the forums most of the time, I am a regular reader and follower of the development of ML and use ML regularly. (Almost religiously ;-) )
G3gg0, you have done an outstanding job on this. I have not tested it myself but from the video it already shows a lot of practical application uses. I never thought about on-camera encryption and locking out of images, but this is fantastic. A secondary partition or saving the files somewhere in a hidden directory in the ML folder or similar that looks like misc files from the camera's OS would do even better if the card was taken out of the camera to be searched. Sure there would be some large files in weird places, but nobody would be able to open them and likely as not nobody would care. Just a thought on if it is practical or not.

A standard format of encrypted CR2 files or JPEG would be good to have documented in a format other than what is easily recognized by most. I am thinking similar to the ML DNG format that is being implemented for RAW recording.  (Conceptually ofcourse. A documented standard "encrypted.*ML crypt file extension here*" type of file. )

As a photographer/videographer that currently works for an organization that works in restricted access countries I can safely say this would be of huge use to myself. Much easier than using a live linux USB distros to move data onto hidden encrypted hard disk partitions... still would be done but makes on-camera files much safer.

Keep up the good work guys.

[BAD PIXELS:]

BAD PIXELS:
Here's a link to Marrek's build that gets rid of the bad pixels (you need to turn on LV_AF_Raw in the Raw Video menu).
https://www.dropbox.com/s/0jiq5wuzwp6igyi/ml60d_01_09_2013.zip

Here's a link to an earlier version (can't remember which one works best - think the one above has Dual ISO as well & some other stuff):
https://docs.google.com/file/d/0B-HdscXfsKpgbTJiT18tcS1ldjA/edit?usp=sharing&pli=1

It works & is the only workaround for the 60D ATM.

Don't be afraid to use the lesser crop modes - I find 1280x... upscales really nicely & you get longer recording times!
Also, remember to change the Picture Quality in the Canon Menu from SRAW to S2 (jpeg) - you'll get longer recording times.
Turn Global Draw off when recording.

And finally, if you want really high res bursts (i.e. higher than 1728x...) you can achieve this by doing the following:
Press x5 zoom button (remember to turn off Global raw first & set Frames Per Second Override!)
Press ML Menu button
Goto Raw Video Menu & you'll notice that you can go further on the Resolution scale (max 2512x...., but i use 2240x.... to be safe).
Exit ML Menu
DO NOT EXIT x5 zoom mode
Press record & you should be able to get about 73frames.

Its not perfect, but once you find a higher resolution that works well it can add to your videos.

Good Luck! 

Sir, you just saved me a lot of time and effort trying to figure out why my 60D could not record more than 4 seconds of 1280x720 30fps video. I knew there was something I had to change in order to make it work but it was a while ago that I read it and couldn't for the life of me remember. For this you have my thanks.

For workflow I have a question. I have been getting mixed results when I bring my raws over. The raw2dng frontend GUI for Mac. Using this I can create the DNG images and it renders a Apple ProRes 422 (HQ) for me as well using ffmpeg. The proxy, however, shows hot pixels. When I bring the DNG files it creates into After Effects there are none but instead I get more noise and a different exposure. (no settings changed during import) What am I doing wrong?

Anyone willing to help out a newbie?

And to everyone working so hard on Magic Lantern, you are amazing.