Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - mesebar2

#26
sorry A1ex, have been super busy until now.
i had switched back to the 17th build in order for making it work.
if it can help the community i will temporarily install the 19th build (or the last compiled build now available) and paste my config file (if that the right way to do it?)

#27
I did not forget to set FPS, i tryed both with globadraw off and on, they were consistent and repeatable.
I managed to capture always only 21 frames before it would fill up
#28
Quote from: a1ex on May 20, 2013, 10:29:04 PM
The x5 mode is a lot more cpu and memory intensive (3.5K source frames)

Thank you very much for your reply, A1ex.
I switched back to the 17th May build and i am now able, having set exact fps at 25, to record without any problem also when magnified!!!   (i am letting you all know, for it may help somebody else, and because the developers may be interested too, you never know :) )
#29
My card is easily handling the 1920x1080 raw video, but when i try to record the magnified way, even if i set the FPS to 25, the recording stops after 20-25 frames!!!
is it happening to you too?
are you setting a lower resolution? (perhaps 720p)
I am using the 19th May built compiled by laurenco

Thank you all guys, it's a great community here!!!
#30
Hi, i am on my tablet and can't send you the report of my card testing, but i can confirm that my Komputerbay 64GB 1000x, which just arrived today, works perfectly in RAW video usage. I did a benchmark, top writing speed at 128MB/s
#31
Quote from: thenickdude on March 30, 2013, 03:24:36 PM
So, I haven't seen any clear instructions for how people can try out the (unstable) development release yet (instead of the older Alpha 3), so here's my guide. Because it is an unstable development release, it could wreck your camera, so do this at your own risk. Please correct me if I get any of this wrong.

1. Start by updating your camera's firmware to the latest Canon version (1.1.3).

2. Because this isn't a final release, your camera needs a little modification made to it so that it can load Magic Lantern from the SD card. This is called turning on the camera's bootflag. When the bootflag is turned on, and a bootable SD card is inserted, the camera will load and run the file "autoexec.bin" from the SD card. Here, autoexec.bin will be the Magic Lantern software.

To turn on the bootflag, format your SD card in your camera, then copy this file to the root of your card:

http://a1ex.magiclantern.fm/bleeding-edge/5D3/5D3-113-bootflag.fir

Put it back into your camera, then run the firmware update option from the menus. The update will turn on your camera's bootflag.

3. Download the nightly Magic Lantern zip here. Unpack the zip file and copy just the "ML" folder to your SD card. Delete any .fir files that are on the SD card. You've now copied just the fonts and other data that ML needs to operate to your SD card.

4. Now you can copy a Magic Lantern development build (autoexec.bin) to the root of the SD card. Building this file is tricky, but NerveGas has kindly built a copy for us and posted it here. Unpack that zip file and copy the autoexec.bin to the root of your SD card.

5. You should now have an "ML" folder and an "autoexec.bin" file in the root of your SD card. That's the data/fonts and the actual Magic Lantern software. All that is left now is to set the "bootable" flag on the SD card, which tells the camera that it should look for and run the autoexec.bin file for us.

On Windows, you can use the EOSCard utility to do this:

http://pel.hu/eoscard/

Select your SD card, tick the EOS_DEVELOP and BOOTDISK options, install no FIR files, and Save.

On Linux / OSX, you can use the make_bootable.sh script instead. Plug in your SD card, then run the script from the terminal with sudo ./make_bootable.sh . Hopefully you know how to use the terminal.

6. Okay, so now you have the bootflag turned on in your camera (so it looks for bootable SD cards), you've marked your SD card as bootable, and you've copied the development Magic Lantern build "autoexec.bin" and the Magic Lantern data files "ML" to your SD card, you're ready to go! Turn off your camera, put the card in, and turn the camera back on. It should boot and run Magic Lantern.

Note: The nightly builds available on the main site do NOT support the 5D Mark III yet. You need to build autoexec.bin yourself or use the version provided by NerveGas instead (as these instructions already mentioned :)).

Hi, i did all of this (three, times, just to make sure i was not missing something) but it did not work for me!
I was able to install the Alpha 3 immediately, but when i then tryed to follow this procedure, it just did not work :/
I noticed that, after formatting my SD, putting the bootflag fir on it and running the Firmware Update on the camera, it would quickly show a message on the lcd saying "Cound not find ML files!"... i suppose this might be the reason for which all the other steps i then carefully followed did not work.

I thought of running the Firmware Update by keeping both the bootflag.fir, the ML folder and the autoexec.bin on the sd card which i had made bootable with EOScard, but since on point #3 it said "Delete any .fir files that are on the SD card.", i thought of asking you to please help me rather then doing something stupid :P

Thank you all for the attention and my compliments for this amazing job you are doing, really fantastic!



EDIT: the moment i switched the MODE selctor to M, everything suddenly worked!!! Setting the mode to M is something that was not clearly stated on this thread (and, in fact, the alpha 3 installed and worked perfectly for me while my mode was on Av) but on the CAMERA PREPARATION in the wiki for installing ML, it said to put the mode to M and so i gave it a try... I hope it might help others :)