Firmware revision 1.1.3 now has an updated firmware installer: http://www.magiclantern.fm/forum/index.php?topic=14704.0
Quote from: Original PostDownload ML for 5D Mark III - Alpha 3 (https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-5D3.113.Alpha3.zip).
Usage:
1) Update camera firmware to 1.1.3 (http://www.magiclantern.fm/forum/index.php?topic=9983.0).
2) Format the card from the camera.
3) Copy ML files on the card and run Firmware Update.
NOTES
THIS VERSION OF MAGICLANTERN HAS AUTOBOOT DISABLED
Which means you'll have to re-run the firmware update every time you power off the camera.
It's a safety measure: this version will not attempt to change any camera settings. Try it if you are not yet confortable with the nightly builds.
Risks:
- This is one of the safest versions as of right now, but its feature set is quite limited.
- Nothing is written into ROM, and no camera settings are changed by this version, so risks should be minimal.
- If anything goes wrong, we don't pay for repairs. Use Magic Lantern at your own risk!
Features:
- Card test at startup
- Histogram and waveform moved to bottom
- New experimental display for focus peaking (extreme sharpness)
- 16:9 bars for anamorphic preview
- Focus box moves faster (not yet customizable)
- After taking a picture and pressing Zoom In right away, you can scroll through pictures
- Saturation boost when adjusting white balance
- Warnings for bad settings (e.g. if you set picture quality to JPEG instead of RAW by mistake)
- Dim the red LED while recording (make it less distracting)
From alpha 2:
- Magic Zoom (zoom while recording), experimental focus peaking modes, ghost image, display presets
- Movie indicators, movie logging, rec/standby notification, force LiveView for manual lenses
- Gradual exposure in movie mode
- HDR video
- Brightness, contrast, saturation, display gain, color schemes, UniWB correction, upside-down mode
- Clean HDMI with pillarboxes
- Anamorphic and fisheye correction
- Image review tweaks (exposure adjust, remember zoom position...)
- Task and CPU usage info
From alpha 1:
- zebras, focus peaking, cropmarks, spotmeter, histogram, waveform, vectorscope, audio meters.
- card benchmark, debug info, stability tests.
Tips:
- Disable Auto Power Off.
- Recommended usage: copy ML on a small SD card, keep it in the camera, and use CF cards for shooting.
- You can use any card combination, just don't put ML on both cards.
- EyeFi cards are working!!! (http://www.magiclantern.fm/forum/index.php?topic=2687.msg15653#msg15653) (thanks kikouyou)
Known issues:
- Some users reported a few random lock-ups with Alpha 1, but I could not reproduce any.
- The experimental focus peaking modes are a bit too slow (will slowdown LiveView frame rate).
(http://a1ex.magiclantern.fm/bleeding-edge/5D3/5d3a2.png)
FOR DEVELOPERS ONLY
Want to help with the porting proces? Use this special updater file (http://a1ex.magiclantern.fm/bleeding-edge/5D3/5D3-113-bootflag.fir) to enable the bootflag and dump the firmware. With this, you can compile your own autoexec.bin (http://www.magiclantern.fm/forum/index.php?topic=991.0) and run it on your camera.
(BE AWARE: This file will set a boot flag which cannot be undone (yet). This will increase your camera boot time slightly and also increase the wake up time from 0.2 sec to 2 sec.) added by Renato 11-6-2013
You will be able to try the entire ML feature set, but the risks of permanent damage are a lot higher than with the public alphas. Use it at your own risk.
I am ready for testing!
Where can we Download?
Coming soon = something in future ;)
I know ;)
But thought there s maybe a special page or thread where I can look at to check news.
Seems like this is the page, haha.
Good luck with your work!
it's like waiting for christmas as a little child all over again ;)
Quote from: wintix on September 10, 2012, 04:36:19 PM
it's like waiting for christmas as a little child all over again ;)
Time to build a bit of hype I guess ;D
hehe, nice :D
can't wait
Do you intend to release the alpha version for 1.1.2 or 1.1.3? Just saw you were preparing to get it going with 1.1.3 and am wondering if one should try and get a hold of firmware 1.1.2 for the camera to downgrade, if already at 1.1.3.
I'll try to get it on 1.1.3.
*wishing you luck* :)
Booo... camera exploded.
exploded? :o
maybe the wishes were a bit too late. :-\
Crying tears of joy and gratitude.
Alex do you think in a future ML firmware version for 5DIII will include HDR video?
Would it be possible to do?
It will include all important features, this is only the first port.
is it becoming stable enough for you to release the alpha for 1.1.3 or are we headed for sunday 23:59 which still is this week? :)
It works on 1.1.3 just as well as with 1.1.2, no problems here.
woohoo! will give it a try once i'm home :)
Looks good, working fine on my 5D3
Whats the best settings for the focus peaking ? Or are there no "best" ?
Uhm I can't get it to autoload. I did the firmware update but I get no green screen, it just loads it and runs it. Is that because the alpha doesnt autorun ?
Right, there's no autoboot yet.
About focus peaking... experiment with it. Default setting should be a good starting point.
so far so good.. works great here !!! :)
Only seen some minor redraw hick-ups here and there.
I will play with it for some days before filling out the google doc.
works fine here as well
just installed it .. seems to be working fine .. will test it out later on today
Quick tests okay, but it does not load at all when having a Eye-Fi card in the second slot (ML on the CF card). I hope you will get this fixed, as Eye-Fi was one of the main reasons to go with the 5D3 ;)
working great. The focus peaking seems really tight. I love the mark III screen and ML takes it up a huge notch
Thank you Alex!! Amazing work! :)
Thank you for working on this! :)
Maybe you should increase the file size for the bigger buffer sizes, it seems it's rather optimistic with 128MB/s as the card is only specified at 86MB/s i think
Good point. If that number would be true, that would be enough for uncompressed video...
would be interesting to see what a 1000x lexar professional cf does. they are specified with 150mb/s read. from what searching just found me they do around 140mb/s write, so maybe if you can somehow dump a uncompressed stream it would indeed be possible.
then again i would gladly take compressed 4k over uncompressed 180p/2k
Thank you Alex. The version is no problem. Looking for the final version. By the way, is 5D3 possible to handle 1080P/60FPS or even 4K/60FPS?
Well... I'm not able to break physics laws :(
what features are you planning on trying out next, once you are satisfied with the amount of people giving feedback and stability so far?
bulb ramping / timelapse functions in general would most welcome to have, also the zoom in functions while recording would be great.
I'd like to try things that don't alter camera settings (as this part might be potentially dangerous). So probably I'll enable some advanceed ISO controls, HDR video, display tweaks... not yet sure.
I'm also thinking to expose H.264 parameters so you can play with them.
Quote from: a1ex on September 14, 2012, 12:12:15 AM
I'm also thinking to expose H.264 parameters so you can play with them.
Yay! :)
Quote from: wintix on September 13, 2012, 10:45:02 PM
would be interesting to see what a 1000x lexar professional cf does. they are specified with 150mb/s read. from what searching just found me they do around 140mb/s write, so maybe if you can somehow dump a uncompressed stream it would indeed be possible.
I have a couple of 32gig 1000x lexar cards. How do i test them on my mk3?
Quote from: a1ex on September 14, 2012, 12:12:15 AMI'm also thinking to expose H.264 parameters so you can play with them.
Does this mean higher bitrate etc? That's the main thing i'd like since you've already got peaking going! :)
Just a quick question,
With ML, Is there a way to re-assign the zoom/magnify button to its original position? (ie 7D, etc)
I too have some 32GB 1000x Cards and would be more than willing to be a Guinea Pig ;D
A1ex,
Thanks again for progress on the 5D3.
Here are my results from testing the last 24 hours. I just sat down with the camera and tried to go through each function. I'll certainly keep testing in real world use, but it seems very stable and free of glitches right now. Congratulations!
The only issues I encountered are:
1. Focus Method is different on 5D3 compared to ML2.3 on 600D. 600D only has Method [1st deriv.; 2nd deriv.], whereas 5D3 has Filter Bias [Fine Detail; Strong Edge; Balanced]. All worked.
2. While using Waveform [Fullscreen], a ghost of the waveform would remain sometimes when I would zoom 5x or 10x... only sometimes. I never use Waveform at Fullscreen, so I hadn't noticed this. But, the same thing happens on my 600D.
3. Histogram, Clip Warning [Gradual] is on 5D3 and not ML2.3 on 600D. I like the Gradual setting!
Here's what I tested:
Installation
I had not updated to 1.1.3 from 1.1.2. So, for kicks I tried installing ML on 1.1.2 (I do not recommend this and was I clearly warned not to do this). It would hang and not install. I removed the battery, reformatted the card and everything was fine. After installing 1.1.3, ML installed fine.
Global Draw
ON, LiveView, and OFF work fine in Liveview and during rec
Zebras
All functions works in Liveview and during rec (when set to show during record)
Focus Peak
All functions (and colors) work in Liveview and during rec (see note above about differences from ML2.3 on 600D).
Cropmarks
All work in Liveview (movie and photo) and during rec
Spotmeter
All functions work in Liveview and during rec
Histogram
All functions work in Liveview and during rec (see note above re: "Gradual")
Waveform
All functions work in Liveview and during rec (see note above re: Fullscreen and push-to-zoom)
Vectorscope
OFF and ON work in Liveview and during rec
Audio Meters
OFF and ON work in Liveview and during rec
I can also say that I tried turning functions off and on during liveview and record. No problems. I used it with all items ON and it kept up nicely.
I look forward to having Magic Zoom!
Quote from: jeffrogerson on September 14, 2012, 02:03:00 AM
Just a quick question,
With ML, Is there a way to re-assign the zoom/magnify button to its original position? (ie 7D, etc)
You probably know this already, but the Canon firmware for the 5D3 has some ability (granted, not much) to reassign that button. I have mine assigned to the "SET" button. I agree that it would be nice to have the ability to reassign it anywhere, so I hope the answer is that ML can do this!
Just finished testing and had no explosions ;D Messed with histogram, zebra, focus peaking, and the overlays. All seemed pretty stable. Thanks for your hard work, and looking forward to testing the next version. Looking forward to bulb ramping and intervalometer.
Thanks for detailed reports!
Yes, a few things were tweaked since 2.3 (like the gradual clip warnings). If they prove to be better than the old ones, they will become defaults.
Focus peaking is based on D2xy, so:
- biased for edges: that's exactly d2xy, and the algorithm is described here: http://www.luminous-landscape.com/forum/index.php?topic=56246.0
- biased for fine details: it's second derivative (d2xy) minus first derivative (what was d1xy). Rationale: strong edges (with high contrast) are very likely to be false positives, so this setting will try to filter them out and only look for textures.
Zoom button is hard to re-assign. There is a generic event for unhandled buttons (GUICMD_PRESS_BUTTON_SOMETHING), so it's not possible to know whether user pressed the old Zoom In or something else from the top area.
Magic Zoom flickers quite a bit (much more than with digic 4). I can make it flicker-free, but it will slow down the frame rate somewhat (probably 20fps or so). Is this a problem?
I wouldn't enable the intervalometer and other photo features right now, because they require some function calls which might not be safe, so I'll do more testing on my camera first for those.
What CF cards are you guys using? Why so fast?
P.S. ( different SD card in second slot have different result)
Using a 4GB class 4 SDHC with 64GB PRETEC 567X CF card
(http://i46.tinypic.com/ajknra.jpg)
Using a 8GB class 6 SDHC with 64GB PRETEC 567X CF card
(http://i47.tinypic.com/2z65jyf.jpg)
@crazypig: Resized images for you in post above as they were too large for forum. Next time please attach a resized-version of the image of around 500px max. on the long side. Most image upload services allow you to resize the image when uploading!
Why I can't Download???
I did Supporters
Thanks
Quote from: crazypig on September 14, 2012, 08:03:17 AM
What CF cards are you guys using?
Using a 8GB class 6 SDHC with 64GB PRETEC 567X CF card
Pretec PCF516G - PRETEC CompactFlash Card 567x - 16GB - transfer speed 85MB/s read 40MB/s write Metal Housing
It seems your card isn't the fastest one around as it is only specified with 40mb/s write speed. you can try rebooting the camera directly prior to running the benchmark to get it into a defined state to run the benchmark from.
@Director: see first post.
@wintix: here's a version which uses a 1.8 GB file for benchmark: http://a1ex.magiclantern.fm/bleeding-edge/5D3/ml-5D3-113.fir
My write speeds: 17.5 and 24.5 MB/s (Transcend 266x, photo mode, outside LV).
thanks, i'll post results in a few hours
Thanks for the reply with more info, A1ex.
I came across one issue that I forgot to post earlier: When I engage the ML menu while recording, I cannot navigate the ML menu using the aperature wheel. When recording, the aperature wheel only changes the aperature, regardless of whether I have engaged the ML menu or not. I can use the nipple to navigate the ML menu while recording. When starting the ML menu when not recording, the aperature wheel works fine to navigate the ML menu.
That's normal, scrollwheels can't be controlled while recording. You should see a crossed scrollwheel icon in menu that suggests this.
Quote from: a1ex on September 14, 2012, 01:29:54 PM
That's normal, scrollwheels can't be controlled while recording. You should see a crossed scrollwheel icon in menu that suggests this.
See it now. Thanks! :-[
Good news: I'm able to move the zoom button back to it's old place.
Not-so-good news: it's also triggered by M.Fn and Light button. But M.Fn is quite handy :)
you are referencing the 5d2 as the zoom buttons old place? from where to where would that move the zoom button on the 5d3? i can't quite imagine it as i don't have a 5d2 to compare with.
Yes, and all other Canon dslrs before 5D3.
http://diglloyd.com/blog/2012/20120325_1-Canon5DM3.html
ah, yes, that's true. not being able to do it with the thumb is indeed annoying. great to know that you can move it back :)
Well... I'm starting to think that the best place for zoom in button is actually M.Fn :)
it would seem so, yes.
alex:
sorry for the shaky video, it's a pita to hold the ipad steady :-[
it tops out a bit over card specification.
Can you try in LiveView? What card do you have? (found: transcend 600x, rated at 90MB/s).
If those speeds are true, uncompressed video (at least in 2.35:1) is possible!
sure. i went ahead and did it in movie mode, assuming you meant that?
Ok got it working, I'm running on a single SD and everytime that i switch off the camera i have to load back the firmware again.
Is it the same with the two cards method?
Quote from: vitafab on September 14, 2012, 04:38:00 PM
Ok got it working, I'm running on a single SD and everytime that i switch off the camera i have to load back the firmware again.
Is it the same with the two cards method?
yes, as stated earlier, autoboot is disabled for now.
alex, just checked, photo mode live view is a tad faster, don't know why.
Why is it that in LV-mode i get less write speed then from the menu ? (especially the 128k buffer mode is much slower)
Sandisk 60mb/s rated CF in liveview mode 54.6 - 61.7 in menu-mode
my 30mb/s rated SD-card only gives about 11mb/sec ?
Well... with focus peaking and other graphics enabled, it's pretty good IMO. Try disabling GlobalDraw.
In photo mode, the sensor is sampled at lower resolution.
Looking forward to see some tests on a 1000x card.
Quote from: a1ex on September 14, 2012, 05:03:06 PM
Well... with focus peaking and other graphics enabled, it's pretty good IMO. Try disabling GlobalDraw.
indeed, performance is pretty good and likely sufficient for high data rate video stuff. :)
video mode global draw disabled: 19,9mb/s 27,5mb/s 85,3mb/s
photo mode live view global draw disabled: 19,4mb/s 25,9mb/s 77,9mb/s
photo mode, menu, global draw disabled: 36,5mb/s 38,9mb/s 99,5mb/s (!)
(ran twice to confirm - missing autoboot is getting annoying ;)
i would guess we see the different results due to the fact that the data has to come from somewhere and also it's ml code which is dependant on how much stuff is going on. i bet canons native write operations are faster, independent on what mode the cam is in?
Quote from: a1ex on September 14, 2012, 05:03:06 PM
Looking forward to see some tests on a 1000x card.
oh yeah :)
These are my results using lexar 32gb 1000x card
keeps skipping last test, and lots of lines on top of display.
http://www.flickr.com/photos/66493340@N02/7986196588/in/photostream (http://www.flickr.com/photos/66493340@N02/7986196588/in/photostream)
For uncompressed FullHD 422 at 24p, I need "only" 100MB/s. Maybe with a 32MB write buffer it's exactly what I need.
For 2.35:1, I only need 75MB/s.
That's pure theory, so take it with a grain of salt.
you could do a test version for us to play with :)
Hmmm. I like your theory ;)
yes definitely would be interested in testing that out
I got slightly slower with one of my lexar 32gig 1000x's.. is the top right telling me there was only 14gig left on the card ? (haven't used ML much). It was at least half full so could that be a factor then?
This was using the 1.8gig firmware tester from page 2.
(http://f.cl.ly/items/0u1H1a2i1i3x0E3V3p32/Lexar1000_Test.jpg)
Put me down for testing uncompressed!! :D
This is such great news! Any increase in bit rate / image quality would be my main request for your next addition. Also, the ability to de-compress 1.5x anamorphic images on the L.C.D. so that the correct aspect ratio is displayed while recording would be fantastic! When one or both of these features are added I'll definitely be donating more. I'm shooting a feature in mid October. Any hope I can get a sharper image out of this camera by then? Thanks for the amazing work!
Hey Alex, a quick couple of things i noticed when playing back and having crop marks (2.35:1) showing;
When using built-in LCD if i press "info" to remove the 'clip location indicator' (whatever its called) top left of screen, the crop marks around that area will flicker on and off exposing the shot behind the cropmark.. not a huge deal but distracting none the less.
When outputting via hdmi to an external display, because it's playing back at 1080 (on my 24" monitor live view doesn't use the full screen so maybe just 720, and playing back clips goes full screen) the crop marks aren't scaled properly and don't cover the proper width etc.
Thanks!
any idea when you might add the intervalometer ? I wanna start shooting timelapse and it would nice not to have to
buy one
same here, looking forward to a alpha 2 build with a bit more functions to toy around with.
btw, is it my imagination or is modifying the shutter speed causing redrawing issues with the aperture number? it's kind of setting me off each time i fiddle with the settings as i first think that i accidentally changed aperture and not the shutter.
Hi guys,
I've test alpha 1 all day long during a wedding reportage and i had no problem with it at all.
It's great to have stuff back as i was used to. I didn't miss much the autoboot since most of the time i left the camera in photo mode with the autopower off. I've update the firmware with no problem except once when battery level was under 17% .
In very low light situation i've use 12800 iso with hard edge focus peacking and it does the job better then the other methods.
Thanks again alex
I'll keep donating
Can't say how grateful I am you guys thanks. Everything seems to be working just fine no problems whatsoever (minor GUI glitch at the bottom when I change shutter or aperture) shot for about six hours today.
I primarily do a lot of green screen work I read somewhere that there was an option for achieving better green screen results in magic lantern what is that setting?
You can use the waveform display to see if your greenscreen is evenly lit. Aim for a horizontally uniform graph.
Quote from: a1ex on September 14, 2012, 07:57:03 AM
Focus peaking is based on D2xy, so:
- biased for edges: that's exactly d2xy, and the algorithm is described here: http://www.luminous-landscape.com/forum/index.php?topic=56246.0
- biased for fine details: it's second derivative (d2xy) minus first derivative (what was d1xy). Rationale: strong edges (with high contrast) are very likely to be false positives, so this setting will try to filter them out and only look for textures.
So far so good - no issues at all for me :)
One question about focus peaking - I see there are two methods now as I don't recall edge from when I had it on the 60D, but in the article you pointed to there was this image (below) - do you think this sort of display is possible as it would be a lot easier to see at a distance or in sunny conditions.
(http://img856.imageshack.us/img856/228/escena2.gif)
I'm afraid this display would require a lot of CPU power.
I have some experimental display modes with alpha blending, but frame rate is quite a bit lower (15-20fps). Probably not an issue for photo mode with slow action, but with fast action it really feels very slow.
Cheers - would be interesting to see, although obviously as a lower priority.
Hi guys,
there any chance to have the hdmi and lcd working at the same time?
Hi guys!
Great work!
Just tested Lexar 32Gb x1000 and got 85MB/s write speed. Read test was skipped.
Maybe that s good news..
http://www.techpowerup.com/172369/The-CompactFlash-Association-Announces-CFAST-2.0-Draft-Specification.html
Hm, never done this before, so please, a step by step what to do!? =) hehe
Just unzip the folder and smack it on the SD card?
Or should the card be prepared in a way? Do I get to choose the ML on start up, or..
Aaah, so many questions, so many many possibilities!
Life is overwhelming now that ML on 5D mark III surfaced.
Or, might just be me, the technoobfool;-)
Regards
hi,
i don't have the mark3 but i will use it for a video shooting.
can you give me the right info to use the alfa version with camera?
i want to use the method the alex suggest.install ml on the small SD and using cf card for recording video.
so....is this what i have to do?:
1:copy ml in sd card
2:insert sd card in camera and press firmware update.
3.in now installed?
4.insert cf card and start to recording
5.i have missing something?
what is the button to have access to ml menù?is the same of the mark2?
thanks
You have got the procedure right my friend. I would insert both cards at the same time and then do the firmware update, because if you waited to insert the cf card the camera would turn off and you'd have to run the firmware update again. No autoexec.bin on the Alpha firmware.
Hope this helps !!
I keep trying to load the firmware with my SD card and my camera doesn't see the file. Do I use the USB? I'm on the updated canon firmware 1.1.3.
Format the card from the camera, and make sure the FIR is on the root of the card.
are you planning to release a second alpha to toy around with over the next weekend, alex? if so, what features do you consider to put in there?
Well... with the 7D thing I didn't really work on the mark 3 lately.
I've tried it on a small event this weekend (1300 pics), had to pull the battery once and got 3 black pictures (but I had a larger feature set enabled). In the google docs, two users also reported lockups (happened once, they could not reproduce). Not that good.
On the other hand, I've seen some reports of 5D3/650D problems without ML ( http://www.canonrumors.com/forum/index.php?topic=8732.0 , http://www.learningdslrvideo.com/canon-t4i-650d-vs-60d-review/ ), so it's going to be hard to diagnose.
For next alpha, I'm thinking to add things that do not require changing any persistent settings. HDR video is one of them, also most DIGIC display tweaks. Also the zoom position on M-Fn.
yeah, saw the changelog was pretty empty and hence hoped for a second alpha soon as things seemed stable from the outside.
i just read the forum thread you linked and it seems that only people that are using the sd card slot with high speed cards are speaking up so far. my glass ball guesses that since the 650d and the 5d3 used with a sd card are affected that it has something to do with the sd card implementation in recent cameras. maybe you can do a release with a ~15G file benchmark (or something so configure the size) to allow specific testing of the sd card slot in the 5d3. maybe it's possible to crash the camera reliably with putting some heavy usage on the sd card slot for a longer period of time.
so far i threw at the 5d3 what i could think of, went through several hundred pictures with ml enabled and didn't experience any issues so far, despite the minor redraw issue in video mode i mentioned earlier.
nice work on the 7d as well, btw! also looking forward to anything testable there. kind of cute to have two cameras with a port in progress. :D
Alex, how hard is intervalometer to implement in next Alpha?
It depends on prop_request_change calls... the thing that I want to avoid for now.
how is that particular call dangerous? if i understand it correctly, it changes camera settings and can potentially lead to a non-booting camera if invalid values are written for whatever reason? - i do see why one wouldn't want to release something like that straight away but it probably doesn't get more safe than it already is with your testing so far?
Quotehow is that particular call dangerous? if i understand it correctly, it changes camera settings and can potentially lead to a non-booting camera if invalid values are written for whatever reason?
Exactly, see here for my past mistakes with that function: http://magiclantern.wikia.com/wiki/Unbricking
mhm, i see your point there.
I installed the ML Alpha version into my 5D Mark III today. It worked so perfectly. (So easy to install, if you follow the instruction)
First I updated my camera firmware from the Canon website (Firmware version 1.1.3), then I download the ML Alpha version from the link provided by ML website and put it in my secondary slot (SD Card) of my camera and updated the firmware, and it's done.. so simple...
The auto-boot feature does not work yet.
Waiting for the upcoming version of ML 2.4
Thanx for the Magic Lantern Development team for their hard work and dedication.
Quote from: a1ex on September 14, 2012, 09:04:09 PM
For uncompressed FullHD 422 at 24p, I need "only" 100MB/s. Maybe with a 32MB write buffer it's exactly what I need.
For 2.35:1, I only need 75MB/s.
That's pure theory, so take it with a grain of salt.
Looks like the 1000x cards sustained write is maxing out at 90Mb/s. 2.35:1 uncompressed would be fantastic. A 2.66:1 option would be even better. There's some good deals on 1000x cards http://www.bhphotovideo.com/c/buy/Memory-Cards/Ns/p_PRICE_2%7C1/ci/1097/N/4270508873+4294955789
Is there any way to read 2048 pixels off the sensor letterboxed?
The other option would be a 4:3 crop for 2-3k anamorphic shooting.
Where is the actual download, going round the house to try and find it?
first page?
There's an optional updated .fir in post #49 to get a more reliable value in card speed tests
I've been testing the ML alpha software for a couple of days and it seems pretty stable.
Thanks a lot again for the alpha release! Hope to hear from future progress as well.
Tested Alpha 1 this afternoon- very happy my 5D Mk3 was still working after the multiple installs
The firmware was stable , only encountered a few issues:
-during the firmware update/loading - never got a mssg on LCD to say the install was finished. Only after a few minutes of looking at a black screen and then hitting MENU button, could i see that the firmware had actually been updated. Later figured out, install would be finished once red light beneath LCD stopped flashing
-I could never get any ML features to display in LiveView either when previewing the scene or during actual recording.
-I could not alter preset values of the features (ie - zebras at 99%) , assume this is because it is an alpha version
I finally did find the LIGHT button to toggle features on/off during playback/review modes. Would not work in LiveView on LCD screen
When do you think that Focus features (trap focus, altered focus patterns, ...) and Exposure Enhancements will be implemented for 5D Mk3?
I am new to ML, but impressed with its potential. Thanks for all the hard work
I tested yesterday during a job,
peaking was perfekt for low light.
Only one time my cam froze, but i can t recreate it... had to put out battery.
i am so happy i don t need en external monitor with peaking!!!
I'll continue testing and fill out the form when I feel like I have tried enough.
Here are two things I found today:
Setup on this test: ML on empty SD card. 4 GB CF card used for recording images/movies.
Minor display bug. The GB remaining (top right corner) does not refresh properly. It doesn't appear to erase the previous value before writing the new value. When you go to the ML menu and come back, the screen refresh cleans this up so that the GB is not messed up (i.e., it displays properly). See screen capture here: https://picasaweb.google.com/lh/photo/gtRb7lAR1hphpAmeVO8Eus6bkbuOKDnQM31wDLF3lbE?feat=directlink
Possible error-inducing feature. This happened to the recording that I was doing while trying to capture the image referenced above. It was tricky, as I had to time it so that the GB remaining would change after I started the screen capture timer, but before the timer elapsed. It took several tries. I believe this is relevant, as you'll see. I let the CF card fill up by continuing to record. When the card filled up on this round, I got Canon error "Err 04 / Cannot save images because Card1 is full. / Replace Card1." To be clear, this did not require a battery pull. The .DAT file remained on the card, but the associated .mov file was blank. The ML debugging log (reported on screen to be writing) was also empty - it was there, just 0 KB. I tried to replicate with both no ML and ML and could not... until I tried the screen capture during recording.
My hypothesis is that the Canon firmware notes space remaining at the beginning of recording and subtracts off the recording size from this, stopping the recording in time to convert the .DAT file to .mov. The screen captures (I did three or four) caused the card to be unexpectedly full before the Canon FW could stop the recording and convert as normal. My own view is that I'm not sure that it is worth trying to fix this with anything other than a warning not to do a screen capture if you plan on filling up the card (perhaps this warning already exists and I just haven't seen it!).
Actually I've noticed the free space bug two days ago (see changeset).
The other one makes sense, now I know what to try next.
hi,
i intend to use the SD slot for storing ML Alpha 1 and CF slot for storing video files.
Is there a way to 'lock' video recording to the CF slot even after a reboot?
regards
Proposed feature set for Alpha 2:
- Magic Zoom
- Focus peaking with grayscale image
- HDR video
- Gradual ISO transitions (this is new feature, and 5D3 is the only camera where it works flawless... yet)
- Display adjustments (brightness/contrast/saturation)
- Clean HDMI out with pillarboxes
- UniWB display correction (bleeding edge)
- Zoom on old button or M-Fn (not quite reliable though, I may disable this)
- Display presets
None of these things require changing any permanent camera settings, so they should be pretty safe. Backend things being tested: DIGIC controls and state object hijacking.
I'm OK with the next proposed feature set!
Been working with the Alpha1 since one week, haven't found serious issues.
So ready to test the next one ;)
Dear Alex,
Only one request....
Would you add autoexec.bin inside the ML please...
More easy to test
Sean
sounds great. hopefully you will get comfortable with using prop_request_change in an alpha soon :)
All working fine here. waiting for next release
Quote from: a1ex on September 24, 2012, 05:32:54 PM
- Clean HDMI out with pillarboxes
Are we talking uncompressed 1080p 4:3?
Quote from: a1ex on September 24, 2012, 05:32:54 PM
Proposed feature set for Alpha 2:
- Magic Zoom
- Focus peaking with grayscale image
- HDR video
- Gradual ISO transitions (this is new feature, and 5D3 is the only camera where it works flawless... yet)
- Display adjustments (brightness/contrast/saturation)
- Clean HDMI out with pillarboxes
- UniWB display correction (bleeding edge)
- Zoom on old button or M-Fn (not quite reliable though, I may disable this)
- Display presets
None of these things require changing any permanent camera settings, so they should be pretty safe. Backend things being tested: DIGIC controls and state object hijacking.
I think that would be fantastic ;D
For those loading ML on SD cards...
Did anyone ever validate if this was accurate??
Well...after some testing I have determined that, if you care at all about high speed shooting or clearing you buffer quickly, YOU DO NOT want to put a card in the SD slot. Why? Because, for some reason unbeknownst to me, Canon decided to build the 5D Mark III with one very fast CF slot which supports the newer UDMA7 protocol and a standard SD card slot which does NOT support the high speed standard (called UHS – for Ultra High Speed). http://www.canonrumors.com/tag/5d3/
Yes, it wasn't (unless you're writing to both cards)
My first speedtest was with ML on an SD card testing my lexar 1000x
(http://f.cl.ly/items/0u1H1a2i1i3x0E3V3p32/Lexar1000_Test.jpg)
I just tested again with ML on the lexar card and no SD and got the exact same results...
Quote from: a1ex on September 24, 2012, 05:32:54 PM
- Clean HDMI out with pillarboxes
What would be the resolution of actual image?
Been waiting for Alex to crack the 5D mkIII... ordered one immediately on release of Alpha 1! Thank you Alex and whole crew for all your hard work!!!!! Can't wait to start testing! ;D
This is all very exciting! I can't thank you guys enough for all this incredible work.
So knowing that these write speeds are around 89 mbs on lexar 1000x, what would that theoretically mean, I have read on here some pretty incredible numbers, but how feasible are they?
What would it take (monetarily, teamwork help, devs) to get these things up and running? What road blocks are you hitting?
Well... if we knew what we are doing it wouldn't be called research ;)
If I'll be able to reprogram the DMA in order to write sensor data to a file, that means zero overhead in the recording process, so benchmark numbers should be accurate.
I forget where, but I remember reading somewhere about starting a kickstarter, I personally think having a fundraising campaign would be a great idea, and open the floor to a broader spectrum of people who can donate.
Is that still on the table?
Yes, and the answer was: we don't need it.
So should I start investing in some 1000x lexars?
Just a little reminder for the testing form. I only have 12 answers. There are people who reported problems, but I can't reproduce any.
https://docs.google.com/spreadsheet/viewform?pli=1&formkey=dFRxbGZlUHYyOHB6SDZWZFVpUlVRTUE6MA#gid=0
Done ! Haven't saw the spreadsheet before your post, hope more people will answer it
No problems so far. It's been a positive user experience since I figured out how to work ML, and even though I'm a novice, I have not had any features in the Alpha not work nor any problems with my camera.
Thanks for the reminder!
Likewise - Minimal use due to schedule but no lockups, no failures, no glitches when we did. Thought I loved ML on the 5D2 but wow... peaking on the 5D3 is heavenly. Whaddaya say kids.. Magic Zoom?? Zoom button? Thx all!!
Still working well, no issues. Waiting for Alpha 2 with donation!
I've also used Alpha 1 with no unusual results or lockups. I used on 3 different occasions while on a paid video shoot and it did exactly as expected.
-Mark.
Nice. I'll try to prepare the alpha 2 next week.
HDMI is causing trouble - anyone needs 720p? I hope not.
Quote from: a1ex on October 11, 2012, 04:51:46 PM
Nice. I'll try to prepare the alpha 2 next week.
HDMI is causing trouble - anyone needs 720p? I hope not.
great!
nope, not really. everything is headed for high-res anyway
Quote from: a1ex on October 11, 2012, 04:51:46 PM
HDMI is causing trouble - anyone needs 720p? I hope not.
Are you referring to 720p HDMI output? Versus 1080i?
Hi guys,
i'm currently shooting a movie with the mark iii and a d800.
ML is helping me so much as usual, but one thing that i don't like about the mark iii compare to the d800 is the fact that when you plug an HDMI monitor the picture goes away on the LCD so i need two monitor with a splitter to give the feed to the director. The d800 doesn't have this issue.
Is because of the clean HDMI? there is any chance to have it working in the next 2 weeks?
Thanks again for the amazing work you're guys are doing.
Cheers
Fabio
That's how the HDMI chip works as far as we know... it re-routes the signal from the LCD to the HDMI port
Quote from: a1ex on October 11, 2012, 04:51:46 PM
Nice. I'll try to prepare the alpha 2 next week.
HDMI is causing trouble - anyone needs 720p? I hope not.
a1ex says "HDMI is causing TROUBLE" and I think "he must be looking at clean HDMI out, YYYYEEEESSSSS!!!!"
Ha ha ha, does anyone else get excited whenever a1ex says the word "HDMI"?
I'm talking about basic ML functionality on HDMI - like zebras aligned with the image etc.
Quote from: a1ex on October 12, 2012, 03:30:24 PM
I'm talking about basic ML functionality on HDMI - like zebras aligned with the image etc.
I haven't had a chance to fill out the survey yet, but here's the only issue I've had on my last 4 full day shoots. I've been using alpha one almost exclusive via HDMI with my SmalHD DP6. Everything I've tested works great; audio meters, fast zebras, focus assist, histogram, vectrascope, an even the manually enabled "Not recording" warning. Here'a what I've had enabled on my long day shoots: "not recording" warning, audio meters, histogram (with gradual warning), and LumaFast Zebras over 99%. The only time I have a problem is when I leave the camera on but power cycle my monitor. When the monitor comes back up, the 16x9 crop bars scale down a bit, slightly covering what should be the proper visible area and revealing part of what's actually not recording.
See this photo showing what I'm saying.
(http://i.imgur.com/K5rIsl.jpg)
Other than that, I've had no alignment issues with any of the features (zebras, focus assist, etc).
Edit: I should add that to get around this, I simply reload the ML firmware.
In 1080p it's fine, but in 720p, on my dp6 it's completely distorted.
Thanks for the screenshots, didn't notice that.
Quote from: mnteddy on October 12, 2012, 04:46:36 PMOther than that, I've had no alignment issues with any of the features (zebras, focus assist, etc).
What about playback with crop marks? Doesn't extend fully on my DP6. Great while recording though.
I've had a couple of times the freeze people have mentioned that's fixed by removing the battery. They were on shoots though and i didn't have time to try figure out reproducible steps. I did notice on a music vid shoot last week that a couple of times i turned the camera off and the led that flashes with card activity kept flashing for at least a minute after turning off so i removed the battery to stop it. What does that mean?
Otherwise, ML peaking through the DP6 (with dp6 peaking on) was kicking ass. Got a heap more useable footage because i was able to rack focus on the fly with pretty good success (80-90% of the time) without blocking/rehearsing or marking the follow focus. Thank you Alex and the team! Add Higher bitrate (or whatever my lexar 1000x's can handle) and this camera would really kick ass for me thanks to ML. :)
So givin all the info on the benchmark tests being done, i asume the 5d3 is powerfull enough to handle true resolution of HD (at 2.35:1)
80+MB/s is really stinkin fast! (Doesnt 80MB/s = 640mbs? is this right?) Can it sustain this for more than a seconded or 2?
PLEASE correct me if im wrong.
If this is acurate then shame on canon for truely limiting this beast! (i know im sounding spoiled) Sounds like from this that theres plenty of processing speed for canon to have included a 1080 mjpeg or something that resoves better. This makes me sad/excited all at once.
Thanks everyone for all your hard work! Once im more confident in my knowledge of software/firmware i will no dought be donating and running ML. I dont quite trust myself to test yet.
This is working extremely well so far. Can't wait to get autoboot. That will make this usable in production environment. Please give that to us soon! You will make many of us extremely happy.
Just curious - last week you'd mentioned possibly having Alpha2 ready this week? Curious if that's still a possibility
Have a shoot this weekend, and a bit drooly at the possibility of shooting a version of an outdoor scene with HDR (which you'd also mentioned possibly coming in Alpha2) and seeing how it goes. No pressure though - haha - your work is SO appreciated!!!!!!
I'll do my best - because that's what I promised :P
Alex please make it auto load......
please~~~~~~~~~
See the 7D thread => no.
In the new releases, can we try a kind of RAW file for video? I mean, something like ARRI or RED cameras in 5D III. I was thinking, if the camera take RAW files from photos, with out the post processing color from sensor, maybe we can get each frame in raw files, 1920 x 1080. And we are the champion, my friends. See you!
Quote from: budafilms on October 19, 2012, 10:04:28 AM
In the new releases, can we try a kind of RAW file for video? I mean, something like ARRI or RED cameras in 5D III. I was thinking, if the camera take RAW files from photos, with out the post processing color from sensor, maybe we can get each frame in raw files, 1920 x 1080. And we are the champion, my friends. See you!
Yeah, that's something new. Nobody thought about th... oh wait...
::)
If you continue with such impossible requests, I think I'll go back to development on entry level cameras.
Quote from: a1ex on October 19, 2012, 10:12:27 AM
If you continue with such impossible requests, I think I'll go back to development on entry level cameras.
I agree, everyone needs to stop asking for these impossible features, let the man do what he does best. The 5D3 is not an ARRI or RED camera, whatever features can be unlocked will be.
Every time we make an absurd request, it's probably making Alex frustrated and not want to work on the 5D3 anymore, so lets lay off him for a little.
Perhaps a little patience and appreciation for the all hard work Alex & others have put into ML would be more constructive than pestering for features that are beyond the hardware capabilities of current Canon DSLRs.
I would be very grateful to eventually have ML 2.3 features working on the mk3.
Thanks guys.
I'm pretty much ready with alpha 2 testing and tweaking, and if there won't be any major quirks, I'll announce it tonight. Can you take a quick look at it?
edit: see first post for download.
Quote from: a1ex on October 19, 2012, 01:34:03 PM
Thanks guys.
I'm pretty much ready with alpha 2 testing and tweaking, and if there won't be any major quirks, I'll announce it tonight. Can you take a quick look at it?
download pre-alpha2 (http://a1ex.magiclantern.fm/bleeding-edge/5D3/magiclantern-5D3.pre-Alpha2.zip)
Thanks Alex !!
Quote from: a1ex on October 19, 2012, 01:34:03 PM
Thanks guys.
I'm pretty much ready with alpha 2 testing and tweaking, and if there won't be any major quirks, I'll announce it tonight. Can you take a quick look at it?
download pre-alpha2 (http://a1ex.magiclantern.fm/bleeding-edge/5D3/magiclantern-5D3.pre-Alpha2.zip)
Thank you a1ex!!! My 5D Mark Free thanks you too :D
Thanks ! I will try it right now!
No problems here with Alpha 2. I like Magic zoom since it has enough cpu and is smooth; no flicker with no other features are enabled. I really like focus peak, specially RAW Type, it makes it so easy to focus under low light conditions. Congratulations on this piece of art!
I will wait for final realeas to comment on bugs if any.
Good job ;D ;D ;D
Yea! alpha 2! cant wait to try! so is the 5d3 skipping 2.3 goin into 2.4? or is it going to join the 2.3 club first?
Works really well, I have a gig tonight that i'll be using it on.
Thanks Again !!
Thanks Alex for your work ! That's nice :)
Yay! I'm writing the release notes :P
Just tried HDR in 720P 60fps. Worked great. I am sure it was discussed before, but it makes you really hope fore 1080p 48fps. Not sure how doable that is though. I will try HDR in 1080P 30fps and conform it to 24fps with twixtor.
Gradual iso worked great also. It was very smooth. Only issue I had with it was it didn't seem to matter that I had set iso limit to 6400. Still I can this feature will become your friend if you are a docu/event shooter.
Thank you, Alex, so much for your work!
I'm gonna test it for real tomorrow, with some anamorphic lenses. Did a quick test today and it worked great.
I noticed some lag in LV when CPU rates are too high. Had to disable some stuff.
Focus peaking has some other modes I've never noticed in previous versions, that are good, but drain a lot of CPU too.
Anyway, congratulations guys! By the end of the weekend I'll post some more thoughts here about the new alpha.
Yes, the new focus peaking modes will slow down LiveView, I think at around 15-20 fps. Needs some heavy code optimizing... or maybe a faster processor.
Thanks Alex for Alpha2
I could load it on my (good) EyeFi card and everything went well with WiFi and ML working
I love focus peeking in gray scale
I have tried magic windows for pictures and all its settings but it seems quite buggy, maybe I am doing something wrong
I cannot get the 2 windows to align when focused and the other settings do not seem to work
Thanks again for your hard work
E
The full screen magic zoom doesn't use the advanced settings, only the small zoom boxes can use those.
Split screen is heuristic, not 100% accurate.
Quote from: a1ex on October 19, 2012, 10:13:50 PM
Yes, the new focus peaking modes will slow down LiveView, I think at around 15-20 fps. Needs some heavy code optimizing... or maybe a faster processor.
Is the DIGIC 5+ slower than the old er cpu?
A automatic white blalance would help extremely in the next release. Press a button in front of a greycard to get the right celvin values :) Is somethimng like that planned?
Quote from: tob on October 20, 2012, 11:56:52 AM
Is the DIGIC 5+ slower than the old er cpu?
Digic IV is even slower with new peaking modes
Quote from: JoeRender on October 20, 2012, 12:09:34 PM
A automatic white blalance would help extremely in the next release. Press a button in front of a greycard to get the right celvin values :) Is somethimng like that planned?
ML already has one-click WB. I have no idea if it is enabled on the 5D Mk III but you can check in the exposure menu by going to the white balance sub-menu (if there's one)
edit: nope, it's not enabled yet
Thank you Alex!!! Will try this out tomorrow. :)
It's not in this alpha for safety reasons, but in the source code it's enabled on the RATE button.
Is there any chance for a 1920x1080 (16:9) clean hdmi out on the 5dMkIII?
great.
perhaps its also possible to implement some preview for 1.5 crop factor :) as for usage with an iscorama lens..
thank you.. that firmware looks really promising.
re
You can create a custom cropmark for that
hello alex,
i mean, that the image will be unsqueezed like the anamorph 1:2..
iscoramas have a squeeze factor of 1.5
thank you.
greeets. rene
... just choose it from the menu ...
My 5D Mark III is very hot after 15 minutes of magic lantern,
CMOS Temperat: 196
is that many?
This is AMAZING. Just loaded it this morning and tried the HDR Video. Flawless. This is so, so, so awesome. Thank you so MUCH for the quick Alpha 2 release.
Very patiently waiting for autoboot. :) I looked in the 7D thread but couldn't find the reason for no autoboot? Could someone reiterate it for me pls?
Nice!
The reason for not enabling autoboot (and most photo features that require properties) is that it changes the ROM contents. Considering the camera price... it's not something funny.
Sure, most USB controller apps change properties as well, but I've experienced bad things - see http://magiclantern.wikia.com/wiki/Unbricking
Thanks Alex. So this is primarily a safety pre-caution, until enough collective testing mileage has been done?
Yes.
I read that alpha 2 will supply uncompressed feed out of the HDMI port at 2.35:1 is this correct?
Also, is there a way to format the card with the Alpha build? Or do we have to delete the images one by one(or on our computers)? I dont see the option to format the card while keeping magic lantern(in the camera)
The way I do it is to use a small SD card (512MB in my case) to store ML files and record all production clips to the CF card. This way you don't have to rely on any fancy formatting of the cards.
I also added the firmware update menu item to my Quick menu. So it's a quick load when I boot up.
Alex,
Is there any way to set iso limit with gradual iso turned on? If no, would it be possible in the future version?
Quote from: rosso_corsa on October 21, 2012, 01:32:53 AMI also added the firmware update menu item to my Quick menu. So it's a quick load when I boot up.
I already have a separate SD card just for ML and record to CF's.. but the above is an obvious and good idea that slipped me by, thanks! Also, a warning to others to check which card is being used often.. i had one instance where my card filled up much sooner than i expected only to realize it had been recording onto the SD card instead of the CF!! :-[
About to test Alpha2, thanks again ML team!
Had a quick play with Alpha 2 just now, very cool! Thanks Alex and ML team!
A few things i noticed (if they've already been noted i apologize!):
• Crop marks on playback - setting my DP6 to "C Playback" and the cropmarks appear to be scaled correctly now (except for maybe a pixel width alongside the sides not long enough), until i navigate the playback controls and actually hit play. You end up with the old view of the cropmarks not scaled properly and on occasion i had the top of the new scaling PLUS the old scaling being drawn simultaneously.
• Focus Peak - if i change from "blinking dots" to "fine dots" it ignores my selection of colour and stays red, plus the left side of frame tends to light up with red dots for no apparent reason - Not sure if the red colour is intended or not, just reporting incase. :)
• Magic zoom - disabled via HDMI - has this always been the case with ML? Would love to use it with my DP6 but understand if it's not really possible. I did notice with magic zoom that when not recording the overlaid zoom image appeared fine, but when i hit record it would start to flicker a little on and off. Nothing dramatic but enough to be distracting. To be expected? I ran with CPU usage being displayed and it actually uses less CPU (during recording) when i turned on magic zoom since peaking gets disabled which seems to use much more CPU. Also a feature request, what are the chances of a mode where if you move the focus ring the magic zoom appears, then timeouts to disappear after focusing is left for a bit? (probably requested/implemented before and i apologize if so - i'm new to ML!)
• REC/STBY Notif - Red crossout - stays on screen even when record is pressed. REC/STBY mode - when pressing record the red box and "REC" only cover the "TBY" of "STBY" overlay so you see "SREC" with a red box around "REC".
Only things i've played with so far and have to get back to work now, but if this has all been covered before then i apologize again! If video footage of any of this would help, please let me know!
Thanks again all!
Really awesome work to all involved!
I have once question, will the clean hdmi out allow external recording via, say an atmos ninja or ninja 2?
OK so maybe two questions.
Is that one way we get around the codec issues and low bit rates and unleash the ability of the sensor.
Im a 'newb' when it comes to this stuff but it seems to make sense in my head lol
Donation on the way!
Alpha 2 is generally great but noticed green bars in magic zoom don't seem to be working.
Quote from: csound on October 21, 2012, 08:56:20 AM
Alpha 2 is generally great but noticed green bars in magic zoom don't seem to be working.
I noticed that too but it was my first time using magic zoom so wasn't sure if it was user error or not.
Now that I am back from travel I will test it more accurately than I was able on tour.
I also had no green bars on magic zoom, peaking causes a red bar on the left of the screen.
I will film today and see what comes next.
Pretty stable by the way!! I remember some troubles with the first 550 versions, really good job, I really appreciate that!
Oh- when I did th card benchmark the cam turned off after a while an I had to wake it up, there was no text about the speed. Maybe I did something wrong, check it again later
Just did an HDR test. Has anyone else experienced blinking video continues when the video has been transferred to Adobe Premiere? Is there a step i am missing?
Hey Alex,
thank you so much for your great work.
I was lookig for another post of the Issue that ML is gone after turning the Carmera off oder taking the CF Card out.
I put the Alpha 2 on the SD Card. If I reinstall ML the Settings of ML are still Saved.
Thanks
It's not an issue, it's a feature. The alphas have autoboot off but still store ML settings to the CF (?) card
Quote from: blueranger1980 on October 21, 2012, 10:46:50 PM
Just did an HDR test. Has anyone else experienced blinking video continues when the video has been transferred to Adobe Premiere? Is there a step i am missing?
Did you read the user guide? You need to use the AviSynth / Virtual Dub workflow to separate the two different exposures into different streams, recombine them as a new HDR stream, and then interpret those stills as video. This doesn't happen automagically.
Quote from: dude on October 21, 2012, 10:48:31 AM
Now that I am back from travel I will test it more accurately than I was able on tour.
I also had no green bars on magic zoom, peaking causes a red bar on the left of the screen.
I will film today and see what comes next.
Pretty stable by the way!! I remember some troubles with the first 550 versions, really good job, I really appreciate that!
Oh- when I did th card benchmark the cam turned off after a while an I had to wake it up, there was no text about the speed. Maybe I did something wrong, check it again later
Alpha 2 is awesome, can't imagine needing anything else out of this camera (aside from maybe higher bitrates or mjpeg codecs, but I know this is a hail mary). All of the features seem to work for me except the "magic zoom" green bars. Would be awesome to have them, but with focus peaking and magic zoom both enabled it's easy to switch between the two and utilize them individually. Really great work here.
I like that it doesn't autoload too by the way. It makes me feel like it's less dangerous. If possible, I would love to never have to autoload. Even in an "official" release. I can't believe Canon doesn't pay you guys. Absurd. I'm emailing them now.
Hey Alex,
thank you so much for your great work.
(http://s019.radikal.ru/i603/1210/fb/aab3de117ba0.jpg)
CF x133 16gb Ok? :)
I guess so, my card is 400x and i can do almost 30Mb/s max on my 50D so i guess yours is a good result.
Thank you! ;)
Well, unless you have a 1000x your result is pretty good actually
Gradual iso worked great also. It was very smooth. Only issue I had with it was it didn't seem to matter that I had set iso limit to 6400. Still I can this feature will become your friend if you are a docu/event shooter.
+1 Worked so well started giggling like a little schoolgirl!!
+1 Still experimenting with the Peaking options (which I adore) Testing on a 100mm Macro - Wow!!!
Same thing with green bars on zoom but candidly with peaking this good...
Seriously you guys.. All this AND the 7D simultaneously?!?! Wow, thank you, thank you, thank you. I've renamed my kid Magic and my dog Lantern. (ok not really, but I did giggle like a schoolgirl) ;) ;)
Damn Canon for moving the bloody zoom to the left...
What's the point for limiting the gradual ISO limits? (since it's manual...)
No point at all in my opinion - Went from bright daylight to under a desk to 12,800 and still looked great! THATS pretty darn awesome!
Quote from: a1ex on October 22, 2012, 03:45:09 PM
What's the point for limiting the gradual ISO limits? (since it's manual...)
Having this gradual ISO and ISO limit work together will enable the usage of auto ISO when necessary.
There are times I have to go in and out of a place. When I do, not only I have to attach/detach a variable ND filter, but also I have to adjust ISO quite often. Point is, if gradual ISO works with hard limit I set (100-6400), then I can set it to Auto ISO, turn gradual ISO turned on, and I am pretty much free to go in and out.
I think it would be great if possible.
BTW, with peaking, magic zoom, and zebra, I have no need for an evf! Thank you!
Gradual ISO is only manual - it actually turns off when you enable auto ISO.
Quote from: a1ex on October 22, 2012, 05:19:46 PM
Gradual ISO is only manual - it actually turns off when you enable auto ISO.
Ahh.. my mistake. I thought this gradual ISO was to enhance and smooth out even in auto iso mode.
I will test this feature again in manual ISO with silent control on. Thanks.
A lot of users are asking about the clean HDMI out. Alex can you clarify whether it is pre or post compression?
As mentioned in release notes - overlays are erased, nothing more. The rest is up to you to find out.
(http://i.imgur.com/levhq.jpg)
Not sure if this is going to work but I had the chance to run a speed test on a 1000x cf card.
The write speed is pretty impressive.
Big thanks to mnteddy for help with the image insert!
Hi Alex,
Thanks for the update on the HDMI, Ive just ordered an Atomos Ninja 2 to test the HDMI.
If anyone has any advice or thoughts for the tests I'm all ears, it should be here this weekend or early next week at the latest.
Is it just a case of we don't know if its uncompressed, is the only way to tell to do some recording?
Thanks again all for your hard work. To be able to sell my plastic GH2 and just use the 5D mkiii would be a pleasure!
This on a 32G lexar cf 1000x card :o
(http://i.imgur.com/kahyD.png)
1000X card is almost 2x speed of SD cameras, wow.
Hey Odlan,
Nice speeds!I have a question for ya, was the CF card the only one installed in the 5d? or did you have a SD installed as well?
Thanks
So far every things working for me! Love it!
I have a question. Does the alpha version completely leave the camera when you turn it off. i have to send it into canon soon.
hi,
Magic Lantern on Samsung sd. Anyway the benchmark is performed whitout liveview running.
In liview mode the result of the test is identical to your.
thanks I was wondering about the set up and difference in speed.
Hello guys,
maybe this is a very stupid question. I own a 5dMIII and would love to run ML alpha 2 , but when i download this from the link in the first post I think it misses some files. I ownly see the map ML / ml-5D3-113.fir and userguide.pdf. There is no execute bin files or whatever this guys says on youtube. My camera is on firmware 1.3, formatted the card like all the steps you and the youtube movies says.
I looked up on youtube how to install it, but they have much more files. Am I doing something wrong? Maybe someone could please help me.
Ivo
QuoteAm I doing something wrong?
Yes, you are trusting the guys on youtube more than our install guide.
FYI, Magic Lantern was not written by the guys on youtube.
100% :D
Quote from: ivoborkus on October 23, 2012, 10:50:36 AM
Hello guys,
maybe this is a very stupid question. I own a 5dMIII and would love to run ML alpha 2 , but when i download this from the link in the first post I think it misses some files. I ownly see the map ML / ml-5D3-113.fir and userguide.pdf. There is no execute bin files or whatever this guys says on youtube. My camera is on firmware 1.3, formatted the card like all the steps you and the youtube movies says.
I looked up on youtube how to install it, but they have much more files. Am I doing something wrong? Maybe someone could please help me.
Ivo
Simply
1- Format your card in fat32
2- Download magiclantern-5D3.113.alpha2.zip on your desktop
3- Unzip magiclantern-5D3.113.alpha2.zip on your desktop
4- Move in the new folder magiclantern-5D3.113.alpha2 on your desktop
5- Copy all the files and folder, as they are, in your card
6- Remove your card from your computer and insert in your Canon 5D Mark III
7- Turn on your Canon
8- Move in Canon menu and do firmware update
Quote from: mixmastermike on October 23, 2012, 12:34:15 AM
If anyone has any advice or thoughts for the tests I'm all ears, it should be here this weekend or early next week at the latest.
Try recording something with bright red colors, zoom in and compare it with the files from the CF. Try recording something in zoom mode on different iso. Also try recording with and without the CF. Would be nice if you uploaded the files so everyone could play with them.
I tried to do the tests yesterday but turned out my blackmagic was faulty :)
Hi guys, you checked this: The next Canon Firmware Update will include clean HDMI UNCOMPRESSED out.
Quote from: dude on October 23, 2012, 04:00:01 PM
Hi guys, you checked this: The next Canon Firmware Update will include clean HDMI UNCOMPRESSED out.
is it april fools already?
The new firmware update will be available, at no charge, in April 2013 from the Canon U.S.A. website and can be downloaded by end users or through Canon Factory Service Centers.
ogo! :o
- Tell what working temperature? it seems to me that at temperature 191 and above Cenon goes mad :(
I read the announcment on canons site about clean uncompressed hdmi. but why april 2013! by then ML will probably have the 5d3 recording uncompressed to the cf card ha ha. April 2013 thats all they got? very lame in my opion.
They need to test it properly, not like us ;)
And judging by the timeframe, this isn't a feature they planned in the first place :/
Quote from: hjfilmspeed on October 23, 2012, 06:27:11 PM
I read the announcment on canons site about clean uncompressed hdmi. but why april 2013! by then ML will probably have the 5d3 recording uncompressed to the cf card ha ha. April 2013 thats all they got? very lame in my opion.
link to the official site please :)
found it sorry http://usa.canon.com/cusa/about_canon/newsroom?pageKeyCode=pressreldetail&docId=0901e024806daf9c
www.nikon.com ;)
I wonder how much of this announcement (6 months in advance) has to do with the work you guys are doing. Why not announce it just before launching it? they were feeling the heat for sure.
6 months tells me they are trying to figure it out, hope to bump up the sales and hold the sales towards other cameras BMC, the LEICA coming out around that time etc.
Quote from: a1ex on October 23, 2012, 06:33:10 PM
They need to test it properly, not like us ;)
yeah right alpha 2 is working great fro me! i plan to donate asap! also i believe that canon is feeling the heat from ML.
Quote from: a1ex on October 23, 2012, 07:10:04 PM
www.nikon.com ;)
haha!
Quote from: Kabuto1138 on October 23, 2012, 07:47:44 PM
I wonder how much of this announcement (6 months in advance) has to do with the work you guys are doing. Why not announce it just before launching it? they were feeling the heat for sure.
6 months tells me they are trying to figure it out, hope to bump up the sales and hold the sales towards other cameras BMC, the LEICA coming out around that time etc.
ML should just start posting all sorts of stuff. then canon will will have more announcments to make ;) jk
Well Cannon April 2013 just isn't going to cut it for clean hdmi...
In my opinion this is a fatal error by you business strategy team, they should all be fired.
The Mayan Calendar has already told us the world is going to end in December, why would I wait till 2013 when Ill be dead. In fact I better start filming now otherwise how ever will I pay for my Homer Simpson like beer addiction....
Do we have any users called cannon reading this forum...
QuoteML should just start posting all sorts of stuff. then canon will will have more announcments to make ;)
Such as... cease and desist letters?
If canon is reading then they would be wise to add 1000 lines of hd (as advertised) to the 5d3 befor they add umcompressed hdmi. In april theyll tell you, in small print, that the hdmi only records to a special canon recorder that costs 15k. ugg canon makes me so frustrated right now. ML ROCKS!
Quote from: a1ex on October 23, 2012, 08:35:41 PM
Such as... cease and desist letters?
Then ML lovers everywhere will rally against the tryrant! >:( jk
i know i know i realize my demands are not realistic im just spoiled now. and again I LOVE ML and i would not want that. Thank you again!
Hi Guys,
this morning i was very happy to receive the news of clean HDMI output!
I ask a suggestion.. in case the new ML will be capable of increasing bitrate,
do you think a 90mb/sec or 600x CF card is enough to increase the bitrate considerably?
i am travelling close to USA and i can do some shopping..
thanks!
JUST DONATED! Finaly ha ha im cheap
Quote from: mixmastermike on October 23, 2012, 08:21:36 PM
The Mayan Calendar has already told us the world is going to end in December, why would I wait till 2013 when Ill be dead.
Hehe, so what does it matter if you shoot it all in 4:2:2? Nobody is going to be around to watch your nicely graded film.
I have the Alpha 2 on the SD Card and had the firmware updated
but the text of magic lentern is smaged and not readable,
otherwise on video mode I can see the audio bars and histogram working.
Any idea what is going on please ?
So umm... beat them to it? Their customers demand it. Then we compare implementation and see whose is better?
QuoteSuch as... cease and desist letters?
From what indy says and CHDK's actions I have doubts. And Canon: feel free to copy/better my code, please. I just want better and more popular cameras, holy crap you'll make money that way and even have some of mine. Listen to your customers and release a fully featured software product that fully utilises your hardware. Not next year, this year for all your cameras. But I'm not holding my breath, I should even say I'll cook up and eat my shoe like Werner Herzog.
i got no reply.. but i could t resist and i bought a lexar pro 1000x, if it will be possible to increase the bitrate this card would help.
I am wondering how many stops more of dynamic range you can get when you process an uncompressed hdmi signal..
any clue?
QuoteAnd Canon: feel free to copy/better my code, please.
That was actually Trammell's dream when he started the project: "It would really please me if Canon incorporated all of the features from Magic Lantern into their firmware." ( http://www.cinema5d.com/news/?p=403 ). Of course, it's very nice to see them listening to customers (even if they can do better).
A lot of ML tweaks were disabled on 5D3 because they are simply not needed, Canon already did them (e.g. fast playback zoom, or movie recording with shutter button).
My point was that we shouldn't push things too much - if we start to turn the 5D3 into a C300, for example, their attitude may change to "hostile". We already have a golden rule: whatever we do, we don't copy Canon code in our software. So if Canon adds feature X, this doesn't mean that we'll copy it to the other cameras.
a1ex
100% Respekt!!! ;)
I totaly agree with a1ex on this one. I am not deffinetly not looking to turn the 5d3 into a c300 tho. it just would have been nice for canon to have seperated from the pack lil and give the 5d3 1000 lines. even if it did it at super 35 crop. im not trying to badger canon cuz i like shooting with my 5d3 i just want to love shooting with it. the fact that il have to buy a recorder and batteries and rigging when i could be focusing on lenses is making me like it less. I think it would have much been wiser for canon just to focus on the in camera recording first. and im not asking these things of ML either im asking them of canon. If your going to put something in the works by april, canon, please let it be a better codec or something not just hdmi stuff. its a mini hdmi anyways and seems kinda scary to record off of. maybe im way out of line but it just seems there are more simple ways of pleasing the 5d3 crowd and this would drive there lense sales more too. :-\
What is the frame rate out of HDMI? Is it true 60i?
CBR for the mk3?
Quote from: 1% on October 23, 2012, 05:00:10 PM
I don't think this feature exists in the HW encoder.
Damn! :(
Thank you !!!
Great release once again. Smooth transitions is already a favorite of mine !
Would it be possible to record video to card 1, and let say images on card 2 ?
Be able to change volume level recording on left channel and right channel separately ?
Keep the crop marks during playback ?
Watch out Canon, ML is here !!!!!
I just see no point in releasing new cameras and not adding new features. Everyone else tries to push in their products. How can you push hardware and say screw it to software. We don't have to copy their code, the features would be implemented all different.
HDMI out should have been 1080p from the get go, otherwise why even spend the money on the HDMI processing and the connector. Just who needs not HDMI the way it is now? Its not just that you can't record from it, its that its just as blurry as the SD out. Even if they left off 4:2:2 they should still have kept it real size in idle. I don't think it will ever work while recording because of hardware limitations (esp, digic IV). We'll never be a C300 because the 30 minute limit appears hard-coded and the cameras overheat. The crop sensors and even the full frames aren't like a full professional camcorder. Genlock and things like that are also hard to implement within what the hardware can do. The DSLRs can only complement and moonlight as cinema cameras.
In fact, C300 and others can't do what things like red/arri/bmcc can at lower/similar prices. 1DC will be their first effort but it seems a bit late. People are recording uncompressed from GH2 right now. How many GH2s + recorders can you buy for 1 5dIII? How can they be mad about features they don't have and don't really sell. CHDK gives raw to point and shoots and they're still selling the DSLRs. They need to give full HDMI to all cameras going back as far as 550D. 5dIII should be shooting 2k with full clean HDMI at the price its selling anything less and people will go elsewhere at this point unless their main focus is stills. But how long before that goes to nikon or someone else?
Quote from: 1% on October 24, 2012, 11:37:17 PM
I just see no point in releasing new cameras and not adding new features. Everyone else tries to push in their products. How can you push hardware and say screw it to software. We don't have to copy their code, the features would be implemented all different.
HDMI out should have been 1080p from the get go, otherwise why even spend the money on the HDMI processing and the connector. Just who needs not HDMI the way it is now? Its not just that you can't record from it, its that its just as blurry as the SD out. Even if they left off 4:2:2 they should still have kept it real size in idle. I don't think it will ever work while recording because of hardware limitations (esp, digic IV). We'll never be a C300 because the 30 minute limit appears hard-coded and the cameras overheat. The crop sensors and even the full frames aren't like a full professional camcorder. Genlock and things like that are also hard to implement within what the hardware can do. The DSLRs can only complement and moonlight as cinema cameras.
In fact, C300 and others can't do what things like red/arri/bmcc can at lower/similar prices. 1DC will be their first effort but it seems a bit late. People are recording uncompressed from GH2 right now. How many GH2s + recorders can you buy for 1 5dIII? How can they be mad about features they don't have and don't really sell. CHDK gives raw to point and shoots and they're still selling the DSLRs. They need to give full HDMI to all cameras going back as far as 550D. 5dIII should be shooting 2k with full clean HDMI at the price its selling anything less and people will go elsewhere at this point unless their main focus is stills. But how long before that goes to nikon or someone else?
Yes 1000000000000000% agree! I should have waited to see reviews first. i was under the impression the all-i feature was gunna rock. oh well. Just a pro still cam to me. I really was hoping for more "pow!" from the 5d3. especialy after seeing what hd realy should look like. sorry but thats how i feel.
This is an interesting read by the way:
http://www.eoshd.com/content/9140/interview-with-canons-mike-burnhill-on-the-canon-1d-c-4k-dslr
Panasonic's thoughts on GH2 hacks:
- It's like a great car--you just want to soup it up and do even more with it.
Darin Pepple, Senior Product Marketing Manager, Imaging at Panasonic Consumer Electronics Co.
Quote from: 1% on October 25, 2012, 12:18:15 AM
Panasonic's thoughts on GH2 hacks:
- It's like a great car--you just want to soup it up and do even more with it.
Darin Pepple, Senior Product Marketing Manager, Imaging at Panasonic Consumer Electronics Co.
Thank you exactly! And the gh2 resolves great as is! ugggg please canon! canon u imagine ML plus 5d3 plus 1000 lines---> joy overload! haha
I read that linked interview.
Quote4K is still in the early stages of growth
Bullshit, what is the resolution of scanned film?
While they did hack MB up a bit and ask the tough questions, he doesn't seem to like his users very much unlike Panasonic.
Quote from: hjfilmspeed on October 25, 2012, 12:36:59 AM
Thank you exactly! And the gh2 resolves great as is! ugggg please canon! canon u imagine ML plus 5d3 plus 1000 lines---> joy overload! haha
Maybe that's what Canon is working on. I hope we are not waiting 6 months for just removing overlays and pillar boxes. One can hope, right?
Right! i hope! also i agree 1% that eoshd.com is a lil harsh against canon at times. they seem a lil jaded. But they do dig up some interesting stuff. a1ex is also right. canon does listen. but they do so just a lil at a time. its like sd cards. they need to make as much money off them as possible other wise we would see 2tb sd cards on the market for the price of 16 giggers. in the same token panasonic seems to listen more i guess. gh3 with 1080 60p or gopro hero 3 with 2k? the market is so crazy right now. And dont say "then buy a gh3" I like the look of the 5d3 and the low light abilities are a force to be reckoned with. But why have all that then top it off with poo rez. there must be a way to better sample the image. look at its s2 jpeg. tack sharp! true 1000 lines makes a hudge difference not only in natural sharpness but it grades way better too! if there is noise its much finer as well. Im not asking for 4444 sony f35 65 raw intense 3D core what ever just a naturally sharp images. And please why say 90mbs if more then half the time it sits at like 30 or so. It should have been ibp codec for (consumers or realy long shoots) and then a pro codec outside of h.264 but inside its processing power. oh boy another rant of mine. Im gunna get kicked out of here huh. :o Again none of this i expect from ML. They have done plenty in my opinion.
Quote from: hjfilmspeed on October 25, 2012, 04:06:42 AM
Right! i hope! also i agree 1% that eoshd.com is a lil harsh against canon at times. they seem a lil jaded. But they do dig up some interesting stuff. a1ex is also right. canon does listen. but they do so just a lil at a time. its like sd cards. they need to make as much money off them as possible other wise we would see 2tb sd cards on the market for the price of 16 giggers. in the same token panasonic seems to listen more i guess. gh3 with 1080 60p or gopro hero 3 with 2k? the market is so crazy right now. And dont say "then buy a gh3" I like the look of the 5d3 and the low light abilities are a force to be reckoned with. But why have all that then top it off with poo rez. there must be a way to better sample the image. look at its s2 jpeg. tack sharp! true 1000 lines makes a hudge difference not only in natural sharpness but it grades way better too! if there is noise its much finer as well. Im not asking for 4444 sony f35 65 raw intense 3D core what ever just a naturally sharp images. And please why say 90mbs if more then half the time it sits at like 30 or so. It should have been ibp codec for (consumers or realy long shoots) and then a pro codec outside of h.264 but inside its processing power. oh boy another rant of mine. Im gunna get kicked out of here huh. :o Again none of this i expect from ML. They have done plenty in my opinion.
I agree 100% about the resolution. I also would rather have better resolution than HDMI. I am not sure if resolution can be changed through a firmware update, but hopefully, I mean, HOPEFULLY, that is a part of improvement that will come after 6 months.
And i realy think canon should also add a type of "canon log" profile to the 5d3 as well. IMO canon should make dedicated products with clear cut descriptions of what there capable of instead of a billion broad and vague products. ok i swear im done for now.
Back to Alpha 2. Ive loaded it a bunch of times with custom canon settings and have yet to experience a lock up. Love the grad expose to so smooth. Great work!
Guys, do you think 422 in 8bit will help with the grading? Greenscreen - yes. But grading? I'm really not sure. I've tested some d800 footage compared to the ninja. Even with it's lower bitrate if holds up pretty nicely. 422 10bit - now that's cool ;)
Quote from: Lcrusher on October 25, 2012, 10:27:46 AM
Guys, do you think 422 in 8bit will help with the grading? Greenscreen - yes. But grading? I'm really not sure. I've tested some d800 footage compared to the ninja. Even with it's lower bitrate if holds up pretty nicely. 422 10bit - now that's cool ;)
That's what I'm thinking too. How much of a difference will it make? Does it worth spending extra $1,000? Can some one share their experience with Ninja and 8 bit 422 vs 420.
Quote from: DTSET123 on October 25, 2012, 10:39:46 AM
That's what I'm thinking too. How much of a difference will it make? Does it worth spending extra $1,000? Can some one share their experience with Ninja and 8 bit 422 vs 420.
Right well the only thing i could liken it to is the c300 and thats 422 8bit which looks amazing but again if they dont fix the rez output then to me its not worth it at all.
it would be much smarter to just up the rez in camera 1st. then people will be able to invest that 1000+ $ in canon glass instead. After seeing what hd should look like you realy long for it and if your going to put blood sweat and tears into your projects no dought you want the rez you were told youd get. im not sure how you round up slightly over 720p to 1080p. just not cool in my book. not for $3500 Ive sent this to canon. we all should!
Quote from: a1ex on September 07, 2012, 04:51:40 PM
Features:
- Anamorphic and fisheye correction
Will defishing be available to recording. Now it only shows in LV and does not show in HDMI?
It's pointless, you can defish in post-production with much better results
Well the 8 bit, 4:2:2 will help and is possible in camera once untethered MJPEG is figured out. Its better than nothing. All of these cameras have resolution <1080P. What is the real line count on C300?
Want to test how much better it is? Record a 1080p clip and take a silent pic while recording. Match the 2 frames and grade them.
Exactly 1% I did a strait up comparison between all-i 1080 and a s2 jpegs at 6fps (down sampled in camera but sequenced in 24p time line in post) NIGHT AND DAY! The rez is there, its just a matter of achiveing that at 24p. from all these benchmark tests it seems like the 5d3s got the power. maybe my math is off but i feel like canon could totaly provide a 1080 mjpeg on the 5d3. even if we went back to shorter clip lengths. heck id take a few minutes of that at this point. This is not a feature i expect from ML as i said they have done enough. i would expect it from canon.
Quote from: hjfilmspeed on October 25, 2012, 07:27:06 PM
Exactly 1% I did a strait up comparison between all-i 1080 and a s2 jpegs at 6fps (down sampled in camera but sequenced in 24p time line in post) NIGHT AND DAY! The rez is there, its just a matter of achiveing that at 24p. from all these benchmark tests it seems like the 5d3s got the power. maybe my math is off but i feel like canon could totaly provide a 1080 mjpeg on the 5d3. even if we went back to shorter clip lengths. heck id take a few minutes of that at this point. This is not a feature i expect from ML as i said they have done enough. i would expect it from canon.
maybe the cpu cannot resize the image like s2 jpeg 25 times a second. I mean that's why the 1d has dual processors (for the burst).
The 300c has a different cpu.
I got confirmation that my ninja 2 arrives this Friday by the end of day.
With respect to any comparisons we should look at Ill be happy to shoot some test shots.
For me any solution that improves the finished product is worth it as I shoot stills and video and I would rather have a quick transfer time to my edit suite and be able to shoot stills with the same camera. A lot to ask I know but I believe we have a great chance of getting there with the talent working on this project.
Gradual exposure is one of the most useful and unexpected things I've seen in ML so far. A great feature that gives us a lot more of control in a same shot with different lighting environments!
I've tested the Alpha with lots of Canon and M42 lenses, as well as a little anamorphic work.
The LV squeeze is awesome, but it has some little problems, like, when combined with focus peaking, the peaking remains on the unsqueezed points of the image (sometimes against a black background). Also, would be great if the squeeze could be applied in Play mode as well. It does help a lot when reviewing a take to decide whether we do another one, or move to the next shot. :D
Once again, congratulations, guys! You rock.
Nice, may I ask you to prepare a few test shots with it?
I'm thinking to post an alpha 2.1 these days (same feature set, but with some redraw bugs fixed).
Canon 5dm3 is giving us about 33% less pixels. 1080 is aprox. 700 and 720 is doing 500.
This is not as it should be at the price of 3500$ + lens + batteries + CF-s . . .
And they put "full hd" info on the box. WTF??? It is HD in FHD container! And 25p :(
Iam very disappointed user. There will be more if Canon dont do anything about this.
Can you please stop bashing?
Quote from: nanomad on October 25, 2012, 06:29:26 PM
It's pointless, you can defish in post-production with much better results
I have been reading about Avisynth but there is no straight forward solution. Learning curve seems pretty steep.
Maybe Alex has develoved a zip package with all the goodies and scripts to do the math.. I love the stuff he did for HDR video, it is really amazing and it took me a few days of work to be albe to do the same on Vegas Pro 12! My hat off to Alex and his knowledge of scripting and the software packages required to do the work.
I have a script for defishing video, based on nona from Hugin. If there is interest, I can polish it and post it online.
Demo video:
Wow! That looks really good. Does it run on Windows? I think you should put a link on the User Guide, just like you did for the HDR video.
I also hope to work on the raw image process for timelapse some day when I get this fishy video stuff working and then I will also hope you can add a link to your masterpiece in the ML User Guide. All of this stuff really adds so much value to all the (amazing!) ML work you are doing.
So thanks for all the great work to all of the ML TEAM! I am learning and improving my skills so much since I downloaded ML for 7D and 5DIII.
;D ;D ;D
Quote from: a1ex on October 25, 2012, 08:45:29 PM
Nice, may I ask you to prepare a few test shots with it?
I'm thinking to post an alpha 2.1 these days (same feature set, but with some redraw bugs fixed).
No worries with test shots pm me whith any requests if work isnt too crazy this weekend Ill shoot some stuff.
Quote from: a1ex on October 25, 2012, 08:45:29 PM
Nice, may I ask you to prepare a few test shots with it?
I'm thinking to post an alpha 2.1 these days (same feature set, but with some redraw bugs fixed).
Was this meant for me? Anyway, the answer is yes! :P
Am I crazy to speculate that the reason 5D MK III has pillar boxes around HDMI output is because that is what the sensor actually resolves. We all guessed 1080 mode resolves around 800 lines and of course, Canon will never admit to this. Maybe, just MAYBE, this clean HDMI firmware HAS TO include the sensor resolving more lines in order to output 1080 image.
Back to Alpha 2. Gradual ISO works great. With MK III's silent mode, it's quiet and smooth!
At least on 600D the pillar boxes + overlay are drawn on.
The YUV buffer can be resized and at least clean SD hdmi is possible. Maybe HD too while not recording.
https://bitbucket.org/hudson/magic-lantern/changeset/a11ebaaa526fb6cf83010db69252cb7d5b57aac4#general-comments
QuoteWe all know 1080 mode resolves around 700 lines
Would you please post a reliable reference and stop talking nonsense?
The YUV sizes are really close to HD, its only a few lines off. Just when not recording the buffer is ~1000x700 and scaled up/pillarboxed. Not a hardware issue except digic can't output HD size and record HD at the same time. I think the dual processor ones can.
Quote from: a1ex on October 26, 2012, 05:51:17 PM
Would you please post a reliable reference and stop talking nonsense?
It was reported (according to Philip Bloom) to be 800 lines not 700 lines, but Philip, himself, may have been given inaccurate info. I revised my post to reflect this.
Yes, I am stopping it right now.
Quote from: Lcrusher on October 25, 2012, 08:14:46 PM
maybe the cpu cannot resize the image like s2 jpeg 25 times a second. I mean that's why the 1d has dual processors (for the burst).
The 300c has a different cpu.
I think it can get much closer anyway. closer than its current state. Also the 1d has dual digi 5s for 4k mjpeg 422 @ super 35 crop. surely the 5d3 could handle 1080 mjpeg @ a super 35 crop resolving 1000 lines. Couldnt it?
Sorry my aim was not to bash canon and i apologize for sounding that way. I got a lil to amped up i guess. I would just like know what the 5d3s potential really is. Canon reps say they want feed back and this seems to be a very loud request. Its hard not to want 1000 lines plus ML. I feel like the 5d2 opened a door for indie cinema, why try to shut it? thats all. i ment no harm i just feel in the dark about the 5d3s true potential. (of course not because of ML tho)
The Nyquist limit is 960 lines and 5D3 has 890 lines according to this test: http://www.dvxuser.com/V6/archive/index.php/t-278877.html
I guess you won't be happy even after breaking some physics laws.
Quote from: hjfilmspeed on October 26, 2012, 07:12:09 PM
Canon reps say they want feed back and this seems to be a very loud request.
He has a point. If we completely stop bitching about Canon's business practices then they will think that they have done a good job getting 5diii out to the market. If consumer is not happy and Canon asks for feedback, then it makes total sense to let them know whats wrong- after all it effects their business. What guys that just arrive here don't understand is that this is not the place to do so. This is a development site and developers here don complain about the problem they are figuring out the problem.
breaking physics laws would not make me happy, fully understanding the 5d3s true limits would. im not trying to start any winey complaining sprees either. a part of figuring out solutions is also learning about the problem. thats all i was trying to do. The nyquist limit was and interesting read and i was unaware of these issues.
i gather from whats being said is that i should assume getting sharper video (gh2 or 3 or fs100 comparable) from the 5d3 is out of the question even for canon. thats fine as i too enjoy stills.
again im trying to understand the limitations of the 5d3 and at the same time ive also been testing ML on it as well. for now i guess its best to put to rest the resolution/sharpness/clearity issue with the 5d3 as i feel its doing more harm then good discussing it. It was absolutly not my intention to irritate or upset anyone or slow down progress with ML and if i have done this i am truly sory. My future posts (ML willing) will be connected to ML alpha testing only. Sory again.
Nothing wrong with complaining, just open a thread under General or whatever. This is not the place
edit: any off topic post after this one will earn you a 24 hour ban. You have been warned.
Alex
On the Magic Window Zoom box with Split screen option, the 2 split screen windows do not move to a non splitted image when on focus. this does not seem normal and may be a bug? I know that we have discussed that one earlier, but I am not sure I understood your response about the fact that these feature is not exactly working like a stigmometer.
Thank you
Focus confirmation is only a heuristic and it's not 100% accurate. Feel free to suggest some better math for this.
Quote from: nanomad on October 26, 2012, 09:06:19 PM
Nothing wrong with complaining, just open a thread under General or whatever. This is not the place
edit: any off topic post after this one will earn you a 24 hour ban. You have been warned.
Thank you!
Im really delighted with the work you guys put into this project and will help any way I can.
I know that Canon switched the zoom button to the left but.. It would seem convienient to me if MAGIC ZOOM could be enabled by the old zoom button on the right, it is easier to use because my left hand is doing the manual focus and not conveniently available to press the canon zoom button.
Quote from: mixmastermike on October 25, 2012, 08:24:41 PM
I got confirmation that my ninja 2 arrives this Friday by the end of day.
With respect to any comparisons we should look at Ill be happy to shoot some test shots.
For me any solution that improves the finished product is worth it as I shoot stills and video and I would rather have a quick transfer time to my edit suite and be able to shoot stills with the same camera. A lot to ask I know but I believe we have a great chance of getting there with the talent working on this project.
I would be interested in knowing the frame rate of HDMI (60i? 30p in 60i wrapper? etc.) and what is the size of actual image when crop it to remove borders. Also if you could make a short comparison clip downloadable, that would be appreciated.
The old zoom button shares the same code with lots of other things (M-Fn, back wheel, lock, DOF and so on). So... lots of false triggers.
Quote from: a1ex on October 26, 2012, 11:00:02 PM
The old zoom button shares the same code with lots of other things (M-Fn, back wheel, lock, DOF and so on). So... lots of false triggers.
I noticed on 7D the Magic Zoom is enabled by other options like the shutter button. Will these options be standarized? I like the shutter option. Also like the focus ring but it does not work yet on 5D3.
Thanks
Each camera has its quirks. Focus ring works only with lenses that report focus distance (I don't have any such lens compatible with 5D3).
Quote from: bumkicho on October 26, 2012, 10:58:44 PM
I would be interested in knowing the frame rate of HDMI (60i? 30p in 60i wrapper? etc.) and what is the size of actual image when crop it to remove borders. Also if you could make a short comparison clip downloadable, that would be appreciated.
Currently sat on sofa waiting for UPS! Ill do some shooting and upload to vimeo over the weekend.
Im not sure how the Ninja 2 works yet, so as for frame rate any tips on how to obtain this is welcome.
Quote from: mixmastermike on October 26, 2012, 11:34:29 PM
Im not sure how the Ninja 2 works yet,
It seems that most of us don't know how that thing works = all eyes on you :) Waiting for your report! Thank you!
Quote from: DTSET123 on October 26, 2012, 11:57:48 PM
It seems that most of us don't know how that thing works = all eyes on you :) Waiting for your report! Thank you!
Well she's here, the batteries are taking longer to charge than bringing a nuclear power station online... hopefully this is a good sign and they might actually last....
With respect to the input source, the ninja looks to auto detect what the input is and displays it on screen. So, once the batteries are charged Ill plug her in and power her up.
I'm not seeing a BMP of the overlays when I take a screengrab, though I still get a working .422 file with the image. Coming in a later build perhaps?
Check the other card. BMP is saved by Canon code, it can't be changed.
Is it possible to temporally disconnect OLP filters just to see if they are any changes in video resolution ? Are they controlled electronically ?
Read the blogs of those who did it.
Amazing update! Thank you so much!
Tried to load from Eye-Fi card, worked 1 time only. Next were black screen. Only pulling Eye-Fi card helped.
Otherwise it's megacool. Anamorphic display is WOW.
The Eye-fy card setup seems to depend on the fact the is a lens or not attached to the body
I now run ML only with a lens attached an it is fine
My lenses have an updatable fw
Note : only the 8Gb Pro card works The 16 does not
Quote from: itsskin on October 27, 2012, 02:31:07 PM
Amazing update! Thank you so much!
Tried to load from Eye-Fi card, worked 1 time only. Next were black screen. Only pulling Eye-Fi card helped.
Otherwise it's megacool. Anamorphic display is WOW.
Yes, it stopped working after I changed to manual m43 lens. But changing back to EF didn't help.
Quote from: itsskin on October 27, 2012, 06:57:58 PM
Yes, it stopped working after I changed to manual m43 lens. But changing back to EF didn't help.
When it stop working you have to do the card and battery pull procedure to get it back to work
Yes. Didn't help though. Just came back home and changed to normal SD card.
Ok So everything's charged and were ready to shoot some test shots..
However I cant get the Ninja to sync corrctly with the HDMI, somehow I managed to get one test shot earlier today at 1080i60, but ever since then the ninja detects at 59.94, this makes for some awful results.
The EVF detects at 1080i60 Im not sure how I managed to get lucky earlier but Ill scour the web for some help on this one, if anyone has any input its welcomed. I read that there were problems with the nikons and ninja not syncing and I wonder if its a firmware issue as this was resolved in a firmware update for the Ninja and Nikon Combo.
I've also tried removing the evf from the loop and recording directly to the ninja this didn't resolve the problem.
Try changing the video system to pal(in the canon menu). Maybe it'll work better in 25 fps.
realized the Ninja wasn't on the latest firmware. updating now.....
Quote from: Lcrusher on October 27, 2012, 09:31:12 PM
Try changing the video system to pal(in the canon menu). Maybe it'll work better in 25 fps.
No luck with that one, or the latest firmware.
On the Nikons, the instructions describe a menu in camera that allows you to select the output HDMI setting thats something we cant do as yet maybe thats whats up.
In 600D firmware there are options for HDMI 1080P, 1080i, 720P, 480P/i (I think). It connects to my TV at 1080i even though it is 720P. It uses EDID data to determine this somehow. I get the same results connecting to 1080P sources. I think you might be having a similar problem and its not the recorder.
Ugh.. canon really needs to work this out.
Quote from: 1% on October 27, 2012, 09:55:58 PM
In 600D firmware there are options for HDMI 1080P, 1080i, 720P, 480P/i (I think). It connects to my TV at 1080i even though it is 720P. It uses EDID data to determine this somehow. I get the same results connecting to 1080P sources. I think you might be having a similar problem and its not the recorder.
Ugh.. canon really needs to work this out.
ugggghhh indeed, maybe 6 months is optimistic for the canon firmware update.
Anyone try using HDMI->DVI adapter?
FF1ED188: STRING: '[EDID] ColorMode = EDID_COLOR_RGB' FF1ECFD8
FF1ED1AC: STRING: '[EDID] ColorMode = EDID_COLOR_422' FF1ECFE4
FF1ED1D0: STRING: '[EDID] ColorMode = EDID_COLOR_444'
FF1ED20C: STRING: '[EDID] SELECTED DVI MODE'
Hmmm... well I just did into a 1080P TV and with magic zoom get "full size" HDMI that covers the entire screen... but those damn overlays need to go.
hmm... spoke too soon, its only outputing 480P, have to make the camera do 1080.... maybe this is HDCP related?
Quote from: 1% on October 27, 2012, 10:35:44 PM
Anyone try using HDMI->DVI adapter?
FF1ED188: STRING: '[EDID] ColorMode = EDID_COLOR_RGB' FF1ECFD8
FF1ED1AC: STRING: '[EDID] ColorMode = EDID_COLOR_422' FF1ECFE4
FF1ED1D0: STRING: '[EDID] ColorMode = EDID_COLOR_444'
FF1ED20C: STRING: '[EDID] SELECTED DVI MODE'
Hmmm... well I just did into a 1080P TV and with magic zoom get "full size" HDMI that covers the entire screen... but those damn overlays need to go.
This could be fantastic at home, no external hdmi recorder needed. I could just TiVo my recordings ;)
Try some displays which support HDCP. I don't think mine does.
Quote from: 1% on October 27, 2012, 10:48:25 PM
Try some displays which support HDCP. I don't think mine does.
I have a samsung smart tv and it worked great connecting it directly to hdmi. The picture looked good and thats on a 65 inch screen.
But was it 1080P or I? My picture looks like crap thru HDMI but have to force 1080P somehow and try DVI again, the SD even looks much better. I only have a 42" 1080P running, have a ~47 but its not 1080P + others. I remember my HV20 wouldn't display 1080P on non-HDCP enabled displays.
*OK, forced FULLHD on DVI and get 1080I (according to MZ).... fuck. Have to make it 1080P.
hold on Ill connect it now....
On 5D3, full screen MZ in 1080p shows full-screen image, 1904x1274, no pillarboxes... but the image is double. One could call it "drunk HDMI out".
(http://i.imgur.com/wbXJu.jpg)
The Samsung is showing 1080i60?
its not covering the whole screen though and I don't have the time today to count all the pixels.... so Im guessing this represents the smaller number of lines produced by the camera??
Makes me wonder if the Ninja 2 is more an Orange Belt than a real Ninja?
For me HDMI 2 = VGA, HDMI 5 = 1080i :( and 17 and 20 stretch the SD image to 16x9. How can I force 1080P? I know my TV is good for it.
Quote from: 1% on October 27, 2012, 11:32:05 PM
For me HDMI 2 = VGA, HDMI 5 = 1080i :( and 17 and 20 stretch the SD image to 16x9. How can I force 1080P? I know my TV is good for it.
Have to say Im not sure on that one, but i am going to write an email to Atomos and inquire about the issue with frame rates and the 5d mkiii.
Quote from: a1ex on October 27, 2012, 11:21:08 PM
On 5D3, full screen MZ in 1080p shows full-screen image, 1904x1274, no pillarboxes... but the image is double. One could call it "drunk HDMI out".
Too much sake for the programmers?
On 600D, full screen MZ has problems in crop mode. I think the magnification is some sort of fixed path and expects certain input size/pitch. In 480P MZ doubles as well. If this sizing stuff is figured out to some extent it might help with controlling MZ too.
Have you ever had it 1080P on any display? Does forcing fullHD on 5dIII have different values? Or is this a product of only 30fps frame rate?
Technically EDID_COLOR_444 exists, not referenced on 600D ( found it, its available but does it output that?)... is it referenced in 5dIII? Also, if 444 is possible... why is canon taking 6 months to do 4:2:2?
Quote from: 1% on October 28, 2012, 01:16:33 AM
Have you ever had it 1080P on any display? Does forcing fullHD on 5dIII have different values? Or is this a product of only 30fps frame rate?
Technically EDID_COLOR_444 exists, not referenced on 600D ( found it, its available but does it output that?)... is it referenced in 5dIII? Also, if 444 is possible... why is canon taking 6 months to do 4:2:2?
I've never had 1080p out to any monitor, earlier this morning I had 1080i60 but that seems to have been more of a fortuitous event than anything else.
6 months is a long time indeed, I guess we can pray that the uncompressed HDMI "official rerelease" has some more value than most of us believe it will.
Hopefully something can be done with this because I don't get an update. A DVI recorder may be cheaper to build/buy.
Quote from: 1% on October 28, 2012, 04:28:29 AM
Hopefully something can be done with this because I don't get an update. A DVI recorder may be cheaper to build/buy.
Im going to speak to atomos, monday and Ill get the dl from them. I doubt the will offer much but maybe they might want to add some "cool" to the brand and work with us? if the Nikon sync issue was sorted via an atomos firmware update maybe we might get some hope for the 5dmk iii.
Good luck with the 600D!
Quote from: 1% on October 28, 2012, 01:16:33 AM
Technically EDID_COLOR_444 exists, not referenced on 600D ( found it, its available but does it output that?)... is it referenced in 5dIII? Also, if 444 is possible... why is canon taking 6 months to do 4:2:2?
Ok all it's left is to find out how to record 14-bit color and we're good to go ;)
On the 1100D you can force the camera to output 444 data via HDMI, just cache hack
FF1DDCCC BEQ EDID_COLOR_RGB
to
B EDID_COLOR_444
The real question is, does it improve anything? I think not, beacuse the camera is simply re-encoding the HD buffer to the correct "language" spoken by the HDMI monitor
Quote from: nanomad on October 28, 2012, 01:49:43 PM
On the 1100D you can force the camera to output 444 data via HDMI, just cache hack
FF1DDCCC BEQ EDID_COLOR_RGB
to
B EDID_COLOR_444
The real question is, does it improve anything? I think not, beacuse the camera is simply re-encoding the HD buffer to the correct "language" spoken by the HDMI monitor
easy to test if we manage to record something through hdmi
Well, we need a video recorder capable or recording RAW hdmi video data because my monitor simply refuses to display anything
After cache hack or pre cache hack? I can't find functions for the colors in my fw, looks like it alters a register. Input could be 4:1:1 and then output at whatever the monitor displays. Or just overlays would be 4:4:4. I'd rather get 1080P somehow vs 1080i... or does it do xxfps in a 60i container?
ldr r0, [r4, #28]
cmp r0, #0
addeq r2, pc, #424 ; *'[EDID] ColorMode = EDID_COLOR_RGB'
beq FF1ECFF8
cmp r0, #1
r2, pc, #448 ; *'[EDID] ColorMode = EDID_COLOR_422' ⬁
beq FF1ECFF8
cmp r0, #2
popne {r4, pc}
add r2, pc, #468 ; *'[EDID] ColorMode = EDID_COLOR_444'
Interesting, looks the 600D version has a different structure
edit: nope, you're looking at the wrong place my friend. Check sub_FF1EAC00 out ;)
I tried dicking with PROP_HDMI_CHANGE_CODE.... on real HDMI it doesn't want to change much. On DVI it took more settings.
hdmi_code_array[0] = 5; - See 2, 5, 17, 20. Allows up to 32.
hdmi_code_array[1] = 1920;
hdmi_code_array[2] = 1080;
hdmi_code_array[3] = 1;
hdmi_code_array[4] = 0;
hdmi_code_array[5] = 1;
hdmi_code_array[6] = 1;
hdmi_code_array[7] = 2;
*Ok, I see it in pana turn on HDMI.
I had to do it a different way. I changed the registers it was comparing.
FF1EAD70: e3530000 cmp r3, #0 - RGB
FF1EAD7C: e3530001 cmp r3, #1 - 422
FF1EAD84: e3530002 cmp r3, #2 - 444
cache_fetch_line(0xFF1EAD78, TYPE_ICACHE);
cache_fake(0xFF1EAD78 , 0x010053E3, TYPE_ICACHE);
cache_fetch_line(0xFF1EAD7C, TYPE_ICACHE);
cache_fake(0xFF1EAD7C , 0x000053E3, TYPE_ICACHE);
I ran it and still get display but can't tell if I get 4:2:2 color or not.
I did the same for 4:4:4... my display tints very red... guess that means its doing something. Will try on 1080P through DVI next.
Yep 444 going red is ok, your monitor does not support it and decodes it as 422
So playback of images should be 4:2:2 or 4:4:4 upsampled depending on what movies/pics actually become in the player.
So now would have to force progressive somehow and figure out how the YUV422 -> HDMI conversion happens and what is really being sent to the screen. What are the specs on the LV buffer, hdmi buffer, etc.
The point is, the in-camera buffer is 422 so you're not going to gain anything. I didn't read canon press release but I think they are not offering anything more than 422 uncompressed output on HDMI
But are we getting 4:2:2 now? I though we weren't.
Just sent to Atomos......
Hi there,
I just bought a ninja 2 to test the recording capabilities of uncompressed HDMI from the Canon 5D mkiii. I'm running Magic lantern alpha 2 firmware.
I appreciate this is not official firmware but I wonder if you can help?
When I plug the camera directly to my Samsung TV it detects the input as 1080i60 (see attachment)
However the ninja 2 detects the signal as 1080i59.94, this seems similar to the Nikon sync issue, not sure?
My question is would you consider taking a look at this or do we have to wait 6 months for the oficial firmware update until we can record uncompressed HDMI. I hope you may consider taking a look, it would be very cool and hopefully beneficial to your company in therms of sales!
Thanks
Quote from: mixmastermike on October 29, 2012, 04:16:48 AM
Just sent to Atomos......
Hmm.. I am not sure if there is much Atomos can do about 60i input from 5D Mark III. This is something Canon should address with their firmware update.
Maybe I am wrong. I just saw the spec of Ninja 2 and it is stated to accept below input frame rates.
1080i60,1080i59.94,1080i50,1080p30,1080p25,1080p24,1080p23.98,1080p30(60i),1080p25(50i),1080p24(60i),1080p23.98(60i)
720p60,720p59.94,720p50,480i,576i
Quote from: bumkicho on October 29, 2012, 07:26:54 PM
Hmm.. I am not sure if there is much Atomos can do about 60i input from 5D Mark III. This is something Canon should address with their firmware update.
I agree but building up a little social movement for the good never hurt anyone.
looking at the implementation of the Nikon hdmi there are settings in the firmware on the camera that allow you to select exactly the output that you want we simply don't have that on the 5d.
Please, help!
Today I installed the firmware on my 5D Mark III, it works.
But I can't understand:
After turning off and on again, firmware disappeared, and I have to install it again.
Is it right, or I made something wrong?
Thanks.
Quote from: gryanik on October 30, 2012, 01:19:23 AM
Please, help!
Today I installed the firmware on my 5D Mark III, it works.
But I can't understand:
After turning off and on again, firmware disappeared, and I have to install it again.
Is it right, or I made something wrong?
Thanks.
Yes, that's right. You have to load it up when you want to use Magic Lantern.
Quote from: gryanik on October 30, 2012, 01:19:23 AM
Please, help!
Today I installed the firmware on my 5D Mark III, it works.
But I can't understand:
After turning off and on again, firmware disappeared, and I have to install it again.
Is it right, or I made something wrong?
Thanks.
Its an alpha version of ML for the 5d3 meaning its purpose is to slowly test ML for 5d3 so a1ex and the gang can work out all the lil bugs. It runs off the card and doesnt install into the camera. at least thats my understanding. It does however save the ML settings, u used last, to the card (brilliant). INSTALL ON MEDIUM SIZE SD CARD AND RECORD TO THE CF CARD. Im using a 2 gb sandisk SD card for ML and a 16 gb 60MB/s sandisk extreme CF card to record to. So far so good! This also insures "safer" testing(read there disclaimer). I havent had one lock up yet. my gopro hero 2 froze 3 times today from its own firmware. to this day my mrk 3 has never frozen even with ML ALPHA 2. Great work guys!
I need some testers. Especially if you have a Kingston 16GB 266x, please do this test (but I'm looking for tests with all other cards).
download (http://a1ex.magiclantern.fm/bleeding-edge/5D3/ml-5D3-113-debug.fir)
What it does:
1) blinks the LED 5 times
2) creates a file named TEST.DAT
3) takes a picture
Please test it on all your cards and let me know:
- the card size and model
- the exact file size of TEST.DAT
- whether you get ERR02 or not
Make sure you run the test with DISPLAY ON! (press INFO if it's off). Otherwise, the camera will start in powersave mode and will not run the tests.
Technical details: http://www.magiclantern.fm/forum/index.php?topic=2528
Source code:
void my_big_init_task()
{
find_ml_card();
info_led_blink(5,200,200); msleep(1000);
FILE* f = FIO_CreateFileEx(CARD_DRIVE"test.dat");
for (int i = 0; i < 1000; i++)
{
FIO_WriteFile(f, YUV422_LV_BUFFER_1, 1025);
}
FIO_CloseFile(f);
msleep(1000);
call("Release");
info_led_blink(5,200,200); msleep(1000);
}
Thanks!
Do you also need test results with other cards?
Yes, with all cards, but especially with that card.
Is it a safe test? (5d3, Transcend 32gb 400x)
Source code is included, I think it's 100 times safer than any regular ML build. No other ML code is running besides that code snippet.
Edit : Just noticed the 1.1.3 firmware requirement, off to update first.
Here are the results with 5Dm3
Name --- card mode ----------- size bytes ----------- --------------
SanDisk sd-32GB 45 MB/sec 1025000 1048576*
Lexar Pro cf-32GB 1000x x x test did not comple, lockup, one time it showed err 02 in live view
SanDisk cf-32gb-60MB/s 102500 1048576*
SanDisk cf-4gb-45MB/s x x test did not comple, one time it showed err 02 (not in live view)
SanDisk cf-16GB-30MB/s 102500 1048576*
Kingston cf-4gb 133x (20 MB/sec?) x x test did not comple, lockup, one time it showed err 80 (not in live view)
Kingston cf-512K- 6MB/s 102500 1048576*
Hm, that's odd.
Preliminary advice: if you care about your data, try not to use the cards that failed the test in 5D3 (with or without ML, doesn't matter). You can use them in 5D2 though.
Could it be any connection between this and the reports of corrupted videos? (I remember seeing some on canon rumors).
Edit: here are my results:
- Kingston 32 GB 266x CF -> OK (1025000 bytes)
- Kingston 16 GB 266x CF -> fails (tried to format it a few times). The red LED stays on for about 1 minute, then takes the picture, then err20.
- Kingston 2 GB class 2 SD -> OK (kinda slow, but works)
Transcend 400x 32gb ----- size 1,025,000 bytes ------ no error
Transcend 32gb 400x CF , 0.97 MB (1,025,000 bytes) , No Error.
Edit : Also tested on a Kingston SD 32GB Class 4. Same results as above.
One of the card that fails: Lexar Pro 1000x is the one I used the most and never had any data corrupted yet!
edit: got it to work, see later post.
Here are some reports:
http://www.canonrumors.com/forum/index.php?topic=8732.0
http://www.canonrumors.com/forum/index.php?topic=6191.msg119814#msg119814
http://www.canonrumors.com/forum/index.php?topic=5360.0
It's probably something that doesn't happen every day, but only with certain settings or usage patterns.
I'm looking forward for comments from those users who had problems with ML on 5D3 (there were a few reports).
Please keep posting the results, even if other users have already posted the results from the same card as the one you use.
I need as many test results as possible in order to draw a meaningful conclusion.
On my card I was able to make an workaround, by slowing down the CF write routine. It can be fixed if you help me.
Here's my results:
Lexar 1000x 32gig CF (#1) > OK (1,025,000 bytes)
Lexar 1000x 32gig CF (#2) > OK (1,025,000 bytes)
Sandisk Extreme 60MB/s 16gig CF > OK (1,025,000 bytes)
Transcend 133x 16gig (#1) CF > OK (1,025,000 bytes)
Transcend 133x 16gig (#2) CF > OK (1,025,000 bytes)
A-Data 'Speedy' 8gig CF > OK (1,025,000 bytes) - (Not sure on speed of this card - prob crap :P )
Panasonic SDHC (4) 16gig SD > OK (1,025,000 bytes) - (Not sure details of this either - i normally use this SD card for ML)
I ran all the above tests by putting the actual test firmware on the individual cards without having the SD (from bottom of list) in the camera running ML like i have been with the alphas - just to be sure it was only testing those cards.
None of my cards seemed to do anything odd - the led blinked.. then went pretty solid as it wrote the YUV422 liveview buffer file (or whatever), then took a photo in live view mode and exited back into live view. Did i do something wrong or am i just lucky with all my cards? I DID format every card before adding the firmware and testing, maybe that helped?
Thanks Alex!!
Aaaah! Got it.
My problem was that I had the cam in photomode. I just redid the tests with videomode, only the fir file on the cards and it works as it should. Swiftly boots, blinks, takes a pic and doesn't freeze. Also the testfile is on all cards being its 1,025,000 bytes in size.
That is again:
Transcend CF 64 GB 400x and 600x
INX 1GB SD (sloooow and old)
Quote from: RenatoPhoto on October 30, 2012, 07:58:43 PM
Here are the results with 5Dm3
Name --- card mode ----------- size bytes ----------- --------------
SanDisk sd-32GB 45 MB/sec 1025000 1048576*
Lexar Pro cf-32GB 1000x x x test did not comple, lockup, one time it showed err 02 in live view
SanDisk cf-32gb-60MB/s 102500 1048576*
SanDisk cf-4gb-45MB/s x x test did not comple, one time it showed err 02 (not in live view)
SanDisk cf-16GB-30MB/s 102500 1048576*
Kingston cf-4gb 133x (20 MB/sec?) x x test did not comple, lockup, one time it showed err 80 (not in live view)
Kingston cf-512K- 6MB/s 102500 1048576*
OK, ALL WORKING NOW!
UPDATE: I put the camera in VIDEO MODE and test all again. All cards tested a lot faster and passed, no hangups.
^-- What did you do differently?
On my camera it doesn't matter in what mode I run the test - the 16GB one always fails with ERR02, the other two are OK.
If you run the test with display off, the camera will start in powersave mode, so it will appear locked. Press INFO to turn the screen on, and should be OK.
So... make sure you run the test with display on.
SDHC Sandisk Ultra - Class 4 - 15 MB/s - 16 GB / No error - TEST.DAT = 1 025 000 octets 2 cards tested
SDHC Lexar FULL-HD VIDEO - Class 8 - 8 GB / No error - TEST.DAT = 1 025 000 octets 1 card tested
CF Sandisk Extreme - 60 MB/s - 32 GB / No error - TEST.DAT = 1 025 000 octets 4 cards tested
So... only my card is buggy?!
I'll add this card test (without picture taking) in the next alpha. It will delay the startup by 1 or 2 seconds, but I think the integrity of your data is a lot more important than a small delay.
If the card will be diagnosed as "not compatible", ML will refuse to run.
Code, for reviewing: https://bitbucket.org/hudson/magic-lantern/changeset/5fcc91e8d936
Maybe it's just my card, maybe not, I don't have enough info to tell, just incomplete theories. We'll see.
will it start up cleanly without needing liveview?
Yes, it should start up without livewview
I have been testing Alpha 2 and find it to be really stable. Just 2 things that don't seem to be working for me...
1. When I use 1280 60p mode (ALL-I or IPB), I get no overlays at all (no zebra, focus peaking, etc). When I bring up the magic lantern menu, it says "GlobalDraw is disabled, check you settings". The overlays work fine in 1080 24p/30p modes.
2. When no cropmarks are selected, and when returning to live view after previewing recorded footage, the top and bottom info bars lose their black background color and become transparent. The info is still displayed... it's just displayed over the live footage.
As a side note, I know you're still early in testing, but auto boot would be my wish list addition as soon you feel it makes sense.
1. go to GlobalDraw to see why.
2. can you tell me the exact sequence of actions to reproduce it? (I've never noticed that)
I left out a critical bit of information... this only happens when using my SmallHD DP4 monitor via hdmi. Works fine on the camera's built in lcd.
As I know it doesn't work in 720 through HDMI.
I didn't realize that 720 via HDMI didn't work. Is that a technical limitation or just something that has not been worked as of this point?
Just asking since I tend to use it quite a bit for slow-mo.
There are a lot of parameters to be guessed (just a lot of work with little benefit).
I definitely understand... thanks.
To recreate the issue of missing black backgrounds on the top and bottom info bars...
1. This only occurs when using my SmallHD DP4 monitor (tested 1080p 24 and 30)
2. When first starting the camera and launching Magic Lantern, my view is as shown in Picture1.
3. I then click the play button to view saved footage.
4. I click the play button again to return and then my view is as shown in Picture2. It stays like than until I restart the camera.
Not sure how to upload a photo... Is this possible?
Use a free image hosting site like imgur
Here are photos of my DP4 display which I mentioned in previously...
View before going pressing the play button on the camera...
(http://i.imgur.com/IjdXzh.jpg)
View after returning from play mode...
(http://i.imgur.com/bmJuWh.jpg)
hey guys,
I am still not able to run ML alpha 2 on my 5dMIII.
My 5DMIII is running 1.1.3 software version from canon. I am doing a low-level format and upload the 3 files from the ML download to my SD Card and try to run the firmwareupdate but it just won't work. I redid all the steps like 600 times now, even reinstalled 1.1.3 onmy 5D.
here is a youtube link what it looks like. http://www.youtube.com/watch?v=Mxuuvy2w9bY&feature=youtu.be
could someone please help me with what I am doing wrong?
Have you tried it without your battery grip?
Use a Canon battery.
tried both things already before... wont work...
So, a canon ORIGINAL battery and no battery grip won't work? Strange
yeah i just dont get it... so for the record, if i download from the link in the first post there are only 3 files in the download! is this right? ML - ml-5D3-113.fir - UserGuide... do I need to press a button when the firmware update is ready or something??
to ivorbus, it seems you have a problem with an electronic part of your 5 D. I just had this trouble with mine (under warranty) "no recognise the battery, "impossible to communicate with battery". CPN changed the part and everythings ok...
Yep, maybe one "wire" connecting the PMC to the battery bay failed. Or maybe the chip in the battery fried itself.
- Do you have that same message even without ML?
- Can you try with another canon-branded battery? (suggestion: go to a photo shop and ask if they'll let you try one)
Played around with recording from the clean HDMI out feature this weekend. Seemed to work quite well. ML was stable, though there were a few times that the image on the HDMI out was inconsistent: sometimes it showed the full 1620x1080 and sometimes only had the framed 1620x912 box even though my settings were to show the full image. I'll try to see if I can replicate it and, perhaps even record it.
Here's a thread I started in the "Post your videos" area with a link to a short video I made of the image from HDMI out and comparison with internal recording: http://www.magiclantern.fm/forum/index.php?topic=3489.0 (http://www.magiclantern.fm/forum/index.php?topic=3489.0)
Thanks a1ex! This is working great!
Quote from: JasonATL on November 05, 2012, 01:23:45 PM
Played around with recording from the clean HDMI out feature this weekend. Seemed to work quite well. ML was stable, though there were a few times that the image on the HDMI out was inconsistent: sometimes it showed the full 1620x1080 and sometimes only had the framed 1620x912 box even though my settings were to show the full image. I'll try to see if I can replicate it and, perhaps even record it.
Here's a thread I started in the "Post your videos" area with a link to a short video I made of the image from HDMI out and comparison with internal recording: http://www.magiclantern.fm/forum/index.php?topic=3489.0 (http://www.magiclantern.fm/forum/index.php?topic=3489.0)
Thanks a1ex! This is working great!
There's always a box around the video. Maybe your TV had auto zoom turned on.
Quote from: Lcrusher on November 05, 2012, 02:05:14 PM
There's always a box around the video. Maybe your TV had auto zoom turned on.
You can remove the box (well, the top and bottom): In the ML menu, Display->Clear overlays
But the pillarbox remains.
Quote from: Lcrusher on November 05, 2012, 03:24:02 PM
But the pillarbox remains.
Sorry for my confusion and for not being clear. My original post meant that sometimes the letterboxes were there (hence the 1620x912) and sometimes they were not (hence the 1620x1080), but were somewhat inconsistent based on the settings I had. Usually, a press of the ML menu button would correct it.
Seems pretty cool ... sounds like we could effectively remove the recording limit in camera. Very cool video Jason, thanks for testing.
I guess it's time to post a small update, mostly with bugfixes.
Download (https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-5D3.113.Alpha3.zip)
The most important change is a card test executed at startup. My 16GB (Kingston 266x) card has problems, and I'm trying to diagnose the issue: maybe it's just my card, or maybe it's related to this (http://www.canonrumors.com/forum/index.php?topic=5474.0). If the test fails on your camera, please report.
There are also a few handy tweaks:
- Histogram and waveform moved to bottom
- New experimental display for focus peaking (extreme sharpness)
- 16:9 bars for anamorphic preview
- Focus box moves faster (not yet customizable)
- After taking a picture and pressing Zoom In right away, you can scroll through pictures
- Saturation boost when adjusting white balance
- Warnings for bad settings (e.g. if you set picture quality to JPEG instead of RAW by mistake)
- Dim the red LED while recording (make it less distracting)
Now, about the photo features. I can enable most of them, but, while running the random stability test, at some point the camera froze; I took the battery out, and found out that LiveView was no longer working (even when booting without card). Cleared camera settings and it's OK now. But this shows clearly that there's something fishy inside.
So, all other features that depend on properties will have to wait until I'll understand what happened. It may take a few months, maybe more, maybe less, I have no idea.
Current alphas are pretty safe, to the best of my knowledge.
Great! Thank you!!!
Thank you for this update ;)! Great job! I hope you'll be able to find out what is going wrong! But no matter what, thank you :)!
The good news is that I've been running the same test on the public alpha for around 2-3 hours and it's still going strong. It's in the Debug menu -> stability tests -> random tests. This means the backend is pretty strong.
Quote from: a1ex on November 08, 2012, 08:23:50 PM
The good news is that I've been running the same test on the public alpha for around 2-3 hours and it's still going strong. It's in the Debug menu -> stability tests -> random tests. This means the backend is pretty strong.
Good news yes :)! I'll do these stability tests as soon as I can. All the best for your work, from Belgium ;).
I'll get a wall adapter (ACK-E6), and if the test will run for 24 hours, I think it will be pretty stable. Maybe I'll be able to film a timelapse with it running.
Oh it would be great! Let's cross our fingers.. I don't know how much it costs but I just sent you (and your team) 10€, not much but I hope it will help you getting what you need ;).
I like the sharpness peaking a lot. Too bad it's a bit laggy.
great alex.
dim function is perfect for my situation :)
sharpness function for focus is great too..
after 5 minutes of testing i found out that the focus function does not work when anamorphic preview is activated..
is that correct?
greets. re
Focus peaking works with anamorphic preview, but only with "blinking dots" display selected.
I've done a shooting all day long yesterday with the alpha3 and found it pretty stable ! None bugs appear, and 0crashs
Quote from: a1ex on October 30, 2012, 08:01:52 PM
- Kingston 16 GB 266x CF -> fails
I too have this card (its my only CF) and it fails.
I can't afford to buy another just now and have never had an issue with it having taken hundreds of images and a fair few videos.
Can you tell me what its testing for (sorry if I missed this answer somewhere in the thread), also despite obviously loading as it tells me on every screen that my card failed I cannot access the menu via the erase button as before.
Also is there a definitive list of safe CFs out there somewhere so when I do get a new one there isn't a nasty surprise.
It simply tries to write a file, with some buffer sizes known to fail on that card, discovered empirically ( http://www.magiclantern.fm/forum/index.php?topic=2528.0 ).
Probably Canon code does not use these buffer sizes, so it's extremely unlikely to fail under normal usage.
I've noticed it when shooting this: http://vimeo.com/48861358 (ERR02 after exactly 116 pictures). I've used some ugly hacks to be able to shoot it. I had ERR02 in normal usage too (just shooting pictures, nothing fancy).
I had no problems using this card in 5D2 though.
Cheers Alex, I only have the 5D3 but I'll upgrade to another card on payday, they're not as expensive as I seem to remember, better that than sometime deep into a project :)
Hi Alex, I was just wondering if the auto restart is included or likely to be included in an update soon? I know the Mk3 now can record for longer (up to 30 mins) but it would stilll be a very useful feature to have so I can just position the camera at an event and leave it recording. Many thanks!
I did a long shoot and it restarts automatically.
Quote from: a1ex on November 11, 2012, 10:20:58 AM
Focus peaking works with anamorphic preview, but only with "blinking dots" display selected.
Working like a charm! :D
I just miss the anamorphic preview in play mode now, but that can certainly wait.
I've been using the Alpha 3 for three days in a row, shooting a short film all day long - no resting times for the camera - with many lenses (m42 adapted, 24-70, 70-200, 50, 16-35), multiple cards (and brands) and custom cropmarks without ANY bugs, quirks, errors and such. Congratulations, guys! Your work helps a lot! I'll certainly donate some more soon. :D
Quote from: itsskin on November 11, 2012, 07:15:31 PM
I did a long shoot and it restarts automatically.
Ooops. Just checked again and this shooting was without ML.
Hey Alex, is magic zoom on half shutter work in progress or we better get used to current options? This feature is a life savior on m2 and it is the most effective feature on ML for "running-and-gunning" - it would be greatly appreciated if you could get that working.
Alpha 3 is working fine on Kingston 16Gb X133.
yes,.. anamorph preview would be great.
Shot a wedding last weekend, Focus Peaking, Zebaras, and Gradual exposure were without any issues !!
Thank you very much... it seems very solid !!
No stability issues.
Zebras - Luma Fast gives solid block of colour for over/under exposure which comes and goes at 1-2 sec intervals.
Focus Peaking - all methods seem to work well on low ISO's. Raw focused best and quickest especially with Strong Edges (my preferred anyway). Increasing ISO made it harder to focus especially using Sharpness. Beyond ISO1250 it was impossible to focus. Changing colour does not have any effect when Fine Dots are selected - in fact it only seems to work in Blinking Dots.
Histogram and waveform at the bottom only worked on 3:2 top/bottom mode. All other modes displayed at the side. Did not move at all on my Marshall 5" monitor.
Gradual Exposure works extremely well.
Fast focus box moving works well.
Will test some more.
Moira
I can't find automatic profile switching for preview/recording.
Or we never had it in 5dm3?
Alpha 3 generally working well but there seems to be an issue with changing ISO while waveform monitor is turned on -
camera crashes every time.
Hi Evre one
What do you advise me to
How to adjust the settings of the cinematic image
And how to adjust the setting "BODIE".
Thanks
Payday approaches and I'd like to get playing with alpha 3, but before I can I have to find a cheap decent sized CF card that passes the test.
I'm based in the UK, any suggestions?
thanks.
yo yo yo A1ex ;D long time no chat =) alpha 3 working pretty good on my 2 x 5d3s
Quote from: Director on November 16, 2012, 06:27:48 PM
Hi Evre one
What do you advise me to
How to adjust the settings of the cinematic image
And how to adjust the setting "BODIE".
Thanks
You can ask the director yourself: http://www.neumannfilms.net/contact-us/
Everyone is waiting for startup and adjustment of bitrate. I especially!
Sure, after fixing all major bugs.
Just because so many people keep asking for auto-boot to be added, I thought I'd post a screen shot of my custom menu. Having firmware as my first option makes it extremely fast to boot into ML. And I think A1ex has said this before, to save power, just switch to photo mode in between shots rather than a full power down.
I do a lot of run and gun commercial shooting, and these are my most used settings:
(http://i.imgur.com/24mCn.jpg)
I did the same thing, takes no time at all.
- 16:9 bars for anamorphic preview
what is this for.. ?
i am a little confused.. cause anamorph has nothing to do with 16:9?
greets. swinxx
Sadly can't load mine since alpha 3 - just down to CF card though - can someone confirm that a "bad" CF card will stop loading as I'm not 100% sure.
Correct, you need a good card.
mnteddy : it seems you like your LCD very bright :D
I could have sworn there was a 1/47 ss option earlier today but it is now jumping from 1/42 (red) to 1/60 (blue) with nothing in between. I've been going through my settings to see if I could reverse/replicate this but I'm striking out at the moment.
is the bit rate feature something that will work with the alpha style boot that runs off the card? I love booting ML off the card. I know its not 100% safe but its deffintly less scary for noobs like me a ha ha
No bumping your own posts ::)
Quote from: nanomad on November 23, 2012, 05:06:27 PM
No bumping your own posts ::)
Not sure if that was for me but i usally make a billion mistakes in my posts or word things poorly so wanted to correct them. grammer is not my strong point. deffinetly was not trying to bump my post.
You can use the edit button ;)
Well, I saw this card in Amazon's Black Lightning deals - Transcend 32 GB 400x Compact Flash - I seem to recall this one working so have ordered.
Alex
The previous time invalidated you to provide me with information about this request did not provide me with information and now asks you if you do not see my question from first time
Can you tell me what are the settings that you used in the film "Bodie"
Thanks
For the last time, ask the bloody producer, not alex (who is not affiliated in any way with the movie)
Hello,
Freshman here, just wondering if there is any ETA for the movie restart mode on the Mark iii as that would be very useful to me.
Keep up the good work, definitely going to support you guys.
The 30-minute limit is a legal one, so I don't want to remove it ;)
Can we expect the analog/digital gain options to be included in the next alpha? They were actually one of the main reasons I used ML on my Mark II, because without, audio recordings are terribly noisy, and with, the audio sounds much better..
No, the audio chip is unknown.
Oh :-O Is this a thing that will be solved later or is the audio chip a hard one (and therefore those features probably not be included at all)?
We need high res pictures of the inside of the camera.... I doubt there's someone willing to take apart his for 'science'
Seems you can ask this guy:
http://www.eoshd.com/content/7727/james-miller-removes-optical-low-pass-filter-from-5d-mark-iii-for-resolution-increase
http://www.eoshd.com/content/7813/how-i-opened-my-5d-mark-iii-and-why-you-have-to-be-crazy-to-do-it
Quote from: nanomad on November 28, 2012, 10:53:16 AM
We need high res pictures of the inside of the camera.... I doubt there's someone willing to take apart his for 'science'
I dunno what you're looking for looks like, but here's some pics of the insides of a mark III:
http://www.lensrentals.com/blog/2012/04/5d-iii-strip-tease
In case it's in there somewhere...
We already have hi-res PCB pics at http://www.pbase.com/rcicala/magiclantern (thanks Roger!)
I believe the chip is the bottom-left one in the second pic, but... good luck reading what's on it ;)
I think I can make out AFIE on the first four letters: http://i.imgur.com/kZMv1.jpg
Quote from: a1ex on November 28, 2012, 06:37:20 PM
We already have hi-res PCB pics at http://www.pbase.com/rcicala/magiclantern (thanks Roger!)
I believe the chip is the bottom-left one in the second pic, but... good luck reading what's on it ;)
Forgot to say we need proper MACRO photos of the PCB. Something that takes time (and focus peaking really helps here ::))
Quote from: feureau on November 28, 2012, 06:57:37 PM
I think I can make out AFIE on the first four letters: http://i.imgur.com/kZMv1.jpg
Enhance.
hello ML guys !
i want to install the alpha3 on my brand new 5DMK3 and after all the step and after click on the "firmware upgrade" i have the loading panel for 5 seconds and then a black screen with a red dot blinks.
after, i come back on the menu and i can see : firmware version : "1.1.3-ml-2.3.next"
can you help me ?
Quote from: aceka on November 29, 2012, 10:52:04 PM
i come back on the menu and i can see : firmware version : "1.1.3-ml-2.3.next"
Congratulations. you've just loaded ML on your 5DMk3.
Press the trash button to load the ML menu. For further info, please consult the manual :3
Amazing that I can see the peaking focus function on my zacuto monitor!! Gerat job
Some of the setting of focus aid are for on camera LCD and some are for external monitor, still trying to figure it out.
Do any of us know what Alex meant when he tweeted this ?
"Some new camera may turn into a 1D-X or it may explode" ???
Hmm... cryptic... I wonder if they'd stumbled on photo fps controller that can increase shooting speed up to 10-14 fps...?
What's his twitter handle btw?
https://twitter.com/autoexec_bin
It was a joke, by the way. Follow the other posts ;)
oops lol ::)
Stop toying with my emotions!!! >:(
gg
Hi, it looks great! Just wondering if you are open to some more suggestions for improvements? Like for example, removing the ridiculous lock that always sets the camera to an iso of 400 when a Canon flash is attached. What a stupid and nonsensical idea!!! In general, I am wondering about more features for still photographers. Are you thinking of a focus trap script down the track? Cheers...
I have the same problem what had Ivoborkus.
The software witht 5D mark 3 is not running
Hi team.
My first post. Absolutley loved magic lantern on my t2i. Recently invested in the 5DM3 and am missing magic lantern alot. Looking at all the Alpha versions that are out, I am seriously tempted to download it.
1 major question i need answering. I have read through all the posts, and this question has not been asked.
I use SD cards as opposed to CF to record my main video.
Will I be able to put Magic Lantern Alpha3 onto a 4GB CF card instead of SD, and then use the SD to record my main footage?
Please let me know if this has been tested.
Thanks.
Sebi 8)
Quote from: sebi_nurayfilms on December 05, 2012, 02:53:45 PM
Hi team.
My first post. Absolutley loved magic lantern on my t2i. Recently invested in the 5DM3 and am missing magic lantern alot. Looking at all the Alpha versions that are out, I am seriously tempted to download it.
1 major question i need answering. I have read through all the posts, and this question has not been asked.
I use SD cards as opposed to CF to record my main video.
Will I be able to put Magic Lantern Alpha3 onto a 4GB CF card instead of SD, and then use the SD to record my main footage?
Please let me know if this has been tested.
Thanks.
Sebi 8)
The question has never been asked because the answer is clearly given on the first page of this thread ::)
Tips:
- Disable Auto Power Off.
- Recommended usage: copy ML on a small SD card, keep it in the camera, and use CF cards for shooting.
- You can use any card combination, just don't put ML on both cards.
- EyeFi cards are working!!! (thanks kikouyou)
Would it be possible to remote the camera via Eyefi?
Ok. Thanks for getting back to me.
So - has anyone tried using Alpha 3 running from a CF card instead of the SD? Is it possible?
Only reason why I ask is that I have heavily invested in SD cards, coming from the t2i to the 5d3. So i don't want to have to buy a new set of CF cards (which are rather expensive).
Please let me know if anyone knows.
The fact that i still do not own a fast cf card made me put ml on the cf card while recording video to sd.
No problems at all. But remember that cf card are much faster because of the speedlimit on sd card in 5d.
by the way,even if i forgot to switch slots to record on sd and it records on the slow cf card with ml on, there are no problems.
Hey Dude.
Thanks for the quick response. So let me get this straight (sorry to repeat myself as I do not want to f up my £3k brand spanking new camera) just so that I know I am doing this right.
So i could put ML onto my CF card (I have a 16GB one - SanDisk Extreme 60MB/s UDMA) and each time I boot up, run the firmware update of the CF card, and record video to my SD? which is a 32 GB Sandisk extreme pro. And even if i record video to the CF card, all is still ok?
Yes
Hi Alex, that's a real shame there's not likely to be any auto movie restart option :(
I cover events and very often I need to rig the camera in some fairly inaccessible places where it's not really practical to restart the camera manually. Indeed the auto restart on the 60D was quite simply the most significant and helpful function I could have imagined!
I'm just wondering - isn't the law to prevent devices going beyond 30 mins of continuous recording? The auto movie restart function doesn't allow for continuous recording over 30 mins. It stops recording, there's a break, thens it starts again, so definitely not continuous?
Such a useful function to have and honestly not sure how I'm going to get by without it :(
Thanks for all your hard work!
Simon
I've run into a problem and I'm not sure if I'm misunderstanding the purpose of a feature.
I've rigged my monitor upside down (easier/cleaner look) and I've enabled the UPSIDE DOWN feature in ML. The UI is readable and flipped perfectly. The LiveView feed is still upside down though, any way to fix this?
Yes, turn the camera upside down ;)
Quote from: a1ex on December 07, 2012, 05:56:24 PM
Yes, turn the camera upside down ;)
That would mean I'm litterally recording an upside down picture, I'm not sure that's the desired solution. :P
Guess I'm going to have to figure out how to rig my monitor another way then.
Hey Alex, just wondering if there's any updates/progress on the already awesome Alpha 3 build.
Thanks Again for everything man !!
Quote from: KAIT Labs on December 07, 2012, 06:05:40 PM
That would mean I'm litterally recording an upside down picture, I'm not sure that's the desired solution. :P
Guess I'm going to have to figure out how to rig my monitor another way then.
It should be easy to flip the video in post. I use MpEG Streamclip to convert footage for editing and it has the option to flip, rotate, mirror, and whatever other transformation you could want. Adds almost no time to the processing.
2 questions:
1. what is the 16:9 bar for anamorphic preview for?
2. is it possible to define a card (cf/sd) for saving video? now i had the problem that when i shoot video i always have to define it at the beginning of the shoot. when i turn the camera off/on, the default is the cf.. i want the default to be sd.. is that possible to save it somewhere?
thx sw
So amazing job, M and now the 650 D, congratulations...
Do you know aproximatively when we can hope for a 5DMIII stable firmware ?
I say that because I would like to separate from my MII for a 650D (to have it as 2nd spare and more dayli cam than my MIII) but I still need many options (timelaps, intervalometer...).
You make a real f... good job...
Sincerely
Yvan
Quote from: feureau on December 01, 2012, 12:39:42 PM
Hmm... cryptic... I wonder if they'd stumbled on photo fps controller that can increase shooting speed up to 10-14 fps...?
What's his twitter handle btw?
Gotta be the 6D if you are trying to push one of the new cams to 10-14fps. ;D
Quote from: a1ex on November 28, 2012, 06:37:20 PM
We already have hi-res PCB pics at http://www.pbase.com/rcicala/magiclantern (thanks Roger!)
I believe the chip is the bottom-left one in the second pic, but... good luck reading what's on it ;)
He seems to love to open stuff up so he might be willing to open it up again and get a close macro shot of the audio chip. Perhaps.
I assume that there is no way to access the full true 1920x1080 image and we will have to wait for the canon firmware to get full-res clean HDMI out?
I wasn't sure if I report alpha3 bugs here or in the Bug Reports section, so let me know and I'll move it over there.
First, let me say that Alex and the whole ML team are geniuses. I've been playing with ML all day and here are my thoughts:
-- Positive: --
1. LOVE the new gradual exposure setting and the blue/red indicators are really useful to track the transition between exposures. I hope the developers find a way to make it work as smoothly on the other DSLRs (T2i please!)
2. The fine dots setting of focus peaking seems to work the best for me right now, but I can't really tell what the difference is with alpha blend. Extreme sharpness has a lot of potential if it was fine-tuned a bit more in future versions to make it a little more obvious
3. Fast focus box is very fast and responsive.
4. Love the anamorphic stretch settings. This is a feature I requested for my T2i that I hope makes it into release 2.4 (please)!
5. Can't wait for the full release to come out!
-- Bugs that I've encoutered: --
1. Redraw problems when any Canon native UI screen elements are called up (e.g., the * button). Native UI draws over the ML UI and it doesn't come back until a second later.
2. The battery indicator seems to be missing. Maybe it's not a bug, but just hasn't been implemented yet.
3. Focus confirmation in magic zoom isn't working for me. I use green bars, but none of the other settings seem to be working either.
4. When magic zoom is used on any of the anamorphic preview settings, it rescales it to be square pixel.
5. When anamorphic display is turned on, you lose focus peaking.
6. The Dim REC LED doesn't seem to do anything when turned on. It seems equally bright when it is on or off.
7. Focus Peaking > Local Focus seems to only work with Blinking dots. If it's only a feature that's only available for this setting, gray it out when something else is selected.
8. Focus Peaking > Fine details causes significant lag in Liveview. Strong edges and Balanced work pretty well.
9. Not a bug, more of a feature request. The vectorscope takes up too much of the screen as is. Please make a "small" option for the vectorscope like the waveform and put it in one of the top corners, or possibly make the background completely transparent or at least more transparent (maybe like 25%)
I think we might be becoming the Red headed step child of Magic Lantern :P
Yea, post #397 is quite easy to miss.
Quote from: a1ex on November 08, 2012, 04:44:27 PM
I guess it's time to post a small update, mostly with bugfixes.
Download (https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-5D3.113.Alpha3.zip)
The most important change is a card test executed at startup. My 16GB (Kingston 266x) card has problems, and I'm trying to diagnose the issue: maybe it's just my card, or maybe it's related to this (http://www.canonrumors.com/forum/index.php?topic=5474.0). If the test fails on your camera, please report.
There are also a few handy tweaks:
- Histogram and waveform moved to bottom
- New experimental display for focus peaking (extreme sharpness)
- 16:9 bars for anamorphic preview
- Focus box moves faster (not yet customizable)
- After taking a picture and pressing Zoom In right away, you can scroll through pictures
- Saturation boost when adjusting white balance
- Warnings for bad settings (e.g. if you set picture quality to JPEG instead of RAW by mistake)
- Dim the red LED while recording (make it less distracting)
Now, about the photo features. I can enable most of them, but, while running the random stability test, at some point the camera froze; I took the battery out, and found out that LiveView was no longer working (even when booting without card). Cleared camera settings and it's OK now. But this shows clearly that there's something fishy inside.
So, all other features that depend on properties will have to wait until I'll understand what happened. It may take a few months, maybe more, maybe less, I have no idea.
Current alphas are pretty safe, to the best of my knowledge.
quoted
Touché´... Thanks again
I've been trying to watch the commits for other models to try to make sure that the 5D3 port isn't neglected for any bugfixes or large changes. (For example, https://bitbucket.org/hudson/magic-lantern/commits/30f69a59cf275599490f66fcd20b4aa447c6bf9f was implementing a change which was done for every other model *but* the 5D3)
Perhaps this just comes with being an "unsupported" model, at the moment. I don't know what the intended release date for a "stable" 5D3 port is supposed to be, but I'll keep trying to make sure that the 5D3 port is still workable in the meantime, as best I can.
Hi,
the focus confirmation ( whatever setting ) is not working in the magic zoom.Rest seems ok.
Thanks for developing this amazing software. It is already very useful for me especially since I work a lot with manual focus lenses.
Luc
hey
i have problems during the installation on my 5D3, after installing the firmware ML (but no green screen), it's working (i checked the version of firmware ML, its ok) but when i turn off the camera, then turn on; the ML disapeared and i have to re install ML again, do you know why?
thanks!
this is typical for this alpha version : the auto boot option is turned off as long as this is not a stable software.
This means that you have to perform a firmware update from your sd card each time that you have turned your camera off ( for this reason you better disable the option of automatic shut down of your camera )
Are there any plans to add the rack focus feature any time soon,
Thanks Guys,
Amr Toukhy
Is it posible to unlock lens chromatic aberration options for non- canon lenses ? Vignetting correction would be great for video mode :)
During the holidays I did some more testing and noticed a few things:
- Two burst pics came out black (just with noise, as if the shutter didn't move at all). After that I had to take the battery out. The same bug happened a few months ago. Total: 4 black pics out of ~10000.
- Sometimes, when starting the camera with ML, the buttons stop responding. Only happens at startup - let's say in 2 out of 100 attempts.
These things happened with the full feature set enabled, and I did not see them on any other camera. Did you notice any of them with the alpha 3? If yes, any hints on how to reproduce?
Quote from: a1ex on January 05, 2013, 01:17:33 AM
Did you notice any of them with the alpha 3? If yes, any hints on how to reproduce?
I've had the "no response from buttons" issue happen at least 3 or 4 times out of at about 400 boots. Each time, the only way to reboot was through a removal of the battery (power switch did not work). To me it seems random, as I'm unable to reproduce it with a certain set of variables.
I've never had a black frame issue, though I've only been doing video work with ML.
I've experienced black frame issue once, with noise like you stated. I'm quite sure that it didn't actually save the image to the card though, I could be wrong and maybe deleted it.
Never was able to reproduce though. If it happens again i'll be more conscious and report back.
I've had the buttons not responding issue happen to me as well (using Alpha 2). Maybe 2 times out of hundreds of boots. Not a biggie.
(http://pel.hu/down/ML5D3.png)
I've moved some stuff from the 7D info screen.
Nice.
Please check the first post, I've just added a DevKit - a FIR file that enables the boot flag, so you can compile and run your own autoexec.bin.
Can you plese provide Alpha 4. I am not a developer but want to use Intervalometer and bulb ramping for timelapse.
Thanks
Renato
Quote from: RenatoPhoto on January 05, 2013, 05:34:28 PM
Can you plese provide Alpha 4. I am not a developer but want to use Intervalometer and bulb ramping for timelapse.
please wait until the devs feel safe for the next alpha.
it will come when we are sure its time for one.
I have followed the developer instructions for windows and got the cygwin compiler working but get an error about not having any rule to construct the object.
I know the risks and since the dev will not provide Alpha 4 I am willing to try to compile it myself
Here is the last of the error.. sorry in spanish
make[1]: *** No hay ninguna regla para construir el objetivo `cygwin/home/PH/arm -toolchain462/arm-none-eabi/lib/lirm-toolchain46', necesario para `lib_a-setjmp. o'. Alto.
make[1]: se sale del directorio `/home/PH/magic-lantern/platform/5D3.113'
Makefile:70: recipe for target `5D3' failed
make: *** [5D3] Error 2
Did you change Makefile.user.default to include the path to your ARM compiler?
Do not edit the defaults file, work on Makefile.user instead
There are a few suggestions for Windows developers in the getting started thread
Quote from: nanomad on January 06, 2013, 04:44:14 AM
Do not edit the defaults file, work on Makefile.user instead
There are a few suggestions for Windows developers in the getting started thread
Since
Makefile.user is not included with the source download anymore, Makefile.inc doesn't have the paths that need to be changed anymore, I had been editing the .defaults file. What is the consequence of this? I have never really gotten a mercurial system to work for me so I have just taken to downloading the source tree from bitbucket.
Quote from: Francis on January 06, 2013, 05:54:06 AM
Since Makefile.user is not included with the source download anymore, Makefile.inc doesn't have the paths that need to be changed anymore, I had been editing the .defaults file. What is the consequence of this? I have never really gotten a mercurial system to work for me so I have just taken to downloading the source tree from bitbucket.
The user file is not downloaded because it's not strictly needed. It's also explicitly not tracked by mercurial for the reasons below.
The build system reads the defaults file first and the overrides it with values taken from the user file. The benefit is that
- you keep your user settings during updates (the defaults file may change, your user file doesn't)
- you don't push your settings to the repository. This creates shorter commits and doesn't break the other's developers build environment every other pull
Thanks for the tips. I created the Makefile.user and added the path as suggested; did not change the Makefile.use.defaults. The Mercurial worked and downloaded some 48 megs into Magic-Lantern.
I can do a" make clean" and then a "make 5D3" The compiler spits out some information for about a minute and then it ends with the information posted above. Some error about not finding a rule for constructing the object.
UPDATE: I changed the language in cygwn LANG=en_US here are the results:
-------------------------------------
$ make 5D3
make -C /home/PH/magic-lantern/platform/5D3.113
make[1]: Entering directory `/home/PH/magic-lantern/platform/5D3.113'
[ CPP ] magiclantern.lds
[ AS ] entry.o
[ CC ] boot-hack.o
[ AS ] stubs.o
[ VERSION ] ../../platform/5D3.113/version.c
[ CC ] version.o
[ CC ] exmem.o
[ CC ] bmp.o
[ CC ] fio-5d3.o
[ CC ] font-dyn.o
[ CC ] config.o
[ CC ] menu.o
[ CC ] debug.o
[ CC ] stdio.o
[ CC ] bitrate-5d3.o
[ CC ] tweaks.o
../../src/tweaks.c:2122:6: warning: conflicting types for 'zoom_trick_step' [enabled by default]
../../src/tweaks.c:1336:9: note: previous implicit declaration of 'zoom_trick_step' was here
[ CC ] lens.o
[ CC ] property.o
[ CC ] propvalues.o
[ CC ] gui.o
[ CC ] gui-common.o
[ CC ] misc.o
../../platform/5D3.113/misc.c: In function 'display_shooting_info':
../../platform/5D3.113/misc.c:67:9: warning: unused variable 'bg' [-Wunused-variable]
../../platform/5D3.113/misc.c: At top level:
../../platform/5D3.113/misc.c:170:6: warning: conflicting types for 'RedrawBatteryIcon' [enabled by default]
../../platform/5D3.113/misc.c:162:5: note: previous implicit declaration of 'RedrawBatteryIcon' was here
[ CC ] picstyle.o
[ CC ] cfn.o
[ CC ] zebra.o
[ CC ] shoot.o
[ CC ] chdk-gui_draw.o
[ CC ] movtweaks.o
[ CC ] my_memset.o
[ CC ] menuhelp.o
../../src/menuhelp.c:143:6: warning: conflicting types for 'draw_page_number' [enabled by default]
../../src/menuhelp.c:42:29: note: previous implicit declaration of 'draw_page_number' was here
cd ../../doc; python2.6 menuindex.py
Could not open menuindex.txt, will not rewrite help index files
[ CC ] menuindex.o
[ CC ] focus.o
[ CC ] notify_box.o
[ CC ] dialog_test.o
[ CC ] vram.o
[ CC ] aj_port.o
[ CC ] lv-img-engio.o
[ CC ] fps-engio.o
[ CC ] tasks.o
[ CC ] tskmon.o
[ CC ] state-object.o
[ CC ] hdr.o
[ CC ] beep.o
[ CC ] audio-ak.o
[ CC ] vsync-lite.o
make[1]: *** No rule to make target `cygwin/home/PH/arm-toolchain462/arm-none-eabi/lib/libc.a', needed by `lib_a-setjmp.o'. Stop.
make[1]: Leaving directory `/home/PH/magic-lantern/platform/5D3.113'
Makefile:70: recipe for target `5D3' failed
make: *** [5D3] Error 2
-------------------------------------------
Thanks for all of your replies.
Renato
I've pushed a patch for something related. Try pulling and updating your local copy and see if it helps
Used: hg pull and then hg update
No improvement!
My Makefile.user is:
ARM_ABI=none-eabi
ARM_LIBC_A=cygwin/home/PH/arm-toolchain462/arm-none-eabi/lib/libc.a
PYTHON=python2.6
I noticed that some instructions say to copy Makefile.user.default and to change the paths. That file is totally different so which one should I use?
There is also some references to update the path in Makefile.inc and Makefile.user.defaults.. Is this also needed or by using the ARM_LIBC_A=...... is enough to pass all this information to other files.
Thanks
Renato
Any help?
I had a same problem.
Follow my instructions in the starting as a developer topic.
This line is the key:
ARM_LIBC_A=../../../arm-toolchain462/arm-none-eabi/lib/libc.a
You should give a relative path.
Quote from: Pelican on January 05, 2013, 02:50:28 PM
(http://pel.hu/down/ML5D3.png)
I've moved some stuff from the 7D info screen.
Pelican, what are the green boxes for? And the number after the battery?
Quote from: Pelican on January 06, 2013, 11:44:24 PM
I had a same problem.
Follow my instructions in the starting as a developer topic.
I have gone over it many times. Cannot solve the problem.
thanks
Quote from: RenatoPhoto on January 06, 2013, 11:49:33 PM
I have gone over it many times. Cannot solve the problem.
thanks
I've just edited my answer. Read it again.
ARM_LIBC_A=
cygwin/home/PH/arm-toolchain462/arm-none-eabi/lib/libc.a
Quote from: scrax on January 06, 2013, 11:48:01 PM
Pelican, what are the green boxes for? And the number after the battery?
The green/gray boxes are the battery performance.
The number is the actually used battery from battery history table.
If you register your batteries there are 1-6 battery info in the battery history.
You can see the same info on Battery info menu, but you should navigate through the Canon menu system to see it.
I have 4 batteries and when I put one of them into the camera I can see right then which one is inserted.
Quote from: Pelican on January 06, 2013, 11:55:47 PM
The green/gray boxes are the battery performance.
The number is the actually used battery from battery history table.
If you register your batteries there are 1-6 battery info in the battery history.
You can see the same info on Battery info menu, but you should navigate through the Canon menu system to see it.
I have 4 batteries and when I put one of them into the camera I can see right then which one is inserted.
Ok so this is stuff that works only on camera with chipped battery I'm supposing, no XXXD cameras support that.
Quote from: Pelican on January 06, 2013, 11:44:24 PM
I had a same problem.
Follow my instructions in the starting as a developer topic.
This line is the key:
ARM_LIBC_A=../../../arm-toolchain462/arm-none-eabi/lib/libc.a
You should give a relative path.
Thanks Pelican, that worked!!
Now I can compile the autoexec.bin which I found under \platform\5D3.113
What are the steps to follow? Since this is not a release the steps are unclear and I do not want to brick my 5D3!
My guess is:
1. Copy the "5D3-113-bootflag.fir" and the "autoexec.bin" to the CF card. Does this card have to be 32Gig or less?
2. Get the ML directory (some where) and copy it to the card. Where do I get it? Can I use one of the old ones supplied with Alpha 2?
3. Install the card and turn camera on.
4. Rotate your mode dial to Manual (M) position
5. Restore your camera to default settings (Clear all camera settings)
6. Launch the Firmware Update process.
7. If all goes well you see the green confirmation screen, restart your camera. Done
I will wait to confirm these instructions before I do this.
Thanks in advance for all your help.
Renato
You should make your card bootable... (EOScard). I used a 16 GB.
I read that there is also a multiple exposure feature in ML for the Mark III, as the 5D III already has this feature but where is it in ML? also once the Alpha 4 comes out with focus staking and so on I will donate for sure thanks;)
Hi Alex/Team,
its been mentioned a few times about either removing the 29min 59sec record limit (which i know youve stated that you dont want to provide that option due to legalities, which is fair enough, but i cant find an option on this ML for my 5D3 for an auto restart.
Is that option available?
The reason why i ask is that i shoot alot of live music performances, aswell as still photography (hence using dslr instead of dedicated camcorders) and sometimes the dslr can be in a place where i cant get to it easily without asking the drummer mid set to stop haha!
I also use a 60d, 600d and 7d for more angles, which i will dl the ML for them too.
Any help would be great!
Oh and ill donate too, great work your doing! this is my first time with ML tonight! :-D
The auto re-start is a normal Canon function to a max od 30 mins - 1 sec.
See page 232 of the Canon EOS 5D3 manual.
Note that you will lose up to a couple of seconds of video depending on Mem card speed.
Ignore previous msg from me.
Total rubbish, well not answering the question.
However, one reason for keeping a time limit is a very serious risk of overheating the sensor.
That function will restart recording when it stops without being stopped by you, so if buffer get full or 30min or 4GB file.
Restart means like if you were restarting it right after stop, so you will have gap in the two video (time camera takes to stop a rec and start another).
If you have multiple video sources you can start them at different times, record audio with an external recorder and them mount the clip to cut the gap with other point of view.
Quote from: vbcoen on January 08, 2013, 01:27:36 AM
However, one reason for keeping a time limit is a very serious risk of overheating the sensor.
Or maybe is just to don't sell it as a camcorder in EU (with different tax rate)
Quote from: jodykirton on January 08, 2013, 12:39:04 AM
i cant find an option on this ML for my 5D3 for an auto restart.
Is that option available?
+1 for Auto Restart
I'd love to see an auto restart option in ML, even if it means there's a couple second gap between the clips. I've become so accustomed to having
auto restart on my ML 60D and T2i. I miss it so dearly. ::)
As mentioned a few times, this feature is surrounded by some legal uncertainity. On 5D3 and probably on all DIGIC V cameras, the only purpose of this feature would be to bypass the 30-minute legal limit (because Canon already removed the 4GB one). Bring some lawyers to prove that it's OK, and I'll enable it.
Quote from: Pelican on January 06, 2013, 11:55:47 PM
The green/gray boxes are the battery performance.
The number is the actually used battery from battery history table.
If you register your batteries there are 1-6 battery info in the battery history.
You can see the same info on Battery info menu, but you should navigate through the Canon menu system to see it.
I have 4 batteries and when I put one of them into the camera I can see right then which one is inserted.
I can't see a way of registering batteries within Canon menus. How have you done this?
Moira
5D3, 5D2, 7D
Select Menu -> Spanner - > sub menu three (from left) -> secound down is 'Battery Info' SET, INFO now select 'Register'
Done , select Menu a few times to quit.
Quote from: a1ex on January 08, 2013, 09:43:06 AM
Bring some lawyers to prove that it's OK, and I'll enable it.
Just to be clear is the 5DMk3 able to record multiple splitted 29'59'' video when reaching 30'?
Can those be merged without frame skip like I read on other forums?
I don't get your concern Alex, there is a tax (4,9% EU only) on
imported camcorder not a limit, the limit is canon way to not pay import tax to keep price down (or to make bigger gains), but they are not breaking any EU tax law, ML either.
Canon is not selling imported camcorder/HDSLR (30' rec) in EU.
ML is not selling anything (AtomNinja do it instead).
Hint:GH1 was shipped with the limit only on EU version.
Is there anyway to enable autoboot on the 3rd alpha so that I don't have to run the installer every time I turn off and on the camera?
Quote from: aaphotog on January 10, 2013, 09:44:04 AM
Is there anyway to enable autoboot on the 3rd alpha so that I don't have to run the installer every time I turn off and on the camera?
no
Just bought a Lexar Professional 1000x umda7,
here is the result:
Write: 32.0
Read: 44.5
Write: 93.0
Really liking alpha 3. I've discovered one little bug though. When I make the display text green I get a green cube in the bottom right corner of the display in record mode. It doesn't happen with any other display colour and a reboot doesn't help. I really like the green display, reminds me of an Apple Iic.
I hope that in the 4th version will auto-loading and auto power sensor to save energy! Or many want?:))
Does anyone what criteria make the sensor overheat when shooting video?
eg, outside temp, recording mode, time of shooting etc.
Why, I would like to shoot some recordings of a meeting that will run well over one hour.
I then have to work out how to extend the 30 minute period apart from remembering to restart it every time.
Questions, question all I have is question.
.. and tomorrow maybe some answers :)
Quote from: a1ex on January 08, 2013, 09:43:06 AM
As mentioned a few times, this feature is surrounded by some legal uncertainity. On 5D3 and probably on all DIGIC V cameras, the only purpose of this feature would be to bypass the 30-minute legal limit (because Canon already removed the 4GB one). Bring some lawyers to prove that it's OK, and I'll enable it.
Auto
restart is exactly what it says. It
restarts recording after a short break but it does not remove the 30 recording minute limit as e.g. the GH2 hack does. It's exactly the same as if you press the record button again immediately after recording stops. How can there be any objection to that?
The new firmware for the 5D3 allowing clean HDMI output will ignore the 30 minute limit if you connect an external recorder but does not require Canon to impose a limit to evade the EU tax because it is not an in-built recording function.
I'm pretty sure that if we remove the 30min limit, Canon will be just happy since they still will not have to pay the import tax.
For us the import tax will not take place since we are "exporting" ML from EU, not importing it and also it's free so 4,9% of 0€ is 0€
Quote from: nigelbb on January 19, 2013, 02:23:20 PM
The new firmware for the 5D3 allowing clean HDMI output will ignore the 30 minute limit if you connect an external recorder but does not require Canon to impose a limit to evade the EU tax because it is not an in-built recording function.
That external recorder, if imported to EU, has to pay the tax since it will record more than 29'59". That's why Canon don't have to pay the import tax even with clean output.
Here in the EU there is 0% import duty on digital stills cameras but 4.9% on video cameras. Here is an extract from the actual regulations defining what is a video camera
products are classified as still image digital cameras 'unless they are capable, using the maximum storage capacity, of recording in a quality of 800 x 600 pixels (or higher) at 23 frames per second (or higher) at least 30 minutes in a single sequence of video'. Cameras that meet each of these criteria will be classified as video camera recorders.
Auto restart where there is a break in recording does not produce a single sequence of video hence even if it were implemented by Canon would not make the 5D3 a video camera under this definition.
Quote from: scrax on January 19, 2013, 04:47:59 PMThat external recorder, if imported to EU, has to pay the tax since it will record more than 29'59". That's why Canon don't have to pay the import tax even with clean output.
No clean HDMI output does not make it a video camera because the camera itself will not record >30 minutes of video. You could record the clean video stream with a computer & capture card & no duty for any recording equipment would be liable.
Here in the EU all DV camcorders that had a Firewire input were classed as video recorders & subject to 14% import duty rather than the 4.9% for video cameras. To avoid paying the tax the manufacturers disabled DV-in but it was possible either by entering a service mode on the camera or using so-called DV-Enabler device to re-enable the DV input. This has echoes in the way that many DVD & Blu-ray players can be rendered region-free by similar methods.
Quote from: nigelbb on January 20, 2013, 10:10:58 AM
Auto restart where there is a break in recording does not produce a single sequence of video hence even if it were implemented by Canon would not make the 5D3 a video camera under this definition.
confirmed. so movie restart is not contrary to this law.
Quote from: nigelbb on January 20, 2013, 10:13:43 AM
No clean HDMI output does not make it a video camera because the camera itself will not record >30 minutes of video.
Yes that was that I was saying.
QuoteYou could record the clean video stream with a computer & capture card & no duty for any recording equipment would be liable.
Since they are not cameras if you buy an imported card and computer you will pay 20% duty on those Not sure but if those are classed as 'information technology products' you will not pay any import duty, so you are right, with a computer as external recorder probably you can already record more than 30' and not pay any import tax.
Quote from: a1ex on November 08, 2012, 04:44:27 PM
Now, about the photo features. I can enable most of them, but, while running the random stability test, at some point the camera froze; I took the battery out, and found out that LiveView was no longer working (even when booting without card). Cleared camera settings and it's OK now. But this shows clearly that there's something fishy inside
Hi Alex and team
Thanks for the great software.
What exactly do you mean when you said you
cleared camera settings? I'm going to use ML on a pretty big project and I must be able to quickly get things going again if something freezes.
Regards,
capanno
Quote from: capanno on January 20, 2013, 05:06:25 PM
What exactly do you mean when you said you cleared camera settings?
He means "Menu - SET UP4 - Clear all camera settings".
Good luck on your project!
hi guys !
as promised i had the chance to play a little bit with the 1Dc : one word : whow!!!!
4K is the way to go.... even downsized in 1080P24 there is more detail than i ever manage to get on my 5DMKIII.
high iso performance is just stupid... a little edit I have done in 1 hour alone in Paris : https://vimeo.com/58056838
Video framegrab of this thing are just ridiculous....
enough said about this beast and back to reality = ANY twin digic 5 can apparently do MJPEG at 100Mb/s (and event way higher than that) the bottleneck is the card and not the camera... so the 1Dx is capable of that but the 1Dc digit are "overclocked" in order to achieve 4K Mjpeg compression on the fly and therefore there is a better cooling.... sensor is not heating more in 4K... (sensor is on or off but wont heat because of image size)
why Mjpeg? because MJpeg is just a JPEG image sequence in a quicktime container and therefore there is no image size limit where H264 do not support 4K yet.... ;D
so basically the 5D MKIII is definitively capable to record 4K Mjpeg but at which frame rate? ( I wouldn't mind a 12fps 4K ala go pro for special effect) and also it is possible to over clock the Digic V .... but it heat more
Att a1ex -
Sir, i have read and researched now for weeks reg ML, and i feel ready to take the plunge and install your software.
BUT i dont seem to be able to figure out exactly how! My biggest concern, is when i choose Mark III (which is the camera i own), it just refers to a page for download to Mark II..... and as i am new, and a bit nervous (disclaimers and harsh words about how it can ruin my camera etc.), i am reluctant to go ahead with both download and install......
any chance you can shed a little light on this?
kindly,
ThomasH
The first post of this thread has the link.
https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-5D3.113.Alpha3.zip (https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-5D3.113.Alpha3.zip)
Just wanted to say thanks, I'm testing out the alpha 3 on my 5dmk3 right now and it seems to be working great! I think later this week I'll head out and do some more strenuous tests!
Alex for some reason it does not please us very long. Waiting for April?
April 2015 :D
joker ;)
SanDisk is having a Amazon lightning deal today I was wondering the the SanDisk Ultra CompactFlash 16 GB Memory Card 30MB/s SDCFH-016G-U46 was a fast enough card to be able to do some of the work that the future of ml will hold. I know the Lexar 1000x is the preferred card, just wondering if this is even worth buying a couple sandisks. - link http://www.amazon.com/SanDisk-Ultra-CompactFlash-Memory-SDCFH-016G-U46/dp/B002ODISD2/ref=br_lf_m_1000862091_1_8_ttl?ie=UTF8&m=ATVPDKIKX0DER&s=electronics&pf_rd_p=1479321762&pf_rd_s=center-2&pf_rd_t=1401&pf_rd_i=1000862091&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=098GKFNE7BNYH2624TDW
Very underpowered and if you look, it has some bad write-ups. Also not listed as UDMA let alone UDMA7.
Stick to Extreme or above although that said I have been using Transcend Premium (400x) UDMA7 CF 32GB and they appear to be fine and a lot cheaper.
The Transcend CF cards and with Sandisk Extreme Pro SDHC UHS-1 used together in a 5D III with the CF card for video.
Hi! Alpha 3 seems to work pretty well. You guys are awesome.
Curious: Is Alpha 2 still online somewhere for download? I think I might prefer using that one instead of having to install it each time. At this point I mainly just use Focus Peak and Magic Zoom. Great work on this and thank you.
Quote from: brad on February 08, 2013, 03:03:14 AM
Is Alpha 2 still online somewhere for download? I think I might prefer using that one instead of having to install it each time.
As yet there hasn't been an Alpha version that doesn't need to be re-installed after power-off.
Oh OK thanks! :)
when I take my battery off and put the ac adapter I got it sayd can't communicate with battery and ask me to choose between ok or cancel, if I press ok it works but the Magic Lantern not installed and if I said cancel it turns the camera off, then when I put the original battery it installs no problem, any idea what this might be?
Is the adapter an official canon product?
That's the problem with 3rd party ACK-xn kit they do not have a chip to report such.
There is no solution other than use a battery or a grip with a pair of batteries.
Have the same problem myself.
Anyone know if the Canon version has the same problems?
Alpha 3 works perfectly for me. Hope autoboot version will be release soon. Than you guys..
So forgive me if this has been asked before, but I can't find mention of it... is it possible to allow this hack to open up the current 29 minute limitation the 5d Mark III has? This is all I am interested in as I have to record long meetings every quarter on my 5d Mark III and by no limitation of the camera itself, it shuts off at 29 minutes due to a European tax law penalizing video cameras with an additional 5% tax. I don't live in Europe, nor do I find this to be something Canon itself cares about past it's bottom line - As such, I am hoping the good people at Magic Lantern can correct this nonsensical limitation.
Just to clarify, currently the camera actually cuts the clips every time they reach 4GB, but these are seamless cuts that will only last until the 29 minute mark is reached. I have been recording meetings up to 2 hours long, non-stop, without any hardware problems so I know this is not a limitation (despite the rumors of overheating that some less-than-intelligent users have been spreading.) I have gotten pretty good at this, leaving only a .5-1 second gap between the 29 minute marks, but it's frustrating to have to baby sit a camera, and on occasion I miss the mark and we lose footage which makes me look very bad in the eyes of my peers despite the reason I missed it being that I was paying attention to the meeting. It would be AMAZING if this frustrating, and silly problem could be overcome with a bit of helpful hacking.
Please let me know if anyone here has some information on this topic - this is a feature that film buffs dismiss due to a lack of a need, but the rest of the community generally struggles with. In the end, as there is not a good reason for the limitation, I am hoping that we can eradicate this problem caused by crooked European laws.
The programmer seems to be worried on allowing the limit to be relaxed as he is under the impression it is breaking some EU laws.
This in fact is incorrect and that no law would be broken as the product is already in a EU country.
However the only way to get around it without the programmer (Alex) changing the source and binary file (ML program) is to download and alter the source code yourself and recompile it. That said getting the needed libraries together for any given platform is easier said than done, well it is for a Mandriva 2011.0 system.
Hope that helps a bit :)
follow on:
.. and yes, the limit is a right pain in the butt/ass (as appropriate).
V
The restriction has been removed in the nightly builds AFAIK but there are no mk3 nightly builds available so you'll have to wait a bit
We were only able to remove 4gb limit on 600D. Changing max recording time did not work. Still stops after 29" even with max rec sec set high. i'll investigate more on 6D but it looks to be a hardware limit or we changed the wrong one. in timelapse it records all night so there is hope.
Any updates on if the next alpha will contain more of the full still photography feature set? Very anxiously waiting. Thanks in advance.
Hi guys!
so .... after playing a bit with the sony FS_700, i have to admit that slo mo is cool !
what are the chance to have a mode to record on the buffer at higher speed rate such as 120fps or 200fps until it is full and then move the file to the card ?
I wouldn't mind having a 1080P120 or p200 even if it is only for 2-3 second ... that would really break the barrier...
by the way just for fun ....
http://cinemaeos.usa.canon.com/products.php?type=Camera&model=5dc
When we make happy Alex firmware with autoload? At least the basic functions. But then so is inconvenient to test
Silence in the air ............
Just saw the video for DotTune AFMA, WOW!! Thats some pretty impressive stuff,
Is there currently anyway for us to get the ML interface that on the video? Not sure if I missed anything.
Thanks Again !!
The simplest way is to run the developer FIR and compile ML. It's quite easy these days, the toolchain is precompiled, there is even a pre-configured virtual machine.
Is there a solution for Mac OS ?
Have to say really impressed you're including DotTune too - this is the sort of things applications are great at.
Looks totally cool!
got excited 'bout the Dot-Tune... guess its not implemented yet... looks cool though - not much into video yet, but some of the still enhancements look great
Quote from: Digitally Altered on February 25, 2013, 08:36:33 PM
got excited 'bout the Dot-Tune... guess its not implemented yet... looks cool though - not much into video yet, but some of the still enhancements look great
Honestly, I wouldn't count on it, the 5D3 looks like the forgotten stepchild of magic lantern development...
You do know that developers also have daily jobs and families, right?
Alex you are a hero !! Sorry to see that people dont see that you are spending a lot of your free time to help them.
I will be happy to support you via paypal when i can.
QuoteHonestly, I wouldn't count on it, the 5D3 looks like the forgotten stepchild of magic lantern development...
DotTune works on 5d3/6D/5d2 and even 50D. Just no pre compiled bins for some of those... ie 5d3.
A1ex is just trying to keep you from killing your cameras, esp with those that are all gimme gimme without enough reading.
I think people are just excited by the feature and keen to try it out.
Also on the forums I usually frequent there have been a few extra mentions of ML in relation to this and many people don't know where to start at compiling a bin file or have the confidence in case they get it wrong (myself included if I'm honest)
Obviously we all very much appreciate all the effort put into the development (well I damn well hope so!) and are just not so good at expressing this without looking like total suck ups.
I totally agrree with every point you made John
Just digging into the project (and the source later on tonight). Great job. Working well on my 5D III. Am thinking about recompiling with the focus menus enabled for testing. Has anyone tried focus stacking or trap focus yet? Is there any way to enable the menu through the UI or does it require a recompile? Thanks!
Focus stacking and trap focus work on 6D so they have a good chance of working here (obviously I can't try). Yes, you will have to recompile.
Well it's Saturday and I'm Swedish so: http://www.youtube.com/watch?v=He7b_AY15OA
Have a nice weekend all..
Where is this Dev Kit VM you speak of?
I have my own build compiled, before I turn on the boot flag with the provided firmware file: how do i turn it off later on?
The fir file turns the flag off/on. Once its on why would you though?
I belive that it only turns it on, there is no way to turn it off again.
Because as I understand it if you don't have an auto exec file from that moment on, the camera won't boot.
You're supposed to be able to unset the flag just like on the other cameras by moving the dial and re-running, etc.
But I've never unset the flag, no ML and camera is pretty useless.
Is this documented anywhere? What dial are you referring to?
I have tested all of it and I can not make it work, the bootflag stays on, if you have a eye-fi card the
camera will refuse to start with that card after applying the dev firmware.
The card has to be bootable and contain a autoexec.bin for the camera to start.
Since you have the "dev kit" fir you can install/uninstall like normal ML. Read the user guide. Previous releases I believe only worked for one boot only.
I'm very confused ? Are you refering to this:
Does Magic Lantern completely replace Canon firmware?
No. Magic Lantern runs from the card, as an add-on over standard firmware. You will still be
able to access all Canon functionality.
To go back to Canon firmware, you may:
• Press and hold SET at startup to bypass ML only once (for the current session).
• Format your card in the camera and choose to remove Magic Lantern.
• Disable the bootflag (this will uninstall ML from the camera; to do this, run Firmware
Upgrade and follow the instructions).
I does not work for me and I have tested several times and if I run the firmware update again it does not remove the bootflag, I get a msg that says that the bootflag is set everytime. And I dont get the question if I want to remove ML when formatting the card
Would be great if a1ex could clear this up; I'm ready to dive right into dev but would like to make sure I can back out of the boot flag change on the 5D3 if I ever want to sell the camera. Will restoring the 1.1.3 firmware reset the boot flag (and will it allow you to restore the same FW already on the device)? If not, is there some other way to turn OFF the boot flag later on?
Reinstalling Canon firmware will not remove the bootflag.
The full installer (not the dev kit) can remove the bootflag, but this is not fully working on 5D3.
a1ex, so when you say the full installer, do you mean if I create my own custom build of autoexec.bin and boot it, that it has an option to remove the boot flag? I've got it built; I'm just trying to find a way to boot it without making what appear to be at the moment permanent modifications to the camera...
No, the installer is the ML code that runs during the firmware update stage
Meh.... to me the ML additions (esp video, go port config loading) far outweigh the problems. 5d3 is pretty mature compared to say eos-m or 650d, on those I might want to remove it still if all props don't work, etc.
I totally agree with 1%, the problem with 5d3 is that ML removes the possibility to use the Canon support for Eye-fi cards and since it's not yes possible to turn the flag of I have to wait :-) with the Eye-fi usage which by the way works real good with my iPad and ShutterSnitch.
a1ex, could you maybe post a second firmware file that disables the auto-boot bit, so we can get to doing some dev without losing the ability to back out of ML if necessary?
How can I disable the bootdisk flag on my 5D3? I have tried all the different options I could find on this board, but nothing has helped. The reason I need this is because there is currently no other way to use my Eye-fi card.
Wouldnt it be possible for someone to produce a .fir file for disabling the bootdisk flag (similar to 5D3-113-bootflag.fir, which is used to enable it)?
All help would be greatly appreciated.
Thanks.
I managed to build a version of autoexec.bin which disables the Bootdisk flag, so I am good with that.
Now if I understand correctly, there is currently no way of running ML with Eye-fi on the 5D3 without having to do firmware upgrade each time the camera boots (which might be risky business if there is an upgrade counter)? This is because the Eye-fi card seems to have and issue with making it bootable.
So I'm confused then; does a custom autoexec.bin disable auto-boot or disable the boot flag, or both? From what I've read, these are two separate things.
I dunno... I put a non bootable card in my 6D and it starts. It was fresh, no autoexec.bin... just no ML. Put in an ML card and its fine. I don't have a 5d3 to test. Whats the deal with non-bootable eye-fi with no ml files? Does it just not start up?
Basically there are two things:
a) the camera has to be told that firmware (autoexec.bin) is being loaded from a bootable memory card at boot-time
b) the memory card has to be bootable for the camera to find the autoexec.bin on it
Now, with a) active, I could find no way to have the camera start-up with the Eye-fi X2 Pro card in it. I tried making the Eye-fi card bootable, non-bootable, formating it, placing and not placing the autoexec.bin on it, using it together with the CF card, using it together with a bootable CF card with autoexec.bin on the CF etc. A normal SD card works fine without issues.
Without the Bootdisk flag set in the camera (a) the Eye-fi works without any issues.
Got it working with a standard SD card. Verified motion detection and focus stacking work. Will test some other features. Are there any particularly dangerous features that write to the camera that I should be worried about?
Old focus patterns, leave them disabled. Besides that, not really.
Dear developers, thank you very much for your every day job. Your ML is really cool.
I have three Q:
1. How to return red color to Luma in Zebras? For EOS-M also. Now color is not enough contrast for me, especially for bright day.
2. Does Sound Recorder (Audio menu) work Movie mode only?
3. Audio RemoteShot (Shoot menu) does not work on my 5D Mark III.
Regards
Quote from: vbcoen on February 10, 2013, 03:25:40 PM
That's the problem with 3rd party ACK-xn kit they do not have a chip to report such.
There is no solution other than use a battery or a grip with a pair of batteries.
Have the same problem myself.
Anyone know if the Canon version has the same problems?
?
Dunno if A1ex found all of the beep/voice stubs for 5d3.
Quote from: vstrglv on March 11, 2013, 02:21:19 PM
Spoke to a Canon guy at Infocus at the NEC last week and he said that even the canon model has the same problem, eg, it does NOT have any smart chips installed.
So its a problem when using ML with a 5D3 and keep power running long term (ish).
Trap focus working nicely. Intervalometer working. Bulb Timer working. Audio Remote Shoot NOT working. Motion detect working. Mirror lockup working.
You'll need the stubs that make beep work for audio remote shot to work.
Some functions in audio.c appear to be turned off for CONFIG_5D3, such as audio_configure. I wonder if this is part of the issue. Was this turned off just because it's experimental, or because something was incompatible?
Nope, audio_configure is our function... Its turned off because new cameras have different IC + different commands.
Also, on 5d3 not much of a need for audio stuff as you already have a headphone jack and can turn off the AGC + wind filter. maybe only useful to adjust volume up and down but that can be done through a canon function.
Also there are 2 (maybe 3) sets of those "beep" functions. Some are backwards compatible, some have different parameters. I'm not sure which ones a1ex put in stubs.s... I know the ones for 6D were all the new functions. or wrong and didn't work.
So far I can beep and start dma but I can't stop it... Also I *think* i can read registers back and maybe set them but have no reg map.
Excuse me, but I repeat my question again :
How return red colour for Overexposure (Luma) in Zebras? For 5D mark ii and EOS-M also. Now colour is not enough contrast for me, especially for bright day. May be somebody send a zebra.c with red colour. I am going to compile autoexec.bin.
Thanks for the replies.. Where in the code are the existing stubs? I can take a look and see if I can find the 5D3 stubs for the audio detection.
You have to get the stubs out of the firmware image after decompiling it. then they go in stubs.s
What are you using to decompile? hex rays?
You have a choice of a few... ida (not free), pel's disassembler (free), a1ex's arm console (free and good once you get the detailed HTML).
I've got a license for IDA and Hex Rays; I need to set it up. If it would help, I should be able to decompile the firmware to C using hex rays... how do you get the firmware to dump? I ran the dev kit file and it dumped a file named ROM DAT but it was only 16k.
You need rom0/rom1.bin, you're looking in the right place, its somewhere in debug.c to dump it. It won't decompile to C, just pseudo code. The program portion of 5d3 is like 15mb.
Quote from: vtq on March 10, 2013, 01:08:53 PM
I managed to build a version of autoexec.bin which disables the Bootdisk flag, so I am good with that.
Now if I understand correctly, there is currently no way of running ML with Eye-fi on the 5D3 without having to do firmware upgrade each time the camera boots (which might be risky business if there is an upgrade counter)? This is because the Eye-fi card seems to have and issue with making it bootable.
Why they should put a firmware update limit?
Have you tried to make the eye-fi bootable with EOSBoot or similar?
Would like to support 5dm3 development. How to?
I'm trying to use Nightly Builds on my 5D3. And I have tried;
1- low level format in the camera,
2- adding fir file to SD Card( http://a1ex.magiclantern.fm/bleeding-edge/5D3/5D3-113-bootflag.fir )
3- download latest nightly build and copy to sd card
4- making card bootable on EOSCard
5- try to update .fir process in camera
But my 5D3 doesn't work with bootable card. It does not open. Tried without ML files and it's same. I guess when i make card bootable, camera does not recognize it. What did i wrong?
Thank you.
Edit: Of course using firmware 1.1.3
Quote from: ozcancelik on March 17, 2013, 02:16:57 PM
I'm trying to use Nightly Builds on my 5D3. And I have tried;
1- low level format in the camera,
2- adding fir file to SD Card( http://a1ex.magiclantern.fm/bleeding-edge/5D3/5D3-113-bootflag.fir )
3- download latest nightly build and copy to sd card
4- making card bootable on EOSCard
5- try to update .fir process in camera
But my 5D3 doesn't work with bootable card. It does not open. Tried without ML files and it's same. I guess when i make card bootable, camera does not recognize it. What did i wrong?
Thank you.
Edit: Of course using firmware 1.1.3
i dont have same camera as you have but this is my way to start up lastest Nightly.. :
format card : in side Canon
upgrade Firmware : to my version ( version my camera need to have )
put on card lastest Stable Magic Lantern 2.3V jun 2012 ( few mounts ago )
fun and experiments with ML 2.3 V ( all the time )
after some time :
I downloaded lastest Nightly Version what was ( Autoexec.bin and ML folder + some 0 kb PDF and firmware ) i downloaded it some 7 days ago so now its not lastest. file have some 4 mb + 1.4mb in ML folder or something.
ireplaced autoexec.bin and ML Folder on my card where i was have instaled 2.3V Version
i put again card to camera and i start it up ..
i push trash button i sean welcome screan from Magic Lantern Nightly Version . i push again some buttons on camera boody and i was ready to go..
i use this steps .. everything works grate . but this is just sugestion from my expirence..in my case it works . but im not sure if this is fully right way to instaling it..
edit :
im not sure but i thing you need first upgrade firmware ( of course if u need ) and after this put on card ML .. so first put firmware files on card . upgrad if camera need .. and later when your camera upgrade firmware ( if need it ) just delete upgrading firmware file from card cuz i dont thing u need it on card any more after upgrading.. later put ML on Card and instal ML ..
Alpha 3 works ok. But problem is 5D3 with Nightly Builds. A1ex says there (http://www.magiclantern.fm/forum/index.php?topic=3072.msg25178#msg25178) "Try the developer FIR, make the card bootable and should work." When I make SD card bootable (with or without autoexec.bin, developer .fir and ML folder) camera doesn't open.
Without bootflag it Nightly builds doesn't work too. I don't make card bootable just copy developer 5d3 .fir file, autoexec.bin and ML folder it says "enable bootdisk :)" but there are no Magic Lantern on trash button. (Also "Set" button does not work with this option. Summary: No ML and No Set button work)
Also I guess Stable Magic Lantern 2.3V jun 2012 can not work with 5D3 anyway.
Add: Is there any different way to make SD card bootable? I'm using EOSCard with enable 0x047 and 0x05C.
Put the fir on non bootable card, set the boot flag.
Then make card bootable and add ML files.
done.
Obviously, if you copy ML for 5D2/550D/etc it won't work on 5D3.
My reply was to a user who compiled ML himself.
Quote from: a1ex on March 17, 2013, 07:31:58 PM
Obviously, if you copy ML for 5D2/550D/etc it won't work on 5D3.
My reply was to a user who compiled ML himself.
I use nightly builds (http://nanomad.magiclantern.fm/nightly/). This files do not work with 5D3? Should i compile it from source code??
Low level format, copying
developer fir file to non bootable SD card, update firmware from camera without ML files(It says some error like there is no ML files), remove card and copy autoexec.bin and ML folder, making card bootable with EOSCard. Doesn't work. It's not Eye-Fi card. Kingston 32Gb 100x Sd card.
Nightly builds don't have 5D3 built in. You need to download the source tree and compile it with 'make 5D3', then copy the autoexec.bin to a bootable SD card, along with the other files from the 5D3 release. You can build it quite easily if you grab one of the virtual machines set up with the dev environment.
I have uploaded a 5D3 autoexec.bin from latest source head here:
http://www.freefilehosting.net/autoexec_1
I take no responsibility if this damages your camera.
Quote from: NerveGas on March 17, 2013, 08:38:51 PM
Nightly builds don't have 5D3 built in. You need to download the source tree and compile it with 'make 5D3', then copy the autoexec.bin to a bootable SD card, along with the other files from the 5D3 release. You can build it quite easily if you grab one of the virtual machines set up with the dev environment.
I have uploaded a 5D3 autoexec.bin from latest source head here:
http://www.freefilehosting.net/autoexec_1
I take no responsibility if this damages your camera.
Now problem is solved. Thank you so much. I saw 5D3 changes in changelog so I thought Nightly Builds works with 5D3.
Thank you again!
Just wanted to get a little more ease of mind before installing alpha 3 - am I right in assuming that no 5D mkIII's (that we know of) have been bricked by ML? :)
I've run all kinds of stuff with Alpha 3, as well as the latest repo head, and had no problems. Someone warned me to stay away from legacy focus points.
Magiclantern for the 5d3 can auto boot now so that I dont have to install every time I shut the camera off?
If you build an autoexec.bin you can make a bootable SD.
I was trying to make ML auto-boot on my Mark III - unfortunately without success.
I read the last few pages in this thread and tried to figure out what to do.
Now, what I did is this:
I downloaded "ML for 5D Mark III - Alpha 3" from this tread and additionally autoexec.bin from this url: (http://www.freefilehosting.net/autoexec_1) that user NerveGas posted a few days ago.
I put all files on my card and used eoscard.exe to make the card bootable.
I put the card into my Mark III and turned the camera on. It didn't autoboot. Manually starting ML works fine though.
There's also no autoboot option in the ML menu.
What did I miss? I thought, all I need is the autoexec.bin, which, as far as I understood it, is enabled for auto-boot?
Quote from: JohnN on March 02, 2013, 11:48:15 AM
many people don't know where to start at compiling a bin file or have the confidence in case they get it wrong (myself included if I'm honest)
+1
I would love to try the DoTtune implementation, but as far as I understand, this feature is not included in the Alpha3.
Could anyone be persuaded to compile a version with DoTtune and share it?
Edit: the vanilla alpha3 works to some extend, and I must say that the gradual exposure change is amazing!
Another feature that canon should ahve thought about long ago :)
Still, if anyone would care to share their different versions I'd be more than happy to test a few more features.
In case I get impatient, how would one go about compiling a a 5D ML with the DotTune feature enabled?
I may have overlooked this question in reading all 26 pages of posts, but has there been any sort of study on the effects of re-loading the firmware on every single startup? Seems to me like this could be damaging, but I'm merely a UI/UX designer, and by no means a developer...
:)
I think it's time to make a firmware autorun for all. Because they themselves are beginning to make it bootable, and can cause problems with the machine. And so we are responsible for our technology, so really hard to do for us to boot, would quickly began testing her, and the desire disappears each time you turn it to register again!
Quote from: NerveGas on March 17, 2013, 08:38:51 PM
I have uploaded a 5D3 autoexec.bin from latest source head here:
http://www.freefilehosting.net/autoexec_1
I take no responsibility if this damages your camera.
Thank you so much it work great like a treat :) :-*
I just installed this on my 5Dmk3, very interesting indeed.
can anyone tell me where the disable Audio Gain Control is on this build?
thanks.
You can disable AGC in camera without ML. Press Menu button then go to SHOOT 4, SOUND RECORDING and then select manual.
RTFM man!
I already had it on manual and it was still hissing with my new rode videopro mic.
so i thought it was still on somehow!
its not just me!
http://www.dvinfo.net/forum/canon-eos-full-frame-hd/508798-hissing-sound-5dmk3.html
I have the same problem. Well it's all down to ML to figure out the audio chip in the 5D mark 3ree and maybe give us a mic input selection feature. Or maybe we both just need to get a better microphone. :)
Ok I've worked it out.
set the microphone to +20Db and the recording level to only a few clicks above 0 on the camera, bingo no hiss!
:-)
As a relative noob to this, I've ben trying to glean as much as I could from the post in this thread, but can someone clarify if the nightly builds contain all the features of ML not in the alpha? is it just more risky?
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) (http://www.canon-europe.com/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_5D_Mark_III.aspx?type=download&page=1).
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 (http://nanomad.magiclantern.fm/nightly/). 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 (http://www.magiclantern.fm/forum/index.php?topic=2602.msg28976#msg28976). 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 (https://bitbucket.org/hudson/magic-lantern/raw/2063f5c9e7259707c07e98542a33dd8bdfe4da7e/contrib/make-bootable/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 (http://www.magiclantern.fm/forum/index.php?topic=3072.0) 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 :)).
Thanks for the guide - I tried it using last nights build - magiclantern-v2.3.NEXT.2013Mar30.60D.550D.600D.50D.500D.5D2.1100D, sadly it didn't work, in fact the only thing it did was disable liveview.
I will confess to not doing the last step to ensure it autoboot, which I'm glad about actually.
It may have been just that build, but I did note the lack of 5D3 in the title.
The card was a previously working boot enabled card and I could load the firmware okay.
I'm not looking for help, I'm just reporting back what happened to me - thanks again for the guide though, no doubt it will be of use.
EDIT - I tried a couple more times and saw a message saying enableboot then a :-) followed by frozen or in one case an error 80.
I would suggest we hold off playing for now, or at the very least try a different build.
Even on the occasions where the firmware loaded and didn't lock it the liveview was disabled and the delete icon did nothing so I never saw a menu to try anything else.
Odd. The nightly build (magiclantern-v2.3.NEXT..) zip is only used for the fonts/other data, not the Magic Lantern autoexec.bin itself, so pretty much any nightly should work. I'm not sure what I did differently to you, because it works for me™.
hehe, loved the TM :)
I recall seeing a spreadsheet posted of what features are enabled on each camera .
It's been a month or so since I saw that posting and I can't find it for the life of me. I just upgraded from a 7D to 5D Mk III and am trying to find the difference in usable functions .
If someone could direct me to the link it would be most appreciated .
http://nanomad.magiclantern.fm/feats.html
Quote from: Francis on March 30, 2013, 07:59:27 PM
http://nanomad.magiclantern.fm/feats.html
Thank you very much !
What are the main deciding factors in moving from alpha to full release / What decides which features are considered safe?
Statistics of dev testing and/or user feedback?
Does the latest nightly build have all the features listed @ http://nanomad.magiclantern.fm/feats.html enabled?
Keep up the good work :)
the full-feature fw runs like a charm, thanks to anyone involved!
Anyone heard of an update to the press release last october about a firmware update for the 5d III that will have clean hdmi out? It's april and no news.
http://www.usa.canon.com/cusa/about_canon/newsroom?pageKeyCode=pressreldetail&docId=0901e024806daf9c
http://www.canonrumors.com/2012/10/canon-eos-5d-mark-iii-firmware-adds-hdmi-af-upgrades/
Quote from: sicetime on April 02, 2013, 09:25:54 PM
It's april and no news.
It's the third day of April!
[spoiler]Heck, it's still only the second day of April in some parts of the world![/spoiler]
For once I hope the firmware comes a little later as it will no doubt knock the release of ML back :(
Quote from: hirethestache on March 23, 2013, 11:54:58 PM
I may have overlooked this question in reading all 26 pages of posts, but has there been any sort of study on the effects of re-loading the firmware on every single startup? Seems to me like this could be damaging, but I'm merely a UI/UX designer, and by no means a developer...
Quote from: hirethestache on March 23, 2013, 11:54:58 PM
I may have overlooked this question in reading all 26 pages of posts, but has there been any sort of study on the effects of re-loading the firmware on every single startup? Seems to me like this could be damaging, but I'm merely a UI/UX designer, and by no means a developer...
Firmware is loaded to RAM I think, not any write-limited memory like ROM.
Hi,
I've been using ML for 550D and 5D mk3 since last autumn.
I've been waiting for some of the features I miss on my 550D, mainly the intervalometer. I thought it isn't yet available on the Alpha 3, but the feature matrix shows the feature available on 5D mk3, http://nanomad.magiclantern.fm/feats.html.
Is this only on a nightly build?
It's not on the nightly build, but if you check out the latest code and build it, you will get the intervalometer. To run the autoexec.bin you need to enable the bootflag using the special .fir from the first post, and make your card bootable.
Ok, thanks for your quick reply.
Could you please advise me with the risks of this procedure. I made my 550D card bootable a couple of years ago, but am slightly hesitant to do it with the 5D mk3. I've read that bricking the camera is possible when doing this.
Hi,
I just enabled the bootflag but and if we want to go back and disable the bootflag what .fir we have to do and one thing is there any difference between the ML files in the 2.3 stable vs the nightly?? I had a blue crash screen with the stable release but not with the nightly, otherwise I'm very happy with the results, excepting the battery consumption and the 65C degrees which my camera reaches, are normal this last things???
Thanks
Quote from: Audionut on April 03, 2013, 01:41:37 AM
It's the third day of April!
[spoiler]Heck, it's still only the second day of April in some parts of the world![/spoiler]
ATMOS is demoing with the new canon firmware at NAB saying it will be releases in may.
http://www.atomos.com/whats-new/
Quote from: DavidBrumbley on April 08, 2013, 07:46:10 PM
ATMOS is demoing with the new canon firmware at NAB saying it will be releases in may.
http://www.atomos.com/whats-new/
I hope so! ;) Canon said the AF option at F8 would be available in that firm as well as the 1DX and other 1D/1Ds becoming the 1st 5D which have this option and the 1s Canon which have it and isn´t part of 1 series ;D
BTW, I was trying the bulb and intervalometer tonight here in EU are 4am 8) and it works perfectly fine :)
Thanks to all devs for doing this possible, the fact of use a bulb and intervalometer without a remote shutter is great one thing less to carry on!
Quote from: eyeland on March 31, 2013, 12:10:25 PM
What are the main deciding factors in moving from alpha to full release / What decides which features are considered safe?
Statistics of dev testing and/or user feedback?
Does the latest nightly build have all the features listed @ http://nanomad.magiclantern.fm/feats.html enabled?
Keep up the good work :)
Bump
Just read on CanonRumours that the new firmware is very likly to be by the end of this month - http://www.canonrumors.com/forum/index.php?topic=14147.0
QuoteEOS-1D C
Another announcement may be coming at the end of April letting us know when we can expect the 25p at 4K update. One of the challenges is encrypting the firmware to combat hacking or reverse engineering of the software inside the camera.
As for the 120fps/720p mode that leaked in a photo a few weeks ago, that feature won't appear in the final version of the firmware update due to "stability concerns".
I lol'd
I guess you need dual digic to record that 120fps and they couldn't make it work/sync.
On 5D3 Ghost Image only works for Panoroma? I'm trying some stop motion thing but ovelay always shows little bit right side.(I guess this way works for panorama). Ghost image still needs to be improvement for 5D3? Or it just works for pano shots? I'm using 11.04.2013 Nightly Build.
Thank you.
You can move the ghost image using the directional pad.
Nope. Doesn't work. Always shows right side and cannot change position.
Quote from: Francis on April 15, 2013, 03:39:22 PM
You can move the ghost image using the directional pad.
Works for me, just tried.
as there is now a larger userbase than just you alex and no problems seem to arise, are there any hopes to get 5d3 into a stable state?
Yes, see the 7D thread, we want to release both updates at the same time. It will take a while, because we are a bit busy at work.
I still have some random issues like camera locking up on startup or not fully shutting down, so you'll have to take the battery out after each run.
well, we're all waiting patiently :)
With the announcement of the 5d Mark III firmware update, scheduled for April 30th, how would that affect ML?
Are people excited for the update? Should users be wary of upgrading since it may not allow ML to work?
Love to hear the communities thoughts, and as always, thank you for your hard work!
http://www.canonrumors.com/2013/04/eos-5d-mark-iii-firmware-coming-april-30-2013 (http://www.canonrumors.com/2013/04/eos-5d-mark-iii-firmware-coming-april-30-2013)
ML only works on 1.1.3 for now, but you should be able to upgrade and downgrade.
If Canon likes us, we'll be able to update ML to work with the new firmware.
Quote from: a1ex on April 22, 2013, 04:11:40 PM
(...)you should be able to upgrade and downgrade.
If Canon likes us, we'll be able to update ML to work with the new firmware.
Fingers crossed
Quote from: a1ex on April 22, 2013, 04:11:40 PM
ML only works on 1.1.3 for now, but you should be able to upgrade and downgrade.
If Canon likes us, we'll be able to update ML to work with the new firmware.
If Canon were to somehow restrict/disable the ability to use Magic Lantern :o it would be public suicide as I'm sure many users would think twice about buying Canon products in the future. Especially when the market has so many choices of products with the likes of Blackmagic etc..
I own a couple of 550d's and a 5DMKIII and Magic Lantern is the only thing that makes them anywhere near reliable to use on mission critical jobs.
Excellent work as always by everyone involved in ML development, looking forward to the weekly build. 8)
Bryan
So i have been saving and seeing a few options. Should I save for extreme cf cards, or invest in something like an atomos ninja and straight to ssd.
There was a notion a while ago about the possibility of using photo jpeg and getting extreme resolution and bitrates from the 5d, is that no longer a pipe dream?
If I went the Atomos route, would I still be able to load ML through the SD and record with the Atomos Ninja? I am guessing there is no way to tell until next tuesday.
Thanks!
I wanted to report a bug I found in the nightly build on my 5D mk3 (I know they are probably full of them, but I just thought I would contribute to working toward a stable release).
When I use the HDR feature set to auto in manual mode on the camera, if I switch lenses or change shutter time for my base, first exposure the auto exposures are out of order (supposed to b 0,+,-,++,-- ect). and the exposures aren't done correctly. I can easily fix this by going back into the ML menu after I change lenses and turn the HDR feature on then off again. Not sure you you have experienced this before. Pretty small bug but repeatable.
In testing out the nightly build on my 5dmark III i enabled the bootflag on my camera. I was aware that i would need to run a boot enabled sd card but my problem now is that every time my camera auto powers off it takes around a sec to reboot which i assume is the camera looking for ML files to run. Now it may not sound like much of a delay but i am expecting my camera to focus and fire as soon as i pick it up. Last weekend at a shoot i missed several fleeting moments waiting for my DSLR to boot like a P&S.
A few pages back someone mentioned that they were able to disable the bootflag for the 5dmark III. Can someone please post the fir file to disable the bootflag or any other way to disable the flag? I do run ML on my 60D and i know that when you boot ML in manual mode you can change the top dial to disable the bootflag, i've tried every combination of boot and dial changes that i can think of to no avail.
alex, new firmware was leaked early. I can post a link if you'd like to take a look at what Canon did.
We can't even be certain if it's the final one, so just be patient until Canon publishes it.
No worries, I'm in no rush just didn't know if it would help out.
Here is the new firmware 1.2.1 for Canon 5D MK III
http://www.canonrumors.com/forum/index.php?topic=14486.msg262450#msg262450
Fir_tool 0.5 (20Mar2010)
fileLen = 0x111a6ac
---.fir header---
0x000: modelId = 0x80000285, 0x010: version = 1.2.1
0x020: checksum = 0x77b669ad
0x024: updater1 header = 0xb0
0x028: updater1 offset = 0x120
0x02c: updater2 offset = 0xffffffff
0x030: firmware offset = 0x1ef9c0
0x034: 0xffffffff
0x038: embedded file size = 0x111a6ac
0x03c: 0x0
0x040: sha1 seed = 0x9965fc33
0x044: 0x00000004 0x00000000 0x00000020 0x00000024 0x00000044 0x000000b0 0x001ef910
0x060: 0x1ef9c0
0x064: firmware length = 0xf2acec
0x068: updater1 hmac-sha1 = 9e2a03ab26c1684fa84d551742bb05430853f24a
0x088: firmware hmac-sha1 = ca21040939b0be86bb951def34e94495d8bc8791
---updater1 header---
0x0b0: updater1 length = 0x1ef8a0. starts at 0x120
0x0b4: 0x1ef8a0
0x0b8: 0x0
0x0bc: xor seed value = 0x5185d350
0x0c0: 6d7c5aaf752d55ac7041169fc22df3e8
0x0d0: 4123f04f138d246a6725ff86f8a1a4e0b40c1c04039abfca468c726f3fb853aa
0x0f0: 113aece6c503b5e41816aae331bba221
0x100: 4d4a9a1951db9782ec8ac5d06302bab7a9f57ce317d28818a7a2df08c6998618
0x120: --- updater1 (ciphered) ---
---firmware header---
0x1ef9c0: (+0x000), offset to decryption data = 0xc
0x1ef9c4: (+0x004), offset to encrypted data = 0x7c. starts at 0x1ef9c0
0x1ef9c8: (+0x008), total firmware length (including header) = 0xf2acec. starts at 0x1ef9c0
-
0x1ef9cc: (+0x00c), firmware length (encrypted part) = 0xf2ac70. starts at 0x1efa3c
0x1ef9d0: (+0x010), 0x00f2ac6c
0x1ef9d4: (+0x014), 0x0
0x1ef9d8: (+0x018), 0xe1b9b48f
0x1ef9dc: (+0x01c), 93b9ffeb652ce01794b33b30ae8dd219
0x1ef9ec: (+0x02c), fb38f38dd22403cb34b16f95dd4e8b3c5a2c4c59ad002098ebe6229a000c84e4
0x1efa0c: (+0x04c), 66c7d7b88a0bb332125f8278c874bd7c
0x1efa1c: (+0x05c), 6cd537a78be7c5e05fb76429c879932e9704aeaf2f96c2d973c18620bd01be4b
---firmware (encrypted)---
0x1efa3c: (+0x07c)
I guess no 6D huh? Big frowns... the HDMI buffer is just like on digic IV cameras.
Quote from: a1ex on April 26, 2013, 07:12:05 PM
We can't even be certain if it's the final one, so just be patient until Canon publishes it.
It should be, I heard they started installing the new firmware at Canon service centres last week. They did the same thing with the MK2 24p update, I went in to a service centre and got it a week before it was officially released.
It was left on a SD card that had just come from Canon Service.
I knew you guys usually are on the look out for firmware other wise I wouldn't have mentioned it. Right now I don't need F8 focusing or HDMI out I'd rather have ML!
Here's a snapshot from the current source code, so you can try the latest raw developments (DNG burst, RAW histogram) and pretty much everything from the nightly builds. The feedback from the early adopters who compiled from source code was positive, I've also ran the built-in tests, and it seems OK at first sight.
Download: autoexec.bin (http://a1ex.magiclantern.fm/bleeding-edge/5D3/autoexec.bin)
You'll have to enable the bootflag with the developer FIR (first post), make the card bootable (eoscard) and copy the other files from the nightly zip. It works only on firmware 1.1.3.
I'll be offline for one week and hopefully I'll get some time to try all the stuff and fix the installer. If it goes well, the next step is to enable the nightly builds.
Thanks for all your hard work and effort. Works like a charm and will be fun to play around with!
Can anyone provide a link with instructions on how to compile one of the nightly builds(with a mac) so that I can install on my 5d3?
http://support-au.canon.com.au/contents/AU/EN/0400079902.html
Firmware 1.2.1 now official
"You shall not alter, modify, disassemble, decompile or otherwise reverse engineer the Software and you also shall not have any third party to do so."
Sorry, folks.
Quote from: a1ex on April 30, 2013, 09:10:37 AM
"You shall not alter, modify, disassemble, decompile or otherwise reverse engineer the Software and you also shall not have any third party to do so."
Sorry, folks.
What do you mean? Do you want to shut down the ML development?
Just wait until Canon posts it without a non-RE clause.
No EULA with this link.
http://www.canon.co.uk/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_5D_Mark_III.aspx?DLtcmuri=tcm:14-1048653&page=1&type=download
Quote from: a1ex on April 30, 2013, 09:52:58 AM
Just wait until Canon posts it without a non-RE clause.
[reliefed] :)
I am surprised that the discovery of low fps raw video aka DNG burst mode has not generated more forumactivity?
Is there a thread I am blissfully unaware of?
Quote from: eyeland on April 30, 2013, 12:49:34 PM
Is there a thread I am blissfully unaware of?
Quite a large one ;)
http://www.magiclantern.fm/forum/index.php?topic=5240.0
"hold all calls, I am going in " :D
Quote from: aaphotog on April 30, 2013, 03:41:42 AM
Can anyone provide a link with instructions on how to compile one of the nightly builds(with a mac) so that I can install on my 5d3?
Alex already gave you everything you need with instructions.
I just tried to downgrade the 1.2.1 firmware back to 1.1.3, won't work! Bastards!
EDIT: Finally got it to work. I downloaded 1.1.3 from another Canon server and reformatted the card.
so is raw video with 5dmk3 really possible without external recorder?
please: can anyone provide a link with a firmware for testing this.?
would be great, i have never compiled a firmware and have no idea what to do??
thx. swinxx.
Check back about a page and Alex posted the file and instructions. If you've never done this before you might want to wait until the "cookie cutter" version is ready. i.e just drop the files on the card and go.
Quote from: a1ex on April 29, 2013, 02:36:25 PM
Here's a snapshot from the current source code, so you can try the latest raw developments (DNG burst, RAW histogram) and pretty much everything from the nightly builds. The feedback from the early adopters who compiled from source code was positive, I've also ran the built-in tests, and it seems OK at first sight.
Download: autoexec.bin (http://a1ex.magiclantern.fm/bleeding-edge/5D3/autoexec.bin)
You'll have to enable the bootflag with the developer FIR (first post), make the card bootable (eoscard) and copy the other files from the nightly zip. It works only on firmware 1.1.3.
I'll be offline for one week and hopefully I'll get some time to try all the stuff and fix the installer. If it goes well, the next step is to enable the nightly builds.
Where is the nightly zip for the 5d3?
Latest post in the nightly thread was on april 26th and it says that there are no 5d3 nightly???
Quote from: aaphotog on May 01, 2013, 05:57:14 AM
Where is the nightly zip for the 5d3?
Read! Directions are 1 post above yours.
Quote from: Jason Montalvo on May 01, 2013, 01:59:34 AM
Check back about a page and Alex posted the file and instructions. If you've never done this before you might want to wait until the "cookie cutter" version is ready. i.e just drop the files on the card and go.
http://www.magiclantern.fm/forum/index.php?topic=2602.msg32231#msg32231
Quote from: Audionut on May 01, 2013, 07:38:15 AM
Read! Directions are 1 post above yours.
http://www.magiclantern.fm/forum/index.php?topic=2602.msg32231#msg32231
I did read and that post says this
You'll have to enable the bootflag with the developer FIR (first post), make the card bootable (eoscard)
and copy the other files from the nightly zip. It works only on firmware 1.1.3.
The problem is, like stated, I dont know where to find the nightly zip. That was my question. Where is the link to the nightly at?
In a big section at the top of this forum labeled Nightly builds. ;)
http://www.magiclantern.fm/forum/index.php?topic=3072.0
Quote from: Audionut on May 01, 2013, 07:56:17 AM
In a big section at the top of this forum labeled Nightly builds. ;)
http://www.magiclantern.fm/forum/index.php?topic=3072.0
I went to that link a day or so ago, and the last post says
Quote from: nanomad on April 27, 2013, 01:52:43 AM
There are no builds for the mk3
So am I supposed to put the nightly build from the link below with the rest of the items when compiling the ML for 5d3?
The link seems to be good for everything BUT the 5d3(it's the only cam that doesn't seem to be listed)...
Is that the correct download link to use, though?
http://nanomad.magiclantern.fm/nightly/
In all honesty, if you can't follow the instructions already posted, you should step away and go and enjoy your camera.
The instructions to unbrick your camera are a whole fuckload more complicated then this process to run the latest source snapshot.
You'll have to enable the bootflag with the developer FIR (first post)
make the card bootable (eoscard)
Download the latest nightly zip http://nanomad.magiclantern.fm/nightly/
Extract the contents of the nightly build to the card you made bootable
Overwrite the autoexec.bin with the one a!ex posted here http://www.magiclantern.fm/forum/index.php?topic=2602.msg32231#msg32231
Insert card, turn the camera on, prey!
on my mac i have tried to format the sdcard with the macboot.class app but got a permission denied error..
what can i do now?
and which option is the right one in that prog.
thx. sw
Has anyone started looking deeper into the 1.2.1 yet?
Any ideas on how hard/easy it will be get the alpha to work with it?
Quote from: Audionut on May 01, 2013, 09:18:59 AM
In all honesty, if you can't follow the instructions already posted, you should step away and go and enjoy your camera.
Amen.... imagine what these guys could do if they didn't have to answer the same questions over and over again day in and day out all because people don't read.
Like I loaded ML and nothing happened... I see the same Canon Menu.
Or every time I restart my camera ML is gone! PLEASE HELP! ::)
Thanks Audionut. Figured it all out.
now running the latest nightly build.
Now, to find out how to record that RAW video :-)
Hey guys.
I used the ML Alpha 3 before with my 5D Mark III previous FW 1.1.3. Worked fine.
Since today when I updated my Mark III FW to 1.2.1 ML no longer works.
Camera Red LED flashes forever and have to take out the battery.
I understand this is a known issue and must use the old FW.
I'd rather stay with Canon's 1.2.1 than revert to 1.1.3.
Unless I don't have any other choice as I really love the Magic Lantern :)
Is there any tweak or anything to be able to use the ML AlphaIII with Canon's FW 1.2.1?
Or at least any rough wild estimate on when's the Magic Lantern Alpha ver support the MK3 FW 1.2.1?
If it's only a short wait, I'd rather just wait patiently.
Thanks for the great work and for being so cool.
I tried searching this message thread and others but can't find a clear answer.
You use the "developer fir" to enable the boot flag.
My question is how do you disable the boot flag and restore the camera to factory default.
Now before I'm jumped on I understand how to remove ML is a stable release version, format card in camera and select remove ML, but I want to know if this same method applies here to an unreleased version where you have to use the developer fir to enable the boot flag or if a special method is required to remove the boot flag and disable the bootable card features.
I would appreciate any help.
Thanks
Quote from: Goldstein on May 01, 2013, 11:03:39 PM
Hey guys.
I used the ML Alpha 3 before with my 5D Mark III previous FW 1.1.3. Worked fine.
Since today when I updated my Mark III FW to 1.2.1 ML no longer works.
Camera Red LED flashes forever and have to take out the battery.
...
Thanks Goldstein! You've confirmed my suspicion that ML 5D3 Alpha 3 does not support 1.2.1, looks like we'll have to wait for Alpha 4 to add the support, I might still try the 1.2.1 update though. Does anyone know a sever still hosting 1.1.3 and would you please post a link to it if not too much trouble, thanks
Your boot flag stays on from 113 -> 121 most likely but the FW is all different, probably wouldn't even boot stubs are in the wrong place. It has to be updated. It just came out what, 2 days ago?
Oh cool, so Alpha 3 might support 1.2.1 also. Might not have to wait as long as Alpha 4 then. Thanks 1%
Nightly would support new fw. Can cook the same feature set as alpha 3... but why?
Quote from: 1% on May 04, 2013, 07:29:06 AM
Nightly would support new fw. Can cook the same feature set as alpha 3... but why?
oh the newest nightly works for 1.2.1? I want both because I like the new "mirror LCD" feature in 1.2.1 so that the Cameraman can use the LCD while a focus puller in on the side of the rig with a field monitor pulling focus, but I also like to have Magic Lantern's focus peak to help the focus puller and also confirm to the cameraman that focus was achieved.
As it is right now (with 1.1.3) when I plug in the external monitor the LCD blacks out and so the cameraman and AC have to crowd together on the field monitor screen, but they get focus peaking due to magic lantern. So my choices are less crowding or focus peaking, but I want both naturally :) lol
btw Canon USA still has both 1.2.1 and 1.1.3 up for download http://www.usa.canon.com/cusa/consumer/products/cameras/slr_cameras/eos_5d_mark_iii#DriversAndSoftware
It will, not yet.
ARG! looks like canon set it up that LCD still shuts off if you don't clear overlays, since magic lantern peaking is an overlay it may not even work.
Heh, I'd just be happy to port the mirroring to 6D. Seems useful, regardless, maybe this problem can be amended.
Quote from: 1% on May 04, 2013, 10:07:50 AM
It will, not yet.
Any rough guess as to when we can use any version of ML on the MK3 FW 1.2.1 ?
It's a tough choice now if to use FW 1.2.1 without ML or go back to 1.1.3 with ML :-\
When you see a 1.2.1 folder in the ML tree then its being worked on.
Just dropped back to 1.1.3 and for the first time it worked :)
Thanks guys I'll have to have a play around - its the first time I've seen it since I had it on the 60D and it looks to have changed a fair bit.
I noticed that the newest nightly build is the 5th of may.
I formatted my card and compiled the nightly build from scratch again, but am I supposed to use the 5d3 fir file found ion the first page of http://www.magiclantern.fm/forum/index.php?topic=2602.675 (http://www.magiclantern.fm/forum/index.php?topic=2602.675), or the fir file found in the new nightly build(may 5th) although it says 1100d?
when I used the fir found on the other thread... everything works fine, but at the bottom when I boot up my camera, it says april 30th.
Quote from: g3gg0 on January 20, 2013, 10:44:30 AM
confirmed. so movie restart is not contrary to this law.
A1ex, et al.
Here's a great article and discussion from dpreview on the 30 minutes issue:
http://www.dpreview.com/news/2012/05/18/WTO-looking-at-moves-to-remove-30-minute-limit-from-digital-cameras
more:
http://www.tested.com/tech/photography/44445-why-digital-cameras-have-a-30-minute-video-recording-limit/
WTO are changing the rules shortly and an European issue. I don't think any Magic Lantern work violates any tariffs to offset potential loss of revenue from folks pirating shows w/ their DSLR. ML is not in the business of selling/importing any video recorders.
I would highly encourage you to reconsider adding the "Movie Restart" back into the 5D MkIII, just like any other ML ports.
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) (http://www.canon-europe.com/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_5D_Mark_III.aspx?type=download&page=1).
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 (http://nanomad.magiclantern.fm/nightly/). 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 (http://www.magiclantern.fm/forum/index.php?topic=2602.msg28976#msg28976). 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 (https://bitbucket.org/hudson/magic-lantern/raw/2063f5c9e7259707c07e98542a33dd8bdfe4da7e/contrib/make-bootable/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 (http://www.magiclantern.fm/forum/index.php?topic=3072.0) 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 :)
Does anyone know when 1.2.1 will be supported? If not, does anyone have 1.1.3? Can anyone post a link to 1.1.3 or post it online? Thanks.
mesebar,
that s the reason why only experienced users should try this.
If you do not have any clue about it, wait until a stable version will be out.
Mots of the "problems" of ML came out of users who had no idea what they are doing, and mistakenly marked as "software problems with ml".
Quote from: bumkicho on May 13, 2013, 12:25:49 PM
Does anyone know when 1.2.1 will be supported? If not, does anyone have 1.1.3? Can anyone post a link to 1.1.3 or post it online? Thanks.
I have 1.1.3 in my Dropbox. Try this link: https://www.dropbox.com/sh/ci4u4y2gnd43t4u/FK0WDvrlfR
If that link doesn't work, try this one: https://dl.dropboxusercontent.com/u/66165792/5D300113.FIR
Quote from: msowsun on May 13, 2013, 01:39:15 PM
I have 1.1.3 in my Dropbox. Try this link: https://www.dropbox.com/sh/ci4u4y2gnd43t4u/FK0WDvrlfR
Downloading it now. Thank you!
I get a few warnings when compiling last nights nightly. Is that common, i havent compiled ML before.
If i get a bin at around 433k, it should be OK right?
Warnings are usually ok
When I try to update the firmware bootflag I get a message saying there is no update available and to check card, I have to take battery out everytime. im just trying to bootflag my mark iii.
I got the bootflag to work but now when I put autobin file and ML file and run auto boot nothing happens. I put sd in and turn camera on and nothing happens.
I will pay someone to call me and walk me threw the process. Im pretty good with computers and have been studying this all day. I just think im missing something.
After the camera starts push the trash button to bring the ML menue
I got all RAW video working out fine, thank to A1ex. Is all good, just one question: is there some way to see the movie RAW file while connecting camera to PC, so far, the only way I could see and transfer it, is by putting CF card in reader and then file is visible. Also in Windows Explorer file M000000.RAW shows as Leica Raw Image. As I heard some horror stories of bend pins in CF card slot on 5DM3, I like to avoid taking out the CF card at all. I am using windows 8. Thank you for any advice
Nope you need a card reader
The RAW, how would it work with an external recorder? Using SSD should be much faster than the CF.
Hello,
My firmware is 1.2.1: can that be a problem?
Thanks
1.2.1 is not supported. You have to revert to 1.1.3. http://www.cinema5d.com/news/?p=17898
I also need to ask you guys about the "disable bootflag" problem. Today in installed the Dev enable bootflag .FIR and tried autobooting ML. This all worked fine. But now i got a new EyeFi Card and want to use it. The problem is that i NEED to disable the bootflag in NVRAM to be able to use this card.
Is there any option to disable the bootflag on a 5D Mark 3?
Current Setup
5D Mark 3
1.1.3 FW
16GB SD Card (for testing ML)
new 8GB EyeFi X2 pro (which prevents the 5D to boot)
Hey i was wondering if this new ML will work with the new update firmware 1.2.1 5d mark 3
No doubt they're working on it but don't pester them it'll just bug them and to be honest I for one don't mind waiting as when it does come out then I'll have to be hassled by Canon about using a third party battery :)
It´s possible transfer RAW data from CF card to SD card, to save space. SD card is slowly to get video RAW but maybe we can have an small back up disk. THanks.
ok so i fallowed step by step guides from several sites and i can confirm only the ML alpha3 works, everything else forces me to reboot by removing the battery, and i used macboot, the command with raw files inside the same folder etc.
any help appreciated
Does Alpha 3 work with canon 5D3 firmware 1.2.1 ?
thx
Quote from: debeeldenstormer on May 28, 2013, 01:50:13 PM
Does Alpha 3 work with canon 5D3 firmware 1.2.1 ?
thx
Not yet... down grade your firmware if you want to run ML
Hi which version of ML should I install to be able to capture raw footage with 5d mark 3 (firmware 1.1.3)... And is it possible to shoot 1920 x 1080 or 1920x820 ...
Thanks.....
Quote from: zemberek on May 29, 2013, 02:23:11 PM
Hi which version of ML should I install to be able to capture raw footage with 5d mark 3 (firmware 1.1.3)... And is it possible to shoot 1920 x 1080 or 1920x820 ...
Thanks.....
Start here:
RAW video & ML -- Beginners Guide and FAQ -- READ FIRST
http://www.magiclantern.fm/forum/index.php?topic=5520.0
Also many more guides here:
Tutorials and Creative use
http://www.magiclantern.fm/forum/index.php?board=15.0
You are getting a warning for not Searching the forums first.
Magic Lantern Forum Rules:
http://www.magiclantern.fm/forum/index.php?topic=934.msg1141#msg1141
I am running the latest v2.3 may25 5D3113 and am happily playing with the new settings.
In my AUDIO section I only have.
-speaker volume
-Beep
-Sound recorder.
I have a RODE mic that gets detected when plugged in and is working in the CANON end but why is my menue short on the items and saying the sound is disabled?
PLease help.
THANKS
M
Hey,
I've been experiencing fairly often but seemingly random lock ups or freezes after I have installed the newest nightly (a couple of days ago) and the only way to reset the camera is taking out the battery.
Is anybody else experiencing the same thing?
I also only have three audio features, Mandersson.
Hi,
I followed the directions here: http://www.cinema5d.com/news/?p=17898 and raw recording is working flawlessly to Lexar 128gb 1000x CF cards.
The only issue I am getting is every time the camera power cycles, I need to go into the ML menu and re-load the module, enable RAW and change the resolution. Is this a limitation of the Alpha?
Cheers to the ML team! :)
I don't know if this is right forum, but I just came across an error. Running ver. 1729277 (May31) on 5DM3. CF card SanDisk 32 Extreme Pro (90MB/sec). While running random tests, with LV in M Movie Mode got err70 twice, after about 4-5 min of running the test. After removing battery all was OK. Don't know if this interests anybody, just want to help somehow to make it better.
Canon 5Dm3. ML_rawrec_1905. Mac. All my RAW's processed through raw2DNG have faint vertical grey lines across the entire frame. Very Noticeable in blue sky. Does this with all my len's.
This Board is to discuss the Alpha 3 + DevKit; not a RAW thread.
For RAW go here:
http://www.magiclantern.fm/forum/index.php?board=49.0
Question:
Is it easier to develop ML for v1.1.3 and then port everything to 1.2.1?
Wouldn't it be better to first port it to 1.2.1 with the existing features
and then proceed with RAW?
I have searched the forum, but could not find an answer to that.
The v1.2.1 update fixes one problem I had as well, so I am rather reluctant
to revert back to 1.1.3. However I of course miss the features that we already
had in Alpha 3. I use that on a daily basis with the 5D MkII
I can wait very patiently for RAW (as exiting as it is).
But I'd die for the basic ML that Alpha 3 offered on 1.1.3.
No offense though, and please don't feel pushed.
I appreciate very much what you guys have given us for free.
Michael Quack
(edit: typos)
When release "Alpha 4" with the RAW module (with autoboot disabled) so we will not have the 'bootflag' problem ?
Any update when we will be able to remove the bootflag from the 5DIII, I really need to use my eye-fi card. :/
Today my new 5D MK3 has arrived. And I installed Magic Lantern.
I am very grateful for all your hard work.
I have a short question: I can not use the half shutter button to activate Magic Zoom, i have just:
Zoom in
Always on
Zoom.rec
Focus +Zrec
Is there a way to make half shutter button work?
Thanks
if i'm not mistaken, that was requesed, discussed and tried elsewhere in this thread but it didn't reliably work from the software side.
Ugh.. I just updated to 1.21 Revert it? or wait?
Quote from: iballs on June 01, 2013, 07:18:20 AM
The only issue I am getting is every time the camera power cycles, I need to go into the ML menu and re-load the module, enable RAW and change the resolution. Is this a limitation of the Alpha?
I was getting tired of re-loading the modules too so went into the Canon menu:
/Settings /Auto power off/ Disable
I just keep the camera on after loading the modules and it works brilliantly.
Cheers and thanks to the people who have made this happen.
-N
Guys
Could I ask you to post some raw DNG's straight out of 5D3 (via dropbex or something like this) in different resolutions from similar footage (highly detailed scene) - I would like to compare the resolutions by myself and I don't know anybody with 5D3 from my neighborhood.
If you can please post:
-1 frame 1920x800
-1 frame 1808x756 (or similar of you don't if you don't have such a res)
-1 frame 1664x696 or so.
With the 6D I can use max 1808x756 for about 15sec, 1600xsomething is much longer. I would like to see for myself how much quality i am loosing when compared to true 1920x .....
I was making some comparisons 1600x... vs 1800x... and difference were smaller than i expected, especially when exported with some decent h.264 for final viewing.
Thanks in advance
Hello,
I can't get ML uploaded into my brand new 5D mkIII ? I have tryed several times, I have followed all the steps in the installation guide and in the message #1 of this thread strictly. I have firmware 1.1.3. for sure. My camera is new, I bought it two weeks ago.
Some observations:
- I have tryed two CF cards (Sandisk Extreme 60MB/s, 32 GB and 16 GB) and one SD card (Transcend 32GB SDHC) and ML only on one card at a time. Also I have tryed with only one card in the camera.
- In the first upload attempts, nothing happened exept card check counter went fast 0-100%, then camera was quiet (no red led blinking). Nothing installed.
- Then I updated firmware 1.1.3. to 1.1.3. for sure (I updated it from the http://pel.hu/down/). After this, the firmware upload to ML ends red led blinking for ever. So was the new 1.1.3. firmware even worse than my original 1.1.3. ?
Could someone tell, where to find 5DmkIII firmware 1.1.3., which would work with ML for sure?
Any other advice?
Just at the moment I would like to have ML to be able to use normal still-shutter button for video. Is this feature working on ML for 5DmkIII ?
Best Regards,
Ilari
Did you make the card bootable? And then putting on the ml files to the card? Did you do the nightly builds?
Quote from: Danne on July 02, 2013, 01:12:40 PM
Did you make the card bootable? And then putting on the ml files to the card? Did you do the nightly builds?
- How is the card made bootable? And why should it? Installation guide doesn't tell anything about that? I understood that Alpha 3 even can't be made boot from the card but must be uploaded everytime power is switched on?
- I formatted the card just as the installation guide tells. And then I copied the ML files I downloaded from the site (of course I first unzipped them)
- I don't do the nightly buildups. Just tryed the announced Alpha 3 for 5D mkIII.
Best Regards,
Ilari
]
Hi! I have a couple of questions please..
1. Where can I download the latest build for 5D Mark III with the RAW functionality included from THIS WEBSITE?... I've managed to test it (works great with LEXAR 1000x) but by getting the links from tutorials around... and everything in this website seems to lead other way or maybe I'm not clever enough! :p...
2. Is a there a version (with RAW func) coming for the latest canon firmware soon? or should I downgrade to 1.1.3 if I intend to use ML this year at least?...
Thanks, I admire what you guys have done...
Sebastian V.
Quote from: ilari on July 02, 2013, 11:14:45 PM
I understood that Alpha 3 even can't be made boot from the card but must be uploaded everytime power is switched on?
On my 5Dmk3 ML autoboots on power-on.
I am running the latest nightly (think its from the 28.6
Hi, guys...
Could somebody help me with the installation of alpha3 on markiii, please... I`ve already downloaded the alpha 3 zip file... but inside there`s no autexec.bin file... do I have to get it from another place...? or do I have to install something else first?
EuAcelasi,
Nothing else to install... Best bet is to install ML on the SD card ( both the ml-5D3-113.fir file and ML folder ) and record images/video on the Compact Flash card. Alpha 3 needs to be installed via the firmware every time you turn the camera on as it can't be installed permanently until more testing is done.
There is no raw recording on alpha 3, is it right? Have somebody tested the Transcend 128gb x1000 cards? are they stable... or have same problems as Komputerbay CFs?
Thanks
I installed the ML for mark iii with the raw recording.... but there is no way to change the recording bitrate like on mrk ii ML, is that right?
This is my first experience with the ML... and it is a great one... Thanks
I have failed to update autoexec.bin today with error.
[spoiler]make -C /home/vstrglv/magic-lantern/platform/5D3.113
................................................
[ CC ] memcheck.o
../../src/memcheck.c: In function 'memcheck_add':
../../src/memcheck.c:99:46: warning: assignment discards 'const' qualifier from pointer target type [enabled by default]
../../src/memcheck.c: In function 'memcheck_malloc':
../../src/memcheck.c:150:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
../../src/memcheck.c:160:5: warning: return makes pointer from integer without a cast [enabled by default]
../../src/memcheck.c: At top level:
../../src/memcheck.c:163:6: error: conflicting types for 'memcheck_free'
In file included from ../../src/dryos.h:644:0,
from ../../src/tasks.h:27,
from ../../src/memcheck.c:3:
../../src/memcheck.h:7:14: note: previous declaration of 'memcheck_free' was here
../../src/memcheck.c: In function 'memcheck_free':
../../src/memcheck.c:194:22: warning: pointer targets in initialization differ in signedness [-Wpointer-sign]
../../src/memcheck.c:208:9: warning: passing argument 1 of 'memcheck_free' makes pointer from integer without a cast [enabled by default]
../../src/memcheck.c:163:6: note: expected 'void *' but argument is of type 'unsigned int'
../../src/memcheck.c:212:9: warning: passing argument 1 of 'memcheck_free' makes pointer from integer without a cast [enabled by default]
../../src/memcheck.c:163:6: note: expected 'void *' but argument is of type 'unsigned int'
../../src/memcheck.c: In function 'memcheck_main':
../../src/memcheck.c:232:25: warning: initialization makes integer from pointer without a cast [enabled by default]
../../Makefile.filerules:23: recipe for target `memcheck.o' failed
make: *** [memcheck.o] Error 1
make: Leaving directory `/home/vstrglv/magic-lantern/platform/5D3.113'
[/spoiler]
Last success for update I had on 18.06.2013
Win7, Cygwin, gcc-arm-none-eabi-4_7-2012q4
No need to use memcheck, it's only for developers.
I use commands:
cd magic-lantern
make clean
hg pull
hg update
make -C /home/vstrglv/magic-lantern/platform/5D3.113
But how off memcheck?
I was wondering if anyone has compiled a version of ML with the new features that those of us who are not adept at coding can use . I consider myself pretty good with a camera but when it comes to programing I'll openly admit I have neither the skill or confidence to attempt putting the pieces together to make a working version .
Reading about the modules and reading the updates in the Change Log section is pretty exciting though at the same time not having the means to implement them to my camera leaves myself ( and I'd bet quite a few others in the same boat) feeling a little left out . I'm hoping an official more simplified release in the form of another alpha or even a beta version will come from the Magic Lantern team sometime soon.
I guess to put it in a nutshell I'm humbly requesting ya toss a bone to us non-codeing nitwits so we can feel like part of the gang .
And thanks for any consideration this post may get.
It's been available as an almost daily update in the Raw Video sub forum in a sticky topic.
It doesn't get any easier and has been going on for months now.... thanks to lourenco on the 5D III
It's also been posted in topics over and over again.
http://www.magiclantern.fm/forum/index.php?topic=6362.0
Thanks for the link and quick reply.
I hadn't checked the threads related to video as I'm more interested in photography features then the cinematic ones.
The build listed in that thread has all the new features...
ETTR, Dual ISO, RAW Video, not sure if the Bolt Recorder is working right now though.... it's what you're looking for.
I had the nightly builds on my 5D Mk II but only have the basic ML 2.3 Alpha 3 on my 5D Mk III.
Is DotTune AFMA possible on the 5D Mk III?
Yes Dot Tune in the Raw Video Build.
Am I right in thinking that development has now switched to the Raw Video Build?
Hi there, need help to find out how to shoot crop RAW video (2X, 3X) on my 5DM3.
Does this camera support in camera review after shooting in silent picture mode? Does silent picture mode support dual_iso?
Anyone know if ML for 5D3 will work with Canon 1.2.1 firmware? Tried to find the answer in the threads without luck.
Quote from: DesterWallaboo on August 12, 2013, 09:22:02 PM
Anyone know if ML for 5D3 will work with Canon 1.2.1 firmware? Tried to find the answer in the threads without luck.
Hint: click on the search button of the forum (third from the top) type "Canon 1.2.1 firmware".
Hello guys!
I am sorry, but how record RAW + audio?
same question: is it possible to record audio together with raw on 5d markiii?
No.
Will it record audio in the final version...? Does ML 2.3 record audio on 5d markii?
Hello (from France)!
After installation, j don't obtain the green screen "success"...it's normal?
My files are in .mov container...it's normal? (on a Komputerbay CF 1000)
Thank you very much
:)
It won't be long before Alpha 3 is a year old. Any updates on the development for the Canon 5D MK III? I am hoping that something will be available for firmware 1.2.1 since I also use the Ninja 2.
Thanks
Just the same case: waiting for the 1.2.1 ML version. Also working with Ninja 2.
In the general development forum people have answered what needs
to be done for 1.2.1 before it can be switched.
They have different priorities but would gladly accept help on those
cumbersome jobs.
Unfortunately my skills are not good enough to be any help.
Quote from: VisualPursuit on August 24, 2013, 08:01:48 PM
Unfortunately my skills are not good enough to be any help.
That is not a brain surgery... :)
You need the ROM dump from the 1.1.3 version and the same ROM dump from the new fw 1.2.1.
If you have a 5D3 then you can get them easily with the devkit.
Then donwload http://pel.hu/down/ARMu.exe, start two instance of it, load the two dumps to them (use the project file from here: http://pel.hu/down/5D3_113.prj, edit the workdir in it, copy to 5D3_121.prj).
Then download the https://bitbucket.org/hudson/magic-lantern/raw/6bb97bcbc0f4ec7ab8b68ff7342541dc5a84665f/platform/5D3.113/stubs.S file from the bitbucket repository.
It contains memory addresses and labels.
That is for the 1.1.3 fw so find the addresses in the first ROM dump then go to the other ROM dump and try to find the same routine in that one.
You can search for code pieces or strings or use your intuition... :)
When you find the address put it into a new stub.S file (you can copy the old one and replace the addresses in it).
Then pick the next address from the old stub and search again.
That's it.
Even if you don't understand the code you can find the most of the stubs and the devs will finish the rest.
Coutts posted not only a new stubs on here somewhere but also mentioned the boot addresses changed.
Quote from: 1% on September 05, 2013, 03:45:21 AM
Coutts posted not only a new stubs on here somewhere but also mentioned the boot addresses changed.
Then sorry, I didn't want to reinvent the wheel...
Anyway I can use a 1.2.1 dump if someone has an extra... :)
Hello!My name is Charlie. I have been a long time user of Magic Lantern from 600D/60D/5D Mark III and it's been fantastic!
I made a video tutorial for installing Magic Lantern, specifically for the 5D Mark III. The video has been really well received, and I return emails every single day from people personally thanking me for it, and also lots of questions that possibly weren't covered in the video. It would be great to help out some more people with this video. So take a look, and by all means recommend it to other if/when they get stuck.
(Link if the player doesn't load: http://www.youtube.com/watch?v=d7pn5Q6wNMY)
Hope this helps! ;D
Quote from: MediaLockeFilmsUK on September 14, 2013, 03:27:50 AM
Hello!
My name is Charlie. I have been a long time user of Magic Lantern from 600D/60D/5D Mark III and it's been fantastic!
I made a video tutorial for installing Magic Lantern, specifically for the 5D Mark III. The video has been really well received, and I return emails every single day from people personally thanking me for it, and also lots of questions that possibly weren't covered in the video. It would be great to help out some more people with this video. So take a look, and by all means recommend it to other if/when they get stuck.
(Link if the player doesn't load: http://www.youtube.com/watch?v=d7pn5Q6wNMY)
Hope this helps! ;D
Maybe you want to post it under Video Tutorials. I dont have bandwidth to watch videos so is this for the installation all the way to RAW or only for Alpha 3
Hi all,
Just wondering if I should download the alpha 3 version for the 5d mkiii, or if I should use the latest nightly build specifically for the 5D3.113 platform (magiclantern-v2.3.NEXT.2013Sep15.5D3113). It's a little confusing, as there's a note in the forum that the nightly build is not for the 5dmkiii.
I'd like to explore ML purely for still photography (it looks like the water's safe), so am looking for the most stable candidate to support that.
By the way, thanks to Charlie and Dugdale for posting the installation how-to clips, and to the ML developers! BTW, hope I'm posting in the right area of the forum.
Cheers,
Robert
You cannot use nightly build untill you set the bootflag in the camera. Notice that this process can not be undone yet.
Read here and watch the video:
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST
www.magiclantern.fm/forum/index.php?topic=5520.0
Thanks for the tip and links, Renato. Just to clarify, this is the installation process to take even if I'm only interested in testing ML's core functionality for still photography?
Quote from: haiku1413 on September 15, 2013, 07:33:15 PM
Thanks for the tip and links, Renato. Just to clarify, this is the installation process to take even if I'm only interested in testing ML's core functionality for still photography?
The advanced modules (AETTR and DUAL ISO) are both for photo or video. I all depends on what you want to do. No clear cut decision, you make your own decisions.
Thanks again for the clarification - I'll take that route and join in the feedback, blogging, etc.
Again I'm totally new here and only installed the 2.3 to my 550D - it is working great including the HDR-video!
As everyone else I'm too excited to try ML on my more expensive 5Dm3. I have watched Charlie's & Dave's tutorials:
http://www.magiclantern.fm/forum/index.php?topic=6099.0
Trying to browse the forum too for a couple of days now. As I understand C&D tutorials they are installing a nightly build version with the bootflag.fir - which cannot be undone. Some threads also suggest that changing the bootflag (still don't quite understand it) would slow down the start up time of 5Dm3 remarkably.
I don't want any permanent changes to my 5Dm3 at this alpha stage, but am happy to accept the fir-update process at every start up. So I'm asking some questions:
- Does this version "Magic Lantern for 5D Mark III - Alpha 3 + DevKit" change the "bootflag" or does the camera revert back to the original Canon firmware at every startup? Is it different to what Charlie and Dave are doing?
- Can you add the RAW functionality without the "bootflag" or not?
I installed ML on my 5d iii everything seemed to work fine after is disabled that on feature?, but two things i never got the "M" in my ML menu . 2. my card failed the next day any ideas on what happened and what i should do. P.S ML did work i recored some clips got the raw files wondering if that was an update that i missed not having a modules section in my menu
Quote from: camera7 on September 17, 2013, 05:15:32 PM
- Can you add the RAW functionality without the "bootflag" or not?
No RAW without bootflag set.
Quote from: teakwood18 on September 18, 2013, 07:52:17 AM
I never got the "M" in my ML menu
Recent changes in ML changed the M for an icon with four little squares, this is the modules tab. Some manuals have to be updated. :'(
I have used ML on a 60D but have changed it for a 5D3 with f/w 1.2.1.
Will ML work with it and does it need to be reloaded everytime of turning on the camera?
Sorry for the questions but getting confused about what is happening having updated the f/w from 113 however I do not have a video recording device for video but have noticed that with 121 it does not like non canon batteries and other than that cannot see what else has been added to 121. Does anyone know what are the changes and yes have looked on the UK and USA canon sites for info but they are very weak on giving such information?
Quote from: vbcoen on September 18, 2013, 02:56:50 PM
Will ML work with it and does it need to be reloaded everytime of turning on the camera?
ML will not work with 1.21 on 5D3.
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST
http://www.magiclantern.fm/forum/index.php?topic=5520.0
Is that likely to change any time soon, e.g., before the end of year etc?
If not, is it worth reverting back to f/w 113?
I do more stills than video .
Quote from: vbcoen on September 18, 2013, 03:13:35 PM
Is that likely to change any time soon, e.g., before the end of year etc?
If not, is it worth reverting back to f/w 113?
I do more stills than video .
1. dont know.
2. 113 is good
3. ML good for still and video
Hmm, looks like I have to go back to 113.
Last questions:
1. Is ML now safe(ish) to use the boot file to make ML permanent as against reloaded on every turn on as this will allow me to use a ACK-6 mains power instead of battery?
The older version would NOT load as the camera would report a battery fault with the ACK-6 and then go back to the boot firmware screen.
If all that is ok, then where is the current version or should I use one of the nightly builds?
Thanks for your help.
Quote from: vbcoen on September 18, 2013, 05:12:43 PM
Hmm, looks like I have to go back to 113.
If all that is ok, then where is the current version or should I use one of the nightly builds?
Watch the videos and read the guides
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST
http://www.magiclantern.fm/forum/index.php?topic=5520.0
Quote from: RenatoPhoto on September 18, 2013, 03:59:48 PM
2. 113 is good
I beg to differ.
Photography remains my main application, and the AFMA error in 113
gives me random AF problems that are fixed in 121.
Worse: Some people have reported that they suffer from the AFMA error
after downgrading to 113 back from 121 but haven't had that with the
initial 113.
That is of course completely irrelevant for people who don't use their
5D mkIII for anything except filming and who use manual focus pulling.
But for those of us who take still pictures as well, 113 is likely a major problem.
Just sayin.
That does not answer my questions and I am familiar with installing the s/w already asI have used it on a 60D and 5d3 (113) last year.
Quote from: vbcoen on September 19, 2013, 02:27:24 PM
That does not answer my questions and I am familiar with installing the s/w already asI have used it on a 60D and 5d3 (113) last year.
Yes it answers your question in a long and windy way.
If you read the guide you will find:
If you want to try the latest features (including RAW) for these cameras then:
Nightly Builds - try the very latest stuff:
HERE: http://www.magiclantern.fm/forum/index.php?topic=3072.0
Quote from: VisualPursuit on September 18, 2013, 10:52:31 PM
and the AFMA error in 113
gives me random AF problems that are fixed in 121.
Can you provide more detail about this AFMA error?
Hi
Question. Cant find modules,
Instal seems to have worked (have the same screen shown on this page) but i dont understand how to get modules and start shooting Raw video.
Been looking for clues for over 24 hours now.
P.S my apologies if this is wrong place to ask questions, never been on a forum before.
Quote from: procter on September 25, 2013, 02:36:04 PM
Instal seems to have worked (have the same screen shown on this page) but i dont understand how to get modules and start shooting Raw video.
Since you did not provide any information, I will get my Cristal ball out and guess that you have not set the bootflag in the camera.
There is a little section in our forum dedicated to RAW video here:
http://www.magiclantern.fm/forum/index.php?board=49.0
In it you will find the following post:
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST
http://www.magiclantern.fm/forum/index.php?topic=5520.0
When you go there watch the videos and read, read, read.
Has anyone experienced with the Intervelometer ,post deflicker, and manual ramping? Can someone clarify how to succeed at doing day to night or night to day timelapses using the exposure ramp option, without it boosting your ISO (preferebly adjusting the shuter and aperature only). And im not sure if i just happen to shoot on oddly windy days, but has anyone experienced a couple image jumps in your timelapses in post? Seems like there is a glitch in the camera, but i just started seeing it.
This could never be fixed, that is why:
Flicker Free ETTR Timelapse: - -Beginners Guide & Basic Post Processing --
http://www.magiclantern.fm/forum/index.php?topic=5705.0
but you have to upgrade to RAW
New user here. I've spent most of the day pouring over the details of this version of ML for the 5D3.
I installed the 2013-09-27 build (first time installing ML) and things went smoothly.
Here is the one thing I discovered, and I'm not sure if it's strictly this build or something else entirely, but when I shoot video RAW, everything is coming out about 2 stops underexposed. Everything looks perfect when recording. I'm watching my histogram closely, but when I look at the DNG's they are consistently 2-2.5 stops underexposed. The ProRes file created by raw2dng also looks underexposed at the same level. I am able to correct this in Camera Raw, but the noise is pretty obvious in the shadows.
Here's a link to a screen capture of the ProRes:
https://dl.dropboxusercontent.com/u/7439425/ML/ML23-5D3-20130927-NoTx.jpg (https://dl.dropboxusercontent.com/u/7439425/ML/ML23-5D3-20130927-NoTx.jpg)
Canon 5D3
ML 2013-09-27
raw2dng 0.13
Quote from: Audionut on September 20, 2013, 06:09:54 AM
Can you provide more detail about this AFMA error?
Sure. Occasionally the camera sets the AF Micro Adjustment to -8 which results
in images that are out of focus. If you notice, you can reset it - until for no known
reason the camera sets it to -8 again.
It is a problem that might or might not occur the next day, and it is hard to see
on the back LCD display.
So, as a wedding photographer I might shoot a whole wedding with unsharp
images and only notice after it is too late. Not my option.
There have been reports of people suffering from that error ony after downgrading
from 1.2.1 to 1.1.3 again, and not having this problem before up/downgrade.
I had the problem from start, and 1.2.1 fixed it. So I am not going back to 1.1.3,
I will have to wait for ML to be compatible to 1.2.1, whenever that will be.
In the meantime, my 5D Mk3 sees little video work, most is done on the 5D Mk2.
Quote from: DesterWallaboo on September 27, 2013, 11:55:47 PM
New user here. I've spent most of the day pouring over the details of this version of ML for the 5D3.
I installed the 2013-09-27 build (first time installing ML) and things went smoothly.
Here is the one thing I discovered, and I'm not sure if it's strictly this build or something else entirely, but when I shoot video RAW, everything is coming out about 2 stops underexposed. Everything looks perfect when recording. I'm watching my histogram closely, but when I look at the DNG's they are consistently 2-2.5 stops underexposed. The ProRes file created by raw2dng also looks underexposed at the same level. I am able to correct this in Camera Raw, but the noise is pretty obvious in the shadows.
Here's a link to a screen capture of the ProRes:
https://dl.dropboxusercontent.com/u/7439425/ML/ML23-5D3-20130927-NoTx.jpg (https://dl.dropboxusercontent.com/u/7439425/ML/ML23-5D3-20130927-NoTx.jpg)
Canon 5D3
ML 2013-09-27
raw2dng 0.13
Same here ! LCD is fine, but the png and prores from raw2dng are much underexposed.
Is it just the need of a color profile ?
Anyone knows ?
ricordu
Quote from: VisualPursuit on September 28, 2013, 01:04:46 AM
Sure. Occasionally the camera sets the AF Micro Adjustment to -8 which results
in images that are out of focus. If you notice, you can reset it - until for no known
reason the camera sets it to -8 again.
I have seen this on my 5D3 with fw113. Dont know what does it! I have not upgrated to 1.21. If 1.21 fixed this issue I would consider an important improvement.
I wonder if ML could be used to always maintain the AF microadjustment.
Quote from: RenatoPhoto on October 11, 2013, 12:01:34 AM
I have seen this on my 5D3 with fw113. Dont know what does it! I have not upgrated to 1.21.
If 1.21 fixed this issue I would consider an important improvement.
Yes, 1.2.1 fixed the problem permanently, which is exactly the reason
I am not going back and thus can't use ML on my 5D MkIII.
Personal preference, of course.
Ive noticed the underexposed shots as well, but i was also told that in this case to shoot 2 stops over exposed to get the right exposure in processing. Is ML compatible with FW 121 now? i thought it was settled at FW113
Hello, I've read a few posts, but I have not figured out if it is compatible with ML 5dIII 1.2.1. I am not able to install it.
Quote from: rselvat on October 16, 2013, 11:49:47 AM
Hello, I've read a few posts, but I have not figured out if it is compatible with ML 5dIII 1.2.1. I am not able to install it.
No it's not compatible.
Hi Alex
Have you any idea how to reset the 5D3 bootflag. I am one of the unlucky that was not aware of setting the booflag would affect using an EyeFi card. Also the start up lag would be nice to be able to get rid of.
Best regards
Steen
http://www.magiclantern.fm/forum/index.php?topic=7125.0
In which way possible to install Alpha 3 on Mark III with firmware 1.2.1? Need to change firmware to 1.1.3?
I signed up just to reply to this post. I'm really confused as there's a lot of conflicting information here.
I'm one of the people who has been using ML on my 5D III and have been unsuccessful getting my Eye-Fi card to work. I've read numerous threads on here and they are all different. As of October 17th, there's a thread such as this http://www.magiclantern.fm/forum/index.php?topic=7125.0 where it says there's no way of removing the boot flag yet (for a standard user). But yet, in this thread, http://www.magiclantern.fm/forum/index.php?topic=2687.msg15653#msg15653 someone said they got it to work using Alpha 3.
I've done everything in that thread using Alpha 3 and I still can't get it to work. Is there a fix for this or not? I've read threads in June, July, September and October - has there been any progress with getting the Eye-Fi card to work with or without ML?
Last stable version for the 5D3?
thanks in advance
Quote from: timetraveller on October 27, 2013, 09:31:41 PM
Last stable version for the 5D3?
There has never been a stable version, just the Alpha 3 - and this requires
you to downgrade your firmware to 1.1.3, which might give you misadjusted AF.
Nightlies are considered to work generally well, but they work only on 1.1.3.
In the general development discussion is a statement to find what needs to be
done before ML can be ported to 1.2.1. - the developers welcome anybody to
come forward and work on these tasks.
Maybe this call for volunteers with a description of the task would make a good sticky?
Quote from: VisualPursuit on October 28, 2013, 12:57:09 PM
There has never been a stable version, just the Alpha 3 - and this requires
you to downgrade your firmware to 1.1.3, which might give you misadjusted AF.
Nightlies are considered to work generally well, but they work only on 1.1.3.
In the general development discussion is a statement to find what needs to be
done before ML can be ported to 1.2.1. - the developers welcome anybody to
come forward and work on these tasks.
Maybe this call for volunteers with a description of the task would make a good sticky?
Thabks for the answer.
I can't find the link for the Alpha 3 version...
Can you help me?
thanks
NOTE:I'll answer to myself; the link is the first page of this thread.
Any idea when ML might become a stable release on 5DIII?
I am reallly interested in all of this great work, but I can't afford to risk my camera.
Quote from: Steve_Brule on October 29, 2013, 06:15:07 PM
Any idea when ML might become a stable release on 5DIII?
I am reallly interested in all of this great work, but I can't afford to risk my camera.
I've been using the nightly builds for quite some time, and it has been pretty stable for me. If you're not quite adventuresome enough to use the nightlies, just throw Alpha 3 on your camera -- it works very well. (I went with the nightly builds for RAW video support and the neat dual_iso module) I've been using it for both cinematography *and* photography, with much success. ;)
Quote from: rufustfirefly on October 29, 2013, 09:38:07 PM
I've been using the nightly builds for quite some time, and it has been pretty stable for me. If you're not quite adventuresome enough to use the nightlies, just throw Alpha 3 on your camera -- it works very well. (I went with the nightly builds for RAW video support and the neat dual_iso module) I've been using it for both cinematography *and* photography, with much success. ;)
I've read some people having slow start problems, unable to reset the bootflag, and a couple of other issues. Also I have firmware 121. Not sure I want to get rid of that. I guess I am not quite as adventurous as some people here. I sure could use some focus aids though.
As of today, Canon announced firmware 1.2.3, again with reference to
further bugfixing on the AFMA misadjustment problem.
http://usa.canon.com/cusa/professional/products/professional_cameras/digital_slr_cameras/eos_5d_mark_iii#DriversAndSoftware
Let's hope they finally fixed it and that this will help in moving from 1.1.3
as a basis for ML to now 1.2.3.
Yes, I know about the work, and unfortunately I cannot be of much help.
Does anybody know when a new ML version will come out to support FW 1.2.3 Versions? I have no problem in using 1.1.3 but for monitoring using hdmi out the image is a fourth of the screen size. So it si no help in buying a 7 inch external monitor for focusing help if the output image on it is only a fraction of its size ( not bigger than the one on the camera back)...
Quote from: phil7 on November 02, 2013, 10:01:28 AM
Does anybody know when a new ML version will come out to support FW 1.2.3 Versions? I have no problem in using 1.1.3 but for monitoring using hdmi out the image is a fourth of the screen size. So it si no help in buying a 7 inch external monitor for focusing help if the output image on it is only a fraction of its size ( not bigger than the one on the camera back)...
My IKAN VH8 works quite nicely with ML on 1.1.3. It has autoscaling, so if you turn off all screen overlays then the video becomes full screen. You should try it and see if you have any luck.
I also had an issue for a while with the preview rectangle being in the wrong position on the monitor, but I read elsewhere that turning the grayscale preview option on would strangely fix this, and sure enough it did.
I can't wait until ML RAW is more stable, but at least it works with a little finessing.
Hi,
I'm new to ML.
I have a 5D3 upgraded to 1.2.3.
Can/should I install ML?
Thanks,
Sharon
Quote from: sharont on November 04, 2013, 07:18:55 PM
Hi,
I'm new to ML.
I have a 5D3 upgraded to 1.2.3.
Can/should I install ML?
Thanks,
Sharon
Sharon, you will have to downgrade to 1.1.3 or wait until someone does the necessary work.
Quote from: VisualPursuit on November 04, 2013, 11:32:59 PM
Sharon, you will have to downgrade to 1.1.3 or wait until someone does the necessary work.
Thanks.
I'll be waiting.
I hope this is the right place for this question.
This may be a silly question but I've searched through the forums & I can't find the answer anywhere (my apologies if I've missed something obvious).
With the Alpha 3 version (or any other version), is it possible to record H.264 video (NOT RAW!) longer than 30 minutes on the 5D3, provided the card is formatted exFAT?
I am trying to see if it is possible to record the native H.264 5D3 video for longer than the 30-minute limit, and I would like to avoid altering the bootflag on the camera if at all possible (that's why I'm attracted to the Alpha 3 version, as if I'm not mistaken it doesn't alter the bootflag).
With this goal in mind, what is the best ML version for me to be using?
Thanks very much for the help.
Is anyone aware whether or not the EULA for the new firmware version (1.2.3) has removed the odious reverse-engineering inhibiting clause, which kept ML from being ported to v1.2.1?
Quote from: rufustfirefly on November 08, 2013, 09:07:03 PM
Is anyone aware whether or not the EULA for the new firmware version (1.2.3) has removed the odious reverse-engineering inhibiting clause, which kept ML from being ported to v1.2.1?
From the End User License Agreement for updating to 1.2.3 on the Canon U.S.A. site ( http://usa.canon.com/cusa/professional/products/professional_cameras/digital_slr_cameras/eos_5d_mark_iii#DriversAndSoftware -- click through and you'll see it just before you download):
QuoteYou shall not alter, modify, disassemble, decompile or otherwise reverse engineer the Software and you also shall not have any third party to do so.
Interestingly, the EULA begins with this sentence:
QuoteThe following End User License Agreement applies only to camera firmware updaters.
I'm no lawyer, but that seems to suggest that it doesn't apply to people who buy their cameras with 1.2.3 or other firmware already on it (i.e., who don't update), and so (perhaps?) it needn't prevent ML from being ported to newer versions of the firmware.
Note that you can download the firmware from Canon's European or UK sites without any reverse engineering clause:
http://www.canon.co.uk/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_5D_Mark_III.aspx?DLtcmuri=tcm:14-1098601&page=1&type=download
EDIT: if anyone has a rom dump for 1.2.3 I'll be willing to have a go at updating the stubs... (I don't want to upgrade to 1.2.3 then downgrade back to 1.1.3 as I've heard a couple of people say that can aggravate the AFMA bug)
Quote from: chris_overseas on November 09, 2013, 03:59:31 PM
if anyone has a rom dump for 1.2.3 for me I'll be willing to have a go at updating the stubs... (I don't want to upgrade to 1.2.3 then downgrade back to 1.1.3 as I've heard a couple of people say that can aggravate the AFMA bug)
I've heard that too. My 5D3 has 1.2.1 (and no ML yet) and I'd be willing to update to 1.2.3 and provide you with a rom dump if I had a clue how to do that. If no one else offers, and you'd like to PM me with instructions or links to instructions for doing a rom dump, I'll give it a shot.
Quote from: mva on November 09, 2013, 08:04:09 PM
I've heard that too. My 5D3 has 1.2.1 (and no ML yet) and I'd be willing to update to 1.2.3 and provide you with a rom dump if I had a clue how to do that. If no one else offers, and you'd like to PM me with instructions or links to instructions for doing a rom dump, I'll give it a shot.
My understanding (and be aware that I'm far from expert...) is that it would just be a matter of flashing the updater firmware in the first post of this thread to get the firmware dumped out to the memory card. I'm not sure where the source code is for that firmware file though so I can't check to be comfortable that it will run successfully/safely on 1.2.3. On top of that, the firmware also turns on the bootflag which currently can't be undone. I'm sure you don't want to enable the bootflag on your camera just yet (it slows down startup/wakeup of the camera and prevents Eye-Fi cards from working) so I'd recommend against you running it. Thanks for the offer though!
Quote from: chris_overseas on November 10, 2013, 04:20:45 PM
I'm sure you don't want to enable the bootflag on your camera just yet (it slows down startup/wakeup of the camera and prevents Eye-Fi cards from working) so I'd recommend against you running it. Thanks for the offer though!
Although I'm seriously considering installing raw on my 5D3, which would involve both downgrading to 1.1.3 and setting the bootflag with no way to safely reset it, you're right that I'm not yet ready to enable the bootflag (or downgrade to 1.1.3). So I hope others come forward to help. Good luck!
Hello friends
I just bought my 5d3 with 1.2.3 on it. Is downgrading possible ?
Thanks
Bonjour a toutes et a tous! Je recherche désespérement le moyen de passer de la version 1.2.1 a la version 1.1.3 sur mon 5d mark III.
Avez-vous un lien de téléchargement du firmware 1.1.3 sur mac et y a t'il un risque en fesant cette manipulation??
All ML 5D3 developers,
Not sure if this is the best thread to post this on, if it's not someone please move it where it belongs. For anyone working on 5D3 ML for firmware 1.2.3, I'm willing to test and provide feedback needed to get it on the way to being a stable release. For me, and I believe others too, my main need from the updated firmware is the HDMI mirroring options. There are many situations on set where there's a need for both the on camera monitor and an external monitor to be running (i.e. 1st AC's pulling focus while Cam Op composes shots) and "Image on both LCD and external monitor at the same time" is listed on the features NOT POSSIBLE list. I feel this feature is very necessary on set and if it's not possible form the ML developer teams I'm willing to help test on the firmware that it's already included on.
Thanks in advance.
It looks like the nasty language is still present in the "Grant of License" section of the license for downloading the v1.2.3 firmware ( "You shall not alter, modify, disassemble, decompile or otherwise reverse engineer the Software and you also shall not have any third party to do so. You shall not modify, remove or delete a copyright notice of Canon contained in the Software." )
This was cribbed directly from Canon's site ( http://www.usa.canon.com/cusa/consumer/products/cameras/slr_cameras/eos_5d_mark_iii#DriversAndSoftware )
Looks like we're not about to see any official Magic Lantern versions based on the v1.2.3 firmware.
QuoteThe following End User License Agreement applies only to camera firmware updaters.
IMPORTANT!
IMPORTANT- READ THIS AGREEMENT CAREFULLY BEFORE CLICKING "I Agree" AT THE BOTTOM OF THIS PAGE!
This License Agreement (the "Agreement") is a legal agreement between you and Canon Inc. ("Canon") under which Canon is providing the software program for version-up of the firmware of Canon's products (the "Software"). BY CLICKING "I Agree" AT THE BOTTOM OF THIS PAGE, YOU ARE DEEMED TO AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT DOWNLOAD THE SOFTWARE. IN SUCH EVENT, YOU WILL NOT BE ABLE TO USE THE SOFTWARE.
1. GRANT OF LICENSE:
Canon grants you a personal and non-exclusive license to install the Software directly or through other medium such as hard disk or CompactFlash and use on Canon's product which you own.
You shall not assign, sublicense, sell, rent, lease, loan, convey or otherwise transfer to any third party, or copy, duplicate, translate or convert to another programming language the Software, except as expressly provided herein. You shall not alter, modify, disassemble, decompile or otherwise reverse engineer the Software and you also shall not have any third party to do so. You shall not modify, remove or delete a copyright notice of Canon contained in the Software.
Except as expressly provided herein, no license or right, express or implied, is hereby conveyed or granted by Canon to you for any intellectual property of Canon.
2. OWNERSHIP AND COPYRIGHT:
The Software is copyrighted and owned by Canon. You agree and acknowledge that Canon transfers neither ownership interest nor intellectual property in the Software to you under this Agreement or otherwise, and that Canon retains all right, title and interest to the Software.
3. EXPORT RESTRICTIONS:
You agree to comply with all applicable export control laws and regulations of the country involved, and not to export or re-export, directly or indirectly, the Software in violation of any such laws and regulations.
4. SUPPORT AND UPDATE:
Canon, Canon's subsidiaries and affiliates, their distributors and dealers are not responsible for maintaining or helping you in your use of the Software. No updates, bug-fixes or support will be made available to you for the Software.
5. DISCLAIMER:
THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU (AND NOT CANON, CANON'S SUBSIDIARIES AND AFFILIATES, THEIR DISTRIBUTORS AND DEALERS) ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU IN SUCH STATES WHICH DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES.
Canon, Canon's subsidiaries and affiliates, their distributors and dealers do not warrant that the functions contained in the Software will meet your requirements or that the operation of the Software will be uninterrupted or error free.
IN NO EVENT SHALL CANON, CANON'S SUBSIDIARIES AND AFFILIATES, THEIR DISTRIBUTORS AND DEALERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, LOSS OF BUSINESS PROFITS, LOSS OF BUSINESS INFORMATION, LOSS OF BUSINESS INTERRUPTION OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES) ARISING OUT OF THE SOFTWARE, USE THEREOF OR INABILITY OF USE THEREOF EVEN IF CANON, CANON'S SUBSIDIARIES OR AFFILIATES, THEIR DISTRIBUTORS OR DEALERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU IN SUCH STATES WHICH DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES.
CANON, CANON'S SUBSIDIARIES AND AFFILIATES, THEIR DISTRIBUTORS AND DEALERS SHALL HAVE NO OBLIGATION TO INDEMNIFY YOU AGAINST ANY CLAIM OR SUIT BROUGHT BY A THIRD PARTY ALLEGING THAT THE SOFTWARE OR USE THEREOF INFRINGES ANY INTELLECTUAL PROPERTY OF SUCH THIRD PARTY.
6. TERM:
This Agreement is effective upon your clicking "I Agree" at the bottom of this page. You may terminate this Agreement by deleting the Software. This Agreement will also terminate if you fail to comply with any of the terms of this Agreement. In addition to Canon enforcing any of its legal rights, you shall then promptly delete the Software.
7. U.S. GOVERNMENT RESTRICTED RIGHTS NOTICE:
The Software is a "commercial item," as that term is defined at 48 C.F.R. 2.101 (Oct 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.72024 (June 1995), all U.S. Government End Users shall acquire the Software with only those rights set forth herein. Manufacturer is Canon Inc./30-2, Shimomaruko 3-chome, Ohta-ku, Tokyo 146-8501, Japan.
8. SEVERABILITY:
In the event that any provision of this Agreement is declared or found to be illegal by any court or tribunal of competent jurisdiction, such provision shall be null and void with respect to the jurisdiction of that court or tribunal and all the remaining provisions of this Agreement shall remain in full force and effect.
9. ACKNOWLEDGMENT:
BY CLICKING "I Agree" AT THE BOTTOM OF THIS PAGE, YOU SHALL BE DEEMED TO HAVE ACKNOWLEDGED THAT YOU HAVE READ THIS AGREEMENT, UNDERSTOOD IT, AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS. YOU FURTHER AGREE THAT THIS AGREEMENT IS THE COMPLETE AND EXCLUSIVE STATEMENT OF AGREEMENT BETWEEN YOU AND CANON CONCERNING THE SUBJECT MATTER HEREOF WHICH SUPERSEDES ANY PROPOSALS OR PRIOR AGREEMENT, ORAL OR WRITTEN, AND ANY OTHER COMMUNICATIONS BETWEEN THE PARTIES RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO AMENDMENT TO THIS AGREEMENT SHALL BE EFFECTIVE UNLESS SIGNED BY A DULY AUTHORIZED REPRESENTATIVE OF CANON.
I have read, understand the information above, and agree to same and wish to download the designated software.
Quote from: rufustfirefly on November 20, 2013, 11:02:14 PM
Looks like we're not about to see any official Magic Lantern versions based on the v1.2.3 firmware.
This is a non-issue. It has been widely discussed on here already and is well known to the developers that firmware downloaded from Canon's European sites doesn't have the reverse engineering clause. The work simply needs to be done by someone who knows how. I would have a go myself if I knew how to get a firmware dump of 1.2.3.
Ou puis-je télécharger la dernière version de ML pour le 5d3?? Merci d'avance!!
Bonjour;
J'ai essayé le dernière mouture sur mon MARK III firmware 1.1.3
Pas de problème ! Parfait.
pour aider, voici ce qu'il y a sur ma carte sd qu'il ne faut pas oublier de mettre en place
avant la mise en marche de l'appareil ++++
DCIM
MISC
ML
5D3-113-bootflag.fir
autoexec.bin
ROM.DAT
C'est tout!
il semble que pour une mise à jour, il faudra écraser le dossier ML et le fichier autoexec.bin
Ou puis-je trouver ces fichiers??
I hope this topic's language did not switch to French...
Quote from: Pelican on December 02, 2013, 04:48:29 PM
I hope this topic's language did not switch to French...
I will have to go back to school to learn it..! ;)
Hi guys,
just buyed today a 5d mkiii. I'm already using ml with 60d and 6d. i've read all i found about 5d mkiii ml development, and as i understood there's no safe way to disable bootflag from the camera and with the bootflag the camera needs seconds to switch on. correct?
So the first post on this thread suggest to use the "non autoboot" way, updating the firmware every time, or try at your own risk the developer version, hoping that sometimes in the future will be possible to disable the boot flag on the camera.
I've tried the alpha3 version. It works, but cannot see the most of magic lantern things (that's probably what is in the alpha3). So my question is, the only way to shoot raw, to use timelapse functions etc, is to use the developer firmware updater (enabling the boot flag) and using the nightly build?
Or is possible to have access to those functions also with the non-developer fir and doing every time the fir install procedure?
i've tried to put the files of the nightly in the same card of the FIR, but magic lantern still display only the alpha3 voices of menu.
thank you guys :)
Bump
The only information I can dig up on the forum about bitrate control and h264.ini is rather scattered and sometimes contradictive.
I know that this feature is of little interest compared to RAW video and the new ML video format, but I'd love to understand how to use the h264-ini or if this feature simply isn't ready/working on the 5dmk3 :)
So, if someone could point me towards he proper thread I'd be grateful.
Keep up the good work! :)
can anybody direct me to where i can find 1.1.3 its no longer on the European canon site. And my body has been updated to 1.2.3. :-\
Quote from: Maddoxfotos on December 12, 2013, 04:42:12 PM
can anybody direct me to where i can find 1.1.3 its no longer on the European canon site. And my body has been updated to 1.2.3. :-\
http://pel.hu/eoscard
scroll down
When I delete a RAW file, ML not recognise the empty size of the card after. So, I have to power off and turn on. It's posible change this?
Quote from: screamer on December 06, 2013, 12:06:20 PM
Hi guys,
just buyed today a 5d mkiii. I'm already using ml with 60d and 6d. i've read all i found about 5d mkiii ml development, and as i understood there's no safe way to disable bootflag from the camera and with the bootflag the camera needs seconds to switch on. correct?
So the first post on this thread suggest to use the "non autoboot" way, updating the firmware every time, or try at your own risk the developer version, hoping that sometimes in the future will be possible to disable the boot flag on the camera.
I've tried the alpha3 version. It works, but cannot see the most of magic lantern things (that's probably what is in the alpha3). So my question is, the only way to shoot raw, to use timelapse functions etc, is to use the developer firmware updater (enabling the boot flag) and using the nightly build?
Or is possible to have access to those functions also with the non-developer fir and doing every time the fir install procedure?
i've tried to put the files of the nightly in the same card of the FIR, but magic lantern still display only the alpha3 voices of menu.
thank you guys :)
+1
any help?
Quotecan anybody direct me to where i can find 1.1.3 its no longer on the European canon site. And my body has been updated to 1.2.3.
Just to inform you that you can't revert to 1.1.3 according to the following Canon note:
Notes:
- Once the EOS 5D Mark III camera is updated to Version 1.2.0 (or later), it cannot be restored to a previous firmware Version (Version 1.0.7 through 1.1.3).
Quote from: fbuff on December 22, 2013, 12:57:22 PM
Just to inform you that you can't revert to 1.1.3 according to the following Canon note:
Notes:
- Once the EOS 5D Mark III camera is updated to Version 1.2.0 (or later), it cannot be restored to a previous firmware Version (Version 1.0.7 through 1.1.3).
Even though Canon say that, plenty of people have reverted to 1.1.3 from a 1.2.x firmware without issue.
You can get the 1.1.3 firmware from here: http://chdk.wikia.com/wiki/Official_Canon_firmware_updates
Quote from: Maddoxfotos on December 12, 2013, 04:42:12 PM
can anybody direct me to where i can find 1.1.3 its no longer on the European canon site. And my body has been updated to 1.2.3. :-\
Google search on "5D300113.FIR" and the second answer, a dropbox link, worked perfectly for me.
jean-david
how can i install this on my 5D3? im using macbook (no windowz here)
Hi, i'm french.
Very good job of explaining the process but i don't have all the menus (expo, M..)
Why? :(
Thanks.
Quote from: Maddoxfotos on December 12, 2013, 04:42:12 PM
can anybody direct me to where i can find 1.1.3 its no longer on the European canon site. And my body has been updated to 1.2.3. :-\
It is here "Index of/user":
http://proofcreative.com/user/canon_5d3_113.zip
Quote from: fbuff on December 22, 2013, 12:57:22 PM
Just to inform you that you can't revert to 1.1.3 according to the following Canon note:
Notes:
- Once the EOS 5D Mark III camera is updated to Version 1.2.0 (or later), it cannot be restored to a previous firmware Version (Version 1.0.7 through 1.1.3).
Not true. Using Canon utility one can set up any version back and forth
Hi guyz,
I'm new to ML. I'm using a 5D3 with fir 113 because I was very interested by the bulb ramping feature.
So I installed the 5D3 Alpha 3 builds on my DSLR, but I can't find the bulb ramping feature.
As I understood, this Alpha is for testing purpose only and, so, has some features disabled. So, there is no way to use bulb ramping with 5D3 at the moment?
Thank you!
Hi All,
I have recently installed 5dmk3 alpha3 on my 5d mk3, I am unable to use the focus peaking the way I used to have ML on 5dmk2 . I am not finding those blinking dots no matter what settings I change on focus peaking. Can someone guide me if I am missing something.
Or Is there any other version which I should use.
THank you so much.
Always use the latest version here: http://builds.magiclantern.fm/#/
how many menu option should be available in the 'audio' setting of ML in the latest build.
also, what would be preventing me from being able to shoot raw above 1080? all I see is the can't shoot higher resolution in current settings or something along those lines...
Latest build can rec audio? I cant find the way...
Quote from: budafilms on January 16, 2014, 06:07:31 AM
Latest build can rec audio? I cant find the way...
http://www.magiclantern.fm/forum/index.php?topic=7122.0
EVERYONE: This is not the thread for raw recording Q&A.
Is there any way to install the code from the nightly build w/o using the .FIR that enables the bootflag? I am a developer (although only a lowly .NET C# one), so I could probably muddle thru creating my own custom build if need be -- with some guidance on what I need to change.
I imagine you'd have to set the bootflag to use any of the modules (e.g raw video), because I thought I've read that they require a reboot to become active. But it would be nice to get some of the other improvements and additional features of the nightly build.
Je ne trouve pas d'information clair pour installé magic lantern complet pour le 5d mark 3 et je n'arrive pas a faire une donnation pour pouvoir l'avoir! Si quelqu'un pourrai m'aider ce serai vraiment cool!! je suis quelqu'un de sérieux
Is there somewhere firmware 1.1.3 for MAC? I was follow each link from this site but was always landed for PC version.
I saw also that "threaten notice" that is impossible downgrade Mark III from 1.2.3 back to 1.1.3. Is that for real?
Thanks for sharing your knowledge. :)
It's a zip file. Just download and expand.
Canon's disclaimer isn't true.
Quote from: Walter Schulz on January 26, 2014, 11:38:09 AM
It's a zip file. Just download and expand.
Canon's disclaimer isn't true.
In the latest ML version, right?
TY!
gelöscht
Alex, g3gg0 and all,
I am taking a leap of faith tonight when I plunge into the darkest realms of my 5D3 by upgrading the firmware to the 1.2.1 version. This will take me off the ML radar for a while, but I will be around scanning through the forums and looking to benefit the user experience through the eyes of my EOSM.
The journey has been fantastic so far ... I learnt and learnt and learnt and ......
Codecs, conversion, confidence, creativity all have become my lifelong friends. I will see them again in the next life when the Alpha upgrades to handle the new firmware versions.
The main reason for moving on was, believe it or not, hard disk space. I am now 5TB,s of HDD and 1TB do SSD space down. So, instead of investing in another disk, I went and got me a Zacuto EVF pro with focus peaking and all. I cannot imagine a life without focus peaking after you folks got me hooked.
The feature I will miss most is the Dual_Iso and Raw record. Not to forget crop mode video.
The Dual_Iso feature for video is my favourite most thing of all times.
The most interesting feature for me was ETTR. I will continue to expose to the right even now and for ever ... God how I hate shadows and dark bands in my pictures.
I am and will remain a friend, supporter, fan and indebted for ever.
Warm regards
I've been actually running ML on 1.2.3 for about one week. So far so good, there are a few missing things, but I expect to merge it into mainline in the coming weeks and announce the new nightly builds.
Until then, you can take a peek here:
http://www.magiclantern.fm/forum/index.php?topic=9827.0
Hello my dear friends
Bought my 5d3 some months ago, took some time to feel familiar with everything, reading here and there, youtube videos etc.
Today I moved on to install ML Alpha 3.
I managed, was very easy by following simple instructions.
However, to my surprise didnt include the cool features, like RAW recording, intervalometer etc so I dig and found this
http://www.magiclantern.fm/forum/index.php?topic=5520.0
It took some time to sort things, format, install, reformat, nothing, again carefully ...
I managed to install the night build and I amazed that the development is far away from Alpha 3.
Congratulations to the developers and everyone that contributes to this project.
I dont blame anybody for my comments. cause I know that everybody contributes at his spare time together with family obligations and jobs.
However in order for someone to obtain structured and updated information for his needs, he has to be very careful and patient.
The information in the forums imho, is a bit messy and I noticed that several attempts were made in order to put some order.
Knowing that the development is something dynamic and the programmers prefer to code than writing manuals or helping newbies, naturally,
I wish some experienced people spend some time in separating information to make things easier.
I am sorry if anybody feels uncomfortable with my post, no intention to trigger arguments, but with constructive mood.
Thanks for your time.
hey Quentin... its a work in progress, and we've all been there, trying to figure it out. the simple fact, that we are able to play with it as its being developed is a risk and a learning process. some of the users here are pro's, some are amateurs, etc etc... so imagine, for someout there its a piece of cake to get the nightly build to run, for some it takes a week or two, and until its stamped as THERE IT IS... it will be like that. until then, enjoy your access to a true gem as its being polished :)
Quote from: Canon eos m on February 08, 2014, 04:45:48 AM
Alex, g3gg0 and all,
I am taking a leap of faith tonight when I plunge into the darkest realms of my 5D3 by upgrading the firmware to the 1.2.1 version. This will take me off the ML radar for a while, but I will be around scanning through the forums and looking to benefit the user experience through the eyes of my EOSM.
The journey has been fantastic so far ... I learnt and learnt and learnt and ......
Codecs, conversion, confidence, creativity all have become my lifelong friends. I will see them again in the next life when the Alpha upgrades to handle the new firmware versions.
The main reason for moving on was, believe it or not, hard disk space. I am now 5TB,s of HDD and 1TB do SSD space down. So, instead of investing in another disk, I went and got me a Zacuto EVF pro with focus peaking and all. I cannot imagine a life without focus peaking after you folks got me hooked.
The feature I will miss most is the Dual_Iso and Raw record. Not to forget crop mode video.
The Dual_Iso feature for video is my favourite most thing of all times.
The most interesting feature for me was ETTR. I will continue to expose to the right even now and for ever ... God how I hate shadows and dark bands in my pictures.
I am and will remain a friend, supporter, fan and indebted for ever.
Warm regards
Hi Alex, g3gg0, 1% and all,
I am back and happy to be so. Feels good to be home again!
Thanks a ton! This time around the pace of development seems faster and the interface appears more solid.
I can feel the action and am happy to be a part of it as a user and beneficiary.
Thank you to you all who make this journey a worth and memorable one!
Is 40 fps 1080p available in 1.1.3 ?
or is this specific to 1.2.3 ?
is there a possibility that i can run my 5d longer then 29:59 minutes in one peace?i would need it for a job please help.thx
Try the sticky shutter setting. Not sure but it has worked on other cameras.
@Danne Can you tell me what is the sticky shutter setting? Is it on Canon Menu or ML (If it's on the canon, as I don't have an english version, I don't really see what is it about and I'm very interesting by the ability to run longer than 29:59 minutes in one peace).
Many thanks !
http://wiki.magiclantern.fm/userguide#misc_key_settings
I just updated to 1.2.3 and I'm hopping on the ML train -- hoping I didn't do myself a disservice by upgrading to current firmware
Is there any possibility we will see the Magic zoom mapped to the half-shutter press like on the 5dMKII? Its sooo inconvenient being on the left of the camera and i love it on the halfshutter for event work.
Also will we see more audio functionality on this camera similar to the MKII, or is it hardware limited?
I wonder if 1.1.3 development is retired ? or it is recommended to move to 1.2.3 ?
Out of alpha status, and firmware installer updated.
http://www.magiclantern.fm/forum/index.php?topic=14704.0