Looks like we hit the jackpot with the M and its firmware dumper.
Thanks to your donations, Bart managed to send the "team" 650D to me to start the new port.
If everything goes according to plans (if the package gets here in time, that is), I'll probably have a 650D hello world by the end of the week
It took more than I expected, but here is the proof of concept:
(http://i.imgur.com/xMjaE.jpg)
(http://i.imgur.com/X8Jgr.jpg)
Welcome to the party, 650D!
May the fun begin...I'll keep you posted :)
For reference: #define RAM_OFFSET 0xFFA4DF58
Quote from: nanomad on November 29, 2012, 12:54:43 AM
Looks like we hit the jackpot with the M and its firmware dumper.
Thanks to your donations, Bart managed to send the "team" 650D to me to start the new port.
If everything goes according to plans (if the package gets here in time, that is), I'll probably have a 650D hello world by the end of the week
May the fun begin...I'll keep you posted :)
Good Luck
This is great news - I'd just bought a 650D but stupidly hadn't checked ML ran on it. Been grinding my teeth a bit.
Just made a small donation, in lieu of some practical help and to say 'thanks' to the team.
Steve
This makes me happy. Finally, the T4i unlocked.
I just lost my job the other day, but I'll be happy to scrape together a few bucks to help out.
Hooray! \o/
Also
Quote from: 33black on November 29, 2012, 01:31:00 AM
This makes me happy. Finally, the T4i unlocked.
I just lost my job the other day, but I'll be happy to scrape together a few bucks to help out.
Sorry abt the job loss. Hope you get a new better one soon.
yea, can´t wait to see ML on my 650D :D
Very good job ;)
I'm kinda hoping that a hidden All-I mode from the 5D MkIII is hidden in that 650D's firmware. :)
... or the cropped video from the 600D/T3i :)
Hopefully, the M didn't have crop mode or anything enabled so I guess its more like the 5d3.
great work! we've been on a roll lately :D
Quote from: nanomad on November 29, 2012, 12:54:43 AM
Looks like we hit the jackpot with the M and its firmware dumper.
Thanks to your donations, Bart managed to send the "team" 650D to me to start the new port.
If everything goes according to plans (if the package gets here in time, that is), I'll probably have a 650D hello world by the end of the week
May the fun begin...I'll keep you posted :)
Good Luck :)
OMG OMG OMG! This is insanely good news!!! My T3i got dunked in the Pacific last weekend and is now dead! Just ordered a T4i because I found it for almost the same price I would have paid to replace the T3i. THEN I find out ML isn't out for it yet.
Here's to hoping this puppy is a relatively painless port and that there are a few pleasant surprises along the way, courtesy of the DIGIC5!
Anything I can do to help speed up the work, I'm all ears!
Can you buy another camera for me ?
Just kidding ... You're welcome
The camera is here. Before going on with the development, here are my impressions so far (keep in mind I had the original 650 and a 1100D)
Like:
- Build quality
- Extra buttons (from the 1100D at least, I still miss the top LCD of the 650)
- Extra features
- Touch screen
Don't like
- "Nipple" buttons
- Some odd button placements (I'd have switched the position of the Menu and Info buttons with Play and Trash for easier one-hand operation)
Can you post the "Hello World" on the 650D as a 1920x1080 so I can use it for my desktop wallpaper ;)
I'll post it as big as I can, don't worry ;)
A quick update on the 650D status: I'm manually going through stubs using the 1100D as a reference, last check says I've got 45 more to do
First post here, total newbee to ML (never used it) but looking forward to test it on my 650D when possible.
A question to nanomad: When you say that you have "45 more stubs to do", what does that mean? Du you have an estimate when the ML will be available for the 650D?
Cheers!
Fred (from Sweden)
stubs are basically function locations in the firmware. There's a tool that helps auto-identifying them but it doesn't work on my PC (4Gb or RAM is not enough for the 650D and 1100D firmwares to be loaded together).
As always, There's no estimate but I can already guarantee you that ML will run on the 650D (at least as good as on the EOSM)
Thanks for you reply!
I´m happy with the guarantee that it will run on my camera...I´m in no hurry so I'll let you work i peace. :)
Quote from: nanomad on December 02, 2012, 11:29:39 PM
stubs are basically function locations in the firmware. There's a tool that helps auto-identifying them but it doesn't work on my PC (4Gb or RAM is not enough for the 650D and 1100D firmwares to be loaded together).
As always, There's no estimate but I can already guarantee you that ML will run on the 650D (at least as good as on the EOSM)
You need help in? ...
If you have problems with your computer I can try to help you!
Tell me what you need .... do you want to match the firmware with ARM-console?
I've done this with the 40D and 5D
I have 24GB so maybe I'll just set up a virtual machine for you to work on it?
Step 1: "Hello World"
Step 2: 4k video support :P
Thanks for the help...yes, I need to match the 1100D firmware (or any other recent camera for that matter) with the 650D one. The trouble is that I can't legally give you the 650D firmware....
one thing holding the M back right now is lack of buttons, so I'm forced to write a touch screen driver for ML. You should be able to advance faster so I can start copying your fixes :)
If you need help with stubs, I'm pretty good at it by now (2 years of working in IDA, i'm fairly efficient now). I found all of the M stubs (130 or so i think?) in just about 6 hours. The advantage to doing it by hand is you don't need to go through and double check everything ;)
Well, I only need to idenitify 16 or so stubs now, but only 3 or 4 are actually important
ya'll are talking WAY over my head hahaha. What is this "M" that everyone keeps talking about?
Quote from: InFocusAV on December 04, 2012, 01:56:52 AM
ya'll are talking WAY over my head hahaha. What is this "M" that everyone keeps talking about?
http://www.dpreview.com/previews/canon-eos-m (http://www.dpreview.com/previews/canon-eos-m)
I am happy to know that soon begin with the 650 ml. I also rush to choose the 650 without knowing that ran the ML. I already made a small donation for a while and just hoped
i like this "May the fun begin" i have a expresion in spanish in my country whit my friends is "capoooo". ;) I'm happy
Hello,
i am new here and sorry for my bad english.
One question: Is it planned to give the Eos650d a FULLSCREEN HDMI out over ML-Software for records with Blackmagic Hypershuttle2?
Thanks
Ralf
No idea, it's too early to speculate on that
I expect, rather than trying to add new features, the team will first try and port ML to the new cameras, changing only what's necessary to make it work.
Once that has been achieved (and released as part of the unified ML), effort can then be spent - if chosen - on adding features.
I think it's more important to port ML as-is to the new cameras than to try and exploit new features they may offer at the same time. This, I'd think, would be the approach giving the best chance of success.
Quote from: steve271 on December 04, 2012, 11:32:48 AM
I expect, rather than trying to add new features, the team will first try and port ML to the new cameras, changing only what's necessary to make it work.
Once that has been achieved (and released as part of the unified ML), effort can then be spent - if chosen - on adding features.
I think it's more important to port ML as-is to the new cameras than to try and exploit new features they may offer at the same time. This, I'd think, would be the approach giving the best chance of success.
Yes, that's my approach too. First make it stable, then start expanding on what we have (i.e. I'd like to work on the 1100D video mode but I feel that a stable 650D port of ML has an higher priority for the community)
I think that too :)
and i hope you guys will get i workin soon, i'm so nervous to flash my sd and have a nice, still more featurerich 650d!!!
Thanks for your great work!
Having a T2i and a T4i, I've been using the T4i as the 'A Camera' and the T2i as the B, since the T4i has the articulated screen, no 4GB limit and other small features, but I've really been missing the audio levels and such from the T2i with ML. Very much looking forward to this. Also looking forward to using high bitrates with UHS-I cards once ML unlocks it.
Though I'll be very please if All-I mode is found in that camera. :)
Quote from: AshleyAshes on December 04, 2012, 04:49:51 PM
Having a T2i and a T4i, I've been using the T4i as the 'A Camera' and the T2i as the B, since the T4i has the articulated screen, no 4GB limit and other small features, but I've really been missing the audio levels and such from the T2i with ML.
The T4i has audio level meters (at least the 650D does, assume they are the same). In the menus find sound level and set it to manual whereupon audio level meters appear.
This may not be as good as the ML ones, I haven't seem them except on videos.
Changelog:
Quote
Today's changes:
090a06dcfe95 | nanomad: 650D: One more batch of hand-picked stubs. Also: properly credit Indy for his stubs
3d0072976633 | nanomad: 650D: More stubs
Yesterday's changes:
a0efe51a1684 | nanomad: 650D: More stubs
Changes for last 30 days:
d0e4cb0cd610 | 2012-12-01 | nanomad: 650D: Start with a minimal feature set, the full one is left as a reference
3871a75af9f2 | 2012-12-01 | nanomad: 650D: Rename bootdisk stubs to match the other cameras
44ec357095c9 | 2012-12-01 | nanomad: 650D: Update stubs and consts.
394373540680 | 2012-11-30 | nanomad: Jumpstart the 650D port from the EOSM, tons of stuff missing
@Nanomad: go on!!!! :)
That reads HOT... feels like a baby 1 week after calculated birthdate... "every second it could be there, don't miss it!!!" :)
Quote from: nanomad on November 29, 2012, 12:54:43 AM
Looks like we hit the jackpot with the M and its firmware dumper.
Thanks to your donations, Bart managed to send the "team" 650D to me to start the new port.
If everything goes according to plans (if the package gets here in time, that is), I'll probably have a 650D hello world by the end of the week
May the fun begin...I'll keep you posted :)
How is it going? Is there something I can do to help?
3a2f564 650D: Stubs, again yesterday
Another commit, yay! How many are left? Is there anything I can do to help? I only have a 650D :)
Looking forward to the extensibility!
Thanks
woaw. that is fantastic news.
best of luck !
you have a whole bunch of fans supporting you ! please let us know how we can help (fw dump, tests, etc.)
Quote from: Chrisprols on December 07, 2012, 02:18:43 PM
woaw. that is fantastic news.
best of luck !
you have a whole bunch of fans supporting you ! please let us know how we can help (fw dump, tests, etc.)
yeah i hope you make that soon ... ;) ;) ;)
Get in there, nanomad!
Willing testsubject here, too!
I know there are plenty of willing testers. The truth is the stubs are done (well, except for a few but that's not really a big issue). The next step is enabling the bootflag and really start hacking on the ML source
That sounds great :D Let us know if there is anything the masses can help you with!
Just joined the group and can't wait to have all the impressive features of ML for my T4i....blown away by how much razzle dazzle with ML!
Thanks for all your efforts.
I also just joined :) I have been checking this site like a kid eagerly waiting for a present. I love the magic lantern's HDR feature. I am hoping that Digic 5 processors on T4i, 5Dmk3, EOS M will take the magic lantern to another level. so excited and happy :D
Quote from: t4ilover on December 09, 2012, 04:56:23 PM
I also just joined :) I have been checking this site like a kid eagerly waiting for a present. I love the magic lantern's HDR feature. I am hoping that Digic 5 processors on T4i, 5Dmk3, EOS M will take the magic lantern to another level. so excited and happy :D
Thank you... You are Welcome to our community...
You can say hello here :
http://www.magiclantern.fm/forum/index.php?board=29.0
http://www.magiclantern.fm/forum/index.php?topic=3812.0
:)
hello
i just wonder if i can use ML Logo when i editing shots what i make with Magic Lantern..
i was thing of put on begine something like :
Powered by Magic Lantern 2012
and logo
..something like that
and if yes from where ican download Logo...
i understand not all art`s are cool enought to put logo on..but its good to ask :D
Quote from: MzytengaM on December 09, 2012, 05:36:41 PM
i just wonder if i can use ML Logo when i editing shots what i make with Magic Lantern..
Just like at the end of movies: Color by Technicolor!
I guess, even if you're using the Technicolor Profile on DSLR, you probably
can't use the image in your end titles (copyright issue). I wonder about ML though.
Just joined, been lurking for years...and I'm still shooting with the ORIGINAL Digital Rebel....so you know I don't upgrade often....
Amazon has the T4i body tonight for $599...I have been debating the T3i vs. T4i for months. Really, the only thing that's holding me back on the T4i is the lack of video digital zoom 3x - 10x. I'd prefer the T4i for touch screen and all cross points focusing, but I do shoot quite a bit of video.
Anyway, my question: what are the chances that ML would support the 3x-10x video digital zoom on the T4i?? If you know it's going to be 0-10% for 2 years, that helps my decision making. But on the other hand if the it's 90% chance in 3 months, that helps too. Of course, there's always waiting for the T5i too, just don't think I can wait that long :-\
TIA for any suggestions. Keep up the awesome work, and you can count on me for a donation! Happy Holidays to all!
Just to let you know, the digital zoom got me thinking about buying the 650 for a while... but when I got that I realized it does have digital zoom, but it is not accessible from the buttons,,, rahter, from the touch screen... But it's the same 3x and 10x :) :)
Digital zoom is not the issue, the lack of video crop mode is (if you want the best possible IQ). It's sad because the 600 had it
@robertsabian
I read the manuals from Canon's web site on the T4i and the T3i. The T3i has the "Movie Digital Zoom" feature on page 152.
For the T4i, there is no feature listed, and many reviews say it is not in the T4i.
http://blog.mtkalin.com/?p=42
http://www.chadsorianophotoblog.com/2012/06/canon-eos-rebel-t4i650d-video-test.html
http://en.wikipedia.org/wiki/Canon_EOS_650D
Regardless of the exact terminology, whether movie digital zoom or video crop mode, this is what I want to do with the T4i:
fast forward to 1:30 https://www.youtube.com/watch?v=D5wNPv60U_o
@nanomad - what do you think the chances are ML could get this feature back? 0%, 50%, 90%?
Thanks again!
Quote from: robertsabian on December 10, 2012, 01:21:50 PM
Just to let you know, the digital zoom got me thinking about buying the 650 for a while... but when I got that I realized it does have digital zoom, but it is not accessible from the buttons,,, rahter, from the touch screen... But it's the same 3x and 10x :) :)
Are you sure...? Only zoom I can find in the touch screen is the x1, x5 and x10 for focus assistance. This zoom is not for shooting film, it resets as soon as the rec button is pressed.
Quote from: Paxman on December 10, 2012, 07:03:30 PM
Are you sure...? Only zoom I can find in the touch screen is the x1, x5 and x10 for focus assistance. This zoom is not for shooting film, it resets as soon as the rec button is pressed.
I second that. No digital zoom in movie mode.
Hi, I just start at this forum. I have a doubt, in the first page of this discussion, steve271 said that he's apply the actual ML to his camera and work. It's right? Can I apply to my T4i without any fear to damage my camera? Thanks.
Quote from: RMiranda75 on December 12, 2012, 08:17:32 AM
Hi, I just start at this forum. I have a doubt, in the first page of this discussion, steve271 said that he's apply the actual ML to his camera and work. It's right? Can I apply to my T4i without any fear to damage my camera? Thanks.
There's no Magic Lantern for the 650D/T4i yet. You read wrong
Hallo...kann ich vielleicht helfen in dem ich die Software auf meine Eos 650d spiele und teste?
Hallo...can i help to test the Software with my eos 650d?
Ralf
Quote from: RAK1966 on December 12, 2012, 12:04:16 PM
Hallo...kann ich vielleicht helfen in dem ich die Software auf meine Eos 650d spiele und teste?
Hallo...can i help to test the Software with my eos 650d?
Ralf
Hello Ralf. Please read the topic. This has been proposed by many people already.
I guess ML staff will let people know when theres any beta out.
Thanks!
Looks like it's working ;)
(http://i.imgur.com/xMjaE.jpg)
(http://i.imgur.com/X8Jgr.jpg)
Thanks to Indy and the whole team (Alex and coutts in particular) for helping me start this port
:D ;D
Nice the black color scheme for photo mode.
Awesome! :D
Great work lads!
Great work :)
Quote from: RMiranda75 on December 12, 2012, 08:17:32 AMmy T4i without any fear
lol i was heard T4i got touche screan :DDDD
i got question ...tis touche screan is for what ? :DD
and if this is only one diference betwen T3i what is point pay more ?
for touche screan ? :DD ... Canon going in wrong way.. it will be soon like... Canon iRebel Pod T6mini
Well, there's a digic V processor in it and a few additions for handled shooting. And video mode AF
Quote from: nanomad on December 12, 2012, 05:22:11 PM
Well, there's a digic V processor in it and a few additions for handled shooting. And video mode AF
ok better cpu ..
Nikon d3200 got 3 digit .. i just thing why canon needs to have 5 on that camera,, if this realy make quality up..or its just for faster moving in Menue lol.. or that 5 it must be only cus touche screan
nanomad, I never doubted you for one second! Ok, maybe for just a second.. or a few hundre.. anyway, congrats on an awesome achievement, and just in time for Chistmas. Doesn't get much better than that!
How long before we see an alpha?? :P
It may be a while, I can't risk bricking people's cameras ;)
Best news all day.
And to update on a post I made 2 weeks ago at the beginning of this thread, I am re-employed. Start a new job today.
Thankfully that didn't take long, so the donation will be coming, just in time for xmas.
REALLY looking forward to getting my hands on this Alpha. I've had a camera for months now that just has basic features. boohoo.
Hi Namomad,
Could you please publish the 650d_101.fir in the source tree ?
It will allow other 650D/T4i owners to enable the bootflag and get a backup (but nothing more) ?
We need more developers, so we have to help them.
Indy
Sure, I didn't upload it because we usually don't have FIRs in the report. I was thinking of uploading the whole hello world sample as a download either here or on bit bucket
I'll sort it first thing tomorrow
Hello!
well, I'm new in this forum
I just got a 650D and I'm a software developer,
I would like to help on the port of 650D but I'm a bit lost,
how should I start??
I work with a mac, but I have a virtualized linux, so I can work on both...
I read how to install the tools, but I don't know from where should I get the firmware, or if it's possible to download it from the camera...
thanks
I'm uploading the "toolkit" right now (it allows you to enable the bootflag and dump the firmware from you camera)
Stubs status, from ML in-camera test:
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1ad194
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] memcpy(foo, bar, 6) => 0x1ad0c0
[FAIL] foo => ''
[Pass] memset(bar, '*', 5) => 0x1ad0a0
[FAIL] bar => '*****ghjkl'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0x3e1c2
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0x7d005
Looks like there's something going on with the strings, although I can't understand what.....
Looks like there's something going on with the strings, although I can't understand what.....
Where can we download the stubs code from please nanomad, it's not possible to look at that excerpt and deduce things aren't working as I don't think we can see what value of 'bar' has been set.
It's always possible the test code has some previously un-noticed bugs ... worth a second look.
Steve
Great work to everyone who was involved!
Quote from: steve271 on December 13, 2012, 07:46:44 PM
Looks like there's something going on with the strings, although I can't understand what.....
Where can we download the stubs code from please nanomad, it's not possible to look at that excerpt and deduce things aren't working as I don't think we can see what value of 'bar' has been set.
It's always possible the test code has some previously un-noticed bugs ... worth a second look.
Steve
Its on the repo inside debug.c as usual :-)
Got it, thanks.
char bar[] __attribute__((aligned(32))) = "asdfghjkl;";
I guess this has all worked before ... but...
I find the macros a bit hard to decode, but is it possible the semi-colon in the 'bar' string is causing some sort of premature termination in the test strings during the macro expansion?
Maybe change the ";" to another character?
Good catch, I'll try it now
edit: didn't solve anything, altough I tried a "manual" test and the stubs passed it with flying colors
Great job nanomad and the rest of the team! Lets hope everything goes smooth the rest of the way.
So... I am a Video Production teacher looking to put ML on my T4i (which I am assuming is the same thing as the 650D). Being a newbie to the ML forums, what I gather from this thread is that ML has been ported successfully to the t4i? Would you recommend on using ML at this point or should I wait until the next build?
Sorry if its a silly question, and let me know if I needed to post it somewhere else!
Quote from: treyboden on December 14, 2012, 03:23:06 PM
So... I am a Video Production teacher looking to put ML on my T4i (which I am assuming is the same thing as the 650D). Being a newbie to the ML forums, what I gather from this thread is that ML has been ported successfully to the t4i? Would you recommend on using ML at this point or should I wait until the next build?
Sorry if its a silly question, and let me know if I needed to post it somewhere else!
No, ML has not yet been ported. The camera has been hacked, which means code can now be run on it. Once the bulk of ML is ported, there will be an alpha release, which is generally unstable and still contains lots of bugs. Once most of the bugs are fixed it will go into beta. When the port is completely stable and no major bugs are reported it will then be ready for a final release.
Which basically means don't expect an alpha before 2013
Hi,
anyone who want to help can enable the bootflag and backup memory using this
https://bitbucket.org/hudson/magic-lantern/src/4cd4e9ae685013224e165f6286e3718dc3eee8cb/platform/650D.101/devkit/650d_dumper.rar?at=unified
Indy
do NOT use a 'prepared card' with EOScard or similar !
use normal card, as formatted by the camera or your operating system.
Indy
(sold my 1100D and bought a 650D)Quote from: Indy on December 14, 2012, 08:02:04 PM
anyone who want to help can enable the bootflag and backup memory using this
Copied the files onto an 16GB SDHC card.
Started the 650D,
'updated' the firmware,
the camera reboots,
the camera comes back to life,
the screen displays
"font addr bad"
"Hello world!"
"EnableBootdisk"
"Oops!"
And a very happy feeling that ML is actualy possible.
Taking pictures works, the camera is in perfect working order.
When I switch off the camera the red led stays on.
Removing and reinserting the battery solves this.
The SDHC card now contains K301_101.DAT
What else can I do to help ?
Quote from: Canon Amateur on December 14, 2012, 10:55:23 PM
(sold my 1100D and bought a 650D)
Copied the files onto an 16GB SDHC card.
Started the 650D,
'updated' the firmware,
the camera reboots,
the camera comes back to life,
the screen displays
"font addr bad"
"Hello world!"
"EnableBootdisk"
"Oops!"
And a very happy feeling that ML is actualy possible.
Taking pictures works, the camera is in perfect working order.
When I switch off the camera the red led stays on.
Removing and reinserting the battery solves this.
The SDHC card now contains K301_101.DAT
What else can I do to help ?
Well, you can help porting if you have time and skills :)
By the way, the solid red light on shutdown (lockup) it's a known issue on the 650D
Quote from: nanomad on December 15, 2012, 12:28:18 AM
Well, you can help porting if you have time and skills :)
By the way, the solid red light on shutdown (lockup) it's a known issue on the 650D
:) I am affraid that I don't have the time and very limited skills.
The red light means in normal conditions that a write action is active.
Just to be sure I waited for 15 minutes for the light to go out.
After 15 minutes I figured that the memory dump should be complete and switched off the camera and removed the battery.
Im new to this world, will be getting my first DSLR, I was going to get the T4i, then I heard about Magic Lantern and liked the features it offered but heard it wasnt on such camera so I was going to get the T3i but now that I see this Im excited, I will get the T4i and as soon as I can I will donate ^_^ looking forward to watching the progress.
any updates yet? that EOS M version moved along REAL quick.
Updates? Yes, the work is going on. I'm testing what's working and what's not at the moment. ::)
Wish i could help out, but my coding days are long gone. now i'm just am actor / amateur filmmaker.
i am tempted to dump the firmware to see what makes it tick...
Okay sorry dumb question but I looked briefly ^^;; but umm where do I go to donate?
Donations are currently disabled while we figure out some organizational details. You can donate to the EFF instead, they do a great job fighting for our "digital" rights and also helped us with legal advice.
Okay sounds good, I will do a small donation to them and another to you guys once you have the system back up... Cant wait to here about some more progress and maybe some more pictures, me likey progress pictures ^_^
There may be an alpha before Xmas after all.... what features would you like to be featured in the upcoming Alpha 1?
I really like to have the ability to do Time Lapse and set the time between shots, is it also possible to do something similar but recording a video so making a recorded time lapse video or stitching the photos together into a video to save a step? if not no worries just a thought.
Quote from: nanomad on December 19, 2012, 09:12:17 PM
There may be an alpha before Xmas after all.... what features would you like to be featured in the upcoming Alpha 1?
I use the Zebra's, Cropmarks and "Quick Zoom SinglePress -> 100%"when I shoot sports with my 50D.
When I feel the urge to experiment I use the extended ISO (25600).
Chomping at the bit for the release...would probably choose motion detection, the fps override and movie restart for some alpha joy.
Quote from: nanomad on December 19, 2012, 09:12:17 PM
There may be an alpha before Xmas after all.... what features would you like to be featured in the upcoming Alpha 1?
High bitrate modes. I wanna see what the T4i's UHS-I drive can do. :)
I would choose focus stacking and motion detection.
But don't let us bully you out of any sort of holiday nano ! :)
just waiting for independent ISO and shutters.
looking forward to having the pro camera features, finally.
its a more than capable DSLR, it sucks how they cripple them.
Restoring the 3x-10x digital video zoom / video crop mode of the 600D would be welcome by many I think.
QuoteRestoring the 3x-10x digital video zoom / video crop mode of the 600D would be welcome by many I think.
I'm sure it will be welcome especially by Canon ;)
I havent had a camera with ML yet (40D and 650D) so I haven't had a chance to evaluate the features. But I am most excited to use focus peaking and zebra stripes.High bit rate, iso override and zoom mode in video are not useful if its out of focus or improperly exposed.
Quote from: tdbartley on December 20, 2012, 01:53:16 PM
.High bit rate, iso override and zoom mode in video are not useful if its out of focus or improperly exposed.
u are not usefull... lets delete everything
Hi,
I am new in here.
I would love to see ML working on the t4i.
kind regards
Christian ;D
Great to hear you've made this much progress before the holidays! Thanks for all your hard work :)
Quote from: nanomad on December 19, 2012, 09:12:17 PM
There may be an alpha before Xmas after all.... what features would you like to be featured in the upcoming Alpha 1?
1) focus peaking
2) histogram
happy holidays!
I will second FPS override.
Hi, i follow this discussion from almost the beginning ! I marked this page in my favorite
and check it almost twice a day !!!
I have a T4I and work a lot with it. The biggest thing i'd love in Magic Lantern
is the sound volume while recording.
I miss so much that from the t2i.
Nanomad, thank you man !
Cheers
A quick update:
(http://i.imgur.com/9BhVc.jpg)
(http://i.imgur.com/741NH.jpg)
As you can see my 650D battery is flat. I'll post the build once I fix that (easy, just plug it in the charger and wait) and I block touch screen events in ML-menu (easy-ish).
For the feature set, I'm shooting for something like the EOS-M alpha 1 and 5D3 alpha 3. There shouldn't be any major side effects and should be pretty safe to test.
I am glad to see the progress! This is a great christmas present nanomad! Thank you for all your work.
Like other said already, I am looking forward for the focus peak, color temperature control and other usefull features!
Big surprise ... and I still waiting for 'my' camera ... : (
Impressive !!!
Great Job Nanomad
very awesome, thank you for your hard work. ^_^ I get my Camera on the 26th
Great Job Nanomad?
Interval is a?
Excellent work!
I decided to buy a DSLR this Christmas, after too many years of P&S cameras that P'd and S'd, but took lousy or out of focus pictures, or simply refused to continue working. One of the main reasons that I chose Canon was the maturity of the ML software and community I really wanted to buy a T2i because I could get a complete, fully supported ML distribution without having to do any work, but the price (even of used equipment) was simply too high relative to a brand-new T4i, so I ended up with the 650D (Well, Amazon tells me I'll have it before Christmas).
I've got a lot of years doing embedded development for a lot of different companies on a lot of different platforms, so I hope to be able to help out here. I've obviously got no background on Canon cameras, but I'm pretty sure I can pick it up quickly if that's where the help is needed - if it's needed with testing, or documentation, or just BS'ing, I'm good for that also.
I really want to thank nanomad for his work on my camera of choice; I'll be heading over to the donation station to express my thanks in a little bit more concrete form.
And I want to apologize to Kilr0y for using a similar nom de guerre, but this is one I've used for a lot of years on a number of different forums, so hopefully we can peacefully coexist.
Hello
You are welcome to our community. This is growing and we need more developers. Any contribution is welcome.
Side question do you think ML would work with Chainfires DSLR Controller android app? I think if the two could come together and work together on making special features and so on that would be AMAZING ^_^
http://dslrcontroller.com/
Edit: yup people are confirming that it works, freaking sweet :)
I've got a lockup while running stability tests. The alpha is on hold while I figure out what causes it. maybe it's nothing but I'm not willing to overlook a potential serious bug.
In the meanwhile you can already compile ML for the 650D yourself and do some tests too.
Quote from: KilroySmith on December 22, 2012, 07:46:02 AM
And I want to apologize to Kilr0y for using a similar nom de guerre, but this is one I've used for a lot of years on a number of different forums, so hopefully we can peacefully coexist.
I've usd Killr0y for about 20 years, but don't let that stop you!
Hi...
I'm also a media teacher and have just got 2 600d's and 2 650d's. (one of the 650's is my personal one)
I'm also really looking forward to the port on the 650d
I wondered if there is any way the audio page can be implemented on the 650d?
Thanks
Midas
Quote from: KilroySmith on December 22, 2012, 07:46:02 AM
I've got a lot of years doing embedded development for a lot of different companies on a lot of different platforms, so I hope to be able to help out here. I've obviously got no background on Canon cameras, but I'm pretty sure I can pick it up quickly if that's where the help is needed - if it's needed with testing, or documentation, or just BS'ing, I'm good for that also.
just start setting up the toolchain until you can compile ML, update from repository and read into the source code what ML is doing.
hint:
it all starts with reboot.c which is executed by bootloader, copies (contained) magiclantern.bin to runtime address and jumps in there to the boot-hack.c's copy_and_restart().
magiclantern.bin is the whole ML stuff statically linked to the runtime addresses (usually around 0xC80100)
so ML startup is in two phases.
it's easy to think about reboot.c as sort of magic lantern's own bootloader, that copies ML itself into ram and then jumps into it.
oh heres a question so it copies itself into the Ram of the camera so does that affect the performance of the camera in anyway? like when doing rapid shots is the buffer for said rapid shots used by the ram and thus you have less so it fills up quicker and reduces the speed of the shots until its offloaded into the memory card or anything else a long those lines that use the ram?
Quote from: kazeone on December 25, 2012, 07:54:25 AM
oh heres a question so it copies itself into the Ram of the camera so does that affect the performance of the camera in anyway? like when doing rapid shots is the buffer for said rapid shots used by the ram and thus you have less so it fills up quicker and reduces the speed of the shots until its offloaded into the memory card or anything else a long those lines that use the ram?
No, ML don't use that part of ram, RAM is already not all available for shooting buffer
even with ML copied to ram and running all of its tasks, the 6D for example still has almost 3mb of available memory, so it hardly makes a dent.
oh okay cool :)
Edit: Woot! My camera just showed up ^_^ let the fun begin.
Hello Merry Christmas! Please tell me nanomad, when you say "In the meanwhile you can already compile ML for the 650D yourself and do some tests too." I have a question... i download the ML version 2.3 and run in the camera? or first update the firmware to this camera 650D? and then run the ML 2.3??? (or use another update to this camera)
I am impatient. I cannot expect to prove it ... I tell you Nanomad that if you disconnect the touch the battery hard mas there is difference.
But i dont have experience to installing firmware ML. I am learning for this way
it would be wonderful if alpha version has a intervalometer
can't wait for the alpha! ;)
great job, nanomad!
merry christmas! ;D
My fiance got me a T4i with the 18-135 STM lens for Christmas...I couldn't be happier! It's my first DSLR and a friend of mine told me about ML. I'm excited to see there will be a port for the T4i. I will donate as soon as I can!
I bought a T4i aka 650D, I'm happy with it but I'm really looking to use Magic Lantern so I'm thinking to get the 60D, but I'm not sure, any recommendations?
Quote from: nanomad on December 04, 2012, 10:49:36 AM
No idea, it's too early to speculate on that
New to ML but I have tons of friends in the film industry that use it.
I bought two canon t4i's and I have was hoping that with ml I will help me take my photography to the next level, and add film making to my repertoire.
Thanks to Ml team and all the supporters.
I will be making a contribution to ml when ever possible.
oh just wondering does ML work with the touch screen? or would I use the physical buttons?
It works with both. The touch screen emulates some buttons while in ML menu
Hi nanomad we chatted on the 1100D thread and then a deal came along and I got the t4i for 300 200 after a bit of work and returned the T3. Haven't even unboxed it yet, but I'll be watching this thread closely.
Happy new year guys..! :)
Light my life with ML in this year :)
Appreciate your hard work :)
Thanks for the reply,
I hope you had a great Holiday and a great New Years ^_^
How goes everything?
Thank you very much!!! This is big deal for me! I'm waiting for ML for 650D since september. Thank you very much.
I'm webdeveloper and if my help is needed ... I'm your man!
Any chance someone can find the property address for movie servo AF and what its supposed to be when on/off.
On 6D I think its named PROP_MOVIE_SERVO_AF, I think.
Sure ill do it tomorrow / today
Btw I'm currently busy with some backend changes that should reduce the overall amount of distraction bugs in ML and make porting to new cameras easier.... The 650D alpha will suffer a bit of delay but should also come up more stable than before :-)
I like this. I really like this.
Thinking of taking a look through the source code myself and brushing off the old programmers fingers for shits and giggles.
How do I get started? where's the thread on that?
I'm probably too lazy to search for it.
The getting started thread is at http://www.magiclantern.fm/forum/index.php?topic=991
Quote from: a1ex on June 07, 2012, 12:55:48 PM
Step 1. Get the source code
hg clone -r unified https://bitbucket.org/hudson/magic-lantern (https://bitbucket.org/hudson/magic-lantern)
Step 2a. Setup the compiler
http://www.magiclantern.wikia.com/wiki/Build_instructions/Unified (http://www.magiclantern.wikia.com/wiki/Build_instructions/Unified)
Step 2b. Or Use a pre-built toolcahin
https://launchpad.net/gcc-arm-embedded
Step 3. Start hacking
http://www.magiclantern.wikia.com/wiki/For_Developers (http://www.magiclantern.wikia.com/wiki/For_Developers)
I personally prefer step 2b
Thinking about it, I'd be willing to throw my T4i in for alpha testing. There's minimal risk of bricking right? It just could be so unstable that it'd be unwise to use it on a 'main camera'?
If you disable properties from features.h the risk of bricking should be really small (unless one of the stubs is wrong, then it's a different story)
Have you got any idea when will be done the ML for 650D? Just a guess? This month, february, later?
Done? We're never done....
This weekend I'll have an idea of a possible release date for alpha
I've got a bit it catching up to do with the latest ML commits
It's adequat for winter tests :P
Hello,
I just wanted to pop in and say that this is very exciting for me as a new t4i / 650d owner (upgrading from my trusty 300d I got close to 10 years ago.)
I did some research into the t4i before I bought it, but in all of my research into the t2i, t3i, and t4i, I had never come across any information on magic lantern. If I had I may have bought a different camera but it seems that the t4i has potential for magic lantern to make it pretty special.
I still know little about magic lantern, so I wanted to ask if some of my hopes could be considered realistic. I have read a few posts asking for the ability of the 10x digital zoom for video to be unlocked like the t3i and would like to add my voice to that request, if such a thing is possible.
Some maybe more complicated features to implement that would be great (again I don't know how realistic some of my hopes are so take that into consideration) would be to unlock the ability to get 1080p60 video and maybe a better downsampling script to eliminate the heavy moire patterns that show up in video. If we are really lucky maybe there will be a way to make the continuous auto focus actually useful.
Maybe opening up some more control over HDR would be possible too. Anyways, I plan to follow this thread for a while and see where things go. Thank you to everyone working on magic lantern for this camera, it certainly gives us t4i owners something to look forward to.
Thank you!
I am thrilled. I would like to more brackets 5 7 9. and maybe +-3 on the bracketing. thanks for your efforts all who are working on this. I am looking forward to ALPHA.
Is there a point of getting class 10 UHS-I (95MB/s) card insead of class 10 SDXC (45MB/s).Price is double here. Does there will be video features that can use the speed of 95MB/s or 45MB/s is good enough?
UHS card is always better for video, especially now that the cameras support UHS speeds.
I've got a UHS card and I can defintely feel the difference (especially when shooting bursts in RAW+L)
actually I made a mistake, for example Sandisk makes 3 different speed UHS SD cards: 95,45 ja 30MB/s. The first one is quite expensive, but can Magic Lantern benefit from it?
in Rapid Burst or "sports mode" you will certainly see a difference with the faster write speeds, your camera will be able to make more rapid shots with out having to slow down to wait for the buffer to unload onto the SD card. I have the Extreme 16gb but I plan to get a 32gb Extreme Pro eventually.
The problem is the small picture-buffer. I can only take 3 raw+L shots in a row with my 650d
A fast card can´t compensate that .
I bought the patriot knockoff of the 90MB card. Real performance would have to be tested in the camera. With these sleazy manufacturers I feel the specs are gibberish. Digic IV is stuck at 20MB but the UHS card will do it longer. Not impressed with increase from 6D tho. 600D seemed to do almost as well.... although on the UHS card audio doesn't stop even with 100Mbps video going.
In the DM log when you record a clip it tells you how fast the files were written out, at least it did on 600D. But don't buy sandisk, their UHS pro card is like $200, others have it for a 1/3 or a 1/4 of that. Look at the sustained write spec if they aren't scared to list it.
UHS-I would be pretty useful with increasing the bitrate of video recorded. Class 10 cards hit the bottleneck pretty quickly. I think UHS-I is required media for All-I compression on the 6D and 5D for this reason (Assuming you're not using CF on the 5D)
I can do all I just fine on non-UHS cards. People tested class IV cards that did the full 20MB/s. Its really hit or miss and you have to read reviews and tests to find out the real sustained write speed. The burst speeds are lies.
I can probably enable 5D3 CF card test and see how the 650D does with a UHS-I card
The 5D3 card test is not for speed, is for diagnosing a bug.
You have a card speed test under Debug menu on all cameras (including the good old 5Dc).
Hey all! First post on ML forums :D and I too eagerly await ML for the 650D.
I'm fairly new to ML, never having used it before but read a fair bit so people talking about write speeds of their cards leads me to wonder if ML would ever be able to increase the buffer on the 650D?
P.s is the direct 650D donate system setup yet? I would be more than happy to help out in any way I can.
One of the first minor things I would love to see possible on the T4i is Kelvin WB control. It's a major buzz-kill that could change this baby into a good companion for my 5dMk3.
Has this been done on any other models where there wasn't out of the box Kelvin WB control?
Quote from: a1ex on January 11, 2013, 09:43:48 AM
The 5D3 card test is not for speed, is for diagnosing a bug.
You have a card speed test under Debug menu on all cameras (including the good old 5Dc).
Ah ok, that's the test I had in mind btw. I was sure it wasn't there on the 650D but I must have missed it
You guys should see if you can use ivaparams on 650D or if you're stuck with setting QP and the other options.
Can have a UHS slice vs UHS ivaparam showdown :)
Quote from: 1% on January 11, 2013, 06:24:53 PM
You guys should see if you can use ivaparams on 650D or if you're stuck with setting QP and the other options.
Can have a UHS slice vs UHS ivaparam showdown :)
Nope, just good old QP. IVA probably comes from the FullFrame branch
When you are planning a trial version?
(http://www.my-wall-decal.com/img/nukem_wall_decal_header.jpg)
More seriously, I'm checking the feautres right now to see what's working and what's not
Nanomad, I hope to soon be able to help you in whatever way necessary.
I'm almost ready to release on 6D.
Need:
* New Peaking on LV not just image review.
* Stop ASIF DAC/ADC properly
* More Memory
* Lens info/ISO display and setting fixed.
Pretty much everything else works. Audio just really needs monitor mode as AGC can be turned off.
Card speed tests
Write, buffer=128k -> 18.2 MB/s
Read, buffer=128k -> 20.4 MB/s
Write, buffer=16384k -> I couldn't read it properly but it was around 45
I wish you success in tests and I count for future works.
Hello,
Will the digital zoom be available with ML in video mode?
Cheers and good luck
It crashed 6D and kept crashing it until the C mode was reset.
The zoom seems to be invoked from the video_parameters property. Mode 0xC flips it to crop mode on 600D. Dzoom ratio property did not respond to changes. On 6D both properties are larger. I imagine on 650D the behaviour will be the same as 6D. It could be something else other than 0xC in newer cameras, I need to find the location or function where all of the modes are listed. Could be different modes on FF or digicV. The functions are in FW tho.
Hey nanomad,
I'm really hoping Kelvin WB can make it into the Alpha for the T4i. Have you tested this feature yet? It's such a small missing feature, but I can't stand not having it since I switch between this and my 5d3 all the time. I shoot 100% manual and Kelvin WB, so this would be HUGE for me.
I am so stoked on what you're doing! My T4i can't wait :P
Quote from: 1ricca on January 13, 2013, 05:33:37 AM
Hey nanomad,
I'm really hoping Kelvin WB can make it into the Alpha for the T4i. Have you tested this feature yet? It's such a small missing feature, but I can't stand not having it since I switch between this and my 5d3 all the time. I shoot 100% manual and Kelvin WB, so this would be HUGE for me.
I am so stoked on what you're doing! My T4i can't wait :P
so when you say KelvinWB do you mean have the ability to select various number values versus AutoWB, Day, Night, Fluorescence pre-configured settings in the WB menu?
Quote from: kazeone on January 13, 2013, 06:03:12 AM
so when you say KelvinWB do you mean have the ability to select various number values versus AutoWB, Day, Night, Fluorescence pre-configured settings in the WB menu?
Yes, precisely. It's a feature that has been implemented with ML on the T2i and T3i (550d and 600d). It's on the 5dMkII and 5dMKIII vanilla/canon firmware where you set it to "Kelvin" as one of the presets and then spin the top shutter wheel to change values. It usually ranges from 2500-10,000. I'm not expecting it to be implemented as well as the vanilla firmware on upper models (though that would be amazing) but at least the way it has been done with ML on the 550d and 600d.
It also kind of stinks that the way Canon ordered the WB presets is not in warm-cold order. IMO it should go from coldest prest to warmest preset from left to right. The current vanilla FW way is just lame and cumbersome to change, especially in video mode, as it stands right now and is of course missing all of the steps in between those presets. Also, the lowest K value in the presets is ~3200 and highest is ~7000. It's nice to be able to go all the way down to 2500K for night time shooting for the most natural look of night time. But the main thing is the lack of in-between K settings that makes it impossible to sync my WB with my 5d3 on shoots.
Quote from: 1ricca on January 13, 2013, 06:12:14 AM
Kelvin!
I gotta bump this post because white balance in kelvin would be a awesome addition to the t4i.
It's working but it won't probably make to alpha 1 because it relies on property changes
Quote from: nanomad on January 13, 2013, 10:43:19 AM
It's working but it won't probably make to alpha 1 because it relies on property changes
That's still great news! Thank you so much!
What's the chances of a hotkey or button+wheel combo to change Kelvin temp?
Oh man, you guys are so great. In about a year or so when our company profit starts going green, I am TOTALLY donating a camera for whatever you are working on! You can hold me to that! ;)
Hi Nanomad,
It is possible to integrate high-speed sync?
Best,
Hi...
I'm a media teacher and have just got 2 600d's and 2 650d's. (one of the 650's is my personal one)
I'm also really looking forward to the port on the 650d and thank you for all your effort so far
I wondered if there is any way the audio page or parts of it can be implemented on the 650d?
Thanks
Midas
High speed sync: dunno. It may require a significant re effort as I don't have any cameras that support it
Audio tweaks: in the future yes, as long as we figure out the chip inside
Forgive me. What is High Speed Sync?
Answers, lot of them ... (http://lmgtfy.com/?q=high+speed+sync)
Quote from: Walter Schulz on January 14, 2013, 07:01:37 AM
Answers, lot of them ... (http://lmgtfy.com/?q=high+speed+sync)
thats sorta an asshole way to reply to a question dont you think? of course anyone could google for the answer but part of the time the asking of the question is not only for seeking an answer but the social aspect of a forum. Also there is no better way to make a person feel un-welcomed in a forum then by the way you just did in your comment.
So you dont need to explain what the answer to the question was but merely state something a long the lines like;
Quote from: 1ricca on January 14, 2013, 04:29:15 AM
Forgive me. What is High Speed Sync?
here is a good link that explains what High Speed Sync is, this should help answer your question
http://www.rpphoto.com/howto/view.asp?articleID=1026
you spend about the same amount of time as you did with your comment but instead you dont come off like an asshole but someone actually adding to the thread. :)
On my experience with some delay settings, between camera shutter and the flash trigger (custom values depending on the speed of the camera and the flash). You can made high speed sync with "regular" dlsr (1/200) at 1/500 even on 1/800.
In the paste I made some tests with an arduino based camera & flash trigger (http://www.apcc.tk/diy-projects/apcc-advanced-photo-camera-control).
Quote from: nanomad on January 14, 2013, 12:05:39 AM
High speed sync: dunno. It may require a significant re effort as I don't have any cameras that support it
Audio tweaks: in the future yes, as long as we figure out the chip inside
Kazeone,
Maybe we can be a little less hasty with the name calling. Reminding people to search google for an answer empowers them to get more than one answer to their question. I realize its helpful to provide guidance on the forum, but a simple reply with an answer is more constructive than being rude to someone that had a valid point.
Quote from: nanomad on January 14, 2013, 12:05:39 AM
High speed sync: dunno. It may require a significant re effort as I don't have any cameras that support it
Be careful with enabling features from another camera, these things are legally risky, even if you don't copy Canon code.
lol thats almost like an april fools joke
Quote from: a1ex on January 14, 2013, 08:31:33 PM
Found something cool:
[youtube*]http://www.youtube.com/watch?v=7ArI_9vmapU[/youtube]
;)
Well at least I know who to contact if we ever want to shoot a 650D trailer :p
btw, a1ex feel free to select a feature set for alpha1 (as I'm not really confident with what features needs props and what doesn't). I'm ready to put it out
I'd like to add: look soon in all theaters of the country! :P
Quote from: nanomad on January 14, 2013, 09:17:31 PM
Well at least I know who to contact if we ever want to shoot a 650D trailer :p
btw, a1ex feel free to select a feature set for alpha1 (as I'm not really confident with what features needs props and what doesn't). I'm ready to put it out
could u include HDR and timelapse mode ? becaus that functions are very important for me ! :)
Thanks Kazeone. My sentiments exactly, minus the name calling ;)
I know how to use google and I know it will produce a ton of results.
I enjoy conversing with people on these forums and I feel I usually get a more relevant answer to my question rather than fishing through an ocean of google results, which usually end up leading me to a forum somewhere else :) Let's keep this thread educational and informative.
Bump on the HDR and timelaps. Though I'm pretty sure timelapse requires changing non-volitile memory.
Also, extra ISO options! 100,160,320,640 etc. If that's been done on the other lower end cameras.
Would there be a way to make the 4 up/down/left/right buttons do the same thing in Movie Mode as they do in Photo Mode?
It would be great to have the FULL WB menu and the FULL Picture Profile menu while in Movie Mode.
While in Movie mode, you must use the Q menu quick settings. In there, the WB doesn't show the K value of each preset. In the Picture Profile settings in the Q menu, it is more difficult to go in and change the settings of each Profile and harder to read what each Profile's settings are.
As of right now, I switch back to Stills Mode to change my WB and my PP everytime. I'd much rather have the D-pad do these shortcuts than to change the focus area. Or better yet, holding +/- button and clicking them does those things in Movie Mode. Would be a little cumbersome but better than nothing. Unless there is a dead button in Movie Mode to use as the modifier key.
What are your thoughts on this? Anyone else that would like this? Has this been done in other builds?
Alex told me you were having trouble finding the Live View buffer addresses - this morning I discovered a new (easy) way for us to do this. I'm gonna push a new commit soon adding a menu option for it (with config_debugmsg enabled), but basically, run this from "run_test":
Quote
call( "lv_vram_dump" );
and look for 3 new .422 files on the root of your SD card, their filenames are the 3 LV buffer addresses :)
New to the forum, and so excited about the port to the 650d. Keep up the good work - can't wait for the alpha! I vote for focus peaking, as a few others have mentioned.
I'd like to donate - should I donate to ML in general, or to this project in particular? And how do I make a donation?
Cheers,
Alec
Hi guys, I was just wondering if there will ever be a full implementation for this on the 650D, like there is on the 600D? How long will this be?
Hi guys, I was just wondering if there will ever be a full implementation for this on the 650D, like there is on the 600D? How long will this be?
Well that is what this entire thread is about :), it is clearly being developed. I gather from reading the forum that an alpha version may be due fairly soon, but other than that I don't think anyone can give you a definitive answer except to say "when it's ready".
Quote from: a1ex on January 14, 2013, 08:31:33 PM
Found something cool:
;)
Thumbs up on the trailer, thanks for sharing.
I can't wait to use ML on the T4i/650D. Thank you all for your hard work and dedication. How does one make a donation to your cause, you great humanitarians you?
What's the status on Alpha 1? Burning with desire!!!
Will Focus Peaking and additional ISO settings be in it?
Quote from: coutts on January 15, 2013, 04:42:59 PM
Alex told me you were having trouble finding the Live View buffer addresses - this morning I discovered a new (easy) way for us to do this. I'm gonna push a new commit soon adding a menu option for it (with config_debugmsg enabled), but basically, run this from "run_test":
and look for 3 new .422 files on the root of your SD card, their filenames are the 3 LV buffer addresses :)
Thanks, looks like I got them right the first time... I still need to figure out what's wrong then
edit: maybe it's the HD buffers...
so how is it going with ML for the 650D ? :)
stable release before summer
One issue left for alpha1. I hope to sort it out today/tomorrow
awesome looking forward to it and thank you for your hard work ^_^
Quote from: nanomad on January 19, 2013, 02:53:41 AM
One issue left for alpha1. I hope to sort it out today/tomorrow
Music to our ears! You are a champion!
coolness
Great news! Looking forward to the Alpha. I've been holding off on a DSLR purchase while following this thread. The 60D is still an attractive alternative with a full ML release already available, but the faster processor and continuous video recording of the T4i is tempting. Keep up the good work!
Nanomad, keep up the good work! You're in the home stretch now! My T4i becons me, asking for me to unleash it!
all waiting on baited breath...
my sd card is waiting.
Quote from: nanomad on January 19, 2013, 02:53:41 AM
One issue left for alpha1. I hope to sort it out today/tomorrow
Reading that makes me want to dance!
Bought this camera one month after its release in sweden and ive been waiting anxiously for ML to arrive for it!
Gonna send you guys a few bucks for the great work!
This may sound dumb but where do i donate?...
They had taken the donation link down due to some...circumstances.
They recommend donating to the EFF instead.
https://www.eff.org/
Hi guys, I would like to ask nanomad what are the chances to overcome the 30minut Record Limit.
(as we know canon 650d - Digic 5 can record up to 30 minutes creating multiple files).
Thank you.
Movie restart should work. As far as overcoming the 30m limit I have no idea
Quote from: nanomad on January 21, 2013, 09:42:55 PM
Movie restart should work. As far as overcoming the 30m limit I have no idea
Sounds good! Any idea on when to release Alpha 1? :)
Quote from: 33black on January 21, 2013, 03:50:19 AM
They had taken the donation link down due to some...circumstances.
They recommend donating to the EFF instead.
https://www.eff.org/
Alright i donate a few bucks to them! Thanks for the info! :D
guys please stop asking when alpha is coming out, its actually pretty rude well Im not sure if rude is the right word for it but I have seen more dev get tired of being asked and end up just drop projects, be patient, just keep checking back, when its ready its ready and he will update the thread title and the first post, so until then be patient as the saying goes all good things comes with time. :)
Quote from: kazeone on January 22, 2013, 02:41:25 AM
guys please stop asking when alpha is coming out, its actually pretty rude, just keep checking back, when its ready its ready and he will update the thread title and the first post, so until then be patient as the saying goes all good things comes with time. :)
Exactly, If you want to be up to date with this conversation, then click notify at the top right corner of the page.
Hello guys... I'm new here, but i'm following the entire thread and i'm excited with ML in 650.. it needs a lot of new stuff, and we know canon will not present us with
I would like to post some suggestions:
I dont know which of them are possible, but lets see..
1 - continuous numbering above 9999 and independent file numbering for videos(create another file sequence for videos)
2 - hidden folders and separated folder view in player(when in a folder, u see just that folder)
3 - instant saving folder select, or better than that, add a "move to folder" within the trash button!
4 - when shooting with AEB, for manual HDR, some way to save files like: IM_xxx1, IM_xxx1-1, IM_xxx1+1 - IM_xxx1_1, IM_xxx1_2, IM_xxx1_3 or any of a kind!! Organizing large amount of files for HDR with some feat like that would be great!
5 - Insert timer remote control functions into Drive mode(improve existing ones)
and all another ones already suggested ;D
Quote from: jvalizi on January 22, 2013, 06:43:58 AM
Hello guys... I'm new here, but i'm following the entire thread and i'm excited with ML in 650.. it needs a lot of new stuff, and we know canon will not present us with
I would like to post some suggestions:
I dont know which of them are possible, but lets see..
1 - continuous numbering above 9999 and independent file numbering for videos(create another file sequence for videos)
2 - hidden folders and separated folder view in player(when in a folder, u see just that folder)
3 - instant saving folder select, or better than that, add a "move to folder" within the trash button!
4 - when shooting with AEB, for manual HDR, some way to save files like: IM_xxx1, IM_xxx1-1, IM_xxx1+1 - IM_xxx1_1, IM_xxx1_2, IM_xxx1_3 or any of a kind!! Organizing large amount of files for HDR with some feat like that would be great!
5 - Insert timer remote control functions into Drive mode(improve existing ones)
and all another ones already suggested ;D
This thread is for the port to the 650D/T4i. For the most part, it can be assumed that we will see all features available in ML 2.3 once the final release is done. The Alpha may very well have missing features, but the EOS M (which is a close cousin to the 650D) has pretty much every feature enabled now. New feature requests should be posted in that forum, as it is a different group that works on those requests.
It's actually the same group, but some feat requests are nice on other cameras too. Plus, we like to have everything organized in one place.
Feel free to open multiple feat requests if they are independent
An update on the 650D status: it turns out that the LV/HD buffers were correct from the start, so there's something else going on...:/
My idiocy is going on, that's what. I marked a const as done while it was clearly using a value taken from the EOSM port...
The issue is fixed, I'm re-arranging the flexinfo screen and then I'm done
Quote from: nanomad on January 22, 2013, 11:00:35 PM
My idiocy is going on, that's what. I marked a const as done while it was clearly using a value taken from the EOSM port...
The issue is fixed, I'm re-arranging the flexinfo screen and then I'm done
Haha It happens, Thanks for all the hard work nanomad!
This Forum clearly needs a "thank you"-Button!!!
Thank you nanomad, any chance of a build this night?
I want to start finding Bugs :D
I don't think so, the alpha builds require a custom build process (since they have autoboot disabled)
I also need to trim down the feature set so that it contains a safe, for now, subset
ok, thank you very much for keeping us updated :)
Hitting the "thank you" button for nanomad. Thank you for your hard work!
hey guys !
How long will it take from the alpha to the main version ?
THANK YOU SO MUCH FOR THE GOOD WORK ! :)
Until all the bugs are fixed and more :)
YOu can read about software release life cycle here (http://en.wikipedia.org/wiki/Software_release_life_cycle).
Stability tests in progress, should have the results back in 15 minutes
edit: looks like it was passed with flying colors this time ;)
Look forward to this, I just picked up my 650d and would love some the features that Magic Lantern has on it!
Quote from: nanomad on January 26, 2013, 11:20:30 AM
Stability tests in progress, should have the results back in 15 minutes
edit: looks like it was passed with flying colors this time ;)
Great, that's a good new! I can't wait to test it !
Thank you for all your work.
Yay! I'm so excited, you have no idea. I've been waiting for this since I bought my camera. I want to let you know that I appreciate all the hard work put in to this and would like to donate some money to the cause.
I have to say, every single posts to this dev thread is becoming a frustrating tease with all of the thank you posts :o
Heh, guess it's my turn to tease.
Realllly looking forward for this to come out soon. Once it do, I can finally have the justification to donate to ML (or an alternate donation since there seem to be some problem?) and get the alpha asap. Not going to bother you with feature request since that's another time. Considering that this would be my first ML, any features is welcome!
Kudo to all of your hard work, nanomad!
My SD card is tingling.
I assume that his latest attempt to get the code to work in the alpha made the T4i explode in his face and he's died a horrible, plastic shrapnel death. :(
No, but I don't want that to happen to YOUR camera :o
Quote from: AshleyAshes on January 27, 2013, 02:10:31 AM
I assume that his latest attempt to get the code to work in the alpha made the T4i explode in his face and he's died a horrible, plastic shrapnel death. :(
Maybe he was running his stability test on the "Don't click me!" function.
Quote from: nanomad on January 27, 2013, 11:27:04 AM
No, but I don't want that to happen to YOUR camera :o
My 50D survived this function. I wouldn'd dare try it on my T4i.
Quote from: nanomad on January 27, 2013, 11:27:04 AM
No, but I don't want that to happen to YOUR camera :o
I appreciate it, because I have some field tests I can put it through when it's ready. :)
ML is one of the first things I looked for when I got my T4i in Sept. I knew from My XTi that Canon locks so many features. Once those features where unlocked it was like I got a new camera.
I'm kind of happy having to wait for ML. It gave me time to get used to the basic feature from Canon that it came with. Now I'm ready for ML and what ever great features it unlocks.
please i have a problem. i can understand. i have my t4i and 2 memories but i test that: I try to write a update firmware to the lens 40mm canon STM. But i can. The mesaje say the disc is write protected. I hope to wait for ML to my camera but now have that problem. I ask this here and to the seller. But the seller there does not know which is the problem. Please tell my Where I can post this question inside the site. And the switch isn't the problem. the switch to lock is unlock. thanks
Quote from: elmatambre on January 27, 2013, 11:32:38 PM
please i have a problem. i can understand. i have my t4i and 2 memories but i test that: I try to write a update firmware to the lens 40mm canon STM. But i can. The mesaje say the disc is write protected. I hope to wait for ML to my camera but now have that problem. I ask this here and to the seller. But the seller there does not know which is the problem. Please tell my Where I can post this question inside the site. And the switch isn't the problem. the switch to lock is unlock. thanks
I think you are in the wrong section! Nevertheless.
Take a look on the SD cards side there is a small slider which makes the card read only.
Try that and see if it helps :)
Quote from: elmatambre on January 27, 2013, 11:32:38 PM
please i have a problem. i can understand. i have my t4i and 2 memories but i test that: I try to write a update firmware to the lens 40mm canon STM. But i can. The mesaje say the disc is write protected. I hope to wait for ML to my camera but now have that problem. I ask this here and to the seller. But the seller there does not know which is the problem. Please tell my Where I can post this question inside the site. And the switch isn't the problem. the switch to lock is unlock. thanks
Are you using a card reader? If connected to the camera via USB, the card is write protected. If you hope to use ML in the future you will need an SD card reader to put the installation files on the card.
Sorry if this reply gets anybody hope up. Just here to let you (the developers) know that i would love a magic lantern on my brand new 650D. I also have a 400D, and that kind of left me out of the ML stuff. I do a lot of macro stuff and i would love the focus stacking option.
If there is any way for me to help (sorry no coding/hacking skills) please let me know.
Looking forward to ML for 650D
Same here, blade. I just got my 650D, my first personal camera I have ever purchased. As a film student, I am counting down the seconds until I can get ML running on this bad boy and unlock its full potential. I can't wait!
Quote from: Gorilla on January 28, 2013, 10:31:10 AM
Same here, blade. I just got my 650D, my first personal camera I have ever purchased. As a film student, I am counting down the seconds until I can get ML running on this bad boy and unlock its full potential. I can't wait!
Exactly the same situation here! I just heard about ML a last week after I bought my 650D, starting my first project in march. Hoping to get a early release of ML running on my camera by then!
If there is anything I can do, donate, help, test or whatever, please let me know!
There's a developer kit available for booting your own autoexec file.
I'm doing some tests because I thought I had a stub wrong. Turns out it was correct but on the plus side we now have flicker free magic zoom and peaking
Quote from: nanomad on January 29, 2013, 12:17:51 AM
There's a developer kit available for booting your own autoexec file.
I'm doing some tests because I thought I had a stub wrong. Turns out it was correct but on the plus side we now have flicker free magic zoom and peaking
When you say "we"...
:P
I can't wait any longer ^^
I think I'll try to build it tomorrow :D
What exactly is magic zoom?
Quote from: JannF on January 29, 2013, 01:55:08 AM
I can't wait any longer ^^
I think I'll try to build it tomorrow :D
What exactly is magic zoom?
I'm willing to be patient, because the longer we have to wait, the more stable the alpha will be.
As for Magic Zoom, it allows you to see a magnified view of the image while recording video. This helps with manual focusing using only the back of the camera.
I think the program I used was called 400Plus on the Xti.
Quote from: msrobi on January 29, 2013, 02:20:26 AM
I'm willing to be patient, because the longer we have to wait, the more stable the alpha will be.
As for Magic Zoom, it allows you to see a magnified view of the image while recording video. This helps with manual focusing using only the back of the camera.
Ahh magic zoom sounds like a lifesaver. Any hope for the return of the t3i video zoom or maybe a better downsampling script to help with the moire and softness? Or is that stuff beyond the scope of ml?
In any case magic zoom will be great to have, especially for those of us without stm lenses.
There's always hope for video crop mode but it is definitely out of the alpha/beta builds
Video crop would be amazing. Its the one thing I really miss from my 600D. Super excited for this to drop. Good work!
Who gets to try the Alphas is it open to any brave souls or is it limited to Developers and Supporters? I used to bata test years ago and I'd love to try an alpha when it's ready.
Quote from: baga on January 29, 2013, 05:15:55 PM
Who gets to try the Alphas is it open to any brave souls or is it limited to Developers and Supporters? I used to bata test years ago and I'd love to try an alpha when it's ready.
As a rule, since ML is an open sourced project, all Alpha builds are made public.
In all probability, the topic for this thread will be changed and the first post will be changed once the Alpha is available.
I would love to have the timelapse mode on my 650D. Is it able to put it in the alpha ?
I'm very excited
I'm sure that what ever is able to be done ML will slowly add to future updates. Right now a basic alpha will be a great start.
So, here is the plan: I'm going to release a pre-alpha build tomorrow morning that is targeted at testers. What this means is that I'll disable prop changing but not the menu entries associated with them. Some features will be non working, maybe partially but the code should not have any side effects (just like the alpha builds)
What I would like you to do is to test every single feature and report back if it works or not for you
Once I collect this information ill disable the non working features and release the real alpha.
Let's call it a test to see how many people are actually interested in helping out the project by donating a bit of time ;)
Nanomad, its good news! I will help as many as i can!)
yeah as long as there is no possibility of harm because Im poor and cant afford another camera lol I will be more then happy to test it out and give you as much feedback as possible :)
Now you got my fingers twitching to click on download! Is it tomorrow yet? lol!
Happy to hear that!
Quote from: kazeone on January 29, 2013, 08:58:40 PM
yeah as long as there is no possibility of harm because Im poor and cant afford another camera lol I will be more then happy to test it out and give you as much feedback as possible :)
Well we can't guarantee that even with stable builds, so... ::)
I'm on board.
i will try to test it as well. can't wait until i get it...
Quote from: nanomad on January 29, 2013, 08:54:10 PM
Let's call it a test to see how many people are actually interested in helping out the project by donating a bit of time ;)
Count me in.
oh then maybe I should wait until beta then to give feedback ^^;;
I wouldn't mind testing as I've been waiting for ML on my 650D for some time.
Quote from: nanomad on January 29, 2013, 08:54:10 PM
So, here is the plan: I'm going to release a pre-alpha build tomorrow morning that is targeted at testers.
I'm in! Guessing you'll post the link on this thread, ya?
I'm so happy right now! it will be a sleepless night :O
Quote from: nanomad on January 29, 2013, 08:54:10 PM
Once I collect this information ill disable the non working features and release the real alpha.
Let's call it a test to see how many people are actually interested in helping out the project by donating a bit of time ;)
I would love to donate as much time as i can possible offer! im having alot of dead hours sometimes on my internship this entire week that i could spend testing some! Gonna keep a close watch on this topic tommorow and i speak from all of us when i say: THANKS ALOT DEVS!
We all (At least i do) appreciate what you done to the Canon film world! ;D
+1 Can't wait to test! Thanks for the great job!
Quote from: Ivarss on January 29, 2013, 10:45:01 PM
I would love to donate as much time as i can possible offer! im having alot of dead hours sometimes on my internship this entire week that i could spend testing some! Gonna keep a close watch on this topic tommorow and i speak from all of us when i say: THANKS ALOT DEVS!
We all (At least i do) appreciate what you done to the Canon film world! ;D
^this... ;)
Count me in as well!
Well heck, I'm in :)
All IN here !!!!
Looks like I've just arrived to this forum on a very nice ocasion ;D
VERY well done Nanomad, its a great deal of brain work gone into this.
Add me to the tester list too, if I may.
Many thanks
Wookie
Quote from: Wookie on January 30, 2013, 03:12:39 AM
VERY well done Nanomad, its a great deal of brain work gone into this.
Add me to the tester list too, if I may.
Many thanks
Wookie
I agree, I had put off checking here and then checked back at the right time.
add me to the list as well please, very excited.
Nanomad for President !!!!
I'm in. And thanks nanomad!
I am limited in time, and cant risk the downtime of a bricked camera, so i will skip the first wave, if i feel comfortable that it works for others i will jump in and start testing.
Looking forward to the (pre-) alpha!
I'm in as well. Keep up the excellent work!
I need a volunteer for testing the pre-alpha1 build installation. Keep in mind this may be dangerous. The first one to answer below will receive a PM from me with instructions
Me? :D
Jannf, you are a brave soul!!! thanx
Quote from: nanomad on January 30, 2013, 10:30:25 AM
I need a volunteer for testing the pre-alpha1 build installation. Keep in mind this may be dangerous. The first one to answer below will receive a PM from me with instructions
Quote from: JannF on January 30, 2013, 10:40:08 AM
Me? :D
goodluck bro :P
We have a green light.
The install procedure is not really straightforward but it should be doable by someone with a ML knowledge
WARNING: This will make both your card and your camera bootable. It should also be the only "permanent" change to your camera this build does, but I cannot guarantee you that
- Reset camera settings
- Reset custom functions
- Turn dial to M mode
- Place a spare SD in the camera
- Do a in-camera low level format
- Download the firmware dumper: 01_650d_dumper.rar (http://nanomad.magiclantern.fm/650D/Pre-alpha1-release/01_650d_dumper.rar)
- Extract it on the card (the structure is similar to traditional ML installs, just with less folders and no autoexec)
- Do a firmware update
- The camera will do some stuff, dump the firmware and then stop with a solid red light
- Turn off the camera
- Remove card and battery
- Place card in the reader
- Run EOSCard, select your card, make it bootable (check all the flags, don't touch the ML or CHDK buttons)
- Hit save a couple of times
- Download the pre-alpha1 build 02_650D.101.PreAlpha1.READTHEFORUM.zip (http://nanomad.magiclantern.fm/650D/Pre-alpha1-release/02_650D.101.PreAlpha1.READTHEFORUM.zip)
- Extract it on your card, replace files when asked (if it doesn't, you're probably doing it wrong :P)
- Put card in camera
- You know what you do ;)
Quote from: blade on January 30, 2013, 08:48:09 AM
I am limited in time, and cant risk the downtime of a bricked camera, so i will skip the first wave, if i feel comfortable that it works for others i will jump in and start testing.
Looking forward to the (pre-) alpha!
You can choose what to boot: Canon or ML.
So if ML is not performing right, or you can't use it as you would like, you can boot the camera without ML.
Quote from: loplo on January 30, 2013, 11:32:21 AM
You can choose what to boot: Canon or ML.
So if ML is not performing right, or you can't use it as you would like, you can boot the camera without ML.
You are properly right, will do the required reading and get to work
Quote from: blade on January 30, 2013, 11:37:37 AM
You are properly right, will do the required reading and get to work
Actually, no. With alpha builds the risk of bricking is higher. If you can't afford the downtime then please don't try running them.
Quote from: nanomad on January 30, 2013, 11:38:53 AM
Actually, no. With alpha builds the risk of bricking is higher. If you can't afford the downtime then please don't try running them.
I wont, but will do the reading on how it schould be done, so if there is an alpha, i will be ready to go
Any feedback? Either noone is risking the pre alpha or everybody is busy testing.
Sweet, I'm up and running, Ill start testing and documenting everything today :) Thanks for the amazing work nanomad! Other than the "dont click's" is there anything thing else we should 100% avoid?
Don't click me is actually fine to call (it justs saves a debug log)
Yup, I feel like a loser right now!
Good deal.
I'm incredibly tempted to go ahead and try this pre-alpha. I think I'll try my best to at least wait 2 or 3 days to see if there is any serious issues.
Quick question, where to testers post bug report on this pre-alpha? This thread, PM to nanomad, or another page/thread? I want to get involved and is trying to figure out how to do this.
Thank you so much for your hard work!
This thread is perfectly fine
is there any audio monitoring? cant find it..
other than that its mostly working, for now at least.. im learning it so, i havnt check all the features :p
great job nanomad! :D
Quote from: roterrion on January 30, 2013, 02:47:20 PM
is there any audio monitoring? cant find it..
No audio monitoring because we lack the details of the audio IC used in the camera
If you're still looking for volunteers, you can count me in!
Quote from: nanomad on January 30, 2013, 10:30:25 AM
I need a volunteer for testing the pre-alpha1 build installation. Keep in mind this may be dangerous. The first one to answer below will receive a PM from me with instructions
If you still looking I'm in. I'm home everyday and keep my camera right on the coffee table and use it constantly.
I've posted the instructions just after that, go on and test if you accept the risks
done, Just taken the jump. Works fine, did all the custom scripts
Done, they works fine
Played around with the HDR filming option and that works also fine.
Focus zebra striping etc works as it should. Cant find anything that does not work.
IS there anywhere any debug info that you would like to have?
Quote from: blade on January 30, 2013, 03:38:11 PM
done, Just taken the jump. Works fine, did all the custom scripts
Done, they works fine
Played around with the HDR filming option and that works also fine.
Focus zebra striping etc works as it should. Cant find anything that does not work.
IS there anywhere any debug info that you would like to have?
I second that, Still searching for something that doesn't work :/
First attempt at movie auto-restart failed ( after 29:59 everything stopped). Trying again. All other movie features seem to work.
Quote from: ProfessorX on January 30, 2013, 03:42:54 PM
I second that, Still searching for something that doesn't work :/
I hope you won't find it :)
I can't really tell if something doesn't work or if it's just me because i'm using ML for the very first time ;D
Check if HDR bracketing works. If it does, I somehow screwed up the build
FYI - I am tracking this thread closely, having my T4i for about a month, now.
Will try the ML firmware this eve and let you'all know how it goes.
Thanks for the dedication to pull this through, wish I could contribute $$ directly.
Best,
Peter
Quote from: nanomad on January 30, 2013, 04:32:43 PM
Check if HDR bracketing works. If it does, I somehow screwed up the build
for movie it does, i cant find it anywhere else ..
update:
so it should be in the shoot menu... well its not... so no screwing up
Did find something that i cant get to work...(could be me) Focus bracketing I keep getting a focus error :-(
Note: the not so happy face is the message in the camera, not me
Quote from: blade on January 30, 2013, 05:27:50 PM
Did find something that i cant get to work...(could be me) Focus bracketing I keep getting a focus error :-(
Note: the not so happy face is the message in the camera, not me
I'm getting the same thing as Blade
Shot a small HDR clip, pretty cool, worked flawlessly
Tried movie-restart 4 times, Different SD cards (16GB and 64GB). Won't restart (can only find HDR in movie menu - no HDR bracketing). First 4 tries at 0.7x rate - Now trying at 1.0X (FW default). will advise. After this I'll run it on my second T4i and see what happens.
After 1st boot up I go to upgrade firmware and let it update, next it goes to the main menu. Hello World comes up, signature=0x12aeb7b3, enableBootDisk, oops! In the top left corner in real small print "font addr bad"
What am I doing wrong? If I try using the camera it seems fine but once it powers down on it's own I find the drive light came back on or right after the sensor clean if I shut it down on my own.
I've reformat and tried about 5 times.
Where am I dropping the ball?
Correct, lens focusing requires props
About bracketing, are you sure it's not in the shoot menu under the name of Adv. bracketing? (no camera here, so I can't check, sorry)
About movie restart, can you check if the "clear overlays when recording" feature works?
Quote from: baga on January 30, 2013, 05:57:31 PM
After 1st boot up I go to upgrade firmware and let it update, next it goes to the main menu. Hello World comes up, signature=0x12aeb7b3, enableBootDisk, oops! In the top left corner in real small print "font addr bad"
What am I doing wrong? If I try using the camera it seems fine but once it powers down on it's own I find the drive light came back on or right after the sensor clean if I shut it down on my own.
I've reformat and tried about 5 times.
Where am I dropping the ball?
Post a screenshot of the content of the SD card
Quote from: baga on January 30, 2013, 05:57:31 PM
In the top left corner in real small print "font addr bad"
Where am I dropping the ball?
I did see that font addr bad too, but it did work... did you put the camera in M on the dial wheel (my error the first time)?
Quote from: nanomad on January 30, 2013, 11:17:46 AM
WARNING: This will make both your card and your camera bootable. It should also be the only "permanent" change to your camera this build does, but I cannot guarantee you that
Reading that makes me wonder what that even means!
Not home right now so cant access my camera right now and get started!
Quote from: baga on January 30, 2013, 05:57:31 PM
After 1st boot up I go to upgrade firmware and let it update, next it goes to the main menu. Hello World comes up, signature=0x12aeb7b3, enableBootDisk, oops! In the top left corner in real small print "font addr bad"
What am I doing wrong? If I try using the camera it seems fine but once it powers down on it's own I find the drive light came back on or right after the sensor clean if I shut it down on my own.
I've reformat and tried about 5 times.
Where am I dropping the ball?
I assume you did not follow this:
Run EOSCard, select your card, make it bootable (check all the flags, don't touch the ML or CHDK buttons)
Quote from: nanomad on January 30, 2013, 06:01:33 PM
Correct, lens focusing requires props
About bracketing, are you sure it's not in the shoot menu under the name of Adv. bracketing? (no camera here, so I can't check, sorry)
About movie restart, can you check if the "clear overlays when recording" feature works?
MOVIE RESTART - Yes Overlay does clear when I hit record (after turning on this setting)
Quote from: loplo on January 30, 2013, 06:44:30 PM
I assume you did not follow this:
Run EOSCard, select your card, make it bootable (check all the flags, don't touch the ML or CHDK buttons)
I thought I followed it. I use a Mac and used MacBook.
Quote from: nanomad on January 30, 2013, 06:01:33 PM
About bracketing, are you sure it's not in the shoot menu under the name of Adv. bracketing? (no camera here, so I can't check, sorry)
under advance bracketing i have:
-bracket type
-frames
-ev increment
-sequence
-2 sec delay
-iso shifting
-post scripts
With all the options there it may be the HDR you mean, but noting called HDR
Same here. Could be something different on some cameras?
(https://lh5.googleusercontent.com/-Z3sX08xaej0/UQly9QmjrcI/AAAAAAAAuQU/fvDv3ks2lRc/s908/13+-+1)
I couldn't get the screen shot to upload so I just re-did everything again and then got stupid and tried moving files around (4g card) when that didn't work. I still get the error message including the oops.
I figure this part is normal. Every time I turn the camera on/off/install batteries the firmware upgrade screen comes up and loads. If I install my none ML 32g card no bootup and looks for upgrade file.
I'm not sure what steps to take.
Quote from: blade on January 30, 2013, 07:49:17 PM
under advance bracketing i have:
-bracket type
-frames
-ev increment
-sequence
-2 sec delay
-iso shifting
-post scripts
With all the options there it may be the HDR you mean, but noting called HDR
What I meant is that it's called advanced bracketing now, but don't bother testing as it's not working in this build :P
If I ignore the message and just start using the camera it works fine except for only 15 second movie of record time and then it turns the recording off.
Lets gets this going! I'm ready to get audio monitoring, I'm not sure if anything else matters! Though it would be a bonus to have more manual features in video mode.
Quote from: nanomad on January 30, 2013, 08:51:01 PM
What I meant is that it's called advanced bracketing now, but don't bother testing as it's not working in this build :P
Thats clear then wont test it.... testing video >4GB now...
Quote from: baga on January 30, 2013, 08:53:37 PM
If I ignore the message and just start using the camera it works fine except for only 15 second movie of record time and then it turns the recording off.
Does this happen with of without the autoexec bin on the card?
edit: I'm in the chat (http://www.magiclantern.fm/forum/chat/index.php) if you want faster help
If i film above the 4GB the counter gets stuck at 0:03... however the file is split and just continues to record
Quote from: loplo on January 30, 2013, 08:37:25 PM
Same here. Could be something different on some cameras?
(https://lh5.googleusercontent.com/-Z3sX08xaej0/UQly9QmjrcI/AAAAAAAAuQU/fvDv3ks2lRc/s908/13+-+1)
That's the screen.
I know that, but did you continue with the install procedure? Or did you stop right there?
Up and running! Everything's great so far!
To whoever is having issues, what OS do you have?
Magic zoom is having issues on mine. Works when not recording. When recording, only Focus+Zrec works.
Is "Trap Focus" not working in this pre-alpha?
Ciao, Walter
Windows 8 (issue with MOVIE RESTART)
Quote from: nanomad on January 30, 2013, 09:54:00 PM
To whoever is having issues, what OS do you have?
Issues with the installation, that's what I meant :P
What happened with the chat? Keeps failing on me...
There were more than 5 users logged in, so it threw a stack overflow :P
First of all, Thanks a lot for your work nanomad! :)
I had the signature/oops issue during installation, but continued without any problem. ML autoloads during every startup. I don't have any issues with short video clips.
Issues i have seen : Canon graphics sometimes overwrites the ML menu (follow focus square). Magic zoom does not draw green lines when in focus, and splitscreen does not adjust.
I am using Win8.
- Canon graphics sometimes overwrites the ML menu: Confirmed
- Magic zoom does not draw green lines when in focus: Confirmed, looks like the focus confirmation structure has changed (the address should be correct)
Quote from: loplo on January 30, 2013, 08:37:25 PM
Same here. Could be something different on some cameras?
(https://lh5.googleusercontent.com/-Z3sX08xaej0/UQly9QmjrcI/AAAAAAAAuQU/fvDv3ks2lRc/s908/13+-+1)
Have you worked it out yet?
Please stop testing the build. Don't run the Firmware Upgrade
Quote from: nanomad on January 30, 2013, 10:51:56 PM
Please stop testing the build. Don't run the Firmware Upgrade
Major issue or compiling the real alpha or what?
ML is up and running.
Stability test runs perfect, but on screen I see some [fail] messages.
Touching the screen is the same as hitting the Q-button. That's nice.
Now checking out other functions.
Major issue, the devkit had one check missing and could potentially screw up the boot flags (like it happened to baga)
Quote from: nanomad on January 30, 2013, 11:12:16 PM
Major issue, the devkit had one check missing and could potentially screw up the boot flags (like it happened to baga)
K. Oh btw Adv. Bracketing is under my shoot menu on mine.
Also, did you catch the bit about magic zoom being a little sketch not just with the green lines? Can't pull it up during recording unless I set it to focus+zrec
It means that zoom isn't detected while recording, I'll have to disable that too (like it's on the 5D3 i think).
So, in the end, who managed to run the pre-alpha1 ?
Quote from: nanomad on January 30, 2013, 11:21:59 PM
It means that zoom isn't detected while recording, I'll have to disable that too (like it's on the 5D3 i think).
So, in the end, who managed to run the pre-alpha1 ?
No, it's working on the 5d3 during recording. Just checked. Only thing on the 5d3 is that I have my SET button to zoom and that doesn't pull up magic zoom, only the real zoom does. That's a whole other issue though... more like a feature request than anything
Quote from: nanomad on January 30, 2013, 11:21:59 PM
It means that zoom isn't detected while recording, I'll have to disable that too (like it's on the 5D3 i think).
So, in the end, who managed to run the pre-alpha1 ?
First of all, thank you Nanomad for your work :-D
I tested just before your advice :-P I got the same error of baga, then finished the procedure following your instructions. I tried only few basic things (zebras, cropmarks) with no noticeable issues.
While the ML menu is active some elements of the main UI (such histogram or exposure level) randomly pop up and down when you press the shutter button.
Notice the line top left corner. Second picture is what it will later look like a few seconds later.
1:(http://i1327.photobucket.com/albums/u667/GSSPIKE/image-1.jpg)
2:(http://i1327.photobucket.com/albums/u667/GSSPIKE/image-3.jpg)
1st time installed.
(http://i1327.photobucket.com/albums/u667/GSSPIKE/photo.jpg)
https://bitbucket.org/hudson/magic-lantern/commits/b2d815e5020637b8f925491dcc2fcc284a097672
"Hudson, we have a problem!" :o
Mhmm pre-alpha1 just runs fine on my camera.
Menu begins to flicker if exited with half pressed shutter button and SD Benchmark crashes.
If everything installed alright on mine, is the major issue with bootflags still a hazard?
Just got home from work since 10am. Did the pre-alpha already disappear? link isn't working.
Can someone sum up what's going on?
Count me in too, I have 3 t4i's two that are just sitting around right know so I'm willing to lend a hand and test on those two.
Quote from: baga on January 31, 2013, 12:11:59 AM
Notice the line top left corner. Second picture is what it will later look like a few seconds later.
1:(http://i1327.photobucket.com/albums/u667/GSSPIKE/image-1.jpg)
2:(http://i1327.photobucket.com/albums/u667/GSSPIKE/image-3.jpg)
Easy enough... Forgot to tell you that you need the ML folder from one of the nightly builds
No? Anyone? Bueller?
tell me how to install the alpha?, I can not find the manual.
Quote from: saha007 on January 31, 2013, 09:38:07 AM
tell me how to install the alpha?, I can not find the manual.
http://www.magiclantern.fm/forum/index.php?topic=3697.msg24949#msg24949
OK, but the link does not work on alpha.
They are working on a few things right now so you have to wait until they bring it back up.
Exactly, there was an issue with the old installer that could cause the camera to enter an invalid state while writing the bootflag. We got a fix but at this point I've got enough testers for a "closed" alpha1 testing before releasing it in the open
Hey guys, back after 12hrs of internet outage.
@baga, no I did not magane to do the firmware dumping as required
@nanomad, what is causing the font - ooops issue?
BTW, I've tried to boot the camera with the ML, it runs, the EV is always overlaying ML. Live view was very laggy and I did not manage to record more than 15 seconds.
I'm looking forward to see the alpha.
I don't remember what's triggering the font oops issue, but it probably has to do with a wrong memory address in the build. Anyway, seems like you have the bootflag ON on your camera so no worries.
Movie recording, on the other hand, is a strange issue I never experienced myself. Please check the following:
- You're able to record more than 15 secs without ML (use another card or disable the bootflag using EOSCard)
- You do not have FPS override enabled (check inside ML menu)
Honestly I'd like to wait for the Alpha version. I really don't want to brick my camera. Yesterday I almost bricked my phone - bad luck is after me these days.
I have one more question. Is there a way to format the card in the camera to get rid of the ML? Right now If I format the card in the camera, ML catches me.
If not, I still can format it via PC.
Yes, start the camera with SET pressed, this skips ML startup
After that do in-camera LOW level format of the card
If that fails, disable the bootflag using EOSCard then do an in-camera low level format
Thanks!
@nanomad: so should i stop testing the prealpha now and uninstall ML or can I go on testing it?
I had the same install issue like baga but everything seems to work fine.
and what did you mean with: "Easy enough... Forgot to tell you that you need the ML folder from one of the nightly builds"
should i download the newest nightly (magiclantern-v2.3.NEXT.2013Jan31.60D.550D.600D.50D.500D.5D2.1100D) and put the ML folder on my SDcard ?
I am very grateful to you for your work nanomad!
Quote from: loplo on January 31, 2013, 10:48:37 AM
Hey guys, back after 12hrs of internet outage.
@baga, no I did not magane to do the firmware dumping as required
@nanomad, what is causing the font - ooops issue?
BTW, I've tried to boot the camera with the ML, it runs, the EV is always overlaying ML. Live view was very laggy and I did not manage to record more than 15 seconds.
I'm looking forward to see the alpha.
Same thing, Before this last crash I could only record about 15 seconds.
Quote from: nanomad on January 31, 2013, 06:43:15 AM
Easy enough... Forgot to tell you that you need the ML folder from one of the nightly builds
What should I try next? I haven't looked for the file that you mentioned I was missing. I haven't re-inserted the batteries since we talked yesterday.
I was having the same issues as everyone else. Managed to get past the "oops" part of the install. Sometimes I did notice, (this has already mentioned I believe) Once I booted the camera magic lanterns features wouldn't load at all, magic lantern would load, (I could pull up the menu up the trash can) but none of the features would work. I would have to enter magic lantern's menu and then exit to get anything to come up. I assume this isn't normal operation?
I think this has been noted as well, Once I power down the camera I have to leave the sd-card in or the canon updater will prompt me to insert an sd-card with an update. I assume this is tied to the bootflag issue?
I never get the ML options to come up.
Quote from: blade on January 30, 2013, 06:30:17 PM
I did see that font addr bad too, but it did work... did you put the camera in M on the dial wheel (my error the first time)?
Yep
So people, forget whatever I said you should do (I wasn't clear enough probabably).
I would like everyone who tried the pre-alpha1 to do this test and report back:
- Remove the SD card
- Power on the camera
Does the camera boot up normally? Or is it stuck asking for a firmware update?
List of affected users so far (can't boot the camera without an SD card):
- Baga
- ProfessorX (correct?)
Yes, I'm sorry I missed that instruction :/
This is what I get. It does freeze on that screen.
(http://i1327.photobucket.com/albums/u667/GSSPIKE/photo-1.jpg)
I can boot the camera normally without the "ML SD-Card".
Quote from: breaker on January 31, 2013, 04:19:11 PM
I can boot the camera normally without the "ML SD-Card".
same here, just "no card in camera" default notification from canon
Quote from: ProfessorX on January 31, 2013, 04:03:51 PM
Yes, I'm sorry I missed that instruction :/
I can't remember, are you using a Mac too?
Quote from: baga on January 31, 2013, 04:27:21 PM
I can't remember, are you using a Mac too?
No sir, Win7 X64
If i remove the sd card the camera boots normaly win xp Here
No Problem - just reads - "No Card in Camera", but does boot.
Boots normally, only "no card in camera" notification.
Power switch set to "OFF", removed card, closed card slot cover, power switch set to "ON":
Displayed "Keine Speicherkarte" = "no card in camera" -> No problem to report from here.
Ciao, Walter
Updated this post on Page 18/ #437
I'm back to testing since my Camera seems unaffected by the bootflag trouble.
Latest edit will in BOLD
General.
Info button in menu: Some of the feature info's bring up another feature in most ut the menus.
Battery usage: Can't say for shure, but i think it uses a bit more battery... I will test! Test complete. Could not see any higher battery use with ML loaded. Tested in LV/standby with RGB histogram enabled when "Magic Off" and Zebras (2..98), Focus Peak, Spotmeter and RGB histogram enabled in ML. :)
Testing of Expo Menu.
White Balance: Not Working (Props I suppose)
ISO: Not Working (Props I suppose)
Shutter: Not Working (Props I suppose)
Aperture: Not Working (Props I suppose)
PictureStyle: Not Working (Props I suppose)
ML Auto ISO: Working
Expo. Lock: Not Working (Props I suppose)
Expo. Presets: Not working (But the function seems to work when values/props can be changed)
Exp. Override: Not Working (No 1/25s and no 1/8000s. Dont know about DOF...)
Testing of Overlay Menu.
Global Draw: Working
Zebras: Working
Focus Peak: Working
Magic Zoom: Partly working (Green Bars and splitscreen dont works - Confirmed by Nanomad in Page 14/ #349)
Cropmarks: Working
Ghost Image: Working
Spotmeter: Working
False Color: Working
Histogram: Working
Waveform: Working (but not when Magic Zoom is activated)
Vectorscope: Working (but not when Magic Zoom is activated)
Testing of Movie menu.
Bit Rate: Working (Tested only CBR. With my card (Sandisk 45MB/s) I could shoot up to 2.8x
Time Indicator: Working
Movie Logging: Working
Movie Restart: Not working (not after 29.59 minutes and not after CBR bitrate to high stop)
REC/STBY notif: Working
Movie REC key: Working
Force LiveView: Not Working (Tried with "Always" and no lens on, had to press LV button anyway...)
Shutter Lock: Not Working
FPS override: Working
FPS ramping: Not tested
HDR video: Working :)
I have tested most of the Shoot menu.
Adv.Bracketing: Not working. It takes pictures, but i can't get any exposure changes.
Intervalometer: Working
TimelapseRamping: Not tested yet.
Bulb Timer: Not working. Can't find any Bulb setting on the 650D - not working on NightPortrait.
Motion Detect: Working
Silent Picture: Maybe Working... Can take pictures in every mode and the pictures get stored on SD, but YUV422 Convertor fails to open them (Unknown image size: 1226880)
Mirror Lockup: Partly Working. Don't think Handheld was working as the picture was taken instantly even with 1 sec delay.
Flash tweeks: Not tested yet.
I will update this post as my test continues... I'll post a new post when updating the testing.
If there is anything you'ld like me to try? I'll be leaving to pick up my grandson. I always take my laptop I'll be taking my camera also.
So if you do could you PM instructions like format, macboot, files etc.
Quote from: loplo on January 31, 2013, 10:48:37 AM
Hey guys, back after 12hrs of internet outage.
@baga, no I did not magane to do the firmware dumping as required
@nanomad, what is causing the font - ooops issue?
BTW, I've tried to boot the camera with the ML, it runs, the EV is always overlaying ML. Live view was very laggy and I did not manage to record more than 15 seconds.
I'm looking forward to see the alpha.
Were you able to record longer before havibg ML on the SD card?
Also remove the card from the camera and check what Class your SD card is! To record HD fot longer periods you should have an Class 10 SD card!
Hope that i van be as much assistance as possible even without the Pre-Alpha1! :)
hey Guys !
sorry I cant test the pre-alpha !
I'm a student and i bought the camera with all the money i saved !! sorry !
Quote from: Ivarss on January 31, 2013, 08:11:26 PM
Were you able to record longer before havibg ML on the SD card?
Also remove the card from the camera and check what Class your SD card is! To record HD fot longer periods you should have an Class 10 SD card!
Hope that i van be as much assistance as possible even without the Pre-Alpha1! :)
Yes I was able to shoot longer videos without ML.
Card is class 10 sandisk extreme with 45MBs. This shouldn't be a problem.
I assume video recording is still fine without ML?
Geez, I guess I really dodged a bullet. My install went perfect and is still working fantastically. Already a more fleshed out ML than my 5dMkIII Alpha in most ways. No errors or oops's anywhere.
I used Win7 Ultimate (custom compiled version though)
Sandisk Extreme III 8GB (my crappiest card)
Followed directions explicitly
I feel extra lucky because I would have used Mac OS X 10.8.2 on any other occasion but they were all in use and I used my dinky little Win7 laptop to do this install for once.
edit: I will post a detailed list of what's working and not by later tonight or tomorrow if I'm too busy.
Hey nanomad !
I'm new here and I would like first to thank you for everything you did do get a ML port for the 650D.
Here are my review of the pre-Alpha version :
I have got the same issues but the main things works pretty well (I love HDR Video :) )
There is still a little bug (but very easily fixable) : When I rotate the screen, it gets mirrored (The writings are backwards !)
Here is an illustration of what I mean :
(http://i48.tinypic.com/2qusyeq.jpg)
Keep up your good work !
ThibaultAnd.
Quote from: nanomad on January 31, 2013, 10:11:38 PM
I assume video recording is still fine without ML?
Yes indeed. I just filmed the unboxing of my new Nexus 4.
There is still a little bug (but very easily fixable) : When I rotate the screen, it gets mirrored (The writings are backwards !)
ThibaultAnd.
[/quote]
I can confirm this bug, same here
Thanks for the feedback everyone, and sorry for the troubles caused to our two fellow testers :-[
I'll see if I can get a fix out ASAP (not today, probably during the weekend)
What will be the next step? A closed pre alpha, or another semi open per alpha? Or is it alpha time already. Just wondering at what step of the development we are now. And how I can participate.
Getting pretty excited. When do you think the next release might be?
THanks for all your hard work.
Once we can ensure a safe boot
Quote from: nanomad on February 01, 2013, 09:27:14 AM
Thanks for the feedback everyone, and sorry for the troubles caused to our two fellow testers :-[
I'll see if I can get a fix out ASAP (not today, probably during the weekend)
No problem, these things happen from time to time. My camera is still very functional just married to the sdcard ;)
Quote from: nanomad on February 01, 2013, 09:27:14 AM
Thanks for the feedback everyone, and sorry for the troubles caused to our two fellow testers :-[
I'll see if I can get a fix out ASAP (not today, probably during the weekend)
Thanks, I'm lost without my camera ready to shoot on the coffee table. lol
thanks nanomad on hard work!
one question: will it be possible to set lower RAW resolution on 650D with ML? (e.g. like on stock Mart II...)
Quote from: nanomad on February 01, 2013, 09:27:14 AM
Thanks for the feedback everyone, and sorry for the troubles caused to our two fellow testers :-[
I'll see if I can get a fix out ASAP (not today, probably during the weekend)
I'm already happy with the limited version of this pre-alpha release.
No issues on my side.
Take your time.
The mirrored text only appears when the screen is flipped to the max. A little turn in both directions and the screen is correct again.
Quote from: kovacm on February 01, 2013, 06:25:48 PM
thanks nanomad on hard work!
one question: will it be possible to set lower RAW resolution on 650D with ML? (e.g. like on stock Mart II...)
This is known for causing bricked cameras.. So no
Still any chance of Kelvin WB in any of the alphas?
I am just impressed by the high bitrate modes, I recorded 30 minutes with 2,5x bitrate and it splitted the movies in 4GB parts and erverything is just working fine.
EDIT: Found a bug, sometimes the play feature hangs, so you can't switch photos, you have to reenter the play mode to make switching working again.
Maaaaaaan. Part of me is kiiiiiinda glad I missed out on the pre-alpha so my camera isn't messed up.
However, I'm insanely excited just to get my hands on a working version of ML.
Such a long wait....a long, long wait.
The upside down mode is working fine in my debug build which means it somehow relies on property change. Good to know
i've never use ML before, so i dont know how exactly each feature works, but i think there's something not right in fps override. the outcome video have a bad image. i tried to record at 0.25 speed, it works, the timelapsing, but the image.. it makes some sort of vertical lines.. however the intervalometer makes a great timelapse! :D :D :D i just dont know how to integrate it with the silent shooting feature, cos i really want to save shutter :P
let me give you the screenshot of fps override x0.25
[spoiler](http://i47.tinypic.com/fw0y9c.jpg)[/spoiler]
i also experiencing crashes while doing some fps override tests. and maybe some random(i dont really sure why it crash) errors.
i'll give you the logs.
CRASH00.LOG
[spoiler]ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan30.650D101
Mercurial changeset : 9d92bca2f850+ (unified) tip
Built on 2013-01-30 09:02:24 by
[email protected].
Free Memory : 254K + 3546K
[/spoiler]
CRASH01.LOG
[spoiler]ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan30.650D101
Mercurial changeset : 9d92bca2f850+ (unified) tip
Built on 2013-01-30 09:02:24 by
[email protected].
Free Memory : 254K + 3547K
[/spoiler]
CRASH02.LOG (timelapse fps override)
[spoiler]ASSERT: 0
at Graphics.c:3580, task CtrlSrv
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan30.650D101
Mercurial changeset : 9d92bca2f850+ (unified) tip
Built on 2013-01-30 09:02:24 by
[email protected].
Free Memory : 254K + 3589K
[/spoiler]
that's all crashes log i had from the first day you release the pre alpha. hope it helps something. :P
but overall, this is a great pre-alpha! keep up the good work! :D
Whats the status Nanomad? ::)
Any chance of a new release this weekend?
Quoteone question: will it be possible to set lower RAW resolution on 650D with ML? (e.g. like on stock Mart II...)
It would probably work but one of them is hard to decode, the other has a purple cast and won't decode. I tested on 600d and this feature is meh an plays havoc on your worflow as lightroom and all won't import even the working ones.
Quote from: nanomad on February 01, 2013, 09:27:14 AM
Thanks for the feedback everyone, and sorry for the troubles caused to our two fellow testers :-[
I'll see if I can get a fix out ASAP (not today, probably during the weekend)
Cameras fixed,
Good job alex!
Thanks for the feedback, I really apprecciate it :D
I'll strike out what requires props and it's working fine in my development builds
Quote from: breaker on January 31, 2013, 07:57:21 PM
General.
Info button in menu: Some of the feature info's bring up another feature in most ut the menus.
Testing of Movie menu.
Movie Restart: Not working (not after 29.59 minutes and not after CBR bitrate to high stop)
Force LiveView: Not Working Fixed
Shutter Lock: Not Working
FPS ramping: Not tested
Adv.Bracketing: Not working. It takes pictures, but i can't get any exposure changes.
TimelapseRamping: Not working.
Bulb Timer: Not working. Can't find any Bulb setting on the 650D Working, read the manual :P Bulb is in M mode, decrease shutter speed until you get there
Mirror Lockup: Partly Working. Should be fixed
Quote from: nanomad on February 03, 2013, 10:16:37 PM
Cameras fixed
Good job alex!
Great job alex and nanomad and every one else that worked on it.
Quote from: baga on February 03, 2013, 10:27:05 PM
Great job alex and nanomad and every one else that worked on it.
Yay, My Camera is back to 100% as well! Thanks guys!
Thats wonderful to hear. Enjoy your lantern! Lets hope the other camera can join in relatively fast. Great job !
Quote from: ProfessorX on February 03, 2013, 10:39:40 PM
Yay, My Camera is back to 100% as well! Thanks guys!
Great!
Status update (since we are on a new page)
I'll strike out what's working (no comment means it requires prop_request_change)
Quote from: breaker on January 31, 2013, 07:57:21 PM
General.
Info button in menu: Some of the feature info's bring up another feature in most ut the menus.
Testing of Movie menu.
Movie Restart: Not working (not after 29.59 minutes and not after CBR bitrate to high stop)
Force LiveView: Not Working Fixed
Shutter Lock: Not Working
FPS ramping: Not tested
Adv.Bracketing: Not working. It takes pictures, but i can't get any exposure changes.
TimelapseRamping: Not working.
Bulb Timer: Not working. Can't find any Bulb setting on the 650D Working, read the manual :P Bulb is in M mode, decrease shutter speed until you get there
Mirror Lockup: Partly Working. Should be fixed
Quote from: nanomad on February 04, 2013, 12:01:13 AM
Status update (since we are on a new page)
I'll strike out what's working (no comment means it requires prop_request_change)
Sorry, now I am slightly confused (better than being slightly mad I suppose). So you have crossed out the things that
are working, is that right? So for example, Shutter Lock is now working?
Thanks for all your hard work. I hope you are allowing yourself time off to eat, sleep and for the performance of normal bodily functions?
Exactly
Features requiring prop changes are and will be broken in alpha 1 but work fine if you compile ml by yourself
So does timelapse work straight away or does it require tweaking?
Really the main reason I wanted ML!
It will work but not in the first alpha
Hi All,
I'm new here but have been following the discussions and tests on the 650D port over the past couple of days. Got a 650D recently and I look forward to joining the ML users family. Just wanted to say thank you to all of you working on this and testing it. If you need any more testers or there's anything I can do to help, let me know.
Quote from: nanomad on February 04, 2013, 08:43:41 AM
It will work but not in the first alpha
Cheers for the response Nanomad :) I look forward to using the feature :D
I have updated my test in page 16/ #396. Latest changes in bold.
@nanomad is it OK that i update original post, or should i post it as a new post?
My progress is not impressive but i'm getting familiar with ML as i'm testing. My only comparison is the alpha for 7d ;)
And nanomad, reading camera manual is so boring. Canon should have used the info button just like you do in ML - but i suppose they are afraid to get sued my you then.;D
It's better to start a new post, makes it easy to follow.
Anyway:
- 99.9% of the expo stuff relies on prop changes
- Overlay should work, except for what you noticed
OK, here is my testing progress. Latest edit is in BOLD
General.
Info button in menu: Some of the feature info's bring up another feature in most ut the menus.
Battery usage: Can't say for shure, but i think it uses a bit more battery... I will test! Test complete. Could not see any higher battery use with ML loaded. Tested in LV/standby with RGB histogram enabled when "Magic Off" and Zebras (2..98), Focus Peak, Spotmeter and RGB histogram enabled in ML. :)
Testing of Expo Menu.
White Balance: Not Working (Needs Prop change)
ISO: Not Working (Needs Prop change)
Shutter: Not Working (Needs Prop change)
Aperture: Not Working (Needs Prop change)
PictureStyle: Not Working (Needs Prop change)
ML Auto ISO: Working
Expo. Lock: Not Working (Needs Prop change)
Expo. Presets: Not working (But the function seems to work when values/props can be changed)
Exp. Override: Not Working (No 1/25s and no 1/8000s. Dont know about DOF...)
Testing of Overlay Menu.
Global Draw: Working
Zebras: Working
Focus Peak: Working
Magic Zoom: Partly working (Green Bars and splitscreen dont works - Confirmed by Nanomad in Page 14/ #349)
Cropmarks: Working
Ghost Image: Working
Spotmeter: Working
False Color: Working
Histogram: Working
Waveform: Working (but not when Magic Zoom is activated)
Vectorscope: Working (but not when Magic Zoom is activated)
Testing of Movie menu.
Bit Rate: Working (Tested only CBR. With my card (Sandisk 45MB/s) I could shoot up to 2.8x
Time Indicator: Working
Movie Logging: Working
Movie Restart: Not working (not after 29.59 minutes and not after CBR bitrate to high stop)
REC/STBY notif: Working
Movie REC key: Working
Force LiveView: Not Working (Tried with "Always" and no lens on, had to press LV button anyway...)
Shutter Lock: Not Working
FPS override: Working
FPS ramping: Not tested
HDR video: Working :)
I have tested most of the Shoot menu.
Adv.Bracketing: Not working. It takes pictures, but i can't get any exposure changes.
Intervalometer: Working
TimelapseRamping: Not tested yet.
Bulb Timer: Not working. Can't find any Bulb setting on the 650D - not working on NightPortrait.
Motion Detect: Working
Silent Picture: Maybe Working... Can take pictures in every mode and the pictures get stored on SD, but YUV422 Convertor fails to open them (Unknown image size: 1226880)
Mirror Lockup: Partly Working. Don't think Handheld was working as the picture was taken instantly even with 1 sec delay.
Flash tweeks: Not tested yet.
Quote from: breaker on February 04, 2013, 10:35:24 PM
OK, here is my testing progress. Latest edit is in BOLD
Bulb Timer: Not working. Can't find any Bulb setting on the 650D - not working on NightPortrait.
To find bulb on 650D, just keep scrolling shutter speed in M or Tv mode past 30 seconds and the next setting is
B for Bulb.
Quote from: steve271 on February 04, 2013, 11:13:42 PM
To find bulb on 650D, just keep scrolling shutter speed in M or Tv mode past 30 seconds and the next setting is B for Bulb.
Thanks Steve. nanomad also commented that when this was initial posted. No need to read the manual when i follow this forum ;)
My testing continues... :)
Focus Menu
Nothing is working. Suppose it all relies on prop?
Display Menu
LV brightness: Working
LV contrast: Working
LV saturation: Working
LV display gain: Working
Color scheme: Working
Clear overlays: Working
Advanced settings: Partly Working (Could not see any difference on Force HDMI-VGA. Not UniWB ither, if I use it correct...?)
When testing HDMI Out the focus peaking didn't work. The lower half of the screen where showing some random orange noise pixels.
Focus relies on props too ;)
I'll check uniWB and the HDMI peaking (which is troublesome as usual)
Quote from: nanomad on February 05, 2013, 08:45:38 PM
Focus relies on props too ;)
I'll check uniWB and the HDMI peaking (which is troublesome as usual)
When do you think you will be releasing another build Nanomad? I am dying to get my hands on Intervalometer feature.
Cheers Allen
Quote from: beej on February 06, 2013, 02:33:56 AM
Just a little polite notice for everyone asking "when will XXX be done..." the answer is mostly "don't know" or "when it's done".
The ML team work on things in their spare time, so development has to fit in around what those guys are doing - not only that, but the nature of development, especially the kind of reverse-engineering that goes on in the case of something like ML, is unpredictable. A single issue might be fixed in five minutes, or it may take six months to solve.
Chasing the devs for ideas about timescales, feature implementations and so on is a little pushy. They will get to it in their own time and announce what they are working on and so on here. So feel free to ask about features, the progress of things and so on, but the "when" question only really serves to slightly irritate devs.
+1
build I use is the build you get. if something isn't working for you, its probably not working for me and an easy fix would be done already.
More of my testing results... :)
PREFS MENU
Image review settings: Working (but can't say if 422 is working since i suppose there is something wrong with the .422 files taken with Silent Pictures)
LiveView zoom settings: Not working
Focus box settings
Speed: Not working
Snap points: Not working (what is the CENTER key of the 650D, SET?)
Misc key settings: Not working
Warning for bad settings:
Mode warning: Working (but in creative modes it's no text on screen, only blinking red light)
Quality warning: Working
ALO warning: Not working (Warning even if my ALO is off (Same fault on my 7D Alpha2!))
Powersave in LiveView: Not working
Config file... : Working
LV display presets: Working
Crop Factor Display: Working
When i played around with Focus box settings my camera got unrespondable, but the LV with overlays seemed to be fine. Even if I turned off the camera the LV stayed on. Had to remove battery...
Quote from: 1% on February 06, 2013, 07:48:41 PM
+1
build I use is the build you get. if something isn't working for you, its probably not working for me and an easy fix would be done already.
Well sometimes the fix is so obvious we overlook it :-X
As I said earlier the pre alpha was more like a social experiment than a regular release. The results, sadly, are exactly what I was expecting
Well, at least we people like breaker that help with testing :D
Thank you nanomad. That's the least I can do when I see all the time you and the rest of the team are using on making our cameras way better :)
I really like the work that have been done with the menu layout - and I see that we can expect an even more polished UI in the future.
Hey all pre-alpha downloaders; What's your experience so far? What have you been using and what have you experienced?
on magic zoom feature, how to move the focus box?
well i dont have any problem moving the focus with my 40mm STM lens since its a full time manual focus, in AF mode i could still play the focus ring and also i could move the focus box with touch screen, even drag the focus box.
but if i use my other lens, MF mode would not allow me to move the focus box with touch screen, i cant find the control to move it via buttons as well. AF mode on my other lens would not allow me to play with the focus ring.
Breaker and Nanomad
I am live and testing, just struggling with a format to give feedback. I was looking for a structured approach, so I will reuse breakers posts.
I have started with the prefs menu.. and added my findings... I have done some user testing, just stability and in general i have no real live hiccups. I will revisit and test your other posts if i have the time.
PREFS MENU
Image review settings: time laps : working
Exposure adjust : working
422 preview: ( no files found ) have not played around with those settings so seems to work but not fully tested
exposure fusion : working
compare images : working
Image review: working
Quick zoom:
on (fast) : I see no difference with off ???
singel press 100%: working
full zoom on af: Not working ( or all my AF are perfect centred)
Quick erase : working
Live view zoom settings:
5x : off not working (no zoom at all)
10x : off not working (no zoom at all)
Rest (3 options) do not work as far as i can see
Focus box settings
Speed: Not working
Snap points: Not working (what is the CENTER key of the 650D, SET?) I dont know either...
Misc key settings: Not working
Warning for bad settings:
Mode warning: Working (but in creative modes it's no text on screen, only blinking red light) Confirmed, and if i go back with the scroll weel, the text does not come back, only after selecting M again.
Quality warning: Working
ALO warning: Not working (Warning even if my ALO is off (Same fault on my 7D Alpha2!)) What is ALO?? have to look it up, so not tested
Powersave in LiveView: Not working
Config file... : Working
LV display presets: Working
Crop Factor Display: Working [i]I do not see a difference maybe i do not understand it or is not working for me have to look into it[/i] confirmed
I will keep you posted on further progress
Focus Menu
Nothing is working. But relies on props... Nanomad, can you explane props a bit for me? I cant figure out what it means
Display Menu
LV brightness: Working
LV contrast: Working
LV saturation: Working
LV display gain: Working
Color scheme: Working
Clear overlays: Working
Advanced settings:
Screen layout: 3:2 Working
16:10 (no hdmi so not tested)
16:9 (no hdmi so not tested)
bottom 3:2 : working
botom 16:9 : working ( aldo i see no difference with 3:2) (ges it for external display)
Image postion: working
Upside down: working
Force HDMI : not tested
Uniwb : Not clear to me what it should do,... so no results visible for me....
http://magiclantern.wikia.com/wiki/Properties ;)
Again i have copy pasted the breakes stuff. If i found the same result i left the text unchanged. Otherwise commented in bold
Expo Menu.
White Balance: Not Working (Needs Prop change)
ISO: Not Working (Needs Prop change) freezes my controles for 10 sec, then resumes, but not working
Shutter: Not Working (Needs Prop change)
Aperture: Not Working (Needs Prop change)
PictureStyle: Not Working (Needs Prop change)
rec pic style is says do not touch... so i did not
ML Auto ISO: Working [b]still figuring out how it shoudl be used, but it seems to work[/b] not working
Expo. Lock: Not Working (Needs Prop change)
Expo. Presets: Not working (But the function seems to work when values/props can be changed)
Exp. Override: Not Working (No 1/25s and no 1/8000s. Dont know about DOF...) Not tested, not sure how to use
Testing of Overlay Menu.
Global Draw: Working
Zebras: Working
Focus Peak: Working AND LOVING IT!!!!
Magic Zoom: Partly working (Green Bars and splitscreen dont works - Confirmed by Nanomad in Page 14/ #349)
Cropmarks: Working
Ghost Image: Working
Spotmeter: Working
False Color: Working
Histogram: Working
Waveform: Working (but not when Magic Zoom is activated)
Vectorscope: Working (but not when Magic Zoom is activated)
To do: ( but most likely not today :-))
Movie menu.
Shoot menu.
Quote from: nanomad on February 07, 2013, 12:05:04 PM
http://magiclantern.wikia.com/wiki/Properties ;)
Thanx, it means a lot of work, and is way beyond my skills...
ML auto ISO can't be working, it needs prop change.
Quote from: a1ex on February 07, 2013, 12:24:49 PM
ML auto ISO can't be working, it needs prop change.
i misinterpreted how it should work, so yes you are correct it does not work...
Another new 650D user looking forward to the release of Magic Lantern on this camera... just got a new manual focus Nikkor 1.2 lens so peaking display is going to be essential! Many thanks to all your guys efforts... :-*
I am also a new 650D user, just a slight upgrade from my old 1000D. Can't wait for ML to be completed so I can use the Advanced Bracketing feature. Thanks for all of your hard work!!
I am so exited about this, you guys are amazing. im going through the forum reading about this and im jumping of excitement lol. i just upgraded to my t4i from a t1i so this is great news.
I GOT IT WORKING. I'M THICK HEADED. I wasn't going to give up trying 8)
Quote from: a1ex on February 07, 2013, 12:24:49 PM
ML auto ISO can't be working, it needs prop change.
I thought it worked. Here is how i tested it:
In movie mode/AV, set the Canon ISO to 100. In ML menu set Exp override to ON. Turn the ML ISO to 100. Turn the ML auto ISO on: Now the iso rises in steps up to 1600, but the AV Shutter and Aperture sustains unchanged. The LV is now brighter, and if you shoot a movie, that will also be that bright too.
BUT the ISO only rises. Not even when i point the lens directly to bright light it goes down...
Now i see a short message on the screen when i turn on the camera with theese settings: "!!! Auto Exposure !!! Set Movie Exposure -> Manual in Canon Menu". So I suppose Canon exposure is working in the background... :-[
Glad to see more testers here, blade! :D Good to see that you double check my testings - maybe other combination of settings can bring other results. I'm also a bit confused of what props does... :o
Quote from: breaker on February 07, 2013, 07:58:30 PM
I thought it worked. Here is how i tested it:
In movie mode/AV, set the Canon ISO to 100. In ML menu set Exp override to ON. Turn the ML ISO to 100. Turn the ML auto ISO on: Now the iso rises in steps up to 1600, but the AV Shutter and Aperture sustains unchanged. The LV is now brighter, and if you shoot a movie, that will also be that bright too.
BUT the ISO only rises. Not even when i point the lens directly to bright light it goes down...
Now i see a short message on the screen when i turn on the camera with theese settings: "!!! Auto Exposure !!! Set Movie Exposure -> Manual in Canon Menu". So I suppose Canon exposure is working in the background... :-[
Glad to see more testers here, blade! :D Good to see that you double check my testings - maybe other combination of settings can bring other results. I'm also a bit confused of what props does... :o
I was just going to ask about the ISO. I couldn't get it to change in ML menu, works only on the camera's menu.
baga, In live view, If you turn on "Exp. override" to ON (bottom of Expo Menu) the ISO is adjustable in ML menu. But if you take a picture you will see that your ISO was not used. Canon's ISO was used. Think this will work when props is enabled.
nanomad, Now i can reproduce camera freeze! Exp. Override: ON. ML Auto ISO: ON. Turn off camera. Turn on camera (shoot mode). LV on. Press trash (ML munu). The menu doesn't appear, but the picture and overlay is live. No other buttons respond ither. When I turn off camera the LV remains on ...Removed battery...
I have reproduced it 5 times, but it's mostly OK. With these settings the CPU is at 99-100%...
Quote from: breaker on February 07, 2013, 08:42:58 PM
baga, In live view, If you turn on "Exp. override" to ON (bottom of Expo Menu) the ISO is adjustable in ML menu. But if you take a picture you will see that your ISO was not used. Canon's ISO was used. Think this will work when props is enabled.
nanomad, Now i can reproduce camera freeze! Exp. Override: ON. ML Auto ISO: ON. Turn off camera. Turn on camera (shoot mode). LV on. Press trash (ML munu). The menu doesn't appear, but the picture and overlay is live. No other buttons respond ither. When I turn off camera the LV remains on ...Removed battery...
I have reproduced it 5 times, but it's mostly OK. With these settings the CPU is at 99-100%...
That did it thanks!
Is the shutter count a true number right from it's first shot taken?
Quote from: baga on February 07, 2013, 08:55:44 PM
Is the shutter count a true number right from it's first shot taken?
To me it looks so. I also have an old 7D, and it seems to fit the picture taken + liveview actuations.
Unless we got it wrong, it should be correct (it counts shots + LV switches)
hello
i am new on ML ans i would like hep you in create the Alpha on 650D or even create a french version because i am french
Thanks after I thought about it the number of shots was right.
Quote from: breaker on February 07, 2013, 07:58:30 PM
I thought it worked. Here is how i tested it:
In movie mode/AV, set the Canon ISO to 100. In ML menu..................
I will retest your settings the next time i test... The explanation Nanomad posted on props is a nice read,... check it out!
Quote from: blade on February 08, 2013, 11:45:46 AM
I will retest your settings the next time i test... The explanation Nanomad posted on props is a nice read,... check it out!
Where is Nanomad's post on props?
thanks
Bob
Post # 451
http://magiclantern.wikia.com/wiki/Properties (http://magiclantern.wikia.com/wiki/Properties)
Quote from: blade on February 08, 2013, 03:12:18 PM
Post # 451
http://magiclantern.wikia.com/wiki/Properties (http://magiclantern.wikia.com/wiki/Properties)
Thanks blade
Quote from: breaker on February 07, 2013, 07:58:30 PM
I thought it worked. Here is how i tested it:
In movie mode/AV, set the Canon ISO to 100. In ML menu set Exp override to ON. Turn the ML ISO to 100. Turn ........
Now i see a short message on the screen when i turn on the camera with theese settings: "!!! Auto Exposure !!! Set Movie Exposure -> Manual in Canon Menu". So I suppose Canon exposure is working in the background... :-[
in movie mode/AV, canon iso is not aviable. If i set to M then select iso 100 and swith back to /av i do sometimes get the ....!!! Auto Exposure !!! Set Movie Exposur... message. So its confirmed not working right?
Shot some hdr movie 25 (1080)and 50 (720)fps and processed in final cut pro x using the http://alex4d.wordpress.com/2012/01/03/ml-u-hdr-compose-fcpx-plug-in/ (http://alex4d.wordpress.com/2012/01/03/ml-u-hdr-compose-fcpx-plug-in/) alex4d plug in. Working
Give us a link with the video. Let's see what you did.
In is à clip of my wife watching tv.... Just à test shot, so no i Will not post it online... Sorry
Got it. I thought you tested it on something else.
Quote from: nanomad on January 30, 2013, 11:17:46 AM
We have a green light.
The install procedure is not really straightforward but it should be doable by someone with a ML knowledge
WARNING: This will make both your card and your camera bootable. It should also be the only "permanent" change to your camera this build does, but I cannot guarantee you that
- Reset camera settings
- Reset custom functions
- Turn dial to M mode
- Place a spare SD in the camera
- Do a in-camera low level format
- Download the firmware dumper: 01_650d_dumper.rar (http://nanomad.magiclantern.fm/650D/Pre-alpha1-release/01_650d_dumper.rar)
- Extract it on the card (the structure is similar to traditional ML installs, just with less folders and no autoexec)
- Do a firmware update
- The camera will do some stuff, dump the firmware and then stop with a solid red light
- Turn off the camera
- Remove card and battery
- Place card in the reader
- Run EOSCard, select your card, make it bootable (check all the flags, don't touch the ML or CHDK buttons)
- Hit save a couple of times
- Download the pre-alpha1 build 02_650D.101.PreAlpha1.READTHEFORUM.zip (http://nanomad.magiclantern.fm/650D/Pre-alpha1-release/02_650D.101.PreAlpha1.READTHEFORUM.zip)
- Extract it on your card, replace files when asked (if it doesn't, you're probably doing it wrong :P)
- Put card in camera
- You know what you do ;)
Do I have to follow every step here to put ML on a second card. ML is running ok on my 4gb card but I really want it on my 32gb card.
Quote from: blade on February 07, 2013, 10:56:37 AM
PREFS MENU
Image review settings: time laps : working
Exposure adjust : working
422 preview: ( no files found ) have not played around with those settings so seems to work but not fully tested Tested and the 422 file is present but i get an error : cannot preview this picture
exposure fusion : working
compare images : working
Devs, question..... the debug menu...
Stability test
benchmarks
show tasks
etc...
Is there anything useful for me to run, and if yes what would you like me to report, I have notices some log files on my SD card....
Quote from: baga on February 08, 2013, 09:25:18 PM
Do I have to follow every step here to put ML on a second card. ML is running ok on my 4gb card but I really want it on my 32gb card.
You have to do at least 4, 5, 11, 12, 13, 14, 15, 16, 17, 18.
In my opinion, there's no need to flash the firmware again.
Quote from: loplo on February 08, 2013, 09:51:23 PM
You have to do at least 4, 5, 11, 12, 13, 14, 15, 16, 17, 18.
In my opinion, there's no need to flash the firmware again.
Thanks I'll give it a try later.
Quote from: blade on February 07, 2013, 10:56:37 AM
Breaker and Nanomad
I am live and testing, just struggling with a format to give feedback. I was looking for a structured approach, so I will reuse breakers posts.
I have started with the prefs menu.. and added my findings... I have done some user testing, just stability and in general i have no real live hiccups. I will revisit and test your other posts if i have the time.
PREFS MENU
Image review settings:
Quick zoom:
on (fast) : I see no difference with off ??? Working here
full zoom on af: Not working ( or all my AF are perfect centred) Working here (it zooms on the currently selected AF point
Live view zoom settings: Working, requires props Couldn't test zoom on focus ring, one feat was broken due a to a wrong button code
Focus box settings: Working, requires props
Misc key settings: Not working Sticky DOF is ok, sticky HS is broken
Warning for bad settings:
ALO warning: Not working (Warning even if my ALO is off (Same fault on my 7D Alpha2!))
Powersave in LiveView: Not working Working
Also fixed HS to exit ML Menu
anything new ?
again THANK YOU for testing and doing such a great job !
Not really.. Just some minor bug fixes here and there
Hello, I'm having a little bit of trouble testing the pre-alpha. I can dump the firmware successfully but when I put
'magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip' onto my SD Card and try to make the card bootable EOScard just gives me "ZIP format." and my camera gives me the bootdisk error and a smiley face.
AS I said, don't test the pre-alpha anymore...it's not safe...
What error are you talking about? can you upload a screenshot?
http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip
I assumed the 'bootfix' meant that it was safe, but okay. I guess I should just wait for the next version.
(http://img266.imageshack.us/img266/1592/img7890ao.jpg)
when a new testable version for 650d ? ::) i am so exitied to use ML
Quote from: beej on February 06, 2013, 02:33:56 AM
Just a little polite notice for everyone asking "when will XXX be done..." the answer is mostly "don't know" or "when it's done".
The ML team work on things in their spare time, so development has to fit in around what those guys are doing - not only that, but the nature of development, especially the kind of reverse-engineering that goes on in the case of something like ML, is unpredictable. A single issue might be fixed in five minutes, or it may take six months to solve.
Chasing the devs for ideas about timescales, feature implementations and so on is a little pushy. They will get to it in their own time and announce what they are working on and so on here. So feel free to ask about features, the progress of things and so on, but the "when" question only really serves to slightly irritate devs.
So... from now on, everybody asking "when" will get a nice red ban from me ;)
@Alex: ;D
Hey everybody! first post, just wanted to show my excitment for the process of this. Actually I bought recently a 650D and like few days later I learnt about ML. Looking forward to it and thanks to everyone participating on it!
Quote from: nanomad on February 09, 2013, 03:38:17 PM
AS I said, don't test the pre-alpha anymore...it's not safe...
What error are you talking about? can you upload a screenshot?
Uhm wait, but it's safe to keep it installed, or did I miss something?
As long as you don't run the firmware upgrade
Just a question, what xactly is the Firmware Update doing?
As I understodd, it just dumps the Firmware, but what is the Firmware used for?
I am just trying to understand this stuff, maybe I will begin to learn developing if time allows it :D
The dump is simply a safety backup. The real thing the updater does is enabling the camera boot flag. But it didn't all the mandatory sanity checks first so it could leave the camera in an invalid state
The checks in which mode it is or if LiveView is on eg.?
Yep
I just want to give a round of applauds to all who are diligently working on this project around their normal daily living. I am thrilled by the progress thus far and am excited for alpha testing, as I am anxious to get this on my camera and start testing and playing with it. again thank you nanomad for all your hard work and effort. I am sure you through your tiresome RnD you are as thrilled as the rest of us with this project.
Much respect and appreciation.
1 question tho if its safe to ask -- just how dangerous is it to start with what available now to tinker?
Hiho!
Another newbie dropping in just to ask When
if there is any Paypal Adress or something?
So all of us who are waiting eager for a Beta-Release can throw some Money at you while we sit here and hit F5.
Found nothing on the Webpage, but maybe im Blind.
And now Hurry up!
Greetings from Germany
Oliver
Yes pls I also want to help you guys out, I been sitting patiently waiting for this to happen.
Quote from: OliverD on February 11, 2013, 06:05:18 PM
Hiho!
Another newbie dropping in just to ask When
if there is any Paypal Adress or something?
So all of us who are waiting eager for a Beta-Release can throw some Money at you while we sit here and hit F5.
Found nothing on the Webpage, but maybe im Blind.
And now Hurry up!
Greetings from Germany
Oliver
Yes if there is an option to donate, please let me know! I would like to support the development of ML!
Guys, do you know what's a better option than spamming the forum thread?
Reading the commits over here (https://bitbucket.org/hudson/magic-lantern/commits) is an interesting alternative ;)
Quote from: brewerrj on February 12, 2013, 01:25:59 AM
Yes if there is an option to donate, please let me know! I would like to support the development of ML!
Unless i am wrong, look at the download page, at the bottom it states:
Thanks to your help, we have covered all our funding needs for now. Please consider donating to EFF, they do a great work in defending your digital rights!
btw I am still testing, will post an update soon
Wish I could join in on the testing. Ah, well.
Did a stability test from the debug menu, 3 fail ( not new to the dev's i think but posting it anyway)
[pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1ad190
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1ad0c0
[FAIL] foo => 'p'
[Pass] memset(bar, '*', 5) => 0x1ad0a0
[FAIL] bar => '*****fghl;'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0xf0e39
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0x2f5f4
[Pass] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x5
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x5
Date/time: 2013/02/12 10:11:05
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x6
[Pass] mod(s1-s0, 60) => 0x1
[Pass] mod(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x3f968
[Pass] p = malloc(50*1024) => 0xfff80
[Pass] CACHEABLE(p) => 0xfff80
m1 = MALLOC_FREE_MEMORY => 0x33158
free(p)
m2 = MALLOC_FREE_MEMORY => 0x3f968
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x395bf8
[Pass] p = AllocateMemory(256*1024) => 0xa56d0c
[Pass] CACHEABLE(p) => 0xa56d0c
m1 = GetFreeMemForAllocateMemory() => 0x355bec
FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x395bf8
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x3f968
m02 = GetFreeMemForAllocateMemory() => 0x395bf8
[Pass] p = alloc_dma_memory(256*1024) => 0x40a56d4c
[Pass] UNCACHEABLE(p) => 0x40a56d4c
[Pass] CACHEABLE(p) => 0xa56d4c
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40a56d4c
free_dma_memory(p)
[Pass] p = (void*)shoot_malloc(24*1024*1024) => 0x4a000068
[Pass] UNCACHEABLE(p) => 0x4a000068
shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x3f968
m12 = GetFreeMemForAllocateMemory() => 0x395bf8
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0x13320004
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id(get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x137c00b0
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0x1402023e
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0x149400c2
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x4
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x407f5b14
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x4
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
SW1(1,100)
[FAIL] HALFSHUTTER_PRESSED => 0x0
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
Uhm, so I broke the HALFSHUTTER_PRESSED macro ... :/
Gotta check it
It requires properties ;)
Found an crash log on my SD card, not sure what caused it as it is from a few days back....so maybe not a lot of help...
ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan30.650D101
Mercurial changeset : 9d92bca2f850+ (unified) tip
Built on 2013-01-30 09:02:24 by
[email protected].
Free Memory : 254K + 3655K
NANOMAD -
Just my periodic drop-by to see how things are progressing. Keep up the good work!
I know nanomad said we should all remove and stop testing the Pre-alpha but I'm curious who other than the Developers are still using/testing it? Other than mine and one other I haven't seen what I consider a lot of major bugs. I know I'm not a developer so I can only go by what I read posted here. The little I have tested so far has been trouble free. I hope this is a good sign so we can continue our testing soon.
I'm not rushing them because I know the pre-alpha and alpha are where the majority of issues are corrected so that the beta version can be more stable and hopefully just need some tweaking.
Thanks Dev. team for all you do on your free time for us.
Bob
More testing......
Movie menu
Bitrate (CBR) : working tested and including 3, seems to work in playback on camera ( timer runs down faster during recording indicating larger file size) Have not exported the files.
time indicator
off: working
elapsed:working
remain.card:working
remain.4gb:working
Movie logging: working
# Magic Lantern v2.3.NEXT.2013Jan30.650D101
Start : 2013/02/12 18:25:22
Lens name : EF100mm f/2.8 Macro USM
ISO : 0
Shutter : 1/0.000s
Aperture : f/0.0
Focal length : 100 mm
Focus distance : 390 mm
White Balance : 0 - Auto, Magenta 0, Blue 0
Picture Style : Auto (3,0,0,0)
FPS : 25.000
Bit Rate (CBR) : 1.0x
CSV data:
Time,ISO,Shutter,Aperture,Focal_Len,Focus_Dist
18:25:22,0,0,0.0,100,39
Movie restart: Not sure how to test this..
rec/stby notify
red crossout: working
rec/stby:working
movie rec key: working
force liveview: not working ?? after lens swap i get a canon message to acitvaye movie shooting
shutterlock: not tested
gradual expo: not tested
FPS override: Not working: starts at 25.000 then jumps to 40.000 live image freezes, (menu etc is still working) If FPS is turned off the image is live agian with a green band in the middle that fades
FPS ramping: with override on, it starts at 25 fps, but no changes.
HDR video working
Update FPS override: downsampling works, however i get mixed results, some recording seem to work (4 fps), other do not start at all, or i get a errer saying that recording has stoped.
Turnig fps ramping on leads to a crash
ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan30.650D101
Mercurial changeset : 9d92bca2f850+ (unified) tip
Built on 2013-01-30 09:02:24 by [email protected].
Free Memory : 254K + 3588K
And last:
Shoot menu.
Adv.Bracketing: As far as i see no working options....
Intervalometer: Working
TimelapseRamping:
Auto expo ramp:
LRT: Keep getting: too dark increasing iso
smooth ramping : Keep getting: too dark increasing iso
man. focus ramping: working (i think)
using ramping i seem to get stuck in the ramping, i get menu control back, but the ramping continuous, i have to turn off the camera to stop
Bulp timer: working
Motion detect: working
Silent picture: working saves a .422 file
mirror lockup: working
Flash tweaks: Not tested
Thats all folks....
A1EX and Nanomad,
I think I have tested everything I can test. I think I am finished for now, unless you have anything additional you would like me to test. Please do not hesitate to contact me. I will be here to test a possible future release!
Thanks for the invaluable testing :)
I noticed you can still get the original dumper from a certain repository, but I'm not crazy enough to use it.
Well, I not much we can do if it's not in an official repo
Please link it here though
Nanomad, i think it is still aviable on the server where you provided the pre alpha and the fix. The folder /650/ is public.
There's no old dumper in the 650D folder
THe only thing that's there is a "boot fixer" package that shouldn't do any harm...I'll remove it though
Quote from: baga on February 12, 2013, 06:16:45 PM
I know nanomad said we should all remove and stop testing the Pre-alpha but I'm curious who other than the Developers are still using/testing it? Other than mine and one other I haven't seen what I consider a lot of major bugs. I know I'm not a developer so I can only go by what I read posted here. The little I have tested so far has been trouble free. I hope this is a good sign so we can continue our testing soon.
I'm not rushing them because I know the pre-alpha and alpha are where the majority of issues are corrected so that the beta version can be more stable and hopefully just need some tweaking.
Thanks Dev. team for all you do on your free time for us.
Bob
I am still using it and I detected a bug in the normal Canon Firmware when ML is loaded.
Sometimes in Picture Review mode I can't use touch or go to other pictures.
When exiting and reentering via. the play button everything seems to be fine again.
I actually can no longer find the link, but it was in the list of commits, the one like the commit that removed it but added it and clicking the 'view file' button downloaded it to my computer.
Ah, here it is, thanks to web history.
https://bitbucket.org/hudson/magic-lantern/commits/5859adcaa2442cfe5be93b025b44a8be64ce33b2
Quote from: JannF on February 14, 2013, 03:41:34 AM
I am still using it and I detected a bug in the normal Canon Firmware when ML is loaded.
Sometimes in Picture Review mode I can't use touch or go to other pictures.
When exiting and reentering via. the play button everything seems to be fine again.
Interesting, I had that happen but I pulled the batt. out. That was yesterday so now I'm only loading ML when I want to try one or two feature and then back out. Up until then I only had questions about how to use certain settings I couldn't get to work.
Thanks for posting that. I was going to try it a couple more times before I posted it. I wanted to make sure it wasn't me first. Now I feel comfortable knowing it wasn't me.
Hey new guy here but been researching about this ever since I got my 650d and I was disappointed that he hadn't been done.. Then search this forum and found this and happy to of choose the 650d as a weapon of choice ! Keep up the work testers and development team it is true appreciated !
Hello, I'm new user, I have a 650D I install Magic Lantern? there is a version?
hello there :)
Things are still in the early development stage you see, so you are gonna have to be really really patient.
Also it's a good tip to read this thread if you want to get a general idea as to were you stand at the moment
early stage... xD
good joke, I'm running the "pre alpha" for a while now, good I was lucky enough to pass the installation, but I can say the ML part without props already runs very well :)
Quote from: JannF on February 16, 2013, 08:52:36 PM
early stage... xD
good joke, I'm running the "pre alpha" for a while now, good I was lucky enough to pass the installation, but I can say the ML part without props already runs very well :)
where is this verson please ?
Quote from: eternity52000 on February 16, 2013, 10:34:12 PM
where is this verson please ?
They don't want any one else testing right now. They feel it is to unstable to keep testing. Just sit patiently, when they feel a new pre-alpha is ready for more testers they will pass it on. If you keep bugging them it won't ever get released. Yes a few of us have it already and most of us have stopped testing like we were told.
Quote from: eternity52000 on February 16, 2013, 10:34:12 PM
where is this verson please ?
The installation is very risky and baga for example had a non working camera afterwards...
I was lucky and it worked out of the box and my camera was alive with and without ML.
Any updates ?
Found any issues with the build so far from the previous tests ?
Keep the hard work up :)
Quote from: JamieRollsMedia650D on February 19, 2013, 08:47:11 PM
Any updates ?
Found any issues with the build so far from the previous tests ?
Keep the hard work up :)
It has been awful quiet. No real news or updates either way. I'm hoping that's a good sign.
Quote from: baga on February 20, 2013, 03:45:37 PM
It has been awful quiet. No real news or updates either way. I'm hoping that's a good sign.
I know baga thought I try see if everything was going fine
There's work too, but you know?
Quote from: nanomad on February 20, 2013, 08:23:32 PM
There's work too, but you know?
Nonomad ah I know sorry if it come across wronge..
Quote from: nanomad on February 20, 2013, 08:23:32 PM
There's work too, but you know?
Same here, I think you took it wrong. I figured you where busy because you haven't really been on and didn't expect you to answer. I thought others were working on it besides you and thought they would update us. Just stuff like found this, tweaked that, turned on this function and testing that. Definitely not how far along are you or when is pre-alfa 2 coming out.
I've been interested in ML since reading about it in a Lifehacker article a couple years ago. I just received my first DSLR (650D/T4i) as a birthday present and have been following this thread daily. (ML being a possibility on the 650D was a major factor in choosing my first DSLR.)
I was also a bit worried not seeing much activity recently. Personally, I'm going to try to master the basics available in the stock firmware while this port is being tweaked in the hopes that I can contribute to testing when a new alpha/beta becomes available.
I want to thank nanomad and the rest of the ML community for all of their hard work, I know the end result will definitely be worth the wait!
Looking forward for this release.
Waiting patiently...
at least they are working on them , rather that others that wanted to hack sony cameras.
Because of that I have to change my sony nex-5n to another, I would like the 650d.
so give them time :)
Hola, I've been following this thread, and I just had a thought that would make the t4i a much better camera.
I have no idea if it's possible or if it's a reasonable idea, but I wish I could swipe the touchscreen with my thumb as my eye is in the viewfinder, as if I was changing the aperture with an aperture wheel on a non-Rebel canon. So, the touch screen would just replace an aperture wheel when I'm looking in the viewfinder and getting ready for a shot.
I've never used ML, and forgive me if this is far out of the realm of possibility. It's just an idea that I thought might help :) I wanna thank you guys for doing what you're doing, we all appreciate it!
Thanks to the ML folks for keeping up the great work. While we lie patiently on the sidelines, here, I have a question about features of ML on other cameras, perhaps the 600D/T3i. One feature I am looking for is a real mirror lockup to quiet the camera down for photographing wildlife or during meetings. Is that a feature in ML for other cameras? The way mirror lockup works on the T4i is that it locks the mirror up temporarily until you release the shutter, to eliminate camera shake during imaging. But as soon as the image is made on the sensor, the mirror returns to the down position - quite loud.
Quote from: cwmane on February 22, 2013, 03:56:56 AM
I have no idea if it's possible or if it's a reasonable idea, but I wish I could swipe the touchscreen with my thumb as my eye is in the viewfinder, ...
Interesting - the weak link I find in the 650D/t4i user interface is having to hold the aperture button down on the back of the camera to change aperture in Manual mode, so i kinda agree with your thinking here. It's a rub-your-head-pat-your-stomach move to adjust aperture.
Quote from: BrightGarden on February 22, 2013, 05:07:51 AM
Interesting - the weak link I find in the 650D/t4i user interface is having to hold the aperture button down on the back of the camera to change aperture in Manual mode, so i kinda agree with your thinking here. It's a rub-your-head-pat-your-stomach move to adjust aperture.
I thought only I felt that way. If you are holding down the shutter 1/2 way it's a 3 fingered pain.
Quote from: cwmane on February 22, 2013, 03:56:56 AM
Hola, I've been following this thread, and I just had a thought that would make the t4i a much better camera.
I have no idea if it's possible or if it's a reasonable idea, but I wish I could swipe the touchscreen with my thumb as my eye is in the viewfinder, as if I was changing the aperture with an aperture wheel on a non-Rebel canon. So, the touch screen would just replace an aperture wheel when I'm looking in the viewfinder and getting ready for a shot.
I've never used ML, and forgive me if this is far out of the realm of possibility. It's just an idea that I thought might help :) I wanna thank you guys for doing what you're doing, we all appreciate it!
When you are near viewfinder - lc shuts down so no input is working. SO i guess this would be HARD task to allow lcd work but at the same time only for custom functions (need to take over other built-in functions override them so you can grab the swipe events and do stuff with it.
I just read this WHOLE THREAD front to back (as it has been a while since I have kept up with where we are) and I'm more lost than I was before I read it! All this talk about all these features I don't understand, boot flag this and dumping that...I'm LOST! The features I DO need and DO understand are audio meters in video mode (why Canon didn't include this is beyond me), zebras, and longer recording times because quite frankly, 29:59 doesn't cut it for a wedding videographer like myself. Does anybody have any enlightening advice or do I need to read that "answers" thread I read about somewhere? I have been longing for ML since I bought my camera in August.
http://www.magiclantern.fm/forum/index.php?topic=4564.msg26384#msg26384
Quote from: InFocusAV on February 24, 2013, 06:57:37 PM
I just read this WHOLE THREAD front to back (as it has been a while since I have kept up with where we are) and I'm more lost than I was before I read it! All this talk about all these features I don't understand, boot flag this and dumping that...I'm LOST! The features I DO need and DO understand are audio meters in video mode (why Canon didn't include this is beyond me), zebras, and longer recording times because quite frankly, 29:59 doesn't cut it for a wedding videographer like myself. Does anybody have any enlightening advice or do I need to read that "answers" thread I read about somewhere? I have been longing for ML since I bought my camera in August.
Here here is a start: http://wiki.magiclantern.fm/userguide http://wiki.magiclantern.fm/install
Quote from: InFocusAV on February 24, 2013, 06:57:37 PM
I just read this WHOLE THREAD front to back (as it has been a while since I have kept up with where we are) and I'm more lost than I was before I read it! All this talk about all these features I don't understand, boot flag this and dumping that...I'm LOST! The features I DO need and DO understand are audio meters in video mode (why Canon didn't include this is beyond me), zebras, and longer recording times because quite frankly, 29:59 doesn't cut it for a wedding videographer like myself. Does anybody have any enlightening advice or do I need to read that "answers" thread I read about somewhere? I have been longing for ML since I bought my camera in August.
Yeah. Get something other than a DSLR for filming wedding photography. o.O Particularly as you'll see the sensor over heat and the camera shut itself down after an hour or so (Depending on environmental conditions of course). But yeah, if you're trying to be a wedding videographer, get some sorta run of the mill prosumer camcorder instead of a DSLR. o.O
Quote from: AshleyAshes on February 25, 2013, 04:36:28 AM
Yeah. Get something other than a DSLR for filming wedding photography. o.O Particularly as you'll see the sensor over heat and the camera shut itself down after an hour or so (Depending on environmental conditions of course). But yeah, if you're trying to be a wedding videographer, get some sorta run of the mill prosumer camcorder instead of a DSLR. o.O
I don't know, I've known people who do wedding videos with DSLR's and they make some amazing stuff. There are definite advantages to a camcorder, but definite advantages to a DSLR as well.
Quote from: Gorilla on February 25, 2013, 11:24:07 AM
I don't know, I've known people who do wedding videos with DSLR's and they make some amazing stuff. There are definite advantages to a camcorder, but definite advantages to a DSLR as well.
I've been to two weddings in the last year or so as a guest and the Pro photographers used DSLR's for videos. It was after the last one I decided it was time to upgrade to one. When the T4i/650D was released I knew that was the one for me.
DSLR's at a Wedding - most pro's use just that - DSLR's, as in Plural or two or more - that way you can get around the 1/2hr or upto 1 hour before overheating issues - and me I DON'T DO WEDDINGS ;D - and I'll happily wait for the 650D ML release (probably the beta) - with the price of 650D's now (around £450), if you're going to be a pro, buy two and some nice glass - or organize you shoots so that you can shoot in chunks of less than 30min - in my experience (I used to do wedding videos) most people don't want to listen to all of a hymn - so you can do first and last verses - anyway, now way off subject :-)
T4i/650D is perfect for wedding videos, really looking forward to a stable ML!
Quote from: InFocusAV on February 24, 2013, 06:57:37 PM
I just read this WHOLE THREAD front to back (as it has been a while since I have kept up with where we are) and I'm more lost than I was before I read it! All this talk about all these features I don't understand, boot flag this and dumping that...I'm LOST! The features I DO need and DO understand are audio meters in video mode (why Canon didn't include this is beyond me), zebras, and longer recording times because quite frankly, 29:59 doesn't cut it for a wedding videographer like myself. Does anybody have any enlightening advice or do I need to read that "answers" thread I read about somewhere? I have been longing for ML since I bought my camera in August.
Another good place to look is YouTube. There are quite a few videos that show how to install and others that go over different features with examples. I've found them very helpful.
I'm looking forward to a stable ML for 650D too! I have a ML for 5DMII, it work great.
Overheating? I haven't been able to successfully overheat 6D or 600D. The most I got was was temp warning on a 90F+ day shooting outside with no AC. 650D shouldn't be different. The older cameras tended to have overheating problems like 550D/5dII (prob old versions). You can also turn on movie restart and that has maybe a couple of seconds gap. 650D being a digic V camera, that gap is a little shorter.
What will happen though is your battery will go dead fairly quickly from LV being on and card cranking. Plug in or have lots of spares.
Having done a few weddings on stills only, I'd use the DSLR to do the shots and then a cheaper camera to record video. You can't do both on one camera and you aren't going to be running around taking videos or they'll be a shaky mess.
Just picked up a Canon X6i (650D) The other day. I had a GH2 and wanted to try something different. Any status on the ML for it? Beta? I looked through the forum and didn't really see anything recent. I am looking to increase the bitrate on the video and have All I-frames. Don't know if that is what you guys plan to do. Let me know if you need donations.
Quote from: APXmusic on February 28, 2013, 04:53:01 AM
Just picked up a Canon X6i (650D) The other day. I had a GH2 and wanted to try something different. Any status on the ML for it? Beta? I looked through the forum and didn't really see anything recent. I am looking to increase the bitrate on the video and have All I-frames. Don't know if that is what you guys plan to do. Let me know if you need donations.
Sorry ... just something before alpha and pre-alpha ... not usable yet. Good luck Nomad&team!!! We are watching you guys (your commits)!
After having just started using and getting used to Magic Lantern on my 5d2 and t3i, now that I just picked up a t4i I feel so paralyzed without it! Or more accurately, I feel like I am shooting blindfolded without peaking, zebras, the zoom in box while shooting, etc. etc.!
On today's shoot I used the t3i on time lapse and the t4i was the primary camera due to 60fps for slow motion. So... Super bummed it's not ported yet!
Can't wait for it to be finished :)
Don't know if it's obsolete or not: Tried to use focus bracketing with pre-alpha. Doesn't work for me, giving me focus error message.
Side effect: Wasn't able to use focus in liveview thereafter.
- Started camera with ML disabled (Set button pressed): Doesn't work either
- Started camera with card without pre-alpha ML installed: Nope, won't run
- Deleted all camera settings + Fn: Works fine.
Well, outdoor macro season is near and sometimes a camera with vari-angle screen will come handy. ;-)
On the other side: 7D will do the job too and a little yoga acrobatic is supposed to be healthy ...
Thank you all for all your efforts!
Ciao, Walter
Thanks walter, I'll look into it :)
I think I have a solid feature set for Alpha 1 right now :)
Looks like someone is going to have fun with his camera this week-end (or at least I hope so :P)
this means that you are going to push out the Alpha1 for the public?
Getting way to excited! Working on my glide cam i got a few days ago. so two toys in one day! Wow
Quote from: loplo on March 02, 2013, 03:04:20 PM
this means that you are going to push out the Alpha1 for the public?
Once a1ex reviews the feture set and builds the release package ;)
Sounds good.
Too exciting! I cannot wait! Thanks for your commitment to the project nano! and A1ex!
Hi Guys,
Not only am i new to the ML forum but also new to the wonderful world of DSLR's as i've just placed my order for a Canon 650D (my first "proper" camera)
I chose the camera after a recommendation from a friend who also raved about ML so i decided to check this forum out.
Looks like it's a very exciting time in the ML universe right now so keep up the sterling work and i look forward to the finished release for the 650D.
Looks like I have some good news for my 650d. Looking forward to be able to make a contribution to this project again.
Kudos.
Very excited to test this build!
So am I
Well done
Paul
Quote from: nanomad on March 02, 2013, 03:06:56 PM
Once a1ex reviews the feture set and builds the release package ;)
Great news and thank you Nanomad! And also a BIG thanks to A1ex for all the hard work you have done! Amazing :)
I'm ready to start testing the Alpha1 8)
Will props be enabled in this release?
I have a T2i and a T4i, I've actually fallen back to using my T2i due to it's Magic Lantern support. We were even chroma keying in an ambulance last night and the waveform monitor was invaluable. It would be nice to get my T4i in action for shoots as well however so I hope progress goes well. Particularly as I can't up the bitrate over 1.2x on most memory cards on my my T2i, and I'm hoping the Digic5 + UHS-I of the T4i support will let me get that higher. :)
I have T2i and T3i both running ML. Thrilled to hear it is coming for my T4i as well. Thank you so much for the effort.
Excellent to hear this. Have had a pretty ridiculous week, but it's neither here nor there!
I'd stopped checking every day and maybe every 2 days or so, and today I see this. Beautiful.
Looking forward to getting that Alpha 1 on there. Great work kids. Really impressive.
Hopefully I'm playing with it in the next few days.
Getting super excited for this now 8)
Can't wait to finally run ML on my 650D! Great work guys! :D
Just registered to say I'm looking forward to the stable release and will donate once the stable version is out.
I have a 400d and have been using 400plus for the past few years, just purchased the 650d and waiting for it to arrive but know ill be missing the extra functionality that 400plus offers.
Lookined forward to the stable release.....
Update: sent a preview to a couple of trusted testers, waiting for feedback ;)
You made a test release for the test release? :P
Got ML alpha 1 running:
I will post screen shots as requested by nanomad of each menu.
I will report as i go on.. First did the stub test.. some fail.
Stub test:
Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1ad108
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1ad0c0
[FAIL] foo => ''
[Pass] memset(bar, '*', 5) => 0x1ad0a0
[FAIL] bar => '*****ghjkl'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0xd479e
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0x45918
[FAIL] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0xd5
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0xa
Date/time: 2013/03/04 10:59:10
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0xb
[Pass] mod(s1-s0, 60) => 0x1
[Pass] mod(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x5f128
[Pass] p = malloc(50*1024) => 0xe06c0
[Pass] CACHEABLE(p) => 0xe06c0
m1 = MALLOC_FREE_MEMORY => 0x52918
free(p)
m2 = MALLOC_FREE_MEMORY => 0x5f128
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x322ff4
[Pass] p = AllocateMemory(256*1024) => 0xa73f2c
[Pass] CACHEABLE(p) => 0xa73f2c
m1 = GetFreeMemForAllocateMemory() => 0x2e2fe8
FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x322ff4
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x5f128
m02 = GetFreeMemForAllocateMemory() => 0x322ff4
[Pass] p = alloc_dma_memory(256*1024) => 0x40a73f6c
[Pass] UNCACHEABLE(p) => 0x40a73f6c
[Pass] CACHEABLE(p) => 0xa73f6c
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40a73f6c
free_dma_memory(p)
[FAIL] p = (void*)shoot_malloc(24*1024*1024) => 0x0
[FAIL] UNCACHEABLE(p) => 0x40000000
shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x5f128
m12 = GetFreeMemForAllocateMemory() => 0x322ff4
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0x946e000a
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id(get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x94b800b0
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0x953e0284
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0x95d00072
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x3
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x40a73f6c
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x3
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
SW1(1,100)
[FAIL] HALFSHUTTER_PRESSED => 0x0
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
Overlay:
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM0-overlay.bmp)
All seem to work except Magic zoom and focus confirmation. I do not get green bars, and split screen also does not work as i would expect.
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM8-overlay-2.bmp)
Movie
Did not test:
bit rate
Gradual expo
Image fine tuning
Movie tweaks --> force live view
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM1-movie-.bmp)
The rest is working as expected.
Shoot:
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM2-shoot.bmp)
Working
Display:
Not tested
Advanced settings-->
HDMI
uniwb
Rest is working
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM3-display.bmp)
Not tested (will do later)
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM4-prefs.bmp)
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM5-debug.bmp)
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM6-help.bmp)
Thats all for today...,......
Seems to be fairly stable *nudge nudge*
I kid, a confident release is a happy release or something like that.
Looks very promising! I hope I can test ML later this week to do some test shots. Finally some nicer weather in The Netherlands right now!
Finally some nicer weather in The Netherlands right now!
Ooooo yea. Today was already nice... Spring and ml. The
NL can be a nice place to live.....
in France as the sun is now hoping that he still silk when the silk ready alfa
wow this is looking great seems more like we are closer to a Beta then an Alpha :)
Aren't the audio settings menu not working at all? :o
The weather is gray in Western Norway today. But I don't need the sun when I have the Magic Lantern Alpha 1 preview! 8)
blade; Nice too see that you have started the testing already :)
I have also gone through some testing, and it looks good!
! The MENU's I have tested so far is tested completely - So when nothing is mentioned I think it's working !
Installation: Smooth
General: Looks great - No more of the Canon overwiting of the ML UI.
Overlay MENU:
- Magic Zoom: As blade wrote, there is still no focus conformation.
The "fullscreen" setting of Magic Zoom isn't working well.
I have also experienced that the Magic Zoom is buggy. It's sometimes flashing, and blocks the function of the "trash/ML menu" button. But then i have loads of overlay on and also Motion Detect on...
Movie MENU:
- FPS override: Not working. Working after disabling sound in Canon menu (Thanx a1ex!)
- Movie Tweaks: Force LiveView set to "Always" works when you take off the lens, but I have to manually press LV after the lens is back on.
Shoot MENU:
- Silent Picture: Can't open the .422 files in the YUV422 Convertor (Unknown image size: 1226880). Can't preview the pictures in camera ither (Set + wheel).
Display MENU:
- Advanced settings: UniWB correct; Can't see any difference... but maybe it's me... :o
- Tested HDMI out to my 1080P TV: Horisontal orange line on some of the Screen Layout's. But much better than the Pre Alpha :)
More testing will follow tomorrow! :D
Quote from: breaker on March 04, 2013, 08:59:58 PM
Movie MENU:
- FPS override: Not working. The movie is auto-stopping after few seconds. Sometimes with crashreport.
Breaker, welkom to the party!
Confirmed, FPS override. Not working.
Some clips last for up to 10 sec, and then the camera crashed. The clip that is saved is a few MB, and consist out of only one frame
FPS set to 2.5
ASSERT: 0
at Graphics.c:3580, task CtrlSrv
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Mar02.650D101
Mercurial changeset : 3eecdcedfce1+ (unified) tip
Built on 2013-03-02 19:43:49 by alex@thinkpad.
Free Memory : 381K + 3612K
Try disabling sound from Canon menu.
ML normally does that automatically, but for this it needs write access to camera settings (not available in safe mode).
Quote from: a1ex on March 04, 2013, 09:22:24 PM
Try disabling sound from Canon menu.
ML normally does that automatically, but for this it needs write access to camera settings (not available in safe mode).
Thanx a1ex! Now it's working fine :)
But when I eager to see it and pushes the Play button to early after stopping the FPS override movie I get a crash with this Crashlog:
ASSERT: 0
at Graphics.c:3580, task CtrlSrv
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Mar02.650D101
Mercurial changeset : 3eecdcedfce1+ (unified) tip
Built on 2013-03-02 19:43:49 by alex@thinkpad.
Free Memory : 381K + 3584K
Which I now see is exactly like blade's Crashlog...
Quote from: momendo on March 04, 2013, 08:18:20 PM
Aren't the audio settings menu not working at all? :o
The 650D had audio settings in the canon firmware.. so no need in ML
Hitting F5 every 2 hours. o. O
greetings for all.
Just subscribe to the thread and you'll get an email notification for each reply.
Happy to see this is getting done, I hope its out soon! ;D
I have question regarding movie recording and zoom:
- will magic lantern enable "crop zoom" on 650D ("digital zoom" when only center of sensor is used for recording video)?
Thanx!
btw regarding smaller size of RAW files - will it be added later or it is definitively impossible to make?
No crop zoom yet, and other raw sizes are kinda dangerous to test without a proper recovery procedure
edit:
Thanks for the feedback everyone, I'll try to package the Alpha release by the end of the week
Quote from: nanomad on March 05, 2013, 08:54:05 PM
Thanks for the feedback everyone, I'll try to package the Alpha release by the end of the week
Best news I've heard this week.
Thanks for all the hard work You did to make us happy and bit more productive with our 650D's!
The "other" raws on 600D weren't easy to process. They also had defects (purple, wrong size reported). I doubt it will crash but you won't be able to load them into lightroom or tools like that. IMO they are kind of a dead end. One of them was kinda decent but the resizing looked bad.
Best news, thanks for all the hard work.
nanomad, thats great news! I promised to test some more today, but I had no time for it. But tomorrow seems to me a good day for testing :)
Nanomad, that HTML feature chart in the nightly download page is awesome. Is there a way we can get that into the wiki or as a link from the Alpha page. It helps people gauge what works and what doesn't. We, the users, can update it if it's in the wiki with good docs. I think that would be a great idea.
Quote from: breaker on March 05, 2013, 11:03:00 PM
nanomad, thats great news! I promised to test some more today, but I had no time for it. But tomorrow seems to me a good day for testing :)
Today is a good day for testing! today is your tomorrow, as you wrote your post yesterday :P. I hope to do some testing during lunch today.... Will keep you posted.
Nanomad, I have been using the build without specific testing, but just shooting, and so far its been nice and stable, nothing to report.
Ridiculously excited about this. Just put ML onto my friends 2 550s. Magic doesn't cover it!! Many thanks to Nanomad and all. Champing at the bit to get the alpha now! :)
Quote from: nanomad on March 05, 2013, 08:54:05 PM
No crop zoom yet, and other raw sizes are kinda dangerous to test without a proper recovery procedure
edit:
Thanks for the feedback everyone, I'll try to package the Alpha release by the end of the week
Hi nanomad, I was wondering if you got my message and photo's yesterday? I can't tell if it went through.
Quote from: blade on March 06, 2013, 08:48:50 AM
Today is a good day for testing! today is your tomorrow, as you wrote your post yesterday :P. I hope to do some testing during lunch today.... Will keep you posted.
That's right! And now I have too keep my promises ;) I have learned a lot from the systematic testing so far, and I find possibilities I would not have found without it!
And here is today's testing.
! The MENU's I have tested is tested completely - So when nothing is mentioned I think it's working !
Prefs MENU:
- Image review settings: The silent .422 pictures doesn't show up (not on PC ither). With Compare Images the primary picture sometimes changes.
- Quick Zoom: "Full zoom on AF pt." allways zooms on the middle of screen - not on AF points.
- FlexInfo Settings: Buggy as hell :o
Debug MENU:
- Burn-in tests: "Stubs API test" 83 passed, 3 failed:
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1acd00
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1acca0
[FAIL] foo => ''
[Pass] memset(bar, '*', 5) => 0x1acc80
[FAIL] bar => '*****ghjkl'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0x84d0b
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0xc355a
[Pass] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x6
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x2c
Date/time: 2013/03/06 19:10:44
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x2d
[Pass] mod(s1-s0, 60) => 0x1
[Pass] mod(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x5f6c0
[Pass] p = malloc(50*1024) => 0xe0120
[Pass] CACHEABLE(p) => 0xe0120
m1 = MALLOC_FREE_MEMORY => 0x52eb0
free(p)
m2 = MALLOC_FREE_MEMORY => 0x5f6c0
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x37ca54
[Pass] p = AllocateMemory(256*1024) => 0xa7a498
[Pass] CACHEABLE(p) => 0xa7a498
m1 = GetFreeMemForAllocateMemory() => 0x33ca48
FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x37ca54
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x5f6c0
m02 = GetFreeMemForAllocateMemory() => 0x37ca54
[Pass] p = alloc_dma_memory(256*1024) => 0x40a7a4d8
[Pass] UNCACHEABLE(p) => 0x40a7a4d8
[Pass] CACHEABLE(p) => 0xa7a4d8
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40a7a4d8
free_dma_memory(p)
[Pass] p = (void*)shoot_malloc(24*1024*1024) => 0x4a000068
[Pass] UNCACHEABLE(p) => 0x4a000068
shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x5f6c0
m12 = GetFreeMemForAllocateMemory() => 0x37ca54
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0x50d00004
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id(get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x511e00ae
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0x51b60114
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0x52580082
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x4
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x407f9cc4
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x4
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
SW1(1,100)
[FAIL] HALFSHUTTER_PRESSED => 0x0
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
Help MENU:
- No documentation. Not when hitting info button on the rest of the munu's ither. Suppose it's because it's nightly..?
When the screen is turned (self shot mode?) it's still mirrored.
I really like the Junkie mode - it gives a quick overview!
And thats all for now! Now my testing will be normal use ;)
nanomad if you need anything more to be tested, you know where to send it 8)
Quote from: baga on March 06, 2013, 03:30:29 PM
Hi nanomad, I was wondering if you got my message and photo's yesterday? I can't tell if it went through.
Got it :)
Saw the good news on the phone and it sounds amazing! Keep up the good work and i hope to join you as soon as possible! As allways thanks for everything you do nanomad and everything included in the project! :D
Got my second T4i coming soon and cant wait to get ML on them! I've been addicted to ML since I first used it on my T3i, and have been following this forum for a long time! I was so pissed when I missed the limited release.
Keep up the Great work nanomad and others!
Accidently hit the qoute button instead of modify so ignore this post! :)
Finally back to a Canon after many years camera-less (last new DSLR I purchased was a 30D, only had it for 6 months).
I have been following ML for some time now, excited to see what you guys can do with these cameras.
Just picked up the 650D yesterday afternoon and cant wait to get ML on her.
Will be making a donation to the cause very soon!
I like using the Intervalometer. "Shoot like crazy"
Sorry for not reporting as promised.... kids... work.... well you know....
I will keep it short, most stuff works, some does not as breaker reported. Overall very stable, and responsive.
And as breaker i do like this mode:
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM0-junkie-1.bmp)
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM1-junkie-2.bmp)
Looking forward to the alpha, so more people can get testing.
Been following Magiclantern for a couple of years now and finally got my first DSLR a month ago(T4i). Pretty impressed after reading these posts so far and can't wait to try it. If you need a ML newbie to test let me know.
Quote from: blade on March 08, 2013, 08:35:57 AM
(http://www.ikloud.nl/wp-content/uploads/2013/03/VRAM0-junkie-1.bmp)
Is this a touch menu or something? Lots of buttons :P
I have a question. I like using the junkie screen menu but does it have everything that the default menu has?
Quote from: brewerrj on March 08, 2013, 02:03:07 PM
Is this a touch menu or something? Lots of buttons :P
Yes it's both.
Quote from: baga on March 08, 2013, 04:09:03 PM
Yes it's both.
I didn't realized that - I always forget that the screen is touch... ;) But testing it now, and for me the touch just works as Q. So you have to navigate with key's to the right box, and then you can press the screen to get into the submenu. I don't know if touch will work on that menu - some of the boxes are a bit too small to hit. Then it need to have some sort of magnifitcaion or white frame on touch and activation on release.
There is an own thread for the menu rationalization. Maybe it's mentioned there: http://www.magiclantern.fm/forum/index.php?topic=4386.0
Touch support is not really working, but feel free to implement it ;)
Quote from: a1ex on March 08, 2013, 04:39:21 PM
Touch support is not really working, but feel free to implement it ;)
If I could I would, but I have no real coding experience, except for a bit of HTML, PHP & ActionScript 2 (the last time I used it was about 3 years ago)
So what language is ML written in?
And do you have some sort of emulation environment to test against or is it a case of compile, load onto the camera and pray?
Its C++, yes, load and pray. If you somewhat know what you're doing, not so much praying
So I don't do c++ as a primary language but am comfortable with programming (mainly scripting such as python).
How big is the MLB dev team and what areas are slowing down the release of the 650d version that I could assist with?
Ah C++. I have a book for that, I got it was part of a course I did about 10 years ago and only opened it once :P
Compile yourself and fix what's wrong. You don't need to wait for a release if you can make the source tree. I think only 1 person working on 650d... but first read up on how ML + the camera works. Camera can make logs, you can dump and disassemble the fw. Once you get the gist you can add features or make old features work on 650D.
Wish I knew how to complie it altogether really want to try this know ! Lol itching !
Hey nanomad, just wanted to extend my gratitude to your awesome effort on the 650D port! Really looking forward to trying out the Alpha. Planning a shoot tomorrow, guessing it probably won't be ready in time, but as soon as it's out I'm dropping everything and taking it out in the wonderful weather we've been having here lately.
Can't help noticing a few people posting "just compile it" or "fix it yourself" - is a working version of the source available already or something?
Hi, I'm from Costa Rica and I own a T4i, how can I help you testing the ml fw?
Quote from: scott.stamp on March 09, 2013, 01:25:51 AM
Hey nanomad, just wanted to extend my gratitude to your awesome effort on the 650D port! Really looking forward to trying out the Alpha. Planning a shoot tomorrow, guessing it probably won't be ready in time, but as soon as it's out I'm dropping everything and taking it out in the wonderful weather we've been having here lately.
Can't help noticing a few people posting "just compile it" or "fix it yourself" - is a working version of the source available already or something?
Yes. The source is, as always, on the repository. There's no point in keeping stuff secret :)
Good Job Guys !!!
Keep up the goood work !!
Thank u sooo much !
Quote from: nanomad on March 09, 2013, 09:31:10 AM
Yes. The source is, as always, on the repository. There's no point in keeping stuff secret :)
I can't find this alpha version of ML, can you put the link?
Nanomad, is Alpha version ready to install? Could you please so kind let me and other men know where is a place for download.
Thanks for your great job !
There's no compiled version, only the source - officially. If you know how to compile and willing to risk to compile and install your version, you're good to go.
And by the way, don't stress the team with such questions. I don't really think that any of us is losing money because he's running canon and not ml.
Thanks, there's nothing more but wait... great work, by the way...
Compile it yourself. What's the problem? :)
Be patience , takes time!
The software was sent to a few trusted testers. And runs in safe mode ( does not boot by itself ). As far is I know no big issues were found. Nanomad already announced that he will compile a public alpha.
That's the time to jump in if you want to make a contribution.
I might be wrong but I think nanomad is the sole developer working on the 650d. So if he finds time, that is greatly appreciated. If not, so be it...
I have no coding skills so I can't make a contributions in that part of the development. If you do have the skills, please help out we're you can.
Otherwise, wait for it, and be thankfull if and when it arrives.
Anyone heard from ProfessorX? I know he was loving the pre-alfa.
Quote from: baga on March 10, 2013, 03:45:48 PM
Anyone heard from ProfessorX? I know he was loving the pre-alfa.
Not on this forum, no. Would be nice to know if he had time to test.
The public Alpha will be out real soon. Those of us that tested the latest version have given nanomad our results. He is working on the alpha and it will be out real soon. Remember this is something he does in his spare time. He has a full time job and personal life. He hasn't let us down yet and if he said real soon, it will be. I figure sometime this weekend if it's not then next week. He doesn't want to brick any camera's on the first public release. The above goes for all the developers and testers.
When it's ready we will all know.
Quote from: blade on March 10, 2013, 04:00:37 PM
Not on this forum, no. Would be nice to know if he had time to test.
I know he was using the original pre-alpha and was enjoying it. I don't think he tested the last update even though it was offered to him to test.
Long time magic lantern user here, (I was privately testing the beta on the 550d when that came out.) I wanted to say thank you to Nanomad and A1ex for devoting their time to such a worthwhile effort. Also thanks to blade, breaker, baga and all the testers for putting your cameras on the frontline to help with dev. I think that the final ML release for t4i is going to be a game-changer, just like it was for the 550d/MarkII back in the day.
Really excited for this Alpha!
Just a thank you for the work you all have been doing. I've used ML on my T2i for a good while and just received my new T4i. I waited for ML to be close before I ordered it. Again. Thanks for the great upgrade to the firmware Canon provides. It really makes these cameras so much easier to use and adds so much functionality. I'm still not sure how I ever did anything with my old SLRs - Minolta SRT-101 and -102! Long time ago. Whole different world. I like today's world better in most way!
Hey hey, just chiming in again, loving the progress so far, just wish I knew where to get that pre-alpha, but from the looks of it will not have to search as an Alpha is on the Horizon. A big thank you for the Devs working tirelessly on this Port. an all the testers testing. I have my virgin Camera here ready to slap some ML love in it. thanks again.
I've compiled myself a magiclantern.bin and autoexec.bin but I'm not sure how to compile the .fir or whatever else I need.
EDIT: I've tried doing "make" in the install/650D folder and it's giving errors that I don't quite understand. I'll post a link to a log as soon as I can get it out of the VM.
EDIT: Is it acceptable to use 650D-bootfix.fir with a compiled autoexec.bin and ML?
EDIT:
I took the plunge and it worked out-of-the-box when I inserted my card and turned on. (I think I had set my camera's bootflag on a previous experiment).
(http://img41.imageshack.us/img41/1047/img7898xo.jpg)
Quote from: Lucas_W on March 12, 2013, 06:48:12 AM
I've compiled myself a magiclantern.bin and autoexec.bin but I'm not sure how to compile the .fir or whatever else I need.
EDIT: I've tried doing "make" in the install/650D folder and it's giving errors that I don't quite understand. I'll post a link to a log as soon as I can get it out of the VM.
EDIT: Is it acceptable to use 650D-bootfix.fir with a compiled autoexec.bin and ML?
EDIT:
I took the plunge and it worked out-of-the-box when I inserted my card and turned on. (I think I had set my camera's bootflag on a previous experiment).
(http://img41.imageshack.us/img41/1047/img7898xo.jpg)
where did you find all those files to compile?
You can get the source over at https://bitbucket.org/hudson/magic-lantern/ (https://bitbucket.org/hudson/magic-lantern/), info on compiling the source can be found on the forum :)
I really want to try this pre-alpha. I'm curious as to what's left to be tweaked in the public alpha.
So in my curiosity, I'm going to try and give this pre-alpha a compile.
If it's alright with Nanomad, I'd be happy to upload/share my own compiled autoexec.bin and post a guide on how to install it. Although I'm not sure how perfect my compilation and install method was. (Are the help docs meant to be missing?)
I would also like to try this but I don't want to screw my camera up. Should I just wait for the public alpha?
Quote from: Lucas_W on March 13, 2013, 07:05:13 AM
If it's alright with Nanomad, I'd be happy to upload/share my own compiled autoexec.bin and post a guide on how to install it. Although I'm not sure how perfect my compilation and install method was. (Are the help docs meant to be missing?)
They weren't on either version I tested. It's probably one of the last things they do. They need all the data they collected from testers ,everything working and including new nightly builds others have compiled before they can write help files.
That's my guess anyway.
Sorry guys I've literally been overloaded by work :'(
Although it's nice to see someone else took the initiative and compiled a bin
That being said I wouldn't use the autoexec method for the alphas mainly because it's safer if nothing is written on the camera in the first place
Also, and i don't know if your builds has props disabled or not. I don't remember what the source code in the repo has set
it's all good. we're all busy. I've had a ton of auditions and such. just looking for something to take my mind off of it. :)
What's the alternative method to using the .bin?
Also, how would I know if I do have Props disabled?
Hey @All,
looks were coming forward step by step... i'm sure there lot of people out there cant await to try it out. so maybe someone could upload compiled binfiles... sure its alpha, sure its not stable, but for compilation-noobs it would be a realy big help, to be also able, to test it out :)
Thanks a lot for your hard work,
regards, TK
Quote from: tk-germany on March 14, 2013, 11:23:38 AM
Hey @All,
looks were coming forward step by step... i'm sure there lot of people out there cant await to try it out. so maybe someone could upload compiled binfiles... sure its alpha, sure its not stable, but for compilation-noobs it would be a realy big help, to be also able, to test it out :)
Thanks a lot for your hard work,
regards, TK
The real Alpha will be out shortly I'm sure, just sit tight. The last pre-alpha was by invite only and that testing is pretty much done. When they shortly they mean it. If you've read this whole thread you know the last thing you want to do is keep asking.
Hi Baga,
as you can see, im within this thread from the beginning, and be sure i read the whole thread "a thousand times" in hope of have overseen the post, where some binaries are hidden :)
Sure im also anoyed of the people asking for a release... that was also not the target of my question :)
Just saw that some guys got it compiled by themself and hoped that they could drop a bin- anywhere, that does not collide with the patience for a final stable version...
Thanks a lot,
TK
Quote from: APXmusic on March 13, 2013, 03:54:59 PM
I would also like to try this but I don't want to screw my camera up. Should I just wait for the public alpha?
Yes wait, it will be out soon. There are somethings working fine in this pre-alpha others aren't there at all and even more that only work partially and shouldn't be used because they can damage your camera. The next version will be out soon.
Quote from: tk-germany on March 14, 2013, 02:09:32 PM
Hi Baga,
as you can see, im within this thread from the beginning, and be sure i read the whole thread "a thousand times" in hope of have overseen the post, where some binaries are hidden :)
Sure im also anoyed of the people asking for a release... that was also not the target of my question :)
Just saw that some guys got it compiled by themself and hoped that they could drop a bin- anywhere, that does not collide with the patience for a final stable version...
Thanks a lot,
TK
That's even worse, you definitely don't want to put those in your camera. You really need a good understanding of not only how ML works, how it's programmed and how to write program your self. Taking a pre-alpha that is not completely functioning and potentially damaging and then putting an untested or approved bin on top of it, not a good combination. I have both pre-alphas and have had my camera locked up for 3 days with the 1st one. Everything is working good for me including ML now.
Believe me I'm as anxious as you and have wanted to test those bins but not on this pre-alpha. I would bet that those new bins aren't in the nightly download section because no one wants to risk bricking some one else's camera.
Really the next release is real close.
Quote from: baga on March 14, 2013, 03:09:45 PM
I would bet that those new bins aren't in the nightly download section because no one wants to risk bricking some one else's camera.
Exactly. Given how the pre alpha went I don't feel like publishing anything when I know I can't be there on time if something goes wrong
So the T4i's normal videos are around 50mbps. In your testing experience, how high of a stable bitrate are you guys able to achieve with the hack?
I know that the question is hated, but shouldn't ML be there a week ago?
Is there a date?
There is no planned release date for anything. ML is a hobby project for us, we do it in our spare time.
Sometimes we have more time, sometimes less.
Is it clear now?
Idk why this message board is flooded with dumb question. It's should be just for the developers and testers. More you ask longer it take! I don't say much bc I'm patient but I don't like that the ppl that are putting in work to be upset. Let them get it done when it gets done!
In my opinion the development threads should be open for posting only for the developers and the testers. The others/curious people should open their own threads and not stress the team. My two cents.
You'll just end up with a load of empty/small threads.
@APXMusic, I tested then and I got up to 2.4x and any-more than that it stopped recording. This is with no HDR-video and with Global Draw in Live-view off. I did a benchmark test on my card and the camera said my card could do 40.9 MB/s (Or is it Mb/s? I forget). If you say that the standard is 50 megabits per second then I can film at 120 megabits per second.
Quote from: a1ex on March 15, 2013, 07:40:08 AM
There is no planned release date for anything. ML is a hobby project for us, we do it in our spare time.
Sometimes we have more time, sometimes less.
Is it clear now?
Sorry for that - but its clear now - i didnt know, that ML is a hobby project.
I changed my 600D to a 650D and im missing ML so much =)
Lol, you've thought that someone is paying them to work and give us ml for free? You gotta read more about ml and find out things about the project.
Quote from: loplo on March 15, 2013, 09:36:33 AM
In my opinion the development threads should be open for posting only for the developers and the testers. The others/curious people should open their own threads and not stress the team. My two cents.
At first I agreed completely with your thoughts. After some thought myself where would the testers come from. Non developers or testers sometimes reading our posts can ask a good question or have an interesting idea because they are just following.
I was guilty of those post in the beginning. I think everyone is starting to help the developers by assisting people under stand the process.
Just my thought's. ;D
Canon should pay these guys. Magic Lantern generates as much interest in canon products as canon's own marketing, maybe more.
Heh, people should just stop being impatient. Its not like ooops we forgot to make an alpha...
Everyone should be able to post tho. Random people have come up with some good ideas and solutions.
That 40MB/s write is megabytes. Video is megabit. I'm assuming you'll get 100-200 megabits out of 650D especially when write out rate is increased. The setup is similar to digic IV on this and eos M.
The resizing is what is interesting. I'm guessing hd buffer is smaller and there is less moire than on 6D. Also wonder how audio is going to go as you have the datasheet and IC is identified.
How about frames per second? How much can the default 1080p at 30 frames/sec be increased? This will be useful with the HDR feature...
What about sensor defects on low FPS override. 6D isn't the only timer A camera.
Good thinking t4ilover, I originally tested at 720@60. I'm currently testing 1080@30 at 3x bitrate and it's still recording at 1 minute 48 seconds.
EDIT: It goes for 6 minutes before cutting off.
hello, i am new to this post and have recently looked into magic lantern for my canon 650D.
A friend of mine downloaded it yesterday for his 550D and it looks amazing.
i was wondering if anyone has any idea when it will be available for the 650D?
Welcome. Read trough the previous pages and you'll find out.
Quote from: joshv on March 16, 2013, 12:31:44 PM
hello, i am new to this post and have recently looked into magic lantern for my canon 650D.
A friend of mine downloaded it yesterday for his 550D and it looks amazing.
i was wondering if anyone has any idea when it will be available for the 650D?
I see you are new so I would suggest reading this post from beginning to end and if you still have the same question I will give you my personal phone number and answer it in person. I want ML and so does everyone else who has a 650D and wants more control. I originally thought ML had some funding but as far as I know it's an unfunded project(this needs to change) and the ML release for the 650D(T4i) is being coded by one person alone. I believe you can donate if you want to help, just please be patient.
Quote from: Chuck J on March 16, 2013, 03:58:50 AM
Canon should pay these guys. Magic Lantern generates as much interest in canon products as canon's own marketing, maybe more.
If Canon paid them it would be to not write ML. They want you to pay more for those options in more expensive cameras. :)
That's correct. Canon and other hardware manufacturers are doing the same thing. Building the same products with minor (look) differences and are trying to sell the in different price groups disabling some options in the software. But this is another story.
r&d costs money as does testing and marketing. ml is saving them tons. don't be fooled by the corporate line that they don't want them to make this product or future products. it benefits canon to have these guys working their tails off. it keeps canon at the fore of the consumer digital film industry.
it's no different than making an app for a computer that makes it more productive
I'm happy to wait on such an awesome product. These guys have done some amazing things here and I look forward to using what they can offer when they can offer it.
Will be making another donation soon and will continue to do so with each job I do with there product.
Quote from: Lucas_W on March 16, 2013, 10:49:49 AM
Good thinking t4ilover, I originally tested at 720@60. I'm currently testing 1080@30 at 3x bitrate and it's still recording at 1 minute 48 seconds.
EDIT: It goes for 6 minutes before cutting off.
Do you think 1080@60 is going to be possible with t4i? it would be nice if this happens 8)
Highly doubtful.
I wonder if it would reduce most of the "when will it be ready" posts if the first post was reformatted into a status post? I am not talking about something fancy, but a simple "Start Here" type of thing. ???
Excited for this to be released! This sounds like very stable programming from what I've read... nobody's had their camera blow up. Thanks for all your hard work, I've never heard of this before today but it looks amazing! Although I'm unable to financially support, I'll give all the moral support I can :D Peace!
Quote from: Chuck J on March 16, 2013, 03:58:50 AM
Canon should pay these guys. Magic Lantern generates as much interest in canon products as canon's own marketing, maybe more.
I agree, its the only reason I choose Canon over Nikon or Sony. Its because of the people here at ML that I buy Canon.
The only Feature I hope is included on this first Alpha release is Bracketing I would like to see 9 or more if possible and unclipping of the +2/-2 to allow for +3/-3 aeb exposure. that would be the greatest gift for me that I could hope for on release alpha, i would test that feature to the ground.
again all props to the Developer and all the testers that were invited into pre-alpha.
Quote from: Chuck J on March 16, 2013, 02:59:23 PM
r&d costs money as does testing and marketing. ml is saving them tons. don't be fooled by the corporate line that they don't want them to make this product or future products. it benefits canon to have these guys working their tails off. it keeps canon at the fore of the consumer digital film industry.
it's no different than making an app for a computer that makes it more productive
Definitely not the same thing. Making an app to make your computer more productive doesn't make your computer ccapable of doing things that you would normally have to upgrade your computer to more expensive model to use . ML makes your for example 650/d do things that a much more expensive Canon can do. A $300 laptop can't be made to preform like a $1200 laptop does just with an App. There are no secret switches to turn on that will do that like a Canon.
Canon doesn't design or market their cameras as easily hack "sorry App upgradable" ::) so people will buy them. Yes we all like the fact Canons can be hacked but don't think they do that to attracted more customers. They save money by basically using similar (not necessarily identical) software and hardware in there models. They just turn on more futures the more expensive camera you purchase.
As far as research and development goes. Canon knows what their cameras can do but they turn off those features so you buy a more expensive camera to use them.
Yes the developers create a large amount of their own features for us and make it so we can use what we are locked out of. I love using and testing ML. But I can't say it enough Canon did not design their cameras so people can do that. If I were to bet, less than 1% of canons are purchased because they are ML hackable. Most likely that same 1% goes for ML users.
Quote from: baga on March 19, 2013, 05:27:06 PM
Canon doesn't design or market their cameras as easily hacked so people will buy them. Yes we all like the fact Canons can be hacked but don't think they do that to attracted more customers. They save money by basically using similar (not necessarily identical) software and hardware in there models. They just turn on more futures the more expensive camera you purchase.
As far as research and development goes. Canon knows what their cameras can do but they turn off those features so you buy a more expensive camera to use them.
Although this is the wrong forum for this topic, clearly some think that "hacking" which ML is NOT doing, is the same thing as developing software code, which ML
IS doing.
Canon turns on and off features based on it's ability to get the product to market within the parameters with the research and development available for the given hardware they put into their camera's.
As hardware quality and performance increase so to does the price. It's not a simple turn on or off a feature to make the price higher.
Some of the features that ML provides Canon Camera division is not permitted to provide because no compete laws with Video production.
As for making a computer more productive with software vs buying a faster computer? apples and oranges. no one said ML makes the cameras faster, just more productive.
Quote from: baga on March 19, 2013, 05:27:06 PM
If I were to bet, less than 1% of canons are purchased because they are ML hackable. Most likely that same 1% goes for ML users.
1% of 22.6 billion is how much? I'll take it!
Quote from: Chuck J on March 19, 2013, 09:05:34 PM
1% of 22.6 billion is how much? I'll take it!
Chuck I think you need to chill out!
Quote from: Chuck J on March 19, 2013, 08:50:16 PM
Although this is the wrong forum for this topic, clearly some think that "hacking" which ML is NOT doing, is the same thing as developing software code, which ML IS doing.
Canon turns on and off features based on it's ability to get the product to market within the parameters with the research and development available for the given hardware they put into their camera's.
As hardware quality and performance increase so to does the price. It's not a simple turn on or off a feature to make the price higher.
Some of the features that ML provides Canon Camera division is not permitted to provide because no compete laws with Video production.
As for making a computer more productive with software vs buying a faster computer? apples and oranges. no one said ML makes the cameras faster, just more productive.
Ok maybe hacking isn't the right word.
But again I was giving an opinion, I wasn't being rude or a jerk. I may not be as smart as you and/or apparently not as informed as you. But up until you I never ran into anyone here like you. People help each other and give opinions, share ideas.
Start over read the rules, introduce your self in the right forum.
What this isn't the place for is the way you are acting.
Read the forum rules Chuck. WE PLAY NICE HERE.
I am playing nice.
Sometimes modern society "tarnishes" the term "hacking" by trying to associate this term with terrorism, or illegal acts as defined in Merriam Websters dictionary: 4:b
intransitive verb
4.a : to write computer programs for enjoyment
b : to gain access to a computer illegally
When I see hacking i see the a form. and also to make something perform better. For instance if I needed a chisel for a job yet only had a screw driver and a grinding stone, I would be able to hack that screwdriver to function more like a chisel. 2. A car that gets 22 MPG if there can be a device that connects to a car that can allow it to get better gas milage or if you can modify the computer in the Car to get better gas mileage -- this is called hacking. And because I own the vehicle there should be nothing wrong with this activity.
Now the governments and corporations would have you think there is something wrong with "hacking" by saying "All Hacking is Terrorism". this is the Lie from the pit of Hell. So fear not the terms used to apply a computer generated program for our enjoyment as hacking to gain access to a computer illegally. I see this as modifying a product to make better use of it.
now that we are on the same page, if I use the term Hacking, I am not trying to use the "ohhh thats bad term". as this is clearly what hacking is not. not to me.
Sorry I am sure this was not the forum to define what "hacking is to me". but let us pull our efforts here and discuss possibility's of this T4i and what this Digic 5 can do and its limitations as well as be ready willing and able to log reports and tests with the Developers of this great software that we can use. As I have mention the only reason I chose Canon was that ML existed to enable my camera to perform better and more stable.
Quote from: buckbullstallion on March 19, 2013, 11:19:51 PM
I am playing nice.
Sometimes modern society "tarnishes" the term "hacking" by trying to associate this term with terrorism, or illegal acts as defined in Merriam Websters dictionary: 4:b
intransitive verb
4.a : to write computer programs for enjoyment
b : to gain access to a computer illegally
When I see hacking i see the a form. and also to make something perform better. For instance if I needed a chisel for a job yet only had a screw driver and a grinding stone, I would be able to hack that screwdriver to function more like a chisel. 2. A car that gets 22 MPG if there can be a device that connects to a car that can allow it to get better gas milage or if you can modify the computer in the Car to get better gas mileage -- this is called hacking. And because I own the vehicle there should be nothing wrong with this activity.
Now the governments and corporations would have you think there is something wrong with "hacking" by saying "All Hacking is Terrorism". this is the Lie from the pit of Hell. So fear not the terms used to apply a computer generated program for our enjoyment as hacking to gain access to a computer illegally. I see this as modifying a product to make better use of it.
now that we are on the same page, if I use the term Hacking, I am not trying to use the "ohhh thats bad term". as this is clearly what hacking is not. not to me.
Sorry buckbullstallion My thoughts were being pointed toward Chuck not you.
Quote from: Chuck J on March 19, 2013, 08:50:16 PM
Although this is the wrong forum for this topic, clearly some think that "hacking" which ML is NOT doing, is the same thing as developing software code, which ML IS doing.
Canon turns on and off features based on it's ability to get the product to market within the parameters with the research and development available for the given hardware they put into their camera's.
As hardware quality and performance increase so to does the price. It's not a simple turn on or off a feature to make the price higher.
Some of the features that ML provides Canon Camera division is not permitted to provide because no compete laws with Video production.
As for making a computer more productive with software vs buying a faster computer? apples and oranges. no one said ML makes the cameras faster, just more productive.
Lets start fresh. :) What version of ML are you using in your T4i/650d or are you using another model camera? Maybe that's why we have different opinions. Also quite a few of features ML can do haven't been activated yet and maybe that's why are opinions differ.
I dont see why you two are fighting all you do is speaking your mind which is allright!
From what i read there were no reason to feel that anyone of you were aggressive. Both were just stating facts but i can agree that the lecture you were given baga might been able to guide baga rather than trying to make him look like a know nothing which he is not! Remember we are in this forum to helåret an guide eachother! Not to fight and push eachother down to look superior!
On topic again:
Keep up the good work guys and i cant wait to get playing around and test the alpha when its ready! :D
It is a little bit of hacking, a lot of reverse engineering.
Canon doesn't add these things because they are bad at software development or don't actually go out and use their cameras... unless the HW guys have their own version or something (c'mon... leak it). You can't even fix the problem with money... none of the more expensive cameras are any better: they're still arbitrarily missing features, sometimes even lower tier features.
1dC has mjpeg 4k... so what... where is mjpeg 2k, 1080p? Where is raw HDR? Focus peaking?
Buying these bodies feels like buying a quad core pc that will only run solitaire and notepad. Truthfully 60% of it is probably so that they don't have to deal with end users questions.
ML isn't going to turn your 650D into a FF, turn SD into CF or speed up a physical shutter. These HW differences are what really separate the models in the end.
Don't mean to insult anyone in here but just for the sake of asking.
Isn't reverse engineering another type of a more sophisticate hacking?
Can an admin go through this post and delete all the junk that's appeared in it over the last few posts, including this one!
To summarise:
Hacker - http://en.wikipedia.org/wiki/Hacker (http://en.wikipedia.org/wiki/Hacker) Reverse Engineer - http://en.wikipedia.org/wiki/Reverse_engineer (http://en.wikipedia.org/wiki/Reverse_engineer)
Hacking covers a broad spectrum of skills, both good and bad, ML do not 'hack' anything. What they do is reverse engineer the cameras in order to gain a better understanding on how they can run custom code. Hacking, or as it's known in the industry 'Penetration Testing', is my day job - http://www.phillips321.co.uk/ (http://www.phillips321.co.uk/)
More importantly and back to the point: Unfortunately i have not used ML before and am patiently waiting for its release.... am looking forward to providing testing feedback when it arrives.
in order to get back on the subject:
I have been using the closed alpha, and the good news is that it works as it should. Nu hang, or other noteworthy spoilers. Oldo i do not test and use everything thats seems to be working.
I would donate time to Nanomad, however that seems to be impossible, until someone is able to hack/reverse engineer the time space continuum. I do see some activity on the 650D here https://bitbucket.org/hudson/magic-lantern/commits/all/ so that keeps me entertained, as for the majority I have no clue what is going on. I mean... dietlib atoi .... or ... allow x++/x-- on floats... its like reading an other language .. o wait.. it is!.
Well spring time is here, maybe a new alpha egg will be in the ML nest in the near future.
I apologize I was having one of those days where I couldn't retract my fangs and claws.
I make a big deal about nicely helping new posters stay on the right track and then I fell right into the trap of one of those posters that jump in, in the middle of a thread spew their nonsense and then go back into hiding.
Sorry again :-[
Quote from: 1% on March 20, 2013, 04:45:49 AM
Canon doesn't add these things because they are bad at software development or don't actually go out and use their cameras...
If Canon are bad at software development then how Sony guys are?
Calm down everyone :)
Just a quick update: With the help of Alex, I've fixed the last couple of bugs people reported during the "closed doors" alpha testing. I just need to find some time to commit it (as it's on my home PC) and properly re-test everything once again ;)
Quote from: nanomad on March 20, 2013, 04:21:28 PM
Calm down everyone :)
Just a quick update: With the help of Alex, I've fixed the last couple of bugs people reported during the "closed doors" alpha testing. I just need to find some time to commit it (as it's on my home PC) and properly re-test everything once again ;)
On your home PC???? You're an IT whiz, SSH home! ;) Cheers though, am looking forward to it (am on holiday this coming weekend so if you've got something out prior to then that would be grand)
Headed home to Chicago on Friday morning for a few days. Any chance it'll be available by late late Thursday night so I can test it out over the weekend? I'm not REALLY asking when it will be done, just if I'll be able to test it over the weekend. :)
If there is any testing I can do with my 650D I would be pleased to help out if I can, will be making a donation once the alpha is out :)
Quote from: alesis_neo on March 20, 2013, 11:15:25 PM
If there is any testing I can do with my 650D I would be pleased to help out if I can, will be making a donation once the alpha is out :)
You can try the alpha but have to compile it yourself. I thought about doing it myself but think i'll just wait. You obviously have to have experience compiling software.
Hello all at ML. What a wonderful international community this is. Why cannot the whole world act as unified as this? its marvellous. I have owned a 650D for about 6 months and am eagerly awaiting to try out Ml on it. Can you advise me on how i go about downloading software and the safe way to install it and open please? I currently have no work but west assured i will make a donation fro my first job which fingers crossed i have lined up which is a low budget fly on the wall documentary with a band that are about to tour pending the release of their new album albeit on a low budget. ( i am hoping to earn enough to possibly afford a 5Dmk3 if all goes well but thats wishful thinking! Do i simply follow the attachments and other options link below? This is such great timing you guys and i hope to be able to send you an example of my results in the near future! ;D
Welcome, you have 29 pages to find out.
TIP: There's no public version, yet.
i will await for the public version as i am new to all this and do not have the money to replace camera if i screw up with test versions! many thanks once again.
regards, paul
While following this thread and waiting for a release, i have come across a small prob with my t4i that I was wondering if anybody else sees. The firmware setting to DISABLE touch shutter always self-enables. I think it has something to do when I change modes from M to HDR, it seems to reset the touch shutter.
Anybody else see this problem? Not my imagination as I frequently have to go back into menu and set to DISABLE.
Might lead to ML fixing a prob with core T4i firmware.
Best,
Peter
Well, the 700D is nearly identical to the 650D. I think we can safely say ML should be able to support the 700D without a lot of effort.
http://www.dpreview.com/previews/canon-eos-700d-rebel-t5i
Quote from: momendo on March 21, 2013, 06:26:17 AM
Well, the 700D is nearly identical to the 650D. I think we can safely say ML should be able to support the 700D without a lot of effort.
http://www.dpreview.com/previews/canon-eos-700d-rebel-t5i
Not one single model has been ported without "a lot of effort." You can safely say that the 650D isn't even in alpha stages.
Hi guys, finally yesterday I ordered my 650D, of course after only one day, canon announced the new 700d camera. I hope the ML 650 will not die on the pre-alpha stage.
If you need any help please send me a PM. I am ready to join the team, I have some programing, developing and testing knowledge.
Previously I worked on an Arduino based DSLR controller (developing the hardware and also the software).
relax, 700D has no major upgrade from 650D. well.. apparently. long live 650D!
Quote from: 1% on March 20, 2013, 04:45:49 AM
Canon doesn't add these things because they are bad at software development or don't actually go out and use their cameras...
Canon doesn't add these things because people buy their cameras anyway, so way take the risk, rock the boat and add features few (in comparison to sales) Rebel users use ... after all everything Canon puts in the fw has to be 100% working, documented and supported, unlike ml. Too many features would even get "too complicated for beginner" reviews, and professionals on 1d(x/c) put reliability over features.
True but they have the option to test things. If its going to confuse new users sure... but new users are buying 6D/5d3?
Oh and that review says 700D has mjpeg. Tilt screen too + one handed controls. Looks pretty win, hopefully they didn't cripple the idle buffer like 650D... those sizes are horrible. Still no crop mode though. Hopefully they fixed UHS to support newer cards.
Quote from: 1% on March 21, 2013, 03:59:07 PMOh and that review says 700D has mjpeg.
I find it odd that no one else has mentioned MJPEG other than DPReview, you'd think Canon would have put it in the press release? 'MJpeg for even better video recording!' that seems like a nice marketing line.
Mjpeg would be nice, but I'm not about to get a T5i for it. I have a T2i and a T4i, a T5i would be an incremental upgrade, my going plan is to save up and get something like a Canon 6D around Black Friday. Maybe a 7D Mk 2 if it comes out and is attractive.
With all these Canon cameras constantly coming out, do you ML devs ever find yourselves going 'TOO MANY CAMERAS! D:'?
6D video quality is kinda meh. There is a reason they are still selling 600D even after 650d (and 700D) came out...
Hopefully the "hdmi" update addresses resizing issues on 6D too.... would be nice if they backported the mjpeg to you know.. a camera that costs 3x as much?
They are saying 1dc has problems with high motion/high iso and mjpeg and card speed is limited to 100Mb/s... da fuq? Even digic IV cranks out almost 200.
QuoteQuality is amazing in natural daylight portrait, but is less interesting in action high iso scene. They are aware of that and the "limit is the card writting speed" at 100Mb/s.
http://www.canonrumors.com/2013/01/canon-eos-1d-c-information/
Quote from: 1% on March 21, 2013, 07:51:56 PM
6D video quality is kinda meh.
I have need for the ISO performance it offers and the 5D is rather costly. I'm shooting a short film, police procedural, on a T2i running ML (Have a T4i waiting for ML as well) and for much of the shooting it's fine, but in a few locations we couldn't control the light enough and we wanted a wider depth of field. We were left using a shallower depth of field because we needed a wider aperture to deal with the fact that the T2i gets pretty noisy and loses dynamic range above ISO 800. The scene is lackluster as a result cause we're chasing focus while characters walk and talk down a hall.
That said, this is also why I have my eyes on what the 70D or 7D Mk 2 could offer.
Quote from: baga on March 20, 2013, 12:09:57 AM
Lets start fresh. :) What version of ML are you using in your T4i/650d or are you using another model camera? Maybe that's why we have different opinions. Also quite a few of features ML can do haven't been activated yet and maybe that's why are opinions differ.
I'm not really a jerk. I just play one on TV. My T4i/650d is without my beloved Magic Lantern until it comes out of pre-alpha hiding. Prior to my T4i I used a T2i with Magic Lantern. I very much miss Magic Lantern and purchased my T4i hoping and praying that one day it too would be graced with the powers of this software, hackware, or whatever you guys want to call it.
To clear up my rantings from before I love canon cameras and I love them even more with Magic Lantern. I will defend them both and sometimes it makes me sound like a jerk. I'm sorry for that. :-\
Just a suggestion, I thought that if you could add a setting that pulls the mirror up before taking the picture; that could reduce camera shake. Maybe add a setting that let you decide how much time to keep the mirror up before taking the picture.
JUST an idea from a guy that has NO experience in this but knows it's a challenging thing to do. So if you think this would be worth adding, that'd be awesome. But I definitely don't expect you to do it if you don't want to :D I'm very happy with all the features you've already added and I don't want to be a pain. Thanks for all your work!
@BrightGarden, I just turned my setting, touch to shoot, off, went to HDR and back, but the setting was still off. I guess I don't have that problem. However, I have noticed that it's turned on a couple of times without me setting it... I thought I was losing my mind, I guess not.
Quote from: Taynkbot on March 22, 2013, 03:36:21 AM
Just a suggestion, I thought that if you could add a setting that pulls the mirror up before taking the picture; that could reduce camera shake. Maybe add a setting that let you decide how much time to keep the mirror up before taking the picture.
JUST an idea from a guy that has NO experience in this but knows it's a challenging thing to do. So if you think this would be worth adding, that'd be awesome. But I definitely don't expect you to do it if you don't want to :D I'm very happy with all the features you've already added and I don't want to be a pain. Thanks for all your work!
Menu -> WRENCH:4 ->Custom Functions -> Mirror Lockup -> Enable
1st shutter press locks mirror up, 2nd takes shot. You can also use with timer. Mirror will lock up on shutter press then take the picture 2 or 10 seconds later. Check out page 140 in the Canon t4i manual for more info.
Thanks devs and testers for all the work!
Quote from: Taynkbot on March 22, 2013, 03:36:21 AM
Just a suggestion, I thought that if you could add a setting that pulls the mirror up before taking the picture; that could reduce camera shake. Maybe add a setting that let you decide how much time to keep the mirror up before taking the picture.
JUST an idea from a guy that has NO experience in this but knows it's a challenging thing to do. So if you think this would be worth adding, that'd be awesome. But I definitely don't expect you to do it if you don't want to :D I'm very happy with all the features you've already added and I don't want to be a pain. Thanks for all your work!
@BrightGarden, I just turned my setting, touch to shoot, off, went to HDR and back, but the setting was still off. I guess I don't have that problem. However, I have noticed that it's turned on a couple of times without me setting it... I thought I was losing my mind, I guess not.
It's not a bad idea at all. Nikons have had this feature for quite some time, at least since the d5000, called steady mode or something along those lines. Its very good for shooting slow shutter, so that the shutter itself doesn't slightly vibrate your shot. Good call. Not a top 10 priority kind of thing, but great idea.
Quote from: diy-greenenergy on March 21, 2013, 08:41:27 AM
Hi guys, finally yesterday I ordered my 650D, of course after only one day, canon announced the new 700d camera. I hope the ML 650 will not die on the pre-alpha stage.
If you need any help please send me a PM. I am ready to join the team, I have some programing, developing and testing knowledge.
Previously I worked on an Arduino based DSLR controller (developing the hardware and also the software).
That totally burns! My main concern is getting a proper build with Kelvin WB controls on the 650d before its abandoned (if it gets abandoned). Also, the 700d will likely not take a whole lot of work for the port from wherever the current build of 650d ML is at the time of that project start, considering it's basically a T2i-T3i type of jump. The 700d is basicallty a slightly tuned 650d.
Why the hell did Canon have to make a t5i so damn fast?!
dngrhm, hey, thanks! I forgot about that trick. For some reason I was thinking it wasn't working with my remote. I guess it flips up two seconds before and then takes the picture.
Anyway, thanks again :D
Quote from: 1ricca on March 23, 2013, 03:35:40 AM
That totally burns! My main concern is getting a proper build with Kelvin WB controls on the 650d before its abandoned (if it gets abandoned). Also, the 700d will likely not take a whole lot of work for the port from wherever the current build of 650d ML is at the time of that project start, considering it's basically a T2i-T3i type of jump. The 700d is basicallty a slightly tuned 650d.
Why the hell did Canon have to make a t5i so damn fast?!
Looks like the same camera but they put back the crop zoom, that is probably the most irritating thing of all unless they offer a firmware update to enable it in the t4i.
Quote from: 1ricca on March 23, 2013, 03:35:40 AM
That totally burns! My main concern is getting a proper build with Kelvin WB controls on the 650d before its abandoned (if it gets abandoned). Also, the 700d will likely not take a whole lot of work for the port from wherever the current build of 650d ML is at the time of that project start, considering it's basically a T2i-T3i type of jump. The 700d is basicallty a slightly tuned 650d.
Why the hell did Canon have to make a t5i so damn fast?!
Right. I finally got my first DSLR after wanting one for about 2 years. Got a T4i a little over a month ago and haven't even got to really use it yet and now the T5i. I really hope ML for the T4i doesn't get scrapped, if that happens i'd have to sell my T4i for a loss. Yeah ML being in development for the T4i was honestly a pretty big factor when I purchased.
Quote from: Seanoneil72 on March 23, 2013, 04:40:27 AM
Looks like the same camera but they put back the crop zoom, that is probably the most irritating thing of all unless they offer a firmware update to enable it in the t4i.
What? They added crop zoom to T5i? I really didn't know about moire when I made my purchase. Would be really nice if that firmware update actually happened but I doubt it.
Edit: Maybe this can be done through ML(can't believe I didn't think of this before)? if so it is a feature that will be implemented in the 650D ML release?
If crop mode is in T5i, I wouldn't advise you to add it in ML ;)
Yesterday I got my 650D but, unfortunately, it is affected by the rubber grip problem (http://www.apcc.tk/photography/canon-650d-rubber-grips-problem). Be carefull, affected cameras are still on the market!.
After I contacted the seller they offered me an instant replacement.
Quote from: a1ex on March 23, 2013, 09:26:45 AM
If crop mode is in T5i, I wouldn't advise you to add it in ML ;)
:-X
8) I am too impatient to use on my 650D ML provided that it does not too late
I board which makes a
good luck to devlopeur
If they added crop and mjpeg it means they are listening.... anyways they aren't going to make 650D anymore.
Quote from: Chuck J on March 22, 2013, 01:53:58 AM
I'm not really a jerk. I just play one on TV. My T4i/650d is without my beloved Magic Lantern until it comes out of pre-alpha hiding. Prior to my T4i I used a T2i with Magic Lantern. I very much miss Magic Lantern and purchased my T4i hoping and praying that one day it too would be graced with the powers of this software, hackware, or whatever you guys want to call it.
To clear up my rantings from before I love canon cameras and I love them even more with Magic Lantern. I will defend them both and sometimes it makes me sound like a jerk. I'm sorry for that. :-\
Same here. :)
I really hope you guys continue to finish ML for the T4i. The T5i doesn't look like that much of an upgrade from the T4i and I don't want to have to waste the money on it.
Just letting you know I'd REALLY appreciate if you continued programming the T4i's ML. You guys are awesome!
Quote from: Taynkbot on March 23, 2013, 09:13:50 PM
I really hope you guys continue to finish ML for the T4i. The T5i doesn't look like that much of an upgrade from the T4i and I don't want to have to waste the money on it.
Just letting you know I'd REALLY appreciate if you continued programming the T4i's ML. You guys are awesome!
It sucks they came out with the T5i before they even upgraded the T4i firmware. Why couldn't they have called it the T4iV or something. lol
@Baga
I know right? It seems more like a firmware update than a new camera. A new 360 turn-able dial? A new body finish? Come on! I really hope that the lack of work they put into the T5i went into the 7DMKII.
Quote from: newsense on March 23, 2013, 04:43:04 AM
Right. I finally got my first DSLR after wanting one for about 2 years. Got a T4i a little over a month ago and haven't even got to really use it yet and now the T5i. I really hope ML for the T4i doesn't get scrapped, if that happens i'd have to sell my T4i for a loss. Yeah ML being in development for the T4i was honestly a pretty big factor when I purchased.
Same boat here. I waited a few months to purchase my T4i because of the grip/rubber issues. Now that I have had it a couple of months, a new model gets released. This always seems to happen when I finally buy something expensive. *sigh* Oh well, at least now that I have my first DSLR, I can start learning.
Quote from: ChodaBoy on March 24, 2013, 06:49:38 AM
Same boat here. I waited a few months to purchase my T4i because of the grip/rubber issues. Now that I have had it a couple of months, a new model gets released. This always seems to happen when I finally buy something expensive. *sigh* Oh well, at least now that I have my first DSLR, I can start learning.
I realized I had an extended return period due to being a silver member at my retailer and could have returned my T4i but I got it for such a steal at $639.99 new with 18-55mm lens plus the only added features the 700D has is really just digital zoom and MJPEG from what I hear. Even if I payed full price I think i'd keep the 650D just for ML since it's close to Alpha now and it was a big selling point for me.
QuoteJust a suggestion, I thought that if you could add a setting that pulls the mirror up before taking the picture; that could reduce camera shake. Maybe add a setting that let you decide how much time to keep the mirror up before taking the picture.
JUST an idea from a guy that has NO experience in this but knows it's a challenging thing to do. So if you think this would be worth adding, that'd be awesome. But I definitely don't expect you to do it if you don't want to I'm very happy with all the features you've already added and I don't want to be a pain. Thanks for all your work!
This guy have a great idea! other one said that yes, the mirror lock up is on the t4i, however is not the live view mode a permanent mirror lock up? but I wonder, WHY, just WHY! in live view the mirror have to at the end of each photo "SLAP!!!" going down and then "SLAP!!!" going up? in the process disturbing people. I consider myself a candid shooters and this does not help me. I'm in live view mode!!!why the camera have to do this?
Is there a way to keep the mirror up in live mode and keep it there as long I use live view? just imagine the smooth sounds of the shutter without the slap of the mirror.
If not, I think this would be a good idea magic lantern for candid shooters, this would me save to buy another camera
Btw i got feedback from the testers for the second closed doors alpha. No major bugs so far but it needs a couple of more tweaks
Quote from: Taynkbot on March 24, 2013, 12:49:12 AM
@Baga
I know right? It seems more like a firmware update than a new camera. A new 360 turn-able dial? A new body finish? Come on! I really hope that the lack of work they put into the T5i went into the 7DMKII.
I don't think I'd like a 360 dial. I read some where about it was over the pealing and faded grips. Sounds like a lame excuse to me. I haven't read all the specs but a firmware upgrade and body is all I see too. If it's smaller and/or lighter I'd hate it. I have the battery grip just to give the T4i some bulk. I also like my larger kit lens.
I like my T4i and will keep thinking of it as an upgraded to the T5i. lol
On 6D the 360 dial has a button in the middle. you have to press it to turn the dial. That part is not so convenient.
Agree with baga t4i is an upgrade to the t5i and ever spinning dial forces you to look at what setting you are stopped on. Maybe canon used the t5i as a means to be rid of the grip recall issue?
;D
Quote from: nanomad on March 24, 2013, 02:22:25 PM
Btw i got feedback from the testers for the second closed doors alpha. No major bugs so far but it needs a couple of more tweaks
Hi @all, 2 Weeks ago i sell my 550d with ML, cause my Birthday Gift on Thuesday will be a used 650d(bought myself :(), but my favorite Gift would be the release of the ML for the 650d, I Thank everyone who helps to develop this Great Peace of Firmware. Good Luck and Thanks!
Happy BDay in advance, welcome to the waiting list :)
Just wanted to let you know I'm yet another person who will be delighted when this port is ready for the world! And if I come into any extra cash (after what I dropped on the camera...) I'll donate to your coding activities. Keep up the awesome.
Quote from: Chuck J on March 24, 2013, 07:24:14 PM
Agree with baga t4i is an upgrade to the t5i and ever spinning dial forces you to look at what setting you are stopped on. Maybe canon used the t5i as a means to be rid of the grip recall issue?
I agree, it's like they just wanted that bad taste to go away. As far as the dial I know where everything is by the stops. It's like the XTi dial. I just use my thumb or index finger to roll it.
Oh well it seems we all love our T4i's especially with ML on it. I still might have made the same choice just for the better kit lens.
Hi, I've never posted here and I'm new and this is my first post. I've been reading this hole thing and have some questions. I read every post, but couldn't find the answer to when is this thing coming out for t4i? Also since the pay version isn't out can I buy the free version now so I can go ahead and used it? Also some of the features that I don't understand. Will ML, is it ok if I call it that, be able to make my t4i lighter weight because I have carpet tunnel syn drome and it is too heavy. And can ML be put in a case when not to be using? Also, will I can use it in automatic green box mode because that's the only mode I no how use. This is it's my first post.
(Sorry guys, I had to...) =P Hope I didn't get anybody upset. Just wanted to add a little humor. I've been following this for some time now and some of the questions I see asked, just annoy me a bit, lol. No biggie, just wanted to have some fun. Now back to your regularly scheduled... whatever it was you were doing...
Have a good day!
Stephen
LOL :o
Nikon fanboys trolling the ML forums I see.
Lol,
However if you would have read the whole post you would know that we are planning to hack the space time continuum. After completion we will implement all future canon and mll features yesterday. So in fact it is already here. And that includes the antigravity function from the eos xx980d extreme from 2042.
Lol! No, I'm actually a Canon guy. Had the old film Rebel XS and recently got a t4i. Loving it so far! As for having the space time continuum, I'm going to go ahead and install ML on my phone, as soon as I wake up yesterday! It will be the best picture phone ever! ;-)
In all seriousness, keep up the good work devs! Thanks for all you do!
Quote from: alaricoxagaras on March 24, 2013, 11:19:15 AM
"SLAP!!!" going down and then "SLAP!!!" going up?
Agreed - a true mirror lockup would be great - I think this is how it used to work on my film Nikon 8008s.
I was at a veterans event today and knew my T4i was "slapping" too loud from the back where I was shooting from. Wanted to make sure I didn't miss a good shot of a flag raising and had it in continuous mode. Not a good thing - was way too loud and obnoxious. I would hate to have to get a mirrorless just for that reason.
Ok guys, this is a huge issue for me and I can't find a thread or any info about it anywhere. Starting to think I might have a defective unit. Here goes:
When I'm in Stills Mode (power switch set to ON not VIDEO), and I'm shooting in M mode (manual exposure), and I go to use Live View, my live view screen is insanely darker than it should be. I take a picture and it looks how it should have looked. If I switch back to video mode on all the same settings, the live view shows exactly what my still came out to be.
Here's the real kicker... If I flip my on-camera flash open while in Live view on M mode, suddenly my live view shows accurately what my settings will look like, close the flash and take the shot, BOOM, perfectly what it looked like in the live view screen WHILE the flash was open. If I take the shot with the flash, naturally it's flashy.
This doesn't happen in Aperture Priority or Shutter Priority. Only Manual Exposure (M), in STILLS Mode with Live View. At least I finally found the little trick with popping my flash open, but it is a huge pain having to pop it open just to see my live view properly and then closing it before I take the shot.
So... anyone else able to reproduce this? This is a HUGE bug, unrelated to ML, but VERY related to this camera being about 20% the original awesomeness I planned it to be. Any help or info is super appreciated. I already read this thread and post to it all the time and I figured you guys would be a lot more helpful than anywhere else :)
Can not reproduce here on my 650D, so I'm sorry (or glad, depending on how you look at it) to say but it must be a defect on your camera...
Just a quick question, don't want to sound rude.
But what shutter speed and aperture do you have set?
Because that does control the live view.
That is at 1/4000 I have a black screen but at 1/20 it is all OK.
Flipping up the flash does brighten this, as they will assume that there will be more light when the shot it taken.
Quote from: caerbannog on March 26, 2013, 03:12:39 AM
Just a quick question, don't want to sound rude.
But what shutter speed and aperture do you have set?
Because that does control the live view.
That is at 1/4000 I have a black screen but at 1/20 it is all OK.
Flipping up the flash does brighten this, as they will assume that there will be more light when the shot it taken.
I was expecting the first reply to be like this...
If you read the entire post, when I switch to any other mode (A, S, Video, etc) with the exact same settings, all is fine. Also, in my post I said that when I actually TAKE the picture, it's the way it should be and the way it looks in the other modes.
My settings are irrelevant. It shows a preview of what looks to be the wrong exposure settings when, in fact, the settings are perfect. Taking a picture yields what my settings SHOULD yield. Live View is simply showing the wrong feedback.
To re-iterate:
Power Switch set to ON
Mode Dial set to M
Live View ON
Showing my live preview as though my ISO is set to 100
Power Switch set to ON
Mode Dial set to anything other than M
Live View ON
Showing my live preview accurately
Power Switch set to VIDEO
Mode Dial set M
Showing my live preview accurately
Power Switch set to ON
Mode Dial set to M
Live View ON
Flash Popped Up
Showing my live preview of what my still will look like WITHOUT a flash (EXACTLY what it will look like and EXACTLY what it looks like in the other mentioned scenarios)
QuoteI was expecting the first reply to be like this...
You must've missed my reply. I did not assume you were stupid... ;)
Quote from: 1ricca on March 26, 2013, 03:21:40 AM
I was expecting the first reply to be like this...
If you read the entire post, ...
Try to not bite the hand that feeds you. They cared enough to try to help you, they posted for the first time. Welcome caerbannog and michel!
I'm not experiencing what you are talking about in M mode. Try resetting to default settings and try again. If you experience the same thing, there is likely an issue with the camera. Good luck.
Menu -> WRENCH:4 -> Clear Settings -> Clear All Settings
Quote from: dngrhm on March 26, 2013, 04:28:31 AM
Try to not bite the hand that feeds you. You are posting a troubleshooting question to a development thread. ...and they cared enough to try to help you, they posted for the first time. Welcome caerbannog!
I'm not experiencing what you are talking about in M mode. Try resetting to default settings and try again. If you experience the same thing, there is likely an issue with the camera. Good luck.
Menu -> WRENCH:4 -> Clear Settings -> Clear All Settings
Thanks for the help. Unfortunately I have installed ML on numerous cards and reset the settings along with each of those times. I was part of the initial Pre-Alpha 1 tests. The only other factor I failed to mention is that this is happening with lenses that are on adapters. I have Nikon glass only right now for my T4i right at this moment. I don't have any Canon lenses to test against this atm.
Just to triple-check, you tried this in non-video mode on M on a higher ISO?
I really hope this model isn't defective.
Quote from: michel on March 26, 2013, 03:04:54 AM
Can not reproduce here on my 650D, so I'm sorry (or glad, depending on how you look at it) to say but it must be a defect on your camera...
Thanks michel. I didn't see your post until just now. Tiny phone screen :)
I just cringe at the strange cultural trend in this world of people questioning a post as opposed to replying to it. The screen is darker than the shot it is spitting out in one specific scenario... why would my shutter speed and aperture be in question? lol.
Was sort of a "did you plug it in?" type of response.
Quote from: 1ricca on March 26, 2013, 04:58:18 AM
Thanks for the help. Unfortunately I have installed ML on numerous cards and reset the settings along with each of those times. I was part of the initial Pre-Alpha 1 tests. The only other factor I failed to mention is that this is happening with lenses that are on adapters. I have Nikon glass only right now for my T4i right at this moment. I don't have any Canon lenses to test against this atm.
Just to triple-check, you tried this in non-video mode on M on a higher ISO?
I really hope this model isn't defective.
That's a horse of a different color. I missed that you had the pre alpha. Also the lens adapter with Nikon lenses could be doing some very strange things. It would be very relevant to testing the pre alpha if you don't have these problems with a ML-less card or ML disabled (hold set on startup I think). I am not running with the alpha and can only confirm it is not a problem on vanilla T4i. I would assume the same for michel and caerbannog.
Quote from: dngrhm on March 26, 2013, 05:08:05 AM
That's a horse of a different color. I missed that you had the pre alpha. Also the lens adapter with Nikon lenses could be doing some very strange things. It would be very relevant to testing the pre alpha if you don't have these problems with a ML-less card or ML disabled (hold set on startup I think). I am not running with the alpha and can only confirm it is not a problem on vanilla T4i. I would assume the same for michel and caerbannog.
I've tried it vanilla. It was happening before I installed ML too. I just always assumed I must be missing some setting somewhere for "constant preview" or something along those lines that was affecting it, but I was wrong.
It's strange too because if it WAS the 3rd party glass, why is it only happening in one very specific scenario and fine in every other way. One way or another, this is CERTAINLY a software bug I am experiencing. I'm not really looking for "help" with it.
Simply trying to see if anyone could reproduce the issue. If anyone can reproduce, it's a firmware bug. If not, my camera is defective. I will make a short video of the issue and post a link, but I will try and not flood this thread with the issue. Just wanted to see if all my fellow advanced tweakers have experienced this or not :)
This is the result of using nikon lenses with an adapter. Im having the same issue with vanilla 650D. My workaround is just not using liveview when taking photos with that lens!
Btw its a samyang 8mm fisheye lens in case you wondered! :)
Quote from: 1ricca on March 26, 2013, 05:18:24 AM
Simply trying to see if anyone could reproduce the issue. If anyone can reproduce, it's a firmware bug. If not, my camera is defective. I will make a short video of the issue and post a link, but I will try and not flood this thread with the issue. Just wanted to see if all my fellow advanced tweakers have experienced this or not :)
Dont worry as i said i have the same isue with the nikon lens but my kit lens is working fine! So either its just that nikon lenses are not made for canon cameras (Capten obvious) or we both gotten ourself defective cameras! At least we are not alone! :D
Quote from: Ivarss on March 26, 2013, 05:29:57 AM
Dont worry as i said i have the same isue with the nikon lens but my kit lens is working fine! So either its just that nikon lenses are not made for canon cameras (Capten obvious) or we both gotten ourself defective cameras! At least we are not alone! :D
Huge relief. Maybe now that we know it is a widespread bug, there's some small hope of a FW or ML fix for it in the distant future.
Edit: Tried it with my 24-105mm F4 L-Series from my office and it's fine. Thought it was doing it at first but I was mistaken.
Thank you so much Ivarss and to all who checked on their T4i. You all just made my day :)
On any other forum, it would have wound up being a confusion fest leading to accusations of me setting my camera up wrong or not understanding shutter speeds or some non-sense ;)
Now at least everyone knows of this issue and that there IS a workaround with temporarily opening the on-camera flash or simply switching to SHUTTER PRIORITY. Switching to Shutter-priority lets you still do everything manually since you have to set the aperture manually on your lens anyway... so long as Auto-ISO and Auto-Lighting Optimizer are off {which I hope would be ;) }
Edit: I had typed aperture-priority but meant shutter. Its fixed now above.
http://www.dvxuser.com/V6/archive/index.php/t-247001.html
https://groups.google.com/forum/?fromgroups=#!topic/ml-devel/8cnLT_FjgIw
This is a Canon bug, present on all cameras that I've tried. ML has a fix for it, just enable exposure override ( http://wiki.magiclantern.fm/userguide#expoverride ).
Quote from: a1ex on March 26, 2013, 08:48:40 AM
http://www.dvxuser.com/V6/archive/index.php/t-247001.html
https://groups.google.com/forum/?fromgroups=#!topic/ml-devel/8cnLT_FjgIw
This is a Canon bug, present on all cameras that I've tried. ML has a fix for it, just enable exposure override ( http://wiki.magiclantern.fm/userguide#expoverride ).
OMFG I love you. Totally worked. Perfect for full time M mode peeps like myself.
Hello to all you fellows
Just to introduce myself shortly: my name is Robert, I'm from Germany and I'm new to this forum and to digital photography.
Been using mit Canon AE1-Program and my T90 (all manual focus for the younger guys - I'm not so old btw, in my mid fortys) and medium format Mamyia RB and RZ.
Now that my beloved 75-300 Apo lens died I had to think of either getting a new MF lens or to switch.
Bad thing - all my loved FD lenses don't fit on EF/EF-S (I now there is an adapter but with the lens for infinity focus in the adapter my 17mm super wide angel is gone :-[ )
So I decided to switch and got the EOS650D in autumn last year. Searching the web I found out about MagicLantern and I get more and more excited about it every day I read and think about it.
I haven't been into video at all before but all this here fascinates me more and more.
So I'm totally desperate for the release of ML for my EOS650D and hope so much that you fantastic guys don't skip the project now that the 700D is out.
so much said - but nothing of importance ;) - I just wanted to thank you here for the fantastic work you do and can't wait to use ML
May I ask how is the alpha going?
I don't mean to pressure anyone just would like an update on it for all of us Magic Lantern lovers that can't wait for it to come out, I check every reply on this post hoping its good news about the alpha :P
Thanks to the developers for all of their dedication on making our cameras so much better and functional :D
Good morning, and congratulations for your project!
I own a 650D and I'm wondering if there's the possibility to set up a "Touch Focus" function, where you touch the point to focus on the screen and the machine focuses it.
It already does it but it shots a photo after focusing. I don't want that it shots the photo immediately :(
Anyway, you are doing an amazing work, I've seen it working on a 5D ;D
Quote from: BrunoLiegi on March 28, 2013, 09:52:23 AM
Good morning, and congratulations for your project!
I own a 650D and I'm wondering if there's the possibility to set up a "Touch Focus" function, where you touch the point to focus on the screen and the machine focuses it.
It already does it but it shots a photo after focusing. I don't want that it shots the photo immediately :(
Anyway, you are doing an amazing work, I've seen it working on a 5D ;D
Turn off "touch shutter" and it will just focus on selected area.
Quote from: laame on March 28, 2013, 10:28:30 AM
from: BrunoLiegi on Today at 09:52:23 AM
Good morning, and congratulations for your project!
I own a 650D and I'm wondering if there's the possibility to set up a "Touch Focus" function, where you touch the point to focus on the screen and the machine focuses it.
It already does it but it shots a photo after focusing. I don't want that it shots the photo immediately :(
Anyway, you are doing an amazing work, I've seen it working on a 5D ;D
Turn off "touch shutter" and it will just focus on selected area.
One note - I have a bug in my 650D and wondering if any of you see it - I disable "touch shutter" but it keeps re-enabling itself.
I will be shooting stills and touching the screen to move the focus box and it will shoot a pic.
Or, in video mode, I touch the screen and it takes a still shot.
I then have to go into the menu and disable touch shutter again.
Getting annoying and I am watching for a release of new firmware from Canon, hoping they fix this.
I can't believe it is happening only my camera, I would have to think that it has to be all 650D's.
Anyone else see this?
Quote from: BrightGarden on March 28, 2013, 12:08:22 PM
One note - I have a bug in my 650D and wondering if any of you see it - I disable "touch shutter" but it keeps re-enabling itself.
I will be shooting stills and touching the screen to move the focus box and it will shoot a pic.
Or, in video mode, I touch the screen and it takes a still shot.
I then have to go into the menu and disable touch shutter again.
Getting annoying and I am watching for a release of new firmware from Canon, hoping they fix this.
I can't believe it is happening only my camera, I would have to think that it has to be all 650D's.
Anyone else see this?
Well, my T4i works just fine and I don't have that issue. Is there sny chance you get a replacement?
Quote from: BrightGarden on March 28, 2013, 12:08:22 PM
One note - I have a bug in my 650D and wondering if any of you see it - I disable "touch shutter" but it keeps re-enabling itself.
I will be shooting stills and touching the screen to move the focus box and it will shoot a pic.
Or, in video mode, I touch the screen and it takes a still shot.
I then have to go into the menu and disable touch shutter again.
Getting annoying and I am watching for a release of new firmware from Canon, hoping they fix this.
I can't believe it is happening only my camera, I would have to think that it has to be all 650D's.
Anyone else see this?
Yes, I have the same issue, but I don't use LiveView for photography.
Usually I just check TouchShutter icon on screen before tap focusing.
Sorry for you, BrightGarden and laame, but at my 650D it works flawless like on cafer35's.
As well in photo as in video mode.
Best, Robert
Hi guys,
Sorry to chase but any idea when a public beta might be available?
Or is it very much like Debian; "It will be done when its done"?
Many thanks to all the devs and I am willing to test the beta (gather its a closed alpha at the moment?)
Cheers guys
Phillips321
That seems correct. It's done when its done. I am testing a closed alpha, and as far as I know there are still a few bugs that need to be fixed before a public realease.
I have no coding skills so a can only speed up the process by testing. But even only testing consumes a lot of free time.
I think that it's a wise disision not to rush the alpha, and to realease a more or less stable code when the time ripe.
Damn, when I'm getting an email with "Topic reply: Canon 650D [Status: Hello, world!]", I'm running like hell to the PC, hoping that there's something new.
Later I realize that someone has nothing better to do, than bugging dev's with the same question.
Sit back, relax and enjoy Easter.
Happy Easter everyone!
Yep, still fixing bugs. Closed doors testing really helps nailing down bugs since people actually test the features. The FPS override bug should be fixed now, so expect another build soon.
My camera is willing o help in case you need it Nanomad! Otherwise i be happy to wait and help you guys when you release it for open! :)
Run luplo, RUN :D! - sorry, you can just sit back :P
Great to hear the progress nanomad! I tested todays nightly since i saw some activity around the FSP override in "hudson" yesterday, but still had crash after end of recording. But i assume from what you wrote that i will also need a newer .fir before it's fixed.
Testing nightlies it's pointless since you need an updated fir.
Quote from: Phillips321 on March 31, 2013, 12:54:21 PM
Hi guys,
Sorry to chase but any idea when a public beta might be available?
Or is it very much like Debian; "It will be done when its done"?
Many thanks to all the devs and I am willing to test the beta (gather its a closed alpha at the moment?)
Cheers guys
Phillips321
Long time Debian user, never expected to see a Debian ref here. Funny one too, haha.
Hi!
I have a 650D, and maybe I can help by testing the 'closed doors alpha' versions, if needed.
I have experience with CHDK on my SX110, which I used for years.
If I can be helpful, please contact me.
Congratulations for the job with Magic Lantern. I read the userguide and watched some videos. It's really (really!) impressive.
Quote from: RafaLibrenz on April 02, 2013, 03:24:08 AM
Hi!
I have a 650D, and maybe I can help by testing the 'closed doors alpha' versions, if needed.
I have experience with CHDK on my SX110, which I used for years.
If I can be helpful, please contact me.
Congratulations for the job with Magic Lantern. I read the userguide and watched some videos. It's really (really!) impressive.
Not sure how they pick there closed door Alphas but i'm guessing it's people that have been active in the ML community for a while. I'd test it too as well as anyone that has posted in this thread i'm sure. Open Beta is going to be the earliest we see it I would guess.
Hello,
I would like to donate for the 650D version. Which Paypal donation link should I use?
Best Regards,
Derek
Me too, can't wait for the 650D port, please post PayPal link to donate for this version, thank you!
Quote from: jimmyD30 on April 02, 2013, 02:58:14 PM
Me too, can't wait for the 650D port, please post PayPal link to donate for this version, thank you!
Bump.
There are enough new followers in this one thread to warrant simply posting a direct link to a paypal donation. Many people aren't even posting, simply coming by to keep up on the status. It would be wise to put it here.
For the 6 millionth time:
QuoteThanks to your help, we have covered all our funding needs for now. Please consider donating to EFF, they do a great work in defending your digital rights!
Source: http://www.magiclantern.fm/download
I checked log files here http://nanomad.magiclantern.fm/nightly/archive/ and I see Nanomad and a1ex works under old models each day and only one day per week under our EOS 650d !!!! Very Nice !
They said they have not time..... I do not sure.
Are you waiting ML for 650D ??? Only after EOS 800D in 3 years. Check log files of the job 650D.
things to clarify:
a) we do this in our spare time and dont allow pressure - thats why even alphas are more stable than any other software
b) we permanently spend all donations for cameras we only use to develop software on, and thus we have no time anymore to shoot any images with them. sigh.
c) there are several other people like you who are asking for things.
d) you are welcome to help.
so please either accept that
a) there is a release when its done
b) not every developer works on every single model
Quote from: Galior on April 03, 2013, 01:45:19 PM
I checked log files here http://nanomad.magiclantern.fm/nightly/archive/ and I see Nanomad and a1ex works under old models each day and only one day per week under our EOS 650d !!!! Very Nice !
They said they have not time..... I do not sure.
Are you waiting ML for 650D ??? Only after EOS 800D in 3 years. Check log files of the job 650D.
I bet they are doing something for 650D every day, like trying to figure out what causes problems or reviewing pre-alpha testers feedback.
Probably they just write and update code once in a while, when there is something worthwhile to open the project and work on it.
As far as I know doing some minor editing on such a massive project is a waste of time when you have to go through a pile of lines of code. You do that when there is more than one minor edit nessesary.
g3gg0, thanks for the info and all your and others hard work.
RE: d) you are welcome to help.
I am programmer for 25 yrs with some time on my hands, how can I help?
Quote from: Galior on April 03, 2013, 01:45:19 PM
I checked log files here http://nanomad.magiclantern.fm/nightly/archive/ and I see Nanomad and a1ex works under old models each day and only one day per week under our EOS 650d !!!! Very Nice !
They said they have not time..... I do not sure.
Are you waiting ML for 650D ??? Only after EOS 800D in 3 years. Check log files of the job 650D.
Some cameras are have a final release and the code needs maintenance, while the new cameras are sometimes a game of hide and seek in the dark.
If you don't have patience, why don't you get a 5D mark II.
Two posts and already flaming.
Get a life dude.
Support programmers! They are doing something that makes your photographic life much easier and releasing it for free. How can you argue with that? Thx to nanomad and all. Keep it up!
side note:with this post i didnt want to beg for "thanks".
it was meant to make people understand the position of developers.
we continue it the way we are doing for years now.
enjoy our work, trying to
improve ML and release new versions that are free for everyone
from time to time.
thats the deal ;)
Quote from: jimmyD30 on April 03, 2013, 02:18:59 PM
I am programmer for 25 yrs with some time on my hands, how can I help?
do you know C, do you know/understand asm, do you know embedded systems and what kind of programming do you do?
Quote from: g3gg0 on April 03, 2013, 03:54:04 PM
do you know C, do you know/understand asm, do you know embedded systems and what kind of programming do you do?
Hey g3gg0, I know java, c, c++, and objective-c. I do not know asm or embedded systems very well, but I'm willing to learn (on my own) and learn new things very quickly, so let me know if you think I can be helpful.
Quote from: Galior on April 03, 2013, 01:45:19 PM
I checked log files here http://nanomad.magiclantern.fm/nightly/archive/ and I see Nanomad and a1ex works under old models each day and only one day per week under our EOS 650d !!!! Very Nice !
They said they have not time..... I do not sure.
Are you waiting ML for 650D ??? Only after EOS 800D in 3 years. Check log files of the job 650D.
Boy for something thats free I dont see them owing you an explanation.
Also, when a changeset message does not refer to a specific camera, it usually applies to all cameras.
Quote from: laame on April 03, 2013, 02:17:32 PM
I bet they are doing something for 650D every day, like trying to figure out what causes problems or reviewing pre-alpha testers feedback.
Probably they just write and update code once in a while, when there is something worthwhile to open the project and work on it.
As far as I know doing some minor editing on such a massive project is a waste of time when you have to go through a pile of lines of code. You do that when there is more than one minor edit nessesary.
The developers here have full time jobs and do this on their own time and they do this unpaid. So some times days can go by before they get back to working on ML and the 650D is not their only project..
Exactly, I usually work on ml during the weekend (assuming it's not an holiday :p) as most of the other devs
Closed doors testing may seem strange bit it helps to keep reports under control when you know the code is still full of bugs
That and the fact that testers actually try out every single function and provide a nice report of what's broken and what's not
Only a side note if you want to start working on ml we can probably arrange a live q/a session over irc with some other devs (I'm volunteering). Let me know if you are interested so I can discuss this with the other guys ;D
Quote from: nanomad on April 03, 2013, 08:19:39 PM
Only a side note if you want to start working on ml we can probably arrange a live q/a session over irc with some other devs (I'm volunteering). Let me know if you are interested so I can discuss this with the other guys ;D
Just curious, has a software camera simulator been developed? Like an iPhone sim in Xcode for apps, if not do you think it would be feasible to create one for testing? This might be something I can do with some guidance from the lead developers.
Quote from: nanomad on April 03, 2013, 08:19:39 PM
Only a side note if you want to start working on ml we can probably arrange a live q/a session over irc with some other devs (I'm volunteering). Let me know if you are interested so I can discuss this with the other guys ;D
I'd be down to at least watch this! I'm currently in school (taking a C class right now in fact!), so I'm very interested in learning as much as I can, and maybe even helping.
following the process of the development of a public version of magic lantern is almost as cool as using a public version of magic lantern. so far i've enjoyed the show!
Thanks for the dedication to this project :)
QuoteJust curious, has a software camera simulator been developed?
See www.magiclantern.fm/forum/index.php?topic=2864
If you are interested, I can publish the current patch (you can run ML code on QEMU, but only one task at a time). For example, I've used this emulator these days to debug a small python interpreter (tinypy).
Alex, nanomad,
I've got >13 years experience with embedded systems, RTOS, programming in assembly (ARM, x86, MIPS) and of course C/C++. I don't have much time, but could help in weekends or when I'm low on projects (if ever...).
A quick session to get started would definitely help, so yes, I'm interested.
I am just excited to brick my camera. I used to program in the day, many years ago asm on 6809 wow have things grown since then. never kept up. But I am always ready to test and report. I am sure you have enough testers but in future releases as I have stated in a post earlier, I would love to test the bracketing script to infinity as I am just now getting into HDR and feel limited with 3 frames.
Keep up the tremendous work, and hopefully the new guys that offered their expertise passes the interview and will lend their talents to this great adventure. Grace and Peace to all who are working on this and to all testers.
So I was thinking that it'd be awesome if you could increase the video frame rate. I know you probably can't get a whole lot faster than 30fps on 1080 but maybe increase frame rate on lower quality videos so we could get some high speed shots!
ONLY a suggestion though and only if you think it'd be worth throwing in (you may already be doing it, I don't know). Thanks again guys! Your work is awesome and I appreciate it!
Hi there,
I'm from germany and also owning a 650D and eagerly awaiting ML for that.
Since I'm recording video with it and don't want use an external audio recorder I would like to get the highest possible quality out of the internal Audio-Codec (i.e. foremost disable AGC).
I'm a embedded software-developer having 5+ years of experience with C and asm (all kind of µC and Interfaces). In case there is anything I could do (especially regarding the Audio-Codec) I would be glad to help.
Cheers,
armino
I would like to share some of the pre alpha testing. Shooting video at 2.5 fps will lead to a system crash ( already reported to nanomad, and a fix is in development as far as i know) Additionally, vertical lines apear in the video. Aldo this may not be specific for this release.
Quote from: armino on April 04, 2013, 10:42:02 AM
Hi there,
I'm from germany and also owning a 650D and eagerly awaiting ML for that.
Since I'm recording video with it and don't want use an external audio recorder I would like to get the highest possible quality out of the internal Audio-Codec (i.e. foremost disable AGC).
I'm a embedded software-developer having 5+ years of experience with C and asm (all kind of µC and Interfaces). In case there is anything I could do (especially regarding the Audio-Codec) I would be glad to help.
Cheers,
armino
you have IDA pro or a comparable tool?
Quote from: AshleyAshes on February 25, 2013, 04:36:28 AM
Yeah. Get something other than a DSLR for filming wedding photography. o.O
A prosumer video camera? Geez, I haven't seen one of those at a wedding in years. I'd bet that a survey would show most pro wedding photogs now use DSLRs. But I shall not be funding such a survey.
Quote from: g3gg0 on April 04, 2013, 11:34:35 AM
you have IDA pro or a comparable tool?
no unfortunately not (unless you're referring to the freeware version 4.9). So far the reverse engineering that I've done was so easy it could be done by looking at the disassembly alone.
Why do you ask? Is it recommended/required?
In the old days I used a lot of SoftICE, not even sure that still exists? Anyway, I know how to work with IDA and other such tools, no problem there.
well, IDA is a necessary tool when you are reverse engineering canon functionality.
for cleaning up code and adding some new features, you just have to set up the build environment,
grab ML from the hg repository and build one on your own.
Quote from: DavidFell on April 04, 2013, 05:59:17 PM
A prosumer video camera? Geez, I haven't seen one of those at a wedding in years. I'd bet that a survey would show most pro wedding photogs now use DSLRs. But I shall not be funding such a survey.
I highly disagree. DSLR's are completely unfit for shooting weddings. They lack the handheld stability, the ergonomics, and overall simplified video functionality necessary for on-the-fly style shoots. DSLR's are also not as sharp as prosumer camcorders, and require special techniques in most cases to avoid things like moire and rolling shutter. The only thing DSLR's excel at with regards to video is the cinematic/film-look and this is something you cannot easily get with on-the-fly shooting.
Of course this is a conversation best left for another forum!
That really boils down to image stabilization.
Sharp lenses make sharp images... put your money in the glass. Also DSLR produces a great image in low light and you have the bonus of a creamy archival quality image that doesn't look flattened out. My experience is that a wedding is a staged event and with planning and use of jibs and sliders you convey much more of the emotional aspect of the event than with zoom on the fly. 8)
Doc producer: T2i, T4i, 60D, Ex1, Ex3
Quote from: killr0y on April 06, 2013, 02:10:44 AM
I highly disagree. DSLR's are completely unfit for shooting weddings. They lack the handheld stability, the ergonomics, and overall simplified video functionality necessary for on-the-fly style shoots. DSLR's are also not as sharp as prosumer camcorders, and require special techniques in most cases to avoid things like moire and rolling shutter. The only thing DSLR's excel at with regards to video is the cinematic/film-look and this is something you cannot easily get with on-the-fly shooting.
Of course this is a conversation best left for another forum!
I've seen a few Pro's at weddings using DSLR's in the past few years hand held.
Quote from: Chuck J on April 07, 2013, 02:54:22 PM
Sharp lenses make sharp images... put your money in the glass. Also DSLR produces a great image in low light and you have the bonus of a creamy archival quality image that doesn't look flattened out. My experience is that a wedding is a staged event and with planning and use of jibs and sliders you convey much more of the emotional aspect of the event than with zoom on the fly. 8)
Doc producer: T2i, T4i, 60D, Ex1, Ex3
.
I agree your glass is key, I can't stress how many amateur photographers I see with 5d's but only one lens in there camera bag. I've saved my money and use a rebel for years and now I have an arsenal of 12 lenses and 2 t4i's.
Hello let us can hope us to have ml by one has two months?
Quote from: killr0y on April 06, 2013, 02:10:44 AM
I highly disagree. DSLR's are completely unfit for shooting weddings. They lack the handheld stability, the ergonomics, and overall simplified video functionality necessary for on-the-fly style shoots. DSLR's are also not as sharp as prosumer camcorders, and require special techniques in most cases to avoid things like moire and rolling shutter. The only thing DSLR's excel at with regards to video is the cinematic/film-look and this is something you cannot easily get with on-the-fly shooting.
Of course this is a conversation best left for another forum!
Everything you can mentioned can be fixed with a glidecam and some accessories. I think a 5d is the perfect camera for shooting weddings.
This is my first post! I'm excited for the future of Magic Lantern especially on the 650d. Thanks for all your hard work :)
anyhow getting back on topic, how is the progress going on ML?
Quote from: nanomad on March 31, 2013, 05:19:25 PM
Yep, still fixing bugs. Closed doors testing really helps nailing down bugs since people actually test the features. The FPS override bug should be fixed now, so expect another build soon.
Nanomad, you are accepting donations to help you with the development of ML for 650D?
Quote from: RafaLibrenz on April 08, 2013, 10:02:49 AM
Nanomad, you are accepting donations to help you with the development of ML for 650D?
I believe there was a previous post in this thread that said they had all the funding needed and posted a link to a cause that helped with copyright stuff or something similar. I suggest reading this whole post. I will keep checking back to hear about any updated towards the progress of ML for the 650D(T4i).
from: http://www.magiclantern.fm/download
> Thanks to your help, we have covered all our funding needs for now. Please consider donating to EFF, they do a great work in defending your digital rights!
Hello I am from Israel and sorry for my bad English I have canon 650d and I waiting for magic lantern thank you for you great work and if you need test it i can help
Quote from: kazeone on April 08, 2013, 03:29:20 AM
anyhow getting back on topic, how is the progress going on ML?
Ironing out bugs, mostly due to overlooking stuff here and there :P
I'm also taking care of the 1100D because I admit I overlooked it a bit.
Quote from: RafaLibrenz on April 08, 2013, 10:02:49 AM
Nanomad, you are accepting donations to help you with the development of ML for 650D?
As g3gg0 pointed out we have all the expenses covered for now, but thanks anyway.
Thanks for the update Nanomad and all your hard work. Truly appreciated.
Small reminder: in reboot.c it should compute a checksum of Canon firmware and refuse to boot with the wrong firmware version. This is a safeguard, so people don't screw up their cameras when Canon releases a new update.
True that
Super excited.
Count me super excited too!
Stayed with the T3i for as long as possible just because of the capabilities I had with ML. Wore the shutter out (was giving hints) and warranty was up, so I upped to a T4i, now also patiently waiting and super excited!!
BTW, have been registered here for a long time, just never actually post about anything...
I can't wait until you unlock the other ML features on the T4i. Live preview features and HDR-video and motion detection is great and all, but I'm excited for when focus stacking and advanced HDR (Picture) bracketing gets on the camera!
Great work all around nonetheless.
I recently bought a 650D and I can't wait until ML!
Just wanna say that I think you are doing a great job and that it is very much appreciated. I LOVE YOU!
I guess I can come out of my non posting corner as well. I have been following this thread for quite a while and I'm really looking forward to ML on this camera. I ordered my 650D this monday and I'm still waiting for delivery.
I will be busy with the standard camera for quite a while but I really hope ML will reach it sooner or later.
The features I'm interested in using is picture HDR and scripting.
My deepest respect for those who have worked on this so far and for those who will make it reach a release.
Quote from: Chuck J on April 07, 2013, 02:54:22 PM
Sharp lenses make sharp images... put your money in the glass. Also DSLR produces a great image in low light and you have the bonus of a creamy archival quality image that doesn't look flattened out. My experience is that a wedding is a staged event and with planning and use of jibs and sliders you convey much more of the emotional aspect of the event than with zoom on the fly. 8)
Doc producer: T2i, T4i, 60D, Ex1, Ex3
You can put Zeiss cinema glass on a T4i and I guarantee you it will never be as sharp as a comparable camcorder. Why? Simple. The sensor has no idea what a 1080P image is. The processor uses extremely crude line & pixel skipping to simulate the 5,184 x 3,456 sensor as a 1920x1080 sensor.
If you were to grab the centermost 1920x1080 sensor data, you would have your moire-less, tack-sharp HD video. The problem is that you'd also be stuck with a ridiculous crop factor that wasn't very useful.
Now, if Magic Lantern was able to change how the raw sensor data was captured, say for example, you pulled the center 3840x2160, then threw out ever 2nd horizontal pixel and every 2nd vertical pixel, you would have a much cleaner image and you would only be dealing with a zoom factor of 26%. This would also reduce the rolling shutter considerably, because a smaller area of the sensor is being refreshed.
Been lurking for too long without paying respect.
Thanks for all the hard work guys,
as someone who is just diving into programming on the side as well as having a full time job,
I have a huge respect for you guys being able to put such hard work into this project.
Best of luck with everything, and don't stress over it too much!
I am new here i dont know anything about coding or anything like that. i am a film student i can only request for what i want to see for the 650D i want to be able to shoot Raw and 4K it will be nice to see these function. ;D
Why stop at 4k? Why not 8K?
and some flowers.
Ah, I love the reality TV folks switching to DSLR because of the beauty of the image over VIDEO. And news folks, and documentary producers, and advertising productions....
I have a question for this crowd. Are RED and Black Magic Cinema video cameras? And what should we consider the differences are between digital film and video cameras?
I bought a Sony a57 before getting a canon 650D
The problem with Sony a57 you cannot change to 24p especially a euro version the good thing About canons you can switch to PALL to NTSC and I call that freedom ;)
One question is the ML ready or I still have to wait for the full release cuz I am having doubts to try the alpha on my new canon 650D.
Can you please tell us the actual release date for ML
Actual release date: sooner or later.
I hope they will add 48fps
250fps for slow motion ;D
That will be great
If you look at 5d3 rumors, CANON couldn't add 120fps even on dual digic. I bet bit rate from that is insane.
QuoteIf you look at 5d3 rumors, CANON couldn't add 120fps even on dual digic. I bet bit rate from that is insane.
so its not possible to add 250fps then
Not really that familiar with ML but is it possible to lower the resolution of the video for the higher frame rate? Like the 800 something by 600 something resolution? I wonder what is the highest fps a camera like this one can go on that resolution?
I think we should let them finish the alpha with all the already great features Magic Lantern has before asking for any extra features or it will never come out :)
Keep up the good work! :D
im try to update my camera firmware im new at canon cameras im following the instractions but i get this message
eos 650d canon ememory card containing firmware is required to update
everytime i try everything this message shows up every time
Quote from: teecee on April 13, 2013, 06:24:28 AM
im try to update my camera firmware im new at canon cameras im following the instractions but i get this message
eos 650d canon ememory card containing firmware is required to update
everytime i try everything this message shows up every time
There are no firmware updates out for the 650D
I think that the high fps would be possible with H.265
Yeah, good luck replacing the HW encoder
This of course means in theory :)
imho, you could accelerate this at the software level.
The best you can hope for is mjpeg since the camera is able to convert to jpeg data. You can try writing a H265 module in software but it will be running on the slow ass arm processor. Maybe you'll get like 1fps or something.
so what a problem, we solder the BCM7445 on the board :D
How are you going to take the digic package apart? Lasers?
Quote from: 1% on April 14, 2013, 04:52:47 AM
How are you going to take the digic package apart? Lasers?
I agree, this is getting silly. We are discussing a serious ML release for a camera that actually exists not building a new one or a Frankenstein 650D. I am happily awaiting any release, beta or otherwise and will test it on my baby anytime. Thanks guys.
With a infrared heater or heat gun ;D
Now seriously, maybe you can somehow manipulate encoder firmware.
People who lack the most basic common sense are no longer welcome on this forum.
Here's a FAQ for you:
http://wiki.magiclantern.fm/faq?&#troll_questions
Hopefully the people in charge of this forum can keep it friendly and respectful.
QuoteNow seriously, maybe you can somehow manipulate encoder firmware.
650d uses mvr config. I think FW is just setting the registers. 6D/5d3 encoder may have an image as it seems detached (I just load parameters/config, can't change quality in real time). Looking at registers here would help but they are changed and the old code is still in FW to confuse. Maybe tracing out EKO mode will turn up something.... But these are dedicated chips from TI not generic FPGA or something. Nothing in the references says anything about loading an image.
Only problem is shrinking 4mb 422 data to like 1mb h264/jpeg, etc. Jpeg would already come out at 4:2:2... You can't increase that 422 data quality unless you resize it.
If you're gung ho about cutting a solid package up (heat gun would only take it off the PCB) just dump the FW and look, maybe you'll see something.
650D still has room for improvement... needs flush rate and QP/slice setting. 6D can push out 400Mb/s... that is like 2MB frame size so 2:1 compression. I'm not able to do flush 1 currently, maybe 650D can. That is solid break your card writing.
hello! Dear developers of ML!
Is it possible to make test version of ML for 650D with sound level indicator ONLY?
Because all another features not needed for 90% users.
I can donate for this version)
How did you get that percentage?
Alex, this is my IMHO)))
But sound level indicator most wanted for daily use/
I shooting wedding with sennhizer radio system attached right in camera and very frustrated about sound)
and whole history of ML development begin from disabling AGC as you remember ;)
I thought there already was a sound level indicator on the 650D?
Hi guys if you keep requesting and requesting, ML for 650D will never come out. those functions will be added obviously
Quote from: Lucas_W on April 14, 2013, 08:58:47 PM
I thought there already was a sound level indicator on the 650D?
It does but for some silly reason you can only access it and adjust the levels from the menu while not shooting. So you can go to the menu, see your levels, then exit and start shooting, but you can't monitor live while shooting.
I am one of the 10 percent.
i think it's done when it's done, right?
Appreciate your work.
Greetings from Germany.
FUCK OFF YOU CUNTS.
IT WILL BE SUMMER AND 650D STILL WONT BE READY. all you saddo's kissing arse, your better off not buying a 650D and having 600D at least you can put ML on it.
IT WILL BE DONE WHEN ITS DONE = NEVER YOU IDIOTS.
i know im getting banned but thats good cause i like to make you laugh and cause shit and stir with the wooden spoon.
IF YOUR GONNA DO IT FUCKING DO IT. stop beating around the bush and telling poor people to stop asking. im telling you now
BAN ME YOU CUNTS
(http://www.reactionface.info/sites/default/files/images/1310566609761.jpg)
I'm not going to ban you because I actually enjoy a bit of drama
(you could also have checked the repo and noticed the port is basically done, it works but it's not safe to be distribuited until we iron out the remaing bugs...feel free to compile it and test it though)
Lol, its done now just no tidy release for you to consume....
Do you even computers, bro?
;D
QuoteFUCK OFF YOU CUNTS.
IT WILL BE SUMMER AND 650D STILL WONT BE READY. all you saddo's kissing arse, your better off not buying a 650D and having 600D at least you can put ML on it.
IT WILL BE DONE WHEN ITS DONE = NEVER YOU IDIOTS.
i know im getting banned but thats good cause i like to make you laugh and cause shit and stir with the wooden spoon.
IF YOUR GONNA DO IT FUCKING DO IT. stop beating around the bush and telling poor people to stop asking. im telling you now
BAN ME YOU CUNTS
looooool
dude it will be out all u have to do is ask them for a test u will get ML
Quote from: cu-nt on April 15, 2013, 09:23:22 PM
F**K OFF YOU C**TS.
IT WILL BE SUMMER AND 650D STILL WONT BE READY. all you saddo's kissing arse, your better off not buying a 650D and having 600D at least you can put ML on it.
... and they try to tell us that the age of sensible debating skill is dead ...
Aw, someone hasn't gotten their banana today! Poor fella.
QuoteAw, someone hasn't gotten their banana today! Poor fella.
looooooool hahaha hehehehe
I guess I've been missing the excitement.
Quote from: 1% on April 14, 2013, 05:05:19 PM
650d uses mvr config. I think FW is just setting the registers. 6D/5d3 encoder may have an image as it seems detached (I just load parameters/config, can't change quality in real time). Looking at registers here would help but they are changed and the old code is still in FW to confuse. Maybe tracing out EKO mode will turn up something.... But these are dedicated chips from TI not generic FPGA or something. Nothing in the references says anything about loading an image.
Only problem is shrinking 4mb 422 data to like 1mb h264/jpeg, etc. Jpeg would already come out at 4:2:2... You can't increase that 422 data quality unless you resize it.
If you're gung ho about cutting a solid package up (heat gun would only take it off the PCB) just dump the FW and look, maybe you'll see something.
650D still has room for improvement... needs flush rate and QP/slice setting. 6D can push out 400Mb/s... that is like 2MB frame size so 2:1 compression. I'm not able to do flush 1 currently, maybe 650D can. That is solid break your card writing.
Thanks for the info. I hope I have a little time next week to get to grips with the issue.
I have an idea about precompression. My russian colleague has introduced long time ago an interesting method. Let's see if I can find contact with him ;)
btw, Why have you allowed the post of cu-nt? What good is that? :o
Quote from: Chuck J on April 12, 2013, 03:21:01 AM
Ah, I love the reality TV folks switching to DSLR because of the beauty of the image over VIDEO. And news folks, and documentary producers, and advertising productions....
I have a question for this crowd. Are RED and Black Magic Cinema video cameras? And what should we consider the differences are between digital film and video cameras?
There isn't much difference between a "digital film" camera and a video camera. Traditional film cameras use a framerate of 23.976fps with usually a 180 degree mechanical shutter. Because of the size of the film format, film cameras can achieve much shallower depth-of-field than a video camera. With that shallow DOF, you can pretty much throw autofocus out the window, so you need a set-up with a good manual focus. Usually you have an assistant cameraman (known as a focus puller) keep the focus while the cameraman is filming.
So a "digital film" camera is a video camera that can simulate a 23.976fps framerate with a 180 degree shutter (2x framerate) with a sensor large enough for a cinema-like depth of field, and a way of doing manual focus pulls. More expensive cameras like your RED's, ARRI's, and even the Black Magic, will also take advantage of the tack-sharp HD sensor by allowing distortion-free prime lenses to be mounted for bleeding edge sharpness. Most DSLR's like the Canon 5d and APS-C cameras use a non-optimal method for converting the camera sensor data to a 1080p image thereby limiting how sharp a video image can be, and are instead used for their versatility in achieving the filmic look. Compare them to something like the Lumix GH3 and you'll know what real 1080P looks like.
If you do photo timelapes, though, even a Canon 550D will put out jaw-dropping ultra sharp videos.
Of course, I'm waiting for Nano to release an alpha or something so I can get the intervalometer functionality back on my 650D ; )
Quote from: cu-nt on April 15, 2013, 09:23:22 PM
FUCK OFF YOU CUNTS.
IT WILL BE SUMMER AND 650D STILL WONT BE READY. all you saddo's kissing arse, your better off not buying a 650D and having 600D at least you can put ML on it.
IT WILL BE DONE WHEN ITS DONE = NEVER YOU IDIOTS.
i know im getting banned but thats good cause i like to make you laugh and cause shit and stir with the wooden spoon.
IF YOUR GONNA DO IT FUCKING DO IT. stop beating around the bush and telling poor people to stop asking. im telling you now
BAN ME YOU CUNTS
Some of you may think that this is funny, I don't, this type of posting should not be tolerated. I have been reading all postings and find that there are a lot that do not meet the criteria's for this blog and should not be allowed. I do however praise the people who are working so hard to develop ML for the 650D and I thank them. All of you that fail to respect them or ask all those stupid questions, can you please find another way to spend your time.
Well, although 'cu-nt' was a little over the top, I'm glad you allowed the post and didn't ban him. I'm a big proponent of free speech and all too often come across moderators who take themselves and their forums a little too seriously.
I'm mean, what a boring world this would be if we all thought alike and didn't allow other to freely express themselves, plus I needed a good laugh!
Trolls gonna troll.
Any possibility on getting the latest build compiled and sent to me? I don't know anything about compiling code. I will be going to Tokyo this coming weekend for a festival and I would like to give the video section a good testing!
Please and thank you!
:D
That would actually be pretty cool if someone posted a compiled build for some more of us to test out. I am still running the very first closed pre-alpha on mine and I would love to test out the latest build and report anything over to the thread. I am absolutely dying to get custom WB even semi-working on my 650D.
Anyone care to help out? I just haven't had the time with all my post production to get deep into learning all the nitty gritty of compiling my own yet.
Likewise, I would also like something to play with while waiting for the full release.
Understandably everyone who downloads the early version does so at their own risk but it would be much appreciated.
I need the intervolameter so that I can do a 2 week time lapse of a plant setup I have ready :-)
Intervalometer is actually potentially really dangerous so I'm not that willing to distribuite it (it requires props). I'll check again and see if we can push out a build
Have any of the builds been at all successful with enabling Kelvin WB manipulation?
Yep, not the safe ones I handed out though (requires props)
I tried to compile the latest version of autoexec.bin and I re-did the EOScard but when I booted up my LED flashes and camera doesn't boot, it's fine without the card though. Is it because I'm using an outdated nightly of Magiclantern or did I do something wrong.
Uhmm..interesting. Did the old alpha work for you? The only thing I can think of is the new CRC check I added to prevent booting with a wrong fw version. (I'll sit on IRC if you want to do a couple of tests)
I never got to try the old alpha. The version I was using before was a autoexec.bin I compiled myself on March 13th with the .fir from the 650D downloads section.
nanomad and I have been testing things on IRC and he thinks there might be a bug with his signature checking or that I was just using an old firmware or similar.
On the plus-side, here's an image of one of Magic Lantern's "features" [It's a joke btw, my camera is perfectly safe!]
https://imageshack.us/scaled/large/820/20130416215724.jpg (https://imageshack.us/scaled/large/820/20130416215724.jpg)
Taking timelapses with cameras with moving mirrors is dangerous since they get worn out after a limited number of shots. Of course it depend on the interval and everything else. Taking 1 pic each 10 sec will produce >8000 images per day.
I know some people who did this and broke the camera completely after a few days.
Watch out guys!
Plants don't really grow that fast (I hope?), so I don't think he'd be taking a photo every 10 seconds. Maybe he could take 1 an hour and have 1 day = 1 second which would produce 14 seconds of time lapse footage at 24 fps.
Lucas, that was the plan 2 weeks lasting 14 seconds.
24 shots per day * 14 days = 336 photos, surely not enought to wear the shutter out!
Of course not. I just wanted to warn for potential mistakes.
Well available builds would be awesome. Please carry on.
Hey guys! Just want to hop in and give a big thanks to everyone working on this release.
Im also wondering how to compile ML? Not that i cant wait for the official release. No stress bro!
But i love living on the edge, experimenting with shit :)
FYI; I have no experience in programming
Then stand back and relax.
Compiling and installing it's not resuming to "next -> next -> finish", so better be safe and wait.
Quote from: loplo on April 16, 2013, 04:15:29 PM
Then stand back and relax.
Compiling and installing it's not resuming to "next -> next -> finish", so better be safe and wait.
Yeah.. Thats what i thought.
What could go wrong when compiling it yourself?
Funnily enough, compiling Magic Lantern sort of is "next -> next -> finish" except Command Line style instead of GUI.
If you do want to compile Magic Lantern I 110% recommend getting the Virtual Machine made for it.
http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip
You'll need virtualbox for it. From then on you just need to make a make.user file and do 'make 650D' in the terminal and get your autoexec.bin off your VM.
Lucas_W, "except". :)
Heh. Yep, it's as simple as pressing a button..... and then doing this, and then doing that, and then writing this here and that there. :P
Quote from: Lucas_W on April 16, 2013, 04:50:50 PM
Funnily enough, compiling Magic Lantern sort of is "next -> next -> finish" except Command Line style instead of GUI.
If you do want to compile Magic Lantern I 110% recommend getting the Virtual Machine made for it.
http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip
You'll need virtualbox for it. From then on you just need to make a make.user file and do 'make 650D' in the terminal and get your autoexec.bin off your VM.
It's always much simpler when you've done it before. I find myself making similar justifications to people about other programmer stuff where, to me, it seems like such a quick and easy task. It's like reformatting a PC. So easy to me, but there really is a ton of particulars and steps that a smart someone who's never done it before could easily screw it up. Being so busy, I know I wouldn't have any problems doing it myself. Just no time what so ever for me right now. Yet, I would absolutely love to test some more out and report on bugs. That I do have time for ;)
Therefor... anyone that would be generous enough to compile a 650d build and PM me with it would be a champion and ultimately be helping out the community just a little more, not just for me :P
If I could compile a version for you ( and I can't) I would not give it to you. Any bugs you run in to you will report back here. And as it would be a costum build the developers would have a hard time figuring out what may have coused the bug.
Wait for the build from nanomad, it will not have every option activated, but it will be testable. So fare the code is very stable ( far more stable then some comersial final software I have to work with) and that takes time.
Aldo I have a pre alpha running, I to look forward to a alpha version. And when it is there I will test and report back.
Quote from: Lucas_W on April 16, 2013, 04:50:50 PM
Funnily enough, compiling Magic Lantern sort of is "next -> next -> finish" except Command Line style instead of GUI.
If you do want to compile Magic Lantern I 110% recommend getting the Virtual Machine made for it.
http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip
You'll need virtualbox for it. From then on you just need to make a make.user file and do 'make 650D' in the terminal and get your autoexec.bin off your VM.
Oh, really?
This is the correct download for the ML build, right? https://bitbucket.org/hudson/magic-lantern/overview
That's the source-code that you compile from, yes.
I'm not sure if I should do this, but I've attached my autoexec.bin and the .fir file for the 650D from the ftp space of the site.
I take no responsibility for what happens if you brick your camera, and I have no idea how to help in such event. I'm not even 100% sure this works.
You'll need to place both into the root of your card and then download the magic-lantern nightly and place the ML folder in the root. Then you'll need to download EOScard and check all threes boxes and click 'save'. Pop the card into your camera and then run the firmware updater and that should work, I have no idea as it's a different process to what I originally did.
Link removed by Nanomad: The bootfix does not enable the bootflag, it fixes it...and the FIR bypasses a crucial safety check
As always, the safest and officially recommended method is to wait until the official Alpha release.
Quote from: Lucas_W on April 16, 2013, 05:40:57 PM
That's the source-code that you compile from, yes.
I'm not sure if I should do this, but I've attached my autoexec.bin and the .fir file for the 650D from the ftp space of the site.
I take no responsibility for what happens if you brick your camera, and I have no idea how to help in such event. I'm not even 100% sure this works.
You'll need to place both into the root of your card and then download the magic-lantern nightly and place the ML folder in the root. Then you'll need to download EOScard and check all threes boxes and click 'save'. Pop the card into your camera and then run the firmware updater and that should work, I have no idea as it's a different process to what I originally did.
*********** - autoexec.bin
*********** - 650D-bootifx.fir
As always, the safest and officially recommended method is to wait until the official Alpha release.
Ok now Im almost shitting my pants
What revision is this?
The latest as of writing, but with a slight modification to bypass the sig check as that wasn't working right.
EDIT: Funnily enough, Bitbucket is also down as of writing...
Quote from: Lucas_W on April 16, 2013, 06:07:14 PM
The latest as of writing.
EDIT: Funnily enough, Bitbucket is also down as of writing...
It didn't work. Just said that i needed "All the ML files on the card" or something like that when i tried the Firmware update tool inside the camera.
Ah, okay. Try this instead:
Wipe the root of your card (Except the DCIM folder if you have anything stored there).
Then extract removed onto it.
Edit by nanomad: Nope, the bootfix won't work..it's a fix, not a proper bootflag enabler
Do the firmware update.
Replace the ML folder and autoexec.bin with the nightly and file I linked to, respectively. Do the EOScard step.
and it should just boot up into ML [Press trashcan on the normal operation display to bring up the ML menu].
Quote from: Lucas_W on April 16, 2013, 06:23:26 PM
Ah, okay. Try this instead:
Wipe the root of your card (Except the DCIM folder if you have anything stored there).
Then extract http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip onto it.
Do the firmware update.
Replace the ML folder and autoexec.bin with the nightly and file I linked to, respectively. Do the EOScard step.
and it should just boot up into ML [Press trashcan on the normal operation display to bring up the ML menu].
That last part was a litte fuzzy. I want to get this 100% correct.
After i do the firmware update with the ML folder and 650D-bootfix.fir, i replace them both with the two files you linked earlier and the bitbucket folder?
EDIT: I dont have a autoexec.bin after i did the firmware update on the memory card
after you do the firmware update:
Download the nightly: http://nanomad.magiclantern.fm/nightly/ (The .zip)
Copy the 'ML' folder in that nightly package into your card (And overwrite when it says if you want to)
Then download the autoexec.bin I originally posted in my first post (The Google drive thing). Put that onto the root of the card and overwrite the old one.
Then run EOScard and check all three boxes and click 'save' (I press it a couple of times because someone suggested that 10's of pages ago and because OCD). Then put the card into the camera and turn it on (You probably shouldn't have to do another firmware update).
What response is one meant to get after the firmware upgrade? I'm following the steps and ML isn't loading (camera is fine tho). When I do the firmware upgrade step I get 'EnableMainFirm :)' on the camera's LCD. That's the only feedback the process generated.
Thanks for taking the time Lucas_W and big thank you to the ML team for their work.
Yes, I was getting that when I was originally trying to get it to work, but I forget what I did. Maybe you need to do the EOScard step when you put the http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip on in that first step as well as after you replace the files?
Same thing happened. I guess I better be patient and wait for an official public release before I do something majorly wrong :) thanks anyway
QuoteEnableMainFirm
That's for unbricking, not for enabling the boot flag.
That makes sense I guess, have no idea why it's saying so, hmm maybe it's not liking the files and it's enabling the main firmware to avoid damage?
All I know is I kept getting that until I somehow got the right setup and got ML working.
Ah, that's right. I also adapted my method of getting it working on my camera from the method from installing the pre-alpha that's no-longer available (http://www.magiclantern.fm/forum/index.php?topic=3697.msg24949#msg24949). Obviously you can't do the dumper part (and I didn't need to). If you (or anyone) wants to continue, you'll have to interpret that and think about what steps to do. I'd be more descriptive, but I'm off to bed now.
Yeah well it didnt work for me either :(
JUST DON'T USE THAT AUTOEXEC OR FIR
It bypasses a critical safety check so it can potentially damage your camera. For real this time
And that FIR is no good, unless you have a screwed up bootflag on your camera
Lucas, can you send the file you gave me on IRC via PM?
Quote from: nanomad on April 16, 2013, 09:13:09 PM
JUST DON'T USE THAT AUTOEXEC OR FIR
It bypasses a critical safety check so it can potentially damage your camera. For real this time
And that FIR is no good, unless you have a screwed up bootflag on your camera
How does it affect the camera? How do i know if something broke?
Good question. If the camera still works correctly it probably didn't damage anything
(Truth be told this check was missing in the pre-alpha too but we may have been lucky)
So excited for the release. I often fondle my camera and envision the moments when I will slid that little ML card into her.....this sounds dirty.....but seriously I cant wait!!!
You guys rock!
i cant wait to see ML in action for canon 650D ;D
hope it comes with video time lapse
Well there we go. I guess it is best to wait until the official alpha, though I still don't get how I managed to get it working on my camera.
Can you uninstall ML if you do not like it and want to go back to the orginal FW or is it now permanent
Mine works without the card in, and I can boot up without ML running by holding down SET as I turn it on.
You can always remove the bootflag from both the camera (by re-running the fir you used to install ML and turning the dial when asked) or the SD card (by doing a low level format with KEEP ML option turned off)
Hate to be this guy, but any idea of a timeframe for stable release?
If you would have read the tread, you would know... Its done when its done. No time frame, no deadline, no ms project planning.
These threads really need a sticky post (that is unaffected by scrolling) giving the answer to the most frequent question... ::)
Or plaster this everywhere
http://wiki.magiclantern.fm/faq?&#troll_questions
Or better yet, make it pop-up in a lightbox kind of embedded pop-up thing for non-registered users.
Quote from: Lucas_W on April 17, 2013, 02:04:49 PM
Or plaster this everywhere
http://wiki.magiclantern.fm/faq?&#troll_questions
Or better yet, make it pop-up in a lightbox kind of embedded pop-up thing for non-registered users.
Or better yet, for people like me who are itching in their pants to get a working version of ML advise that monetary donations will not help but coders/programmer will.
Note to people monitoring this thread: How many people eagerly checked the thread to see if my post was a release???? ;-)
Quote from: Phillips321 on April 17, 2013, 03:59:49 PM
Or better yet, for people like me who are itching in their pants to get a working version of ML advise that monetary donations will not help but coders/programmer will.
We are not accepting donations, so that should be clear enough ;)
Hello, why to have no version ml with the functions which do not walk to block it would allow all to practice and it could wait
Quote from: oli650d on April 17, 2013, 07:04:15 PM
Hello, why to have no version ml with the functions which do not walk to block it would allow all to practice and it could wait
I think Oli is requesting a version of ML with the buggy parts disabled so that other less buggy areas can be tested(played with).
I presume the extra effort required to do this should just go towards fixing the bugs?
I think Oli has to use more punctuation marks.
You've already got Magic Lantern with the buggy parts disabled, as I think what nanomad was trying to say was that they haven't got the installing/loading of Magic Lantern completely done/safe.
more like you're a large noob.
Once I get my hands on ML. I will be like, finally it's out!!! :D :D :D >:(
After all that waiting :'(
Quote from: Lucas_W on April 17, 2013, 07:14:52 PM
You've already got Magic Lantern with the buggy parts disabled, as I think what nanomad was trying to say was that they haven't got the installing/loading of Magic Lantern completely done/safe.
Exactly. There's no point in releasing an alpha that has a critical flaw in it
Enough with the spam now
I just wanted to take a minute and thank nanomad,1%, a1ex, baga, blade and all of the others that have put so much time into this. I feel that you have all taken steps above and beyond what anyone could have ever expected of you. I look forward to pitching in when and where ever I can to help ML for the 650d move forward.
I still have more reading to do on ML before I dig to deep though.
Is it possible to programmatically add the add-back and the front of the lens focus? That would be great!
Hi devs, been lurking for a while but I thought that I'd post to say I appreciate your efforts and am looking forward to seeing the port when its ready.
Keep up the good work.
Hi everyone!
I just wanted to say that you guys are awesome with the development of ML but I have a question regarding the front page. It says that ML is available for 650D, is it a typo or is there a beta of ML lurking somewhere for 650D?
I am new to this forum so be gentile to me :P ;D
IT says "soon"
Quote from: nanomad on April 20, 2013, 12:59:30 PM
IT says "soon"
No it doesn't?
Look:
http://postimg.org/image/vlnlhwa3x/
Yes it does?
(http://i.imgur.com/MzWRCFa.png)
yeah, about that..! i think you should make it much bigger something like Soon You know for the desparate of us who are larking silently at the background trying to figure it all out!
Haha it was so small I thought it was a camera model! Thanks!
Quote from: nanomad on April 20, 2013, 04:29:32 PM
Yes it does?
(http://i.imgur.com/MzWRCFa.png)
What is a 5Dc?
also the soon if just glanced @ could look like 500n or something hahahahah
http://www.magiclantern.fm/forum/index.php?topic=1010.0
I've been following this topic from the beginning, my friends about how much is still left to wait ML?
If you've followed the thread, you'd know.
soon
Quote from: saha007 on April 22, 2013, 07:49:00 PM
I've been following this topic from the beginning, my friends about how much is still left to wait ML?
Everyone here is dying to have Magic Lantern working on 650D. Me too. But unfortunately all we have to do now is wait (and don't bugging developers).
Quote from: Walter Schulz on April 20, 2013, 10:11:40 PM
http://www.magiclantern.fm/forum/index.php?topic=1010.0
Thanks Classic 5Dclassic
QuoteEveryone here is dying to have Magic Lantern working on 650D. Me too. But unfortunately all we have to do now is wait (and don't bugging developers
True, well said.
We have the largest number of views of the topic.
At the time, the other topics are moving forward, but the development of ML 650D is really dead. There is nothing to say thank you (((. Green light changes to red. Alpha version? Are you sure? How to speed up this process? Canon 650d camera ceased to produce. Do not wait for 1.0.2 firmware ((((( sorry
How to speed up? By shutting your mouth and keeping this kind of comments for yourself.
Quote from: MarkFlex on April 24, 2013, 05:45:13 AM
We have the largest number of views of the topic.
At the time, the other topics are moving forward, but the development of ML 650D is really dead. There is nothing to say thank you (((. Green light changes to red. Alpha version? Are you sure? How to speed up this process? Canon 650d camera ceased to produce. Do not wait for 1.0.2 firmware ((((( sorry
Repent turn your heart back to the Creator, have faith, and Believe.
Quote from: loplo on April 24, 2013, 06:17:45 AM
How to speed up? By shutting your mouth and keeping this kind of comments for yourself.
That's actually not true. You can grab the source code and start working on the port if you wish. It's all there
Do you all miss my drama ;)
shall i come in and say some stuff
LOL (just having a laugh with you thats all, i thought my previous crap would cheer you up)
Holy carp..., heard that the T5i is coming and a flash of terror overtook..., OMG I hope the dev for the T4i is compatible in some way...
Double Carp!! Knowing Canon, they'll muck it up just enough that everyone will have to start all over with development for that..., or just give up and stick with the mainstreams (5D3, 6D, etc.)
Funny that I started with a Canon F1 (top of the line for all intents) back in 1981 and went DOWN to a T3i just to use ML for vid overseas and so I wouldn't hack a lung if I dropped it off a cliff while paragliding...
T4i is waiting for ML (which WILL come and it sounds like SOON) and take it overseas to risk certain peril.
BTW, those who worked on T3i dev, thank you, thank you, thank you!!! Countless times ML saved the day with functions Canon couldn't see fit to provide.
Put the pre-alpha nightly builds, please ... Add me to the list of testers. OMG! If I knew how to program, I would not sleep day!! but heck, I'm just a user ...
So has anyone official actually given an actual approximate expected date for the t4i ML?
I am interested because because of its ability to enable headphone monitoring adapters. I think I jumped the gun in buying my t4i, having used the 5D I assumed it came with a headphone jack. Boy was I wrong, and monitoring audio is critical for what I do. ( I must admit I'm kind of mad >:( at Canon for making a great camera and leaving off something so basic)
http://wiki.magiclantern.fm/faq?&#troll_questions
@alex: ahahahahaha ;D never saw that page
Hi, I'm from Brazil and I began to follow the development for T4i, chances are the magic lantern work?
:) :) :)
Thanks. That's quite understandable and it sounds like its being worked on. So I can wait patiently and never bug you again on this topic.
All the ML features look so exciting that I will try to save up and buy a used T2i or T3i extra body and dedicate it to ML. So many times with cameras, I frustrate that they almost do what I bought them for. I think it's so wonderful you ML guys do what do, enabling so many to create in new ways. That you dedicate your hearts and minds to creating solutions is very incredibly great. I applud you! Thanks. :D
Agreed. I appeciate the efforts and skills of the developers and testers. Thank you all. Good luck and good speed with progress.
Hello ladies, gentleman, and trolls...
In the interest in impartiality, and with the understanding that there has been some animosity/impatience brewing on the ML release for the 650D, let me articulate both sides of the issue and maybe propose something that will assuage the angst of waiting for an official ML release.
On the one hand, we have people like nanomad who have spent considerable personal time porting ML to the 650D. It isn't relevant why he's doing this, other than to point out that he isn't being paid. He owes no one anything, and if anyone is a better coder/hacker then they should step up to the plate themselves and stop looking a gift horse in the mouth.
On the other hand, some people have certain expectations, unwarranted or otherwise, of individuals who are identified and "privileged" as ML team members. Some feel that there are others waiting in line with the time and skill to do what the guys who were given cameras bought with donation money should have finished by now. After all, its been six months and it hasn't even reached alpha.
So these are the two opposing perspectives, each biased with their own interests in mind. Where is the common ground?
To me this is about setting expectations. There was an unwarranted expectation that an alpha would be available early on in the year based on the progress of the M and previous ports. People are not good at accepting "when it's done" as an answer, even if what they are waiting for is free. I'm not sure why exactly, that's just the way it is.
Because so many ML enthusiasts are laymen when it comes to understanding the coding aspects of ML, it would be a noble gesture for the current coding team to provide a run-down of what has been completed and what specific work yet needs to be done before a stable release is made. And then the laymen will return that noble gesture with one of their own: Stop whining like little bitches.
Fair?
You'll never ever stop people whining.
And detailing all the changes with an essay on what's still to come and ETA, is just taking development time away for the whingers.
It will come when it comes is a perfectly reasonable response to anyone who understands they aren't owed anything! And anyone who doesn't understand that they aren't owed anything should be ignored!
I think the main issue was that the boot flag fir had the possibility of bricking some cameras. Rather than release it went into closed beta testing.
Wanna know what is/isn't likely working? I don't see a private repo for nanomad so :
https://bitbucket.org/hudson/magic-lantern/src/e6744dc12079864bdc930252e7d906835342f08e/platform/650D.101/features.h?at=unified
https://bitbucket.org/hudson/magic-lantern/src/e6744dc12079864bdc930252e7d906835342f08e/platform/650D.101/internals.h?at=unified
Its in terms I would hope people understand at least somewhat.
From what I see there are EOSM style issues with syncing overlays, etc. Honestly though, some of these comments are pretty demotivating.
Thought i'd try to shed some sunlight on this thread. I am an aspiring filmmaker and got my T4i 3 months ago and went with Canon for my first DSLR mainly for ML. I am a long time Linux user and could easily compile the pre-alpha myself but it took me about 2 years to get my first DSLR and would rather play it safe and wait. I fully trust and appreciate everything the ML team is doing and will patiently wait for an official release.
Like all of us I'm a busy guy. I can't believe some of the whining I'm seeing on here. Thank you ML folks for all the work you're doing for whatever reasons you're doing them. I'm super anxious to be using ML on my camera, and so grateful for all that you're doing to get ML running on the t4i.
One piece of feedback, make it easier for folks to donate to you. I only looked for a minute, but couldn't find it... part of my job is building websites, having that "DONATE" button in the face of each user might help getting the message through that this is a voluntary pursuit and if they really wanna help, put their money where their mouth is.
I'll take a look and am sure I'll find it, but either way, thanks.
Quote from: shaunlaf on April 26, 2013, 04:47:30 PM
I only looked for a minute, but couldn't find it... part of my job is building websites, having that "DONATE" button in the face of each user might help getting the message through that this is a voluntary pursuit and if they really wanna help, put their money where their mouth is.
I'll take a look and am sure I'll find it, but either way, thanks.
They are no longer accepting donations. Although i think they should to help pay for hosting, bandwidth, machines to compile on and so on....
I agree,
I have been looking forward to this as well, but don't wanna rush the dev's or make them feel undue pressure.
That being said, I am more than willing to donate to this. These guys are working really hard to make our lives easier, if I met them in person the least I'd do is buy them a beer. Donating to this would be the virtual "beer's on me".
Guys, we can follow a little of what's going on here:
https://bitbucket.org/hudson/magic-lantern/commits/all
Please stop bothering and demotivate the guys who are doing it for free.
okay for those freaking out about the T5i coming out and T4i being dropped in dev well considering older camera models are still being worked on, I dont see that as an issue and considering there practically no difference between the T4i and T5i, bring a port over may not be difficult, I cant say Im not a coder but in any case, the efforts for the t4i will continue (I hope).
I also agree, am I biting at the bit to try out ML on my T4i of course, who wouldnt be? but I have worked in software, worked as a tester and so on and can tell you that trying to work on something on your own personal time can be tough when you have this thing called life popping up which tend to have far more priorities then something like this.
So please stop with the negative comments, that is the quickest way to end development then it is to help spur it on, I have seen it happen and have been sadden by such... so only positive comments please.
I for one am grateful and hope everything is going well with everyone involved both with the project and with their personal life. Keep up the great work.
Quote from: Phillips321 on April 26, 2013, 04:50:56 PM
They are no longer accepting donations. Although i think they should to help pay for hosting, bandwidth, machines to compile on and so on....
We got that covered for now :-)
Like someone else mentioned.. what keeps me happy and hopeful about the 650d Port is the number of views for 650d 110635 Views! 8)
Even in number of replys only second to 6D 993 Replies
Update:
- Added a better fw signature for the 650D
- Fixed MagicZoom vsync
woot ^_^
Thanks for the update nanomad! Hope the rest of your work with 650d goes smooth :). Have a nice weekend!
LOVE the "virtual beers" idea.
Maybe in real-life, somewhere, sometime? I travel a lot. Overseas mostly, but get around the country now too quite often. Solo, run&gun shooter, have-equipment-will-film kind of stuff. So just maybe..., that would be cool, eh? Do a film about a guy who goes around the country just to take ML code-runners out to dinner and drinks? Who's up for it? Wait..., Canon would send a hitman in for sure..., well..., maybe not the greatest idea...
For what it's worth I used ML on my 550d and loved it, then I upgraded to the 650d knowing that ML was not available for it. I really miss ML but I'm prepared to wait however long it takes, and I will never be able to thank the developer enough for all his hard work!
Quote from: nanomad on April 27, 2013, 02:00:56 PM
Update:
- Added a better fw signature for the 650D
- Fixed MagicZoom vsync
Nanomad, does the better firmware signature mean that boot problem that could brick a camera is fixed? And no more flickering magic zoom is very nice!
I know this is a strange request but could some of the people testing, make little videos to show off whats working and so forth, I think this could help feed some peoples desires of ML. ^_^
oh and when I say videos, I mean shots showing the software in action so I guess you would need a camera to film the camera so that might not be as plausible as I was thinking in my head. ^^;;
With all the interesting developments around the 5Dmkii/iii maybe being able to save raw image's without shutter action, at a reasonable speed. (http://nofilmschool.com/2013/04/magic-lantern-raw-video-canon-5d-mark-ii-iii/ (http://nofilmschool.com/2013/04/magic-lantern-raw-video-canon-5d-mark-ii-iii/)) I'm interested to know if this might be able with the 650d?
It works on EOS M to save the DNGs already but I can't get the Lv recorder (or other modules) working... so maybe nanomad will have better luck on a more robust camera.... No clue if 650D is as crippled in regular live view.
I found a download link for 650D alpha 1, is it an early stage alpha? ???
https://bitbucket.org/hudson/magic-lantern/downloads
Quote from: Aborgh on April 28, 2013, 10:27:54 AM
I found a download link for 650D alpha 1, is it an early stage alpha? ???
https://bitbucket.org/hudson/magic-lantern/downloads
if its not been posted here in this thread by one of the devs or testers then well I wouldnt trust it as far as I know its still closed testing.
Oh alright! New to this forum so I do not know how things work here!
Thanks!
Quote from: Aborgh on April 28, 2013, 10:27:54 AM
I found a download link for 650D alpha 1, is it an early stage alpha? ???
If I am correct this is the source code from last month. If you have the skills you can compile your own version from this code. Unless you know what you are doeing I would not advise this
There is no precompiled public version available at the moment. A closed alpha is a viable to selecte testers, however this is still an early version. However progress is being made and when it's safe it will be released.
ca begin has smell nice
Quote from: blade on April 28, 2013, 11:14:29 AM
If I am correct this is the source code from last month. If you have the skills you can compile your own version from this code. Unless you know what you are doeing I would not advise this
There is no precompiled public version available at the moment. A closed alpha is a viable to selecte testers, however this is still an early version. However progress is being made and when it's safe it will be released.
There are no real skills required to compile the source code but I understand why you advise against it since it may brick your camera but I think people that want to go for it should know how easy it really is to compile. 1: ./configure, 2: make, 3: make install.
Quote from: newsense on April 28, 2013, 11:49:41 AM
There are no real skills required to compile the source code but I understand why you advise against it since it may brick your camera but I think people that want to go for it should know how easy it really is to compile. 1: ./configure, 2: make, 3: make install.
Is it like compiling a build on android or completely different?
Way easier if you use the pre-configured virtual machine ;)
Quote from: nanomad on April 28, 2013, 12:37:23 PM
Way easier if you use the pre-configured virtual machine ;)
Haha, yes if you know what you are doeing! Out of curiosity I downloaded the virtual box image and got the latest code downloaded... Thereafter it became to difficult for me... But then again if I see a command line I het scared :-)
My question is how safe is ML for the 650D in the current state? I saved up for literally 2 years to get a DSLR. That being said would any of the devs here say it's safe but just not complete or any tips on running it and avoiding bricking?
Quote from: nanomad on April 28, 2013, 12:37:23 PM
Way easier if you use the pre-configured virtual machine ;)
Where can I get the VB image and does it have the latest ML source?
I just want to get some things straight
ML does not modify the firmware right?
Does ML flash any firmware onto the camera?
When ML installs what exactly does it install?
Quote from: Aborgh on April 28, 2013, 01:31:00 PM
I just want to get some things straight
ML does not modify the firmware right?
Does ML flash any firmware onto the camera?
When ML installs what exactly does it install?
1. It does modify the firmware, part of why it is currently un-safe.
2. Well, it doesn't flash a firmware but it does modify part of the on-camera memory, which is why it is potentially un-safe and why the 650D Magic Lantern port has not been released for testing.
3. It changes the 'boot-flag' on the camera's memory (IE. Not on the SD card but the camera itself) that IIRC tells the camera to look on the SD-card for a debug firmware (Which is there for when Canon is doing testing/etc I imagine).
I posted the link to the VB image a couple pages back,
I'll edit it in shortly.Here it is: http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip
But it doesn't come with the latest source, so you'll need to grab the latest from bitbucket.
And because someone mentioned it on this page, no, it is not currently safe.
Thank you very much all of you involved with this project for your effort, dedication and ingenuity.
Any predictable timing on 650D stable or even beta port? Mine is anxious to take some nice time lapses =)
I ask because I don't want to buy one of those expensive remote controllers with timed repetitive shutter release, as ML can do that and much more...
News is found either by a developer posting here or on the source code repository: https://bitbucket.org/hudson/magic-lantern/commits/all.
Hi I found this on the internet
Magic Lantern Unlocks RAW Video on the Canon 5D Mark II and Mark III
http://nofilmschool.com/2013/04/magic-lantern-raw-video-canon-5d-mark-ii-iii/ (http://nofilmschool.com/2013/04/magic-lantern-raw-video-canon-5d-mark-ii-iii/)
I hope this will come on 650D 6D 7D or 60D
Quote from: Lucas_W on April 28, 2013, 02:02:39 PM
1. It does modify the firmware, part of why it is currently un-safe.
2. Well, it doesn't flash a firmware but it does modify part of the on-camera memory, which is why it is potentially un-safe and why the 650D Magic Lantern port has not been released for testing.
3. It changes the 'boot-flag' on the camera's memory (IE. Not on the SD card but the camera itself) that IIRC tells the camera to look on the SD-card for a debug firmware (Which is there for when Canon is doing testing/etc I imagine).
I posted the link to the VB image a couple pages back, I'll edit it in shortly.
Here it is: http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip
But it doesn't come with the latest source, so you'll need to grab the latest from bitbucket.
And because someone mentioned it on this page, no, it is not currently safe.
OK right! Thanks for that :)
If bootflag does not work then there is no chance of bricking the device since bootflag does not show where the device should boot from. So the bricking device thing is in the bootflag?
Ok, here are the "dangerous" things ML can do:
- Fail the enable bootflag stage (happened in pre-alpha1) -> Camera boots only via SD, internal FW disabled. An ad-hoc firmware update made by alex recovered those cameras. The bug in the installer should be fixed already.
- Write a wrong value to a prop -> Camera enters an ERR70 loop. We may be able to fix it by skipping the error, restoring a correct value and rebooting. Untested. Alphas have props disabled anyway.
- Boot an incompatible firmware version because of the missing firwmare signature check. Anything can happen, including completely wiping out the ROM. I've added the signature but some cameras refused to boot because they had a different signature. I should have fixed it yesterday (I hope)
- Call unsafe canon functions / Poke the wrong registers. See previous point for effects.
Btw, send me a PM if your 650D has the bootflag on (I wiped the old ones, so I don't remember who had it)
So there is a "backup" function! That is good, at least for closed private testers :P
Quote from: nanomad on April 28, 2013, 03:37:23 PM
Btw, send me a PM if your 650D has the bootflag on (I wiped the old ones, so I don't remember who had it)
Just double checking for clarity. You want us to PM you if we had the bootflag bug or just anybody who have had installed (or attempted to) your pre-alpha?
I've had tried out the pre alpha and loved it. Lost the file (my fault with formatting) though so I'm really stuck with the vanilla T4i, heh.
If you could run the pre-alpha then you can send me a PM
QuoteBoot an incompatible firmware version because of the missing firwmare signature check
I think this to be fixed for all digicV... my 113/112 bins would cross boot to black screen and I was like WTF.
I would love to try to run the pre-alpha but since there are no compiled builds around and I do not have the time or skills to compile a build I can not help you!
I actually still run the first pre-alpha1 for my videography life. it works and never fails me. therefore i really eager to check out the updates you've been working on. i use it for basic stuff: extra iso, focus peaking(helps a lot), zebra, and cropmarks. the other feature i love is hdr movie and intervalometer. hope you guys will release the most stable alpha ever. cheers! ;D
hello there,
first i want to thank you for developers work.
and second: i read roterrion's post and curious, can i test this version?
(and a little bit offtopic: im the only one who disappointed with the 650d image and video quality? )
Quote from: ejszarny on April 28, 2013, 09:27:13 PM
hello there,
first i want to thank you for developers work.
and second: i read roterrion's post and curious, can i test this version?
(and a little bit offtopic: im the only one who disappointed with the 650d image and video quality? )
Im not disappointed but then again it comes down to the lens and settings being used.
Quote from: kazeone on April 28, 2013, 09:30:06 PM
Im not disappointed but then again it comes down to the lens and settings being used.
This.
I was disappointed until last week when I had to do a lot of video shooting. Did some research for best setting for green screen and found out various tip and tricks to set up the camera for better video recording. The quality is so much better now.
Quote from: kazeone on April 28, 2013, 09:30:06 PM
Im not disappointed but then again it comes down to the lens and settings being used.
i see too much noise from iso400 and the video is completely a disappointment for me. 3 monts ago i try lots of setting but really not help for me...
Quote from: ejszarny on April 28, 2013, 09:44:16 PM
i see too much noise from iso400 and the video is completely a disappointment for me. 3 monts ago i try lots of setting but really not help for me...
well I would say direct this question in the photo forum so we can address it further verses this dev thread. Video was always secondary, if you want dedicated video then you want their C "Cinema" line but ML is working on making that better :)
Sure you're not just under exposed? I've been shooting on the 5D MII and 7D for two years and just started using the 650D and to be honest, cannot justify the price difference when it comes to video (judging by the quality I got from the different cameras)
Quote from: Shadeena on April 28, 2013, 09:49:21 PM
Sure you're not just under exposed? I've been shooting on the 5D MII and 7D for two years and just started using the 650D and to be honest, cannot justify the price difference when it comes to video (judging by the quality I got from the different cameras)
i do not want post too much offtopic, but no, sometimes i try in same position with different expo and settings, and all off them are bad, i think im too lame or this one camera i have a bit worst than other 650ds - or both.
and for example my 650d never shot 3 pic in a row in raw, only 2 and then wait - the factory description say 6 raw in a row.
i think this example what i cant do in wrong way...
Shitty card?
Video quality is OK... not much different than past generations.
On 6D probably doing better than 1DC except for 1DC cropping and mjpeg.
Quote from: 1% on April 28, 2013, 10:04:15 PM
Shitty card?
Video quality is OK... not much different than past generations.
On 6D probably doing better than 1DC except for 1DC cropping and mjpeg.
21MB/s samsung sdhc
Thats like kinda fast enough for digic IV.
You're missing about 9MB there to take up the whole interface. How big are raws? My 600D is shooting 6 raws in a row.
Do you shoot raw or raw + jpg? Only raw works fine for me, raw + jpg will make it pause after 3-4 shots if I remember correctly.
Quote from: 1% on April 28, 2013, 10:35:22 PM
How big are raws? My 600D is shooting 6 raws in a row.
My rawes are up to 27mb
Quote from: blade on April 28, 2013, 10:36:02 PM
Do you shoot raw or raw + jpg? Only raw works fine for me, raw + jpg will make it pause after 3-4 shots if I remember correctly.
both mode stops after 2pic and after one second shot the third.
i think too little the buffer in camera
Quote from: ejszarny on April 28, 2013, 10:43:33 PM
both mode stops after 2pic and after one second shot the third.
i think too little the buffer in camera
I think that it is likely your SD card having too slow mbps write speed. I had the same issue until I upgraded to 45 mbps and it was so much better.
Unless its like EOSM with its impressive 50MB of shoot malloc. You should be able to go at advertised speed unless your cards are too slow.
Remember with SD cards... mind the bits and bytes.
My 650d does work as advertised. That leaves the card
Speaking of card quality. I was on a budget when I got my card and didn't consider the card speed and quality and how it would effect my final output. Anyone know if the Sandisk Ultra 30mbps cards are any good?
for me no problem with sandisk mentioned below 95mb/s
Quote from: 1% on April 28, 2013, 10:50:52 PM
Unless its like EOSM with its impressive 50MB of shoot malloc. You should be able to go at advertised speed unless your cards are too slow.
Remember with SD cards... mind the bits and bytes.
121 of shoot malloc here.. Should be enough for at least 4 shots in raw (i can get around 6 with a 95 MB UHS card I think)
How is the buffer in 650D at idle? On EOS M its locked to 30fps like 720 lines... its actually taller & wider in zoom mode.
Quote from: ejszarny on April 28, 2013, 10:43:33 PM
both mode stops after 2pic and after one second shot the third.
i think too little the buffer in camera
Check to see if you have "Lens Correction > Chromatic Aberation Correction" ENABLED on the camera. If it is ENABLED, the camera will behave exactly as your describing (it will burst for 2 shots and then slow down) whenever it is writing JPEGS (includes RAW + JPEG).
Quote from: Chicolom on April 29, 2013, 09:55:15 AM
Check to see if you have "Lens Correction > Chromatic Aberation Correction" ENABLED on the camera. If it is ENABLED, the camera will behave exactly as your describing (it will burst for 2 shots and then slow down) whenever it is writing JPEGS (includes RAW + JPEG).
which if your using say Adobe Lightroom you can use its Lens correction profiles to do this for you instead of the camera
I set mine to enabled chromatic aberration correction and I can still burst shoot at ~5 frames. My SD card is 45mbytes/s though.
Correction of l 'aberration chromatic 3 photographs then slowing down :P
I deactivate it: nobody more of slowing down i to stop before filling the card sd :)
Quote from: Chicolom on April 29, 2013, 09:55:15 AM
Check to see if you have "Lens Correction > Chromatic Aberation Correction" ENABLED on the camera. If it is ENABLED, the camera will behave exactly as your describing (it will burst for 2 shots and then slow down) whenever it is writing JPEGS (includes RAW + JPEG).
thank you man!
i check it and disable, now shot 3 pic and after then slow down a little bit.
thank you :)
Quote from: Chicolom on April 29, 2013, 09:55:15 AM
Check to see if you have "Lens Correction > Chromatic Aberation Correction" ENABLED on the camera. If it is ENABLED, the camera will behave exactly as your describing (it will burst for 2 shots and then slow down) whenever it is writing JPEGS (includes RAW + JPEG).
Oh, wow! Thank you! I was pretty satisfied with my ~4 shots before it started slowing down (came from a camera that did 0.1fps). Now, AFTER slowing down, the camera still does at least 1.5 shots per second which is much better than before. It takes me about 8 to 9 shots before it started slowing down. I had attributed the higher fps I have seen mentioned elsewhere to a higher speed card (I got a 45mbps card).
Quote from: lostear on April 28, 2013, 09:34:35 PM
This.
I was disappointed until last week when I had to do a lot of video shooting. Did some research for best setting for green screen and found out various tip and tricks to set up the camera for better video recording. The quality is so much better now.
Where did you find these tips because I just purchased a t4i for my church and they do a lot of green screen announcements but when I shot one of the videos last week with MY t4i, I noticed it picked up the fabric lines (it was a spandex green screen material) and I'm not sure how well it's going to key out....PLUS I need to know how to teach my volunteers how to shoot with a DSLR and knowing how to shoot with a green screen would help. Thank you in advance.
Quote from: InFocusAV on April 30, 2013, 01:04:13 AM
Where did you find these tips because I just purchased a t4i for my church and they do a lot of green screen announcements but when I shot one of the videos last week with MY t4i, I noticed it picked up the fabric lines (it was a spandex green screen material) and I'm not sure how well it's going to key out....PLUS I need to know how to teach my volunteers how to shoot with a DSLR and knowing how to shoot with a green screen would help. Thank you in advance.
I just used the setting in the description of this youtube vid. (I'm deaf, i have no idea what is being said in the video though). My video did not have top quality but is was still a lot better than before. More clearer edges and whatnot. Until seeing this, I had no idea that the picture style setting also impacted the video quality.
http://www.youtube.com/watch?v=Ec2qufjpbao
It is not a green screen specific setting. Just getting better quality shot in general should help. If you still need more advice or tip with green screen, PM me and I'll try to help you as far as my limited experience can.
If the fibers of the fabric are showing blur the background.
I've keyed some exceptionally bad footage... a little fabric isn't too bad. Lighting is key.
Quote from: 1% on April 30, 2013, 01:40:03 AM
I've keyed some exceptionally bad footage... a little fabric isn't too bad. Lighting is key.
I agree. Practice working on your keying. I had once shot some bad green screen footage and it was so bad that we thought it was no good. I later went back to these abandoned footages and found out about screen matte which fixed everything for me. Apparently screen matte is a very simple technique. I now can do green screen fairly well thanks more to my better understanding of After Effect than my camera's setting.
Now, let continue this discussion elsewhere, please. We do not want to annoy all of those who subscribed to this thread in hope for any update (Including me, heh).
It feels like the silent picture feature is stealing the thunder! And it should :D Because it is awesome!
Time for a second pre-alpha.
This one is targeted at those that already have the bootflag enabled on the camera.
http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip
Instructions:
- Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar
- Copy over the files to the SD card
Known issues:
- Full screen magic zoom is broken
Stuff I'd like to be tested:
- Card benchmark under the debug / benchmarks menu (Post a screenshot if you do)
- HDR video (check if all the frames are in sync, e.g. no half exposed frames). Do this at every possible resolution / fps combination
- Everything else
Build still has props off, so expect some bugs here and there
If you really want to make your camera bootable you can use the devkit available on the repository inside the 650D platform folder). JUST DO NOT RUN THE FIR IN MOVIE MODE, USE PHOTO MODE AND TURN THE DIAL TO M
Quote from: nanomad on April 30, 2013, 03:38:23 PM
Time for a second pre-alpha.
This one is targeted at those that already have the bootflag enabled on the camera.
http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip
Instructions:
- Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar
- Copy over the files to the SD card
Known issues:
- Full screen magic zoom is broken
Stuff I'd like to be tested:
- Card benchmark under the debug / benchmarks menu (Post a screenshot if you do)
- HDR video (check if all the frames are in sync, e.g. no half exposed frames). Do this at every possible resolution / fps combination
- Everything else
Build still has props off, so expect some bugs here and there
If you really want to make your camera bootable you can use the devkit available on the repository inside the 650D platform folder)
Yes! Thank you! Installing this right now. I'll report back if I encounter any issues or bugs.
Out in the feeld today, but will install the minute I get home! Tx
Zebras and focus peak is not showing up on liveview.
Even if I have Global Draw enabled on liveview, all of the options on that page is grayed out.
(googled this just to see if I did a newbie mistake and missed something obvious about ML, couldn't find out anything)
The help text was red and blinking at some point, but the user interface experts didn't like it ;)
Quote from: a1ex on April 30, 2013, 04:06:29 PM
The help text was red and blinking at some point, but the user interface experts didn't like it ;)
Yeah, I don't agree with that choice either.
Anyway, cycle LV screens a couple of times with the INFO button
Quote from: nanomad on April 30, 2013, 04:09:30 PM
Yeah, I don't agree with that choice either.
Anyway, cycle LV screens a couple of times with the INFO button
This helped with the zebras and focus peak. Apologies for the newbie mistake. I'll be testing out everything after this Thursday once I finish all of my end of the semester's projects.
Many thanks to you, Nanomad!
Quote from: nanomad on April 30, 2013, 03:38:23 PM
Time for a second pre-alpha.
This one is targeted at those that already have the bootflag enabled on the camera.
http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip
Instructions:
- Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar
- Copy over the files to the SD card
Known issues:
- Full screen magic zoom is broken
Stuff I'd like to be tested:
- Card benchmark under the debug / benchmarks menu (Post a screenshot if you do)
- HDR video (check if all the frames are in sync, e.g. no half exposed frames). Do this at every possible resolution / fps combination
- Everything else
Build still has props off, so expect some bugs here and there
If you really want to make your camera bootable you can use the devkit available on the repository inside the 650D platform folder). JUST DO NOT RUN THE FIR IN MOVIE MODE, USE PHOTO MODE AND TURN THE DIAL TO M
This is awesome. Woke up to let the cat out and planned on going back to sleep but not after seeing this. I was just wondering if there are any features that are known to be buggy that maybe we should just not use for now? I really want to help test(and check it out for myself) but want to be as cautious as I can with my baby ;)
I'd avoid full screen magic zoom and FPS control if you want to be safe, but that's it
Good Morning, so excited to finally test out Magic Lantern on my 650D, I tried installing it and went through all the steps, (Low lvl format, EOScard, and passing over the files) and turned on my camera and couldnt get ML to work.
I passed over the ML folder and overwrited the autoexec file that EOScard put in my SD card for the one in the ML pre-alpha. Did I do something wrong?
Does your camera have the bootflag enabled? ::)
How does one enable the bootflag?
Many thanks
N
Quote from: nanomad on April 30, 2013, 03:38:23 PM
Time for a second pre-alpha.
This one is targeted at those that already have the bootflag enabled on the camera.
http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip
Instructions:
- Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar
- Copy over the files to the SD card
Known issues:
- Full screen magic zoom is broken
Stuff I'd like to be tested:
- Card benchmark under the debug / benchmarks menu (Post a screenshot if you do)
- HDR video (check if all the frames are in sync, e.g. no half exposed frames). Do this at every possible resolution / fps combination
- Everything else
Build still has props off, so expect some bugs here and there
If you really want to make your camera bootable you can use the devkit available on the repository inside the 650D platform folder). JUST DO NOT RUN THE FIR IN MOVIE MODE, USE PHOTO MODE AND TURN THE DIAL TO M
So for those that don't have the boot flags enabled we are not able to run this pre alpha?
ooooh my god this made my dayyyy! :D :D :D
I'll be testing this tonight if someone can explain how to enable the bootflag. I was already planning on doing some greenscreen tests, now I have this to look forward to as well!
Got home, did the low level format etc etc. and it works.
I will start testing in detail tomorrow. Thanks everyone !
Quote from: SlimSpydey on April 30, 2013, 05:56:59 PM
I'll be testing this tonight if someone can explain how to enable the bootflag. I was already planning on doing some greenscreen tests, now I have this to look forward to as well!
you need EOSCard
Cool! Would make my day even better if I knew where to find the bootflag fir! I would love to test it! I even have 2 650d's so if I brick one I'm not SOL! ;)
Thanks for all your Hard Work!
Quote from: newsense on April 30, 2013, 06:02:38 PM
you need EOSCard
Is that just the canon utility? If not where can I download it?
can u give me the firmware link. i have canon 650D
software to make the card bootable: http://wiki.magiclantern.fm/3rd_party_software
ML Alpha2 for 650D: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip
Instructions: http://www.magiclantern.fm/forum/index.php?topic=3697.msg32446#msg32446
Quote from: newsense on April 30, 2013, 06:08:16 PM
software to make the card bootable: http://wiki.magiclantern.fm/3rd_party_software
ML Alpha2 for 650D: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip
Instructions: http://www.magiclantern.fm/forum/index.php?topic=3697.msg32446#msg32446
You sir are a saint and a scholar.
Quote from: SlimSpydey on April 30, 2013, 06:09:24 PM
You sir are a saint and a scholar.
Haha thanks. Off to play and test ML now before the rain starts.
thanx mate
Pre-alpha (the first one) worked after following the instructions. Clear, easy to follow, step by step.
This one is ... well ... not that easy to follow, softly spoken. As time of writing: Not working.
Ciao, Walter
Quote from: Walter Schulz on April 30, 2013, 06:36:13 PM
Pre-alpha (the first one) worked after following the instructions. Clear, easy to follow, step by step.
This one is ... well ... not that easy to follow, softly spoken. As time of writing: Not working.
Ciao, Walter
Not working is not really an answer, what's not working? What error do you get? Does it boot to ML menu? Is the camera bootable? Is the card bootable?
i cant load ML on cam, am new to this ML stuff, will it destroy my cam if ML got error or somthing
This was intentional, nanomad. I think the instructions needs to be reworked and any attempt to solve my individual problem will be time wasted as handling a symptom, not the cause. Let's wait a moment to see if others have similiar problems.
Ciao, Walter
I too am unable to load ML,
I set the card to be bootable with MacBoot, but I don't know how to set the Boot Flag on as well.
is this version removes iso control? 160,320,etc from the first pre-alpha?
How can I enable the BootFlag on my 650D for Magic Lantern to work?
Quote from: SlimSpydey on April 30, 2013, 06:59:58 PM
I too am unable to load ML,
I set the card to be bootable with MacBoot, but I don't know how to set the Boot Flag on as well.
Did you check "Make DSLR Bootable" ?
Quote from: alesis_neo on April 30, 2013, 07:08:52 PM
How can I enable the BootFlag on my 650D for Magic Lantern to work?
Read my post #1081
Quote from: newsense on April 30, 2013, 07:12:02 PM
Did you check "Make DSLR Bootable" ?
Yea I did, I then copied the ML files to the root of the SD card and booted my camera,
I was unable to open ML at all from there.
Is there another step I'm missing?
(BTW thanks for the help!)
My card is bootable, the problem is the my camera isnt.. :(
i think its not with our Cams. i think the wrong is in that zip file
dont try guys, i think version is mismatch
Quote from: MarlonSenanayake on April 30, 2013, 07:28:36 PM
i think its not with our Cams. i think the wrong is in that zip file
There are some specific steps to make our camera bootable frist before you can even boot Magic Lantern. Please read the original post. You will see that there is a small print hinting on how you might make your camera bootflag enabled. This is somewhat risky and should be done carefully.
That ZIP file is okay. It worked well on those of us who had already enabled the bootflag on our camera before. It is indeed your camera's bootflag that need to be enabled. And if you are new to this kind of thing, you are better off just waiting for the official release if you cannot risk breaking your camera.
You need to enable the bootflag in your camera. And the only way to do that is with a firmware update. Which i dont think has been released publicly. So if you have it from the first release then you can run ml if not then you need to wait more. I wish i had it!
Quote from: Cliff on April 30, 2013, 07:40:32 PM
You need to enable the bootflag in your camera. And the only way to do that is with a firmware update. Which i dont think has been released publicly. So if you have it from the first release then you can run ml if not then you need to wait more. I wish i had it!
yea i think its better to wait for public release
Quote from: lostear on April 30, 2013, 07:37:43 PM
There are some specific steps to make our camera bootable frist before you can even boot Magic Lantern. Please read the original post. You will see that there is a small print hinting on how you might make your camera bootflag enabled. This is somewhat risky and should be done carefully.
That ZIP file is okay. It worked well on those of us who had already enabled the bootflag on our camera before. It is indeed your camera's bootflag that need to be enabled. And if you are new to this kind of thing, you are better off just waiting for the official release if you cannot risk breaking your camera.
thnx bro
Was so excited to test the pre-alpha2, but I guess I can't since bootflag isn't enabled, only pre-alpha1 testers can do it since there is no firmware dumper available yet.
Does anyone have a link to the DevKit, I see the small text but no link to the "repository" where I can download it.
EDIT: Ignore my noobiness, I found it and was able to set the bootflag and install ML.
At this point it seems a bit buggy, as it was jumping from liveview to menu's and a No Image screen, but after it ran for a bit that went away.
I will try to make a tutorial video tonight on how to go about installing ML on the 650D, from a bone stock camera.
Thank you nanomad for this update! I have loaded the new version, and is ready to play with it :) First impression is good!
And about people complaining about an vague installation instruction, i think it on purpose; Remember this is still an PreAlpha, and I don't recommend it for you if you haven't read at least this thread. I think you will find some hints someplace (think I have seen so...) But I am lucky - my camera was Bootflag-enabled at the first PreAlpha, so I don't have to look for it 8)
it works. i booted just right now, its working
The instructions were vague on purpose. I don't want people running it without thinking a bit. Heck it's not even an alpha.
But once again it's clear that people don't even read the second line, let alone the fine print.
Quote from: nanomad on April 30, 2013, 08:38:04 PM
The instructions were vague on purpose. I don't want people running it without thinking a bit. Heck it's not even an alpha.
But once again it's clear that people don't even read the second line, let alone the fine print.
Good thinking,
Even though i went into the installation confused, having to look into it forced me to learn about how the camera works and the dangers involved.
That being said, I'll hold off on doing a tutorial video which will hopefully keep people from bricking their cameras.
seriously, I guess common sense or patients is lacking with people, you specifically declared that this was for testing with people already set up for testing, not for adding new people who have never done this before which means would offer no assistance in fixing any problems since they have no clue in how to load the firmware to begin with which screams put your camera down and walk away before you hurt yourself... ~_~
Let the people who know what they are doing work on this and stop being hassled by all the newb questions on something clearly people have no idea and this way they can actually focus on working and making this better instead of wasting time answering questions that shouldnt be asked at this time.
this is awesome, how long will it take to release stable for 650D
Magic Zoom box is flickering, not work poperly
Quote from: MarlonSenanayake on April 30, 2013, 09:17:16 PM
Magic Zoom box is flickering, not work poperly
Tell me
- video mode resolution and FPS (even if in photo mode)
- magic zoom settings, all of them
Quote from: nanomad on April 30, 2013, 09:20:57 PM
Tell me
- video mode resolution and FPS (even if in photo mode)
- magic zoom settings, all of them
video mode resolution - 1080p 24fps
magic zoom - (+) , Med, TL, 2:1 (this is how it shows, i don't know)
Got a fix, gonna try it
video mode. when in standby it flicker heavily, when recording it low flickering. and when recording small line appear middle of screen.(when magick zoom box on)
Nanomad, and all the other devs.... Thanx
Now i will give my smaal contribution:
As requested:
https://www.dropbox.com/s/jfr1fpdv43fz2mc/Sandisk%2032GB%2045MB%3As.BMP (https://www.dropbox.com/s/jfr1fpdv43fz2mc/Sandisk%2032GB%2045MB%3As.BMP)
I have seen other cards perform a lot faster aldo this is in line what the card is supposed to do.
I did the stuptest: 1 fail.
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1ad108
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1ad0c0
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x1ad0a0
[Pass] bar => '*****hjkl;'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0x81282
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0xbe498
[Pass] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x0
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x4
Date/time: 2013/04/30 15:09:04
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x6
[Pass] mod(s1-s0, 60) => 0x2
[Pass] mod(s1-s0, 60) => 0x2
m0 = MALLOC_FREE_MEMORY => 0x4f0a0
[Pass] p = malloc(50*1024) => 0xf0800
[Pass] CACHEABLE(p) => 0xf0800
m1 = MALLOC_FREE_MEMORY => 0x42890
free(p)
m2 = MALLOC_FREE_MEMORY => 0x4f0a0
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] p = AllocateMemory(256*1024) => 0x7f5d58
[Pass] CACHEABLE(p) => 0x7f5d58
m1 = GetFreeMemForAllocateMemory() => 0x3590fc
FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x4f0a0
m02 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] p = alloc_dma_memory(256*1024) => 0x407f5d98
[Pass] UNCACHEABLE(p) => 0x407f5d98
[Pass] CACHEABLE(p) => 0x7f5d98
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x407f5d98
free_dma_memory(p)
[Pass] p = (void*)shoot_malloc(24*1024*1024) => 0x4a000068
[Pass] UNCACHEABLE(p) => 0x4a000068
shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x4f0a0
m12 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0xc9220004
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id((unsigned int)get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0xc96c00b2
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0xc9f20294
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0xca8400c2
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x4
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x407f5d98
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x4
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
SW1(1,100)
[FAIL] HALFSHUTTER_PRESSED => 0x0
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
I will test most settings with the standard settings, if not if will make a note:
Overlay menu:
Zebras:
Color space
RGB:OK
luma: OK
lumafast:OK
Underexposure:OK
Overexposure OK
When recording:OK
Focuspeak:OK
Did not play with the sup settings.
Magic Zoom: Not 100% OK Image is flickering in 2:1 and 3:1 mode. In 1:1 mode fast flickering
Trigger mode: OK (only + tested)
Size: OK Only medium tested
Position:
Focus box OK
Top-Left: OK
Top-right: OK
Bottom-right: OK
Bottom-left:OK
Cropmarks:OK
Bitmap : 5/5 OK
Show in photo mode:OK
Show in play mode: OK
Ghostimage:OK
Autoupdate:OK
Spotmeter:OK
Unit:
Percent:OK
0..255:OK
rest: not tested
Spot position:
Focus box:OK
Center:OK
False color:Not 100% ok?? A box as in spotmeter ( that is off) remains in the middel of the image and is not effected.
Marshall:OK
SmallHD:OK
50-55:OK
67-72:OK
banding detection:OK
Greenscreen: I do not have a green screen, seems to work but cant confirm
Histogram: OK
Color space:
Luma:OK
RGB:OK
scaling:
Log:OK
Linear:OK
Clipwarning:OK
Waveform:OK
small:OK
medium:OK
large:OK
Vector scope: OK
UV scaling 2x:OK
More to come. I will test a complete menu en reference to my other posts.
Thats all for now...
nomad. it flick also in photo mode. two box appear on screen, magic zoom box and. samll one middle on screen
Quote from: MarlonSenanayake on April 30, 2013, 09:46:10 PM
nomad. it flick also in photo mode. two box appear on screen, magic zoom box and. samll one middle on screen
That's how it works, the small box is where the zoom box is looking at
Quote from: nanomad on April 30, 2013, 09:36:16 PM
Forgot to ask...video or photo mode? If video mode, was it recording?
(I guess video mode, stby)
For me in Photomode the image inside the box flickers every 3-4 seconds.
In movie mode the lower 1/3 of the box is flickering wile the top 2/3 are fine. This is also true while recording.
Got it fixed in video mode, but the LV "corruption" is still there
Quote from: nanomad on April 30, 2013, 09:48:03 PM
That's how it works, the small box is where the zoom box is looking at
not that box buddy. ill upload a photo tomorrow, same box look like magic zoom box
Quote from: MarlonSenanayake on April 30, 2013, 09:55:55 PM
not that box buddy. ill upload a photo tomorrow, same box look like magic zoom box
Great thanks.
Looks like the 650D maxes out at around 40MB/s ... what a shame
Just got this working! Its 03:02 here in sweden so will start testing it tommorow and provide the feedback needed! Thanks alot for releasing it to everyone this time! :D
This is totally worth the wait! :D
Loving ML so far. Didn't really have time to really test it today but I plan on testing tomorrow. I hope I don't upset anyone but I thought i'd share howto make you camera bootable, enable the SD card bootflag and howto load ML. This assumes you know a little about virtualization or are able to look into howto load the image and get the .fir file onto the SD card on your own as I won't go into detail on that.
Instructions:
Make the camera bootable
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-Download one of the VM guest OS images. (I chose the VMware image and enabled hardware virtualization on my motherboard)
-start the guest OS.
-copy ~/magic-lantern/platform/650D.101/devkit/650D-safe-dumper.fir to the root of your SD card
-Place the SD card in the camera navigate to the fourth wrench menu and select firmware, camera, than select ok.
OR (easy)
-Download the .fir file from https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified (Thanks to Lucas_W for pointing out the link, I would have uploaded the .fir myself but thought who would use firmware from some stranger)
Enable the bootflag on the SD card:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar ( software to make the card bootable: http://wiki.magiclantern.fm/3rd_party_software )
Install Magic Lantern
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- Copy over the files to the SD card ( Download ML Alpha 2 for the 650D here: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip and unzip to the root of your SD card. You should than have a ML folder and an autoexec.bin on the root of your SD card.
Quote from: nanomad on April 30, 2013, 09:48:03 PM
That's how it works, the small box is where the zoom box is looking at
http://www.mediafire.com/?72vh8vja86y5jdc this is the two boxes i mentioned, small pink lines appear on screen when switch to photo mode, and also flicker ini video mode
nomad can u please unable manual white balance option insted ow presets and custom whitebalance
Quote from: MarlonSenanayake on May 01, 2013, 07:01:36 AM
http://www.mediafire.com/?72vh8vja86y5jdc this is the two boxes i mentioned, small pink lines appear on screen when switch to photo mode, and also flicker ini video mode
That's exactly the indicator of the region analyzed by magic zoom
Flickering and corruption will be fixed in the next build
Is there any difference in the files you released and the custom-compile with the source-code?
@Newsense Why bother downloading the VM when you can get the .fir here? https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified
Quote from: Lucas_W on May 01, 2013, 01:01:35 PM
Is there any difference in the files you released and the custom-compile with the source-code?
@Newsense Why bother downloading the VM when you can get the .fir here? https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified
The source version may have more fixes. Props are disabled there too
But wouldn't the link be the updated version while the one that's included in the VM out-of-date?
Unless you're suggesting that doing 'make 650D' also makes a .fir?
Ah, you were talking about the .fir :D
That one rarely changes, but it's always worth checking out the latest source code in the event it got changed.
Perhaps, except it takes 5 seconds to download the .fir and on my connection about 45 minutes for the VM image :P Luckily I used my School's fibre and it only took 5 minutes.
EDIT: Oh right, you were talking about the first part of my original post for your reply. Oops.
how is the progress now nomad
will you be providing exposure (iso, aperture, shutterspeed, etc) menu as in first pre alpha on the alpha? even though i could use ML EV on the video menu to get 85, 160, 320 iso. but i just miss it :p. just asking.
Expo override mostly requires props... it will be in the betas
Clock in live view ignores time zone.
Camera time is set to GMT+2 w/ summer time (+3) but ML outputs it w/o thoes settings.
Quote from: roterrion on May 01, 2013, 02:25:10 PM
will you be providing exposure (iso, aperture, shutterspeed, etc) menu as in first pre alpha on the alpha? even though i could use ML EV on the video menu to get 85, 160, 320 iso. but i just miss it :p. just asking.
how to change iso. is there any specific way. i mean insted of iso button, i cant change ML iso
Movie > Image Finetuning > ML Digital ISO
Any chance of getting the 01_650d_dumper.rar file to make my 650D bootable?
Would really like to give this a try on the camera but it seems unless you have experience with a previous ML offering you are stuck and there is no clear information on how to get things up and running on the 650D.
I understand that if done incorrectly that there is a risk of damaging the camera but I still want to try this out.
Can anyone provide me with the appropriate files and install procedure to get this working?
Quote from: StreetShotz on May 01, 2013, 07:04:15 PM
Any chance of getting the 01_650d_dumper.rar file to make my 650D bootable?
Would really like to give this a try on the camera but it seems unless you have experience with a previous ML offering you are stuck and there is no clear information on how to get things up and running on the 650D.
I understand that if done incorrectly that there is a risk of damaging the camera but I still want to try this out.
Can anyone provide me with the appropriate files and install procedure to get this working?
If you follow this thread carefully, than you have all the info you need to get PreAlpha2 running on your camera.
If you can't figure it out with all this delicious information, than you're better off w/o playing with PRE alpha.
Quote from: laame on May 01, 2013, 08:37:15 PM
If you follow this thread carefully, than you have all the info you need to get PreAlpha2 running on your camera.
If you can't figure it out with all this delicious information, than you're better off w/o playing with PRE alpha.
As helpful as this is I have never installed ML on a camera before. I have however, had the pleasure of using it on a few cameras and was greatly impressed.
With 46 pages to sort through and so much "do this, don't do this, use this, unstable this...."
I'm good with everything except making the camera bootable. If anyone is willing to help (read: not just say above commented information as it is no help at all) I would be hugely appreciative. If not then I keep waiting.
Quote from: StreetShotz on May 02, 2013, 12:33:58 AM
As helpful as this is I have never installed ML on a camera before. I have however, had the pleasure of using it on a few cameras and was greatly impressed.
With 46 pages to sort through and so much "do this, don't do this, use this, unstable this...."
I'm good with everything except making the camera bootable. If anyone is willing to help (read: not just say above commented information as it is no help at all) I would be hugely appreciative. If not then I keep waiting.
one word "youtube" :)
Quote from: StreetShotz on May 02, 2013, 12:33:58 AM
As helpful as this is I have never installed ML on a camera before. I have however, had the pleasure of using it on a few cameras and was greatly impressed.
With 46 pages to sort through and so much "do this, don't do this, use this, unstable this...."
I'm good with everything except making the camera bootable. If anyone is willing to help (read: not just say above commented information as it is no help at all) I would be hugely appreciative. If not then I keep waiting.
The answer you are seeking was just a couple posts behind.
I hope it helps, worked for me. But be carefull.
Quote from: Lucas_W on May 01, 2013, 01:01:35 PM
@Newsense Why bother downloading the VM when you can get the .fir here? https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified
And were up and running... Now it time to learn how to work everything :) Thanks all!!!!
Wish there was somewhere else I could ask, but I have it installed now, everything looks great but none of the features seem to work at all....
Zebras, Focus Peaking...both on, overlay is selected for LiveView but I get nothing....I hate being a noob
Quote from: StreetShotz on May 02, 2013, 02:04:11 AM
And were up and running... Now it time to learn how to work everything :) Thanks all!!!!
How did you get it to work? If i may ask :)
Quote from: StreetShotz on May 02, 2013, 02:23:31 AM
Zebras, Focus Peaking...both on, overlay is selected for LiveView but I get nothing....I hate being a noob
Try pressing the info button while in LiveView.
Quote from: greenthoughts on May 02, 2013, 03:19:55 AM
Try pressing the info button while in LiveView.
Downloaded the fir file listed a couple posts above.
Downloaded the 650D Alpha2 file
Downloaded the program to make the SD card bootable.
formated SD card, dropped fir onto sd card, updated firmware on camera, removed SD card and installed ML Alpha2 650D made the SD bootable and installed into camera....BOOM!!! This is the greatest day since....yesterday!
Does this version of ML allow reverting to the original firmware temporarily and permanently as outlined in this FAQ?:
http://wiki.magiclantern.fm/faq#does_magic_lantern_completely_replace_canon_firmware
From the reading I have done you can revert back to original "Canon" stuff simply by running the Bootfix file...I may be mistaken, but I do believe you can go back to just Canon firmware.
To temporarily revert back to "pure-Canon" turn the camera off. Hold down the 'SET' button then switch to On. You should see "Magic Off" printed to the screen.
To permanently revert to Canon stock firmware I think you can do that by formatting the card in-camera and there should be an option to disable 'Keep ML'.
@StreetShotz I think running the bootfix firmware updater allows you to remove the bootflag, which would also permanently disable ML as well.
Quote from: StreetShotz on May 02, 2013, 04:36:27 AM
From the reading I have done you can revert back to original "Canon" stuff simply by running the Bootfix file...I may be mistaken, but I do believe you can go back to just Canon firmware.
Again, DON'T USE THAT FILE.
Oh, right. I'm always getting confused between the bootfix.fir and the safe-dumper.fir.
Since everyone is giving everyone advice and some people obviously give false/dangerous advice. Would it not be good if the moderators edit those posts and add some bold Admin edit: Don't do this or similar?
That would probably be helpful to many people that just suck up all the helping posts they see here. Much clearer than finding some later post that debate the correctness of the previous ones.
I don't think anyone is intentionally giving incorrect information. Also, the admins/developers have repeatedly said that this is a pre-alpha and even the officially released pre-alpha was intended for those apart of the first pre-alpha. So it kind of goes without saying that everything else is unofficial and not officially supported.
As I saw it, the idea of the pre-alpha 2 was for people already testing the pre-alpha to continue testing. If people are going to suck up all the helping posts, they'll do that regardless. and if there weren't any helping posts, they'd ask for some, as they have.
If you were passively meaning me, I try to give as accurate advice as I can and most of my advice is helpful [Like that 'bypass-the-45-minute-VM-download' it seems]. The only time I think I gave potentially dangerous information was when I gave out my autoexec.bin and a link to the bootfix.fir [See my post on my confusion over the two .firs], though I did explicitly say I wasn't responsible in that post, and the links were then edited out when nanomad saw what I had done wrong and no-one's cameras were damaged/bricked.
Of course no one give out false information on purpose, I never meant that. Well this time I kind of meant you, but other people do this as well. I don't mean any offence to you, most such errors are by mistake.
My point being that forums like these are not really suited for this kind of instructions since people just add walls of text after each other instead of updating some kind of relevant instruction list.
I know the release is not intended for everyone. But judging from the posts many people try it out anyway.
Anyhow, this is meta. Nevermind. I don't care. I will try ML soon anyway.
Cropmarks disappear when flipping screen. Also overlays are mirrored in self portrait screen position.
Noted.
Overlays re-appear on HS press
continues from post # 1115
I will skip the movie menu for now, as i have no pc today to review clips.
Shoot:
Advanced bracketing: No advanced bracketing in pre alpha :-(
Intervalometer: OK
tested different settings with snap simulation. All variables work as expected.
Motion detect:
Trigger by:
Frame diff: OK
expo change: OK
Steady hands: Fail Could not get a snap, also tested withoud snap simulation. Also played with trigger level 8-30 and detect size.
Detect size: small/medium/large: OK
Silent picture:
Simple:OK
Burst:OK
continuous:OK
Note: it is taking the .422 pictures, and they are on the card. I have not checked if they are OK
Shoot preference:
Pic at once: OK tested 1-3-5
Snap simulation: OK
Display
LV Brightness OK
LV contrast:OK
LV saturation:OK
LV display gain:OK
Color scheme:OK
Clear overlays:Not jet test due to short lunch break
Advanced settings: see above
Ok, I will finish the Display menu next time... So far everything is nice and stable. I did notice some flickering in the menu now and then, but noting i can reproduce.
Looking forward to the magic zoom fix.
Magic zoom is a pain. I managed to deflicker it but now it locks up the camera (keeps redrawing...)
Great work @devs!
Just installed the second pre-alpha and playing with it right now.
I think I just found a bug, though:
Quote from: blade on May 02, 2013, 01:47:19 PM
Intervalometer: OK
I cannot confirm that.
If the camera does not get focus confirmation, the intervalometer will attempt to take the shot, fail, refocus, and die, leaving the camera in a state where it eighter hangs completely, or focus just won't work anymore.
(standard factory settings, except for C.Fn 4 on 2 and C.Fn 6 on 1. and quality on raw. Mode M, AF-S, "normal" photo mode (not liveview).)
can you reproduce that and/or suggest a workaround?
As stated I only tested with snap simulation. So without actual taking a picture. The next time I test I will revisit this item
QuoteMagic zoom is a pain
I think for EOSM will just have to fall back to a different sync mode while recording. I have had no crashes or lockups, just the rec flicker.
Are the image overrides somehow working in non QR mode?
My motion detect is working on Steady Hands, so this may be intermittent. The setting I used was 8. I will have a better look at it later today.
.422 files are being made for me as well, but I can not get them to open. They error back saying they do not have a size, which I imagine refers to the 1920x1080 frame size.
Intervall is also cousing a lockup for me, if I have autofocus on. If I turn autofocus off it works as it should.
waiting waiting waiting waitng for 650D ML
I was about to see what I can do with the .422 files. I see that there is a command line tool https://bitbucket.org/hudson/magic-lantern/src/tip/422-jpg.py (https://bitbucket.org/hudson/magic-lantern/src/tip/422-jpg.py). As I only run Mac I was wondering if there is a Mac tool ( pref with GUI ) out there....
Can't you just get Python for Mac?
This will most likely run on a Mac. However It would safe me some command line headaches if a nice Mac implementation was available. I have search for it but came up empty handed.
Quote from: blade on May 03, 2013, 09:31:11 AM
This will most likely run on a Mac. However It would safe me some command line headaches if a nice Mac implementation was available. I have search for it but came up empty handed.
I think you can get by with that python script and Automator.
Quote from: laame on May 03, 2013, 10:53:52 AM
I think you can get by with that python script and Automator.
Good suggestion, i will see if i can get that to work.
I'm having a brain freeze. I can't remember how to bring up the alternate menu screen.
Canon menu button?
Hows HDR video working?
I dont know if it's a bug or harware limitation, but if you have zebras on for both under and ower exposed areas, they don't show up at the same time, but alternate in unpleasant fassion.
Quote from: laame on May 03, 2013, 05:51:54 PM
I dont know if it's a bug or harware limitation, but if you have zebras on for both under and ower exposed areas, they don't show up at the same time, but alternate in unpleasant fassion.
Limitation
Been testing ML and so far the only problem I have had which isn't really a problem is when you bring up the ML menu with the Canon stock overlay on the screen the exposure bar flickers on and off over the selection description at the bottom of the screen. in the ML menu. No problem if you enter ML menu with no overlay or ML overlay on screen.
Quote from: Aborgh on May 03, 2013, 05:49:54 PM
Hows HDR video working?
http://wiki.magiclantern.fm/userguide#hdr_video
or
http://lmgtfy.com/?q=magic+lantern+hdr+video+tutorial
Got bored today so I looked at lvrec / raw video and identified almost all the needed stubs. I'll probably include it in the next build just to see how this camera does. Keep in mind the sd controller is cheap and only does 40 MB second max
It depends on how much shoot malloc you have. 600D does more frames than EOSM. They're almost the same size or bigger and SD speed is slower.
Quote from: nanomad on May 04, 2013, 02:50:42 AM
Got bored today so I looked at lvrec / raw video and identified almost all the needed stubs. I'll probably include it in the next build just to see how this camera does. Keep in mind the sd controller is cheap and only does 40 MB second max
:o go go nanomad ;D
btw, when the card, battery and lens is inserted, the dial is switched off, then you scroll the scrollwheel the LED blinks. is that okay? 60D doesn't behave like this. just curious.
Quote from: Aborgh on May 03, 2013, 05:49:54 PM
Hows HDR video working?
I uploaded a video a while ago showing HDR video on the 650D. It's certainly not the best video showing HDR as it was hand-held and had moving subjects and it was my first go at it. [Not sure if it has a lot of dislikes for that reason [and if so, I say those reasons in the description anyway] or because people think it's fake?]
http://www.youtube.com/watch?v=s05gZqJ8gS0
Hi nanomad, I want to ask you something, we will have a public release in the next alpha or betas when they arrive?
Quote from: Lucas_W on May 04, 2013, 05:33:54 AM
I uploaded a video a while ago showing HDR video on the 650D. It's certainly not the best video showing HDR as it was hand-held and had moving subjects and it was my first go at it. [Not sure if it has a lot of dislikes for that reason [and if so, I say those reasons in the description anyway] or because people think it's fake?]
http://www.youtube.com/watch?v=s05gZqJ8gS0
Yeah I saw that video a while ago , how is HDR video working in the pre-alpha 2? Any better than pre-alpha 1?
The number 1 reason I want ML is HDR video and fps override, anyone tried it on the pre-alpha2?
Quote from: nanomad on May 04, 2013, 02:50:42 AM
Keep in mind the sd controller is cheap and only does 40 MB second max
I know my setup wil not go over 40 mb. However this is in line with the ad card specifications sit you see more tests that confirm it can't go faster even with faster cards?
Got a 95MB/s card, still 40. And the controller isn't using the 208Mhz bus
when do u add manual white balance to ML 650D (((to nanomad))) am waiting fot it
Quote from: nanomad on May 04, 2013, 12:33:10 PM
Got a 95MB/s card, still 40. And the controller isn't using the 208Mhz bus
That's to bad, but a clear limitation of the hardware.
First of all I want to thank you all developers for their great job.
I have tried to run ML but i have got problem. ML didn't start properly. There are only free space info and ISO limitation info on standard 650d info after startup. I also can't use ML menu. There is standard menu after pushing 'Menu'. Some ML information can be shown in LV mode after selecting by 'Info' button. Is this my mistake or something wrong with camera/ML?
Why are you running a pre-alpha if you don't even know how magiclantern works?
You enter ML menu using the trashcan button ... .... ...
Quote from: nanomad on May 04, 2013, 01:55:00 PM
Why are you running a pre-alpha if you don't even know how magiclantern works?
You enter ML menu using the trashcan button ... .... ...
Oh, thank you. It's so simple :). 650D is my first Canon DSLR, so I didn't have possibility to try Ml before. I also want to test ML and help in debugging.
Quote from: Aborgh on May 04, 2013, 12:18:14 PM
how is HDR video working in the pre-alpha 2? Any better than pre-alpha 1?
I haven't tried it out on Alpha 2, but I have no reason to believe that it's any different to when I attempted to try it out as I don't remember seeing any code change commits relating to HDR video.
Quote from: nanomad on May 04, 2013, 01:55:00 PM
Why are you running a pre-alpha if you don't even know how magiclantern works?
You enter ML menu using the trashcan button ... .... ...
nanomad when will u add manual white balance to ML 650D
no am running pre alpha on my cam, its awesome for video, i wating for manual white balance
http://wiki.magiclantern.fm/faq#troll_questions
"When it's done"
Quote from: MarlonSenanayake on May 04, 2013, 03:15:38 PM
no am running pre alpha on my cam, its awesome for video, i wating for manual white balance
And sound level indicator! )))))) Pleeeease! ))
(http://s019.radikal.ru/i628/1305/82/8e0e72d8c22f.jpg) (http://www.radikal.ru)
I tried the HDR video function and it works great
Quote from: donjames150 on May 04, 2013, 06:05:55 PM
I tried the HDR video function and it works great
http://www.youtube.com/watch?v=rcfNESH1yLY
i think its not working properly. when iso switches form one to another it change the white balance and gradually changing color.
so wait if the camera can do a tops of 40mbs then does that mean there isnt a point to spending a small fortune on a 95mbs memory card like SanDisk Extreme Pro and better of getting just the SanDisk Extreme at 45mbs second and using that extra cash to get a larger capacity card instead?
Gradual Expo - On - Ramping Speed 1EV/16 Frame
HDR Video - ISO 200/800v 2EVO
Recorded Video also Flicker
Quote from: kazeone on May 04, 2013, 06:52:16 PM
so wait if the camera can do a tops of 40mbs then does that mean there isnt a point to spending a small fortune on a 95mbs memory card like SanDisk Extreme Pro and better of getting just the SanDisk Extreme at 45mbs second and using that extra cash to get a larger capacity card instead?
Yes, unless a canon update brings the 208Mhz mode (unlikely, I hope the 700D has it but then, who knows)
Quote from: MarlonSenanayake on May 04, 2013, 07:07:18 PM
Gradual Expo - On - Ramping Speed 1EV/16 Frame
HDR Video - ISO 200/800v 2EVO
Recorded Video also Flicker
RTFM - http://wiki.magiclantern.fm/userguide#hdr_video
It's suppose to flicker, that's how the HDR Video feature works.
I'm running PreAlpha2 here on my T4i. It's working, and I'm happy! Thank you, Nanomad!
Here is the benchmarks of my cards:
(https://lh3.googleusercontent.com/-bI7bdKGxg7o/UYXPW507WsI/AAAAAAAAIB0/Rlmho8T2-ig/w1287-h480/64GB.jpg)
(https://lh6.googleusercontent.com/-EP39krB6S5c/UYXPXTyQJwI/AAAAAAAAIB4/_3NQYZgDf3Q/w1287-h480/32GB.jpg)
For those still struggling to enable boot flag. Here is how I got it working:
Downloaded the fir file (650D-safe-dumper)
Downloaded the 650D Alpha 2 file
Downloaded the program to make the SD card bootable. (EOScard)
Format SD card (Low Level in Camera)
Copy fir file onto SD Card
Update firmware in camera
Remove SD card
Copy ML Alpha2 650D onto SD Card
Put SD Card back in
Install ML Alpha 2 650D (Update firmware in camera)
Remove SD Card
Make the SD bootable (using the program EOScard, Tick first two boxes, Press Save, Refresh)
Put SD Card back in
Done.
Where can I find PreAlpha2? I'm interested in testing this.
Quote from: wild05kid05 on May 05, 2013, 07:11:58 AM
For those still struggling to enable boot flag. Here is how I got it working:
Downloaded the fir file (650D-safe-dumper)
Downloaded the 650D Alpha 2 file
Downloaded the program to make the SD card bootable. (EOScard)
Format SD card (Low Level in Camera)
Copy fir file onto SD Card
Update firmware in camera
Remove SD card
Copy ML Alpha2 650D onto SD Card
Put SD Card back in
Install ML Alpha 2 650D (Update firmware in camera)
Remove SD Card
Make the SD bootable (using the program EOScard, Tick first two boxes, Press Save, Refresh)
Put SD Card back in
Done.
Thanks for this :D
Quote from: Aborgh on May 05, 2013, 10:30:29 AM
Thanks for this :D
Aborgh - Do you have files to 650D? If you have got, could you send me?
Quote from: pemstudio on May 05, 2013, 10:39:05 AM
Aborgh - Do you have files to 650D? If you have got, could you send me?
I posted the links in a previous post and found all the links here in this thread.
"-Download the .fir file from https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified (Thanks to Lucas_W for pointing out the link, I would have uploaded the .fir myself but thought who would use firmware from some stranger)
Enable the bootflag on the SD card:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar ( software to make the card bootable: http://wiki.magiclantern.fm/3rd_party_software )
Install Magic Lantern
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- Copy over the files to the SD card ( Download ML Alpha 2 for the 650D here: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip and unzip to the root of your SD card. You should than have a ML folder and an autoexec.bin on the root of your SD card. "
Is it really that hard to search?
Quote from: loplo on May 05, 2013, 10:56:03 AM
Is it really that hard to search?
He contributed so maybe he felt he shouldn't have to read?
In this case, "mea culpa".
Quote from: newsense on May 05, 2013, 10:55:09 AM
I posted the links in a previous post and found all the links here in this thread.
"-Download the .fir file from https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified (Thanks to Lucas_W for pointing out the link, I would have uploaded the .fir myself but thought who would use firmware from some stranger)
Enable the bootflag on the SD card:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar ( software to make the card bootable: http://wiki.magiclantern.fm/3rd_party_software )
Install Magic Lantern
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- Copy over the files to the SD card ( Download ML Alpha 2 for the 650D here: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip and unzip to the root of your SD card. You should than have a ML folder and an autoexec.bin on the root of your SD card. "
Thanks for this .
Quote from: newsense on May 05, 2013, 10:55:09 AM
I posted the links in a previous post and found all the links here in this thread.
"-Download the .fir file from https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified (Thanks to Lucas_W for pointing out the link, I would have uploaded the .fir myself but thought who would use firmware from some stranger)
Enable the bootflag on the SD card:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar ( software to make the card bootable: http://wiki.magiclantern.fm/3rd_party_software )
Install Magic Lantern
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- Copy over the files to the SD card ( Download ML Alpha 2 for the 650D here: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip and unzip to the root of your SD card. You should than have a ML folder and an autoexec.bin on the root of your SD card. "
Thank yo very much for your help.
Quote from: newsense on May 05, 2013, 10:55:09 AM
I posted the links in a previous post and found all the links here in this thread.
"-Download the .fir file from https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified (Thanks to Lucas_W for pointing out the link, I would have uploaded the .fir myself but thought who would use firmware from some stranger)
Enable the bootflag on the SD card:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-Do a low-level format of the SD card (DO NOT SKIP THIS)
- Enable SD card bootflag using EOSCard or similar ( software to make the card bootable: http://wiki.magiclantern.fm/3rd_party_software )
Install Magic Lantern
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- Copy over the files to the SD card ( Download ML Alpha 2 for the 650D here: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip and unzip to the root of your SD card. You should than have a ML folder and an autoexec.bin on the root of your SD card. "
On mac, do you use macboot and choose "make dslr bootable" with log?
Quote from: Aborgh on May 05, 2013, 12:23:15 PM
On mac, do you use macboot and choose "make dslr bootable" with log?
I choose "canon scriptable" or what its called and it worked for me
Quote from: wild05kid05 on May 05, 2013, 07:11:58 AM
For those still struggling to enable boot flag. Here is how I got it working:
Downloaded the fir file (650D-safe-dumper)
Downloaded the 650D Alpha 2 file
Downloaded the program to make the SD card bootable. (EOScard)
Format SD card (Low Level in Camera)
Copy fir file onto SD Card
Update firmware in camera
Remove SD card
Copy ML Alpha2 650D onto SD Card
Put SD Card back in
Install ML Alpha 2 650D (Update firmware in camera)
Remove SD Card
Make the SD bootable (using the program EOScard, Tick first two boxes, Press Save, Refresh)
Put SD Card back in
Done.
Thanks for this!
I had to charge the battery, then start the installation....
Almost F'ed up my camera when trying to install... Will leave this for now...
Quote from: Aborgh on May 05, 2013, 03:13:31 PM
Almost F'ed up my camera when trying to install... Will leave this for now...
This was so easy to install with above instructions and links took me 5mins.
Also this ML stuff is amazing. Can not wait for final release with everything working 100%.
IF I find anything to report that hasn't already I will put up straight away.
After
5montha of me following this I have finally got ml so yea big day for me!
Quote from: JamieRollsMedia650D on May 05, 2013, 03:34:02 PM
This was so easy to install with above instructions and links took me 5mins.
Also this ML stuff is amazing. Can not wait for final release with everything working 100%.
IF I find anything to report that hasn't already I will put up straight away.
After
5montha of me following this I have finally got ml so yea big day for me!
Mine showed up with small boxes and said "ML did not find no fonts" or something like that and some white texts in the upper left corner kept on flashing... :S
Quote from: Aborgh on May 05, 2013, 03:13:31 PM
Almost F'ed up my camera when trying to install... Will leave this for now...
i have Installed this alfa on all my 3 650D cameras - all working good)
Quote from: kzi2006 on May 05, 2013, 03:51:50 PM
i have Installed this alfa on all my 3 650D cameras - all working good)
Could you please tell me your steps and how the camera behaved while you upgraded it?
As a developer, it would be best if you explained what you did and what went wrong
rather than have to figure out where all these files are at..........
Create a magic lantern folder on your hard drive
Download http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip (unzip all files to your ml folder)
On your camera select menu, first wrench icon, format card
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified, then copy the .fir file to your card and put it back in the camera.
With the cam in manual mode, go to last wrench setting before star, fimware ver, set, select ok, then my menu settings will read enablebootdisk :)
Put your card in the computer and download http://pel.hu/down/EOScard.exe and run this program
Check EOS Devlop and Bootdisk boxes, save
Check the card, if EOS card wrote any files, delete them
Copy from your ML folder these files: ML folder, autoexec.bin and 650D-safe-dumper.fir to your card
Put card in camera and press the trashcan button after it boots, then the left arrow button to the left of the set button
Quote from: nanomad on May 05, 2013, 03:55:53 PM
As a developer, it would be best if you explained what you did and what went wrong
I low formated the card , Downloaded the 650D-safe-dumper.fir put it on the SDHC card, tried to update and thats when the "ML something something" white text in the upper left corner appeared saying something about some font and then a smal QR code look-a-like box appeared in the middle of the screen. Thats when I panicked and shut the camera off, removed the battery and removed the files that were on the SDHC.
Or is it suppose to do this?
You need the FIR and ML files on the card too.
But:
- Remove any third party accessories / batteries first
- Don't use a battery grip
- Clear canon settings and Cfn
- Run fw upgrade from PHOTO M mode (not video, photo)
Quote from: nanomad on May 05, 2013, 04:21:05 PM
You need the FIR and ML files on the card too.
But:
- Remove any third party accessories / batteries first
- Don't use a battery grip
- Clear canon settings and Cfn
- Run fw upgrade from PHOTO M mode (not video, photo)
Then I am hella confused!
Since everybody discribes the installation like this:
1.Format card, download 650D-safer-dump.fir and put on camera
2.intall upgrade
3.put the card back in computer and make EOS Card
4.Put ML files on card
5. Boot camera
And you are telling me that I need ML files from step number 1?
I didn't make the FIR, but having can't hurt (and given the gibberish error message I would try)
Quote from: nanomad on May 05, 2013, 04:30:09 PM
I didn't make the FIR, but having can't hurt (and given the gibberish error message I would try)
Spontaneously I feel like I shouldn't be dealing with this since I got a weird error code...
But one thing that have happend is that when I go to update firmware menu thing and press it, it says "you can upgrade firmware when you want" or something like that when I DON'T have a .fir file on my camera. Before I tried installing ML it did not say anything when I tried to upgrade the firmware without a file
maybe "clear settings" (selection above firmware selection)
Quote from: Aborgh on May 05, 2013, 04:38:32 PM
Spontaneously I feel like I shouldn't be dealing with this since I got a weird error code...
But one thing that have happend is that when I go to update firmware menu thing and press it, it says "you can upgrade firmware when you want" or something like that when I DON'T have a .fir file on my camera. Before I tried installing ML it did not say anything when I tried to upgrade the firmware without a file
On 600D when there is no .fir on the card you can't see the upgrade firmware item in the menu.
Does it shows the same without card too? what about the boot flag? MAybe having it on will keep the menu item shown even without fir? I never noticed it if that's true...
Quote from: scrax on May 05, 2013, 04:45:08 PM
On 600D when there is no .fir on the card you can't see the upgrade firmware item in the menu.
Does it shows the same without card too? what about the boot flag? MAybe having it on will keep the menu item shown even without fir? I never noticed it if that's true...
Without card it says the same thing but when I press it says "Card with firmware is needed". So it seems normal :)
maybe you have a bad copy of the .fir file for some reason
download again and try
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified
Quote from: donjames150 on May 05, 2013, 04:49:58 PM
maybe you have a bad copy of the .fir file for some reason
download again and try
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified
Step by step now if I will try again:
1. Low format the SD card
2. Put the safe-dumper fir on SD card
3. Put the SD card in camera and then put it in M photo mode.
4. go to fourth wrench menu and update firmware.
5. Pull out the SD card and put in the computer again
6. Use macboot and choose "Canon-scriptable"
7. Put ML folder and AUTOEXEC.BIN on SD card
8. Put it in camera and it should be fine?
Does it matter that I've tried to make EOS card before running the .fir file?
Quote from: Aborgh on May 05, 2013, 05:00:22 PM
Step by step now if I will try again:
1. Low format the SD card
2. Put the safe-dumper fir on SD card
3. Put the SD card in camera and then put it in M photo mode.
4. go to fourth wrench menu and update firmware.
5. Pull out the SD card and put in the computer again
6. Use macboot and choose "Canon-scriptable"
7. Put ML folder and AUTOEXEC.BIN on SD card
8. Put it in camera and it should be fine?
Does it matter that I've tried to make EOS card before running the .fir file?
I didn't, the camera is just looking for the .fir file. BUT, I think we may need someone
who is a MAC person to jump in here who has successfully installed this because
I'm on a pc. Did you try with a new copy of the .fir file?
also you should try "clear settings" (selection above firmware selection) as Nanomad suggested
Quote from: donjames150 on May 05, 2013, 05:05:37 PM
I didn't, the camera is just looking for the .fir file. BUT, I think we may need someone
who is a MAC person to jump in here who has successfully installed this because
I'm on a pc. Did you try with a new copy of the .fir file?
also you should try "clear settings" (selection above firmware selection) as Nanomad suggested
I can try booting in PC in a minute and do the different steps. What exactly does the 650-safe-dumper.fir file do?
Post number 1234 woot wooot!
Quote from: Aborgh on May 05, 2013, 05:10:36 PM
I can try booting in PC in a minute and do the different steps. What exactly does the 650-safe-dumper.fir file do?
Post number 1234 woot wooot!
the .fir file makes it so the camera boots from the SD card
Quote from: donjames150 on May 05, 2013, 05:23:15 PM
the .fir file makes it so the camera boots from the SD card
How did the camera behave when you updated with that .fir?
Quote from: Aborgh on May 05, 2013, 05:26:55 PM
How did the camera behave when you updated with that .fir?
the screen went to "my menu settings" and displayed "enablebootdisk" with a smiley below it
Quote from: donjames150 on May 05, 2013, 05:36:49 PM
the screen went to "my menu settings" and displayed "enablebootdisk" with a smiley below it
Ah-ha I see , mine didn't :P
Maybe because I did EOScard in Windows and mac and then tried to update firmware?
Quote from: nanomad on May 05, 2013, 04:21:05 PM
You need the FIR and ML files on the card too.
But:
- Remove any third party accessories / batteries first
- Don't use a battery grip
- Clear canon settings and Cfn
- Run fw upgrade from PHOTO M mode (not video, photo)
So you need to extract files from Pre-alpha2 onto the formatted SD Card and put the safe-dumper.fir, then upgrade the firmware?
(Worked for me)EDIT: Magic Lantern up and running, thanks! :D
Quote from: alesis_neo on May 05, 2013, 05:48:19 PM
So you need to extract files from Pre-alpha2 onto the formatted SD Card and put the safe-dumper.fir, then upgrade the firmware?
then make the card bootable by running EOScard
the .fir file makes the camera able to boot from the card and the EOScard program makes the card a boot drive basically
then the autoexec.bin file runs ML
I figured FPSOveride is not really functional right now right guys ?
If you can not do this you should not own a computer so easy man lol
Quote from: wild05kid05 on May 05, 2013, 06:34:00 PM
I figured FPSOveride is not really functional right now right guys ?
yes i think it has something wrong
Aborgh, are up and running yet with ML?
Did you try running EOScard from a pc?
If not there's a MAC version
http://www.zenoshrdlu.com/macboot/macboot.html
Quote from: donjames150 on May 05, 2013, 07:32:54 PM
Aborgh, are up and running yet with ML?
Did you try running EOScard from a pc?
If not there's a MAC version
http://www.zenoshrdlu.com/macboot/macboot.html
Up and running :D Thanks guys! The help is awesome! Just looooooove the HDR function.
FPS over-ride does appear to be working
Quote from: donjames150 on May 05, 2013, 08:03:04 PM
FPS over-ride does appear to be working
It works but it crashes often :/
Nomad, if crash logs are useful then I can submit to you. Just let me know if I can do anything to help :).
What settings did you use to make it work?
Quote from: Aborgh on May 06, 2013, 12:19:19 AM
What settings did you use to make it work?
i just set mine at 60fps to see if it worked at all. Haven't tried any of the non-standard framerates
In EOS-M it needed to update from EVF state and the timers need to be set up so you don't get collapsed image. Shouldn't be crashing... just image freezing. If that happens hit play and it will reset.
be careful with FPS overide!!!!
for some reason this option is turned on the first time you install the prealpha in your camera.
i was checking options like 1 minute and the screen began to show banding.
red lines across!!!
i´ve seen this in another camera and this symptom isn´t good. it can damage your camera.
so be careful and wait for a stable release and please turn it off as soon as you install this prealpha.
anyways.
magic zoom isn´t working good.
even when is the only feauture activated and without sound recording.
Is it possible to have a feature where you set a timer for recording ? I was thinking if that's possible, I "maybe" be able to do hyperlapse with just FPS override. I would like to hear opinions :)
Quote from: wild05kid05 on May 06, 2013, 03:55:02 AM
Is it possible to have a feature where you set a timer for recording ? I was thinking if that's possible, I "maybe" be able to do hyperlapse with just FPS override. I would like to hear opinions :)
go to movie tweaks. in time indicator select elapsed
Quote from: MarlonSenanayake on May 06, 2013, 04:17:37 AM
go to movie tweaks. in time indicator select elapsed
A timer, not a time indicator. I want to make precise segments of 1s/2s/3s/etc.
Quote from: wild05kid05 on May 06, 2013, 05:08:09 AM
A timer, not a time indicator. I want to make precise segments of 1s/2s/3s/etc.
are you saying to want to be able to make time lapse movies and skip the process of taking a shit ton of photos and merging them and turning those photos into a video and just have the camera film it with pauses instead?
Please tell me How to set for iso 160 ,320...? I can't see in ML menu . Sorry for my english .
Quote from: kazeone on May 06, 2013, 05:31:51 AM
are you saying to want to be able to make time lapse movies and skip the process of taking a shit ton of photos and merging them and turning those photos into a video and just have the camera film it with pauses instead?
I can do that with FPSOveride, what I am saying is to make a
hyperlapse using FPSOveride. I want precise segments of "timelapse using FPSOveride". So like two-secs segment every 3 inches. Of course I can count via the time indicator, but it's not precise. I hope that make sense.
Seems like development has finally ramped up again! I'd been checking only once every few days.
Finally gave the prealpha a shot yesterday. So many random things going on, wish I had my skills from my old programming days.
The one thing I noticed was that the WB meter was always on top of ML menus covering everything up on the bottom of the screen.
I ran some of the tests but didn't know how to export the logs. I uninstalled it, but if someone can tell me how to dump the logs, what tests to run, and if they'd actually be contributing, I'd be happy to do it again.
It seems as if there's enough data now though?
Keep it up.
Quote from: Vietky69 on May 06, 2013, 06:13:00 AM
Please tell me How to set for iso 160 ,320...? I can't see in ML menu . Sorry for my english .
Goto image finetuning - ml digital iso than choose -0.3 EV
guys stop talking about useless thing, report bugs to nanomad, he can figure out bugs then
Quote from: wild05kid05 on May 06, 2013, 05:08:09 AM
A timer, not a time indicator. I want to make precise segments of 1s/2s/3s/etc.
It's already available but alex disabled it since it can be done with scripts instead (which are not available on the 650D yet).
Btw, known bugs
- [CONFIRMED] MZ not working properly. Got a fix, but it causes lockups.
- [???] FPS Override not working properly. I need a confirmation by more than one guy
Quote from: nanomad on May 06, 2013, 10:00:30 AM
- [???] FPS Override not working properly. I need a confirmation by more than one guy
I have filmed some HDR last weekend, and plan on testing and post processing the HDR tomorrow evening. I will test the FPS also. I also plan on finishing the rest of the testing.
I also have to revisit the motion detect, as steady hands is not working for me....
Al in all... very few bugs, nice work!
Quote from: nanomad on May 06, 2013, 10:00:30 AM
- [???] FPS Override not working properly. I need a confirmation by more than one guy
I tried with 2.5 fps (from 24), in 1920x1080 pixels. Something like two minutes (in real time) has been recorded. It worked! (It's awesome!)
Then i tried with 0.15 fps (from 24 too), 1920x1080 pixels too. Something like 10 seconds has been recorded. Apparently worked, but when I stopped recording my 650D locked up.
It causes 'Err 70' and saved this log (CRASH00.LOG) in my card:
ASSERT: 0
at Graphics.c:3580, task CtrlSrv
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Apr30.650D101
Mercurial changeset : ca7870e6a59c (unified)
Built on 2013-04-30 13:27:39 by nanomad@workhorse.
Free Memory : 316K + 3603K
P.S.: I tried to make some HDR Videos too, and it's working fine (I tried in 1080p24 mode). I used the HDR Workflow (HDR-workflow-051.zip), and everything is ok!!!
Quote from: nanomad on May 06, 2013, 10:00:30 AM
It's already available but alex disabled it since it can be done with scripts instead (which are not available on the 650D yet).
Btw, known bugs
- [CONFIRMED] MZ not working properly. Got a fix, but it causes lockups.
- [???] FPS Override not working properly. I need a confirmation by more than one guy
i selected 1080p 24 fps_ then turned on FOS ovrride and made fps to 25 then pink lines appear and camera wont respond,
I think I found a [very] little bug. In play mode (viewing images from card) if I press SET button (to preview exposure fusion, i.e.) the touch screen stops working. If I simply go to photo mode, an return to play mode, touch screen returns, no need to reboot.
P.S.: That didn't bother me, even a little.
Did you see any vertical lines in the final movie. A 2.5 fps test i did with the previous alpha showed green vertical lines.
http://youtu.be/-4-fsAupiSI (http://youtu.be/-4-fsAupiSI)
Can you upload your tests?
Did a quick look at FPS override, there's my experience:
Had my camera set to 1080p25 w/ audio disabled.
Set FPS override to 12.50fps - all worked fine, video was fine
Set FPS to 1.00fps - it was hard as nails to get the exposure right and resulting wideo had 1st couple seconds way underexposed and the rest of the clip was fine.
Didn't get any banding or something like that.
At one point desired fps setting started to change its values by itself until I quit ML menu.
After that somehow it allowed me to set fps to 50fps and other weird rates. I did not dare to try them, as they were a resault of some bug.
Also, during my messing around with fps override my camera froze once, so I had to turn it off/on, there were no crashlogs in card.
I'll try to do a couple more tests later tonight, after I get back from work, unless meanwhile someone find some terrible bug that can mess up camera.
Just attempted FPS override
At 40 FPS or higher i keep getting a scrambled live view ( repeated it 5X....:-) ), and a camera that hangs ( had to remove the battery)
ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:0
Magic Lantern version : v2.3.NEXT.2013Apr30.650D101
Mercurial changeset : ca7870e6a59c (unified)
Built on 2013-04-30 13:27:39 by nanomad@workhorse.
Free Memory : 316K + 3648K
Quote from: kzi2006 on May 06, 2013, 07:21:33 AM
Goto image finetuning - ml digital iso than choose -0.3 EV
Thanks for reply .
Hello
I am new to ML and been lurking here for a while.
I've been trying FPS override and noticed that no matter what settings and options I choose few frames at the beginning come out ok, but all remaining frames are overexposed.
Here's an example: http://youtu.be/YWCT1bOTX7M
Not sure if it's my mistake or some king of bug.
Anyway, big thanks for your work!
Quote from: red5446 on May 06, 2013, 03:45:02 AM
be careful with FPS overide!!!!
for some reason this option is turned on the first time you install the prealpha in your camera.
i was checking options like 1 minute and the screen began to show banding.
red lines across!!!
i´ve seen this in another camera and this symptom isn´t good. it can damage your camera.
so be careful and wait for a stable release and please turn it off as soon as you install this prealpha.
anyways.
magic zoom isn´t working good.
even when is the only feauture activated and without sound recording.
SAME HERE BRO
Anything happening yet guys? I'm a bit anxious to use the 'test' version as the T4i ain't exactly the cheapest camera out there. But are we looking at a release date soon?
Another one.
Yes it will be released..... sooner or later.
i don't think that alpha release gonna come soon for 650D, it'll take sometime i think, not good news for my video productioons
Quote from: mattgirvan on May 06, 2013, 07:36:31 PM
Anything happening yet guys? I'm a bit anxious to use the 'test' version as the T4i ain't exactly the cheapest camera out there. But are we looking at a release date soon?
http://wiki.magiclantern.fm/faq#when_will_you_release_the_next_version
guys please report ur problems, i only got magic zoom and FPS over ride problem for now, and also there is problem with HDR video, ISO levels jump constantly it dont work properly
I don't see what the problem with HDR video is? It's meant to change ISO levels in the display to let you preview the two light levels you'll work with.
If you mean on playback it changes ISO, that's how it's supposed to be. Look at the documentation I linked you to before (http://wiki.magiclantern.fm/userguide#hdr_video).
If it's something beyond those two, then I guess you have found a unique bug, but you'll probably need to describe it better.
I tested the HDR video feature and even though I didn't look into it much I was able to use it. I had no problems recording or processing.
FPS crashes sometimes after i stop recording
ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Apr30.650D101
Mercurial changeset : ca7870e6a59c (unified)
Built on 2013-04-30 13:27:39 by nanomad@workhorse.
Free Memory : 316K + 3634K
this crash was after recording a few minutes with
0.15 (from24)
optimized for exact FPS
Quote from: nanomad on May 06, 2013, 10:00:30 AM
It's already available but alex disabled it since it can be done with scripts instead (which are not available on the 650D yet).
Btw, known bugs
- [CONFIRMED] MZ not working properly. Got a fix, but it causes lockups.
- [???] FPS Override not working properly. I need a confirmation by more than one guy
When I tried FPS override, it would say 23.94 fps, then just drop to 2.5, and I couldn't select anything else. Every time I turned it off and then back on, it would say 23.94 for a split second, then just drop to 2.5.
Should it be 23.976?
Quote from: 33black on May 06, 2013, 09:25:48 PM
When I tried FPS override, it would say 23.94 fps, then just drop to 2.5, and I couldn't select anything else. Every time I turned it off and then back on, it would say 23.94 for a split second, then just drop to 2.5.
Should it be 23.976?
You need to configure it before turning it on
Press the q button
Quote from: newsense on May 06, 2013, 08:28:31 PM
I tested the HDR video feature and even though I didn't look into it much I was able to use it. I had no problems recording or processing.
HDR video works flawlessly been shooting with it quite a lot and it is perfect!
Everything seems to work for me except FPS override and MZ but everyone already knows that!
Quote from: nanomad on May 06, 2013, 09:37:34 PM
You need to configure it before turning it on
Press the q button
Got it. Just reinstalled.
Ok, set it up to 24 and said "actual fps: 23.976" then it kept randomly displaying "FPS override: 24fps" on the screen, but yeah, live view doesn't work at ALL, so I wasn't able to really do anything.
I tried to record with it, and literally got like a 3 colored garbled screen, had sound though.
Quote from: nanomad on May 06, 2013, 10:00:30 AM
It's already available but alex disabled it since it can be done with scripts instead (which are not available on the 650D yet).
What's the official name for this function Nomad ? I was digging the script api with no luck.
Cheers
Quote from: 33black on May 06, 2013, 11:11:55 PM
Ok, set it up to 24 and said "actual fps: 23.976" then it kept randomly displaying "FPS override: 24fps" on the screen, but yeah, live view doesn't work at ALL, so I wasn't able to really do anything.
I tried to record with it, and literally got like a 3 colored garbled screen, had sound though.
Disable it
Also: what video res and FPS were you using?
Quote from: nanomad on May 06, 2013, 11:37:00 PM
Disable it
Also: what video res and FPS were you using?
1080/24
I am new to this forum, and just successfully installed the alpha 2 on my 650d. Ever thing seems to be working great, though I have not tried to FPS override that everyone is talking about. I LOVE the focus peaking, and it seems to work very well. I tested the HDR right away, and posted the results here: https://vimeo.com/65588885
The way the HDR feature works, I would expect ghosting. But in the second test, there is jittering in the center of the frame, on the face of the tunnel that seems strange. It is probably not a bug, just how HDR works on this camera.
I really LOVE ML, thank you to everyone helping out in the development of ML for the 650d.
PS. I can't wait for some audio features to be released.
Nanomad or other developers including the 5DmarkIII team -- do you think it would be possible to port the Multiple Exposure feature that the 5D Mark III has? I do believe they run the same Proc. Just wondering if it could be done and perhaps replace something on the dial setting for this on the 650 D. Please share you thoughts regarding this. thank you.
Quote from: nanomad on May 06, 2013, 11:37:00 PM
Disable it
Also: what video res and FPS were you using?
(https://dl.dropboxusercontent.com/u/10903383/photo%201.JPG)
(https://dl.dropboxusercontent.com/u/10903383/photo%202.JPG)
Quote from: newsense on May 06, 2013, 08:28:31 PM
I tested the HDR video feature and even though I didn't look into it much I was able to use it. I had no problems recording or processing.
http://www.mediafire.com/?ylluwgbynka63kf this is wat happen wehn HRD function turned on (download and watch it)
As I've said before and the guide says, that's normal. That's how the HDR Video feature works, it changes the ISO every other frame. As the guide said, you have to use software on a computer to get the final video.
lol this is useless option, and waste of time, its easier to use ND filter
Quote from: MarlonSenanayake on May 07, 2013, 08:24:18 AM
lol this is useless option, and waste of time, its easier to use ND filter
+100! FPS Override, HDR options... FOR WHAT purposes? Only for experiments and for enthuziasts.
Kelvin WB, zebra, cropmarks, some sound features, right ISO and maybe some features for timelapses - that turns DSLR brick to real video camera and all i need for real shooting.
IMHO)))
Quote from: kzi2006 on May 07, 2013, 08:34:24 AM
+100! FPS Override, HDR options... FOR WHAT purposes? Only for experiments and for enthuziasts.
Kelvin WB, zebra, cropmarks, some sound features and maybe some features for timelapses - that turns DSLR brick to real video camera and all i need for real shooting.
IMHO)))
Awesome will you develop this for us on your free time and give it away for free?
If not then be quiet as you got no idea whats easy to implent and whats hard!
Stop expecting something from a team that do this for FREE and on their FREE TIME and ask NOTHING in return!
They said exposure and such needed props which is usually available in the beta!
HDR Video is meant for HDR, something that an ND filter won't do.
If you find it useless, you're probably (and are) doing it wrong, else the developers wouldn't have put the time into making it.
The FPS override I think is meant for easy-timelapses, since you don't have to compile the pictures after taking it and you don't have to activate your shutter a 1000 times.
Quote from: Ivarss on May 07, 2013, 08:41:09 AM
Awesome will you develop this for us on your free time and give it away for free?
I can donate or bought ml because i earn money with shooting and this software help me in my work last 1.5 year )))
I think at this point people should only respond to anyone that's posting vital testing information, or any of the admins working on the release that are asking vital questions.
There's 52 pages in this thread now, and only about 4 of them are relevant information. The rest are people asking when it's going to be done, complaining about it, and then people pointing out to them that they're stupid and it's free software, etc. etc.
Can we delete and start over?
Here's a crash log: https://dl.dropboxusercontent.com/u/10903383/CRASH00.LOG
I turned on FPS override, switched to movie mode, obviously live view not working, turned off FPS in movie mode, and it crashed. There's the log.
Also, here's my stubs api test: https://dl.dropboxusercontent.com/u/10903383/STUBTEST.LOG
and a general use log: https://dl.dropboxusercontent.com/u/10903383/LOG000.LOG
This is what happens when I try silent pictures:
https://www.dropbox.com/s/kn2tf3gv0kujug3/2013-05-07%2010.53.08.jpg
I get a lot of corrupt files on the SD card too
Quote from: Aborgh on May 07, 2013, 11:02:22 AM
This is what happens when I try silent pictures:
https://www.dropbox.com/s/kn2tf3gv0kujug3/2013-05-07%2010.53.08.jpg
I get a lot of corrupt files on the SD card too
lol i thought it was my memory card. i tried it too but didn't notice until you say now :D :D
Here's one money-making (for Luke) application of the HDR video function. I've been studying real estate video filming for 1-1/2 years and one of the biggest problems is indoor lighting. The windows tend to get blown out unless you use a lot of lighting or film on cloudy days or at night. If you film on a sunny (or even bright overcast day), you can never see out the windows from inside, they're just squares of bright light. Even the best real estate videographers (Fred Light, Dan Achatz) wind up with some blown out windows unless they spend a LOT of time (and money) with lighting. This is really the beauty of Magic Lantern and HDR video. Check out what Luke Neumann says about it:
HDR video is a great feature I've been using that outputs video you certainly can't with a ND filter, I love it!
Thanks to all the developers for all the great work! :D
donjames150 I was just about to share that same video, man I wish people would take the time to actually read and study before reporting something as a glitch when its working flawlessly lol, how can you test ML if you have no idea what ML does correctly in the first place. This is why they didnt want everyone to try out the prealpha2, people new to ML should wait until Beta to start really using it. I have never used ML but I have watched at least 4hrs of how to videos, and read countless pages of its features and yeah HDR Video is high on my list of awesome ^_^
To anyone who is willing to help this newcomer,
I carefully followed the instructions generously given by the following two members:
- wild05kid05 (May 05, 2013, 07:11:58 AM) - forum PAGE 49
- donjames150 (May 05, 2013, 04:09:55 PM) - forum PAGE 49
... and after running EOScard, getting the 'success' message, and re-inserting my SD card, my camera does not boot. Nothing. Black screen. No light telling my the card is being accessed. Just nothing. This has me pretty nervous, of course. I'm running Windows 7, if this matters.
Can anyone PLEASE help?
Quote from: Ed B on May 07, 2013, 08:14:56 PM
To anyone who is willing to help this newcomer,
I carefully followed the instructions generously given by the following two members:
- wild05kid05 (May 05, 2013, 07:11:58 AM) - forum PAGE 49
- donjames150 (May 05, 2013, 04:09:55 PM) - forum PAGE 49
... and after running EOScard, getting the 'success' message, and re-inserting my SD card, my camera does not boot. Nothing. Black screen. No light telling my the card is being accessed. Just nothing. This has me pretty nervous, of course. I'm running Windows 7, if this matters.
Can anyone PLEASE help?
You do have the battery in and charged right?
Does it boot without the SD card?
Quote from: Ed B on May 07, 2013, 08:14:56 PM
To anyone who is willing to help this newcomer,
I carefully followed the instructions generously given by the following two members:
- wild05kid05 (May 05, 2013, 07:11:58 AM) - forum PAGE 49
- donjames150 (May 05, 2013, 04:09:55 PM) - forum PAGE 49
... and after running EOScard, getting the 'success' message, and re-inserting my SD card, my camera does not boot. Nothing. Black screen. No light telling my the card is being accessed. Just nothing. This has me pretty nervous, of course. I'm running Windows 7, if this matters.
Can anyone PLEASE help?
Ed B, I'm pretty sure these instructions are complete so try them again
Create a magic lantern folder on your hard drive
Download http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip (unzip all files to your ml folder on your hard drive)
On your camera select menu, first wrench icon, format card
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified, then copy the .fir file to your card and put it back in the camera.
With the cam in manual mode, go to last wrench setting before star, fimware ver, set, select ok, then my menu settings will read enablebootdisk :)
Put your card in the computer and download http://pel.hu/down/EOScard.exe and run this program
Check EOS Devlop and Bootdisk boxes, save
Check the card, if EOS card wrote any files, delete them
Copy from your ML folder these files: ML folder, autoexec.bin and 650D-safe-dumper.fir to your card
Put card in camera and press the trashcan button after it boots, then the left arrow button to the left of the set button
newsense - battery in and charged
Lukas_W - Yes, it does. *sigh of relief!!* * embarrassment for not trying that earlier!*
donjames150 - Trying it again right now...
THANK YOU GUYS!
Will update soon --
Will HDR photo be available in the beta? Really wanna check that out.
GOT IT!!!
A million thanks to all
donjames150 - you were right. just had to repeat steps. think maybe i missed the 'delete EOScard-created files from card' part...
Quote from: Ed B on May 07, 2013, 09:11:12 PM
GOT IT!!!
A million thanks to all
donjames150 - you were right. just had to repeat steps. think maybe i missed the 'delete EOScard-created files from card' part...
Great! Took me a couple of times as well :)
Continue from post #1158
Movie menu:
Bit rate:
Mode CBR: OK
Tested factor 0.4 ( blocks visible in video ( as expected) and up to 2.0 recorded 30 seconds, looked good.
VBR: not tested
Bitrate info : OK got a nice a, b and Q info...
Record key: OK
Gradual expo: Not tesed
FPS override: See other post (#1268) Not working 100%
HRD:OK
Vignetting: OK
Image finetuning: Not tested I have no clue what to look for. However it did not crach te camera, so it may be OK
ML digital iso:OK
black level: OK
Movie tweaks:
Timer indicator: OK
Movie logging:OK
# Magic Lantern v2.3.NEXT.2013Apr30.650D101
Start : 2013/05/07 19:20:21
Lens name : EF100mm f/2.8 Macro USM
ISO : 0
Shutter : 1/0.000s
Aperture : f/2.8
Focal length : 100 mm
Focus distance : 5630 mm
White Balance : 0 - Auto, Magenta 0, Blue 0
FPS : 25.000
CSV data:
Time,ISO,Shutter,Aperture,Focal_Len,Focus_Dist
19:20:21,0,0,2.8,100,563
rec/start: OK
force live view: Not tested
Well thats it for me, I have tested the whole thing as far as i can. Again, very stable, and looking forward to a next version. I hope that some props will be enabled in the next version. If I have a vote i would love to test the advanced bracketing! Planning an urban trip and I would like to be able to take HDR with 5 or more photo's http://www.flickr.com/photos/roosloot/sets/72157632849808418/ (http://www.flickr.com/photos/roosloot/sets/72157632849808418/)
If I can assist in any more testing, or verification of other bugs, I will keep an eye on this tread.
Thats all folks!
Blade - does "rec/start: OK" refer to record/restart? (after 29:59 minutes)
Quote from: Jseeker on May 07, 2013, 09:43:09 PM
Blade - does "rec/start: OK" refer to record/restart? (after 29:59 minutes)
No. It starts/stops recording by pressing the shutter 1/2 for one second
This is my first venture into ML - I have a 650D mainly for video work and would love the on screen Audio Meters, be able to select Native ISO's for less noise and Higher Bit Rates ect..
I've loaded the Pre-Alpha2 which doesnt look like it can do all that yet... I'll probably take it off and wait for the finished product to come out.
I didn't see anyone else report this yet (sorry if they have) but while in Movie Mode the graphics were a bit glitchy, for one the light meter wouldnt go away while I was in the ML menu.
(https://lh4.googleusercontent.com/-Ud7gKAG_C0w/UYldqro8lsI/AAAAAAAAAK8/8HTQPxPlus0/w720-h480-no/VRAM1.BMP)
Quote from: RéaGeorge on May 07, 2013, 10:05:12 PM
I've loaded the Pre-Alpha2 which doesnt look like it can do all that yet... I'll probably take it off and wait for the finished product to come out.
I didn't see anyone else report this yet (sorry if they have) but while in Movie Mode the graphics were a bit glitchy, for one the light meter wouldnt go away while I was in the ML menu.
If a may ask, you have taken the time to install it, why not keep it on and do some testing and contribute? It may help the development and speed up the release if a stable version for you to use.
And yes I reported the glitchy graphics before, however I never got a nice shot of it posted. Thanx!
Btw, you do know that the audio meters can be found in the stock canon firmware right?
I dont mind doing some testing....
As I said I'm completely new so I wouldn't really know where to start as I've never used it before so dont fully know how it should work. I am however relatively tech savvy, so if you want to suggest what I could do that would be cool, and I'll see what I can do :)
You could take a look at my post, and go trough all the menu's and all the function and test them. Report what is working and what is not, confirm what works according to others and what not.
For more info look at this: http://www.magiclantern.fm/forum/index.php?topic=946.0 (http://www.magiclantern.fm/forum/index.php?topic=946.0)
So far the magic zoom is not working as it should and the FPS override is causing problems.
I skipped some stuff as I have no clue what i am testing, I am not a movie guy, so maybe you can test the untested stuff by me?
Cool
I'll have a read of that other thread, and see if I can find some time tomorrow to go through the settings. :)
That would be very helpful. Thanx
So my GlobalDraw isn't turning on...is that an issue in the prealpha or is that just me?
---
wait, I'm an idiot. it's a movie only feature.
with that said, with it on, none of the other options are working. no zebras, no focus peaking. it's not drawing anything on the screen.
are these features just not implemented? There's so many pages of arguing about nothing in this thread, I think I'm missing the important posts.
Quote from: 33black on May 07, 2013, 11:39:41 PM
So my GlobalDraw isn't turning on...is that an issue in the prealpha or is that just me?
---
wait, I'm an idiot. it's a movie only feature.
with that said, with it on, none of the other options are working. no zebras, no focus peaking. it's not drawing anything on the screen.
are these features just not implemented? There's so many pages of arguing about nothing in this thread, I think I'm missing the important posts.
It's just you. All of those features are working. Maybe you should re-download the ALpha2 and try again. You do know you have to hit the info buttons a few times to display the ML overlay right?
There it is, didn't hit the info buttons.
Sorry, I'm a newbie, and I tend not to read instructions because I like to pretend i'm a man's man.
So everything looks like it's working for me in general.
It's just that damn FPS override.
FPS sucks on all digic V.
Quote from: 1% on May 08, 2013, 01:52:40 AM
FPS sucks on all digic V.
Yeah. But why Canon..., Why..?, dammit!!!
I would like to ask: will HDR be available in photos?
Quote from: pemstudio on May 08, 2013, 01:52:13 PM
I would like to ask: will HDR be available in photos?
It is already there in the stock canon firmware. And you even have a selection on the dial for it...
They mean ML's HDR-Photo function (http://wiki.magiclantern.fm/userguide#hdr_bracketing).
and the answer is yes, I don't think there's any reason that it won't be eventually included on the 650D but just not at the moment.
Then the answer would be yes. It should work, however it depends on props. And for now no props are active. So maybe in the next alpha or so some props may be active.
Okay, 1 question, does anyone use a battery pack, and if so does the battery pack work after the install. After I unlocked the boot loader, and run the ML on my 650 I am no longer getting the battery pack to work. If anyone could verify if their battery pack works, and perhaps what brand you have that would be great. I have a generic brand. or if there is a switch inside ML that enables or disables the battery I would like to know thank you. I am so happy to have my camera with ML that I can care less at this time. but just thought I would ask that question perhaps I messed something up. But right now after applying this update I no longer am able to use my battery pack.
Quote from: buckbullstallion on May 08, 2013, 02:45:07 PM
If anyone could verify if their battery pack works, and perhaps what brand you have that would be great.
I have a cheap "Qumox" Battery grip
http://amazon.de/dp/B00B8PBBEU
Works perfect with ML
Original canon BG and AC adapter. They work fine with ML (I always have them on unless I need to enable the bootflag)
just to confirm, the 650D canon firmware to go with prealpha2 would be ver 1.0.1?
There are no other firmwares for the 650D, so yes
okie dokie.. thanks ;)
Hi nanomad
Thanks so much for your work. I'm new to ML and to digital photography (the 650D is my first digital - used my T90 before) and it is fantastic to get such an awesome tool from you guys.
Will have to play around with it and learn a lot. I'm totally excited.
thanks, thanks, thanks!!!!
to buckbullstallion:
Using a Phottix BG-550D batterygrip and it is working normal - all buttons work.
Best, Robert
Quote from: nanomad on May 08, 2013, 04:18:17 PM
Original canon BG and AC adapter. They work fine with ML (I always have them on unless I need to enable the bootflag)
I use a photive PH-GRP550D I know its a t2i system but was working fine, Maybe my AC battery block did something to the system. Sad face. it does work with the battery and the AC battery pack. I will fully charge the batteries and recheck will let you guys know. I just know that the pack above mentioned was working just prior to the Update and now doesn't. If it doesn't work. Again I accept full responsibility for my actions on my camera, but if someone has this battery pack adapter and could verify that theirs works that would be great.
I am so Thrilled that ML is working that that doesn't matter. ML FTW. Thank you nanomad and all devs for making this possible on the 650D
Quote from: Yeti183 on May 08, 2013, 08:26:35 PM
Hi nanomad
Thanks so much for your work. I'm new to ML and to digital photography (the 650D is my first digital - used my T90 before) and it is fantastic to get such an awesome tool from you guys.
Will have to play around with it and learn a lot. I'm totally excited.
thanks, thanks, thanks!!!!
to buckbullstallion:
Using a Phottix BG-550D batterygrip and it is working normal - all buttons work.
Best, Robert
JINX and that's the same one I am using. I will fully charge batteries and give it another go. thanks for responding and reading my MIND!!! LOL they may not be the same, but they are both 550D just probably rebranded.
Also, to the DEVS, is there a way to move the Memory text that is on top of my battery indicator into a more black spot on the screen, like a shift of 8 fonts to the Right?
Tested the BGRip with full batteries -- nothing changes. I will re-order one and see if its my BG grip that went bad. I will repost in 2 days regarding this. Also is there a way to re-lock the firmware to original to test if that works?
Quote from: buckbullstallion on May 09, 2013, 01:14:45 AM
Tested the BGRip with full batteries -- nothing changes. I will re-order one and see if its my BG grip that went bad. I will repost in 2 days regarding this. Also is there a way to re-lock the firmware to original to test if that works?
I've used Meike batt grips with sterling effect over the years (bashed around in India, Kuwait, etc). Never a problem, solid, well built and cheap (like $30 on the A). Works perfect with ML PA2. So yeah, send yours back for another copy (like we seem to have to do with lenses on a regular basis these days...)
To boot into the "original firmware" you can hold down the SET button as you switch the camera into the On mode, a message will appear on the screen saying "Magic OFF".
Quote from: TomJ on May 09, 2013, 04:50:24 AM
I've used Meike batt grips with sterling effect over the years (bashed around in India, Kuwait, etc). Never a problem, solid, well built and cheap (like $30 on the A). Works perfect with ML PA2. So yeah, send yours back for another copy (like we seem to have to do with lenses on a regular basis these days...)
Oh yeah, I just called Canon on it, but they wanted me to start up a case, I just hung up on Him. I will diagnose myself, and yes I agree boomerang it if it fails. Quicker and faster then any RMA.
Quote from: Lucas_W on May 09, 2013, 07:00:37 AM
To boot into the "original firmware" you can hold down the SET button as you switch the camera into the On mode, a message will appear on the screen saying "Magic OFF".
The battery pack no longer works with camera therefore cannot do that. It may be in the unlocking of the Boot loader. I am just hoping that it did not fry anything in the camera as I was removing the battery pack. I am hoping that the battery pack if anything failed which I will test on Friday and will post my findings. I just wanted to know if there was a way to Relock the boot loader into the original firmware. I am sure if a new firmware comes out I will be able to apply that and should relock the BL.
Okay so I go to debug menu>burn-in tests>stubs API test:
Test completes with 85 pass 1 fail. Is that normal?
Yes, the halfshutter test fails because it requires properties.
Thank you has all for alpha 2
I little finally to play with
Good luck for the final version
Quote from: a1ex on May 09, 2013, 10:55:28 AM
Yes, the halfshutter test fails because it requires properties.
Thank you, will continue testing. I didn't do it but it looks tempting will the menu option that says don't test this brick my Camera?
So I've started to go through all the settings checking things...
All the overlays basically seems to be working, with slightly glitchy graphics though, Magic Zoom is the worst, it shows up but is too glitchy to really use easily.
Zebras - OK
Focus Peak - OK
Magic Zoom - Works but with glitchy graphics
Cropmarks - OK
Ghost Image - OK
Spotmeter - OK
False Color - OK
Histogram - OK
Waveform - OK
Vectorscope - OK
Probably nothing new here....
I will continue to the next page (Movie) but do let me know if there's anything in particular I should look at.
Magic zoom is a know bug, nanomad has a fix, small side effect is that it freezes the camera :-)
Have you also tested the settings in the sub menu's? E.g. Zebras--> overexposure / underexposure etc.? Just wondering what you mean by ok.
And aldo it may be noting new, you confirm that it works! That's nice!
Yeah tried to test the different settings within each option as well...
I just got ML installed on my camera, most of the stuff works perfectly except for the OVERLAY menu which is not working at all for me, I have Global Draw enabled but still nothing is working. Could anybody help? Thank You.
While in LiveView, press the INFO button a couple of times. That should do it.
RAW silent pics are working :)
Quote from: Lucas_W on May 09, 2013, 04:27:05 PM
While in LiveView, press the INFO button a couple of times. That should do it.
Thank You very much, it worked perfectly.
hello
First thanks for magic lantern
second I run some test and this is my resolute:
*** stubs API test: 83 passed 3 fail
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1acd00
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1acca0
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x1acc80
[Pass] bar => '*****hjkl;'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0x79d2c
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0xbc73b
[Pass] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x16
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x2
Date/time: 2013/05/09 14:32:02
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x3
[Pass] mod(s1-s0, 60) => 0x1
[Pass] mod(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x4f088
[Pass] p = malloc(50*1024) => 0xf0740
[Pass] CACHEABLE(p) => 0xf0740
m1 = MALLOC_FREE_MEMORY => 0x42878
free(p)
m2 = MALLOC_FREE_MEMORY => 0x4f088
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x387240
[Pass] p = AllocateMemory(256*1024) => 0x801a34
[Pass] CACHEABLE(p) => 0x801a34
m1 = GetFreeMemForAllocateMemory() => 0x347234
FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x387240
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x4f088
m02 = GetFreeMemForAllocateMemory() => 0x387240
[Pass] p = alloc_dma_memory(256*1024) => 0x40801a74
[Pass] UNCACHEABLE(p) => 0x40801a74
[Pass] CACHEABLE(p) => 0x801a74
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40801a74
free_dma_memory(p)
[FAIL] p = (void*)shoot_malloc(24*1024*1024) => 0x0
[FAIL] UNCACHEABLE(p) => 0x40000000
shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x4f088
m12 = GetFreeMemForAllocateMemory() => 0x387240
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0x204a00ac
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id((unsigned int)get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x209600b0
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0x212e01e2
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0x21d20042
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x4
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x40801a74
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x4
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
SW1(1,100)
[FAIL] HALFSHUTTER_PRESSED => 0x0
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
*** Magic Zoom when Working the Cpu in 90-95% load
*** When I press rec The time indicator show me 11 min to record but t4i can record 29 min
Some crash in fps
----Crash00-----
ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Apr30.650D101
Mercurial changeset : ca7870e6a59c (unified)
Built on 2013-04-30 13:27:39 by nanomad@workhorse.
Free Memory : 316K + 3605K
----Crash00-----
ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Apr30.650D101
Mercurial changeset : ca7870e6a59c (unified)
Built on 2013-04-30 13:27:39 by nanomad@workhorse.
Free Memory : 316K + 3618K
Quote*** When I press rec The time indicator show me 11 min to record but t4i can record 29 min
The time indicator was designed for cameras with a 4GB limit. What about CONFIG_CAN_RECORD_MORE_THAN_4GB?
Also take a look at the 5D3 indicator code (bitrate-5d3.c, REC indicator).
QuoteASSERT: !IS_ERROR(semErr)
Probably we need to tweak some semaphore timeouts. What FPS value did you use?
I think I went to "old school" indicators for some reason after trying the 5d3 ones.... maybe just make the 4gb indicator not default? I picked elapsed.
I Rise up to max of fps
and if you are need more help two test I can help
All stubs test passed :D
I have a few mishabs i would like to report, some are already reported by others:
- Magic zoom (box) flickers specially when i make the zoom box larger
- When I am in the menu sometimes I can see a small spot from the live view through the magic lantern menu.
- I tried the motion detect function but it is really slow. It takes about 3 seconds before it takes e picture, also with manual focus/M dial mode, does this also have to do with global draw overlay (CPU overload or something)?
I'm a first time ML user, so a stupid question: Stuff like audio meters & bulb timer are not available yet because of props/Alpha version? I saw that on 600D audio options are not available because of the standard Canon manual audio control, will this also be the case with the 650D?
I am thinking if there would be a way to adjust the Opacity of the ML overlay screen so we can see Live View in background better. I notice that it doesn't take over the screen, that its actually on top of the screen -- hence why some will see flicker -- that's usually because camera is in a live view status and the Screen is overlaying it -- thus not overriding Live View, but if you could make the ML screen a bit more opaque we will be able to see the Live View a bit better. Just a thought and an Idea. and addressing the prior comment on why the flickering is happening.
Try pressing the LV button while in ML menu :P
Quote from: nanomad on May 09, 2013, 11:49:53 PM
Try pressing the LV button while in ML menu :P
AWESOME!!! Thanks. this is great stuff.
Hi, I have enabled the Zebras, FocusPeak, MagicZoom (via the +) and CPU-load (from debug menu).
After a very short time using Magic zoom, the RED card-LED comes on and stays on constant.
The CPU-load shows 98-99% most of the time, and I have to turn off camera to normalize.
I will try this out in more depth later today and see if I can find some connection between
the heavy CPU-load, lit LED and my usage of the ML. Anyone else experience this behaviour?
The 650D has a huge CPU load in LV regardless of ML, but everything seems to be working fine here
first, thank you, ml sits on my 650d :)
hdr bracketing is currently not in this version?
EOS M- 42% @ idle. MZ maybe uses 10-15%. I can't imagine what the load is with display filters. No card lights/shutdown for me though.
BTW, the RAW.C stuff like color matrix and DR was the exact same between M and 650D.
I just bought my first camera and hope to learn it and use ML.
Is it me or Power Saving is missing in this built ?
Quote from: PelleParafin on May 10, 2013, 10:02:44 AM
Hi, I have enabled the Zebras, FocusPeak, MagicZoom (via the +) and CPU-load (from debug menu).
After a very short time using Magic zoom, the RED card-LED comes on and stays on constant.
The CPU-load shows 98-99% most of the time, and I have to turn off camera to normalize.
I will try this out in more depth later today and see if I can find some connection between
the heavy CPU-load, lit LED and my usage of the ML. Anyone else experience this behaviour?
After some more testing I come to the following regarding my CPU-load:
* With just the LV overlay (No zebras, Magic zoom or Focus peak) it seems to stabilize on 72% cpu-load.
* As soon as I turn on zebras, it maxes out on 98-99% and stays there.
Regarding the lit card-LED:
* As soon as I cycle through the LV overlays (0 and 1) with the Info button the LED turns on, and stays lit.
* After I shut off LV the LED goes from constant ON to short blinks 5 seconds apart after 30 seconds.
Quote from: PelleParafin on May 10, 2013, 08:25:41 PM
After some more testing I come to the following regarding my CPU-load:
* With just the LV overlay (No zebras, Magic zoom or Focus peak) it seems to stabilize on 72% cpu-load.
* As soon as I turn on zebras, it maxes out on 98-99% and stays there.
Regarding the lit card-LED:
* As soon as I cycle through the LV overlays (0 and 1) with the Info button the LED turns on, and stays lit.
* After I shut off LV the LED goes from constant ON to short blinks 5 seconds apart after 30 seconds.
for me:
Everything off and no LV 3.2-3.4%
every thing off ( including global draw) and LV on and focus on manual: CPU + 69.6- 70.8%
If i turn auto focus on: it is up to 79.1-79.3
If i then turn LV off, it drops to 39% when focusing
LV on, and Global draw and zebras it goes up to 84.2-84.6%
Add focus peak and it increases to 99.2-99.4%
If I then turn autofocus off again, in drops slighly to 996.8-97.2%
I can confirm the led light:
Go te prefs, and turn on LV display presets to 2.
cycle with info button in lv, and led turns solid.
ihowever i cant get it to go off by shutting of lv, it stays solid.
I just got Magic Lantern for my Canon 650D now, and I must say, it works great!!! I have used the Intervalometer function in about two hours now, and it works great. 750 pictures taken so far :)
Quote from: buckbullstallion on May 09, 2013, 07:06:33 AM
Oh yeah, I just called Canon on it, but they wanted me to start up a case, I just hung up on Him. I will diagnose myself, and yes I agree boomerang it if it fails. Quicker and faster then any RMA.
The battery pack no longer works with camera therefore cannot do that. It may be in the unlocking of the Boot loader. I am just hoping that it did not fry anything in the camera as I was removing the battery pack. I am hoping that the battery pack if anything failed which I will test on Friday and will post my findings. I just wanted to know if there was a way to Relock the boot loader into the original firmware. I am sure if a new firmware comes out I will be able to apply that and should relock the BL.
Received new Grip, and it works. I purchased the Same make and model. So apparently I had the battery pack inside the grip while removing it, that's what I am thinking. So please note that the Grip is working and thanks goes out to everyone who addressed my concerns. I am now returning grip back to the Big A.
Nanomad or other Devs. is there a link you can post that shows me how to write the Scripts so I can make an HDR 7 exposure script and where and how to apply it to the camera many thanks for the great job.
Quote from: blade on May 10, 2013, 08:56:59 PM
for me:
Everything off and no LV 3.2-3.4%
every thing off ( including global draw) and LV on and focus on manual: CPU + 69.6- 70.8%
If i turn auto focus on: it is up to 79.1-79.3
If i then turn LV off, it drops to 39% when focusing
LV on, and Global draw and zebras it goes up to 84.2-84.6%
Add focus peak and it increases to 99.2-99.4%
If I then turn autofocus off again, in drops slighly to 996.8-97.2%
I can confirm the led light:
Go te prefs, and turn on LV display presets to 2.
cycle with info button in lv, and led turns solid.
ihowever i cant get it to go off by shutting of lv, it stays solid.
I did note that while shooting a 7 minute video with default ML settings that the Camera body became very hot, as I am sure this is related to the High CPU load, I am wondering if this is normal with all those features running? as I see from posts that its happening, my concern is Overheating the board.
Quote from: blade on May 10, 2013, 08:56:59 PM
LV on, and Global draw and zebras it goes up to 84.2-84.6%
When I use LumaFast in the zebras i get 75%
QuoteAdd focus peak and it increases to 99.2-99.4%
Focus peak bumps it up to 96%
Everything else is similar, except my LED turns from solid to flashing 30 seconds after i turn off LV and the canon info (completely black screen).
LV presets are ok with props on, so I guess that's why they are not working.
I've fixed a little bug that made the canon metering draw over the ML ui (it still does, but for a split second)
Quote from: nanomad on May 11, 2013, 12:37:32 AM
LV presets are ok with props on, so I guess that's why they are not working.
I've fixed a little bug that made the canon metering draw over the ML ui (it still does, but for a split second)
should I be installing nightlies?
Quote from: buckbullstallion on May 11, 2013, 02:20:20 AM
should I be installing nightlies?
No, they do not support your camera
But if you compile from a last source, it should work very well ;)
Very well indeed.
Quote from: satriani on May 11, 2013, 11:08:12 AM
But if you compile from a last source, it should work very well ;)
I want to compile but how?
Not necessary, feel free ;)
https://www.dropbox.com/sh/z1dvw3fpstggz68/wxr8gFzaaW
Quote from: satriani on May 11, 2013, 12:27:03 PM
Not necessary, feel free ;)
http://db.tt/C9icw03e
Wow! Thank you :) What a good guy ^^
Does it feature anything new except silent pictures?
Quote from: satriani on May 11, 2013, 12:27:03 PM
Not necessary, feel free ;)
http://db.tt/C9icw0
For the safety of my camara I will skip this. Thanks but no thanks !
Quote from: blade on May 11, 2013, 12:57:53 PM
For the safety of my camara I will skip this. Thanks but no thanks !
Honestly, I would not recommend this also. But who trusts me, is welcome :)
I have changed the link above.
Quote from: satriani on May 11, 2013, 01:46:25 PM
Honestly, I would not recommend this also. But who trusts me, is welcome :)
I have changed the link above.
Do you have it?
Which version is newest?
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1acd00
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1acca0
[FAIL] foo => ''
[Pass] memset(bar, '*', 5) => 0x1acc80
[FAIL] bar => '*****ghjkl'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0x89ec0
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0xd12cc
[FAIL] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x29
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x31
Date/time: 2013/05/11 10:01:49
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x32
[Pass] mod(s1-s0, 60) => 0x1
[Pass] mod(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x3ea50
[Pass] p = malloc(50*1024) => 0x100d90
[Pass] CACHEABLE(p) => 0x100d90
m1 = MALLOC_FREE_MEMORY => 0x32240
free(p)
m2 = MALLOC_FREE_MEMORY => 0x3ea50
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x379820
[Pass] p = AllocateMemory(256*1024) => 0x80317c
[Pass] CACHEABLE(p) => 0x80317c
m1 = GetFreeMemForAllocateMemory() => 0x339814
FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x379820
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x3ea50
m02 = GetFreeMemForAllocateMemory() => 0x379820
[Pass] p = alloc_dma_memory(256*1024) => 0x408031bc
[Pass] UNCACHEABLE(p) => 0x408031bc
[Pass] CACHEABLE(p) => 0x8031bc
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x408031bc
free_dma_memory(p)
[FAIL] p = (void*)shoot_malloc(24*1024*1024) => 0x0
[FAIL] UNCACHEABLE(p) => 0x40000000
shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x3ea50
m12 = GetFreeMemForAllocateMemory() => 0x379820
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0x3a3400ac
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id(get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x3a8200ae
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0x3b1a0108
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0x3bbc004e
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x4
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x408031bc
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x4
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
SW1(1,100)
[Pass] HALFSHUTTER_PRESSED => 0x1
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
Whitebalance work like charm
magic zoom work good med tl 3:1
HDR WORK find
only stub test 5 error
Quote from: Aborgh on May 11, 2013, 01:58:23 PM
Do you have it?
Which version is newest?
ML_N_11.05.zip
ML = Magic Lantern
N = nightly
11.05 = Date 11 May
If developers don't wish this, so let me know and I remove the link.
Quote from: satriani on May 11, 2013, 02:16:25 PM
ML_N_11.05.zip
ML = Magic Lantern
N = nightly
11.05 = Date 11 May
If developers don't wish this, so let me know and I remove the link.
Is this a compile of nightly for every camera or specifically for 650D?
specifically for 650D.
If you have a questions please pm me. Let's keep this thread clean.
I am not a developer, so i may be wrong.
The developers post an alpha, on order to get feedback on this particular build.
You and anybody is free to compile what they want, however, if people start reporting bugs, from your build its may be difficult to track whats going on.
Additional if you make a mistake and brick your own camera, thats your own problem, if you brick someone else its camera they will turn to the developers to fix it. And that may be very hard for them.
Therefor i would advise if you have the skills to compile it yourself, please do so, otherwise be patient....
Self compilation has props enabled, hence the manual white balance and whatnot. IIRC, having props enabled is /very/ dangerous.
Did some testing with the video modes on Pre Alpha 2. I filmed some footage at 1080 24p. The normal bitrate usually comes out at around 50mbps. I upped it to 1.3x and it came just over 60mbps. I tried 1.4x but for some reason it went back to 50mbps. Anyone else try this?
Does qscale -16 also show as q +- 16 on 650D?
Quote from: APXmusic on May 11, 2013, 03:36:33 PM
Did some testing with the video modes on Pre Alpha 2. I filmed some footage at 1080 24p. The normal bitrate usually comes out at around 50mbps. I upped it to 1.3x and it came just over 60mbps. I tried 1.4x but for some reason it went back to 50mbps. Anyone else try this?
I did try vbr qscale -16 and it's still 40-55. :/
EOS-M gets up to 70MB/s even with flush rate and "cbr" numbers cranked up all the way. Both of these should support ALL-I/IPB/IPP with some hacking.
You can get 10mbit/s with QScale -16 and it's perfectly normal. You can also get 80mbit/s with QScale +4 and that's also perfectly normal.
And "up to X" means X is an upper limit (that is, you can get any value equal to X or lower).
How/where can you see the actual bit rate that your recording at?
Is it displayed on screen or are you checking the footage afterwards?
Thanks
:)
I recorded some HDR video tests today and it varied from 68 to 72 mbps, very happy with the results :)
Used a SanDisk Extreme Pro 95mb/s SD card and CBR at 1.5x
Quote from: RéaGeorge on May 11, 2013, 05:14:33 PM
How/where can you see the actual bit rate that your recording at?
Is it displayed on screen or are you checking the footage afterwards?
Thanks
if you're on a pc, go to the start icon and right-click to open the explore file utility. Find the file and right-click on it. Then select properties, then details.
And on a Mac? :P
Quote from: RéaGeorge on May 12, 2013, 12:09:57 AM
And on a Mac? :P
sorry, I'm not a mac person. Anyone?
there prob is an equivalent. Can you find the file and right-click?
The only thing I know of thats equivalent to that is the "Get info" button for any file... but it doesn't show that detail...
If someone does know that would be awesome, otherwise I'll just check a few of my files in windows.
Could try mediainfo?
Tried VBR Qscale at -16 and it worked great. Got 67mbps data rate on the file. (audio included) seems like a bit of a boost. I tried it at +4 like someone mentioned but it looks like ass! It's nice to have a hack, even if the bitrate is a minor improvement. The focus peaking is what I really enjoy having. Thanks ML team! ;D
Quote from: satriani on May 11, 2013, 12:27:03 PM
Not necessary, feel free ;)
https://www.dropbox.com/sh/z1dvw3fpstggz68/wxr8gFzaaW
You r great ! Cheers! Waiting audio meter)
i find bug - Once taking custom WB - no way to choose auto WB
You can choose auto whitebalance from the normal canon menu. Also, you're suppose to report bugs from the Alpha 2, that's why it was released.
after ""2013Apr30.650D.PreAlpha2"" is there any prealpha update
No that is the current version, please test and report any bug found
(http://s8.postimg.org/odtu4xsd1/image.jpg)
Hi Nanomad, thanks for the ML ;)
most of the stuff works perfectly.
good luck for next update
my test results:
focus peaking working (made some mistakes, but working :) )
fps override noes not work - no fps change and after 2-3 seconds recording stopped.
can i begging for hdr bracketing? :)
The option HDR is serially in a camera but it gives a file which is connected, so version with ML will be very useful. I would like to ask about an absorbing with adding of this function. Does it need many work?
Guys, please be so kind and describe issues in detail. This can be very important for developers.
Thanks.
Quote from: ejszarny on May 12, 2013, 02:50:52 PM
fps override noes not work - no fps change and after 2-3 seconds recording stopped.
I have the same problem
I i woud like to reproduce your not working fps. What setting should I put my camera in , what exact setting should I use in fps ? Please give as much information as possible.
As fps is working for me in some settings, and some not, I wonder why it is not working at all for you.
Please let me know so we can fix this
Quote from: blade on May 12, 2013, 09:15:47 PM
I i woud like to reproduce your not working fps. What setting should I put my camera in , what exact setting should I use in fps ? Please give as much information as possible.
As fps is working for me in some settings, and some not, I wonder why it is not working at all for you.
Please let me know so we can fix this
I think they are forgetting to disable audio first...
Quote from: RéaGeorge on May 12, 2013, 01:06:21 AM
The only thing I know of thats equivalent to that is the "Get info" button for any file... but it doesn't show that detail...
If someone does know that would be awesome, otherwise I'll just check a few of my files in windows.
Open with QuickTime and press cmd+i
Hi everybody,
thanks for ML!!! Really good work!
I have foung a bug:
1) when I took a photo in M mode, view of the photo turned in B&W and after that "overlay saved" -> camera automatickly jump into livewiev
2) after taking photo (in live view mode - doesn´t matter if in fiml mode or photo mode) I have an overlay of last taken picture
Nothing helps (batery out, card cart and so on)
(http://K:%5CDCIM%5C100MEDIA%5CIMAG0097_BURST006)
Check your ML settings, sounds like you have Ghost image enabled.
Remember: if you see something weird, the first thing you should try is resetting canon and ML preferences (make a backup of ML settings first so you can figure out what was causing it)
nanomad,
the hdr bracketing is problematic with digic V ?
Hi!
I've been using the latest alpha for a while and I noticed two corrupt RAW files when taking time lapses. Here is one:
https://dl.dropboxusercontent.com/u/10119318/PublicPrivate/IMG_3322.CR2
I'm not sure if ML is the cause, the only know that this did not happen before I started using ML. I left live view before starting the time lapse shots and I don't have any special settings enabled (no Zebras, no Focus Peak, no Magic Zoom, no Cropmarks, no Ghost image, no Spotmeter, etc.) Let me know if you need more information or if this definitely does not have anything to do with ML.
EDIT: I just found another one: https://dl.dropboxusercontent.com/u/10119318/PublicPrivate/IMG_3121.CR2
Today I was out testing ML and really enjoy how fast I can set my exposure with the histogram and decided to try out HDR video again which worked great. I noticed that the histogram updates very slow when set to 60p. Is this normal or a possible bug? This was with HDR turned off BTW.
I'm very excited as I bought the T4i without thinking that ML hadn't been ported yet. I'll surely be donating once I can.
Also, noob question: where exactly can I download these Betas?
Quote from: papkee on May 14, 2013, 01:34:10 AM
I'm very excited as I bought the T4i without thinking that ML hadn't been ported yet. I'll surely be donating once I can.
Also, noob question: where exactly can I download these Betas?
I am going to present you with the answer to every noob question ever asked. READ. Read this whole post or at least the last 15 pages or so and you shall see the light. Congrats on getting a new T4i BTW and welcome to the forums.
Quote from: papkee on May 14, 2013, 01:34:10 AM
I'm very excited as I bought the T4i without thinking that ML hadn't been ported yet. I'll surely be donating once I can.
Also, noob question: where exactly can I download these Betas?
ahhhwwww he thinks its in Beta lol its not even into Alpha yet lol but yeah please read or at the very least do a search within the thread.
Quote from: Morghus on May 13, 2013, 09:34:25 PM
Hi!
I've been using the latest alpha for a while and I noticed two corrupt RAW files when taking time lapses. Here is one:
https://dl.dropboxusercontent.com/u/10119318/PublicPrivate/IMG_3322.CR2
Hi Morghus,
Just d/ld your pics and they look fine to me, although one looks to be compressed and one not 5MB & 20MB resp.
What exactly is the problem?
Isn't there an exposure and audio menu?
Not in the pre-alpha
I went through all this struggle and registered myself just to write this single post!
I can't seem to figure how to successfully install ML.
What i did:
1. Low level format
2. Put the FIR-file on the sdcard and then put the sdcard back in the camera
3. In Manual photo mode, go to the fourth wrench and do a firmware update.
Here's where the problem occurs, when it's done it says "Update file cannot be found. Please check the memory card and reload the battery and try again". :-\
I got firmware ver. 1.0.1
Hi everyone ! I'm french, and i'm trying to understand your posts... But my english is not good enough !
I just have one question please, i'm about to buy a DSLR for video mainly. Hesitating between Sony Alpha 77 or 650D with Magic Lantern...
Reading your words, it seems that a lot of features are working now. So have i just to install ML alpha to get all those features working well with probably some bugs, or do i need to install it, and then modify some files or other things ?
hopefully you will understand what i mean... :-\
Thx !
Quote from: Sandsnor on May 14, 2013, 05:11:36 PM
I went through all this struggle and registered myself just to write this single post!
I can't seem to figure how to successfully install ML.
What i did:
1. Low level format
2. Put the FIR-file on the sdcard and then put the sdcard back in the camera
3. In Manual photo mode, go to the fourth wrench and do a firmware update.
Here's where the problem occurs, when it's done it says "Update file cannot be found. Please check the memory card and reload the battery and try again". :-\
I got firmware ver. 1.0.1
maybe you have a bad copy of the .fir file for some reason
download again and try
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified
Has anyone else noticed the histogram updates slow in 60p or is it just me?
Quote from: donjames150 on May 14, 2013, 06:18:25 PM
maybe you have a bad copy of the .fir file for some reason
download again and try
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified
Thanks for the advice!
I actually got it to work, changed from a MicroSDXC (With adapter) to a regular SD-card and it seems to work seamless now (:
Is it a known problem that you can't use microSD-cards for ML?
http://www.eoshd.com/content/10324/big-news-hands-on-with-continuous-raw-recording-on-canon-5d-mark-iii
Another game changer by the Devs! Great Job!!!!! ;D And now for the newb question. Is this possible for 650d to any extent? :-[
Quote from: iBeethoGun on May 14, 2013, 06:17:14 PM
Hi everyone ! I'm french, and i'm trying to understand your posts... But my english is not good enough !
I just have one question please, i'm about to buy a DSLR for video mainly. Hesitating between Sony Alpha 77 or 650D with Magic Lantern...
Reading your words, it seems that a lot of features are working now. So have i just to install ML alpha to get all those features working well with probably some bugs, or do i need to install it, and then modify some files or other things ?
hopefully you will understand what i mean... :-\
Thx !
If you are in Paris, let me know, I will be there early next week and can show you my T4i with PA2 on it and you can play with it a bit. I could help you instal, but hesitant as many say you can brick, but I think if people follow the exact dirs, there won't be an issue.
And you could help me with things there in Paris in exchange perhaps?
Quote from: newsense on May 14, 2013, 06:45:39 PM
Has anyone else noticed the histogram updates slow in 60p or is it just me?
It's probably not a bug, but I'll check it out
How do I install ML onto my 650D?
You read the thread.
Quote from: Stevenbaril on May 15, 2013, 06:34:37 AM
How do I install ML onto my 650D?
This is what worked for me:
Create a magic lantern folder on your hard drive
Download http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip (unzip all files to your ml folder on your hard drive)
On your camera select menu, first wrench icon, format card
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified, then copy the .fir file to your card and put it back in the camera.
With the cam in manual mode, go to last wrench setting before star, fimware ver, set, select ok, then my menu settings will read enablebootdisk :)
Put your card in the computer and download http://pel.hu/down/EOScard.exe and run this program
Check EOS Devlop and Bootdisk boxes, save
Check the card, if EOS card wrote any files, delete them
Copy from your ML folder these files: ML folder, autoexec.bin and 650D-safe-dumper.fir to your card
Put card in camera and press the trashcan button after it boots, then the left arrow button to the left of the set button
Hi everyone. Firstly, big thank you to the ML developers. You're doing a great job and I look forward the stable version of ML for 650D.
The main reason why I want to install ML on my camera is 'intervalometer'. I wouldn't probably use much else from ML.
And so the question: Is it stable and safe to use intervalometer in pre-alfa version? Or am I better to wait till the stable version is released. I am between waiting for that or buying a hardware intervalometer.
Thank you for you time to answer.
PS: i am tempted to ask when the ML is done (in weeks? months? years?), but i already know the answer from reading this forum for a while ;) keep up the good work guys!
Just downloaded ML - everything seems to be working fine (when I say this, I mean that all of the little bugs that I have noticed have already been mentioned in this thread).
I did notice something, however. My LiveView is tinted ever so slightly more red/orange than the actual picture. Is this normal?
When enabling the boot flag the camera is giving errors about fonts.dat. Should I have the ML folder and the 650D-safe-dumper.fir both on the card?
To clarify all that is currently on the card is the "650D-safe-dumper.fir" file
Thx
Yes, you need the fir and the ML stuff on the card
Massive thanks to Nanomad and all. Installed and working. Now to test everything. ;D
QuoteThis is what worked for me:
Create a magic lantern folder on your hard drive
Download http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip (unzip all files to your ml folder on your hard drive)
On your camera select menu, first wrench icon, format card
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified, then copy the .fir file to your card and put it back in the camera.
With the cam in manual mode, go to last wrench setting before star, fimware ver, set, select ok, then my menu settings will read enablebootdisk
Put your card in the computer and download http://pel.hu/down/EOScard.exe and run this program
Check EOS Devlop and Bootdisk boxes, save
Check the card, if EOS card wrote any files, delete them
Copy from your ML folder these files: ML folder, autoexec.bin and 650D-safe-dumper.fir to your card
Put card in camera and press the trashcan button after it boots, then the left arrow button to the left of the set button
I tried this, now my camera won't turn on as long as the card is in the camera. Did I brick the camera, or corrupt the card?
Stevenbaril -- Your camera and card are most likely fine...
I had the same issue. I tried to find the post page where it was addressed, but no dice.
Just make damn sure you follow step, "Check the card, if EOS card wrote any files, delete them"
This is what got me, first attempt. If I were you, I'd format the SD card and 'take it from the top'.
Cheers
I checked to see if EOScard wrote any files. I noticed that after running EOScard that these files appear on my card:
ML (folder)
autoexec
ROM.dat
User Guide
INSTALL
Shall I delete all these files, then copy the Magic Lantern folder I made to the card, then insert into my camera and boot up?
Guys, I know its prealpha but I really can't wait to run ML on my t4i
is it safe to install it yet?, and if so... is ML's installation reversible?
is there any known risks for this release?
Quote from: Stevenbaril on May 16, 2013, 06:10:04 AM
I checked to see if EOScard wrote any files. I noticed that after running EOScard that these files appear on my card:
ML (folder)
autoexec
ROM.dat
User Guide
INSTALL
Shall I delete all these files, then copy the Magic Lantern folder I made to the card, then insert into my camera and boot up?
Replace the files on the card with the ones inside the zip
I installed it, after 30 mins of playing I gotta say this is real good for a pre-alpha :D
the only problem I had is the camera crashes when I'm browsing the menu and the live view automatically shuts itself off and switch to the view finder
I was browsing the frame override menu to be exact
--
I dunno where to send the crash logs?
I can't find any attachment options in here
I started doing this, but that EOS Card program doesn't work on Mac and I tried using Wine Bottler, and that didn't work. Hopefully a fix comes up soon.
Quote from: digital_canon on May 16, 2013, 05:16:40 PM
I started doing this, but that EOS Card program doesn't work on Mac and I tried using Wine Bottler, and that didn't work. Hopefully a fix comes up soon.
Use MacBoot
http://wiki.magiclantern.fm/3rd_party_software
I believe you need to check the BootDSLR box
Quote from: Eslam Omar on May 16, 2013, 12:17:04 PM
I dunno where to send the crash logs?
I can't find any attachment options in here
Upload them somewhere (dropbox? Mega?) and link them here
I've got all the files downloaded. Should be able to test when I get back home. Will try and go as in-depth with feedback as I can.
I saw the question a little further back, but will it be at all possible to shoot in RAW? I know the 5D3 can because it has RAW out already, but is there any potential for the 650 to do similar?
Quote from: nanomad on May 16, 2013, 05:29:02 PM
Upload them somewhere (dropbox? Mega?) and link them here
there ya go,
http://www.mediafire.com/?7s62h7527zkpakk
& is it possible for the new continuous RAW to work on the t4i?
O Magic Lantern para nossa câmera (650D/T4I) funciona ou funcionará com touchscreen?
;)
The Magic Lantern for our camera (650D/T4I) work or work with touchscreen?
;)
Mostly without although you can tap to confirm selection
RAW recording should work with resolution just under 720p at 24 fps but in reality it produces pink noise only. That's what I'm working on
Quote from: nanomad on May 16, 2013, 09:19:41 PM
RAW recording should work with resolution just under 720p at 24 fps...
Is there a technical reason for this or is it just a quirk that it has to be that low of a resolution?
Canon went cheap with the sd controller
Well after a short outing with the 650D it appears that most of the features work.
The only real issue I found with the features I used was that MagicZoom flickered quite a bit, but I believe that was covered already.
Tests:
Overlays
-Zebras: OK
-Focus Peak: OK
-MagicZoom: Heavy flickering at 1080p, useable at 720p
-Cropmarks: OK
-Ghost Image: OK
-Spotmeter: OK
-False Color: OK
-Histogram: OK
-Waveform: OK
-Vectorscope: OK
Movie
-BitRate: Untested
-REC Key: OK
-Gradual Exposure: OK
-FPS Override: Untested
-HDR Video: OK
-Vignetting: Untested
-Image Finetuning: Untested
-Movie Tweaks: All OK
Shoot
-Intervalometer: OK
-Motion Detect: Didn't seem to work
-Silent Picture: Also appeared to be unworking
-Shoot Preferences: All OK
All display settings appeared to work.
FPS Override is bugging way out on me.
Causes the entire overlay to flicker during preview.
Anyone else seeing that?
Vignetting is working perfectly though.
The container fps is whatever you select in Canon menu, you need to import the video in an editor and override it
Quote from: nanomad on May 17, 2013, 06:41:19 AM
The container fps is whatever you select in Canon menu, you need to import the video in an editor and override it
Thanks. I tested and everything seems to be working right. Still getting the strange flickering of the overlay while using FPS Override during preview, but everything else seems to be working.
Hi guys
Just say cheers for all the hard work from the developers and testers on this! Looking forward to the full release. :) Slowly working through all the features and will flag up anything that doesn't work as it should etc
I noticed there is one thing missing from these great instructions as it caught me out - see in blue. Hope this helps everyone
Cheers
L
Quote from: donjames150 on May 15, 2013, 08:02:05 AM
This is what worked for me:
Create a magic lantern folder on your hard drive
Download http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip (unzip all files to your ml folder on your hard drive)
On your camera select menu, first wrench icon, format card
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified, then copy the .fir file to your card and put it back in the camera. (You also need the extracted ML files on the card too)
With the cam in manual mode, go to last wrench setting before star, fimware ver, set, select ok, then my menu settings will read enablebootdisk :)
Put your card in the computer and download http://pel.hu/down/EOScard.exe and run this program
Check EOS Devlop and Bootdisk boxes, save
Check the card, if EOS card wrote any files, delete them
Copy from your ML folder these files: ML folder, autoexec.bin and 650D-safe-dumper.fir to your card
Put card in camera and press the trashcan button after it boots, then the left arrow button to the left of the set button
Ok, I went for it and downloaded this version onto my 650D. Install was fine.. Seems to work better using a PC. I'm a newbie but in the menu are you meant to get a little rectangle showing a portion of the live view at the bottom of the screen, covering up the description of the feature you're highlighting? And I can't seem to get any of the features of ML to actually affect the display. Nothing seems to be happening, such as Focus Peak. Any help?
Also the capacity of the SD card value actually covers up the battery symbol when using the viewfinder which is a bit annoying. Am I doing something wrong or is this an easy fix?
Quote from: Morkins on May 17, 2013, 06:55:40 AM
Thanks. I tested and everything seems to be working right. Still getting the strange flickering of the overlay while using FPS Override during preview, but everything else seems to be working.
Can you upload a video of the flickering? Quickly browse ML menus and canon menus so I can see what settings are in use
- Canon overlays drawing over ML menu: known bug, I'll try the EOSM fix
- No ML stuff in LV: User error :P Press DISP button until Canon overlays are gone :)
- SD card capacity doing weird stuff: known bug, the fix did not work as I expected though. I'll try different positions
Quote from: Eslam Omar on May 16, 2013, 12:17:04 PM
I installed it, after 30 mins of playing I gotta say this is real good for a pre-alpha :D
the only problem I had is the camera crashes when I'm browsing the menu and the live view automatically shuts itself off and switch to the view finder
It should happen when you have FPS override ON and FPS higher than max supported by the camera. FPS Override isn't really fully working on the 650D right now (need more time testing timings and such), think of it as a bonus feature for now :)
Nevermind, just had to turn off the Canon interface. :D When I take stills in movie mode, horizontal bars appear in the photos though.
Quote from: mattgirvan on May 17, 2013, 01:37:06 PM
Nevermind, just had to turn off the Canon interface. :D When I take stills in movie mode, horizontal bars appear in the photos though.
Yeah, I noticed that also, but wasn't sure if it was expected behavior or not???
Once again, THANK YOU DEV TEAM!!!
Tried it last night
so far so good need to test all the menus still
Thanks and cant wait for Final version
I will be taking my camera out this weekend to shoot an episode of my series. I will use the Sigma 30mm F1.4 lens (2013 Version) and have the bitrate set to CBR 1.3x (So far that's the only rate that I find actually makes a difference and ups the bitrate to over 60mbps) I will post the youtube link here when it's all edited together!
Hey I read in https://bitbucket.org/hudson/magic-lantern/commits/all
some ting like this :
650D: Habemus RAW video recording
WTF ???
Quote from: ZiskinbMe on May 17, 2013, 08:48:40 PM
Hey I read in https://bitbucket.org/hudson/magic-lantern/commits/all
some ting like this :
650D: Habemus RAW video recording
WTF ???
Looks like exactly what it says... RAW video recording support for the 650D. ;)
It's a pity that Canon made a mess with the SD controller. It says that it's UHS I, but the writing speed doesn't really confirm this. It could have been a decent raw recording little camera. I hope ML guys will be able to squeeze something out of it.
Hey guys,
here is a new link (https://www.dropbox.com/sh/q1zrrlmy03psr2y/F3PR9UwMWZ) of my compiled ML from the last source inkl. "RAW video recording", but i have not tested this.
Quote from: satriani on May 17, 2013, 10:22:45 PM
Hey guys,
here is a new link of my compiled ML from the last source inkl. "RAW video recording", but i have not tested this.
I'm not thinking publishing compiled binaries of just committed code is so much a good idea as not good. I realize that there is a strong desire to help others out in the ML community, but I think waiting for the next round of alpha is much safer. Please read:
http://www.magiclantern.fm/forum/index.php?topic=3624.0
http://marcansoft.com/blog/2011/01/safe-hacking/
This is not even tested and risks mass-bricking of cameras. This is
VERY RISKY.
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1acd00
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1acca0
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x1acc80
[Pass] bar => '*****hjkl;'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0x14dd6
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0x52860
[Pass] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x2
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x28
Date/time: 2013/05/17 19:43:40
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x2a
[Pass] mod(s1-s0, 60) => 0x2
[Pass] mod(s1-s0, 60) => 0x2
m0 = MALLOC_FREE_MEMORY => 0x36b48
[Pass] p = malloc(50*1024) => 0x108c80
[Pass] CACHEABLE(p) => 0x108c80
m1 = MALLOC_FREE_MEMORY => 0x2a338
free(p)
m2 = MALLOC_FREE_MEMORY => 0x36b48
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x3851a8
[Pass] p = AllocateMemory(256*1024) => 0x802cf0
[Pass] CACHEABLE(p) => 0x802cf0
m1 = GetFreeMemForAllocateMemory() => 0x34519c
FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x3851a8
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x36b48
m02 = GetFreeMemForAllocateMemory() => 0x3851a8
[Pass] p = alloc_dma_memory(256*1024) => 0x40802d30
[Pass] UNCACHEABLE(p) => 0x40802d30
[Pass] CACHEABLE(p) => 0x802d30
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40802d30
free_dma_memory(p)
[Pass] p = (void*)shoot_malloc(24*1024*1024) => 0x42200068
[Pass] UNCACHEABLE(p) => 0x42200068
shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x36b48
m12 = GetFreeMemForAllocateMemory() => 0x3851a8
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[Pass] suite = shoot_malloc_suite_contig(24*1024*1024) => 0x108c80
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1800000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x108ca8
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1800000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42200064
[Pass] UNCACHEABLE(p) => 0x42200064
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0xf81f0
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1f24000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x108618
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1f24000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x48000064
[Pass] UNCACHEABLE(p) => 0x48000064
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(64*1024*1024) => 0xf81f0
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x5
[Pass] suite->size => 0x4000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x108618
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x19bc000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000064
[Pass] UNCACHEABLE(p) => 0x4a000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x1086d0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x37b8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42200064
[Pass] UNCACHEABLE(p) => 0x42200064
chunk = GetNextMemoryChunk(suite, chunk) => 0x108708
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3bb8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x419ff0a4
[Pass] UNCACHEABLE(p) => 0x419ff0a4
chunk = GetNextMemoryChunk(suite, chunk) => 0x108740
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3c90000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x49f240e4
[Pass] UNCACHEABLE(p) => 0x49f240e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x108778
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x48000064
[Pass] UNCACHEABLE(p) => 0x48000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4000000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0xf81f0
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x6
[Pass] suite->size => 0x5c00000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x108618
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x19bc000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000064
[Pass] UNCACHEABLE(p) => 0x4a000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x1086d0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x37b8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42200064
[Pass] UNCACHEABLE(p) => 0x42200064
chunk = GetNextMemoryChunk(suite, chunk) => 0x108708
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3bb8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x419ff0a4
[Pass] UNCACHEABLE(p) => 0x419ff0a4
chunk = GetNextMemoryChunk(suite, chunk) => 0x108740
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3c90000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x49f240e4
[Pass] UNCACHEABLE(p) => 0x49f240e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x108778
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x5bb4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x48000064
[Pass] UNCACHEABLE(p) => 0x48000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x1087b0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x5c00000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x47f240e4
[Pass] UNCACHEABLE(p) => 0x47f240e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x5c00000
shoot_free_suite(suite); suite = 0; chunk = 0;
EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0x599200ce
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id((unsigned int)get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x2f3800b0
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0x2fd001ba
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0x3072008a
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x4
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x40802d30
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x4
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
SW1(1,100)
[Pass] HALFSHUTTER_PRESSED => 0x1
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
Quote from: papkee on May 17, 2013, 12:29:35 AM
Well after a short outing with the 650D it appears that most of the features work.
The only real issue I found with the features I used was that MagicZoom flickered quite a bit, but I believe that was covered already.
Tests:
Overlays
-Zebras: OK
-Focus Peak: OK
-MagicZoom: Heavy flickering at 1080p, useable at 720p
-Cropmarks: OK
-Ghost Image: OK
-Spotmeter: OK
-False Color: OK
-Histogram: OK
-Waveform: OK
-Vectorscope: OK
Movie
-BitRate: Untested
-REC Key: OK
-Gradual Exposure: OK
-FPS Override: Untested
-HDR Video: OK
-Vignetting: Untested
-Image Finetuning: Untested
-Movie Tweaks: All OK
Shoot
-Intervalometer: OK
-Motion Detect: Didn't seem to work
-Silent Picture: Also appeared to be unworking
-Shoot Preferences: All OK
All display settings appeared to work.
I've used the vignetting, and it works just fine.
Quote from: ZiskinbMe on May 17, 2013, 08:48:40 PM
Hey I read in https://bitbucket.org/hudson/magic-lantern/commits/all
some ting like this :
650D: Habemus RAW video recording
WTF ???
Latin :p
I literally tested it for 30 seconds so feel free to try it if you want. Keep in mind that you also need to enable modules and TCC in order to use the raw video recorder
What's the best resolution we could hope for on 650D raw? Could we get something in the neighbourhood of 1920x800? Cheers! And thank you for you hard work!
Less than 720p
Manual white balance. What can I do to help the progress?
@donjames150, thanks for the instructions. I was able to put ML on my T4i. I've noticed that the "EXPO" menu is not available in the version I installed. I was really looking forward to exploring the ISO half steps but am unable to. Does anyone know if/when that menu setting will be available for the T4i?
hey Nanomad
I compiled from 17/5/2013 and test It and I want to tell you thank you very much
Tests:
Stubs API test : 4750 Pass 0 Fail
Overlays
-Zebras: OK
-Focus Peak: OK
-MagicZoom: OK
-Cropmarks: OK
-Ghost Image: OK
-Spotmeter: OK
-False Color: OK
-Histogram: OK
-Waveform: OK
-Vectorscope: OK
Movie
-BitRate: OK
-REC Key: OK
-Gradual Exposure: OK
-FPS Override: Didn't seem to work
-HDR Video: OK
-Vignetting: OK
-Image Finetuning: OK
-Movie Tweaks: All OK
Shoot
-Intervalometer: Untested
-Motion Detect: Untested
-Silent Picture: Untestedg
-Shoot Preferences: Untested
All display settings appeared to work.
Test 2
Expo
-WhhiteBalance: working kelvin auto adjust .... all working fine
-ISO: OK 160 320 1250 working good
-shutter : ok
all expo working fine thanks
Quote from: satriani on May 17, 2013, 10:22:45 PM
Hey guys,
here is a new link (https://www.dropbox.com/sh/q1zrrlmy03psr2y/F3PR9UwMWZ) of my compiled ML from the last source inkl. "RAW video recording", but i have not tested this.
Hello! Working unexpectable. many new bugs (not in raw video))) .... Anyway, Thank you!
Quote from: ZiskinbMe on May 18, 2013, 11:47:31 AM
Test 2
Expo
-WhhiteBalance: working kelvin auto adjust .... all working fine
-ISO: OK 160 320 1250 working good
-shutter : ok
all expo working fine thanks
Can you test silent pictures?
Hello! Working unexpectable. many new bugs (not in raw video))) .... Anyway, Thank you!
sorry
------Hello! Working unexpectable. many new bugs (not in raw video))) .... Anyway, Thank you!
I didn't find any bug you can explain
and silent pic working
Quote from: ZiskinbMe on May 18, 2013, 12:10:56 PM
sorry
------Hello! Working unexpectable. many new bugs (not in raw video))) .... Anyway, Thank you!
I didn't find any bug you can explain
and silent pic working
Did you use a nightly compiled build? If so you will get a lot of features which are not working
first from what I tested only 1 thing didn't work is FPS
Quote from: VlastaS on May 17, 2013, 09:27:16 PM
It's a pity that Canon made a mess with the SD controller. It says that it's UHS I, but the writing speed doesn't really confirm this.
As long as major Brand SD-Cards with 30MB/s sport the UHS-1 Badge i think Canon can claim UHS-1 for 40MB/s too ^^
Just a warning
NEW BUILDS FROM SOURCE HAVE PROPS ENABLED
They can potentially brick your camera if a prop is not set correctly due to a bug
Quote from: nanomad on May 18, 2013, 01:09:33 PM
Just a warning
NEW BUILDS FROM SOURCE HAVE PROPS ENABLED
They can potentially brick your camera if a prop is not set correctly due to a bug
Can you build a build for us with correct props?
I cannot "correct" a prop, you can either build with props enabled or disabled. And the source code in the repository has them enabled. You can disable them by commenting a line in internals.h and recompiling the source code
Quote from: nanomad on May 18, 2013, 02:04:17 PM
I cannot "correct" a prop, you can either build with props enabled or disabled. And the source code in the repository has them enabled. You can disable them by commenting a line in internals.h and recompiling the source code
Oh okay! Thanks for the correction :)
well i have tried to follow the instructions to install the preAlpha.
when i try to update the firmware (1.0.1) i am getting "update file cannot be found" error message.
The 650-safe-dumper.fir (size 216,124b) is on my SanDisk Extreme SDXC I 64GB card that was previously low-level formatted.
what am i doing wrong? i have tried it several times with no success. even downloaded the file again, but still the same message.
cheers for help
Quote from: tomaash on May 18, 2013, 02:14:28 PM
well i have tried to follow the instructions to install the preAlpha.
when i try to update the firmware (1.0.1) i am getting "update file cannot be found" error message.
The 650-safe-dumper.fir (size 216,124b) is on my SanDisk Extreme SDXC I 64GB card that was previously low-level formatted.
what am i doing wrong? i have tried it several times with no success. even downloaded the file again, but still the same message.
cheers for help
This has worked for several people here who have had trouble getting ML installed:
This is what worked for me:
Create a magic lantern folder on your hard drive
Download http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip (unzip all files to your ml folder on your hard drive)
On your camera select menu, first wrench icon, format card
download https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified, then copy the .fir file to your card and put it back in the camera.
With the cam in manual mode, go to last wrench setting before star, fimware ver, set, select ok, then my menu settings will read enablebootdisk :)
Put your card in the computer and download http://pel.hu/down/EOScard.exe and run this program
Check EOS Devlop and Bootdisk boxes, save
Check the card, if EOS card wrote any files, delete them
Copy from your ML folder these files: ML folder, autoexec.bin and 650D-safe-dumper.fir to your card
Put card in camera and press the trashcan button after it boots, then the left arrow button to the left of the set button
thanks donjames150.
these are the exact instructions i have followed and the comments of others made me confident to test it.
i know it worked for them and i don't understand why it doesn't work for me...
Quote from: tomaash on May 18, 2013, 02:30:31 PM
thanks donjames150.
these are the exact instructions i have followed and the comments of others made me confident to test it.
i know it worked for them and i don't understand why it doesn't work for me...
Try all steps again. Sometimes a file (such as the .fir file) doesn't copy correctly and doesn't indicate that it didn't copy incorrectly. If that
doesn't work, try rebooting your computer and then re-download the .fir file and copy to your card. I have all sorts of strange things happen
if I don't reboot regularly.
Another thing to do is a disk check on your card, it's a long shot but something is wrong :-)
Or you could just upload a screenshot of the content of the card, as you're probably copying stuff in the wrong place ;)
Hi tomaash
Not sure but maybe the reason is you use a 64BG card?
"■For first install, use a simple SD/SDHC/CF card (32 GB or smaller). 64GB cards and larger will not work for first install (but you can use them with ML, see below).
"
If you have a smaller card give it a try with that one - you can use the bigger ones as explained in the install instructions in the Documentation web pages.
Best, Robert
the instructions posted by donjames are accurate but to get it to install for me i had to go into menu > 4 dot spanner > Clear Settings > clear all camera settings before the install would work for me.
i also used a 2GB and 16GB card, not tried on my 32GB (currently has footage from a live project on it) and i dont have a 64GB.
i also didnt get the green boot disk screen but i have a 3 day old build installed and most features work as already stated.
Massive thanks go out to Nanomad and the rest of the team for all this hard work.
Quote from: En veritas on May 18, 2013, 06:10:32 PM
the instructions posted by donjames are accurate but to get it to install for me i had to go into menu > 4 dot spanner > Clear Settings > clear all camera settings before the install would work for me.
i also used a 2GB and 16GB card, not tried on my 32GB (currently has footage from a live project on it) and i dont have a 64GB.
i also didnt get the green boot disk screen but i have a 3 day old build installed and most features work as already stated.
Massive thanks go out to Nanomad and the rest of the team for all this hard work.
you are right, that's something I forgot in my instructions. I had cleared my special settings ::)
thank you all for your input.
it looks like the size of the card might be the problem however that's the only card i have.
* i cleared my settings
* i downloaded bright new .fir file
* all the files (ML folder, autoexec.bin a 650D-safe_dumper.fir) are in the root of the card (as in the tutorial video)
* chkdsk found no errors
the next step is to find another card and try it all again.
any experience with using a big card? mine is SanDisk Extreme SDXC I 64GB 45MB/s, the one I bought with the camera.
can anybody please test the card to see if that's the problem?
Canon SHOULD pay these guys for this AWESOME work!!! you probably increased canon DSLR's sales by 20% :)
Don't know maybe there is already is this: but controlling audio bitrate as the video-would be great. i guess nobody needs audio with 1500 Kbps. 448 should be good :D
Also noticed that focus peak drains battery very fast (and camera is new..so it couldn't be old batt) and increases cpu temp kinda fast. from 33c to 45c in 10mins :(
PS. i did all the instructions in above post and everything works.
Quote from: tomaash on May 18, 2013, 06:53:32 PM
thank you all for your input.
it looks like the size of the card might be the problem however that's the only card i have.
* i cleared my settings
* i downloaded bright new .fir file
* all the files (ML folder, autoexec.bin a 650D-safe_dumper.fir) are in the root of the card (as in the tutorial video)
* chkdsk found no errors
the next step is to find another card and try it all again.
any experience with using a big card? mine is SanDisk Extreme SDXC I 64GB 45MB/s, the one I bought with the camera.
can anybody please test the card to see if that's the problem?
Looks like your card IS the problem. You can't use a larger than 32 gb card for first install (updating firmware), but you can run ML
on it after you've updated the firmware
http://magiclantern.wikia.com/wiki/Unified/Install
First-time installation
Magic Lantern Unified - Install Tutorial(03:22)
49,518 views
Step 1. Preparing your camera
Fully charge your battery
Remove any accessories from your camera (such as battery grip or external flash)
For first install, use a simple SD/SDHC/CF card (32 GB or smaller). 64GB cards and larger will not work for first install (but you can use them with ML
Best Buy has 2GB cards for $4
good job donjames150. thank you. meanwhile i have found this and was about to post it too...
"SD cards up to 2G size are always formatted in-camera with FAT16 file system, where SDHC cards 4G and larger format with FAT32 (and even larger SDXC cards with ExFAT) ... It seems that most firmware update executables run more happily in the FAT16 file system environment."
so yes the ExFAT file system of my 64GB card is the problem. well unexpected.
thanks everybody.
Hi everyone, just installed ML and everything looks useful, as I see, you just got to be lurking on this thread in order to avoid messing it up.
Btw, after reading this whole thread, I got surtprised about Canon and its such way to shit on hardware (The whole SDcard thing) in order to stop the ML train... But CHOO CHOO motherfuckers, we are here!
"Saludos" for everybody who is woking in this project.
I should've brought the T3i
Nano, how close are we in terms of any RAW capabilities or even another PreAlpha?
I'm quite interested in helping out by beta testing whenever I can.
Quote from: nanomad on May 17, 2013, 12:31:44 PM
Can you upload a video of the flickering? Quickly browse ML menus and canon menus so I can see what settings are in use
- Canon overlays drawing over ML menu: known bug, I'll try the EOSM fix
- No ML stuff in LV: User error :P Press DISP button until Canon overlays are gone :)
- SD card capacity doing weird stuff: known bug, the fix did not work as I expected though. I'll try different positions
Sorry for the terrible phone video(which refused to focus), but I was just wanting to sort of show you what I was talking about.
Edit - Give youtube a minute to process....
Too many noobs if you are going to post in a forum do a little research. ;D So when the admins and devs see your post they don't go from this :D to this >:( because you are asking for stupid things like 4k video on a t2i.
Quote from: papkee on May 19, 2013, 05:01:13 AM
Nano, how close are we in terms of any RAW capabilities or even another PreAlpha?
I'm quite interested in helping out by beta testing whenever I can.
RAW fully working, 1280x560 is what a good card can record at 24p. The trouble is that the RAW feed has the movie mode AF points burnt into the image. It's probably a software thing as canon H264 video doesn't have them and I need to figure them out before releasing anything.
Quote from: Morkins on May 19, 2013, 05:14:04 AM
Sorry for the terrible phone video(which refused to focus), but I was just wanting to sort of show you what I was talking about.
Edit - Give youtube a minute to process....
Are you changing FPS while recording? If so, you're not supposed to as everything goes out of sync
I know all about the when is it going to be finished questions and will it have this super dooper thingy
Im just curious to see if you've toyed in your mind what might be possible with the 650d?
If this is a silly question or wastes your time, then please dont answer
Im just in the process of choosing a camera between the 600d and 650d for videoing motocross and Im at a cross roads
Many thanks for all of your hard work desire :)
Paul
www.freedom7motox.com
Are there any plans for 5 7 or 9 shot auto bracketing?
Quote from: APXmusic on May 19, 2013, 10:47:38 AM
Are there any plans for 5 7 or 9 shot auto bracketing?
im also waiting for this...
It's already working once you enable props
I have been following this thread since last October (nearly every day!), recently installed the pre-alpha thanks to you guys. I wanted to congratulate Nanomad on cracking the Raw recording, can't wait to test!
Nanomad, I have also read stuff on ML about the ability to record clean HDMI with an external device, and a recent firmware update on the 5D mark III which allows for clean HDMI recording; can we hope for more improvement on that front with the 650d or what you are doing now is as good as it will get (which is already great)?
back again... with ML on my camera!
beyond my expectations what you guys put together to make photographer's life easier or in a way to allow him to be more creative... thanks a lot!!
i have had the camera for only a couple of months so i am still exploring all the build-in features of the camera itself.
i was looking at Creative filters and when i applied one of them a canon message pops up saying "cannot playback image" and a moment later ML error message overlays it and camera freezes with red LED on. had to remove battery...
the ML msg says:
ASSERT: isChuckSignature...
here's the log:
ASSERT: IsSuiteSignature( hSuite )
at ./PackMemory/PackMem.c:577, task InnerDevelopMgr
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013Apr30.650D101
Mercurial changeset : ca7870e6a59c (unified)
Built on 2013-04-30 13:27:39 by nanomad@workhorse.
Free Memory : 316K + 3667K
===
when looking for the log files on the card i found a file drive:\ML\LOGS\ROM0.BIN, size 16MB ?!
a bug??
just to clarify. i installed ML from a small 32MB SD card, but running ML from the 64GB SDXC. also i have no idea whether the Creative filters worked before i installed ML, however it seems like it's ML that causes the actual crash/freeze.
correction: i updated the firmware from small 32MB card (not ML)...
Looks like it run out of memory...did you use any other ML features or run stuff from the debug menu before testing the creative filters?
Quote from: tommix on May 19, 2013, 07:41:59 PM
few months and still exploring?? man..this is noob's camera..toy..what you explore so long in it? :D really...i want to...cause right now im ashamed to even show this cam to people :D looks like toy.
sorry for offtopic :D
*sniff sniff* I smell a troll in the making, please leave the forum or keep your trap shut if you have nothing positive to say towards other members...
Not everyone is a photographer expert or can instantly know every end and out of a camera just by merely touching it and this by far not a toy like a point and shoot camera would be in comparison...
Have some respect for others in this forum...
It's only a toy if you play ML's script game :P
Quote from: Lucas_W on May 19, 2013, 08:36:33 PM
It's only a toy if you play ML's script game :P
omg how cool would it be if they were able to get tetris to work on these cameras? have something to play during your down time lol that would be epic ^_^
Quote from: nanomad on May 19, 2013, 10:34:51 AM
Are you changing FPS while recording? If so, you're not supposed to as everything goes out of sync
Nope. When I'm recording it doesn't flicker at all. That only happens while previewing.
650D + M are definitely the runts of the litter. Quality is acceptable, esp compared to what was around previous years.
Should find out whats up with the creative filters to get image effects back on DigicV...
Quotehat you explore so long in it?
Dump fw and find out
Hello, first I want to thank the contribution nanomad MagicLantern For Canon T4 .. And second question I wanted to query a ... I have noticed that the official version v2.3 has the Live Audio ... So my question is if in the future this feature will be present for this camera ...
Sorry if I do not write as it should but I'm using the google translator ... and thanks in advance ...
creative filters issue:
i have tried it again and it fails without doing anything before. the logs are the same.
the 32MB SD card is too small and it won't let me apply any filter so can't try that. even with low-res picture (S3).
i tried to apply filter to low-res photo on the 64GB card and it failed too. smaller picture would take less memory however it didn't make any difference.
another thing that surprised me and i am not sure if it is an intention...
when formatting the small card that had ML installed (to see what it does without ML) i got a ML message, after the formatting finished, saying "unknown partition: 4". also no option to remove/keep ML as the 'installation wiki' says. it behaved normal after second format. no ML message.
anyone else keen to try that? or is it only my camera doing it? meaning applying 'creative filters'...
tomaash I have the same problem that you have with creative filters
Quote from: nanomad on May 19, 2013, 10:32:45 AM
RAW fully working, 1280x560 is what a good card can record at 24p. The trouble is that the RAW feed has the movie mode AF points burnt into the image. It's probably a software thing as canon H264 video doesn't have them and I need to figure them out before releasing anything.
That's actually not bad. That's about the same as a cinescope video at 720p, and with the prices on Extreme cards going down every day it looks like the 650d may actually be viable as a budget raw camera.
Quote from: Karlos_01 on May 20, 2013, 01:37:39 AM
tomaash I have the same problem that you have with creative filters
Can you try creative filters with a card that does not have ML on it? (or just disable the boot flag from the ML card using EOSCard)
Quote from: nanomad on May 20, 2013, 09:30:22 AM
Can you try creative filters with a card that does not have ML on it? (or just disable the boot flag from the ML card using EOSCard)
hi nanomad, it works fine with my 64GB card with disabled bootflag. i could apply any filter on high-res photo with no problem.
what is the newest pre alpha version for 650D i used both """v2.3.NEXT.2013Apr30.650D.PreAlpha2"" and 2013.june10 version, anythinw than these two???????????
A few random question for the devs,
When shooting video, I have read that the camera uses a pixel skipping process to scale down the 18mp image captured by the sensor to a ~2mp 1080 video frame, or a ~1mp 720 frame. So then the cpu is basically just remapping select pixels from the sensor into the video frame of whatever size if I am understanding correctly?
Is there any possibility that the sensor data could be looked at on the whole and downsampled so that averaged values were used for the remapped pixels or is there not enough horsepower in the cpu to process that amound of data quickly enough to fill the frame buffer in real time?
If downsampling (mathematically averaging and redrawing not simply remapping values) is not possible maybe its possible to fine tune focus peaking so that the peaking would register as ideal when ever so slightly defocused, which actually seems to produce an equally sharp video image with less aliasing and less moire?
I have no clue about altering the downsampling algorithm (it could be hardcoded or programmable, who knows). What's sure is that using the CPU to do so is impossible
About focus peaking, you can raise the treshold as you wish (the higher, the more "false" in focus points you have)
I have a crash-log for you guys playing around with black levels
https://www.dropbox.com/s/i86ow3nxonxwhj0/MLcrash.zip
Question about the pre-alpha given: Looking through a lot of this forum, is the FPS Override the only major hurdle/problem keeping it from being an alpha release? Or is there more major problems than this. I'm about to put this onto my camera so just wanted to know what exactly to inspect and such. Thanks!
Quote from: nanomad on May 19, 2013, 10:32:45 AM
RAW fully working, 1280x560 is what a good card can record at 24p. The trouble is that the RAW feed has the movie mode AF points burnt into the image. It's probably a software thing as canon H264 video doesn't have them and I need to figure them out before releasing anything.
What do you mean by a good card ? Is a 45mb/s Sandisk Extreme (http://www.amazon.com/SanDisk-Extreme-Class-Memory-SDSDX-032G-AFFP/dp/B007M54E1M) enough for this ? I did a benchmark of it on ML and i've got an average of 39 / 40 mb/s in write speed (with a peak of 41.2 mb/s when it comes to bigger buffer)
Thanks for everything !
Quote from: nanomad on May 20, 2013, 11:24:42 PM
I have no clue about altering the downsampling algorithm (it could be hardcoded or programmable, who knows). What's sure is that using the CPU to do so is impossible
About focus peaking, you can raise the treshold as you wish (the higher, the more "false" in focus points you have)
Good to hear that focus peaking treshold is adjustable, thanks. Not sure what would be in control of downsampling, cpu was just a catch all term, intended to be anyway, not sure if there was more in the camera for processing than that digic 5 chip because have no clue about the hardware in the camera. :-)
I do have a feeling that Canon would make a point to make such a thing impossible because if these cameras simply had an average downsampling matrix, say like the default windows picture viewer, then the video quality would smoke movie cameras costing over 20 times more.
HELLO there!
I have read awesome stuff about ML doing remarkable things in cameras like T2i, T3i, 5d series and I am sure in near future I and many of us will have A VERY STABLE VERSION of ML for our T4i/650d cameras. Yes waiting can be very annoying though having this belief that eventually I will have access to something really remarkable is giving me hope :)
I salute to our ML Heros :)
Quote from: ThibaultAnd on May 21, 2013, 10:39:09 AM
What do you mean by a good card ? Is a 45mb/s Sandisk Extreme (http://www.amazon.com/SanDisk-Extreme-Class-Memory-SDSDX-032G-AFFP/dp/B007M54E1M) enough for this ? I did a benchmark of it on ML and i've got an average of 39 / 40 mb/s in write speed (with a peak of 41.2 mb/s when it comes to bigger buffer)
Thanks for everything !
That's as good as it gets on the 650D, so yes. That card is ok
Quote from: nanomad on May 21, 2013, 03:32:30 PM
That's as good as it gets on the 650D, so yes. That card is ok
will be possible with a SanDisk Extreme Pro 95MB/s UHS-I to get double speed? so maybe we can achieve at least 720p at 90Mbs.?
Quote from: red5446 on May 21, 2013, 10:16:42 PM
will be possible with a SanDisk Extreme Pro 95MB/s UHS-I to get double speed? so maybe we can achieve at least 720p at 90Mbs.?
No. This appears to be a limitation of the SD hardware in the 650D. ~40MB/s
cool it work. but what i really wanted is the audiometer. it is a way to get it????????? i just buy a audio amp, a RCA spliter and the canon rca cable for monitoring??
Quote from: dngrhm on May 21, 2013, 10:21:30 PM
No. This appears to be a limitation of the SD hardware in the 650D. ~40MB/s
in the specifications of t4i it says that it supports the latest UHS-I SDHC cards.
here http://www.imaging-resource.com/PRODS/canon-t4i/canon-t4iA6.HTM (http://www.imaging-resource.com/PRODS/canon-t4i/canon-t4iA6.HTM)it says that with a SanDisk Extreme Pro 95MB/s the Time per shot, averaged over 6 shot buffer capacity.
so if we are making something like it´s the 1/9 of a default raw wich is 18MP maybe we can dream a little of taking HD video wich is only 2MP.
Well, the time per shot it's the same with a sandisk 45MB/s
Quote from: red5446 on May 22, 2013, 03:05:03 AM
so if we are making something like it´s the 1/9 of a default raw wich is 18MP maybe we can dream a little of taking HD video wich is only 2MP.
Each image may only be 1/9th the resolution (and, ostensibly, the size) of a full RAW image, but remember that HD video is taking a minimum of 24 of those frames every second.
I only use the SanDisk UHS-1 Cards, and I will absolutely be testing RAW .dng sequence video like crazy when it is implemented. I will probably do a test shoot in Death Valley or on Mt. Wilson just to put it through the paces.
I've successfully installed the second pre-alpha on my camera and I have noticed a bug, I'm not sure if it's been reported before:
When using the standard zoom function (magic zoom turned off) in Manual Video mode i noticed that I got a strange pink abberation of lines and static (in the box) whenever I moved the frame or tried to adjust the focus box. I'll retest when I get back to see if the issue persists.
Quote from: red5446 on May 22, 2013, 03:05:03 AM
in the specifications of t4i it says that it supports the latest UHS-I SDHC cards.
here http://www.imaging-resource.com/PRODS/canon-t4i/canon-t4iA6.HTM (http://www.imaging-resource.com/PRODS/canon-t4i/canon-t4iA6.HTM)it says that with a SanDisk Extreme Pro 95MB/s the Time per shot, averaged over 6 shot buffer capacity.
so if we are making something like it´s the 1/9 of a default raw wich is 18MP maybe we can dream a little of taking HD video wich is only 2MP.
UHS-I can either support a clock of 100MHz writing 4-bits (1/2 byte) per clock = 50 MB/s or UHS104 specifies a 208MHz clock writing 4-bits per clock = 104 MB/s. The SD controller in the T4i is a Macronix MX25L6436EM2I-10G with a clock speed of 104MHz. The T4i will not support anything faster than 50MB/s. Slice and dice your video however you want. That is the (theoretical maximum) hose you have to work with.
Quote from: dngrhm on May 22, 2013, 06:13:55 PM
UHS-I can either support a clock of 100MHz writing 4-bits (1/2 byte) per clock = 50 MB/s or UHS104 specifies a 208MHz clock writing 4-bits per clock = 104 MB/s. The SD controller in the T4i is a Macronix MX25L6436EM2I-10G with a clock speed of 104MHz. The T4i will not support anything faster than 50MB/s. Slice and dice your video however you want. That is the (theoretical maximum) hose you have to work with.
Sorry to be daft- but just trying to understand this limitation- how does this apply to CBR override for instance on the T3i? CBR 1.4 for instance has been shown to be around 62mb/s?
Sorry, just looked in to this more, it is- bits vs bytes...CBR not using nearly as much throughput as RAW
Quote from: dngrhm on May 22, 2013, 06:13:55 PM
UHS-I can either support a clock of 100MHz writing 4-bits (1/2 byte) per clock = 50 MB/s or UHS104 specifies a 208MHz clock writing 4-bits per clock = 104 MB/s. The SD controller in the T4i is a Macronix MX25L6436EM2I-10G with a clock speed of 104MHz. The T4i will not support anything faster than 50MB/s. Slice and dice your video however you want. That is the (theoretical maximum) hose you have to work with.
I wonder if the T5i fixed this by using the 208MHz part?
Quote from: ChodaBoy on May 22, 2013, 08:05:04 PM
I wonder if the T5i fixed this by using the 208MHz part?
Good question. Got a T5i, if so could you open it up and see what SD controller it uses?
Quote from: dngrhm on May 22, 2013, 06:13:55 PM
UHS-I can either support a clock of 100MHz writing 4-bits (1/2 byte) per clock = 50 MB/s or UHS104 specifies a 208MHz clock writing 4-bits per clock = 104 MB/s. The SD controller in the T4i is a Macronix MX25L6436EM2I-10G with a clock speed of 104MHz. The T4i will not support anything faster than 50MB/s. Slice and dice your video however you want. That is the (theoretical maximum) hose you have to work with.
Thanks for not making two devs waste their time in pointless experiments :D
Do you have a source for that info? (even in pm)
Quote from: nanomad on May 22, 2013, 09:07:00 PM
Thanks for not making two devs waste their time in pointless experiments :D
Do you have a source for that info? (even in pm)
Info on UHS (necessary to equate clock speed to data rate)
http://en.wikipedia.org/wiki/Secure_Digital#UHS_Speed_Class
Identify part in 650D (you can either check the print on the ICs or there is a part list at the bottom ;) )
http://www.chipworks.com/blog/recentteardowns/2012/07/06/inside-the-canon-rebel-t4i-dslr/
Info on SD controller
http://datasheet.octopart.com/MX25L6436EM2I-10G-Macronix-datasheet-15540225.pdf
Thanks :)
Note for me: Audio IC is AK4950 -> http://www.asahi-kasei.co.jp/akm/en/product/ak4950/ak4950_f01e.pdf
NANOMAD does the ml t4i have a audiometer
Quote from: slingkidy on May 23, 2013, 02:40:35 AM
NANOMAD does the ml t4i have a audiometer
The T4i has an audio meter in the Canon menu, though no persistent display. Setting a manual gain is also available. This is difficult to get into ML for now as the Audio IC has changed. The higher priority is just getting ML to work on the T4i.
The request has been stated many times throughout this thread. You are not alone in your desire ML audio meter goodness. :)
Audio meter works on eos M while recording... it should work here too... but does not work at idle.
Auto-ETTR looks interesting [Check out the bitbucket log! :)] I wonder what it could get out of the 650D?
http://en.wikipedia.org/wiki/ETTR
https://bitbucket.org/hudson/magic-lantern/commits/all
Also, as the newly appointed moderator for this 'New ports' section, along with blade,
Hello!
Quote from: Lucas_W on May 23, 2013, 07:12:35 AM
Also, I as the newly appointed moderator for this 'New ports' section, along with blade,
Hello!
hi! cool blue bars you got there, dude! keep up your nice work!
Quote from: Lucas_W on May 23, 2013, 07:12:35 AM
Also, as the newly appointed moderator for this 'New ports' section, along with blade,
Hello!
Also from me, Hello...
hello please can you tell me if it works on magic lantern canon 650 d and if so where to find this firmware I can say is just beginning in this world of photography.thank you !
Quote from: adrian2013 on May 23, 2013, 09:22:46 AM
hello please can you tell me if it works on magic lantern canon 650 d and if so where to find this firmware I can say is just beginning in this world of photography.thank you !
The firmware is in the early stages of development right now, meaning it works to some degree but there are features missing and bugs that pop up. It's best if you wait for a later version to be released before you start using it, but if you really must try it now, you can find the files and instructions to do so just by going back through the pages of this thread.
Thank you very much for the reply, I expect stable version
Few thoughts about RAW video:
1. Is it possible to use USB instead of SD card? Theoretically it is 60MB/s. Practically? And would PC or/and USB stick work?
2. One crazy thought: What about combining USB and SD card. For example odd frames would be stored on SD card and even through USB on USB stick or computer. And it would be combined in post-production similarly like HDR video.
3. Is it possible to shoot in RAW but only capture luminosity? Black & white picture would require lower bit rate.
4. Instead of using RAW would jpeg work better?
Thanks for your work. I am thankful user of pre-alpha 2.
1: The theoretical Maximum of USB is around 60MB/s. Practically that is not often reached, usually USB sticks come around 30MB/s, which would be even slower than an SD card solution. Somebody would have to tell us how fast the USB controller is.
My Opinion is that USB would be awesome, because we could use cheap HDDs or SSDs. But I don't know whether it would work over USB at all.
2: No idea, if that is possible.
3: As far as I understand that is not possible. Processing the pictures to black and white would need the CPU to do that to 24 images per second! The CPU can not handle this.
Right now the CPU does nothing at all. All that the RAW feature does is simply writing the image "on" the Sensor directly to SD. So the CPU is in idle all the time.
4: Same as 3. This would require much more processing power.
A user made a module that downsamples the raw data on the fly from 14 to 12/10 bit so there's a bit of hope :P
About USB, it would probably have an impact on the CPU usage of the camera but it's worth investigating in the future.
Quote from: dngrhm on May 22, 2013, 06:13:55 PM
UHS-I can either support a clock of 100MHz writing 4-bits (1/2 byte) per clock = 50 MB/s or UHS104 specifies a 208MHz clock writing 4-bits per clock = 104 MB/s. The SD controller in the T4i is a Macronix MX25L6436EM2I-10G with a clock speed of 104MHz. The T4i will not support anything faster than 50MB/s. Slice and dice your video however you want. That is the (theoretical maximum) hose you have to work with.
Actually, on a second inspection...that module does not look like a SD controller. It's just a 64Mb Serial flash
http://www.flickr.com/photos/78309769@N08/8790349631/
dont know if this is actual write speed proof due to it being a H264 stream but quicktime reads the data rate at 64.27mbps on the file straight from the camera.
ignore the current size, thats just the size of the video in the window not the actual video size.
footage is HDR video from a high street, lots of chroma and luma variation plus switching ISO values between frames with CBR +1.4 active.
Quote from: En veritas on May 23, 2013, 02:02:14 PM
http://www.flickr.com/photos/78309769@N08/8790349631/
dont know if this is actual write speed proof due to it being a H264 stream but quicktime reads the data rate at 64.27mbps on the file straight from the camera.
ignore the current size, thats just the size of the video in the window not the actual video size.
footage is HDR video from a high street, lots of chroma and luma variation plus switching ISO values between frames with CBR +1.4 active.
That's Mb/s. It's quite different from MB/s. One byte contains eight bits so 64.27 megabits per second is not the same as 64.7 megabytes per second.
Cheers
Quote from: VlastaS on May 23, 2013, 02:57:22 PM
That's Mb/s. It's quite different from MB/s. One byte contains eight bits so 64.27 megabits per second is not the same as 64.7 megabytes per second.
Cheers
Sorry i wasnt clear on what i meant. I understand the difference between bits and bytes when it comes to write speed. i am now wondering if 64 megabits per second is the maximum speed supported?
No, that's just the data rate of the codec.
Quote from: VlastaS on May 23, 2013, 03:32:32 PM
No, that's just the data rate of the codec.
yes i realise it is the data rate of the decoded stream.
I was just curious to know if that is the maximum data rate i will get from a H264 using ML on a 650D or if i need to increase the CBR settings or move into variable Q settings trials to get the best image quality.
thanks.
I think you guys need to implement IPB and ALL-I/etc to squeeze the most out of this camera. The settings for all that stuff are in EOS-M (so here too)... I haven't bothered since the raw recording though. By default its like digic IV H264.
all I frame recording would be most welcome to kill those annoying macroblocks.
RAW recording would also be great but to be honest just having a working pre alpha was more than i expected for the 650D with canon releasing a camera every 3 months!
Quote from: nanomad on May 23, 2013, 12:07:06 PM
Actually, on a second inspection...that module does not look like a SD controller. It's just a 64Mb Serial flash
... and that's why I'm not a HW guy :( I'm still convinced 50MB/s is the max for pumping out to the SD card. That still meets the UHS-I standard and that is what we are seeing on performance testing SD cards.
No, you're right.. you just pulled the wrong? datasheet. Look at the datasheet the SD chip connects to as well. There is a max mhz and from lookin the firmware its SDR50/DDR50 for sure. The MHZ matches up.
Quote from: 1% on May 23, 2013, 03:38:46 AM
Audio meter works on eos M while recording... it should work here too... but does not work at idle.
Is this currently in the M build or do you have to take out the #undef of AUDIO_METERS in features.h
I saw a version of video raw on forum. Is there anybody who can share it to me for testing? I know that it is unstable. I would like to ask about can a software destroy it?
I've got weird stuff with RAW recording on the 650D, including a semi-brick of the camera with the latest source code. I wouldn't use it
I can confirm this. Played too much with it and thought my cam is gone ???
Please be patient.
Quote from: multi.flexi on May 23, 2013, 10:56:34 AM
Few thoughts about RAW video:
1. Is it possible to use USB instead of SD card? Theoretically it is 60MB/s. Practically? And would PC or/and USB stick work?
2. One crazy thought: What about combining USB and SD card. For example odd frames would be stored on SD card and even through USB on USB stick or computer. And it would be combined in post-production similarly like HDR video.
3. Is it possible to shoot in RAW but only capture luminosity? Black & white picture would require lower bit rate.
4. Instead of using RAW would jpeg work better?
Thanks for your work. I am thankful user of pre-alpha 2.
Re: #4, what about implementing sRaw or mRaw for Raw video?
Could we downsample the RAW to 8 - bit? Would that be too much for the CPU to handle in real time? It wouldn't be as glitzy as 10 / 12 bit... But most of us that have prior experience with canon cameras (I've been shooting DSLR since 2009 on the t2i) know that the sensor in this camera is only capable of so much. If I remember correctly the c100 shoots 8-bit hd video in avchd 4:2:0, so in theory it doesn't sound so bad. This is baring in mind the special 8.1 MP sensor on the c100.
In theory this would set raw at 8 - bit per pixel (I believe), it seems to me that would be much more likely to support (near or at) HD/2k sizes in a raw continous stream. My math figures it would be below 40 MB/s which would allow a cieling so that Global Draw can be enabled during recording. As a bonus this might offer some really high frame rates to 5D mark III RAW, and maybe open the feature up to older cameras.
I know we don't even have proof of concept for the 12 / 10 bit yet, and I know the 650d still burns strange AF artifacts into the images. So those will definitely be the first and most time consuming. But, can someone tell me if this is an option?
Maths:
1924 pixels by 820 pixels = 1577680 pixels per raw image
Which would work out to 8 - bits or 1 byte per pixel resulting in 1.5046 MB per frame or
36.2 MB/s for what could be 24 fps scaled at 1920 x 820 2.34 : 1
Quote from: lordgnagey on May 24, 2013, 07:44:41 AM
Could we downsample the RAW to 8 - bit? Would that be too much for the CPU to handle in real time?
I'm not too knowledgable on this stuff, but I think that would defeat much of the purpose of shooting in RAW. You might still get extra sharpness and such, but the real advantage of RAW is the extra bits. Right?
Quote from: Gorilla on May 24, 2013, 09:07:57 AM
I'm not too knowledgable on this stuff, but I think that would defeat much of the purpose of shooting in RAW. You might still get extra sharpness and such, but the real advantage of RAW is the extra bits. Right?
I believe the real advantage of RAW is increased post production capabilities. Of course the higher bit count would be more desirable, but RAW compared to compressed at any bit count gives greater control in post.
Just based on numbers 36.2 MB/s is still way higher than any h264 compression would allow in terms of bitrate. Sharpness would not decrease dramatically as individual pixels are still being written into the raw. We might lose some dynamic range and some color depth (again I'm just theorizing here).
However, with the sensor in the t4i I feel 8-bit high res is better than 14 / 12 bit low res any day of the week. Not to mention it should cut down on the number of unusuable Magenta codec glitches that continue to appear in single frames. (some people say this is caused by a type of image buffer overrun?)
To bring back the main point, Nanomad and the rest of the ML team have some serious work ahead of them just trying to code out the af point burn in and making 650d raw video into a stable module.
The main reason I'm looking forward to RAW is dynamic range.
In the tests, what have you seen in terms of dynamic range? I've seen shots of the 5D3 and the range looks amazing, so how much of that trickles down to the 650d?
Hi,
I just installed this to my 650d but i couldn't make it to record hdr videos, is this feature disabled on alpha version?
http://ae.tutsplus.com/tutorials/production/a-simple-way-to-shoot-hdr-video-footage-using-magic-lantern/
i found this tutorial to record hdr vids, as you can see there, i need to change the firmware from noob mode to advanced mode. but it seems it is disabled on alpha right? no?
That tutorial is way old. We don't have "hidden" features anymore. HDR should be in the alpha, look closer inside menus
Quote from: midnite on May 24, 2013, 04:35:39 PM
Hi,
I just installed this to my 650d but i couldn't make it to record hdr videos, is this feature disabled on alpha version?
http://ae.tutsplus.com/tutorials/production/a-simple-way-to-shoot-hdr-video-footage-using-magic-lantern/
i found this tutorial to record hdr vids, as you can see there, i need to change the firmware from noob mode to advanced mode. but it seems it is disabled on alpha right? no?
It should be in the recycle bin menu under "Movie". Just press [Set] to enable/disable.
thanks for the answers, i just realized i need to set my iso setting manually. (it was set to auto) now i can record HDR videos. thanks all.
Quote from: midnite on May 24, 2013, 08:04:31 PM
thanks for the answers, i just realized i need to set my iso setting manually. (it was set to auto) now i can record HDR videos. thanks all.
This is a valuable resource for processing HDR video. Jump ahead in the video to 4:45 as he has a 5D Mark III. He made a couple of mistakes in his directions, one he says that avisynth opens first, but it's virtualdub that gets open. After virtualdub has separated the lights from the darks, then avisynth combines them and finally imports them into virtualdub where you need to set your framerate (unless you want 25fps) and set your compression, then save your avi from within virtualdub. There is a script file where you can change the fps default and the compression default so that you don't have to do it everytime. If you want to do this, set your framerate and compression then select file, export settings and name a file. Then go into that file and copy those lines into the \HDRWorkflow\scripts\hdr_join.vcf script file. Then you go to the frames folder and delete all the files there.
Or... Id you happen to use final cut like me, get the plugin and it will do it all for you.
Hello, I have been following this topic for a while, and recently was able to install ML on my T4i(thank you very much to everyone here btw :D) , and I have a couple questions that seem to still elude me. :-\
1. I have noticed that people have been asking about advanced bracketing, is this feature currently disabled or unavailable?
2. I have been messing around with the scripts, mainly the custom exposure one, and i have edited it thusly:
// Custom bracket sequence
console_hide();set_aperture(22);
set_iso(100);
set_shutter(1./2000);
takepic();
set_shutter(1./1000);
takepic();
set_shutter(1./500);
takepic();
set_shutter(1./250);
takepic();
set_shutter(1./125);
takepic();
etc.....
but any time i run this script it just takes a few pictures at 1/125??? what am i doing wrong here
i think that anyform of raw video in a canon rebel will push the camera and cinema industry to unknown levels.
is it possible that camera makers like sony or panasonic will stay quiet and decide to not implement camera raw in their cameras next year? i don´think so. they have to. it´s an obligation now that currently with a hack, canon has the upperhand at least at the midrange.
just hack one rebel one and things are going to get very entertaining in the industry.
just out of curiosity here! whenever that is, comes the next version. what is it gonna be prealpha 3 or alpha?
Quote
Raw & HDR video from CANON cameras - its a fake
Care to prove that?
Raw video from BMCC... its a fake.. buy red or alexa... its everything you need.
Quote from: 1% on May 25, 2013, 10:02:19 PM
Care to prove that?
Raw video from BMCC... its a fake.. buy red or alexa... its everything you need.
Red and Alexa are fake... buy a ARRI 35mm film camera :P
35mm is fake... buy large format like 102mm
Color is fake... buy a Revere Model 88.
Large format cameras are fake.... use your eyes :P (top that if you can LOL)
Alright jumping back to development now.
I'm shooting a short video on my cousin's RC drift car. We'll see how that turns out with ML's help.
Right now bitrate is set to 1.4x and results are looking good.
@kzi2006 - a reality check:-
The Black Magic Pocket Camera is a concept prototype until it is released.
The Black Magic Pocket Camera has a significantly smaller sensor than ALL Canon DSLRs
The Black Magic Pocket Camera's raw video ability is not proven and does not exist. It will not exist even when it is released (whenever that is?!)
The Black Magic Pocket Camera looks fucking amazing! (as a b-cam to a Canon 5dMkIII DSLR). I want one TOO, not instead of my DSLR.
I installed magic lantern and started playing with the FPS override with little success. I've managed 5 crashes so far, slow live view response, pink blown out areas in live view, static images of what appears to be noise in the resulting movie files and jumps in exposure after a second or so. Before I go off to find reproduction scenarios, I wanted to ask if this feature is SUPPOSED to be working?
someone can pass me the link to download ML for the 650D and a tutorial to install it?
Try post 1472 for installation links and instructions.
Quote from: rainman on May 26, 2013, 12:03:59 AM
Try post 1472 for installation links and instructions.
where is that? I did not understand
Each reply is numbered. Go back to page 59 and look for post 1471.
Could anyone send me the 650D-safe-dumper.fir?
Cuz i do not know why my downloading process always stuck at 22% (47.5KB/211KB) and i've tried several networks
Quote from: xanta on May 26, 2013, 11:31:40 AM
Could anyone send me the 650D-safe-dumper.fir?
Cuz i do not know why my downloading process always stuck at 22% (47.5KB/211KB) and i've tried several networks
sorry i didn't post my email address. By attachment PLZ!
[email protected]i'm a sophomore from China and i'm interested in the Magic Lantern working on 650D cuz i dont have spare money to buy aother upper class camera~~~~LOL
THX
I waited for almost 6hrs while downloading the 650D-safe-dumper.fir and now it's ready !
did it as the #1471? said
no extra heat no crush yet~~
thx for the help from the above Replies to the topic
i am quite a newbie here and haven't figured out how to use ML but im trying to learn!
ahahaha!
one little thing which im not sure whether it matters or not
at Video mode ,pushing the Trashcan button do get me to the ML menu but the EV bar(?dunno what to call it...)remains at the bottom of the display, i mean just the area which shows the EV overlay on the ML menu
not good at expressing myself clear in English, hope you guys can undestand me......
not a big deal is it?
Known issue but thanks for reporting it :)
;D ;D
YOU GUYS ARE THE BEST!
My first time trying to share files via dropbox so let me know if it didn't work. Here are 8 crash logs I've generated messing around with FPS override for the most part.
https://www.dropbox.com/s/9uvjfverjhw6h1b/MLCrashLogsMay26.zip?m
The crashs were caused by 2 assertion failures:
- ASSERT: !IS_ERROR(semErr) at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522
- ASSERT: 0 at Graphics.c:3580,
Not understanding how the LOG###.LOG files are being used, I'm not sure how valuable they are to assertion crashes but I've included them anyway. Can someone describe to me how the LOG###.LOG files are being used (I was a coder in a past life)? Is there enough context in the LOG*.LOG files to debug assertion failures or is more context needed to find the problem?
Thanks!
Same here, seems to me like the camera needs time to collect it self after a shooting a timelapse.
if leave it alone for a minute it comes back to normal, other wise i have to shut it off a few time to get the screen to show a live feed again.
ASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
ASSERT: 0
at Graphics.c:3580, task CtrlSrv
lv:0 mode:3
Here is a link to the logs/crash logs
http://www.yousendit.com/download/WFJYS3hkdEM5eFhtcXNUQw
can i activate Movie REC key in this prealpha?
i was trying to find it but it seems it lacks this feature. want to try if it´s possible to trigger video with a 603 younguo.
what should i do if i want to do things as nanomad?what do i need to be skilled in?C or any other programming language?
i major Electronic and Information Engineering and i learned something of C progranmming, is that enough?
Quote from: red5446 on May 27, 2013, 02:37:39 AM
can i activate Movie REC key in this prealpha?
i was trying to find it but it seems it lacks this feature. want to try if it´s possible to trigger video with a 603 younguo.
im not sure what a 603 younguo is but when i tried out this afternoon, it seemed the REC key halfshutter worked just fine
is that what you need?
Quote from: red5446 on May 27, 2013, 02:37:39 AM
can i activate Movie REC key in this prealpha?
i was trying to find it but it seems it lacks this feature. want to try if it´s possible to trigger video with a 603 younguo.
i tried to google it and figured out it is a wireless trigger,im not sure whether a wireless trigger works but if that still needs to be pluged in the jack on the side of the camera, it would work cuz i tried my wire trigger?cable trigger?(dunno what to call it for my poor vocabulary.....) just now.it worked and started recording video when i half push the shutter,
Quote from: xanta on May 27, 2013, 03:31:06 PM
i tried to google it and figured out it is a wireless trigger,im not sure whether a wireless trigger works but if that still needs to be pluged in the jack on the side of the camera, it would work cuz i tried my wire trigger?cable trigger?(dunno what to call it for my poor vocabulary.....) just now.it worked and started recording video when i half push the shutter,
i have this one :http://www.amazon.com/gp/product/B0050E7OSM/ref=oh_details_o00_s00_i02?ie=UTF8&psc=1 (http://www.amazon.com/gp/product/B0050E7OSM/ref=oh_details_o00_s00_i02?ie=UTF8&psc=1)
i want to try that but i can´t find the option in this prealpha.
what camera did you use? i have a 650d
Quote from: red5446 on May 27, 2013, 08:57:26 PM
i have this one :http://www.amazon.com/gp/product/B0050E7OSM/ref=oh_details_o00_s00_i02?ie=UTF8&psc=1 (http://www.amazon.com/gp/product/B0050E7OSM/ref=oh_details_o00_s00_i02?ie=UTF8&psc=1)
i want to try that but i can´t find the option in this prealpha.
what camera did you use? i have a 650d
same 650D. :)
i found the [REC key] under the MOVIE section, and set it to [halfshutter],and it worked, with a wired shutter trigger or just the shutter on the camera.
BUT i noticed that the instructions below says [Start recording by press shutter halfway. Wired remote]
@nanomad does that mean a wired remote works with this feature but a wireless one doesn't?
i guess there must be some difference of the operating principles between the wired and wireless remote/shutter trigger
Quote from: xanta on May 28, 2013, 04:06:33 AM
same 650D. :)
i found the [REC key] under the MOVIE section, and set it to [halfshutter],and it worked, with a wired shutter trigger or just the shutter on the camera.
BUT i noticed that the instructions below says [Start recording by press shutter halfway. Wired remote]
@nanomad does that mean a wired remote works with this feature but a wireless one doesn't?
i guess there must be some difference of the operating principles between the wired and wireless remote/shutter trigger
i just confirmed this.
it works ok wiressly!
nice :D
Quote from: red5446 on May 28, 2013, 04:34:37 AM
i just confirmed this.
it works ok wiressly!
nice :D
Congrats~
Hey guys, cheers for all the great work.
I think there may be a bug, when you flip the screen round so that is facing the same way the lens is, (for self shooting) the magic lantern overlay is mirrored vertically!
Is this a known issue?
Yes and fixed in the repository already ;)
Notifications are disabled right now because we were sending too many emails.
the Histogram shows up above video mode or LiveView
just like what i said about the EV bar before
Should be fixed in the repository too, I'll check it though
With this application the camera 650d is able to shoot video in RAW format such as 5d mark III ?
Well, up to 1280x560 pixels
awesome!!!!
Quote from: nanomad on May 28, 2013, 09:58:11 PM
Well, up to 1280x560 pixels
Does that mean RAW video is not semi-bricking cameras now?
Thanks for all the work! It's amazing that the 650D can support RAW at any res!
So where exactly can I find these new builds? I've been wanting to try out RAW and the other various features but the main Nanomad filesystem doesn't seem to have them.
Also on a side note: has ML.fm been loading slowly for anyone else?
Hi All,
Maximum Read and Write is at 33mb/s on a 64GB Class 10 which should be able to transfer at 95MB/s.
Quote from: papkee on May 28, 2013, 10:48:40 PM
So where exactly can I find these new builds? I've been wanting to try out RAW and the other various features but the main Nanomad filesystem doesn't seem to have them.
You need to compile build from a last source or you can feel free an use build compiled by me here (https://www.dropbox.com/sh/q1zrrlmy03psr2y/F3PR9UwMWZ).
Set a boot flags an your SD and extract zip to SD. Works very well.
And please diligently and extensively report the bugs ;)
Quote from: arne182 on May 28, 2013, 11:17:06 PM
Hi All,
Maximum Read and Write is at 33mb/s on a 64GB Class 10 which should be able to transfer at 95MB/s.
8 bits (b) = 1 Byte (B) Minimum performance for Class10 (according to http://en.wikipedia.org/wiki/Secure_digital#Speed_Class_Rating (http://en.wikipedia.org/wiki/Secure_digital#Speed_Class_Rating)) is 10MB/s. 33Mb/s would be equivalent to ~4MB/s. Likely the Max Read/Write benchmark you are referring to is 33MB/s which is not 95MB/s.
I have always found the whole class rating and 100x and other marketing crap of SD cards to be highly confusing. I have to look it up every time I'm shopping for a new one.
Quote from: satriani on May 28, 2013, 11:44:45 PM
You need to compile build from a last source or you can feel free an use build compiled by me here (https://www.dropbox.com/sh/q1zrrlmy03psr2y/F3PR9UwMWZ).
Set a boot flags an your SD and extract zip to SD. Works very well.
And please diligently and extensively report the bugs ;)
testing here
Achieving 200 frames at 1280x720
34MB/s with my 45MB sandisk. :P
all other ML things turned off (zebras, focus peaking etc)
below that i can record without problems.
higher than that i can only do like between 2 seconds and 4 seconds. the best i can top it´s like 45MB
what´s the best workflow with this raw?
can anybody share some good tutorial :)
(http://img7.imageshack.us/img7/4457/000110uo.jpg)
Why i always get these horrible photos every time i record in RAW whatever the resolution is ? :o
(http://img801.imageshack.us/img801/8568/000025cv.jpg)
I changed the resolution but still have this weird dots, Any solutions ?
Quote from: satriani on May 28, 2013, 11:44:45 PM
You need to compile build from a last source or you can feel free an use build compiled by me here (https://www.dropbox.com/sh/q1zrrlmy03psr2y/F3PR9UwMWZ).
Set a boot flags an your SD and extract zip to SD. Works very well.
And please diligently and extensively report the bugs ;)
thank you kindly, installed just fine ;)
(the build i was using was missing a few features, namely bracketing)
reporting again~~~~
i tried the RAW feature under 1280*720, skipped one frame every 300 frames,and the speed is around 35MB/s, sandisk U-1,45MB/s,im not sure weather the card speed is enough, a U-1 should be 45MB/s shouldn't it?
i transferred the raw to dng sequence and imported to after effects
but in each frame there is a strange area of redish grain, and its in the certain position of the picture and doesn't move with the stuff inside the picture
how do i upload my picture?
Quote from: satriani on May 28, 2013, 11:44:45 PM
You need to compile build from a last source or you can feel free an use build compiled by me here (https://www.dropbox.com/sh/q1zrrlmy03psr2y/F3PR9UwMWZ).
Set a boot flags an your SD and extract zip to SD. Works very well.
And please diligently and extensively report the bugs ;)
i just tried your build. thanks for the compile.
bugs:
1. one crash when i set the picture style in magic lantern menu, (the camera goes crazy)
ASSERT: 0
at ./Capture/Capture.c:509, task EventMgr
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013May28.650D101
Mercurial changeset : 87906563dde1 (unified) tip
Built on 2013-05-28 11:44:35 by root@magiclantern-VirtualBox.
Free Memory : 106K + 3457K
2. when i turned the lcd the face tracking focus is mirrored (only with magic lantern)
and for RAW video
1280x720: goes until 271 frames with a sandisk 45MB/s
1728x972: 38 frames
1440x810:83 frames
1320x742: 112
aspect ratio 3:2
1728x1152: 24 frames
1600x1066:38 frames
1440x960: 46
1280x854:103
aspect ratio 1.1
960x960: 373
1280x1158:43
aspect ratio: 2.35:1
1728x736:65 frames
aspect ratio 3:1
1728x576: 159 frames
and the most important thing: for now every raw video i shot gives this pattern of dots:
(http://i42.tinypic.com/mwvcdj.jpg)
https://www.dropbox.com/s/my5dhhadihgdd4x/Comp%20%280-00-07-29%29.jpg(https://www.dropbox.com/s/my5dhhadihgdd4x/Comp%20%280-00-07-29%29.jpg)
The pattern is something I am working on. I'll probably provide a test build that dumps a couple of raw frames with different settings to decide which one looks better
About screen being mirrored : there's a setting n ML menu that changes that behavior :D
And the speed you're getting are fine. The controller isn't that good
Quote from: nanomad on May 29, 2013, 07:27:58 AM
The pattern is something I am working on. I'll probably provide a test build that dumps a couple of raw frames with different settings to decide which one looks better
About screen being mirrored : there's a setting n ML menu that changes that behavior :D
And the speed you're getting are fine. The controller isn't that good
So there is no chance of getting higher res of RAW becuz of the controller?
Unless someone figures how to get 12/10 bit raw and assuming it will somehow help
Quote from: nanomad on May 29, 2013, 10:12:33 AM
Unless someone figures how to get 12/10 bit raw and assuming it will somehow help
i thought the 14bit is too much for me actually even if it is quite good for professional work. but, not necessary for me
I'm not sure how Nanomad feels on this, but this thread is for testing the public pre-Alpha 2, not a privately compiled build. Posting bugs on own-compiled things is sort of irrelevant when the current pre-alpha has been released. I would think a better way of discussing the current changes to ML would be through PM or on the IRC.
Also, it's worth noting that having props disabled, which enables all the stuff in ML, is potentially dangerous as that's mainly where the bugs haven't been ironed out.
This stage of prealpha, nanomad/devs has probably long since completed.
Maybe this is better for him that people can test the latest changes, detect and report the bugs.
But a developer has to decide themselves.
Typically, a developer will not release source until he has tested them.
I speak from experience because I'm a paranoid developer and treat my source very carefully ;D
I'm fine with people posting builds. It's free software, you can do whatever you want with the source code :P.
As I said, I've got the raw video pixels thing to sort out before I'll relase anything myself but feedbacks and bug reports are more than welcome. Just remember to state the commit the binary is based on (you can see it inside the debug menu)
@satriani:
your build enables the hdr bracketing for more expos?
and if yes, this build can bricked my camera?
most exciting thing for me the hdr bracketing, but this one missed for prealpha :)
but i dont want a brick :)
As a general rule:
***************************************************
* *
* THIS IS DANGEROUS AND MIGHT DAMAGE YOUR CAMERA. *
* NO WARRANTIES. NO GUARANTEES. DO NOT TAUNT. *
* *
***************************************************
If you are not comfortable with this, stop reading and delete the
software before you are tempted to try running it on your camera.
Please read the user guide carefully before installing this software.
To repeat this important point:
***************************************************
* *
* THIS IS DANGEROUS AND MIGHT DAMAGE YOUR CAMERA. *
* IF IT BREAKS, YOU GET TO KEEP BOTH PIECES. *
* *
***************************************************
Excuse me, but why the 29 may version doesn't boot up? I put it in my camera, but it doesn't allow to boot up. Can turn on my camera after removng SD card and battery. The first version of ml 650d is working on other card, any solution? And it boots up without card.
Which may 29th version?
Don't just state the date, link the download too.
And no, "official" nightly builds don't work on the 650D... there's no 650D in the file name.
Oh, sorry didn't notice about that it is missing 650D, that must be the problem, is there any newer version for 650d than the first one? I had one, but i've lost it. It was posted in this topic, but i can't find it anymore.
Quote from: Emiils on May 29, 2013, 05:30:45 PM
Oh, sorry didn't notice about that it is missing 650D, that must be the problem, is there any newer version for 650d than the first one? I had one, but i've lost it. It was posted in this topic, but i can't find it anymore.
the one i believe to be "official" from @nanomad is from #1472, but there was no RAW yet
now im using the compiled build from @Sariani with RAWVIDEO
which is from the group?or both ?
Quote from: xanta on May 29, 2013, 06:10:22 PM
the one i believe to be "official" from @nanomad is from #1472, but there was no RAW yet
now im using the compiled build from @Sariani with RAWVIDEO
which is from the group?or both ?
How is that build working? Does FPS overide work, hdr bracketing?
What does work and what does not work?
Quote from: xanta on May 29, 2013, 06:10:22 PM
the one i believe to be "official" from @nanomad is from #1472, but there was no RAW yet
now im using the compiled build from @Sariani with RAWVIDEO
which is from the group?or both ?
In that which i were using there wasn't Raw could someone please provide me last version before RAW? That would be realy nice. In that version which i were using there were like small icons near options which shows like magic zoom loction or other thing place or so,ething associated with that feature. That was really usefull. Sorry for mistakes.
Quote from: Aborgh on May 29, 2013, 06:13:04 PM
How is that build working? Does FPS overide work, hdr bracketing?
What does work and what does not work?
most of the features work fine BUT operating with ML settings under Liveview mode may cause a crash,just remove the battery and the card then wait a moment it'll be ok
the RAW video recording could be set to around 1732*1150 or some values else but was limited to 1280*720 to work just ok with 1 skipped within every 300 frames on a sandisk 45MB/s SD card
you can check the detailed test carried out by someone above
i will update some other reports when i come back
Quote from: Emiils on May 29, 2013, 06:49:32 PM
In that which i were using there wasn't Raw could someone please provide me last version before RAW? That would be realy nice. In that version which i were using there were like small icons near options which shows like magic zoom loction or other thing place or so,ething associated with that feature. That was really usefull. Sorry for mistakes.
you mean prealpha2 without RAW?
try this that i found #1472
https://www.dropbox.com/s/zr0uki4jrxqsrl0/magiclantern-v2.3.NEXT.2013Apr30.650D.PreAlpha2.zip
Nop, that isn't the correct version. There were small icons beside features which showed like location and that stuff, it was very usefull, it was newer version than this. Could you provide the RAW version, that would be really good.
You mean probably this menu
(http://s18.postimg.org/4n7mmjca1/VRAM4.png)
this work fine with the compiled builds, just press the menu button while you are in ML menu.
Take a look to my signature ;)
Hey guys, been testing Satriani's build and I have some notes...
2.35:1 1440 x 614 23.973fps recording with NO skipped frames at all... That is, until I hit the 4.29 gb barrier. ;) This is with Overlays off and sound options disabled.
Other than the artifacts (which can be hidden/corrected to a degree) it's looking really great! Moire is a nightmare still, but the rainbow swirls can be fixed pretty easily. I've been processing the files into video just to get familiar with the workflow. Using Photoshop to grade and DaVinci Resolve for final polish and convert into 1080p ProRes.
This was done using 16gb UHS-I 95MB/s Sandisk Extreme cards.
Quote from: lordgnagey on May 30, 2013, 06:05:49 AM
Hey guys, been testing Satriani's build and I have some notes...
2.35:1 1440 x 614 23.973fps recording with NO skipped frames at all... That is, until I hit the 4.29 gb barrier. ;) This is with Overlays off and sound options disabled.
Other than the artifacts (which can be hidden/corrected to a degree) it's looking really great! Moire is a nightmare still, but the rainbow swirls can be fixed pretty easily. I've been processing the files into video just to get familiar with the workflow. Using Photoshop to grade and DaVinci Resolve for final polish and convert into 1080p ProRes.
This was done using 16gb UHS-I 95MB/s Sandisk Extreme cards.
Could you plz upload a ref picture of you RAW?
THX
Note: You can use the raw2dng tool to process RAW videos. (https://bitbucket.org/hudson/magic-lantern/downloads/RAw2dng.exe)
You will need to download the 2 programs it needs and set up your PATH settings as well.
[http://www.magiclantern.fm/forum/index.php?topic=5404.0]
Well I'm at work right now. I can upload the videos and/or some reference raw when I get home.
Go ahead. ;)
Here's an early test. It's a 1600 x 540 3:1 (if memory serves) and sorry it got downsampled to 720p (I hate QuickTime presets). Ill have a more interesting full 1080p stream later tonight. Plus plenty of reference DNGs.
As a reference this is California sunrise at around 7:30am... Very bright but you can see the details both inside and outside.
http://www.youtube.com/watch?v=bnkeaINBd4s&sns=em
Edit: I promise the next upload won't be as ugly. :P
Quote from: lordgnagey on May 30, 2013, 07:01:27 AM
Here's an early test. It's a 1600 x 540 3:1 (if memory serves) and sorry it got downsampled to 720p (I hate QuickTime presets). Ill have a more interesting full 1080p stream later tonight. Plus plenty of reference DNGs.
As a reference this is California sunrise at around 7:30am... Very bright but you can see the details both inside and outside.
http://www.youtube.com/watch?v=bnkeaINBd4s&sns=em
Edit: I promise the next upload won't be as ugly. :P
that sequence seems fine despite the moire~~
looking forward to seeing your next one, IF the 650D can do a real 1080P RAW that would be fantastic~
You can get rid of the moire by using raw_rec with the 5X zoom in movie mode, which basically gives you the good old "crop zoom mode" of the 600D
Quote from: lordgnagey on May 30, 2013, 07:01:27 AM
Here's an early test. It's a 1600 x 540 3:1 (if memory serves) and sorry it got downsampled to 720p (I hate QuickTime presets). Ill have a more interesting full 1080p stream later tonight. Plus plenty of reference DNGs.
As a reference this is California sunrise at around 7:30am... Very bright but you can see the details both inside and outside.
http://www.youtube.com/watch?v=bnkeaINBd4s&sns=em
Edit: I promise the next upload won't be as ugly. :P
How do you change the resolution on raw video?
Sorry but I think I'm foolish because I can't pass the program to camera....
xaxa
Quote from: Aborgh on May 30, 2013, 01:34:22 PM
How do you change the resolution on raw video?
Q button is for further settings of the feature, try it
Quote from: xanta on May 30, 2013, 01:54:03 PM
Q button is for further settings of the feature, try it
When I go in silent picture I can only choose Simple , burst , burst en trigger , best shots and slit-scan. Am I missing something here?
Quote from: Aborgh on May 30, 2013, 03:24:45 PM
When I go in silent picture I can only choose Simple , burst , burst en trigger , best shots and slit-scan. Am I missing something here?
Raw is a completely separate module. You need a build with the raw_rec module. Either compile the source yourself or use a satriani build. (This is alpha territory. If you can't live with a bricked camera, don't do it. If you do and experience a lockup where your camera or ML don't respond, remove your battery immediately to stop all processes and prevent your camera from overheating)
Once you have the correct ML installed on the SD card. Open the ML menu and there should be a new "M" menu. Select load modules under the "M" menu. Raw rec will then appear under video.
Quote from: dngrhm on May 30, 2013, 03:40:54 PM
Raw is a completely separate module. You need a build with the raw_rec module. Either compile the source yourself or use a satriani build. (This is alpha territory. If you can't live with a bricked camera, don't do it. If you do and experience a lockup where your camera or ML don't respond, remove your battery immediately to stop all processes and prevent your camera from overheating)
Once you have the correct ML installed on the SD card. Open the ML menu and there should be a new "M" menu. Select load modules under the "M" menu. Raw rec will then appear under video.
Thanks man it works! But how to open the files in a computer? Do you know any converting software?
Nevermind! Found a whole thread about this :P
So does anyone out there have a comparison of the standard T4i HD video, versus the RAW video?
I'm an actor, still learning more about the technical side of the business, going to try and do some of my own shorts at some point, so don't flame me for this question. I learn better visually instead of reading about luminance values and raw data.
Now that someone has made the very beginning version of it available on the T4i, I am just curious what that looks like. I get that the idea is that it's the raw data from the sensor, and there is no compression or processing of WB or anything from the camera, but what sort of image will that get vs the standard.
Great work to everyone. If I was still back in high school years ago cracking away at ansi C, I'd try and pitch in, but I've mostly forgotten.
Except for printf().
Quote from: lordgnagey on May 30, 2013, 07:01:27 AM
Here's an early test. It's a 1600 x 540 3:1 (if memory serves) and sorry it got downsampled to 720p (I hate QuickTime presets). Ill have a more interesting full 1080p stream later tonight. Plus plenty of reference DNGs.
As a reference this is California sunrise at around 7:30am... Very bright but you can see the details both inside and outside.
http://www.youtube.com/watch?v=bnkeaINBd4s&sns=em
Edit: I promise the next upload won't be as ugly. :P
How did you get rid of the red lines?
Quote from: 33black on May 30, 2013, 07:52:09 PM
I get that the idea is that it's the raw data from the sensor, and there is no compression or processing of WB or anything from the camera, but what sort of image will that get vs the standard.
Someone else will be able to give a better answer than this, but basically the raw video would probably give you an image that is sharper, contains very little to no noise reduction, has less banding, and has a greater dynamic range.
Quote from: Aborgh on May 30, 2013, 01:34:22 PM
How do you change the resolution on raw video?
By adjusting the raw_rec module. There is a section to select aspect ratio and another for choosing horizontal resolution.
if useful i have some crash logs:
currently using the build of satriani.
works ok. but be careful i got a semibrick or err (i dont remember what number i just pull of the battery and all is allright)
if i use 24fps over ride i can obtain 600+ frames of 1280x720. That´s 3x times what i get the normal way. But it crashes if i choose other any option than optimized for low light.
1crash
QuoteASSERT: 0
at ./Capture/Capture.c:509, task EventMgr
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013May28.650D101
Mercurial changeset : 87906563dde1 (unified) tip
Built on 2013-05-28 11:44:35 by root@magiclantern-VirtualBox.
Free Memory : 106K + 3457K
2. crashes
QuoteASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013May28.650D101
Mercurial changeset : 87906563dde1 (unified) tip
Built on 2013-05-28 11:44:35 by root@magiclantern-VirtualBox.
Free Memory : 106K + 3433K
2 crashes
QuoteASSERT: !IS_ERROR(semErr)
at ./EekoApp/Color/WB/LV/LvWbAlgorWrap.c:522, task CLR_CALC
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013May28.650D101
Mercurial changeset : 87906563dde1 (unified) tip
Built on 2013-05-28 11:44:35 by root@magiclantern-VirtualBox.
Free Memory : 106K + 3464K
assert log for all crashes:
QuoteML ASSERT:
PROP_LEN(206000a) correct:4 called:18
at ../../src/property.c:308 (prop_request_change), task GuiMainTask
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013May28.650D101
Mercurial changeset : 87906563dde1 (unified) tip
Built on 2013-05-28 11:44:35 by root@magiclantern-VirtualBox.
Free Memory : 106K + 3463K
LOG000.LOG
QuoteWed May 29 04:47:30 2013
0: 33.238 [STARTUP]
K301 ICU Firmware Version 1.0.1 ( 5.5.9 )
1: 33.271 [STARTUP]
ICU Release DateTime 2012.05.24 17:48:32
2: 35.259 [SEQ] seqEventDispatch (Startup, 0)
3: 35.286 [STARTUP] startupEntry
4: 35.367 [PROPAD] PROPAD_CreateFROMPropertyHandle DRAMAddr 0x42000000
5: 36.066 [PROPAD] SerialFlash Packages!! 0x10000
6: 46.584 [STARTUP] InitializeIntercom
7: 46.839 [STARTUP] InitializeIntercom End(0x0)
8: 95.605 [PROPAD] SerialFlash Packages!! 0x7
9: 96.266 [PROPAD] SerialFlash Packages!! 0x340000
10: 125.867 [PROPAD] SerialFlash Packages!! 0x7
11: 125.963 [STARTUP] startupPropAdminMain : End
12: 126.026 [SEQ] seqEventDispatch (Startup, 1)
13: 126.055 [STARTUP] startupPrepareProperty
14: 127.855 [SEQ] seqEventDispatch (Startup, 2)
15: 128.284 [RSC] hMemoryQueue (0x980010) hStorageQueue (0x9A0012)
16: 129.522 [RSC] ### LIST 6 0 6 ###
17: 141.284 [JOB] InitializeJobClass (ID = 5592, Num = 13)
18: 143.279 [EM] emLockControl (TYPE_JOBSTATE = 0x0)
19: 145.193 [JOB] InitializeInnerDevelopJobClass (ID = 5592, Num = 16)
20: 145.224 [JOB] InitializeHDRShootJobClass ( Num = 12 )
21: 145.249 [JOB] InitializeHDRSaveAndEndJobClass ( Num = 32 )
22: 145.273 [JOB] InitializeGISShootJobClass ( Num = 12 )
23: 145.300 [JOB] InitializeGISSaveAndEndJobClass ( Num = 26, 32 )
24: 147.713 [RTC] ChangePropertyCBR 0x0, 0x0
25: 148.106 [RTC] RTC_Permit 0x20
26: 149.149 [RTC] InitializeRTCDriver 0x20, 0xff1306dc
27: 149.898 [DOS]threshold 0x37a 0x35c
28: 154.482 [SND] Seq LPC fin
29: 154.845 [SHTRD] [MNAV] MEMNAVI_Initialize
30: 155.132 [SHTRD] [MNAV] MEMNAVI_SetMemoryMap: 1
31: 157.095 [ENG] [ENGIO](Addr:0x41400000, Data:0x 44000)
32: 160.928 [ENAV] EEKO_NAVI_Initialize[START]
33: 161.255 [ENAV] EekoNavi_InitializeEekoSystem
34: 161.313 [ENAV] EEKO_NAVI_Initialize[FINISH]
35: 194.267 [ENAV] Eeko Initialized:Async
36: 194.343 [SHTP] spsInit
37: 211.330 [FM] FM_RegisterSpaceNotifyCallback
38: 211.365 [MRK] MRK_RegisterSpaceNotifyCallback
39: 211.433 [FM] FM_RegisterSpaceNotifyCallback
40: 211.598 [TERMINATE] SHUTDOWN init comp
41: 211.652 [TERMINATE] Abort init comp
42: 214.682 [MC] PROP_GUI_STATE 0
43: 214.935 [MC] JobState 0
44: 215.720 [MC] PROP_VARIANGLE_GUICTRL : Enable
45: 215.780 [MC] [MC] PROP_HEADPHONE_VOLUME_VALUE : 0
46: 215.906 [MC] [MC] PROP_MOVIE_PLAY_VOLUME : 9
47: 216.873 [MC] regist master CardCover
48: 557.153 [SD] sdSendOCR: 1.8V Signaling Card
49: 558.375 [SD] sdSendOCR: Hi-Capacity Card
50: 566.787 [SD] Set 1.8V Signaling
51: 601.640 [SD] CARD CAPACITY is 30436Mbyte( 62333952Sec )
42: 214.682 [MC] PROP_GUI_STATE 0
43: 214.935 [MC] JobState 0
44: 215.720 [MC
Benchmarks with a sandisk 45MB/s
(http://i42.tinypic.com/auhafl.jpg)
Please anyone with a 95MB/s make a benchmark a post it, will be helpful to see what buffer are better and if by any chance there is at least 10MB more of performance over a 45MBs :)
Quote from: Aborgh on May 30, 2013, 07:59:10 PM
How did you get rid of the red lines?
Color and Luminance noise reduction in photoshop. But they do appear to degrade the image when turned up too high. In the future uploads this apparition will probably be more pronounced, but only to retain detail in the resulting video.
I've got an extreme pro 95mb/s. I'll have to play around with this today.
Downloading a build now. :)
Okay, videos are processing now.
So far with a SanDisk Extreme Pro 16gb 95mb/s card the max I've been able to use RAW-wise has been 1440 at 2.35:1 with sound off. Anything higher uses up the buffer and recording stops within 100 frames. So overall not bad. If we can ever figure out how to downsample to 10bit in-camera we may have some very usable footage soon.
Will be posting test videos later today.
Quote from: red5446 on May 30, 2013, 10:52:33 PM
if useful i have some crash logs:
currently using the build of satriani.
works ok. but be careful i got a semibrick or err (i dont remember what number i just pull of the battery and all is allright)
if i use 24fps over ride i can obtain 600+ frames of 1280x720. That´s 3x times what i get the normal way. But it crashes if i choose other any option than optimized for low light.
1crash2. crashes2 crashes
assert log for all crashes:
LOG000.LOG
Benchmarks with a sandisk 45MB/s
(http://i42.tinypic.com/auhafl.jpg)
Please anyone with a 95MB/s make a benchmark a post it, will be helpful to see what buffer are better and if by any chance there is at least 10MB more of performance over a 45MBs :)
UHS-I only appears to be useful when UHS is usable by the cardbus...
(http://i.imgur.com/svzbxPZ.png)
I'm only getting 37.9MB/s MAX! I've tried this with and without Global Draw enabled and I get the same result.
:( It literally hits a cieling. what card do you use? Is it this one:
http://www.amazon.com/SanDisk-Extreme-Pro-SDHC-SDSDXP1-032G/dp/B004JJQN8G/ref=pd_sim_pc_1
Quote from: lordgnagey on May 31, 2013, 12:27:48 AMI'm only getting 37.9MB/s MAX! I've tried this with and without Global Draw enabled and I get the same result.
:( It literally hits a cieling.
Benchmark results seem to differ in photo and video mode ...
Sandisk 95 MByte/s, 8 GByte
I use this build:
https://dl.dropboxusercontent.com/sh/q1zrrlmy03psr2y/NoRx3aSzTl/ML_N_28.05.2013.zip
(http://image-upload.de/image/OsYaYs/ce46d6e0bd.jpg)
(http://image-upload.de/image/K7RjST/4f2b69e81b.jpg)
10 MByte/s more would be fine, but it seems the controller is the bottleneck.
Ciao, Walter
Quote from: Walter Schulz on May 31, 2013, 01:43:46 AM
Benchmark results seem to differ in photo and video mode ...
Sandisk 95 MByte/s, 8 GByte
I use this build:
https://dl.dropboxusercontent.com/sh/q1zrrlmy03psr2y/NoRx3aSzTl/ML_N_28.05.2013.zip
(http://image-upload.de/image/OsYaYs/ce46d6e0bd.jpg)
(http://image-upload.de/image/K7RjST/4f2b69e81b.jpg)
10 MByte/s more would be fine, but it seems the controller is the bottleneck.
Ciao, Walter
looks like with a t4i it´s best to get a 45MB/s card because with a 95MB/s you don´t get better performance at all.
anyways it will be cool to know if t5i has the same limitation.
i think at least 10MB/s more will get the job done for 1280x720
Quote from: red5446 on May 31, 2013, 02:48:18 AM
looks like with a t4i it´s best to get a 45MB/s card because with a 95MB/s you don´t get better performance at all.
anyways it will be cool to know if t5i has the same limitation.
i think at least 10MB/s more will get the job done for 1280x720
I'm sorry my first response was off, I misread your post. You're right, buying a UHS-I 95MB/s card is pointless if you are only using it on the T4i...
HOWEVER future UHS-I compliant devices will more than likely take advantage of the more than double speed increase from the 45 to the 95 cards. The prices aren't that different, so I say why not future proof your cards?
i have this one 2013/05/10 hope u looking for this
https://docs.google.com/file/d/0B0TZGuUZQ-_ZX2VPdXNvY2dLV2s/edit?usp=sharing
https://vimeo.com/67355212
I had to compress it pretty heavily to get it to upload, but the ProRes 422 file is about 1 gig. I've put the ProRes file on Dropbox and it should be able to view later, I'll update this post with the link when finished.
I'm going to wait until we figure out whether or not the color apparition can be dealt with in camera before I do too much more with RAW video.
Quote from: lordgnagey on May 31, 2013, 05:25:46 AM
https://vimeo.com/67355212
I had to compress it pretty heavily to get it to upload, but the ProRes 422 file is about 1 gig. I've put the ProRes file on Dropbox and it should be able to view later, I'll update this post with the link when finished.
I'm going to wait until we figure out whether or not the color apparition can be dealt with in camera before I do too much more with RAW video.
That one was great! i wonder what SDcard you used for this, and is there any frame skipped?
i have my own 650D tested but the res must be set to 1280*720 so that it will not skip frames too soon
another problem i have now is the strange red and blue dots on the picture as i posted before
ahhhhh, the strange dots is killing me.......i wish i can help but i have almost forgot what i learned about C programming
Quote from: xanta on May 31, 2013, 10:25:55 AM
That one was great! i wonder what SDcard you used for this, and is there any frame skipped?
i have my own 650D tested but the res must be set to 1280*720 so that it will not skip frames too soon
another problem i have now is the strange red and blue dots on the picture as i posted before
I used a SanDisk Extreme Pro 95MB/s
Red and blue dots are part of the colorful apparition that I have been complaining about. They are burned into the image sadly, Nanomad is trying to clear these up. I have to use Color and Luminance noise reduction in photoshop which seriously degrades the detail of the image.
No frames skipped.
Quote from: lordgnagey on May 31, 2013, 11:20:41 AM
I used a SanDisk Extreme Pro 95MB/s
Red and blue dots are part of the colorful apparition that I have been complaining about. They are burned into the image sadly, Nanomad is trying to clear these up. I have to use Color and Luminance noise reduction in photoshop which seriously degrades the detail of the image.
No frames skipped.
what about the writing speed while recording? i am using a Sandisk Extreme 45MB/s card and the writing speed is 34-35MB/s, under 1280*720 frames were skipped at about 300th frame then it keeps skipping, but if i use a 1280*692(1.85:1) then no frames were skipped
Hi,
Can someone give me link of ML with rawVid? I cant find it in posts.
Thanks!
@erka: Reply #1694
Quote from: xanta on May 31, 2013, 11:27:41 AM
what about the writing speed while recording? i am using a Sandisk Extreme 45MB/s card and the writing speed is 34-35MB/s, under 1280*720 frames were skipped at about 300th frame then it keeps skipping, but if i use a 1280*692(1.85:1) then no frames were skipped
Write speed was estimated at 35.2MB/s. It labored around 33-36 and usually didn't spike any higher. I really wish we could max out the 50MB/s write speed, or even come close to 45... That would add a world of new resolution options.
However 1440 : 614 at 2.35:1 Is an acceptable option in my eyes. It's viewable angle isn't quite 2-perf Techniscope however it is still a tad larger than M4/3.
M4/3 2.35 - 17.30mm x 7.36mm
1440raw 2.35 - 18.24mm x 7.75mm
Techniscope 2.33 - 22.00mm x 9.47mm
Quote from: lordgnagey on May 31, 2013, 12:17:40 PM
Write speed was estimated at 35.2MB/s. It labored around 33-36 and usually didn't spike any higher. I really wish we could max out the 50MB/s write speed, or even come close to 45... That would add a world of new resolution options.
However 1440 : 614 at 2.35:1 Is an acceptable option in my eyes. It's viewable angle isn't quite 2-perf Techniscope however it is still a tad larger than M4/3.
M4/3 2.35 - 17.30mm x 7.36mm
1440raw 2.35 - 18.24mm x 7.75mm
Techniscope 2.33 - 22.00mm x 9.47mm
my card speed is the same performance as your 95 on 650D, i tried your 1440*614 and there is no skipped frames too
but the recording may stop itself automatically and suddenly, not because of the buffer is full, the screen is off and the reflex is closed, i can here that click sound, could you understand what i mean? and when i dump the RAW file to the raw2dng.exe the cmd window flashed and showed me nothing, i mean the raw2dng couldn't process the suddenly-stopped raw file
Hi lads, what funtions are working safely on the pre alpha that is linked on page 59?? I would be hoping to use the kelvin temperature setting, cropmarks and the histograms and some other funtions from the overlay menu. magic zoom.. vectorscope. all that jazz. Great work with the RAW video aswell I hope the developers get the results the are looking for, and thanks for the time and hard work you are all putting in to this.
It has. Go to "Modules" (last tab to the right) -> Load modules now
Now return to "Movie" and look at the bottom of the list.
Ciao, Walter
Quote from: Walter Schulz on May 31, 2013, 02:09:45 PM
It has. Go to "Modules" (last tab to the right) -> Load modules now
Now return to "Movie" and look at the bottom of the list.
Ciao, Walter
thnx bro. can any one focus audio recording. i think its so important than raw videos. raw is important too bt audio is a must
Hey guys,
to be always up to date, use the "Daily compiled builds from the last ML source" (https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0) or take a look to my signature. The compilation occurs automatically on my server, then tested on my camera and published.
I will try my best to upload every day. And please don't forget guys, always to report the bugs ;)
Quote from: xanta on May 31, 2013, 12:56:27 PM
my card speed is the same performance as your 95 on 650D, i tried your 1440*614 and there is no skipped frames too
but the recording may stop itself automatically and suddenly, not because of the buffer is full, the screen is off and the reflex is closed, i can here that click sound, could you understand what i mean? and when i dump the RAW file to the raw2dng.exe the cmd window flashed and showed me nothing, i mean the raw2dng couldn't process the suddenly-stopped raw file
If your camera auto shuts off during recording of a ML RAW video, the recording is lost. There is a footer that is written when the recording is stopped. If ML doesn't get a chance to write this footer to the file, raw2dng has no clue what is in the file (no frame size, no frame count, ...) The file is lost unless someone has a raw2dng that you can input the necessary info manually (which I don't think exists).
Quote from: xanta on May 31, 2013, 12:56:27 PM
my card speed is the same performance as your 95 on 650D, i tried your 1440*614 and there is no skipped frames too
but the recording may stop itself automatically and suddenly, not because of the buffer is full, the screen is off and the reflex is closed, i can here that click sound, could you understand what i mean? and when i dump the RAW file to the raw2dng.exe the cmd window flashed and showed me nothing, i mean the raw2dng couldn't process the suddenly-stopped raw file
You probably hit the card capacity or the file limit 4.29gb, I'd bet on the latter. Sad thing is I can't see any way of easily recovering that data. You have to watch your GB size with raw_rec. It's very early yet in its development.
But yes keep under that limit and you'll be fine.
Quote from: satriani on May 31, 2013, 03:20:42 PMAnd please don't forget guys, always to report the bugs ;)
Thanks for your service!
Bug: Focus stacking
Doesn't work as intended. I tried several options (shots to be taken in front and back, focus step setting) and the result was always the same. Focus is established, takes first shot, the focus plane is shifted forward in a slow pace and then ... surprise ... it takes a fast walk back to the focus point for the first shot and takes the second shot at this very point. Then focus wanders forward where the third shot has to take place (slowly) and again the focus races back to "ground zero" and captures the third shot.
All shots are taken at the very same focus point.
Tried with today's build, too. All the same. Tried with Canon EF 100/2.8 Macro USM and Canon EF 100/2.8 L IS Macro USM.
Ciao, Walter
Quote from: satriani on May 31, 2013, 03:20:42 PM
Hey guys,
to be always up to date, use the "Daily compiled builds from the last ML source" (https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0) or take a look to my signature. The compilation occurs automatically on my server, then tested on my camera and published.
I will try my best to upload every day. And please don't forget guys, always to report the bugs ;)
What a good guy! Thanks :)
Quote from: lordgnagey on May 31, 2013, 03:40:52 PM
You probably hit the card capacity or the file limit 4.29gb, I'd bet on the latter. Sad thing is I can't see any way of easily recovering that data. You have to watch your GB size with raw_rec. It's very early yet in its development.
But yes keep under that limit and you'll be fine.
i didn't go that far to 4 gig, just about 1gig or less,good news is that was just a testing video and nothing was important, but thank you all the same for your concern~
I searched the thread and haven't been able to locate anything recently on the subject of movie restart. Is the plan still to include it at some point? Not talking about RAW video here, although that would also be interesting if possible.
Thanks for the great work you guys are doing
Guys stop talking about raw videos. there is much more to do before raw shooting,
Why should they stop? :o
What I do suggest though is opening a 650D thread where all the other raw video threads are so that I can keep track of the issues in an easy way ;)
Exactly nanomad. The more intense it will be tested and reported bugs, the faster the release is ready for production use :P
Quote from: satriani on May 31, 2013, 03:20:42 PM
Hey guys,
to be always up to date, use the "Daily compiled builds from the last ML source" (https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0) or take a look to my signature. The compilation occurs automatically on my server, then tested on my camera and published.
I will try my best to upload every day. And please don't forget guys, always to report the bugs ;)
Which of all these files we put and how ?
Thanks ;D
BUG:
When I change the ISO during recording, the iso numbers on the bottom of the screen don't change right away.
BUG:
Gradual exposure causes discoloration when changing between ISO settings.
Quote from: satriani on May 31, 2013, 03:20:42 PM
Hey guys,
to be always up to date, use the "Daily compiled builds from the last ML source" (https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0) or take a look to my signature. The compilation occurs automatically on my server, then tested on my camera and published.
I will try my best to upload every day. And please don't forget guys, always to report the bugs ;)
Hey man. I wanted to say I really appreciate the work! And I have tested out the May 31st build. Apologies for being so direct, but with the adjusted frame sizes 1472 width at 2.35 actually pushes us over the limit in terms of the buffer. It no longer allows for continuous recording, because of this I will be using the older build (with 1440) for my 24fps raw tests.
Is there a way to free up more space for alternative resolutions? Could we do this by removing the options above 1728? I think it would be beneficial considering that these higher res options are useless with this camera's capabilities. Personally I would like to see something like 960 1088 1152 1216 1280 1344 1408 1440 1456 1472 1536 1728 as width options to find what res that has enough cushion to allow for continuous recording. 1216 width would probably be the highest 16:9 with continuous recording.
I do understand that you were attempting to keep all resolutions within a multiple of 64 to maximize efficiency of RAW recording, but sadly it has cost us the highest 2.35 resolution that could record continuously at 24fps. And from my perspective, the speed improvements do not outweigh the option for doing longer takes. 1456 which is 22.75 x 64 might be a decent option, but I assume that 1440 will be a safer resolution to work with as neither is a direct multiple of 64.
That aside, I will say that I did test FPS override at 2.5 fps and I got a pretty nice 3.0x CBR h.264 sunrise TL. Now if only we could implement ALL-I frames... :P
I uploaded a RAW Video Test: http://t.co/oSV53iVdw1 here.
Resolution: 1280x432, I got a slow card. I reduced the pink noises on post using noise reductions from adobe photoshop/after effects. losing details :-\
using satriani's custom ML_N_31.05.2013 build.
how to playback raw file
You can't:
http://www.magiclantern.fm/forum/index.php?topic=5654.msg39968#msg39968
Ciao, Walter
got some crashes when try fps override and silent pictures:
ASSERT: 0
at Graphics.c:3580, task CtrlSrv
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Apr30.650D101
Mercurial changeset : ca7870e6a59c (unified)
Built on 2013-04-30 13:27:39 by nanomad@workhorse.
Free Memory : 315K + 3426K
and rec is frozen, and on the video lots of vertical lines...
i cant upload the crash log happened with silent pictures, because the camera totally frozen and does not write crash log...
Quote from: MarlonSenanayake on May 31, 2013, 06:46:46 PM
Guys stop talking about raw videos. there is much more to do before raw shooting,
I agree. raw video on this camera is worthless to invest time in. People who wants good raw-will have to buy 5D.
Now i think developers could spend more time for more useful things in 650D.
Does anyone of you filming something soooo special that needs raw video? Whats the point of raw video when you shoot it with kit lenses :D As we all see 650d have write speed limitation ~ 40MB/s so raw video anyways will be not the best one.
Also i do not know what on earth worth to have 40MB/s frame rate video that i would save it and not convert to smaller size :) I'd rathar go with BBC Planet Earth HDs then mine raw :D
I'm just sayin'
BUG:
The red circle record indicator sometimes disappears while recording with the ML overlay. I accidentally stop recording today, because I didn't notice the red circle. This might be problematic to a lot of users.
Thanks for the great work developers!
I have installed and it works fine, but now the screen always flickers, as if playing back hdr video, but the settings are normal.
it flickers during playback of stills as well.
anyone else having this problem??
Quote from: tommix on June 01, 2013, 07:57:01 PM
I agree. raw video on this camera is worthless to invest time in. People who wants good raw-will have to buy 5D.
Now i think developers could spend more time for more useful things in 650D.
Does anyone of you filming something soooo special that needs raw video? Whats the point of raw video when you shoot it with kit lenses :D As we all see 650d have write speed limitation ~ 40MB/s so raw video anyways will be not the best one.
Also i do not know what on earth worth to have 40MB/s frame rate video that i would save it and not convert to smaller size :) I'd rathar go with BBC Planet Earth HDs then mine raw :D
I'm just sayin'
I'll have to agree. If the RAW is just janky at best, it's probably a waste of time. I'd rather have all of the full features working just like on the T3i and then start to add improvements.
I wouldn't generalize about "kit lenses." I don't have a kit lens. You can do some pretty good looking stuff with a T4i if you take the time to do it. Granted there's a LOT of mediocre work out there, but I wouldn't generalize.
Bug: Modules loading/unloading several times freezes camera. After removing and insertingbattery camera starts up again.
Not sure if this is relevant or not.
Ciao, Walter
Quote from: 33black on June 01, 2013, 09:10:08 PM
I'll have to agree. If the RAW is just janky at best, it's probably a waste of time. I'd rather have all of the full features working just like on the T3i and then start to add improvements.
I wouldn't generalize about "kit lenses." I don't have a kit lens. You can do some pretty good looking stuff with a T4i if you take the time to do it. Granted there's a LOT of mediocre work out there, but I wouldn't generalize.
Now I'd have to disagree. While the raw that comes from this camera isn't the best, keep in mind that this camera is not a 5D, and therefore was not bought by someone looking to get the utmost quality and features. On the contrary, in least in my case, it was bought to be a semi-budget camera for youtube. The addition of RAW support of any kind is a very great bonus, and given that I'm very grateful for the effort the team has put in to RAW recording. Once we sort out the weird elements bug, the T4i has the potential to become a very powerful RAW camera for the entry-level cinematographer.
Guys please stop to tell developers what they have to do!
They also working hard for another devices. The RAW video recording is now the part of the project Magic Lantern.
Take a look to the change log and you will see, that RAW video recording is not the only thing that developers are working on.
Please, have a little patience.
Quote from: lynx on June 01, 2013, 08:13:13 PM
BUG:
The red circle record indicator sometimes disappears while recording with the ML overlay. I accidentally stop recording today, because I didn't notice the red circle. This might be problematic to a lot of users.
Thanks for the great work developers!
well, I experienced this also, on the pre alpha 1 (i believe). so the thing i thought i record wasn't recorded, vice versa. luckily it's not a wedding or such. :P
Quote from: roterrion on June 02, 2013, 06:25:11 AM
well, I experienced this also, on the pre alpha 1 (i believe). so the thing i thought i record wasn't recorded, vice versa. luckily it's not a wedding or such. :P
Thank goodness it wasn't a wedding... But I have one coming up soon, and I probably won't use the ML overlay just yet. I think the build I was using was the Alpha 2, it was the build complied by satriani (ML_N_30) that has the RAW video module.
As a suggestion, use the rec/stdby overlay that shows a big red overlay when not recording
hello it and the best adjustment for motion détection ?
I find the slow detection even in manual AF
for bird photography
Congratulations for a great job ml!
Trap focus is missing in this version. Would be better suited for this kind of work.
Ciao, Walter
Trap focus is not working on the 650D because canon isn't updating the "realtime" focusinfo anymore
Unless you have the lens set to AF ::)
Thanks for the info!
@oli650D: There may be a workaround for you:
Tap a single pin on your lens or camera (Link, german only (http://ip-networx.de/index.php?option=com_content&task=view&id=26&Itemid=)), set focus mode on the lens to AF, enable "Continuous shooting", adjust focus distance manually and press the shutter button. Would be best to use a wired remote where the shutter button can be fixed in that position.
Tested it with 650D and EF 100/2.8 L IS USM Macro (IS off) and EF 100/2.8 Macro USM. Works like a charm. May be not your choice because shooting will continue as long as focus is established and SD-Card has free space.
Tested it with 7D: Not that great. 7D shoots once, gives an Err and will not do a second shot until shutter button is released.
But there is an ML alpha 2 doing trap focus without hardware tweaks. ;-)
Ciao, Walter
Quote from: 33black on June 01, 2013, 09:10:08 PM
I'll have to agree. If the RAW is just janky at best, it's probably a waste of time. I'd rather have all of the full features working just like on the T3i and then start to add improvements.
I wouldn't generalize about "kit lenses." I don't have a kit lens. You can do some pretty good looking stuff with a T4i if you take the time to do it. Granted there's a LOT of mediocre work out there, but I wouldn't generalize.
i agree with timmy this is waste of time, make firmware stable and then keep work on raw
dir seen her this option is not available on the 650d?
hello guys I'd like to try this software for canon650d can help me with a download link for that please? thank you!
Quote from: adrian2013 on June 02, 2013, 12:34:39 PM
hello guys I'd like to try this software for canon650d can help me with a download link for that please? thank you!
http://www.magiclantern.fm/forum/index.php?topic=3697.msg32446#msg32446
These are the official instructions for the pre-alpha 2 and the posts after describe how to get it working from scratch.
thank you Lucas
Hey guys,
the last build ML_N_02.06.2013.zip (https://www.dropbox.com/sh/hxsv61cq992egmy/Zmfg0vB1m9/ML_N_02.06.2013.zip) was compiled with disabled Rev 7242, because of occured error by compilation.
This change seem not to be relevant for 650D.
Quote from: 1pModules now work on EOSM... took out beep so add dummy stubs
Waiting for solution :)
Quote from: oli650d on June 02, 2013, 12:34:16 PM
dir seen her this option is not available on the 650d?
I'm not able to understand your question, please rephrase!
Ciao, Walter
trap will focus on t he day 650d?
I board the impresion that the motion detec function well at times
and the other not,! :-\
Trap focus, dunno.
Motion detect works as it does not rely on focus data
Just installed ML on my 650D: Really great work, thank you! One question: are there costumizable shortcut keys to access specific menu items (for instance: I'd happy to have a fast access to the "Auto adjust Kelvin" function)?
Hi folks,
Noob question - I installed the pre-alpha (satriani's latest daily build). No problems installing, but the overlay menu is grayed out. I can toggle the options, but focus peaking, magic zoom, crop marks, etc., - none of them work when I toggle them on. I'm in live view, movie mode, etc. Could someone tell me what I'm missing?
Quote from: AlecWild on June 03, 2013, 03:04:29 AM
Hi folks,
Noob question - I installed the pre-alpha (satriani's latest daily build). No problems installing, but the overlay menu is grayed out. I can toggle the options, but focus peaking, magic zoom, crop marks, etc., - none of them work when I toggle them on. I'm in live view, movie mode, etc. Could someone tell me what I'm missing?
Make sure Global Draw is on
Hi thanks - Global Draw is on - greyed out in LiveView, ON all modes; white in QuickReview. The rest of the overlay menu is still greyed out, no matter what mode Global Draw is in.
Thoughts?
yeah, hit info until you get to the ML overlay
Well, there's how much a noob I am. I thank you. I'm continually impressed with the cordiality on this board. And the dedicated hard work.
Is there any KELVIN White balance menu on the pre alpha? Also I tried using the camera through an external monitor
and had issues with the focus peaks it just looked like a bar of red static across the middle of the screen and Zebras didnt seem to work, these functions work fine on the camera monitor but not on the external monitor all other overlays working perfectly except for magic zoom but that has been noted already by other people a few pages back.I like how the Magic lantern menu tabs look on the 650 as well, could it be possible to have a new design for live view screen aswell, I would be more than happy to design something if someone could write the code for it.
Kelvin white balance is enabled on the latest daily compiles, but not Pre-Alpha 2.
Quote from: Lucas_W on June 03, 2013, 08:22:49 AM
Kelvin white balance is enabled on the latest daily compiles, but not Pre-Alpha 2.
Hello! Any news about audio meter? Maybe in daily compiles?
tell me why when recording raw video shows pink dots in the center of the frame? can be seen in all assemblies with the raw video. and yet in all the assembly since May 16, when turn on the magic zoom, the picture is choppy, it was not in the build up to and including May 16, and after the raw video as it did not twitch as will not fix. sorry for my English language, I write through a translator.
Quote from: kzi2006 on June 03, 2013, 10:57:18 AM
Hello! Any news about audio meter? Maybe in daily compiles?
yeaah audio is so important than raw
Quote from: NikeFreak on June 03, 2013, 12:26:06 PM
tell me why when recording raw video shows pink dots in the center of the frame? can be seen in all assemblies with the raw video. and yet in all the assembly since May 16, when turn on the magic zoom, the picture is choppy, it was not in the build up to and including May 16, and after the raw video as it did not twitch as will not fix. sorry for my English language, I write through a translator.
Pink dots are due to the hybrid AF. The fix is in the backlog right now.
MZ being choppy looks like a regression, I'll fix it ASAP.
About audio meters, I need to investigate the audio section (maybe taking hints from the 6D, dunno). It's on schedule though. Don't worry
Quote from: nanomad on June 03, 2013, 05:22:41 PM
Pink dots are due to the hybrid AF. The fix is in the backlog right now.
MZ being choppy looks like a regression, I'll fix it ASAP.
About audio meters, I need to investigate the audio section (maybe taking hints from the 6D, dunno). It's on schedule though. Don't worry
What does backlog mean? :P
It means that they are aware and it is on the list to be fixed, I presume.
Are you guys planning on including movie restart in a later release?
Thanks
Quote from: Foley on June 03, 2013, 06:57:39 PM
It means that they are aware and it is on the list to be fixed, I presume.
Tank you :)
Quote from: Dogfish on June 03, 2013, 08:12:04 PM
Are you guys planning on including movie restart in a later release?
Thanks
It should be working already in the repository. Let me know if it doesn't
Okay, here's what I've got for RAW. A little test video made at my local pier.
Excuse the camerawork; forgot a tripod and had to warp stabilize the h*ll outta it.
Quote from: papkee on June 04, 2013, 05:39:52 AM
Okay, here's what I've got for RAW. A little test video made at my local pier.
Excuse the camerawork; forgot a tripod and had to warp stabilize the h*ll outta it.
Nice job, looks like you put a little time into this! What did you use to remove the af dots? I assume the color/luminance noise reduction in photoshop? What were the settings used?
Quote from: papkee on June 04, 2013, 05:39:52 AM
Okay, here's what I've got for RAW. A little test video made at my local pier.
you removed the pink dots?
Quote from: NikeFreak on June 04, 2013, 10:21:08 AM
you removed the pink dots?
No, you can see them in the end of video.... :-[
Pick one:
- Tearing MagicZoom
- In sync MZ but all camera buttons unusable when enabled except for the MZ trigger key.
tell whether the function is implemented digital zoom while recording video, which is in the 600d and 700d, is it worth to wait for it to 650d?
Quote from: NikeFreak on June 04, 2013, 12:47:38 PM
tell whether the function is implemented digital zoom while recording video, which is in the 600d and 700d, is it worth to wait for it to 650d?
OMG... For the last time, there is no digital crop zoom on the T5i/700D. All the sites that said so were wrong. I have never seen a lie perpetuated for this long before. I feel bad for all the people who decided to buy a T5i/700D after reading such misinformation thinking that the digital crop zoom had returned. It hasn't. Get over it. If you want it, get the T3i/600D.
I wonder if Canon is the one who started this lie in order to convince people to buy the T5i/700D over the now less expensive yet identical T4i/650D...
Quote from: nanomad on June 03, 2013, 08:50:14 PM
It should be working already in the repository. Let me know if it doesn't
I just installed what I think is the latest code and I dont see movie restart anywhere. A few weeks ago it was there but I could not get it to work.
Thanks for all you do! Keep it up!
Cliff
Quote from: nanomad on June 04, 2013, 10:52:27 AM
Pick one:
- Tearing MagicZoom
- In sync MZ but all camera buttons unusable when enabled except for the MZ trigger key.
THIS PLZ! - In sync MZ but all camera buttons unusable when enabled except for the MZ trigger key.
Phhoenyxx that is for the 650d digital zoom will not be?
Huge thanks to all the people involved in this project, I've played with a couple of builds and am loving some of the extra features. (especially sokoban :) )
Can I ask a question about raw and its benefits when shooting greenscreen?
I want to do some green screen shooting soon, I'm assuming raw would be ideal for this. but at the lower resolution (<720p instead of 1080p) will it still be noticeably better to hang on for raw?
I imagine that increasing the bitrate to 1.3X and then scaling the compressed 1080p video down to 720p will reduce a lot of the problems introduced by the compression.
or does the h.264 compression on the 650d do more than just reduce pixels, does it lower bit count for each channel too etc?
Sorry if this is slightly off-topic!
Quote from: NikeFreak on June 04, 2013, 05:15:17 PM
Phhoenyxx that is for the 650d digital zoom will not be?
Digital Crop Zoom is ONLY on the T3i/600D! BOTH the T4i/650D AND the T5i/700D DON'T HAVE IT!
Will ML be able to add it to the T4i/650D and the T5i/700D? Maybe, but it's not a default feature of those cameras.
Quote from: Phhoenyxx on June 04, 2013, 05:18:57 PM
Digital Crop Zoom is ONLY on the T3i/600D! BOTH the T4i/650D AND the T5i/700D DON'T HAVE IT!
Will ML be able to add it to the T4i/650D and the T5i/700D? Maybe, but it's not a default feature of those cameras.
I know that it is not in 650V, I asked whether it would make ML.
Quote from: NikeFreak on June 04, 2013, 05:54:18 PM
I know that it is not in 650V, I asked whether it would make ML.
I don't know, but I hope so. It would be a cool extra feature to have, but I have a feeling Canon needed to remove it because it conflicted with the new on-sensor phase detections pixels added on their new Hybrid-CMOS sensors. They probably couldn't have digital crop zoom and the on-sensor phase detection pixels at the same time/place. My guess is that if ML is able to add it, they would need to do so by disabling the on-sensor phase detection pixels. It will most likely be one or the other, but not both at the same time. That's just my theory though. I don't really know much about this stuff.
Quote from: 30dbs on June 04, 2013, 05:16:09 PM
Huge thanks to all the people involved in this project, I've played with a couple of builds and am loving some of the extra features. (especially sokoban :) )
Can I ask a question about raw and its benefits when shooting greenscreen?
I want to do some green screen shooting soon, I'm assuming raw would be ideal for this. but at the lower resolution (<720p instead of 1080p) will it still be noticeably better to hang on for raw?
I imagine that increasing the bitrate to 1.3X and then scaling the compressed 1080p video down to 720p will reduce a lot of the problems introduced by the compression.
or does the h.264 compression on the 650d do more than just reduce pixels, does it lower bit count for each channel too etc?
Sorry if this is slightly off-topic!
I think 422 is the best you can do with the h.264 that comes out of the normal vid recording. Getting 444 video even at 8-bit is much better for keying. I'm not familiar with the RAW post processing, but I think 444 is possible and will help keying on the edges of your subject. I'll leave the technical discussion on why to a google search. It has been discussed a time or two. hint: 422 chroma key
Quote from: nanomad on June 04, 2013, 10:52:27 AM
Pick one:
- Tearing MagicZoom
- In sync MZ but all camera buttons unusable when enabled except for the MZ trigger key.
I really like having MZ, and it is not really optimal to use as is was now.... If i am using it, i would at least have to be able to use shutter right? So i will still go for the tearing MZ....
Quote from: nanomad on June 04, 2013, 10:52:27 AM
Pick one:
- Tearing MagicZoom
- In sync MZ but all camera buttons unusable when enabled except for the MZ trigger key.
I'd rather have MZ in sync, even at the expense of being able to use other buttons.
if i understand correct, you can only turn it on and off, nothing else....
Quote from: Gorilla on June 04, 2013, 09:02:02 PM
I'd rather have MZ in sync, even at the expense of being able to use other buttons.
Agreed.
I would much prefer the tearing MZ options as I have shot 3 projects using this build and I find it useful to be able to start recording and change settings with MZ enabled.
Also I don't really find the tearing MZ that distracting, I can still use it to check my focus easily and find it much more convenient than using the canon zoom.
Just my opinion!
Please can you tell me where to find the menu icon EXPO I just installed this software and I often can not find or is a problem with firmwere
Hello, I've been looking all day but I can't seem to find them. Can somebody please link me to where the nightly builds are being posted and can be downloaded from? Thank you!!!
You may want to use satriani's daily builds: https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0
Ciao, Walter
Quote from: Walter Schulz on June 05, 2013, 07:09:40 AM
You may want to use satriani's daily builds: https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0
Ciao, Walter
guys please write a change log if u can, people can figure out what are the changes
There *is* a change log ...
Ciao, Walter
Please can you tell me where to find the menu icon EXPO I just installed this software and I often can not find or is a problem with firmwere
Could it be possible to bypass this error with magic lantern?
(http://www.bildites.lv/images/qb8cansx6vqz2ahsxiu_thumb.jpg) (http://www.bildites.lv/images/qb8cansx6vqz2ahsxiu.jpg)
And what's about that flickering in movie mode? Or i'm the only one who has this problem?
Quote from: Emiils on June 05, 2013, 04:05:50 PM
Could it be possible to bypass this error with magic lantern?
(http://www.bildites.lv/images/qb8cansx6vqz2ahsxiu_thumb.jpg) (http://www.bildites.lv/images/qb8cansx6vqz2ahsxiu.jpg)
And what's about that flickering in movie mode? Or i'm the only one who has this problem?
I'm not an expert, but I don't think that's related to the firmware or to ML. You should do what it says. Clean the contacts. Remove the lens and try another one if you can. If the problem persists, contact Canon.
There is a thread on old Sigma lenses that cause this error:
http://www.magiclantern.fm/forum/index.php?topic=1749.0 (http://www.magiclantern.fm/forum/index.php?topic=1749.0)
Could this be your problem?
Quote from: adrian2013 on June 05, 2013, 03:47:06 PM
Please can you tell me where to find the menu icon EXPO I just installed this software and I often can not find or is a problem with firmwere
Press the trashcan when you are not in playback (reviewing the pics you just shot) mode. To save you another post, press info several times if global draw is not working. Check this out for questions about features http://wiki.magiclantern.fm/userguide (http://wiki.magiclantern.fm/userguide)
If the ML menu doesn't come up when you push the trashcan, you either are in playback mode or ML is not installed correctly. (make sure your camera and SD card are boot enabled. there are posts on how to do this)
Hello!
I'm pretty new to this, I got my 650D in front of me, but I can't find any download for ML on the site, where is it, or is there one?
2nd Question, if a installation fails, is there anything you can to to fix the camera?
Quote from: iSw3de on June 05, 2013, 04:59:20 PMI'm pretty new to this, I got my 650D in front of me, but I can't find any download for ML on the site, where is it, or is there one?
Linked on the very page you put your post ...
Quote from: iSw3de on June 05, 2013, 04:59:20 PM2nd Question, if a installation fails, is there anything you can to to fix the camera?
Short answer: Yes or no.
Those who know the future don't participate in this thread but relax on their own islands which they purchased after having a great time in the casino.
Longer answer: If you can't stand the risk of turning your camera into a solid paperweight you might want to stay away from pre-alpha software versions.
Ciao, Walter
Quote from: iSw3de on June 05, 2013, 04:59:20 PM
Hello!
I'm pretty new to this, I got my 650D in front of me, but I can't find any download for ML on the site, where is it, or is there one?
2nd Question, if a installation fails, is there anything you can to to fix the camera?
1. Make sure that the firmware is fixed for a booting from SD card. If not, follow this instruction:
- Download this boot fix: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip
- Extract this to your SD card
- Put the SD card in your camera and do a firmware update
your camera firmware is fixed :)
2. Make sure that the bootflags is setted on your SD card. If not, follow this instruction:
http://wiki.magiclantern.fm/install#installing_magic_lantern_on_other_cards
3. Download the new zip file and extract it to your SD card.
Note, the name of the zip file contained a creating date in european format.
ML_N_11.05.zip
ML = Magic Lantern
N = nightly
11.05 = 11 May
4. Test this build diligently and report the bugs ;)
https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0
Hiya
This is what I am getting when following the guide:
First when I try to update firmware I get a screen telling me that
"Firmware Update Program"
".....Loading"
I am then returned to the screen where I can select "firmware ver.: 1.0.1"
then after a few seconds the following text appear over the usual screen text:
" EnableMainFirm "
" :) "
I downloaded the files from the links posted right above and have followed the instructions.
As far as searching this thread for "EnableMainFirm" goes, a1ex wrote the following.
Quote from: a1ex on April 16, 2013, 07:30:15 PM
That's for unbricking, not for enabling the boot flag.
Can anyone tell me where I went wrong?
Quote from: kostasra on June 05, 2013, 06:50:01 PM
1. Make sure that the firmware is fixed for a booting from SD card. If not, follow this instruction:
- Download this boot fix: http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip
- Extract this to your SD card
- Put the SD card in your camera and do a firmware update
your camera firmware is fixed :)
2. Make sure that the bootflags is setted on your SD card. If not, follow this instruction:
http://wiki.magiclantern.fm/install#installing_magic_lantern_on_other_cards
3. Download the new zip file and extract it to your SD card.
Note, the name of the zip file contained a creating date in european format.
ML_N_11.05.zip
ML = Magic Lantern
N = nightly
11.05 = 11 May
4. Test this build diligently and report the bugs ;)
https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0
But I mean, we are supposed to report the bugs, how big is the chance of my camera just stop working? If something goes wrong can i reset it or something?
Does anyone know when it will be made stable version?
By the way guys, I think we should rename the topic status to ALPHA, we are far from the Hello World status right now :)
Quote from: adrian2013 on June 06, 2013, 12:56:41 AM
Does anyone know when it will be made stable version?
When it's done.
Quote from: iSw3de on June 06, 2013, 12:37:30 AM
But I mean, we are supposed to report the bugs, how big is the chance of my camera just stop working? If something goes wrong can i reset it or something?
"if it breaks you get to keep both parts" This al (pre)alpha, so it has the potential to permanently brick you camera. If you can't take that risk, do not use it. However, this also applies to the stable version. Overall the software is very stable. If you get a freeze, pull the battery.... as you may be overheating your CPU, if you format the SD, ML will no longer boot, and you are back to stock firmware.
Quote from: nanomad on June 03, 2013, 08:50:14 PM
It should be working already in the repository. Let me know if it doesn't
I've tried a few builds - can't find Movie Restart - Am I looking in the wrong place?
any clue about audio monitoring menu
Quote from: rfrandsen on June 05, 2013, 09:56:37 PM
Hiya
This is what I am getting when following the guide:
First when I try to update firmware I get a screen telling me that
"Firmware Update Program"
".....Loading"
I am then returned to the screen where I can select "firmware ver.: 1.0.1"
then after a few seconds the following text appear over the usual screen text:
" EnableMainFirm "
" :) "
I downloaded the files from the links posted right above and have followed the instructions.
As far as searching this thread for "EnableMainFirm" goes, a1ex wrote the following.
Can anyone tell me where I went wrong?
Hi! im new to this forum and to the ML world, im having the same issue than rfrandsen, after the update the screen says "EnableMainFirm
:)"
What did i do wrong?
Thanks a lot
I'll be locking this thread and opening a new one ASAP with proper instructions :)
Make sure to link it when you do. I don't know my way around these forums very well. :P
Good idea bro ;)
Quote from: nanomad on June 06, 2013, 10:52:14 PM
I'll be locking this thread and opening a new one ASAP with proper instructions :)
As someone who's been lurking since December, that is the best news! Thanks for all your hard work.
Quote from: Jseeker on June 06, 2013, 04:11:03 PM
I've tried a few builds - can't find Movie Restart - Am I looking in the wrong place?
I cant find it either. And would use it every day if it was there! I shoot long events often!
Thanks
Cliff
Quote from: Cliff on June 07, 2013, 04:28:08 PM
I cant find it either. And would use it every day if it was there! I shoot long events often!
Thanks
Cliff
I don't believe it's in ML for the 650d yet. If you highlight movie tweaks under the video menu in ML you can see it listed but when you enter movie tweaks it's not there, i'm guessing when it's added it'll be there.
can we do audio monitoring whit ml on 650d. i allready have all the hardwere.??????????? thx
Quote from: slingkidy on June 08, 2013, 04:21:13 AM
can we do audio monitoring whit ml on 650d. i allready have all the hardwere.??????????? thx
Not yet
i've been following this thread for several days and im grateful to u guys for ur great work!
i heard of the RAW things of the 60D from a friend of mine, he said the 60D had the same problem of pinky dots on the image but soon u guys fixed it, what im thinking is, can 650D be fixed in the same way? are they similar?
im not asking or requesting u guys to do things, i know u have ur own schedule so im just saying.
THX for ur work again
No 60D is a very different camera from the 650D/EOSM
Can anyone tell me if this option is mettering audio Alpha version?
Quote from: nanomad on June 08, 2013, 11:08:31 AM
No 60D is a very different camera from the 650D/EOSM
im aware that the problems on 60D and the 650D are different. the color dots on the 60D are separate but what i see on my camera was an area of regularly arranged dots. so i id better spend my time on other features~ ;)
Quote from: nanomad on June 08, 2013, 10:32:18 AM
Not yet
Great. it mean that it will be possible. Hope it's will be befor my trip to Costa Rica ;D
Excited about your great job
Quote from: nanomad on June 06, 2013, 10:52:14 PM
I'll be locking this thread and opening a new one ASAP with proper instructions :)
Hi i hope this new one ASAPtopic with the instructions to install the alpha!!! To my canon T4i. Thanks. I follow this post since I bought my camera in August last year. And now I read every night when I got home the post to see what's new for 20 days. Thanks for such good work. I am very happy, and hope to install the alpha ;)
Thanks Nanomad for your hard work.
Hello ))will be on 650D audio menu as the 550D or 60D and audio meters ??
and can make the 650D such button in 600D for quick setup and ISO WhiteBalance
this is what is missing most in the 650D.. Thank you very much for your work and such a masterpiece as Magic Lantern :) :D
there is an insertion already has the status an alpha why it don't place on an official site? in the same place there are alphas for 7D and EOS-M
Quote from: satriani on June 07, 2013, 09:30:06 AM
Good idea bro ;)
Where is todays compiled build? :O
Quote from: NikeFreak on June 09, 2013, 11:35:11 AM
there is an insertion already has the status an alpha why it don't place on an official site? in the same place there are alphas for 7D and EOS-M
Because I have a better idea in mind for the ML downloads system ;)
Quote from: nanomad on June 09, 2013, 02:10:38 PM
Because I have a better idea in mind for the ML downloads system ;)
And what is that idea?
could you answer without sarcasm, I communicate through an interpreter, and it is very difficult to understand what it is about, please answer the letter.
Quote from: Aborgh on June 09, 2013, 02:03:41 PMWhere is todays compiled build? :O
::) Quote from sitriani: "I will try my best to upload every day."
Quote from: Aborgh on June 09, 2013, 02:03:41 PM
Where is todays compiled build? :O
there (http://nanomad.magiclantern.fm/nightly/) is none, then to 650 and will not be until there appears
Quote from: Aborgh on June 09, 2013, 02:25:39 PM
And what is that idea?
Re-write the ML nightly builds bot to support multiple models at the same time as it can only handle "unified" models right now.
Great Idea!
Hi guys,
I am really unexperienced and I had some troubles installing ML and get it working. Most people will know how to install it the right way but for me it was not so obvious. Now I found out what I did wrong so maybe this helps some other noobs like me 8)
1. Download the needed files
- 650D-safe-dumper.fir: https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified (https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified)
- Latest Magic Lantern builld from user Satriani: https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0 (https://www.dropbox.com/sh/hxsv61cq992egmy/BtTgp4q6i0)
- EOSCard for Windows http://pel.hu/eoscard/ (http://pel.hu/eoscard/) or MacBoot for OS X http://www.zenoshrdlu.com/macboot/macboot.html (http://www.zenoshrdlu.com/macboot/macboot.html)
2. low level format your SD card
3. Copy 650D-safe-dumper.fir on SD card. Start camera in M mode and run firmware update.
4. Copy the stuff from latest build on SD card (ML folder and autoexec.bin). The 650D-safe-dumper.fir just stays on the card.
5. Run EOSCard, check EOS_Develop and BOOTDISK
6. Put SD card in camera just press the trashcan button to run ML
I made a mistake before at step 4. I did not leave the .fir file on the card and copied the ML folder and autoexec.bin BEFORE running EOScard.
Thank you guys for the impressive work!
Quote from: Aborgh on June 09, 2013, 02:03:41 PM
Where is todays compiled build? :O
sorry guys, I had no way to test it, so this delay :P
The new build is done ;)
Quote from: nanomad on June 09, 2013, 03:32:54 PM
Re-write the ML nightly builds bot to support multiple models at the same time as it can only handle "unified" models right now.
Very cool. Thank you!
Quote from: satriani on June 09, 2013, 05:26:40 PM
sorry guys, I had no way to test it, so this delay :P
The new build is done ;)
another noob question 8): can I just copy the files from the new builds (ML folder and autoexec.bin) over the "old" ones and that's it?
that is exactly what you have to do ;)
Quote from: satriani on June 09, 2013, 05:26:40 PM
sorry guys, I had no way to test it, so this delay :P
The new build is done ;)
Yaaay :D Thank you!