For raw video and autoboot, check this thread (http://www.magiclantern.fm/forum/index.php?topic=7464.0).
Merry christmas!
(http://i.imgur.com/y1c1Zb2.jpg)
Its time to release the second alpha version of the 7D port.
We've enabled these features since alpha 1:
* Advanced Bracketing (HDR)
* Intervalometer
* Audio tags
* Bit Rate manipulation
* [EXPERIMENTAL] Modify card flush rate for higher bit rates
* [EXPERIMENTAL] Modify GOP size (down to ALL-I or up to 100 for better (?) details)
* a lot of minor fixes
Key Features:
* Audio meters while recording
* Zebras
* Focus peaking
* Magic Zooom (via half-shutter, or focus ring)
* Cropmarks, Ghost image
* Spotmeter
* False color
* Histogram, Waveform
* Vectorscope
* Movie logging
* Movie auto stop
* Trap focus
* LiveView settings (brightness, contrast...)
* Level indicator
* Image review tweaks (quick zoom)
* and some debug functions
But:
* If anything goes wrong, we don't pay for repairs. Use Magic Lantern at your own risk!
Known issues:
* You have to reload Magic Lantern every time you use it. (this is intentional)
* when using HDMI output, frame drops may happen (to be verified)
* make sure your battery/adaptor is chipped, else canon menu will abort "firmware update" (= loading ML)
* movie restart and video effects menus visible but not working
Installation
1) Update camera firmware to 2.0.3
2) Format your CF card from the camera
3) Extract contents of ML .zip into your card's root folder
4) Run "firmware upgrade" once again
5) Voilà. Magic Lantern. (press DELETE for menu)
Thanks to all who helped us with donations and bug reports.
We finally received a few IDA licenses and can improve Magic Lantern a lot now!
Main article:
Click here to read this article! (http://www.magiclantern.fm/index.php?option=com_content&view=article&id=145)
Download:
http://upload.g3gg0.de/pub_files/17248a00956f1e932457094756b2a3ba/magiclantern_7D_203_Alpha2.zip
Alternative: https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern.7D.203.Alpha2.zip
G3gg0, Congratulations!
This is a good gift desired by many of our users
Mery Christmas
Happy Holiday 7D user :)
Thanks a lot!
Merry X-mas and a happy successfull New Year! And: enjoy your holiday g3ggo!
g3gg0 thank you a lot !
Mery Christmas !
enjoy your holliday ( you deserve it !!!!! )
g3gg0 and team - thanks for the continued efforts, and of course alpha2, and have a great holiday season. 8)
Time to dig out the manual for the new features... :)
Excited for: HDR exposure bracketing, timelapse, rack focus and lots more... awesomeness
The perfect xmas gift for every 7D owner, thanks to all the developers (especially Santa g3gg0).
i think i'm going to be in trouble with the missus!
a new MLalpha to play with on xmas day and a new lens too (they don't know i know about that though! :-X !)
thanks a lot g3gg0 and gang! happy festivities!
THANK YOU and the sweet TEAM !!! Best present ever !!! 2012 !!!
I think i found a bug, wend i use the intervalometer the zoom show up in the screen, is this normal? Some time its show up other times not.
Merry Xmas to all the good people!!!
Thanks G3gg0, this is the best christmash gift that a 7D owner can desire.
Merry Christmash.
Greetings from Spain
Now its time to play CustomBitRate.
Dear g3ggo,
Nice gift! Thank you for the wonderful contribution and all your great effort!
Merry Chiristmas to you, your family and also to the rest of the ML team.
Best wishes form Ecuador!!!
Best. Christmas. EVER! \o/
Thank you g3gg0!
Btw, what does High Sharpness mode do? I don't see this in the ML user manual. Is this unique to the 7D? None of the image effects seems to work though. (intentionally disabled?)
Initial bug reports:
Under Expo > Aperture: I couldn't dial down my aperture to 1.8. If I go down from 2.8, it goes: 2.8 > 2.4 > 2.2 > 2.0 > 22.6
Video hacks settings not saved. kept defaulting to Off, flush at 4 and GOP 12
Can anyone confirm this?
Quote from: feureau on December 24, 2012, 03:37:47 AM
Btw, what does High Sharpness mode do? I don't see this in the ML user manual. Is this unique to the 7D? None of the image effects seems to work though. (intentionally disabled?)
yeah image effects dont work yet. not sure why i didnt disable the menu yet :)
Quote from: feureau on December 24, 2012, 03:37:47 AM
Under Expo > Aperture: I couldn't dial down my aperture to 1.8. If I go down from 2.8, it goes: 2.8 > 2.4 > 2.2 > 2.0 > 22.6
didnt notice, thanks. will check after xmas.
Quote from: feureau on December 24, 2012, 03:37:47 AM
Video hacks settings not saved. kept defaulting to Off, flush at 4 and GOP 12
intentional behavior, we dont save such experimental settings.
Quote from: g3gg0 on December 24, 2012, 08:51:56 AM
didnt notice, thanks. will check after xmas.
Awesome! What's High Sharpness mode do though btw?
Quote from: g3gg0 on December 24, 2012, 08:51:56 AM
intentional behavior, we dont save such experimental settings.
Will this stay this way up till final version? I've figured out a setting I like for flush and GOP that works well for me with my 7D and card combination. Would be nice if there's a way to have this setting load up every time ML is loaded...
Awesome Christmas indeed! :-*
yeah due to lack of time i've missed to disable some menus.
might also happen that a feature is broken that worked in alpha 1. sorry if that happens.
i focused on the technical aspects and the results are especially the bitrate thing that involves master and slave digic cache hacks. (controlled via RPC handlers as canon does it to communicate)
i also tried to put fps override into this release, which also requires master and slave patching.
it works but after some time (approx. a minute or less) the picture freezed or was crappy.
and this makes the feature useless, so its disabled.
Quote from: feureau on December 24, 2012, 09:38:44 AM
Awesome! What's High Sharpness mode do though btw?
Will this stay this way up till final version? I've figured out a setting I like for flush and GOP that works well for me with my 7D and card combination. Would be nice if there's a way to have this setting load up every time ML is loaded...
i didnt add sharpness feature. its mainly from the digic register research.
i just didnt make it work on 7d as i focused on different things ;)
we will see how stable it works. i am not sure yet how to make the setting safe enough.
i am afraid that some settings and/or use cases can render the video crappy and the user doesnt notice.
just imagine you shoot your whole xmas and later you realize that you just have defective videos.
so it depends on how stable the features are. we will decide depending on your
feedback.
edit:this means: tell us if the experimental features work or if they dont.
tell us what the best settings are, why these are the best and which settings are a no-go and why?
(e.g. GOP 100 is too much or do we even need GOP 10000?)
also tell us if the features are a
must-have or if they are for nuts and nobody will use them.
so we can tune the values and make it appear in stable releases too somewhen.
woo hoo, intervalometer and hdr, you made my day
thanks a lot :D
Excellent work and as always THANK YOU.
HAVE A GREAT HOLIDAY!
Quote from: g3gg0 on December 24, 2012, 10:14:10 AM
we will see how stable it works. i am not sure yet how to make the setting safe enough.
i am afraid that some settings and/or use cases can render the video crappy and the user doesnt notice.
just imagine you shoot your whole xmas and later you realize that you just have defective videos.
so it depends on how stable the features are. we will decide depending on your feedback.
edit:
this means: tell us if the experimental features work or if they dont.
tell us what the best settings are, why these are the best and which settings are a no-go and why?
(e.g. GOP 100 is too much or do we even need GOP 10000?)
also tell us if the features are a must-have or if they are for nuts and nobody will use them.
so we can tune the values and make it appear in stable releases too somewhen.
One thing I've been noticing in using bitrate hacks with GOP and flush settings is that how I would set them up differently for different situation.
For instance,
I would crank up the CBR factor/VBR Scale to the max, disable audio and low flush and low GOP number to shoot audioless stuff, e.g., stuff like trees, macro shots and other objects, etc.
I would switch flush to 24 with audio enabled with medium GOP to shoot things that makes sound, like a musical instrument or machines chugging. I shoot with an external audio recorder that I would sync with in post, so having sound really help to sync stuff. (even when VideoRemoteShot gets enabled in future firmware)
This version seems to disable audio every time I fiddle with video hacks so I'd have to manually turn on audio after every settings, so that's kinda annoying.
So, the biggest feedback I have is probably this: having a custom preset that could save video bitrate setting preset would be nice. This could be experimented on pre-release to maximize stability, and user-customizable if one desire to experiment on.
Not sure if this is outside the 7D ML scope, but there it is.
Has anyone researched on lowering the audio bitrate btw?
Also: I'm loving the sticky half shutter function :D Is it possible to assign it to the AF-ON button too? (a lot of shooters uses the back button to focus)
And is the DOF preview sticky still disabled? I can't seem to get it to work. DOF preview sticky seems only to work on liveview mode, and not through the OVF. Is there a way to get this to work with the OVF?
Thanks for all the hard work, g3gg0! This thing is superb! :3
"Limit bitrate to:" option is needed when shooting video in VBR mode. Otherwise if I have many cards with different speeds I have to change video settings. If invalid parameters are set then recording will stop. This makes bitrate manipulations unuseable. Also lack of this option limits safe ISO range due to excessive bitrate caused by noise and makes hard to determine this ISO for certain scene.
Quote from: xmd5a on December 24, 2012, 09:50:34 PM
"Limit bitrate to:" option is needed when shooting video in VBR mode.
Try using CBR mode. It's like setting a "max" bitrate.
Quote from: xmd5a on December 24, 2012, 09:50:34 PM
if I have many cards with different speeds I have to change video settings. If invalid parameters are set then recording will stop. This makes bitrate manipulations unuseable.
This is an issue with the card's write speed though. You shouldn't set the bitrate to exceed your card.
Quote from: xmd5a on December 24, 2012, 09:50:34 PM
Also lack of this option limits safe ISO range due to excessive bitrate caused by noise and makes hard to determine this ISO for certain scene.
I've been trying out some settings. Maybe having a "bitrate setting cookbook" would be nice. Sort of a rule of thumb on how high the bitrate can be set in relation to ISO. OTOH, this is something that you should have a rough idea of.
For example: Turning the audio off, I find that I can shoot grass and trees at 12800 ISO, with a fast flush and small GOP. With the audio on, it would drop recording at about 1600 ISO, plus flush needs to be set according to framerate it seems.
thanks ml-team...just love the hdr and intervalometer
Quote from: xmd5a on December 24, 2012, 09:50:34 PMif I have many cards with different speeds I have to change video settings.
Settings are save on the card, so you can optimize it once for each card.
its a feature now ;D
where should we post bugs?
Merry Christmas together.
First I want to say that ML is a great extension for all EOS cameras.
My compliments ... great job.
I use mainly the bit rates increase .... but somehow it does not happen with me. I set up a CBR times at 2 to 3. But the uptake rate is unfortunately not up. It goes partially downwards. (Display film Inspector in QuickTime Player)
I would like a cbr 100 mbit / s
What am I doing wrong?
Thank you
Ralf
Quote from: StefanKeller.AC on December 25, 2012, 10:47:12 AM
Settings are save on the card, so you can optimize it once for each card.
its a feature now ;D
Flush and GOP settings aren't currently being saved. Plus there's different optimal settings for different situations.
Quote from: RAK1966 on December 25, 2012, 11:48:31 AM
I use mainly the bit rates increase .... but somehow it does not happen with me. I set up a CBR times at 2 to 3. But the uptake rate is unfortunately not up. It goes partially downwards. (Display film Inspector in QuickTime Player)
I would like a cbr 100 mbit / s
What are your settings?
If you use low ISOs there might not be enough details to save, therefore the bitrate stays low.
For maximum bitrate, try this:
Disable audio, ISO 12800 Flush at 4, GOP 1 and fill the screen with tall grasses. You're going to need a fast card, but I managed to hit around 350mbit/s this way.
One caveat: this is a nice cute exercise but for real world shooting, you should optimize to get the most details you can, instead of extremely high bitrate.
for that reason gop 100 might be good.
you save no unneccessary image regions, so you save your bitrate for the regions that need the high details
Great news on the Alpha-2!
Thanks a lot :)
Myabe it's time to update this page though http://www.magiclantern.fm/newmodelsstatus ? ;)
(http://pel.hu/down/ML7D.png)
http://pel.hu/down/ML7D.png (http://pel.hu/down/ML7D.png)
I've played with the info screen a little, but I've forgot how can I update it to my fork... :(
And one question:
The mode warning is more useful for me if it warns when I not in the Av mode (instead of M), because I mostly use Av, and I use M mode only for (multi)flash photography.
I've changed it to fit my taste, but maybe others don't like it.
So, what do you think?
M or Av or configurable?
Edit: I've made the mode warning configurable, fixed the ALO warning and put the info screen changes to my fork. It will go to the main source when my pull request will accept.
Quote from: Pelican on December 25, 2012, 10:31:49 PM
http://pel.hu/down/ML7D.png
I've played with the info screen a little, but I've forgot how can I update it to my fork... :(
Holy cow! That is awesome. If you can get that to the release that would be great :D
Quote from: Pelican on December 25, 2012, 10:31:49 PM
The mode warning is more useful for me if it warns when I not in the Av mode (instead of M), because I mostly use Av, and I use M mode only for (multi)flash photography.
I've changed it to fit my taste, but maybe others don't like it.
So, what do you think?
M or Av or configurable?
That's a great idea, my vote goes to configurable because some people may not like it.
Quote from: g3gg0 on December 25, 2012, 03:51:25 PM
for that reason gop 100 might be good.
you save no unneccessary image regions, so you save your bitrate for the regions that need the high details
I know from my previous testings that in the default firmware, you can really tell the difference between the I frame and the P frame, with the P frames looking worse. I'm testing it again with long GOP at 96 (for 24 frames x 4 seconds) with audio enabled. I'll give an update with whatever I can find later.
Though it can get confusing after too many video recordings: I wish the video .log files record GOP and flush settings too. I get confused which file is which sometimes. Had to take notes separately.
And changing GOP and flush kept disabling audio - it can get quite annoying to have to re-enable audio every time I change the GOP. Would be nice to have an option to do this separately. (the one that comes with the firmware is buried pretty deep if you go back and forth from ML).
Recording audio seems to only work when flush is at 24. Is this something due to the experimental nature of this feature or is this how it's supposed to be?
One thought: Maybe it would be useful (if at all possible) to change and customize the CBR/QScale factor and flush and GOP size (even on-the-fly while recording) according to ISO values, apart from the custom settings I mentioned, of course. For instance: I was just trying something out, and at ISO 12800 one scene would fail at QScale -8 or lower. However, the same scene would record at a rather low bitrate at ISO 100 at QScale -16. The idea is that if you change the ISO settings, the QScale settings would change along with it, maximizing bitrate but not letting the video to stop recording. Thoughts?
Thanks for all the hard work, g3gg0! :D
Quick Notes. If I don't make a comment after the feature, that means it seems to work fine and I love it :)
White Balance Manipulation
ISO Manipulation
REC/STBY - Beep doesn't work, We have no Blue LED
Bracketing
Mirror Lockup Tweaks
Follow Focus via Joystick (Bug, with zoom via half shutter, follow focus does not work, will look into further)
Adjustable speed settings
Disabling x5 zoom
Increase SharpContrast (You can see if more so when zoomed in)
LiveView Zooming on Half Shutter
Focus Box Settings
LiveView Power Savings
I know these notes are sparse, but you added oh so much, it's impossible to go through it with a fine tooth comb right now :)
Quote from: Digital Corpus on December 26, 2012, 12:07:09 PM
REC/STBY - Beep doesn't work
Can not confirm that. Beep works.
Quote from: xmd5a on December 26, 2012, 02:24:57 PM
Can not confirm that. Beep works.
Double checking this morning and you're correct. Works fine now :\
Quote from: feureau on December 26, 2012, 12:09:40 AM
Holy cow! That is awesome. If you can get that to the release that would be great :D
That's a great idea, my vote goes to configurable because some people may not like it.
Agreed, that's a really nice look for the info screen.
Also agree with the M/Av thing.
Thanks everyone. GOT to get a CF card reader!
First of all,
Thx for bringing out for 7D. This is great news.
When I installed it, it worked first. Then when I restarted the camera, i did not see the ML menu anymore. It's like it was not installed.
Expecting the beta version...
Success..
Quote from: Carlomera on December 27, 2012, 02:53:18 AMWhen I installed it, it worked first. Then when I restarted the camera, i did not see the ML menu anymore. It's like it was not installed.
Yes, alpha versions have to be manually reloaded every time for now.
Hello! Thanks for the firmware, did a great job! Firmware enjoy!
We would like to see in the new alpha version of more opportunities in the silent picture - such as a matrix of multiple images with zoom ...Thanks!!
Speaking of sticky keys of holding half-shutter for a few seconds to stop and start recording video: How about using the M.Fn. key to start and stop recording too? it's seldom used, and it's sitting right beside the shutter button. Looks perfect to start and stop recording video, this button is quite similarly placed as in the video record button on the Nikon D800. Should help mitigate/reduce that shake that happens when you start/stop recording.
Thanks to the team for all the additional features for us to test. :)
I have a request for future 7D Alpha releases regarding the "red" pulsing error message which pops up at the bottom of the LCD display when required.
Red text on a black background is a really bad idea to start off with as the contrast between these two colours is just too low to render a crisp edge to the letters. Pulsing the colour of the error message text from black to red and back to black makes it impossible to read until it is at it's brightest, which is even harder if you are already in a bright environment and before you can read more than a word or two the error message fades back to black. Any pulsing text (hopefully in a higher contrast colour) should be displayed for longer than it is not displayed, or rather display a blinking icon followed by solid text.
Sorry if this sounds trivial, but the interface is as important as the functionality which it drives.
All the best for 2013.
Chas.
i installed magic lantern, all went fine, started testing the new hdr thing, and after a few shots my camera froze, gave an error, restarted and now it sais i hae low battery and it wont turn on. tryed with 2 different batteries, charged....
any ideeas on what to do?
I've been taking a lot of HDR and never had this issue. Can you tell us what settings you used?
Try turning on your camera without ML? (or even a card in the slot?)
Wow wow weee wow. Thanks for your continuous work! Cheers mate!
First of all, thanks so much for getting ML running on the 7D. I've been waiting for this ever since I got my 7D and it's truly worth the wait.
Anyhow, I found a little hiccup I might mention. When I put my 7D on powersave (through the Info button option) it starts up again after about 15 minutes. I can't imagine this being a big problem though. BTW is there any difference between putting the camera in this ML powersave mode and switching to non-liveview photomode (except for the mirror staying up)?
Also, the analog iso adjustments (like decreasing it below 100) doesn't seem to do anything (it'll indicate it has changed but the image stays the same). Though since that's not on the list at the top of this treat I assume it's not working yet.
keep up the good work
Some issue in audio record:
1. Set Audio Remote Shot ON
(http://img854.imageshack.us/img854/1779/vram4.png)
2. Go to Audio menu and click Test Beep Sound
(http://img854.imageshack.us/img854/4340/vram3.png)
Now is not possible to use Audio Remote Shot because the audio release indicator still show "0"
(http://img43.imageshack.us/img43/208/vram2.png)
Right and left audio channel are locked on this position:
(http://img201.imageshack.us/img201/7413/vram1.png)
You can just switch OFF and ON to make it work fine to next beep signal.
Audio remote shot works fine for me but I used clapping or whistling to activate it.
The only thing I would change it could be more level setting beyond 20.
Quote from: Pelican on December 27, 2012, 10:10:53 PM
Audio remote shot works fine for me but I used clapping or whistling to activate it.
The only thing I would change it could be more level setting beyond 20.
Have you tried also after using the beep function before?
by the way can you explain me a little where are defined
PROP_ARTIST_STRING
PROP_COPYRIGHT_STRING
I'm trying to add them in the 600D too: http://www.magiclantern.fm/forum/index.php?topic=4001.0
Let me first add my thanks for ML on the 7D. Love in HDR and the in camera exposure fusion. Going to do more exploring over the next couple of days.
Now for some requests, Can you add an in camera multiple exposure feature similar to Nikon's? Can you enable second curtain sync without having an EX II series flash attached (not holding my breathe on this one)?
And lastly, a bug. I was playing with the focus stack, following the steps on the docs page. I went a bit to far on adjusting the focus with the joystick (20 steps, 10 pics) and the camera buttons stopped responding. The off switch and CF door didn't turn the camera off. Pulling the battery worked. Tried the same steps and got the same result. Tried one more time the next day and just received a focus error message and the camera stopped responding to button pushes. The display/liveview continues to update like normal. I am using the new 40mm pancake.
Really been enjoying the new features so far.
A question on rack focusing. I'm using a 17-55 2.8 IS, and I'm finding the results of the rack focus to be less than optimal.
So I focus and set this to 0 (to be the end/destination of the rack focus operation).
I then use the scroll wheel to set to, say -20 steps from 0, and perform the rack focus. The rack focus is performed, but never ends up on 0 (ie where the initial focus point is) - it's always short (so in the above example, it would probably end up in visual terms of more like -7 steps from 0, rather than 0. So the end point is always out of focus, rather than in focus.
I'll do some playing, and I understand this is very much lens dependent, but I was wondering what the results are from other people (both with other lenses and also the 17-55) to compare? Is this feature working for you? Does it work for you better with some lenses than others? Certain step sizes? Or is the feature a little bit flaky unless you have amazing lenses..?
I'm just trying to work out how to best get this feature to work for me, or if there is an issue with it, etc?
Edit: More detail.
I've got it working better by increasing the step delay from 10ms to 20ms, step size 2 (or 1 for finer resolution), step wait on. It seems to be hitting the end point more accurately now.
One slightly frustrating thing - when altering the steps to here value with the top scroll wheel, moving it fast (which you kinda have to do with a step size of 1 for it to go anywhere, as you want values of +100 or more) often comes off the parameter (especially if the soft-limit is reached, but it will often come off the parameter without that happening) - and then you are now scrolling fast through the menus. Not only that, but there is no way (I can see) of continuing to adjust the steps to here value without first zeroing it out and starting again. This makes setting up a rack focus operation quite painful, currently.
So - could you check what's happening when moving the top wheel quickly to adjust the steps to here parameter, and stop it exiting adjusting the parameter and flying off into menu scrolling - basically, if you hit the soft-limit, continuing to move the top dial should have no effect, with the value sticking at the soft limit, and the camera shouldn't just exit adjusting the parameter without warning.
And if there could be a way to go back into the steps to here parameter and continue adjusting it without zero-ing it out again first, that would be an extra bonus (though less of an issue if the previous issue can be made a bit more stable.)
Hi guys,
I'm very new to ML And testing it right now on location But i can't Find the HDR feature. Camera mode is set on manual. It should be on the movie settings, called HDR right? Sorry if am mistaken.
First of all, awesome job everyone! I've been looking forward to this for years.
Now I tested my 7D with a 60mb/s CF card and I pushed the bitrate up to 80mb/s before it started with weird artefacts... The fastest CF card I found was an UDMA 7 with 150mb/s but can anyone tell me how you got 350mb/s and with which card?
All the best
Dave
Quote from: DaveVegas on December 28, 2012, 12:24:06 PM
Now I tested my 7D with a 60mb/s CF card and I pushed the bitrate up to 80mb/s before it started with weird artefacts... The fastest CF card I found was an UDMA 7 with 150mb/s but can anyone tell me how you got 350mb/s and with which card?
warning, dont mix up mbit/s (mbps) and MiB/s (MB/s). there is a factor 8 between them.
set VBR and qscale to -16, raise ISO to max, enable video hacks, set flush rate to e.g. 2-4, film grass and move the camera around.
(rotating is best).
voila, you get the max possible bitrate.
Quote from: sanderroeling on December 28, 2012, 11:15:46 AM
Hi guys,
I'm very new to ML And testing it right now on location But i can't Find the HDR feature. Camera mode is set on manual. It should be on the movie settings, called HDR right? Sorry if am mistaken.
you are looking for "advanced bracketing" in shoot tab. (exposure bracketing)
Quote from: g3gg0 on December 28, 2012, 12:30:46 PM
you are looking for "advanced bracketing" in shoot tab. (exposure bracketing)
Ah tnx! Will try That now!
When I do the Video Hacks on the Canon Sound gets disabled. IS that a bug? Thanks!
Quote from: sanderroeling on December 28, 2012, 11:15:46 AMI'm very new to ML And testing it right now on location But i can't Find the HDR feature. Camera mode is set on manual. It should be on the movie settings, called HDR right?
If you are talking about HDR photos, then you want the advanced bracketing function.
If you are talking about the HDR movie feature, it's not in the 7D alpha yet, afaik.
Thanks g3gg0!! this alpha is amacing!
One question:
video bitrate: what is the best configuration for the best quality? How do you recomend?,
you can tell me about diferents situations of the shot if you want.
THANKS!
So now it won't record with your settings... :/
Quote from: DaveVegas on December 28, 2012, 01:42:20 PM
When I do the Video Hacks on the Canon Sound gets disabled. IS that a bug? Thanks!
No that's how it works
Quote from: scrax on December 27, 2012, 10:30:56 PM
Have you tried also after using the beep function before?
by the way can you explain me a little where are defined
PROP_ARTIST_STRING
PROP_COPYRIGHT_STRING
I'm trying to add them in the 600D too: http://www.magiclantern.fm/forum/index.php?topic=4001.0 (http://www.magiclantern.fm/forum/index.php?topic=4001.0)
They are defined in property.h and I wrote the prop handler for them to propvalues.c/.h
Quote from: Pelican on December 28, 2012, 04:55:50 PM
They are defined in property.h and I wrote the prop handler for them to propvalues.c/.h
I
can't find them in property.h (https://bitbucket.org/hudson/magic-lantern/pull-request/43/7d-info-screen-configurable-mode-warning/diff#Lsrc/property.hF4T4) diff...
will look at your sources.
EDIT: Found them :), thanks
Do you think they are the same for other camera? Is it safe to try? They are just readed, not?EDITII: Ok now got it better they were already in property.h that's why they are not in your diff...
EDIT III: Working on 600D too, but I have a name too long :D
Quote from: scrax on December 28, 2012, 05:31:18 PM
I can't find them in property.h (https://bitbucket.org/hudson/magic-lantern/pull-request/43/7d-info-screen-configurable-mode-warning/diff#Lsrc/property.hF4T4) diff...
will look at your sources.
Do you think it's hard to find them for 600D? If not can you tell me how, please?
property.h from line 170:
#endif
#define PROP_EFIC_TEMP_MAYBE 0x010100ed
//#define PROP_BATTERY_RAW_LEVEL_MAYBE 0x80030014
#define PROP_ARTIST_STRING 0x0E070000
#define PROP_COPYRIGHT_STRING 0x0E070001
#define PROP_LANGUAGE 0x02040002
#define PROP_VIDEO_SYSTEM 0x02040003
It is in the main source it's not my find.
If it doesn't work on 600D then turn property spy on, go to edit artist name, save it and see which property is changing.
Ok pel, thanks I found and added them on my fork and it works, only strange thing is that the first 3 char of artist name get cropped when showed, I can read the name correct only if I put 3 spaces in front of it. Will try to change it's position now.
EDIT: Can be that first 3 char are not read because of wrong prop address?
Is the bulb ramping for timelapse feature enabled in this alpha? (I think it was blocked waiting for some of the same property setting stuff that the HDR features needed, wasn't it?)
About the dial modes warning, I like the option to chose it but in general should be excluded in video mode IMHO, because it's already clear that it's not photo mode and now with warning on it's annoying having it when in movie mode.
Quote from: ryebrye on December 28, 2012, 06:22:36 PM
Is the bulb ramping for timelapse feature enabled in this alpha? (I think it was blocked waiting for some of the same property setting stuff that the HDR features needed, wasn't it?)
Yep, all of that stuff is now in there, bracketing, intervalometer, focus ramping, bulb ramping etc. I haven't played with bulb ramping yet though.
Thanks for the great work on ML for the 7D ! I really love it, but is there any way to start ML automatically when the camera boots ?Is this feature considered to be part of Alpha 3 ?
Quote from: media100 on December 28, 2012, 09:16:35 PM
Thanks for the great work on ML for the 7D ! I really love it, but is there any way to start ML automatically when the camera boots ?Is this feature considered to be part of Alpha 3 ?
As mentioned many times in all the alpha docs and forum threads on the 7D port of ML:-
That will come when the 7D port is stable - for now, this is intended as a testing release only, not for production work, which is one of the reasons for this limitation - the other being that apparently the boot procedure needs to modify certain camera properties and the devs aren't comfortable doing this yet while there is a possibility of camera brickage...
Thanks for another alpha release. Yesterday I kept getting an error message say that I needed to remove and reinstall the battery. Whenever I put fresh Canon batteries in my 7D it would read as empty. I removed the card and the error would still appear. After a few cycles of removing the battery and card I finally got the camera working normally. I'm a little hesitant to put the alpha back on my camera but I don't think that it'll brick my 7D. I kinda freaked out when it happened and formatted my card so I don't have the error dump file. Whenever I muster up the courage to reinstall the alpha and if I run into the issue again I'll upload the dump files. If I'm not mistaken it was an Error 30 message.
Quote from: aace on December 29, 2012, 05:57:26 AM
Thanks for another alpha release. Yesterday I kept getting an error message say that I needed to remove and reinstall the battery. Whenever I put fresh Canon batteries in my 7D it would read as empty. I removed the card and the error would still appear. After a few cycles of removing the battery and card I finally got the camera working normally. I'm a little hesitant to put the alpha back on my camera but I don't think that it'll brick my 7D. I kinda freaked out when it happened and formatted my card so I don't have the error dump file. Whenever I muster up the courage to reinstall the alpha and if I run into the issue again I'll upload the dump files. If I'm not mistaken it was an Error 30 message.
There's another user that reported similar behavior, what were you trying to do when this happen?
Just did some tests and was able to crank up bitrate to 185 mb/s but the image looks horrible (with high iso). Normal shutter and low iso with open aperture looks way better even though it's only 60-80mb/s.
My settings were Flush 1, GOP 100, (Audio Disabled) and Q-Factor -16 with ISO 3200
Best
Dave
Quote from: DaveVegas on December 29, 2012, 12:42:50 PM
Just did some tests and was able to crank up bitrate to 185 mb/s but the image looks horrible (with high iso). Normal shutter and low iso with open aperture looks way better even though it's only 60-80mb/s.
My settings were Flush 1, GOP 100, (Audio Disabled) and Q-Factor -16 with ISO 3200
Best
Dave
high bitrate recordings of crappy scenes results in high quality crap, not more.
crank up the vbr setting to -16 and use normal settings.
the results is that you will not lose too much details details in noisy scenes.
it was reported that filming dark scenes with with higher iso better to filter in post when you use high bitrates.
With "it looked horrible" I meant that it was really noisy (which is obvious with high ISO) and with low ISO the scenes looked fine.
Which settings do you reccomend? VBR -16 and video hacks off, audio on?
Awesome work!!!
Best
Dave
Quote from: DaveVegas on December 29, 2012, 01:08:55 PM
With "it looked horrible" I meant that it was really noisy (which is obvious with high ISO) and with low ISO the scenes looked fine.
Which settings do you reccomend? VBR -16 and video hacks off, audio on?
Awesome work!!!
Best
Dave
I find the best result in high iso is to use an All-I setting. That is GOP at 1 and audio off. And CBR at 20x.
I'm still trying out long GOP settings at high ISO, it looks really promising, though adobe premiere hates it and I had to re-encode to DNxHD or ProRes to edit in premiere.
I wonder if there's a way to go Unlimited GOP....? :3
Can someone explain me why high ISO is so important for bitrate? I get it, more information but also the noise gets really annoying too...
Hi,
Seems awsome. I just didn't see anywhere if you found the probleme with saving battery since the first alpha release for the 7D ?
Is it something we still need to worry about ?
Thanks for your answers and for all this fabulous work !!
Quote from: DaveVegas on December 29, 2012, 01:36:48 PM
Can someone explain me why high ISO is so important for bitrate? I get it, more information but also the noise gets really annoying too...
It's actually the other way around: High bitrate is important for High ISO > Which means all the sensor noise gets recorded due to the high bitrate, therefore retaining more details that can be brought out in post by denoiser plugins.
Recording on low ISOs, there's not much noise (which the codec interprets also as details) to record, therefore the bitrate won't go up so high.
Quote from: niavuli on December 29, 2012, 02:08:16 PM
Hi,
Seems howsome. I just didn't see anywhere if you found the probleme with saving battery since the first alpha release for the 7D ?
Is it something we still need to worry about ?
Thanks for your answers and for all this fabulous work !!
What means saving battery?
Plus, it's still alpha, which means there may be some bugs lurking underneath. (there's two reported bugs that shuts down the 7D clean, almost bricking it) use with caution.
Quote from: feureau on December 29, 2012, 04:19:17 PM(there's two reported bugs that shuts down the 7D clean, almost bricking it) use with caution.
you talk about the battery error? well i dont think these are ML bugs.
either ML crashes+bricks the camera or it just crashes it.
maybe it changes some CFn settings without reverting etc.
but this reported behavior sounds like a contact issue to me.
Quote from: g3gg0 on December 29, 2012, 05:21:20 PM
you talk about the battery error? well i dont think these are ML bugs.
either ML crashes+bricks the camera or it just crashes it.
maybe it changes some CFn settings without reverting etc.
but this reported behavior sounds like a contact issue to me.
Ah, I see! Thanks for clearing this up. I've been running a lot of HDR to try to reproduce it but it didn't work. I don't think it's ML related either.
Why HDR options seem complicated? It was easier when using ML on T3 and 60D but with 7D..... When I do the auto bracketing settings like for example:
Bracket type: Exposure (Tv, Ae)
Frames: 7, also I tried Autodetect
EV increment: 2 EV
Sequence: 0 + ++
2 second delay: Auto
ISO shifting: Off
Post scripts: Align + Enfuse
it only shows 7 images with same exposures. Did I do something wrong?
Quote from: feureau on December 29, 2012, 10:22:12 AM
There's another user that reported similar behavior, what were you trying to do when this happen?
I remember moving files from the card to my laptop and when I turned it back on I kept getting the error message. The battery level indicator would register full the entire time I would use the camera. After the battery ran out and I changed the battery I did some more shooting and moved the files. After that the error message showed up.
Quote from: feureau on December 29, 2012, 01:13:43 PM
I find the best result in high iso is to use an All-I setting. That is GOP at 1 and audio off. And CBR at 20x.
I'm still trying out long GOP settings at high ISO, it looks really promising, though adobe premiere hates it and I had to re-encode to DNxHD or ProRes to edit in premiere.
I wonder if there's a way to go Unlimited GOP....? :3
thats the point about large gops.
when editing, you must edit the whole gop at least.
and with large gops this leads to either use uncompressed frames (huge) or reencoding (quality loss).
gop is set to max 100 now. i can set it to infinite too, but is it useful?
(well, not infinite, but 2^32-1 which is effectively the same.
Quote from: g3gg0 on December 30, 2012, 10:52:21 AM
thats the point about large gops.
when editing, you must edit the whole gop at least.
and with large gops this leads to either use uncompressed frames (huge) or reencoding (quality loss).
I use premiere so: There appears to be a limit on the GOP in premiere. Longer than that, and it would only look for several frames before/after, not finding an I-frame, it would look garbled instead. I recompress to DNxHD or ProRes and it would edit faster. It's already my regular workflow, so that's not a problem. If there's any quality loss, using DNxHD/ProRes minimize this. I can't tell the difference in quality between source and reencode.
Quote from: g3gg0 on December 30, 2012, 10:52:21 AM
gop is set to max 100 now. i can set it to infinite too, but is it useful?
(well, not infinite, but 2^32-1 which is effectively the same.
Not sure how useful it'd be, but given that we're trying out long GOP, I'd like to see how this works out. :D I think there's a risk of when the card 'hiccups' one might lose the rest of the recording due to one wrong B-Frame though. I've had this happen in where one frame gets corrupted and it ruins the rest of the group until the next I-frame. Which pretty much is a non-issue with All-I.
Above all, I still wish there could be that preset thing to choose between one customize-able/stable settings to others, that can be customize-ramped up on CBR/VBR/Flush/GOP scale according to ISO. :3 plus audio recording enable/disable
yeah thats my fear. the longer the gops are, the longer bit errors wirr propagate and escalate.
one bit error in the first frame that causes no visual error will perhaps cause useless frames seveeal seconds later.
but right, we have to try it to know for sure.
i understand that you would like such setting profiles.
but yet is is still experimental and will get improved later depending on general feedback.
yet i have to think about how to make this power-user feature normal-user-proof.
any wrong setting causes the whole footage to get useless.
so it has to explicitely get configured for now.
what about the others? are you using video hacks? do you see use in them?
i can also put that code into a plugin to make sure its available to those who need it and hidden to those who dont.
Quote from: g3gg0 on December 30, 2012, 11:48:41 AM
i can also put that code into a plugin to make sure its available to those who need it and hidden to those who dont.
Sounds like a good idea. Could also include a few (3?) profiles that are considered to be good - maybe that have different good points and bad points. Average user then has a choice with those, advanced user can get the plugin and make their own profiles taylored to their needs.
Thank you guys for this awesome second alpha!
Maybe, I´ve found some little bugs.
The first one: I always get a strange sound, if I activate "ALO warning" in "Warnings for bad settings..."
The second one: Quality warning "Other than RAW" isn´t working. Is there a possibility to configure this like I need it? Maybe in the next alpha?
Can somebody confirm the two bugs?
Hi, need a bit of help, I am very new to all this and own a 7D which I wish to do more with the HDR setting. At the moment the 7D only lets you take 3 images can this be increased with the ML firmware update and if so how many will it allow me to take ?. The 7D that I have has the Canon firmware updated to Ver. 2.0.0. Also I am not sure where to download ML for the 7D on this site and is there instructions on how to install and use the firmware once it has been downloaded.
I do understand that what I am asking is quite easy for some of you on this forum, but as I say I am very new to this.
Many thanks
Mark
Just shot a little short and the best settings for bitrate for me with good image quality and audio working is the following:
VBR with -16 & Video Hacks on (Flush at 24, GOP at 1) AUDIO works enabled with these settings. ISO at 800-3200.
Awesome work again!
Best
Dave
Quote from: markymark on December 30, 2012, 06:02:10 PM
Hi, need a bit of help, I am very new to all this and own a 7D which I wish to do more with the HDR setting. At the moment the 7D only lets you take 3 images can this be increased with the ML firmware update and if so how many will it allow me to take ?. The 7D that I have has the Canon firmware updated to Ver. 2.0.0. Also I am not sure where to download ML for the 7D on this site and is there instructions on how to install and use the firmware once it has been downloaded.
I do understand that what I am asking is quite easy for some of you on this forum, but as I say I am very new to this.
Many thanks
Mark
Hi Mark, the answer to your questions are in the first post on this thread http://www.magiclantern.fm/forum/index.php?topic=3974 (http://www.magiclantern.fm/forum/index.php?topic=3974) ;)
The user guide is here http://wiki.magiclantern.fm/userguide (http://wiki.magiclantern.fm/userguide)
To get started...
Installation
1) Update camera firmware to 2.0.3
2) Format your CF card from the camera
3) Extract contents of ML .zip into your card's root folder
4) Run "firmware upgrade" once again
5) Voilà. Magic Lantern. (press DELETE for menu)
Quote from: markymark on December 30, 2012, 06:02:10 PMHi, need a bit of help, I am very new to all this and own a 7D which I wish to do more with the HDR setting. At the moment the 7D only lets you take 3 images can this be increased with the ML firmware update and if so how many will it allow me to take ?.
Yes - up to 9 shots. It's a great feature!
Quote from: g3gg0 on December 30, 2012, 11:48:41 AMyet i have to think about how to make this power-user feature normal-user-proof.
what about the others? are you using video hacks? do you see use in them?
For me, I'm mostly ok with the default video quality - however, I would like the option to engage a "higher quality" mode for important footage. So, I'm wondering if the feature should basically work something like the following:
A menu option called eg "Video Quality", which lets you set to "Canon Default", "Better", "High Detail" and "Custom" or whichever presets make sense in light of user-testing of what settings work for what application. Then a power user could either hit the Custom setting and get into all the specific bitrate parameters, or hit the Q button to see the settings for each preset and tweak/save accordingly - perhaps even create their own presets for their own use.
So basically - for me I'm personally not generally that interested in tweaking all the various bitrate settings to work out what works for me - simply the ability to toggle quickly to a "higher quality" mode for important or highly detailed footage is all I really require, with the ability to go in and tweak the settings if I really wanted to.
Quote from: beej on December 30, 2012, 07:56:38 PM
For me, I'm mostly ok with the default video quality - however, I would like the option to engage a "higher quality" mode for important footage. So, I'm wondering if the feature should basically work something like the following:
A menu option called eg "Video Quality", which lets you set to "Canon Default", "Better", "High Detail" and "Custom" or whichever presets make sense in light of user-testing of what settings work for what application. Then a power user could either hit the Custom setting and get into all the specific bitrate parameters, or hit the Q button to see the settings for each preset and tweak/save accordingly - perhaps even create their own presets for their own use.
So basically - for me I'm personally not generally that interested in tweaking all the various bitrate settings to work out what works for me - simply the ability to toggle quickly to a "higher quality" mode for important or highly detailed footage is all I really require, with the ability to go in and tweak the settings if I really wanted to.
Yes, very good idea. I would like to see also.
Quote from: _7D_ on December 30, 2012, 05:36:31 PM
Thank you guys for this awesome second alpha!
Maybe, I´ve found some little bugs.
The first one: I always get a strange sound, if I activate "ALO warning" in "Warnings for bad settings..."
The second one: Quality warning "Other than RAW" isn´t working. Is there a possibility to configure this like I need it? Maybe in the next alpha?
Can somebody confirm the two bugs?
ALO warning was buggy, it always makes false alarm. I've fixed it, it will be in the next release.
Raw warning works fine for me. If I turn off RAW then beeps and write a message.
First of all thank you for all the hard work on ML.
Unfortunatly I am feeling a bit stressy after I think I found out a bug :( . My autofocus doesn't work anymore after I tried the focus peaking benchmark in ML. The focus performance test started but ended immediatly with a beep and since then no autofocus anymore (also with another lens). I tried to re update the firmware of the camera but still no autofocus. Any help or tip is welcome.
OK I just found a workaround (erase all camera custom settings). One extra info for debugging: in the viewfinder the bracketing * kept blinking while I pressed the shutter half for focussing.
Quote from: Aldeme on December 30, 2012, 09:51:22 PM
First of all thank you for all the hard work on ML.
Unfortunatly I am feeling a bit stressy after I think I found out a bug :( . My autofocus doesn't work anymore after I tried the focus peaking benchmark in ML. The focus performance test started but ended immediatly with a beep and since then no autofocus anymore (also with another lens). I tried to re update the firmware of the camera but still no autofocus. Any help or tip is welcome.
OK I just found a workaround (erase all camera custom settings). One extra info for debugging: in the viewfinder the bracketing * kept blinking while I pressed the shutter half for focussing.
Similar happened with me, after I played with the ML, my autofocus custom settings have changed, I had have to set them again.
@Aldeme:
Canon menu -> C.Fn IV -> 1 -> PicStyle button
@Pelican:
thanks for your contribution. i really love the way it looks now.
due to the flood of space changes, i rejected your pull request and added it manually (https://bitbucket.org/hudson/magic-lantern/commits/c5e001352bb0)
maybe you should revert all your space changes to this changeset and continue from there.
I don't know if this is a bug (maybe a feat request), but today i've "presented" ML to a friend of mine (professional cameraman at cinecittà) with a 7D.
The card used for the demo was an historic 8MB card :D
ML worked and loaded but since there was the CARD FULL dialog on screen INFO button didn't worked for switching Canon's overlay mode, i suppose this is a canon behavior and we solved using his card for setting camera to no overlay mode, after that we had some test again with the card, after a brief explanation of ML menu he wanted it on his card ;)
During the showcase we had some hang with battery pull needed. I can't remember what was the cause since we tried almost all. If possible i'll make more test in the next days to try reproducing them.
Quote from: g3gg0 on December 30, 2012, 11:48:41 AM
what about the others? are you using video hacks? do you see use in them?
i can also put that code into a plugin to make sure its available to those who need it and hidden to those who dont.
Oh, yes, 97% of the time. On low ISO I would go long GOP at flush 24 and GOP 96 so I can record audio for sync in post. On High ISO, I would tend to use GOP at 1 because, even though a lot of my stationary tests couldn't prove this, to my eye, in real world shooting, after denoising, the noise on high ISO (say 12800) with long GOP seems to tend to blur the details a lot more compared to All-I (GOP at 1).
The 3% of the time is when I'm too lazy to set my flush and GOP and enable audio :D
Love the plugin idea. I hope there will be customizable presets in there that can ramp/customize the settings according to ISO.
Btw, why is it that audio recording only works properly at flush 24 or bitrate hacks off? (what are the GOP and flush for bitrate hacks off btw?)
Tried to compile for 7D but got this errors:
gdb.o: In function `gdb_task_stall':
gdb.c:(.text+0x4): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
collect2: ld returned 1 exit status
Quote from: g3gg0 on December 30, 2012, 11:43:18 PM
@Pelican:
thanks for your contribution. i really love the way it looks now.
due to the flood of space changes, i rejected your pull request and added it manually (https://bitbucket.org/hudson/magic-lantern/commits/c5e001352bb0 (https://bitbucket.org/hudson/magic-lantern/commits/c5e001352bb0))
maybe you should revert all your space changes to this changeset and continue from there.
Thanks!
Last night I had an idea how to speed up the load of help pages. (My camera looked like a cheap chinese toy with this slow screen refresh)
The main idea is to save the vram when the bmh is opened/displayed and next time if the loader finds saved vram, then it loads to the vram directly instead of loading the bmh. Of course we can create all of them in advance and put it in to the distribution.
It's lightspeed now, hundred times quicker even it moves more data. You can load and display all the 153 pages in 3 seconds... 8)
The disadvantage is the bigger doc size (its about 75 MB ~ 3 raw image size on 7D) but in the zip its only 3 MB instead of 2.5 MB (the bmh files) so it will bigger with only half megabyte.
I wanted to merge it right now, but I had to pull the changes, so I'll go home now and make it again.
The load and save is very simple:
void save_vram(const char * filename)
{
uint8_t* b = (uint8_t *)bmp_vram();
ASSERT(b);
if (!b) return;
FILE * file = FIO_CreateFile( filename );
if( file == INVALID_PTR )
return;
else
{
FIO_WriteFile(file, b, BMP_VRAM_SIZE);
FIO_CloseFile( file );
}
}
int load_vram(const char * filename)
{
uint8_t* b = (uint8_t *)bmp_vram();
ASSERT(b);
if (!b) return -1;
unsigned size;
if( FIO_GetFileSize( filename, &size ) != 0 )
return -1;
return read_file(filename, b, size);
}
And if you don't have any saved vram (page-xxx.vrm) in your doc folder than doesn't do anything at all.
It instantly works on all the cameras which has the same vram size as the 7D has.
Also I made a togglable page number display (with Set button) so you can't lost during browsing the help pages.
What do you think?
HAPPY NEW YEAR ALL!!!!
Thanks for the alpha 2, great work!! I've been using ML on my 600D and yesterday I tried it on my 7D and I wanted to test photographing fireworks with motion detection. I got it working on my 600D but on the 7D I could not set the shutter speed below 1/30 (wanted 2") in live view (needed for motion detection) I compared settings with my 600D, tried Exposure override but without luck. Am I missing something or is this a bug?
BR Nicke
Great work with ML for 7D so far, many thanks!
I've tried both Alpha1 and Alpha2 releases so far. The only major problem I've had in both releases is that a few times, when recording video (normal settings - no video hacks), the camera has hung when I end the recording with the start/stop button. Opening card door or power off didn't work - only removing battery helped. After putting the battery back in, everything is fine, except the video I was recording cannot be played.
Just wondering if anyone else has seen a similar issue?
(CF card was Kingston 32GB 600X and the lens was 50mm f1.8 in manual)
Hello,
Once again It seems it's my first Post here so: many thanks for your work!
Is there any way to compile a 7D ML with last changes/ contrib and how?
I would like to add the Hyperfocale/Near/Far/Actual distabces to the/my std LV view - is this doable or only via code changes?
Oh, yeah one more thing: HAPPY NEW YEAR!
Yes, you can build your own autoexec, but if you want to run it you have to set the boot flag on your camera.
See the starting as a developer topic for how to setup your machine to compile the code.
Hi All,
Many thanks for the info on how to install ML on my 7D, just a quick question am I right in saying that at the moment once I have installed ML on the 7D I need to keep the same CF card in and shoot with this in and once I have turned the camera off I need to go through the installation of ML again to use it ?
Many thanks
Mark
Quote from: markymark on January 01, 2013, 03:14:52 PM
Hi All,
Many thanks for the info on how to install ML on my 7D, just a quick question am I right in saying that at the moment once I have installed ML on the 7D I need to keep the same CF card in and shoot with this in and once I have turned the camera off I need to go through the installation of ML again to use it ?
Many thanks
Mark
That's right, each time you cut the power to your camera you will have to re-install Magic Lantern. Luckily it only takes a matter of seconds to do this. ;)
If you were to load ML then change CF cards your camera would cut the power when you open the card door, so re-installing would be required.
:)
Quote from: Pelican on January 01, 2013, 02:03:54 PM
Yes, you can build your own autoexec, but if you want to run it you have to set the boot flag on your camera.
See the starting as a developer topic for how to setup your machine to compile the code.
I can't compile the nightly, with the summon arm toolchain make all, make 600D, make 500D... works ok, "make clean; make 7D" gives me error in gdb.c:
gdb.o: In function `gdb_task_stall':
gdb.c:(.text+0x4): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
what is *ABS* section? I can't see nothing "strange" in gdb.c
Hi All,
okay have done the upgrade to the Canon firmware 2.0.3 and downloaded the ML firmware onto my pc, formatted the cf card in the camera, but now need to uzip the ML firmware into the route folder on the cf card, but which folder is the route folder I have
DCIM (and two other folders in this folder 100EOS7D & EOSMISC)
MISC
Many thanks
Mark
Quote from: markymark on January 01, 2013, 06:49:54 PM
Hi All,
okay have done the upgrade to the Canon firmware 2.0.3 and downloaded the ML firmware onto my pc, formatted the cf card in the camera, but now need to uzip the ML firmware into the route folder on the cf card, but which folder is the route folder I have
DCIM (and two other folders in this folder 100EOS7D & EOSMISC)
MISC
Many thanks
Mark
Is the letter of the card on win for example:
E:\misc\
E: is the root. misc and dcim are subfolder of root folder.
Quote from: scrax on January 01, 2013, 06:54:51 PM
Is the letter of the card on win for example:
E:\misc\
E: is the root. misc and dcim are subfolder of root folder.
When I put the CF card into my laptop in my computer it's coming up as EOS_DIGITAL (E:), so do I just uzip it straight onto E: (no need to put it in anyfolders ?)
Also is it just the MAGIC.FIR that I unzip on to the card or that and everything that is in the ML folder ?
Quote from: markymark on January 01, 2013, 07:02:50 PMdo I just uzip it straight onto E: (no need to put it in anyfolders ?)
Yes - that's what "root" means - the top level, not inside any folders.
Quote from: markymark on January 01, 2013, 07:02:50 PMAlso is it just the MAGIC.FIR that I unzip on to the card or that and everything that is in the ML folder ?
Step 2, Installation docs:
"Unzip
all of the files from Magic Lantern zip archive to the root of your card."
Just follow the docs exactly, don't change steps or second guess them... :)
okay uzipped all the files from the ML downloaded file onto the CF card placed in the camera went to firmware on the menu pressed set (current version is 2.0.3. Update press ok firmware up date program, sensor screen came up on back of screen and the red light by the cf door flashed. firmware ver. 2.0.3-ml-v2.3.next on the screen now, but don't see anything new :(
press TRASH! ;D
but maybe you should give a read to the guide too...
Hi all,
Just like to come out of the shadows,been lurking for a while now :-X , and thank g3gg0 for his time and effort in cracking the 7D as well as all the rest of the contributors who made this project happen ;). I dont really do any filming with my kit as i am a stills kind of person ::), but what ML has under the hood for my line of photography is just amazing and i am genuinely blown away by the choices on offer.
I would like to contribute some money to the cause, but cant find any donation links? I'm sure i seen them somewhere...
Thank-you all again,
Peace, Love, and a Happy New year.
:D
Quote from: markymark on January 01, 2013, 07:49:07 PM
okay uzipped all the files from the ML downloaded file onto the CF card placed in the camera went to firmware on the menu pressed set (current version is 2.0.3. Update press ok firmware up date program, sensor screen came up on back of screen and the red light by the cf door flashed. firmware ver. 2.0.3-ml-v2.3.next on the screen now, but don't see anything new :(
Ok, you're up and running. Now you need to learn how to use it. Press the Trash button, and read the docs :)
Quote from: SoulCatcher09 on January 01, 2013, 07:54:43 PM
I would like to contribute some money to the cause, but cant find any donation links? I'm sure i seen them somewhere...
Hi,
seems you have missed this recent article about actual situation of ML: http://www.magiclantern.fm/whats-new/78-news/145-happy-holidays-updates-inside
Quote from: SoulCatcher09 on January 01, 2013, 07:54:43 PMI would like to contribute some money to the cause, but cant find any donation links? I'm sure i seen them somewhere...
I think they said they disabled the donation links for now, as donations have funded the immediate needs of getting IDA licenses to help with development.
Quote from: beej on January 01, 2013, 07:58:56 PM
I think they said they disabled the donation links for now, as donations have funded the immediate needs of getting IDA licenses to help with development.
Ahh thanks for the info, will look out for when the team needs more donations.
Cheers
That's great thanks for being patient with me just need to test it out ;D
Quote from: SoulCatcher09 on January 01, 2013, 08:02:59 PM
Ahh thanks for the info, will look out for when the team needs more donations.
Cheers
In the meantime, please, report all your findings/problems so to help with development ;)
Hey guys,
I've shot a little short after doing some tests with the 7D and this is the result: http://www.youtube.com/watch?v=8KUsaJGe4jk
A little shortfilm called "The Visitor". I shot everything on a 7D with bitrates between 100-150mbps and all I-Frames. I really did see the difference in post.
Keep it up!
Just a follow up on this:-
Quote from: beej on December 28, 2012, 03:36:57 AMA question on rack focusing.
One slightly frustrating thing - when altering the steps to here value with the top scroll wheel, moving it fast (which you kinda have to do with a step size of 1 for it to go anywhere, as you want values of +100 or more) often comes off the parameter (especially if the soft-limit is reached, but it will often come off the parameter without that happening) - and then you are now scrolling fast through the menus. Not only that, but there is no way (I can see) of continuing to adjust the steps to here value without first zeroing it out and starting again. This makes setting up a rack focus operation quite painful, currently.
While this is all true, I've just discovered (duh!) that changing the focus steps using the top dial is not the only, and certainly not the best way of changing the parameter. Using the multi-controller instead moves the steps continuously, rapidly and smoothly, and doesn't "run off the end" in the same way the top dial does, which goes a long way into making the feature smooth to use.
Just in case anyone else is running into the same issue. I'm really going to be using the rack focus feature a lot (it is one of the features I really like on my Sony Z5, along with zoom and aperture ramping, but without that super-shallow depth of field it's far less sexy than a DSLR...).
Quote from: DaveVegas on January 01, 2013, 11:42:30 PMA little shortfilm called "The Visitor". I shot everything on a 7D with bitrates between 100-150mbps and all I-Frames. I really did see the difference in post.
Nice, Dave! I'm not going to ask about the opening shot... ;)
What was the difference in post you speak of? More flexibility in the grade? Or for VFX?
Nice work on the sound design too.
I'd really like us folks to boil down some preset settings for the bitrate feature, because at the moment I don't really understand what many of the settings are doing and sometimes judging the interplay of a few of these variables can be quite difficult to discern and understand the behaviour of...
Quote from: DaveVegas on January 01, 2013, 11:42:30 PM
A little shortfilm called "The Visitor". I shot everything on a 7D with bitrates between 100-150mbps and all I-Frames. I really did see the difference in post.
Nice one Dave! Looks great.
Quote from: beej on January 02, 2013, 05:59:20 AM
Nice, Dave! I'm not going to ask about the opening shot... ;)
Lol ;)
-flownez-
Thanks for the new update Christmas present!! Can't wait to try it out and pass on some $$ once the donation link is back and all the other Christmas presents are paid off.
Quote from: beej on January 02, 2013, 05:59:20 AM
Nice, Dave! I'm not going to ask about the opening shot... ;)
What do you mean? The short was shot in a ski-area and I went on a skilift with my 7D and just shot some trees :)
Quote from: beej on January 02, 2013, 05:59:20 AM
What was the difference in post you speak of? More flexibility in the grade? Or for VFX?
Nice work on the sound design too.
Thank you for the kind words! I definitely experienced a wider range of possibilities while grading, also the noise reduction didn't result in a mess as it usually does (Makes the image washed-out). The visual effects in this one are basically just some lens flares and these were as always.
Keep it up, higher bitrate definitely makes the post-process better!
By the way my settings were balanced, VBR, Q-16, Flush 24 (Because of sound) and GOP at 1 (That way you can edit faster without transcoding). Also forgot to mention I tested out some anamorphic lenses I got.
Thanks!
Best
Quote from: DaveVegas on January 02, 2013, 02:38:08 PM
What do you mean? The short was shot in a ski-area and I went on a skilift with my 7D and just shot some trees :)
"Right, I need this tracking shot through this car park. Ok guys, you can rig up the skit lift here..." :D
Quote from: DaveVegas on January 02, 2013, 02:38:08 PMI definitely experienced a wider range of possibilities while grading, also the noise reduction didn't result in a mess as it usually does
When you say noise reduction, are you doing this in post, and what ISO where you typically shooting at?
For me, while NR does get decent results, it's very easy to blur the image too much and lose detail, and the NR batch process is really processor intensive which is a bit of a pain.
Quote from: DaveVegas on January 02, 2013, 02:38:08 PMBy the way my settings were balanced, VBR, Q-16, Flush 24 (Because of sound) and GOP at 1
Thanks for that, I will give this stuff a try - I've just been reading through the bitrate monster thread to get some overview on the settings...
Hi Guys!
I've made some tests with ISO 6400 in my room. I used Q -16 and GOP 1. I started with a flush rate of 25 - I was able to record about 10-15 seconds. I wanted more so I decrased the flush rate to about 5. Now the strange thing: The buffer of my 7D was full after about 3 seconds. So - why is the second record shorter? Shouldn't it be a little bit longer than the first one?
Quote from: beej on January 02, 2013, 04:50:58 PM
"Right, I need this tracking shot through this car park. Ok guys, you can rig up the skit lift here..." :D
When you say noise reduction, are you doing this in post, and what ISO where you typically shooting at?
For me, while NR does get decent results, it's very easy to blur the image too much and lose detail, and the NR batch process is really processor intensive which is a bit of a pain.
Thanks for that, I will give this stuff a try - I've just been reading through the bitrate monster thread to get some overview on the settings...
I was shooting up to 3200 ISO and I used Neat Video noise reduction (best one available in my opinion) and it gave pretty good results.
Best!
Has anyone tried recording 720p at 60fps with audio?
I tried recording at 720p 50fps with audio and it completed recording up to 4gb successfully. Set the flush to 50 and GOP at 1.
But recording 720p at 60fps with audio, it seems one would need to set the flush to 60 which can't be done because the flush only goes up to 50. I tried setting it to 10, 24, 25, 30, and it would stop recording after a few seconds. GOP set at 1.
I've tried this with various CBR/VBR rate with the same results.
Can anyone confirm this?
I really liked the short Dave!! Inspired in Close Encounters I assume :P!! REALLY liked the camera movement when the character sees the light for the first time... And, of course, got a little scared in the end, haha..
I wanted to ask you something.. what lenses did you use?? Because I gotta say the texture of the movie was nothing like digital.. you achieved a very organic texture.. I was wondering.. is it the color correction? The bitrate did increase the quality?? Or is it just the great lighting and everything else??
Really happy if you share any tips!!
Good bye and thank you!!! Cheers from Argentina!
First: Thanks for this beautifull piece of code:-)
2: I noticed a strange colorshift when using the magic zoom and move it around. At some positions its normal (like it always was in alpha 1) and in between it shows a bluish/blackandwhite-like picture in the box. Did anyone else notice this?
3: I was very happy to see, that autorestart is in alpha 2 because this is a feature i need for documentary situations and things like live-concerts etc. but i tried it and it always stops after one clip. Is this intended? Or when will this feature gets activated? :-)
Thank you for your time and efforts:
Maurice
Quote from: moemusic on January 03, 2013, 10:44:36 AM
2: I noticed a strange colorshift when using the magic zoom and move it around. At some positions its normal (like it always was in alpha 1) and in between it shows a bluish/blackandwhite-like picture in the box. Did anyone else notice this?
Hmm... I can't seem to reproduce this. What are your magic zoom settings? Did you modify the liveview white balance settings too? (not the WB Shift setting, the one in ML for liveview) Plus, it still flickers at 60fps
Quote from: moemusic on January 03, 2013, 10:44:36 AM
3: I was very happy to see, that autorestart is in alpha 2 because this is a feature i need for documentary situations and things like live-concerts etc. but i tried it and it always stops after one clip. Is this intended? Or when will this feature gets activated? :-)
Yep, it wouldn't autorestart on mine either.
Quote from: g3gg0 on December 23, 2012, 11:30:14 PM
Known issues:
* You have to reload Magic Lantern every time you use it. (this is intentional)
* when using HDMI output, frame drops may happen (to be verified)
* make sure your battery/adaptor is chipped, else canon menu will abort "firmware update" (= loading ML)
* movie restart and video effects menus visible but not working
;)
Thank you for the kind words, Tony! A little bit :P
Actually I shot this on a Arri Alexa. lol joke :D
Even though the bitrate helps you achieve better results in post the most important factor is the traditional on set cinematography. I just try to get as much as possible in camera (with lights) and everything in post just enhances that experience.
Also I used Marvel's Picture Style :)
Thanks again!
Best
Dave
Quote from: tonybeccar on January 03, 2013, 10:09:59 AM
I really liked the short Dave!! Inspired in Close Encounters I assume :P!! REALLY liked the camera movement when the character sees the light for the first time... And, of course, got a little scared in the end, haha..
I wanted to ask you something.. what lenses did you use?? Because I gotta say the texture of the movie was nothing like digital.. you achieved a very organic texture.. I was wondering.. is it the color correction? The bitrate did increase the quality?? Or is it just the great lighting and everything else??
Really happy if you share any tips!!
Good bye and thank you!!! Cheers from Argentina!
* movie restart and video effects menus visible but not working
ah, sorry, i thought i'd read everything...
Is it possible for the next release?
Has anyone made experiences with full hdmi-out?
Thanks!
Yes...please...fullframe (1920x1080) clean HDMI-out....pleeeease.
So I just downloaded and updated everything so I'm ready to put ML onto my 7D, but I'm unsure as to how you remove it completely from the camera. Could you please clarify?
Quote from: Tim French on January 04, 2013, 09:43:39 PM
So I just downloaded and updated everything so I'm ready to put ML onto my 7D, but I'm unsure as to how you remove it completely from the camera. Could you please clarify?
Turn off the camera and is goes out of memory. To completely get rid of it you will have to delete if from your CF card.
Quote from: kenb129 on January 04, 2013, 09:45:18 PM
Turn off the camera and is goes out of memory. To completely get rid of it you will have to delete if from your CF card.
Mind blown. >Ojo<
o
Hi all,
first of all, many thanks to all the developers, i just got my 7d and ML looks great so far.
just one issue I couldn't find any reference to in the manual or release notes:
i want to use silent pictures to play with time lapse videos until FPS override is ready, but I can't take Hi res pictures. is that option not enabled yet or am I'm missing something?
and again thanks for all the hard work
itay
hi, welcome.
it's not enabled yet as it showed some weird offsets.
Hi all,
This is my first post here and i'd like start saying TANKS to all the ML team for this beautiful hack,
I already have the alpha 1 and the thing that makes me curious about this new release is the possibilty of crack up the bitrate.
Has anyone here did a comparison test of diferent bit rates to see if there are noticeable improvements?
Sorry if this question has been asked yet, i surely missed. The only thing i saw was the wonderfully looking short film made by DaveVegas.
Until now the Alfa 2 rules. Its the best !!!
It's possible to get out uncompressed HDMI from the 7D with Magic Lantern? And more then the 60fps? If not why?
Thanks more one time for existing people that change the rout of man kind, THANK YOU.
Quote from: arrinkiiii on January 06, 2013, 12:46:51 AM
It's possible to get out uncompressed HDMI from the 7D with Magic Lantern? And more then the 60fps? If not why?
you are welcome.
no, no, performance problems
Quote from: g3gg0 on January 06, 2013, 02:22:49 AM
you are welcome.
no, no, performance problems
Damn.... even with Dual Digic!!! So, about rising quality in the beautiful 7D just the bitrate modification? No clean HDMI, no more then 60fps greeeeee.... =))
Thank for the fast response and for the wonderful work that you and the rest of the team have done. Much appreciated, thank you. Just for curiosity and for the rest of the guys that have a 7D that are waiting, can you give us wend came the next alfa with FPS override?
fps patching is basically working, but crashing after some time for unknown reason.
so its useless for now.
as the most important stuff is in alpha 2 already, i am focusing on infrastructural things.
Any hope for having HDR video soon?
Quote from: ted ramasola on January 06, 2013, 10:52:16 AM
Any hope for having HDR video soon?
If I'm reading the repo push/pull right, they fixed the thingy that's making it not work. So, you can either compile your own firmware right now, or wait for the next alpha(/beta?) for this.
I've been trying to set up my machine to compile the firmware following that instruction thingy. I think I've just beginning to understand what I was supposed to do in the first line.
Btw, the whole firmware is written in C, right?
its all in C, yes.
HDR video on 7D is not possible yet. sorry.
I see. Thanks for the update
Quote from: g3gg0 on January 06, 2013, 09:05:19 AM
fps patching is basically working, but crashing after some time for unknown reason.
so its useless for now.
as the most important stuff is in alpha 2 already, i am focusing on infrastructural things.
Yes =)) All good for me. Fps and HDR video will be very nice features, indeed. Im from the time of basic and pascal language (dinosaur times) and im trying to understand how this work but usseless, can't understand, wood like to help more the team.
Let se, wen i hit the rec button i start to record, the information pass to the codec that compress this information and then go to the card to record... my question is, is not more less processor work if go's directly to the out put (HDMI) with out compressing? And with external recorder record that information? Any ways, for sure if not exist this function is because its not possible and i believe you gays.
I want to help but its like having my hands tight. Tell me if a can do anything more. Im from Portugal, i dont own a 7D it's from my boss that he let me work with. If we now that im putting Magic Lantern in is 7D is just going fire me (hihihi) but i dont care, Magic Lantern have change the game, have change the work, have change the mind of people... in resume, it have change the path of mankind in the video and photography world. (sorry go so philosophic but is not everything about machines but also so about society. And here is a example of anti-capitalism, with out greedy, and every one's works together in one direction.
Thanks again to Trammell Hudson, Al3x and all the team behind this community and especial thanks to you, to G3gg0. For work in the 7D.
Quote from: feureau on January 06, 2013, 11:03:31 AM
If I'm reading the repo push/pull right, they fixed the thingy that's making it not work. So, you can either compile your own firmware right now, or wait for the next alpha(/beta?) for this.
I've been trying to set up my machine to compile the firmware following that instruction thingy. I think I've just beginning to understand what I was supposed to do in the first line.
Btw, the whole firmware is written in C, right?
Hi Feureau, how you can do that? Making a new firmware for your 7D for the fps override?
Best regards
you can not do it at the moment. sorry.
Quote from: arrinkiiii on January 06, 2013, 02:56:03 PM
Hi Feureau, how you can do that? Making a new firmware for your 7D for the fps override?
Best regards
I'm just following the set up your computer for ml development thread. I'm not doing anything with the firmware, just trying to compile it for fun. For the fps override, you'd have to wait until the wizards do their thing with the thingamajig.
Quote from: feureau on January 06, 2013, 05:03:40 PM
I'm just following the set up your computer for ml development thread. I'm not doing anything with the firmware, just trying to compile it for fun. For the fps override, you'd have to wait until the wizards do their thing with the thingamajig.
ok, thanks, i will wait for next version of ML. Meanwhile im making some clips and testing the alfa2, for what i know to change and work in this new version everything is alright. One thing that im not testing is the bitrate... Im reading for understand better, for wend i make some changes i know what im doing...
Hi!
I`ve seen a new download for the 7D on https://bitbucket.org/hudson/magic-lantern/downloads (https://bitbucket.org/hudson/magic-lantern/downloads). This version was uploaded a few minutes ago. What´s new? Is this the "old" version (Alpha 2 from December) with a few bugfixes? That would be very nice!
Greets
its the alpha 2. nothing new.
Ah okay, thanks... I only thought because of the "7 minutes ago" and "0 Downloads"...
"Audio tags"
How do you get to the Audio tags? I can't find it anywhere? This would be an awesome feature.
I found it under Audio/Sound Recorder/Voice Tags
But it only works if you have quick review enabled, and only good directly after you take the image. It would be great if you could tag them after you've already taken all your images and your reviewing them all.
Don't get me wrong, this has opend up my 7D, and I feel as though I have a new camera.
nice to hear. but thats not a 7D specific wish.
so the right forum is "feature requests".
Quote from: ricksieminski on January 13, 2013, 08:31:04 PM
I found it under Audio/Sound Recorder/Voice Tags
But it only works if you have quick review enabled, and only good directly after you take the image. It would be great if you could tag them after you've already taken all your images and your reviewing them all.
Don't get me wrong, this has opend up my 7D, and I feel as though I have a new camera.
I've asked for that too, the problem is to find a way to know wich pic is show in play mode.
i don't know if this is a bug.
when i shoot HDR 9 frames and i use live view the camera isn't taking the 9th picture.
happend a couple of times know. with live view of no problems
best regards sander
Quote from: madebysander on January 15, 2013, 11:11:01 AM
i don't know if this is a bug.
when i shoot HDR 9 frames and i use live view the camera isn't taking the 9th picture.
happend a couple of times know. with live view of no problems
best regards sander
Maybe I'm wrong but I thought the idea of ML HDR was that the software analyses the scene from the first exposure and then takes however many shots are required to capture the entire dynamic range. I don't think there is a hard and fast number of exposures it will take every time.
I tried it yesterday inside a house and it refused to take more than three exposures because that was all the scene needed.
Again, I could be wrong though. ;)
(btw I like your HDR work, nice style you have there)
this is when you set "Auto" frames.
then ML will check the dynamic range and continue shooting as long we lost dynamic.
can you tell me the exact settings and way to reproduce?
i have sent the exif in pm
well, i talked about ML settings.
i could not reproduce the problem. i always get 9 images if i set it to 9
Hello :)
i'm sorry to say this but.... your work is a m a z i n g!
Thanks g3gg0!!!!!
I can't wait to test more functions, and I hope you're havin fun with your brand new IDA licenses ;D
And btw, haven't found any bug or glitch yet.
I maybe noticed a little more heat produced by the CPU (CF card is hotter than usual when removing it), especially with liveview or videos.
:-*
First of all
g3gg0 and the ML Team THANK YOU for all the work on 7D.
I have two minor reports - questions:
1. in Movie settings, REC/STBY notif: beeps - video is recording, but no sound recording (is it possible to turn mike on)
2. when focus ring is used for triggering magic zoom - nothing happens
(tested with Canon 50mm f1,4 USM)
Keep On Rockin'
Quote from: Mare on January 17, 2013, 11:39:58 PM
1. in Movie settings, REC/STBY notif: beeps - video is recording, but no sound recording (is it possible to turn mike on)
2. when focus ring is used for triggering magic zoom - nothing happens
(tested with Canon 50mm f1,4 USM)
1) i dont understand this. what beeps?
2) this is dependent on the lens. some report focusing changes, some not iirc.
Hi
Under menu Movie is REC/STBY notification, option "beeps" (at start and the end of recording is short sound like beep).
Works fine, but there is no sound recording.
I hope that helps.
Best regards
You mean no audio being recorded in the video, or no beep recorded in the audio?
If the problem is no audio being recorded, you might want to check your audio setting in the regular audio enable/disable auto/manual level setting in the canon menu. The audio also gets disabled when you enable the video hacks settings (to set the flush and GOP thingy).
Well, sound recording on other settings work fine, just when you choose beep notification for start or stop recording, you can hear the beep (that's OK), video is recording, but no sound recording.
It would be fine and much easier for sync audio with video in post, because now with ML :D I can trigger (start and stop) video with remote controller, audio is anyway rec by other device.
:)
Not sure whether this is a bug, a general ML implementation detail or whatever, but:
If I set Movie Rec Start/Stop to a half shutter press, it works as expected. However, I have back-button focus setup (AE Lock Button -> Metering & AF Start) and do not have focus on the shutter button. If I hold the "*" button to focus, on release the camera will go into record mode - in short, when movie start/stop is set to half-shutter, a back-button focus operation will also cause a movie start/stop operation.
This is contrary to the behaviour I would expect :)
I would like the back button to not trigger movie start/stop, so I can focus as usual without starting/stopping recording...
Also - I wish quick erase would also work for movie files, it only seems to work for picture files...
It's probable that both buttons send the same event code. If it so, there's little we can do
Quote from: g3gg0 on January 16, 2013, 01:04:56 AM
well, i talked about ML settings.
i could not reproduce the problem. i always get 9 images if i set it to 9
shoot in M-mode
ML settings
bracket type exposure
frames 9
ev 1.5
sequence - + -- ++
iso shifting of
post scripting of
camera setting iso 200
F9
live mode on
focus with live mode
then lens on manual focus
and push the shutter button.
between shot 7 and 8 it beeps once same beep as minute counter on bulb.
and after shot nr 8 it stop.
Quote from: madebysander on January 19, 2013, 10:42:20 AM
between shot 7 and 8 it beeps once same beep as minute counter on bulb.
and after shot nr 8 it stop.
I tried this settings three times on different lighting conditions, but I'm still getting 9 out of 9 frames. Can you try fresh-install a newly downloaded ML to your card? (format the card, copy newly downloaded alpha 2 into card) and see if it still has this problem?
Quote from: g3gg0 on January 16, 2013, 01:04:56 AM
well, i talked about ML settings.
i could not reproduce the problem. i always get 9 images if i set it to 9
Quote from: feureau on January 20, 2013, 12:14:01 AM
I tried this settings three times on different lighting conditions, but I'm still getting 9 out of 9 frames. Can you try fresh-install a newly downloaded ML to your card? (format the card, copy newly downloaded alpha 2 into card) and see if it still has this problem?
Hi guys,
I've registered, because g3gg0 and feureau could not reproduce a bug/glitch found by madebysander.
YES, my 7D has the same glitch too.
v.2.3 built on 2012-12-23 23:12:12 by g3gg0
It is not an "Auto"-frame, nor 9th-frame problem.
Something, working in Live-View by changing from M to BULB is responsible for this glitch.
Explanation:
1) It is not a 100% reproducible bug (some time 20% some time 50%), but annoying. Therefore, I think reinstall will not help.
The glitch occurs ONLY in Live-View mode if ML need to change the mode for example from M to BULB after you reach 30 second-limit.
The workaround for me -> dont use Live-View mode after 30sec-limit.
To have a chance to catch the bug you need to shoot (in Live-View mode only) even TWO photos with change to BULB in between.
You dont need to shoot 9 times.
Example:
t1=30sec in M (lens cap closed)
bracket type: exposure
frames: 2
ev increment: 1ev
sequence: 0 + ++
iso shifting: off
Try it 5 times to be sure.
UPDATE
Very repeatable is following:
If you set t1=30, f=11 in M (lens cap closed) you get t2=64sec in ocular-mode, but 63sec in Liveview-mode.
One second is some-how lost.
If bracketing breaks, there is an additional accoustic warning.
Hope I could help.
This bug has something to do with memory, threads and communication in between .. you know.
You are great, guys! It is not easy to hack a dual-cpu system .. very big respect and deep gratitude!
2) I dont use ALO. Newertheless, I receive warnings about "ALO is enabled". Warning-settings are on, of course.
It is interesting to see warnings, but not this one. Is it a bug?
UPDATE: It is a bug. http://www.magiclantern.fm/forum/index.php?topic=3974.75
Because I always get this warning by HDR bracketing glitch, could they be correlated to each other?
3) Why can I set only 9 HDR-frames, but not as in ML2.3 (non-7D) unlimited? If you can 9, why you cannt 50 in 7D?
4) Why is bracketing in ML slower than fast canon bracketing?
Thank you guys, again!
hi, thanks for that detailed explanation.
will check tonight again.
i will answer some of your questions:
3) this seem to have changed since v2.3 and is not 7D-specific.
to be honest - why do you need more than 9 brackets?
if you do HDR, you normally would need up to 5 or 7 iirc (or let ML decide it automatically)
4) canon knows how to tell the correct devices what to to in which order and how fast.
we are basically looking if an image was taken and then shoot the next one.
but alex found out some interesting stuff and improved that for 5D3 already.
Quote from: g3gg0 on January 20, 2013, 01:24:32 PM
hi, thanks for that detailed explanation.
will check tonight again.
i will answer some of your questions:
3) this seem to have changed since v2.3 and is not 7D-specific.
to be honest - why do you need more than 9 brackets?
if you do HDR, you normally would need up to 5 or 7 iirc (or let ML decide it automatically)
4) canon knows how to tell the correct devices what to to in which order and how fast.
we are basically looking if an image was taken and then shoot the next one.
but alex found out some interesting stuff and improved that for 5D3 already.
Thank you for your fast answer!
3) Bad news if it is so. But for 2.3 is reported "Number of bracketed shots: unlimited."
http://www.magiclantern.fm/releasenotes
I need this feature to be sure to catch REALLY full light available in small 0.5-1EV (to minimize noise) stops.
And then develop photos and play with them as I wish.
To make an artifical look for example.
If you have in one situation a very big difference in shadows and lighs (chandelier, lustre ..)
you will have more then 30 EV stops inbetween to catch vacuum-tube coil and deepest room schadows.
The limited possibilities of displays and eyes has nothing to do with, it is about security, time saving and artifical choise of lights.
I think it is great to have possibility to transform the night to the day and sometimes something inbetween.
And for a non-moving objects I like to do the job fully automatically and simultaneously be fully sure about the result,
because you can always delete taken photos, but you cannt make the same new scene.
4) It is really great! Thank you very much for your work!
Have nice day!
In autodetect mode, the number of frames is unlimited (as many as needed). Or, edit your config file and place 100 frames if you really need that.
Quote from: a1ex on January 20, 2013, 02:32:00 PM
In autodetect mode, the number of frames is unlimited (as many as needed). Or, edit your config file and place 100 frames if you really need that.
Thank you!
I am very new user of ML.
Which config is it?
Could you give a step-to-step procedure or what should I search for?
Btw, how can be autodetect mode unlimited (as many as needed)?
How can I set, that for example 99,9999% but not 99,0% of light will be saved?
Quote from: a1ex on January 20, 2013, 02:32:00 PM
In autodetect mode, the number of frames is unlimited (as many as needed). Or, edit your config file and place 100 frames if you really need that.
Found it for config, thank you!
But can you recompile the sources, to set it permanetly up to for example 0-99?
Btw, do I need always PC to change config file now?
There is no parameter editor in 7D.
Quote from: a1ex on January 20, 2013, 02:32:00 PM
In autodetect mode, the number of frames is unlimited (as many as needed). Or, edit your config file and place 100 frames if you really need that.
Ooh! This is neat!
I opened it up. Is there a h264 setting I can add for custom enable bitrate hacks, flush, and GOP settings?
Thanks
g3gg0, Hello!
Please tell me, when it is expected the new version, at least roughly :)) Love your work, soon I will have PayPal, I will make a donation.
Please add the new version of a full opportunity to work with silent pictures.
Some rumors said that 7D has a firmware update limit, is it true?
I want to turn off AGC while recording.... :'(
The only limit I'm aware of: Canon doesn't support downgrading firmware v2.x back to v1.x.
Ciao, Walter
Hi,
there is no plan for the next alpha.
Quote from: Walter Schulz on January 23, 2013, 09:08:59 AM
The only limit I'm aware of: Canon doesn't support downgrading firmware v2.x back to v1.x.
Ciao, Walter
That's not correct, you can downgrade with EOS Utility.
Quote from: Pelican on January 23, 2013, 04:18:00 PM
That's not correct, you can downgrade with EOS Utility.
No, you can't, at least not changing the version.
If you've upgraded to 2.x you're no longer able to downgrade to 1.x, sure not with EOS Utility, checked it time ago.
You can only downgrade whitin the same version, for example you can downgrade from 2.0.3 to 2.0.1.
About the number of firmware upgrades I remember I've read on Magic Lantern site, months ago, that they did too many firmware upgrades on the 7D, used for test/development, and suddenly the camera refused to do other upgrades so maybe there's really a maximun number of firmware upgrades (probably higher than needed for standard users waiting only for official updates but not so higher for developers).
Angelo
Quote from: angelom on January 23, 2013, 05:00:21 PM
No, you can't, at least not changing the version.
If you've upgraded to 2.x you're no longer able to downgrade to 1.x, sure not with EOS Utility, checked it time ago.
You can only downgrade whitin the same version, for example you can downgrade from 2.0.3 to 2.0.1.
I repeat, that is not correct, I did it a few times without any problem (from 2.x.x to 1.x.x).
Quote from: angelom on January 23, 2013, 05:00:21 PM
About the number of firmware upgrades I remember I've read on Magic Lantern site, months ago, that they d id too many firmware upgrades on the 7D, used for test/development, and suddenly the camera refused to do other upgrades so maybe there's really a maximun number of firmware upgrades (probably higher than needed for standard users waiting only for official updates but not so higher for developers).
Maybe there is something, but I did so many fw upgrade in the last three years so I should reach that limit but I didn't.
I can imagine for example a failed fw upgrade counter, but I don't believe if there is a limit for the normal fw upgrades.
Quote from: Pelican on January 23, 2013, 05:30:31 PM
I repeat, that is not correct, I did it a few times without any problem (from 2.x.x to 1.x.x).
This sound very strange, myself and all the people I know that tried many times to downgrade the 7d from 2.x to 1.x were unable to do so, there was a test that we did whitin a photography forum and all owners got the same result.
You're the very first one I hear that was able to do that...
Quote
Maybe there is something, but I did so many fw upgrade in the last three years so I should reach that limit but I didn't.
I can imagine for example a failed fw upgrade counter, but I don't believe if there is a limit for the normal fw upgrades.
Maybe, but only Canon knows for sure.
Anyway let's go ahead with Alpha 2 testing! 8)
Quote from: angelom on January 23, 2013, 06:44:13 PM
This sound very strange, myself and all the people I know that tried many times to downgrade the 7d from 2.x to 1.x were unable to do so, there was a test that we did whitin a photography forum and all owners got the same result.
He is not the only one. Try using older EOSUtility versions like 2.10.x.
http://www.canonrumors.com/forum/index.php?topic=8646.msg157053#msg157053
Ciao, Walter
Quote from: g3gg0 on January 23, 2013, 01:17:39 PM
Hi,
there is no plan for the next alpha.
So, the next one will be a "final build"? :D like, unified with the rest of the ML family? :P
as said, there is no plan. we will see what comes next. i have no clue :)
I got an idea.. Lets figure out how to use an iPhone or iPad as monitor.. wireless :-D fullHD of cause ;D
And drink some beers?
Quote from: g3gg0 on January 23, 2013, 09:27:29 PM
as said, there is no plan. we will see what comes next. i have no clue :)
Quote from: Walter Schulz on January 23, 2013, 07:19:04 PM
He is not the only one. Try using older EOSUtility versions like 2.10.x.
http://www.canonrumors.com/forum/index.php?topic=8646.msg157053#msg157053
Ciao, Walter
Tests were did with 2.9 and 2.10 versions, if not even older, as 2.11 was not available at that time, no luck.
But we're off topic here.
Quote from: Pelican on January 23, 2013, 05:30:31 PM
I can imagine for example a failed fw upgrade counter, but I don't believe if there is a limit for the normal fw upgrades.
I'm pretty sure that I read that from Trammel somewhere too. At first it looked like a firmware counter but then I remember reading that there was not a limit in firmware updates but in failed updates (and that counter could be also on all other camera for what I know)
Quote from: g3gg0 on January 23, 2013, 09:27:29 PM
as said, there is no plan. we will see what comes next. i have no clue :)
Hello g3gg0,
Is it not safe yet to enable autoboot up of ML in your next release?
Thanks for your efforts,
Ted
So I booted up ML for the first time on my 7D. I followed all directions accordingly. It seemed to install, but I can't access the ML menu, and at this point I'd just like to take whatever ML put on my camera off until a the stable build comes out. But since I can't access the menu I can't do a full uninstall. Maybe it never actually installed?
Can anyone experienced offer me some insight?
Alpha builds don't touch anything in the camera. You can simply delete the files from the card
Glorious. Thank you. I was having one of those senior moments were you think you've done something terribly wrong with a technology you don't understand.
I'm a big fan of ML but I not recommend to anybody to use 7DML for anything except testing.
I'm using it from the beginning (from autoexec.bin) and I took about 20.000 images with it but it is not safe for production work, I lost a lot of good actions because somehow the camera's settings changed. So before a final or a beta version we should fix those things.
(It's not a complain, I know what I'm doing, I took the risk to use the ML on my camera.)
which settings changed?
Hi all
Thanks to the devs for extending the possibilities of my 7D.
I have experienced one bug. When engaging the focus peaking feature in live view, the camera seems to reboot after one minute or so. Happened twice. Is this a known issue?
The focus peaking overlay also seems "noisy". Would it be an idea to apply median filtering or some other "clustering" of sharp pixels?
best regards
.h
There's very little CPU power for real-time focus peaking; if you can optimize it to be fast enough and also use median filtering (or whatever other algorithm), be my guest and give it a try.
the new peaking is now very nice. very little slowdown on 600D. the blinking dots peaking is all over the place. suprised its crashing on 7d as 600d is technically lower, is it not?
Probably in movie mode, it is.
ML digital iso (digic) in the suboption of iso is not operating normally.
Even if it changes a value, brightness does not change.
even if it checks a recorded thing -- the same :-[
I shoot a lot of video with my 7D. I use a sennheiser wireles microphoneset and record the audio on my Zoom because when I record audio on the 7D there always is a hiss ons the background. This is a well known problem with de 7D. AGC is probably the reason for this problem. ML doesn't have the option to shut off the AGC I believe, maybe in a next version. I would be great. Has anyons experienced this problem as well?
Peter
Since canon firmware 2.0 you can deactivate AGC on your 7D!
I dont believe you can turn AGC off with 2.0.3. You can adjust audiolevels, but there remains a hiss because of the acg....
You can eliminate hiss and other sound anomalies in post production with gain and EQu and will be ok. AGC can produce little hiss, but is almost not noticeable, the main problem of AGC is that in some situations is out of control, for example: very loud environment. If you have manual control over audio levels there is no more auto gain level.
Sorry for my bad English
Hi Guys!
I would really like to be on the current status, so I´d like to compile the code by myself. But I think I don´t have the necessary knowledge.
So - can anybody maybe compile the newest code and upload it anywhere? That would be so fantastic!
Greets, _7D_
as we are currently in alpha state, that is limited to FIR booting ("Firmware Upgrade" functinality), releases can just be made by us.
you cannot compile it on your own yet.
Wait, so pelican said they've been using it with autoexec.bin. Doesn't this means that you have to compile the alpha yourself to do this?
As I understand it, FIRs must be signed with some encryption keys that only some of the devs have to avoid copyright violation thing, but users are free to compile autoexec.bin (I think means with bootflag enabled to auto load ML everytime you turn on the camera)
I've been playing with an ubuntu VM following the getting ready for development guide, does this mean the two 7D folders I pulled with the rest of ML from bitbucket won't compile or something?
There is a developer FIR that enables the bootflag: http://magiclantern.wikia.com/wiki/7D_support (on 1.2.3 firmware).
There are a few things unsolved for the autoexec version, so at the moment it's more difficult to get it running, compared to the single digic cameras.
Quote from: g3gg0 on January 27, 2013, 03:53:25 PM
as we are currently in alpha state, that is limited to FIR booting ("Firmware Upgrade" functinality), releases can just be made by us.
you cannot compile it on your own yet.
Could you please release a dev kit so I can compile the newer Bulb Ramping function from unified? I am using it with 5D3 and work fairly good, but on 7D I have problems as noted here: http://www.magiclantern.fm/forum/index.php?topic=4259.0
Quote from: a1ex on January 28, 2013, 08:12:41 AM
There is a developer FIR that enables the bootflag: http://magiclantern.wikia.com/wiki/7D_support (on 1.2.3 firmware).
There are a few things unsolved for the autoexec version, so at the moment it's more difficult to get it running, compared to the single digic cameras.
Ah, I see. At any rate, I've been enjoying ML so much lately. The grassroot effort side alone made me more curious about programming (I've been using http://www.computerscienceforeveryone.com/) and figuring out setting up my own VM with all the stuff for ML has been fun. :D
That being said, I only wanted a 7D ML that can record video in All-I by default. Apparently there's no setting for this in the config file either, so I guess it has to be compiled from source. I hope it wouldn't be too much to ask for a custom build with minor tweaks like this? :D Please? Just video hack on with GOP at 1 by default.
That reminds me, is it possible to raise the flush to 60? Apparently this would allow 720p recording at 60 fps with audio.
Otherwise, I think it'd be great if there could be a dev kit to let us to compile custom ML :D Would be fun to learn all this stuff.
Thanks for all the hard work!
g3gg0
Hi! Please tell me when a new version? I'd like to try the new features! Thank you! With best wishes, Vladislav
g3gg0,
happy new year to the man who was Santa for so many of us last year! :-)
Yes please, can you estimate if and when loading ML from within the camerea will be available? As the BlackMagic Cinema Camera gets delivered so slowely I guess many of us will be happy to use their 7D with ML.
But as I'm going to Australia in April I'm a bit afraid ML will be not as useful to me as it could as keeping the camera running all the time will shurely heat it up too much down under (had this problem twice before in Oz when I did interviews and had to stop inbetween as the 7D turned too hot although it was kept off at all times not necessarily running).
Thanks a lot for all your efforts so far!
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.
On that note, it seems the 7D development is not going forward as frenzy as the other ones anymore. (5D3, 6D, EOS-M) You see a lot of updates on the threads and bitbucket for those, but rarely on the 7D anymore. It's not even on nightly build.
With g3gg0 stating that there are no further plans and no news, I wonder if it's going back into hibernation like before?
But still, I'm saying this just out of curiosity and because I love the whole ML on 7D thing. No pressure to the devs or anything. There is one thing I have to say on the whole ML thing though: ML availability has become one of the top concerns on choosing future canon bodies for me. I most likely won't buy any more canon bodies that hasn't been properly ML'd. It's that important, and I'm really grateful for all the work done.
hey i'm getting an error when i try to download the ML 2.0.3 alpha for 7D. am i doing something wrong? it pops up saying:
Forbidden
You don't have permission to access /pub_files/17248a00956f1e932457094756b2a3ba/magiclantern_7D_203_Alpha2.zip on this server.
Apache/2.2.14 (Ubuntu) Server at upload.g3gg0.de Port 80
what should i do? can someone help with this?
I'll go back home at the next week, and I want to spend more time with 7DML developing.
Quote from: Pelican on February 06, 2013, 09:39:22 PM
I'll go back home at the next week, and I want to spend more time with 7DML developing.
Hi Pelican, if I don't break any rules I could put for a limited period of time the Alpha2 203 on a server onine
fixed ;)
Quote from: feureau on February 06, 2013, 06:00:35 AM
On that note, it seems the 7D development is not going forward as frenzy as the other ones anymore. (5D3, 6D, EOS-M) You see a lot of updates on the threads and bitbucket for those, but rarely on the 7D anymore. It's not even on nightly build.
With g3gg0 stating that there are no further plans and no news, I wonder if it's going back into hibernation like before?
But still, I'm saying this just out of curiosity and because I love the whole ML on 7D thing. No pressure to the devs or anything. There is one thing I have to say on the whole ML thing though: ML availability has become one of the top concerns on choosing future canon bodies for me. I most likely won't buy any more canon bodies that hasn't been properly ML'd. It's that important, and I'm really grateful for all the work done.
Just a thought, some times when you're changing big chunks of code, you dont commit anything for days even if you make progress because you could break the build or leave the program inconsistent. Maybe that's the case. i hope :)
there will be a new 7D release as soon the current changes to menu etc etc etc are done.
you dont want a buggy menu i think...
i am investigating loading from autoexec.bin the last 3 weeks.
its not possible that easy, so it will take its time.
Hello to you all, I'm an italian student I study cinema director and I'm here for my first post so I wish to say hello to anyone! :)
I have posted here in the 7D ML thread because I have a question about 7D with magic lantern: I have not this DSLR but my teacher do have it. I have talked about this firmware to him a lot of times to let him know about this 'meraviglia' so at the end he asked to me to get information about how to try it. I belive I can help him to do it installing the firmware by following your tutorials and many guide around the web (youtube, etc, etc...).
I need to know if possible: can the current ML firmware for 7D archive the possibility to have custom bitrate? I have explained to my teacher that Magic Lanter allow the user to select custom bitrate to have some kind of "raw" files, I said him that having a super bitrate allow the filmmaker to work in post processing without the fear to loose in detail after having done the job. Can we do it with 7D and ML aready?
Is the firmware almost stable to install it to the 7D of my teacher (I risk my head eheheh)?
Thanks a lot for your help and having a good day,
Dan :)
Quote from: Brawl on February 07, 2013, 01:50:44 AMI need to know if possible: can the current ML firmware for 7D archive the possibility to have custom bitrate?
Yes.
Quote from: Brawl on February 07, 2013, 01:50:44 AMI have explained to my teacher that Magic Lanter allow the user to select custom bitrate to have some kind of "raw" files, I said him that having a super bitrate allow the filmmaker to work in post processing without the fear to loose in detail after having done the job. Can we do it with 7D and ML aready?
Increasing the bit rate is not the same as the camera recording RAW video data, which is not possible at this level. Basically you can think of increasing the bitrate as a way to reduce compression and blocking artifacts in highly detailed or high-frequency noisey material.
Quote from: Brawl on February 07, 2013, 01:50:44 AMIs the firmware almost stable to install it to the 7D of my teacher (I risk my head eheheh)?
ML is an Alpha-testing release, therefore should not be used in production, and there may well be issues. However, most people have found it reasonably stable so far, so there is no problem in using it, particularly to play around and familiarise yourself with the features etc. Just be aware that there are no promises of stability yet...
Quote from: Pelican on February 06, 2013, 09:39:22 PM
I'll go back home at the next week, and I want to spend more time with 7DML developing.
Awesome! Btw, how did you compile for the 7D? I followed the getting started with development guide and I can compile for the other MLs but not the 7D. Was told in the forum that you can't compile it yet.
Quote from: g3gg0 on February 07, 2013, 01:08:52 AM
there will be a new 7D release as soon the current changes to menu etc etc etc are done.
you dont want a buggy menu i think...
i am investigating loading from autoexec.bin the last 3 weeks.
its not possible that easy, so it will take its time.
Great news, g3gg0! Thanks for all the hard work!
I found some bugs:
1. with default settings, the 16:9 Ratio is not masked out in video mode
( therefore I cut some feet at the first shooting :) )
using the 16x9_blk cropmark.bmp now works, but the mark is shown in photoreplay (with overlays) too, although I switched that off in the settings
but
2. overlays in photoreplay are not shown reliable, usually they are not shown anymore after same time, (only?) reloading ML helps
3. replay often starts in the 2x2 or 3x3 images grid instead of showing single-image as usually.
my experienced bug with alpha1, that the AF with the outer Focuspoints refused to work, didn't happen anymore :)
Quote from: StefanKeller.AC on February 07, 2013, 11:16:20 AM
I found some bugs:
1. with default settings, the 16:9 Ratio is not masked out in video mode
( therefore I cut some feet at the first shooting :) )
using the 16x9_blk cropmark.bmp now works, but the mark is shown in photoreplay (with overlays) too, although I switched that off in the settings
but
2. overlays in photoreplay are not shown reliable, usually they are not shown anymore after same time, (only?) reloading ML helps
3. replay often starts in the 2x2 or 3x3 images grid instead of showing single-image as usually.
my experienced bug with alpha1, that the AF with the outer Focuspoints refused to work, didn't happen anymore :)
1. This is normal. You have to enable cropmarks or there won't be any cropmarks at all, even at default 16x9. I think this is enabled by default though, so you must've turned off the cropmarks at some point to cause the feet cropping issue you had.
2. Are you sure you have overlays turned on?
3. This is canon behavior. You have to zoom to default zoom and press info until you get the desired display
Quote from: feureau on February 07, 2013, 11:31:49 AM
1. This is normal. You have to enable cropmarks or there won't be any cropmarks at all, even at default 16x9. I think this is enabled by default though, so you must've turned off the cropmarks at some point to cause the feet cropping issue you had.
2. Are you sure you have overlays turned on?
3. This is canon behavior. You have to zoom to default zoom and press info until you get the desired display
1. no I renamed MAGIC.CFG to check -> Cropmarks are OFF by default
2. yes, they are shown by pressing the picturestyle button after startup, shooting and reviewing some time they are not shown any more , reloading ML helps
3. again no, I never had this without ML in 2 years
Quote from: g3gg0 on February 07, 2013, 01:08:52 AM
there will be a new 7D release as soon the current changes to menu etc etc etc are done.
you dont want a buggy menu i think...
i am investigating loading from autoexec.bin the last 3 weeks.
its not possible that easy, so it will take its time.
thanks a lot for your efforts, g3gg0 - good to hear development is still going on! take your time.
Quote from: StefanKeller.AC on February 07, 2013, 11:44:08 AM
1. no I renamed MAGIC.CFG to check -> Cropmarks are OFF by default
2. yes, they are shown by pressing the picturestyle button after startup, shooting and reviewing some time they are not shown any more , reloading ML helps
3. again no, I never had this without ML in 2 years
1. Okay, so just make sure it's turned on.
2. Can't help you there. It always shows up fine on my ML. Can you reproduce this using freshly downloaded set of firmware and tell us what you did so it can be reproduced?
3. This is canon firmware default behavior. (Without ML) If you leave the preview at zoomed out at grid icons, if you go back to preview, it will show the preview at the last grid-zoom position.
Quote from: g3gg0 on February 07, 2013, 01:08:52 AM
there will be a new 7D release as soon the current changes to menu etc etc etc are done.
you dont want a buggy menu i think...
i am investigating loading from autoexec.bin the last 3 weeks.
its not possible that easy, so it will take its time.
Dear development-team,
thanks for all your great work to give the 7D new functions, that will give me new ideas for usage!
For me it doesn't matter, that I have to use the update-function to get ML to work ... either I work with ML or without. An automatic load and start is not necessary for me!
Regards
Gerd
Quote from: feureau on February 07, 2013, 12:14:14 PM
3. This is canon firmware default behavior. (Without ML) If you leave the preview at zoomed out at grid icons, if you go back to preview, it will show the preview at the last grid-zoom position.
yes of course, but I didn't enter grid view before, may be a Problem with quickzoom.
btw:
4. Quickzoom can't jump to AF-Point ( and yes, it can be displayed by canon firmware )
Quote from: g3gg0 on February 07, 2013, 01:08:52 AM
there will be a new 7D release as soon the current changes to menu etc etc etc are done.
Really happy to hear! ML for 7D have really given the camera new life. I couldn't imagine the possibilities this software have given the camera.
I love the new tab's on the 650D prealfa. And i see really nice things happens in the "UI rationalization" thread 8)
To me the missing ML autoload isn't the biggest problem. HDR video would be nice! Will the new alpha also include PicoC scripting?
Congrats on the work on ML for the 7D !!
Just a question as I am new to this. What is to be gained from changing the CBR to say 1.4, 1.8...and so on if you can't record audio.
I do a lot of vids for bands that I sync the audio with so really I don't see how this could help. If I was shooting something without sound then fine. Would like to know if there was some unique work around. Cheers !!
Quote from: jman on February 10, 2013, 07:29:24 AM
Congrats on the work on ML for the 7D !!
Just a question as I am new to this. What is to be gained from changing the CBR to say 1.4, 1.8...and so on if you can't record audio.
I do a lot of vids for bands that I sync the audio with so really I don't see how this could help. If I was shooting something without sound then fine. Would like to know if there was some unique work around. Cheers !!
Yeah, don't turn on the bitrate hack, or, if you turn on the bitrate hack, don't forget to enable audio in the canon menu. The Alpha 2 has a strange .... quirk .... that the devs enabled that it disables audio when you turn on the bitrate hack. (this does NOT include increasing the CBR and VBR)
If you want to enable audio with bitrate hack on, make sure the flush is at your framerate. i.e. if you're shooting 24p, have the flush at 24. If you shoot 720p at 50fps, have the flush at 50. Unfortunately, the devs have decided to limit the flush at 50, so you can't shoot 720p at 60fps with audio. I hope this can be fixed for future releases.
Good luck.
Thank you very much...will try this. :)
Hi just wondering when the fps override will be available for the 7D. I had a play with the intervalometer for timelapse and it worked fine but it gave the shutter mechanism a workout. Looking to try the same experiment using fps override.
Cheers.... Otto
Dear developers, I'm really happy about current and future ML features, but since 7D has dual cpu is it possible to use this power to raise the FPS speed. Can we shoot at high speeds like 120fps or higher in full HD?
or like.. thousands fps in at least 2K ?? :o
Unlike the multicore in desktop PCs for example, the 7D dual processor works as master-slave. My understanding is that ML only have access to the slave processor which controls the master of some sort.
At any rate, it seems the 7D has achieved the highest bitrate among canon dslrs so far? It shows that the camera has quite a processing power. Though there's no way we could achieve thousands of fps, I wonder how high we can push knowing that the record so far is at 36 fps. Maybe up to 48 fps?
Last week I played with a small Canon waterproof compact camera (D20) and it can take 240 fps video in 640x480 (?) which sounds completely useless, but when I filmed flying hummingbirds it made a wonderful slow-mo movie of their flight...
I think most if not all compact canon cameras can shoot high framerate at reduced resolutions. I wonder what ML can do if that sensor readout thing can be figured out. (eliminate moire even?)
slo-mo of sports also look great. I used my P&S to shoot slo-mo basketball once...
unfortunately the second digic doubles the overhead and we dont have just double processing power.
not sure why the 7D has two digics anyway, but a 600D which uses the same sensor has only one..
i think its just because of raw/jpeg processing. for "our use" the second digic dows not provide any additional processing power.
a second lane on your street doesnt make your car drive twice that fast ;)
and yes, we can use the second digic for our purpose. but the limited resource is the MPEG encoding hardware.
Thanks for clearing that up, g3gg0!
Have you guys made any progress on figuring out that mpeg encoder thingy? Last I heard there's some talk on figuring out the line skipping/pixel binning thing?
First of all sorry for my bad English.
My greatest wish is for a 3 x digital Zoom in Magic Lantern like on the 600d.
Are there any plans?
If that was possible I would love some donations.
Sorry if this has already been discussed.
Quote from: feureau on February 11, 2013, 11:34:46 PMLast I heard there's some talk on figuring out the line skipping/pixel binning thing?
Does that mean there's the potential possibility of being able to improve the video quality somewhat by intercepting the data before it gets line skipped etc? Interesting... I assume the whole line skipping thing happens to reduce the amount of data thrown at the encoder, otherwise why would Canon use this method?
With line skipping, the sensor readout is 3x faster. Nothing to do with encoder.
I'm not aware of any advances that would improve downsampling.
Thanks for all your great work! ML made my 60D SO much better and with this new release, I can finally jump on a 7D now that the prices are coming way down.
A few things:
Can someone point me towards a full list of working features on the 7D alpha2 compared to the "official" 2.3 release?
I don't think anyone has compiled such a list. But I think the only feature missing from the 2.3 ML would be:
- HDR Video
- That line reading thingy that you can use to make slit scan video
- FPS override
- ISO 25600
g3gg0 mentioned the audio thingy that hasn't been properly figured out for recording high bitrate video
Anything else?
Quote from: feureau on February 12, 2013, 05:06:16 PM
I don't think anyone has compiled such a list. But I think the only feature missing from the 2.3 ML would be:
- HDR Video
- That line reading thingy that you can use to make slit scan video
- FPS override
- ISO 25600
g3gg0 mentioned the audio thingy that hasn't been properly figured out for recording high bitrate video
Anything else?
wow, that is really nice!
Could someoe try the function that allows you to save with one PP while using another one for LV just to make sure that it isn't buggy?
I have one of my first paid gigs plus a wedding for my brother in law, and this ML update gave me the final push towards the 7D over another 60D :D
One more thing, I'd love to see an implementation of the custom modes (C1,C2,C3) for ML
Quote from: arrinkiiii on January 06, 2013, 12:46:51 AM
Until now the Alfa 2 rules. Its the best !!!
It's possible to get out uncompressed HDMI from the 7D with Magic Lantern? And more then the 60fps? If not why?
Thanks more one time for existing people that change the rout of man kind, THANK YOU.
I set "Clear Overlays >>> Recording" Soon as it starts recording, the LV overlays disappear. The HD monitor says 1920x1080i , but it does not fill the entre screen of the monitor. When I play back the file, it fills up the monitor screen. Putting the files on FCP7, it says 1080p files.
So...is this a compressed signal that am monitoring on the HD TV? I want to capture it
Quote from: eyeland on February 12, 2013, 06:33:18 PM
wow, that is really nice!
Could someoe try the function that allows you to save with one PP while using another one for LV just to make sure that it isn't buggy?
I have one of my first paid gigs plus a wedding for my brother in law, and this ML update gave me the final push towards the 7D over another 60D :D
The way it works is that when you switch to live view, it will display in one PP and when you hit record, it will switch to another PP. I haven't found any issues with it, though apparently, it kept turning this feature off more and more lately.
One caveat though: This is an alpha build, and it's not meant for production use. I've had my camera suddenly shut down for no reason that I can reproduce. Though it only happened maybe only two or three times in the past few months.
Quote from: eyeland on February 12, 2013, 06:33:59 PM
One more thing, I'd love to see an implementation of the custom modes (C1,C2,C3) for ML
How do you mean? they already works with ML.
The only problem I'm having that I can't seem to put my finger on is that when you put M in one of the custom modes, HDR would sometimes not expose properly.
Fantastic. Seems stable for me.
issue:
I can't get rid of the transparent crop bars in live view even though I turn everything off... (I think)
Would be a great help since I'm using it for live visuals with HDMI out.
Quote from: feureau on February 14, 2013, 07:30:31 AM
The way it works is that when you switch to live view, it will display in one PP and when you hit record, it will switch to another PP. I haven't found any issues with it, though apparently, it kept turning this feature off more and more lately.
One caveat though: This is an alpha build, and it's not meant for production use. I've had my camera suddenly shut down for no reason that I can reproduce. Though it only happened maybe only two or three times in the past few months.
oh.. I thought I'd actually get to use LV with one PP and save with another PP WHILE shooting :)
Yea, I realize that this build might not be that stable, but I have a backup-body to save the day if ML decides to reboot.
Quote from: feureau on February 14, 2013, 07:56:31 AM
How do you mean? they already works with ML.
The only problem I'm having that I can't seem to put my finger on is that when you put M in one of the custom modes, HDR would sometimes not expose properly.
What I meant was that I'd love for the ML srettings tobe relative to the Custom recall modes - is that implemented?
Quote from: palegolas on February 14, 2013, 10:03:01 AM
Fantastic. Seems stable for me.
issue:
I can't get rid of the transparent crop bars in live view even though I turn everything off... (I think)
Would be a great help since I'm using it for live visuals with HDMI out.
If you disable cropmarks, there will be absolutely no cropmarks at all in movie live view mode. Though the camera will only record what's inside that disabled transparent 16:9 cropmark.
Quote from: eyeland on February 15, 2013, 04:06:17 PM
What I meant was that I'd love for the ML srettings tobe relative to the Custom recall modes - is that implemented?
It is not. Though it's beyond the scope of the 7D alpha port. You should put a request in the main ML feature request thread. Search for it first in case it's been asked before.
Hi, I would like to ask, how instalation of ML works? It is copied into 7D (or it makes any modifications in 7D) or it is only file on card? So If I have got two cards, I need to copy ML to each card and update firmware for each card?
Thanks.
See first post in this thread.
This alpha version has to be activated each time you turn on the camera. This is installation step 4 as described.
Therefore: Yes, you have to copy it on each card if you intend to use this alpha version with both.
Ciao, Walter
Is there a separate thread dealing with overheating issues of 7D video? (both concerning native settings and ML tweaks to bitrate etc)
Quote from: eyeland on February 16, 2013, 01:58:21 PM
Is there a separate thread dealing with overheating issues of 7D video? (both concerning native settings and ML tweaks to bitrate etc)
overheating?
is there a problem?
Quote from: g3gg0 on February 16, 2013, 07:13:43 PM
overheating?
is there a problem?
Not in particular in relation to ML, was just wondering if tweaking video settings with ML had a history of worsening the occasional overheating that some 7D video shooters are talking about.
If you have heard no serious mention of this alleged issue here, maybe it really is a non-issue :)
Quote from: eyeland on February 16, 2013, 07:34:53 PM
Not in particular in relation to ML, was just wondering if tweaking video settings with ML had a history of worsening the occasional overheating that some 7D video shooters are talking about.
If you have heard no serious mention of this alleged issue here, maybe it really is a non-issue :)
Never had overheating issue with ML. There's been gossip of 7D/5D shutting down due to overheating, but I've never seen on does that. Even when I was shooting or hours during summer in the desert.
My 7D stops recording after about 90 minutes of continuous shooting. The room temperature was 26 degrees Celsius.
Back then, some 550D users had some luck with long recording times by turning the display off. Don't remember the numbers.
From what I remember from the vimeo boards the overheating had to do with the Flashcards. I never had the problem though.
I was recording a few nights back for a club, it was extremely hot and moist as expected, yuck. But I was recording for around 1 and a half / 2 hours until my 7D just went black with half of the battery still remaining. I sat down trying to work out what had gone wrong, took the battery out a few times doing tests, no red light or battery low screen. I then put a backup battery into the camera and it booted up like normal, switched back to the other battery and the camera wouldn't start again. Only when I got home later did the battery start working again, still with half a charge?
Almost as if the battery overheated or something even though that's impossible with no sensors. Strange.
Quote from: _iLiam on February 17, 2013, 05:43:31 PMAlmost as if the battery overheated or something even though that's impossible with no sensors. Strange.
Well, there are some components inside a battery pack. Overheating a LiON cell is not such a good idea therefore it makes perfectly sense to avoid this condition by adding a circuit breaker.
Disclaimer: I didn't disassemble it and didn't check the PCB inside. But I have a link:
http://www.camerahacker.com/Canon_Accessory/BP511_Disassembly.shtml
Ciao, Walter
@xmd5a how did you get your 7D to record for 90 minutes?
I cant get my 7D to record longer than 12 minutes. Movie Restart feature seem not to work as well.
-Ray
Quote from: RayG76nyc on February 18, 2013, 12:29:26 AM
@xmd5a how did you get your 7D to record for 90 minutes?
I cant get my 7D to record longer than 12 minutes. Movie Restart feature seem not to work as well.
-Ray
You have to press record button again when recording stops.
is anyone having issues with hearing the live audio, when connected to a monitor, or headphones connected via a Fiio unit, when recording?
Quote from: _iLiam on February 17, 2013, 05:43:31 PM
Almost as if the battery overheated or something even though that's impossible with no sensors. Strange.
Lithium Ion batteries go feral when they overheat - I haven't had a problem with my camera but have experienced the same thing with my notebook battery. Unplug it and let it cool for a while and all is good again.
I'm so glas to have ML on the 7D
Any progress on disabling AGC?
The canon 2.0.3 sound level adjustment still has agc. SO much noise, I'm still having to record sound on a protable recorder and sync up with pluraleyes. this works pretty well but the extra step in the workflow is costly in terms of time.
any new news on 7D happenings ? :o
Quote from: PhotoOp on February 23, 2013, 02:54:04 AM
any new news on 7D happenings ? :o
Latest news is on the 7D itself is that the 7D Mk II coming out in fall. Rumored at 24mpix @10fps for $2200.
Let me rephrase:
A1ex and/or G3gg0,
any new updates on ML 7D development?
I just watched the DotTune demo and I am excited! Congrats!
Yippee ki-yay,
PhOp
hi,
there is nothing new regarding to 7D-specific issues like:
- cpu load with HDMI monitor attached
- flush rate hacks with audio enabled
- fps override not available
all the other changes happening in main repository also work on 7D.
as the menu changes seem to have settled, i can check whats missing on 7D before making the next alpha.
That's great news, g3gg0 :D
Any plans for having the 7D ML integrated to the main repo and get nightly builds? :D
great news g3gg0, shame about the fps override, but we didn't have that to begin with, so I have no clue what I'm missing anyways ;D
Hey everybody...
new member in ML forum, I downloaded the Alpha 2 for Canon EOS 7D and planning to test it during next week! I had some questions, but last week I spent a lot of time, reading quite everything on the forum about the ML on my camera and...no questions anymore!
Me too, I was wondering about a new release also, as many of you, but I think that I have to learn a lot about the current release and then "dreaming" of a new one....I will try to "install" the ML tomorrow at evening and do some tests...I hope that everything will be ok....elsewhere I will ask about your help....!
Best regards and many thanks to the developers!
Quote from: g3gg0 on February 24, 2013, 03:06:18 PM
hi,
there is nothing new regarding to 7D-specific issues like:
- cpu load with HDMI monitor attached
- flush rate hacks with audio enabled
- fps override not available
all the other changes happening in main repository also work on 7D.
as the menu changes seem to have settled, i can check whats missing on 7D before making the next alpha.
Great news G3gg0. Hope a solution to the fps will ultimately be found.
Looking forward to the next release.
Cheers.... Otto
Quote from: g3gg0 on February 24, 2013, 03:06:18 PM
hi,
there is nothing new regarding to 7D-specific issues like:
- cpu load with HDMI monitor attached
- flush rate hacks with audio enabled
- fps override not available
all the other changes happening in main repository also work on 7D.
as the menu changes seem to have settled, i can check whats missing on 7D before making the next alpha.
Btw, any news on the:
- plugin to allow saving of bitrate hacks (flush, GOP) config you mentioned (or just outright letting it save? is there a hidden.cfg settings I could use to do it now?)
- that hold the DOF button to keep the camera shooting at 8fps in low light
Thanks, g3gg0
Hey everybody...
I want to give a try to Alpha 2, but I have one question....
I downloaded the version in a zip folder that has 2 files, the 1st is called ML and the 2nd MAGIC.FIR
I have to extract both of the files in the memory card to boot the ML in my camera or only the ML folder?
I did format my card from by the camera and I'm ready to try it but I want to be sure about the right procedure because is not so clear in the description...
thank you in advance and waiting for a reply asap!
Chris, you boot from the CF card while in the camera. Both the Magic.fir and ML folder need to be together and not in a separate folder on the Card.
When the card is in the camera, use the menu to go to third wrench icon (sorry don't know it's name!). Scroll to the bottom and select Firmware. Select the Magic version.
Once loaded, you can press the Trash icon to being up the ML Menu. The firmware needs to be re-loaded every time you re-start the camera. Also if you format the card you will dump the firmware too!
Regards, Gordon
Quote from: chris bouk on February 26, 2013, 10:20:24 PM
I downloaded the version in a zip folder that has 2 files, the 1st is called ML and the 2nd MAGIC.FIR
I have to extract both of the files in the memory card to boot the ML in my camera or only the ML folder?
Yes you are right. Extract the zip-file
folder (that contains the ML directory and MAGIC.FIR) to the root of your card. Remember to use a cardreader - the camera wont let you write to the card.
Good luck!
...ok,huys thank you very much....
one more question, may I use also the menu of the camera as before installing the ML?
Yes, the normal menus are still accessible.
...sorry for the questions.....!!! and what about photography? I saw so many videos about ML but everybody had the video mode and nobody did a demo about photography....what does it meant?
Questions are not a problem here... ML is used for both.
...thank you...yes that's truth....but why nobody didn't upload a demo video about photography with ML on 7D cameras? I use more the photo mode than camera mode in mine, but I will install it because I like it a lot....I was just curious about that....
thank you for being patient...!!!
Chris - read the ML docs on the website and you'll see what features are available for photography in ML...
Quote from: chris bouk on February 26, 2013, 11:22:42 PM
...thank you...yes that's truth....but why nobody didn't upload a demo video about photography with ML on 7D cameras? I use more the photo mode than camera mode in mine, but I will install it because I like it a lot....I was just curious about that....
thank you for being patient...!!!
I'm the same Chris in that I only use ML for the photography side of things I have never used ML on the video side and never will as I have
no interest in video. Using ML on the photography side of things is just great it has fantastic features which makes the 7D like a now camera, as beej says read the ML docs on the website to see what you are able to do :).
Just a quick question to G3gg0 is it possible to have a cut down version that ONLY includes the stuff that is use on the photography side of things ?
We can't make custom versions for every single user, but you can compile ML yourself and disable what you don't use. Or just hide these things from the menu (read the manual).
hey guys!!!!
I have been in ML with my 7D for a while....everything seems so beautiful and good! at the beginning I was a little bit afraid not to do something wrong but everything is so clear, so the possibilities to harm your camera is 0! I will do some tests recording with ramp focus etc tomorrow morning, (now n Greece is night and rains a lot) and I will report any bug (I hope no bugs) or misunderstood...
One question : why says that magic zoom doesn't work well with this video settings? I didn't any changes.....and in more when I'm on the screen while in live view is working fine....It's very pleasant also that you can switch from ML to Canon menus so easy....I'm sure I'm gonna love it!!!
Quote from: a1ex on February 27, 2013, 07:47:50 PM
We can't make custom versions for every single user, but you can compile ML yourself and disable what you don't use. Or just hide these things from the menu (read the manual).
Thanks for the info Alex :)
Quote from: a1ex on February 27, 2013, 07:47:50 PM
We can't make custom versions for every single user, but you can compile ML yourself and disable what you don't use. Or just hide these things from the menu (read the manual).
Is there a config that I can use to set the default GOP and flush rate on the alpha 2? (As I understand it, we can't compile 7D ML yet)
Thanks
good morning from Greece...
ML is wonderful, I really enjoy scrolling the menu and find out news.....
one question in more because I couldn't find out what does it mean....what is the T154 (the number is in case) which stands aside the Picture Profile on my main screen...I didn't found any explanation on the documentations, can you help me?
thank's in advance!
I never seen that before... Can you get a pic of the screen with the T154?
It is a CMOS temperature in some units.
Hello I am using ML in my 7D, and battery life during video recording is less unlike when not using ML, is this normal?
it is very unlikely that your camera consumes more power when using magic lantern.
although the consumption will be higher if you enabled bit rate hacks and flushing rate etc,
it should not be that high hat you will notice it.
can you please measure the recording time with and without magic lantern and tell us?
Quote from: feureau on February 06, 2013, 06:00:35 AM
On that note, it seems the 7D development is not going forward as frenzy as the other ones anymore. (5D3, 6D, EOS-M) You see a lot of updates on the threads and bitbucket for those, but rarely on the 7D anymore. It's not even on nightly build.
With g3gg0 stating that there are no further plans and no news, I wonder if it's going back into hibernation like before?
But still, I'm saying this just out of curiosity and because I love the whole ML on 7D thing. No pressure to the devs or anything. There is one thing I have to say on the whole ML thing though: ML availability has become one of the top concerns on choosing future canon bodies for me. I most likely won't buy any more canon bodies that hasn't been properly ML'd. It's that important, and I'm really grateful for all the work done.
agreed 100%
i have often thought about selling the 7d body and getting a 60d instead. but i love the 7d... especially with ML on it
g3gg0... what are the chances of an alpha that doesn't need installing each time? (or is that a beta?) i thought there was an issue (copywrite?) with the 7d bootflag? has that been resolved?
thanks
dave
as said, there will be a next alpha soon.
there is no technical problem for a 7D autoexec.bat version without bitrate hacks anymore.
<first post> g3gg0 - does that mean that the next alpha version will be self-booting?
not yet, sorry. this would mean, you will lose bitrate changing possibilities.
Hello
Will the alpha 3 for 7d inklude the new implented auto microtune adjustment?
I mainly use ML for photo
Great work!! :)
auto microtune adjustment?
Do you mean, lens microadjustment? (this is already available by default canon firmware)
Quote from: g3gg0 on March 02, 2013, 09:53:35 AM
not yet, sorry. this would mean, you will lose bitrate changing possibilities.
Will there be abilities to save bitrate settings on this next alpha?
And flush up to 60 for ability to record audio with custom bitrate at 720p60?
Any news on the DOF preview toggle when not shooting in liveview? (to maintain max 8fps thing)
Thanks for all the hard work, g3gg0. :D
auto microtune adjustment?
Do you mean, lens microadjustment? (this is already available by default canon firmware)
I know but I meant the new Dot-Tune AFMA
Yes is it a lens microadjustment Tool
Quote from: feureau on March 02, 2013, 04:19:19 PM
auto microtune adjustment?
Do you mean, lens microadjustment? (this is already available by default canon firmware)
I know but I meant the new Dot-Tune AFMA
Yes is it a lens microadjustment Tool!
Been watching the ML bitbucket feed. Looks like Dot Tune AFMA is enabled on the 7D now. Hopefully it'll make it to the next alpha.
I promised my self not pushing the developent, but now with the Dot- tune inside i,m not so relax person that i thougt was:)
Please get us the new alpha 3 soon as possible.... The bitrate and other video trouble is'n a issue for me. Do Solving that for the next/ alpha/beta :)
I wish to get the "umlimited" recording time feature in the next alpha, cause i am making a lot of documentary stuff. (start new clip after 12 minutes automatic). And is there a way to get cleaner Audio like on the 600d? i think theres to much noise in my microphone jack:-0
A big thanks to all who are working on this piece of magic!
Maurice
Quote from: moemusic on March 05, 2013, 03:50:53 PM
I wish to get the "umlimited" recording time feature in the next alpha, cause i am making a lot of documentary stuff. (start new clip after 12 minutes automatic)
Auto start recording is already in the current alpha. Thought it takes a few second for it to start again so you get that cutoff.
Oh, i tried it two or three times but it failed so i thought it would be a feature for the next alpha. I will try it once again. Hope i find something interesting to record for more than 12 minutes:-)
Quote from: feureau on March 05, 2013, 06:29:14 PM
Auto start recording is already in the current alpha. Thought it takes a few second for it to start again so you get that cutoff.
I haven't tried the 7D alpha yet since thay haven't enabled it to autoboot. But I'd like to know, when you say the auto start recording takes "a few seconds" to start again, do you mean it takes longer than on the 5D? or just the same? I have the 5D with ML and it probably takes 1-2 seconds to restart. Is it about that or longer?
Hello! I've tried various settings but can not find the best. What is the best setting for a good quality video and little grain? I always work at 160, 320, 640, ISO with CBR or Canon default.
I tried my first use of BRamp tonight, and it has a bug, I think. I can do the BRamp setup once, but then the next time it fails with "bramp could not go to play mode" until I remove and reinstall ML. What is causing the problem and why?
P.S. I am a supporter but donated before I started my forum account and it doesn't show me as one.
hi
will there be an option for aperture/shutter/iso smooth change?
Quote from: golanster on March 07, 2013, 07:13:33 AM
hi
will there be an option for aperture/shutter/iso smooth change?
Probably not for aperture and shutter. But there's supposed to be smooth ISO ramping thingy isn't it?
Quote from: feureau on March 07, 2013, 11:41:21 AM
Probably not for aperture and shutter. But there's supposed to be smooth ISO ramping thingy isn't it?
i ment for video, not ramping, to change the iso/aperture/shutter while shooting and getting smooth transition and not "jumps" in the shot
This doesn't work on 7D (same problem as with FPS override, image effects etc).
Quote from: a1ex on March 07, 2013, 12:25:59 PM
This doesn't work on 7D (same problem as with FPS override, image effects etc).
will it be possible in future release, or is it something that wont happen?
in v2.3 its working for other cameras?
We are not very good at predicting the future ;)
Not sure if this has been reported or not but, can anyone confirm this:
With ML on, on video mode, if you zoom in, the exposure shifts about +1eV.
This is highly apparent on the highlights when using cinestyle. Set it so you have a large portion of the frame that almost clip the highlights. (set it so that you clip the highlights at 1x zoom, then go down until it doesn't clip) When you hit zoom, go to the highlights and it will clip.
Quote from: g3gg0 on March 01, 2013, 10:40:54 PM
as said, there will be a next alpha soon.
there is no technical problem for a 7D autoexec.bat version without bitrate hacks anymore.
Is the waiting time over soon? :D
I Hope the New Version comes to eastern :)
i hope too ;)
currently i am testing the new/changed features what effect they have on 7D and if their behavior is intended.
and there are a lot new features.
Quote from: g3gg0 on March 10, 2013, 11:52:32 AM
i hope too ;)
currently i am testing the new/changed features what effect they have on 7D and if their behavior is intended.
and there are a lot new features.
That is a Great Message :D
Quote from: g3gg0 on March 10, 2013, 11:52:32 AM
i hope too ;)
currently i am testing the new/changed features what effect they have on 7D and if their behavior is intended.
and there are a lot new features.
Thanks for quick reply!
I,m very exited for the new alpha, hope Dot-tune AFMA will work on the 7D
Dear ML-team,
I'm now using ML onmy 7D also more and more for video. I'm very happy to find, that I can start video with a long-shutter-press so I can use it with a wireless remote-control. But the LCD-sceens stays always on. Is there a setting to switch-off the LCD-screen during video's? To make video's from e.g. birds via a remote-control and switched-off LCD will keep more battery-power left.
Regards
Gerd
Hi @ all,
I am new here, tested the 7D Alpha 2 and try to give some feedback.
First of all: Thanks to the developers - you are doing a VERY good Job and ist so exciting to follow you.
To the things i found:
- Power consumption seems to be much greater then normal. I am no video guy, so I can just talk about the non-video part.
Just going through all the menu items, looking at what you can do there heats up the camera like NOTHING I have done before with it. It gets very warm in the area of the set-button to the Display and battery life during "menu surfing" is very bad.
- There is a bug with followfocus: turned on it is sometimes possible to move the "focus-field" instead of using follow focus with the multicontroller. Being able to move the field via "right-up / right-down / etc. could be intended. But using left/right/up/down it shouldn't.
- I found another strange thing but can't remember what I did, I will test some more the next days if I have the time.
Best regards!
thome
Hi -
Can you tell me if the audio controls from the unified magic lantern will be possible on the 7DML? The ability to manipulate analogue and digital gain...
thanks - great work.
Andrew
Hello Magic Lantern team and users,
Recently loaded to my 7D and really appreciate the hard work that is going in to developing this product.
I'm looking for some guidance. I am trying to monitor audio through headphones on my 7D with ML loaded. I'm using the USB to RCA cable that came with the camera- attaching that to an RCA to mini adaptor cable- plugging that into a Fiio headphone amplifier and plugging my headphones into the Fiio.
In addition, I have a Small HD DP4 hdmi monitor plugged into the camera as well.
I'm not getting any audio to the headphone whether in standby or when recording. I do see the audio meters when recording but not in standby.
Any help would be appreciated in solving my headphone issues.
Thanks and can't wait for the next update.
Jim
Quote from: Jim Carswell on March 11, 2013, 06:50:53 PM
I'm not getting any audio to the headphone whether in standby or when recording.
didnt try that, since i dont have such setup.
Quote from: Jim Carswell on March 11, 2013, 06:50:53 PM
I do see the audio meters when recording but not in standby.
working as intended, see the alpha 2 thread.
Quote from: Jim Carswell on March 11, 2013, 06:50:53 PM
Hello Magic Lantern team and users,
Recently loaded to my 7D and really appreciate the hard work that is going in to developing this product.
I'm looking for some guidance. I am trying to monitor audio through headphones on my 7D with ML loaded. I'm using the USB to RCA cable that came with the camera- attaching that to an RCA to mini adaptor cable- plugging that into a Fiio headphone amplifier and plugging my headphones into the Fiio.
In addition, I have a Small HD DP4 hdmi monitor plugged into the camera as well.
I'm not getting any audio to the headphone whether in standby or when recording. I do see the audio meters when recording but not in standby.
Any help would be appreciated in solving my headphone issues.
Thanks and can't wait for the next update.
Jim
I have never tried that way.. I have a JuiceLink.. Connecting my mic and headphone to the juiceLink and from the juiceLink to the cam.. Everything works that Way?
Thanks for the replies g3gg0 and jphansen.
jp- does your juicedlink set-up allow you to monitor what is actually being recorded by the camera?
I am feeding my audio through a Sound Devices 302 mixer. I can monitor at the mixer level but not the camera level. Two very different things.
g3gg0- I read on another site about the set up I detailed in my original post- that write up indicated it worked- which leads me to believe I am doing something wrong. I'll continue working at it.
Thanks again,
Jim
Quote from: Jim Carswell on March 11, 2013, 10:51:15 PM
Thanks for the replies g3gg0 and jphansen.
jp- does your juicedlink set-up allow you to monitor what is actually being recorded by the camera?
I am feeding my audio through a Sound Devices 302 mixer. I can monitor at the mixer level but not the camera level. Two very different things.
g3gg0- I read on another site about the set up I detailed in my original post- that write up indicated it worked- which leads me to believe I am doing something wrong. I'll continue working at it.
Thanks again,
Jim
Its All about the level meter.. You cant trust the "true" level from output of the cam.. what if your earphones mess up the audio? To avoid noise you have to do it that way.. If You crank up the rec level in the cam you will get way too much noise :-/ in my setup I have the rec level i click from the lowest rec level on the camera - that way the juicelink boost the level up from the clean juicelink preamp And I get clean audio.. go see some Of the videos at juicelinks site.. There is a lot to learn from :-)
Offtopic sorry but: Just found this "Audio for DSLR: How to Get Good Sound with DSLR Video Cameras!".. I havnt seen it yet my self: http://www.youtube.com/watch?v=W1OewziXCTs (http://www.youtube.com/watch?v=W1OewziXCTs)
Hi guys. i noticed that there's an experimental binary (bitrate monster) to play around with bitrates and GOPs,
Since this binary was released prior to this alpha2 my question is, are these bitrate tweaking possibilities available in alpha 2?
Thanks in advance!
Quote from: feureau on March 08, 2013, 11:55:16 AM
Not sure if this has been reported or not but, can anyone confirm this:
With ML on, on video mode, if you zoom in, the exposure shifts about +1eV.
This is highly apparent on the highlights when using cinestyle. Set it so you have a large portion of the frame that almost clip the highlights. (set it so that you clip the highlights at 1x zoom, then go down until it doesn't clip) When you hit zoom, go to the highlights and it will clip.
Go into the ML menu, go to the smilie face prefs and go into the 2nd option, LiveView zoom settings...
Look at your Auto exposure on zoom and Increase SharpContrast.
Quote from: premini on March 12, 2013, 03:40:13 PM
Hi guys. i noticed that there's an experimental binary (bitrate monster) to play around with bitrates and GOPs,
Since this binary was released prior to this alpha2 my question is, are these bitrate tweaking possibilities available in alpha 2?
Thanks in advance!
Yes, they are in Alpha 2. You have to enable bitrate hacks in order to use them.
I'm awaiting Alpha 3 :)
Hi!
I've been following the forum for some time already, but this is my first post so I got to say the obvious first... Your work is awesome, thank you all for developing ML!
I would love to see the 7D version self bootable, but take your time. (I know you will. :) )
I'm using an eye-fi card (the new 16gb pro X2 version) with my 7D whenever I don't need a fast card. (which is most of the time) and I was wondering if it will work with ML or not?
Some say that ML doesn't work with the new X2 cards, but then I read this:
http://www.magiclantern.fm/forum/index.php?topic=2457.msg20790#msg20790
Does this mean we can somehow self-modify the eye-fi card to work with ML? Does a1ex have some trick to make it work? This would be good news, as I would love to have both, ML and the eye-fi functionality.
Quote from: jalejake on March 14, 2013, 11:32:44 AM
I'm using an eye-fi card (the new 16gb pro X2 version) with my 7D
wait.. you use an SD card? i guess you use an SD->CF adaptor, right?
Quote from: g3gg0 on March 14, 2013, 02:57:52 PM
wait.. you use an SD card? i guess you use an SD->CF adaptor, right?
That's right. I hear the older adapters don't work with eye-fi but I've got a new one and it works perfectly. Here's a post about it on eye-fi forums in case you're interested: http://forums.eye.fi/viewtopic.php?f=2&t=326&start=60#p27298 (http://forums.eye.fi/viewtopic.php?f=2&t=326&start=60#p27298)
Not much about the 7D port development. Any news?
Thanx and keep up the magic.
there are news. i am working on 7D.
oh wait, its not new :)
just added ML's vignetting correction to 7D, but needs some testing.
maybe HDR can also get implemented that way. we will see.
Hit me :o
Btw is it in anyway possible to crop the HDMI output to get rid of those damn black bars in the sides Of the monitor??
Quote from: g3gg0 on March 16, 2013, 12:53:51 AM
there are news. i am working on 7D.
oh wait, its not new :)
just added ML's vignetting correction to 7D, but needs some testing.
maybe HDR can also get implemented that way. we will see.
I wait with excitement as this (HDR) is among the features I am excited about due to the 7D's 60p capability allowing us to have smoother HDR video. I hope you can already implement autoboot up in the next alpha.
Good luck! Hope you can gift us with the next alpha soon.
HI,
Like all other, I'm very excited about a new alpha but: please don't give it to us just for eastern: my family would be veryx angry if I spend all eastern with my Camera and ML playing around ;D
Quote from: oli4h on March 16, 2013, 09:09:09 AM
HI,
Like all other, I'm very excited about a new alpha but: please don't give it to us just for eastern: my family would be veryx angry if I spend all eastern with my Camera and ML playing around ;D
Nice reverse psychology. No easter ML for you! :P
ML is the coolest creation since the invention of film :) Just loaded Alpha 2 on my 7D, can't wait to start implementing its features, especially timelapse, HDR and motion detection. I tried using ISO 25600, it wouldn't work, is this feature not fully funtional on the 7D? Anyway, this promps me to start a paypal account to donate, thanks ML developers, this is awesome stuff.
Nevermind :D
The idea was to get it much sooner than eastern 8)
Quote from: oli4h on March 17, 2013, 01:19:25 PM
Nevermind :D
The idea was to get it much sooner than eastern 8)
I wish there's a 7D nightly build. I also like to live dangerously.
Quote from: jalejake on March 14, 2013, 11:32:44 AM
I'm using an eye-fi card (the new 16gb pro X2 version) with my 7D whenever I don't need a fast card. (which is most of the time) and I was wondering if it will work with ML or not?
Some say that ML doesn't work with the new X2 cards, but then I read this:
http://www.magiclantern.fm/forum/index.php?topic=2457.msg20790#msg20790
Does this mean we can somehow self-modify the eye-fi card to work with ML? Does a1ex have some trick to make it work? This would be good news, as I would love to have both, ML and the eye-fi functionality.
Interesting - I have the same Eye-Fi card and haven't been able to get it to work in the 7D, but maybe it was because I'm running the ML firmware (which is awesome by the way, thanks guys, you're legends).
I have the adapter pictured in that thread on the Eye-Fi forum - I'll have a bit more of a play around and see what I can come up with...
:)
Quote from: g3gg0 on March 16, 2013, 12:53:51 AM
there are news. i am working on 7D.
oh wait, its not new :)
just added ML's vignetting correction to 7D, but needs some testing.
maybe HDR can also get implemented that way. we will see.
Great news, then!
Does that mean a new Alpha in the near future, so we can test it?
Good work, no rushes. ;)
well, yes. there will be a next alpha in the near future.
but there is no date yet, as it is done as spare time job and depending on workload in main job and in family,
i have some more or less time for it.
And we appreciate any time you give above and beyond the rest of your responsibilities to make ML magic happen. Thank you ;D
PS: I am a Supporter, though that does not show. I am glad to be able to donate what I can for ML support.
Agree.. g3gg0 - you do hell of a job here..
Quote from: g3gg0 on March 19, 2013, 12:39:48 PM
well, yes. there will be a next alpha in the near future.
but there is no date yet, as it is done as spare time job and depending on workload in main job and in family,
i have some more or less time for it.
Thanks for your work.
Quote from: g3gg0 on March 19, 2013, 12:39:48 PM
well, yes. there will be a next alpha in the near future.
but there is no date yet, as it is done as spare time job and depending on workload in main job and in family,
i have some more or less time for it.
Always thanks for your effort to our 7D.
Take your time for business and family ....... and when you can, don't forget us ;) :P
I appreciate your work.
Quote from: g3gg0 on March 19, 2013, 12:39:48 PM
well, yes. there will be a next alpha in the near future.
but there is no date yet, as it is done as spare time job and depending on workload in main job and in family,
i have some more or less time for it.
You are doing such an amazing job, and I'm sure there are many others watching this thread that aren't members, but are wanting to say thanks!
Can't wait for the new features!
Is there an option on ML to have image both in LV mode and in an external HDMI monitor? If not, could that be achieveble?
Thanx and keep up the good work.
Big maaaaaaybe for dual digic cameras. Single digic.... not possible.
I tried using ISO 25600, it wouldn't work, is this feature not fully functional on the 7D? Thanks for all your hard work on ML.
Quote from: 1% on March 22, 2013, 09:46:03 PM
Big maaaaaaybe for dual digic cameras. Single digic.... not possible.
It would be great, especially for those who work with directors, who want to monitor all shots at all time!
Should this be posted on 'features requests'? :D
If you like chasing unicorns, grab a C compiler and a disassembler and give it a try ;)
Winks aside, how does one who know very little about programming get in to the unicorn chasing business? ML in particular.
I've been trying to teach myself C using this: http://www.computerscienceforeveryone.com/ but it's not very complete yet. What sort of disassembler would one need to learn?
Quote from: DaveVegas on January 01, 2013, 11:42:30 PM
Hey guys,
I've shot a little short after doing some tests with the 7D and this is the result: http://www.youtube.com/watch?v=8KUsaJGe4jk
A little shortfilm called "The Visitor". I shot everything on a 7D with bitrates between 100-150mbps and all I-Frames. I really did see the difference in post.
Keep it up!
nice video.
Quote from: feureau on March 05, 2013, 06:29:14 PM
Auto start recording is already in the current alpha. Thought it takes a few second for it to start again so you get that cutoff.
Did i miss something? i have alpha 2 version and the auto start record doesnt work!
On the first page it says that the option ''auto start'' is in the menu but is not working.
I really hope this get correct in the next version (alpha 3 i suppose). This option is a must for me.
Yeah, sorry 'bout that. It doesn't work on the 7D alpha 2 yet. I was thinking of my other canon.
Hi - can you say whether the 7D ML will ever have the same audio functions as the unified ML? analog and digital gain settings etc...
many thanks
analog gain -> canon menu
digital gain -> post processinfg
Thanks,
Anychance audio meters may be displayed before recording is started?
Andrew
Quote from: ajwickett on March 26, 2013, 01:24:20 PM
Thanks,
Anychance audio meters may be displayed before recording is started?
Andrew
This would be very useful. Along with using the back wheel to adjust audio volume a'la 5D3. Maybe trigger it with pushing another button like HDR fusion preview thing?
If everyone keep asking for stuff, and the developers (g3gg0,?) keep trying to oblige then Alpha3 will be a loooooong wait.
Also, if you have friends with a 7d and or you haven't downloaded Alpha2 then get behind the product, download and try it. 7D Alpha1 - 25534 downloads, Alpha #2 - 213....... Not much incentive to devote a lot of time and energy.
Playing with alpha2 and patiently waiting for Alpha3 :)
What is the point of a forum if one can't suggest ideas/requests/improvements?
No one is demanding anything here. Merely asking if things may be possible in the future or suggesting ideas.
A simple 'not possible' 'not a priority' 'don't know' or no response would be fine.
If possible in next alpha - could we have the shutter button set to eject comments from sarcastic members?
Like most i follow ML with interest. The skilled developers are not chained to desks and forced to program, so part of me is sure they do what they do because they find it interesting/ a challenge/ gratifying/ dare i say enjoyable.
Therefore i don't find it unreasonable to ask questions or make requests here. Again, they are not demands, but suggestions/questions.
Thanks, Andrew
well, currently i am implementing some very interesting stuff: modules
that is something i want to have in the next alpha.
as the 7D is quite popular, that new concept will get a broad user base that tests it ;)
didnt do much 7D-specific stuff yet
"... didn't do much 7D-specific stuff yet." From my view, I'll be anxious yet waiting. All the fun begins after resurrection (Easter) anyway...
Thanks for your work!
Not sure if this can be done for the next release, but gonna ask anyway. Earlier on in this post it was asked if when in photo mode can the number of HDR pictures taken be set so that it can take more than a total of 9 images (Maybe upto 30)
Hi!
How's the work going?
I think you can't hear this question any more, but: When can we expect the Alpha #3? Are there only a few days left or do we have to wait a few more weeks?
Greets
_7D_
the current state has a stability problem.
sometimes when switching mode between play and recording, the camera screen stays black.
dont expect a new alpha the next days.
sorry for that.
Quote from: g3gg0 on March 31, 2013, 12:32:26 PM
the current state has a stability problem.
sometimes when switching mode between play and recording, the camera screen stays black.
dont expect a new alpha the next days.
sorry for that.
oh, no! More hard work for you! I'm sorry for that.
Happy Easter to all of you! :)
yep, its weird. took the 7D with me to take some shots/videos on a party and had to use it witout ML.
wasnt stable at all, i thought its caused by the module system, but i had it disabled in this version.
It's not a big problem :-) Happy Easter everybody!
I just wanted to know if everything is fine. But take your time! I think we all can wait!
Greets
I just want to say thanks to the developers! I've just downloaded the 7d alpha2 build & am looking forward to the alpha3 build whenever it is available. I wish I could help, but I only know java.... :P
http://www.canonrumors.com/2013/04/canon-eos-7d-l-announced-shipping-in-may/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+canonrumors%2Frss+%28Canon+Rumors%29
The firmware seems identical to the regular 7D. I've just loaded ML and it worked out of the box.
(http://a1ex.magiclantern.fm/bleeding-edge/7D-L.jpg)
Oh wow, this April starts with a revolution for us lefties! 8)
Hi, I can not find the function Arrow/SET shortcuts...is this function with Magic Lantern alpha 2 possible ?
Thank you!
But seriously though, the world is in desperate need for a left-handed camera...
Still enjoying Alpha2 here, and doing fun things with it. It's becoming too useful to ever not have it loaded... ;)
Thanks g3ggo and team ML...
Yesterday I used Magic Lantern for a full shoot! I can't believe how useful it is!! It's unbelievable how much it helps you shoot... really, thank you g3gg0 and all the developers for your hard work!!!
I'd like to report a bug that I don't think it got mentioned here! I was using the cinemascope cropmark for my shoot, I made a custom one myself, but I didn't compress it with the script.. I noticed it was a bit slower when loading.. Anyway.. the bug is that after some time I lost the cropmark.. it went back to the 16:9 black one.. and I had to load another cropmark and then my custom one again.. I don't know if this happens with the pre-established cropmarks.. but withmine it did.. Also, when in preview mode, the cropmark didn't stretch until the borders. I must add that I was using a monitor! A lilliput 569 to me more precise.
And 2 more things.. just to see if it is possible. I have a 7D, and the monitor does not blink when hitting the record button. But it blinks when you press the menu or the preview button, the monitor goes black, it says "no imput signal" and then it connects again. There is not any change in resolution, it is the same, 1080i it says. Is there any way that magic lantern could improve this problem that the monitor has? Is the transition when you get out of liveview when the monitor loses the signal, just asking!
And the last one.. is there any chance to have Magic Zoom in the monitor while having a 1080i signal?? It's ironic because the monitor resolution is 800x480 pixels.. but it says "1080i", I think it's downscaling or something, I don't know exactly.. There is an option in ML to "force VGA in monitor" but it loses quality and it gets stretched out, a mess really. It'll be sweet to mave magic zoom, or even a fake magic zoom.
I want to thank again for this wonderful software!!! I got really wonderful footage thanks to you guys!!
Cheers from Argentina!!!
Your doing a great job guys, I love ML when I first started using it on my 600D - is there anyway that ML can duplicate the x3 and x10 digital zoom on the 7D that the 600D has I have to keep swapping cameras when doing my wildlife. thanks.
Dear ALL
First of all, I thank to the people from ML for this very interesting software (non yet tested, because of the issue below).
I already installed the ML for my Canon 7D. Indeed it works. But...I turned the camera OFF. As soon as I turned the camera ON and pressed the DELETE button to again open ML menu, nothing happens. Now, in the topic ""Magic Lantern for 7D alpha 2"" is mentioned that "" You have to reload Magic Lantern every time you use it. (This is intentional)"".
Therefore, my questions are:
1) If the camera will be turned OFF, the ML should be installed again (from the CF-Card) when the camera will be again ON?
2) If so, this means that the software is installed ONLY on the CF-Card? The camera software (2.0.3) will be not affected?
3) If so (again), it is possible to use the CF-Card (photos, movies) with the same card?
4) If the card will be exchanged, must ML installed again on the next one?
Thank you ALL for an answer.
Best Regards, Eugene
1) If the camera will be turned OFF, the ML should be installed again (from the CF-Card) when the camera will be again ON?
2) If so, this means that the software is installed ONLY on the CF-Card? The camera software (2.0.3) will be not affected?
3) If so (again), it is possible to use the CF-Card (photos, movies) with the same card?
4) If the card will be exchanged, must ML installed again on the next one?
1. Yes, each time the camera is started you need to go into the menu to load ML.
2. ML is only "staying" on the CF Card and is loaded to the camera when you load it. It DOES NOT overwrite or erase the camera operating system.
3. You need to load the ML system into the top level of the CF Card. Photos are stored in a sub-directory. You can use the same card.
4. If you want to use ML, it needs to be on each card you use in the camera. Related, if you re-format a card, the ML system will be deleted from the card and you will need to re-load the ML system on the re-formatted card.
Regards...
you do not "install ML", you just run it from a FIR.
in alpha versions you never install ML.
@all:
about the alpha 3: we are currently finding out a lot of interesting stuff.
as long we are still in this process, it makes no sense to release an alpha.
we are currently enjoying finding out how to use it for cool features.
then let us make those cool new features user-safe, and you will see a new 7D/5D3 alpha that will amaze you.
Gee thanks ML for the alpha2, Been looking for this a long time now after running alpha1 w/o a hitch!
Installed it today and so far so good but one small think i think.
When using intervalometer in conjunction with timelapseramping set at sunset a square is displayed on my screen that flickrs a few times during calibrating and end with the message intervalometer had stopped after telling me it can not calibrate.
Quote from: g3gg0 on April 08, 2013, 09:53:37 AM
you do not "install ML", you just run it from a FIR.
in alpha versions you never install ML.
@all:
about the alpha 3: we are currently finding out a lot of interesting stuff.
as long we are still in this process, it makes no sense to release an alpha.
we are currently enjoying finding out how to use it for cool features.
then let us make those cool new features user-safe, and you will see a new 7D/5D3 alpha that will amaze you.
Liking the sound of this! :) Any clues or is it :-X until it's released?
well, its public. TCC, module system and RscMgr memory access.
the module system is more like linux kernel modules, which means full access to ML and canon functions.
this way additional functionality can be added very easy.
our ideas for modules:
- full C compiler using TCC
- put Movie hacks there (nitrate, GOP, ...)
- ...
TCC adds a C compiler to use full-C scripts that are treaten like modules (have full access etc)
RscMgr memories allow us to use a lot more memory.
on 7D and 60D we can use 7-8 Megabytes for ML without having to steal it from anywhere.
plus we know how to allocate up to 250 Megabytes on these models for saving data like we have to do when formatting the card.
all these things make ML more extensible and usable.
I didn't understand a word of what you just wrote.. but I'm looking forward to the next alpha anyway ;-)
Hi,
I don't use ML very much but I use it for video and I think it is a great piece of software.
I wanted to report a problem that has been reported before : battery drain. Yesterday I shoot a little video. I started with a battery 75% full. Suddenly I noticed that my camera had stopped because the battery was empty. I had not done anything special. I had used ML for the magic zoom. Here is a part of my configuration :
Global Draw On, all modes; Zebras Lumafast over 99%; Focus Peak On, 0.5, R; Magic zoom F+HS Med TL 3:1; Cropmarks 16x9; Gost Image Off; Spotmeter Percent AFbox; False color Off; Histogram RGB, Log, clip, warn; Waveform small; vectorscope Off;
I had recorded maximum 2mn of film and it stopped as I was not recording. The battery is not a Canon but I've never have any problem with it.
Thanks for all the efforts. Looking foreward to the next version.
Not a ML problem.
http://www.youtube.com/watch?v=HbUN_g2IIOE
http://www.magiclantern.fm/forum/index.php?topic=1573.0
http://wiki.magiclantern.fm/faq#does_magic_lantern_consume_more_power_than_standard_canon_firmware
can you retry the same procedure with and without ML and measure the time until your battery is empty?
Thank you very much for your time, your excellent job and your free ML!!! It is my fist time trying to install it (with alpha 1 and alpha 2) on my Canon 7D.
It works but when I am done with my shootings and that I turn off my camera, the next time I want to use my camera and turn it on, the ML program is not there anymore when I press on the delete button. I do not want to I reinstall Canon FirmWare 203 everytime because I am loosing all my 7D settings.
What can I do? Thanks to help me :)
Quote from: g3gg0 on April 08, 2013, 09:53:37 AM
you do not "install ML", you just run it from a FIR.
in alpha versions you never install ML.
Quote from: Thierry on April 08, 2013, 02:31:08 PMWhat can I do?
You have to reload ML alpha 2 each time after your camera shuts down. Manually!
This is alpha and intended.
Ciao, Walter
I understand, thank you g3gg0 and Walter! I can't wait to try your installing version! Congratulations for your great research and work! :D
A1ex : I have used the video a bit since I bought my 7D (2 or 3 hours of rushes) and never had such a behaviour, with or without ML.
Now the problem obviously does not occur very often. Is it even a ML problem ?
G33g0 : I'll give it a try again as soon a I have time. There was a lot of over exposure. Could it be linked ?
Quote from: kanak on April 08, 2013, 02:49:46 PM
G33g0 : I'll give it a try again as soon a I have time. There was a lot of over exposure. Could it be linked ?
i dont think, but you are welcome to prove me wrong ;)
Just a quick question last night I was out shooting with my 7D and a couple of others that were with me had the 5D mkII and they showed me on the 5D mkII using the magic lantern software how to set the camera to check the color balance using Kalvin. They pressed the AWB on the top of the camera while the live view was on then pressed the set button and the software did it's magic and set the correct kalvin automatically, but when I tried the same with the 7D it did not work, is there another way to set this on the 7D or is this not yet in the Alpha 2 version.
I tried to reproduce the problem but the battery behaved normaly.
Of course what happened to me on Sunday could be due to the battery being less charged than I though.
Just wanted to drop you all a line and thank you for the hard work in getting ML to full feature on the 7D....makes a world of difference from the Canon software! I've shot a bunch of stuff with both Alpha 1 & 2 and have had no major issues AT ALL, little hiccups, but nothing that hasn't been brought to light yet.
As soon as I can get some work shooting and pickup a paycheck or two, I will be throwing into the coffers to help the good fight. Until then, I figured I could share the latest thing I've shot. It's a teaser for a short that is currently in post-production...check it out and let me know what you think; I'd appreciate it. http://youtu.be/FcW6fmYBS-M (http://youtu.be/FcW6fmYBS-M) I'm also shooting a feature, that I will share as soon as there's something to share.
Thanks again!!
The cpu usage indicator (percentage) does not stay on when i insert an other card with the same config file.
Great work, looking forward to alpha 3.
Good afternoon everybody.
I was looking for a timelapse for my 7d and Google showed me the good way : Magic Lantern !!!!
Thank you for the great job done (I still can't understand why all the features of ML are not included in the Canon firmwares ????).
I've downloaded The Alpha2 version of ML, but I don't know how to install it on my memory card. I have no card reader on my Mac, so do I have to use Eos Utility ?
Must I load only the .FIR file and the ML directory that comes withe the Alpha2 release, or only the .FIR file ?
The firmware version of my 7d is : 2.0.3.
Are there french menus included in the software ?
Thanks for your coming help.
Regards
Thierry
Hi ThLDQ
You do need a card reader to install ML Alpha 2. See http://www.magiclantern.fm/forum/index.php?topic=3103
(http://www.magiclantern.fm/forum/index.php?topic=3103) link for instructions.
The EOS utility doesn't allow you to write to the card using the camera.
Great !
Thank you da.vanderzon
Thierry
Quote from: jphansen on April 08, 2013, 01:05:10 PM
I didn't understand a word of what you just wrote.. but I'm looking forward to the next alpha anyway ;-)
i think i can translate:
it's gonna be the boss! 8)
Hello all! Developers please add to function on magic lantern: full functional whith big size silent picture for timelaps and intervalometr, fast speed- 60 k per second or 120 k per second if real. Thank you for your work, magiclantern great product!!!!
I've really loved my 7d, but looking at the new black magic camera, I've become very excited for the possibility of shooting ProRes 422. I shoot really run and gun and the extra color space can help me a lot in post. I'm thinking of selling my camera before the pocket comes out, just in case the market gets flooded with 7ds. But the worst thing would be if I sold it only to find that magic lantern gifted the 7d with the ability to shoot 422. I was wondering, is there any possible way this could happen? Or is 422 impossible on the 7d?
- Dan
Hi. Thanks for your work. Ive got a question - is there any possibilitie to change shutter speed with arbitrary values and use them in a intervalometer ramping for more smoother exposure changing? Thanks.
See http://www.magiclantern.fm/forum/index.php?topic=1915 - no success yet.
Hello all! the function a motion detect don't work on video mode!
Any hope for changing the h.264 encoding profile on 7D? http://william-patin.de/blog/canon-and-the-h-264-profile/
Quote from: Sky_cleaner on April 17, 2013, 06:37:33 PM
Any hope for changing the h.264 encoding profile on 7D? http://william-patin.de/blog/canon-and-the-h-264-profile/
There is more to video codec quality than the h.264 profile. Just ask the x264-people.
-h
Great job ML this firmware is amazing can't believe this is not stock with Canon firmware. But I am really looking forward to HDR recording and photos with my 7D. The other thing I can't wait for is Follow Focus since my 7D is used for B roll rack focusing for interviews.
Hi, I'm using ML alpha 2 in Motions sensor more in live view. 2 things I want to mention besides thanks a lot and will soon donate!
1, Can motion detect also run in non live view more please? and 2 in does drain my battery fast but i still wonder if that's not an issue normally when in live view. I'm hoping to convince my photo club members to start using ML on their 5D's and 7D's when i'll give them a demo :) during a club session!
Yes, it's possible to implement the simplest type of motion detection outside LiveView. I'm not going to do it, but anyone else is free to give it a try.
Ok will give hat a try tomorow! Now i have to see if ML did not delete some shots I made in the morning before using ML.
Getting my shots of the 7d's cf card now, saw some jpg's and mov's that the 7d preview did not show while in ml. Gone try to reproduce that and report
Great work on ML Alpha
I absolutely love the CBR settings.... very practical when you don't need ultra quality or forgot your high capacity CF on the road
Just like to make a note and make some suggestions for Global Draw and HDMI out
1) ML basically facilitates HDMI out recording with help from Global Draw Off. Great feature
However, some things I would like to request:
1) Global Draw option to turn off grey Bars top and Bottom
2) Option to remove The RECORD red dot that displays
or
2b) Move the RECORD red dot up into the grey bars. This way we can just crop the grey bar from the scene without losing too much of the picture.
3) Remove the overheat sensor from displaying or move it to the top of the picture. The overheat sensor displays obtrusively in the right side. Maybe move it to the lower right or to any other corner. That way if it ops up you can just crop it out of the scene
There seems to be 1 bug to the Global Draw off.
After you use the autofocus, the focus frame square bracket still shows on screen (normally with ML, the focus square bracket disappears after a few secs). The workaround is to click ML Menu twice and the focus bracket will disappear. Maybe there is a check missing from Global Draw after the autofocus button is used?
My goal is to get a clean HDMI out signal, so that I can record off of HDMI via external recorder.
Thanks alot for the great work and that's my 2 cents.
Thanks again for the great work. A perfectly clean HDMI out image without recording symbols would be absolutely fantastic
Would be even more fantastic if you could read the manual.
http://wiki.magiclantern.fm/userguide#clear_overlays
Nice, can confirm now that the jpg's and mov's i made are still there :) Tomorrow a new ML testday :)
Hey Alex,
Got a no go for my 7d on motion detect w/o live view on :( Switching live view on works like a charm but not without.
Read my post again (all of the words, not just half of them).
Ok saw it thx Alex
Now think a bit logically. If you cover the sensor with shutter and mirror, then what will record the movement in front of the camera?
Live view off the camera records only the movement of the shutter button, even without the ML.
Quote from: gipukan on April 22, 2013, 11:47:07 PM
Hey Alex,
Got a no go for my 7d on motion detect w/o live view on :( Switching live view on works like a charm but not without.
Quote from: Mark0ki on April 23, 2013, 07:35:44 PMNow think a bit logically. If you cover the sensor with shutter and mirror, then what will record the movement in front of the camera?
Well, might be possible to engage mirror lock-up, flip up the mirror and get the sensor to monitor the image for motion/processing etc, without the whole live-view/screen thing on - it's the screen which sucks up a lot of power...
Just look at exposure indicator - if it changes too much, take a picture. Keep shutter pressed halfway.
Quote from: beej on April 23, 2013, 10:04:54 PM
Well, might be possible to engage mirror lock-up, flip up the mirror and get the sensor to monitor the image for motion/processing etc, without the whole live-view/screen thing on - it's the screen which sucks up a lot of power...
As a general feature, not just 7D specific, I thoroughly agree with this. But would it be easier to go at it the other way? Use normal motion detect WITH live view, but turn off the display, and anything else that wouldn't be needed, to help battery?
Quote from: a1ex on April 23, 2013, 10:41:55 PM
Just look at exposure indicator - if it changes too much, take a picture. Keep shutter pressed halfway.
Hadn't thought of that. How precise is the exposure readout? 1/3 stop wont get some things will it? Nice idea though, that would be low power!
Hi, I'm just wondering, is 422 color even a possibility on the Canon 7d? Is that on anyone's list of things to do?
So, I heard (http://"http://www.eoshd.com/content/10221/magic-lantern-discover-2k-raw-dng-function-on-5d-mark-ii-and-iii?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EOSHD+%28EOSHD.com%29") they found some DNG RAW live view in 5DM2 and 5DM3. Any news in that front regarding the 7D? :D
i am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
Quote from: g3gg0 on April 26, 2013, 10:56:53 PM
i am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
Most Excellent!
Quote from: g3gg0 on April 26, 2013, 10:56:53 PM
i am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
Wow! You guys are feature assassins! Nice work!
Quote from: g3gg0 on April 26, 2013, 10:56:53 PM
i am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
The RAW video on the 5D3 is being discussed all over the internet. Are you saying raw or (YUV422) might work on the 7D as well ??? Wow..
Quote from: g3gg0 on April 26, 2013, 10:56:53 PM
i am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
I want to fly over there, give you a big hug and buy you a pint of the finest beer known to man.
Do you think you can get the framerate up to 24 or 25?
...heu guys!!! I hope you are fine...I'm very happy to use ML, I'm trying every time I turn on my camera....I will donate soon....
I want to ask,....Last week i went to a mountain bike race, and i wanted to test the detect motion feature on my 7D...
I tried everything but the result was that my camera started to fire photos in continues mode,,,,couldn't explain it,,I have used all the parameters but at the end, I decided to don't try it more, than losing the race...! Can anybody suggest me, the way to use the detect motion feature,,,,maybe I'm doing something wrong...!have someone used this feature in a race...something like mountain bikes,,,etc etc...?
thank you for your patience...looking forward to hear from you soon!
Best regards
Chris
An excellent feature that can add would be able to record at 60fps at 1080p, would the best they can do.
Quote from: davidutn on April 29, 2013, 05:47:45 AM
An excellent feature that can add would be able to record at 60fps at 1080p, would the best they can do.
It seems the hardware won't allow this, it's simply not powerful enough - so I'd give up on that one, nice though it would be...
Hello
Is a Release in the next 3 Weeks possible?
Thanks
I know g3gg0 is busy in other things, he said that in a message a while ago,
Is there any other developer thats working with the 7D spesific? Or is just g3gg0?
Nice work with the alpha 2 but alpha 3 has so much more facilities, what have read in this forum
Thanks :P
Sorry, I see know that you have posting several message after that specific post :-[
Quote from: g3gg0 on April 26, 2013, 10:56:53 PM
i am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
Comparing with 4:2:0, 4:2:2 sounds like exactly 2 times more calculation to me (I don't know very well about video encoding), I am just wondering that if there is any ways to split the task into the two processors. Will it be possible to turn on some multi-threading flags in the compiler ( I heard a rumor that in Windows, you can use the -safethread flag to enable parralel threading, or some like that.
You know... if you have a raw 1080p "video" feed off of the camera, is it possible to reroute that to the H.264 encoder and get a clean, high detail, moire-less H.264?
Before I start digging through all the dev stuff and repositories, is there everything in the repositories to easily compile an autostarting version for the 7D (without any additional coding)? If so, a pointer to where to look for would be great. Thanks :-)
Last time I checked, because you need the signature to allow canon to load the firmware update, you can't compile your own 7D ML yet, though it seems one user, pelican, have been able to do so.
Anyway, it's been months since the last time an alpha was released for 7D. Alpha 2 was released before christmas. I wonder if it's high time another alpha gets released? :D
Quote from: pfluger on May 04, 2013, 09:13:38 PM
Before I start digging through all the dev stuff and repositories, is there everything in the repositories to easily compile an autostarting version for the 7D (without any additional coding)? If so, a pointer to where to look for would be great. Thanks :-)
Yeah, I would love to see an autostarting version too. Even without all of the latest features if some are unstable and not yet fully tested. They could be added gradually when stable? ;) I think many would benefit from having ML ready when turning the camera on. But of course first things first, and take your time to do your magic. I know I couldn't, so who am I to tell what you should do. :)
Quote from: pfluger on May 04, 2013, 09:13:38 PM
Before I start digging through all the dev stuff and repositories, is there everything in the repositories to easily compile an autostarting version for the 7D (without any additional coding)? If so, a pointer to where to look for would be great. Thanks :-)
You can compile the autoexec.bin for your 7D, the main repo contains all the necessary sources, just type 'make 7D'.
The extra step you need is enabling the bootflag on your camera.
There is a dumper fwupdate which dumps the memory and enables bootflag. It's for an old fw version maybe for 1.1.0 so you should downgrade your camera's fw first with EOS Utility.
But much better if you trust in the developers and use the alpha until they decide to make a beta version which autoloads itself.Quote from: feureau on May 04, 2013, 10:08:05 PM
Last time I checked, because you need the signature to allow canon to load the firmware update, you can't compile your own 7D ML yet, though it seems one user, pelican, have been able to do so.
You can compile your own autoexec to 7D from the beginning.
Quote from: Pelican on May 05, 2013, 12:37:47 PM
But much better if you trust in the developers and use the alpha until they decide to make a beta version which autoloads itself.
Yeah, I'll definately wait for the beta version instead of downgrading my fw. :)
Quote from: Pelican on May 05, 2013, 12:37:47 PM
You can compile the autoexec.bin for your 7D, the main repo contains all the necessary sources, just type 'make 7D'.
The extra step you need is enabling the bootflag on your camera.
There is a dumper fwupdate which dumps the memory and enables bootflag. It's for an old fw version maybe for 1.1.0 so you should downgrade your camera's fw first with EOS Utility.
But much better if you trust in the developers and use the alpha until they decide to make a beta version which autoloads itself.
You can compile your own autoexec to 7D from the beginning.
Thanks a bunch for that info! Too bad about having to downgrade, that's definitely a showstopper for me. So yeah, I will patiently wait for a beta ;-)
On my 7D, "Movie Restart" doesn´t work.
Is this a bug or am I doing something wrong?
Quote from: Kea on May 06, 2013, 02:21:55 PM
On my 7D, "Movie Restart" doesn´t work.
Is this a bug or am I doing something wrong?
Known issues:
* You have to reload Magic Lantern every time you use it. (this is intentional)
* when using HDMI output, frame drops may happen (to be verified)
* make sure your battery/adaptor is chipped, else canon menu will abort "firmware update" (= loading ML)
* movie restart and video effects menus visible but not working
Thank you, so I have to wait for the next alpha.
It is waiting for updates ML, next week I stay abroad .... would love to take advantage of the updated firmware ... Maybe there is something like nightly releases at least try what that new features ...?? Best regards.
Prompt please, maybe there's an opportunity to make such a firmware function as a blackout ... so you can use the camera without darkening filters when shooting in the afternoon, in the summer on a sunny day at 1/60 1/120. something like the sensor is receiving less light, such as when using a low ISO. It is possible to implement? Then the regular means without additional filters can be removed during sunny weather. Thank you.
Brilliant! Using ML alpha 2 on the 7D, and so far the results are spectacular. Especially loving the overlays and the custom VBR--and the only issue I can report is that, occasionally, the camera stops recording at 3X VBR, but only when ML is first loaded. So, first try: camera records for maybe 2 secs, then stops. After that, it works seamlessly. Recording on a SanDisk Extreme Pro UDMA 6 CF card rated at 90 MB/s.
THANK YOU FOR THIS BRILLIANT FEAT OF ENGINEERING!
Quote from: Serdcelov on May 07, 2013, 09:42:30 AM
It is waiting for updates ML, next week I stay abroad .... would love to take advantage of the updated firmware ... Maybe there is something like nightly releases at least try what that new features ...?? Best regards.
Prompt please, maybe there's an opportunity to make such a firmware function as a blackout ... so you can use the camera without darkening filters when shooting in the afternoon, in the summer on a sunny day at 1/60 1/120. something like the sensor is receiving less light, such as when using a low ISO. It is possible to implement? Then the regular means without additional filters can be removed during sunny weather. Thank you.
I wish there's a nightly build too. One of the reason against releasing buggy firmware was that people would be nagging the developers for every bug they find, taking precious development time.
Anyway, what do you mean firmware blackout? As in lower than 100 ISO? That would be nice, but on other camera models, that dramatically reduces dynamic range. ND filter or stopping down is still preferable.
Quote from: fixedframe on May 07, 2013, 08:01:16 PM
the camera stops recording at 3X VBR, but only when ML is first loaded. So, first try: camera records for maybe 2 secs, then stops. After that, it works seamlessly.
Wait, did you mean VBR or CBR? VBR value is between 16 and -16, CBR is 0x to 20.0x
Also, I had issues on one CF card with camera sometimes stop recording after about 2 seconds. I formatted the card in-camera, then full-formatted the card (as in, writing bits to every location and deleting them while checking for errors) and I never had any issues with that card anymore. You might want to try that.
Also, for super-high bitrate, disable audio and you can push it to the max. (I managed to hit 500 mbits at some point)
QuoteI wish there's a nightly build too. One of the reason against releasing buggy firmware was that people would be nagging the developers for every bug they find, taking precious development time.
Anyway, what do you mean firmware blackout? As in lower than 100 ISO? That would be nice, but on other camera models, that dramatically reduces dynamic range. ND filter or stopping down is still preferable.
ND Filter sell is a very high price
I know there's lots of amazing things on the horizon for ML - but for me and maybemany others an interims version which does not have to be loaded via firmware update all the time would be a real relief.
Could such a thing be released without too much work on dev's side or isthis functionality just not ready yet?
Thanks and sorry if I asked a question posed 100 times before.
Good luck with your endeavour!
Quote from: gmfbln on May 08, 2013, 10:41:28 AM
I know there's lots of amazing things on the horizon for ML - but for me and maybemany others an interims version which does not have to be loaded via firmware update all the time would be a real relief.
Could such a thing be released without too much work on dev's side or isthis functionality just not ready yet?
Thanks and sorry if I asked a question posed 100 times before.
Good luck with your endeavour!
+1
I think the devs said only once it reaches beta/stable will this be added.
Definitely the only missing feature for me, too. Sometimes there is just not the time to manually load the firmware.
Hi, if the beep is enabled is not possible to record any sound.... is a bug?
Which beep?
Also, if the video hack is enabled, ML automatically disable audio. you might want to check that out. Annoying behavior, but that's intentional. For some reason...
Hello everyone! Please explain that to which the menu a bit rate change, in particular for what I do with video hack
any chance that the new raw recording feature will be ported to the 7d? are the two processors able to deal with the data? i guess it could make the 7d video a little nicer, too... :)
no idea.
That would be cool! 8)
I read that YUV422 and 14-bit RAW video recording is possible even on 600d, I hope 7d dual processor could be used to reach awesome video quality, possible?:-)
Theoretically:
Quote from: 1% on May 13, 2013, 05:37:08 AM
7D has to be coded... should work tho.
I am eager to see where this leads. Granted out developer here is the one who made the breakthrough. Patience will reward us hopefully :)
Quote from: feureau on May 12, 2013, 12:53:37 PM
Which beep?
Also, if the video hack is enabled, ML automatically disable audio. you might want to check that out. Annoying behavior, but that's intentional. For some reason...
Hallo feureau,
I don´t mean in video hack modus ;-) but in normal modus.
Any ideea?
Thank you!
(Audio Menu - Magic Lantern alpha 2)
REC/STBY notify
Custom notifications for recording or standby:
Red Crossout (highly recommended if you forget to press record)
Message (it shows STBY or REC)
Beeps (it will beep when recording starts or stops) ------- I mean This Feature -------
Blue LED (obvious if your camera has it)
Quote from: g3gg0 on May 14, 2013, 12:33:25 PM
7D: working on it, but it seems the interesting part is being handled on master digic that is harder to access (only via FIR)
Quote from: g3gg0 on May 14, 2013, 01:32:33 PM
i am not that optimistic that there will be a quick solution :(
I think that is not going be possible to us, 7D users. See how long that 5D users got all the things working on... Its sad but it's the way things are, unfortuned...
Maybe it's time to sell my 7D :'( I dont need full frame (its better for low light situations) just need the raw thing working in my 7D...
sad to see that other developments are moving forward, but for us owners of 7d Months from now remains an incomplete version of magic lantern that does not grow. right :-\ :'(
sorry my bad english
Quote from: Gippi on May 14, 2013, 02:15:51 PM
sad to see that other developments are moving forward, but for us owners of 7d Months from now remains an incomplete version of magic lantern that does not grow. right :-\ :'(
sorry my bad english
It's true Gippi, even with 2 processors (that i think in the past that is a good thing, more thing to do with the 2 processores) but is the oposit, its more hard to code things.
For us, 7D users, we have to load every time the ML :-\ , no hdr video... I think the only good man in the job for the 7D is g3gg0 and he do a good job but i think he have now a 5D III... so i think is better to sell the 7D (that i dont want) for we have the latest ML.
For me selling the 7D is not big problem but the lenses?? The lenses is the bigger issus for me. Im very happy with my 7D, imagine having raw in the 7D but with 60fps... for me im just imagin having only raw at 24fps, already good for me.
I wish that show up anybody that can code for the 7D, only g3ggo doing the job i think that we will wait long time or maybe never se the sun of having raw in ours beloved 7D.
And saiyng this, big up to g33g0 for code to 7D, if not him we dint have nothing!!! God bless g3ggo !!!
(also sorry for my inglish)
Patience, guys! Rather have a well engineered and tested version that takes its time than a rush job with disappointments and other problems.
Things take as long as they take. Take it from me ;)
Quote from: da.vanderzon on May 14, 2013, 03:22:16 PM
Patience, guys! Rather have a well engineered and tested version that takes its time than a rush job with disappointments and other problems.
Things take as long as they take. Take it from me ;)
Yes, you have totaly reason!!! But i think that is not going to be a easy task or not even be possible to port to a 7D. But lets have our fingers cross and pray to
God G3gg0 for he solve this code thing on the 7D.
In the end canon always wins with ML. If they dont port to the 7D i will sell my and buy a 5D, mark 2 or 3. And people still work with video on canon dslr because and only of the ML soft. Canon shoud pay to the ML team. Because in the bottle end is canon that wins (money) ...we win camera with good software (ML) ...and thats ok for me (+/-)
Quote from: Gippi on May 14, 2013, 02:15:51 PM
sad to see that other developments are moving forward, but for us owners of 7d Months from now remains an incomplete version of magic lantern that does not grow. right :-\ :'(
if that would be the generic 7D user opinion ...
Cry me a river
Cry me a ML for 7D ;D
:'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'(
You go g3gg0, god of 7D users !!!
Quoteif that would be the generic 7D user opinion ...
Nope, it's not for the majority of 7D users. I have followed the developement of ML since you released ML for 7D. And even if we don't have all the amazing new features on our 7D's, I know it's all done for the best for every ML user - also for 7D users if it's possible.
Congratulation for the great job you, a1ex and the rest of the team have done with bringing 14 bit RAW to Canon DSLR! I celebrate with you - and I know you'll be back when the mission is completed :)
Quote from: g3gg0 on May 14, 2013, 04:24:53 PM
if that would be the generic 7D user opinion ...
Sorry if I generalized speaking in the plural, this is just my opinion.
But it would be nice to hear instead of what is your point of view concerning further developments for the 7 D.
Grazie di cuore
For something most of you have never even donated for you sure have no problem requesting/begging/demanding features to be added within a couple of days of it enabled on more capable models without having a clue what kind of work it takes I fear one day you people that fall into this category will ruin the motivation/innovation of some of the most skilled coders here.
Keep up the excellent work g3gg0, at your own pace of course!
What stedda said.
Also, maybe it's best to lock this thread until the next release. All the bugs we could possibly find has been discussed to death, and looking from the bitbucket feed, it seems the 7D ML has moved far from what we have in alpha 2. The last few pages is only filled with people waiting for the next alpha or something, and I'm sure it annoys the devs as much as it annoys a lot of us to read. It adds nothing of value to the discussion/development of the alpha anyway.
Just know that we love you and greatly appreciate what the whole ML dev team has given us. Especially you, g3gg0. I wish I can fly over there, buy you a pint of the finest beer, and hug you.
TL;DR - stedda, close thread, love you.
Just wait and let Magic Lantern team work. It can be annoying when people ask only for their cameras.
Quote from: g3gg0 on May 14, 2013, 04:24:53 PM
if that would be the generic 7D user opinion ...
I am quite sure this is not the case. Most people are just waiting without saying too much, a few people run out of patience and send mails like this. I for example am enjoying the first alpha still very much since it gives me the posibilty to record movies with my 7D. Without the zoom screen I would not be able to record a movie since I would not be able to focus correctly. Thanks for now for all and looking forward to newer developments any time in the future.
I too wish to take a moment to commend all of the ML developers, especially g3gg0, for bringing this break through software to my 7D. It has opened up possibilities that would only be available to me at significantly higher cost of equipment replacement. I've shot some of my favorite photos since installing the software.
Your work is appreciated and recognized for it's innovation!
7D isn't compatible with UDMA 7 cards, so maybe we'll never see full HD raw video working on 7D. :-*
Quote from: edwmotion on May 16, 2013, 12:10:40 AM
7D isn't compatible with UDMA 7 cards, so maybe we'll never see full HD raw video working on 7D. :-*
Um, no...
http://www.learn.usa.canon.com/resources/blogs/2011/20110426_eos7d_firmware125.shtml
g3gg0, please continue to develope the 7D firmware. We know you have a life, some people are just impatient. Your work on the 7D has been tremendous and a lot of us want to see it continue. The rest of us who are quiet probably understand that you're developing the RAW video and that once you get it nailed down, then you'll have more time.
I'd love to see more work on the 7D, and a full version of ML on it if you can make that happen. I hope others agree, since it's been said, but please take your time and develop something great for us. I'd donate again if the options was present.
its not that easy.
the slave processor ML runs on, doesnt have access to the raw data stream as it seems :(
Quote from: g3gg0 on May 16, 2013, 01:50:42 AM
its not that easy.
the slave processor ML runs on, doesnt have access to the raw data stream as it seems :(
Ouch, that hurts. Well, thank you g3gg0 we really appreciate all of your hard work and effort.
Quote from: Digital Corpus on May 16, 2013, 12:19:34 AM
Um, no...
http://www.learn.usa.canon.com/resources/blogs/2011/20110426_eos7d_firmware125.shtml
Firmware 2.x.x
Figure based on updated firmware, ISO 100, Standard Picture Style and with UDMA 7 CF memory cards. Note: UDMA 7 CF memory card read/write speeds are not fully supported with the EOS 7D Digital SLR camera, if using UDMA 7 memory cards, the read/write speeds will be equivalent to UDMA 6.
http://www.usa.canon.com/cusa/consumer/standard_display/EOS7D_firmware_features
We were at a stage where the 7D could not boot ML. One day we may have access to the master ARM chip. Just need another apiphany.
EDIT: Ah, well, UDMA6 goes up to 133 MB/s. Granted the highest regular benchmarks on the 7D I've seen are at ~55MB/sec. It's been a while since I've run a ML benchmark on my cards, but I only have Sandisk's 60MB/s cards.
a Sandisk's 60MB/s would be fine for 1280x720 (or slightly bigger) raw on 7D which would give better flexibility for WB and more dynamic than the 7D Video has.
and maybe more visible resolution in comparison when upscaled to 1080p
Quote from: g3gg0 on May 16, 2013, 01:50:42 AM
its not that easy.
the slave processor ML runs on, doesnt have access to the raw data stream as it seems :(
Didn't you manage to get 422 YUV out of it? What about plugging that feed to the H.264 encoder and get a clean, sharp, moire-less video? Is that possible? (sorry if stupid question)
Raw video is great, but holyshit 128GB for 15 min.
I need some help. I'm new to the ML world and learning how this all works.
I have a 7D with the FW 2.0.3
I downloaded the 7D Alpha 2 and pulled the contents onto a CF card and then went through the steps to load it on the camera.
However while it's in the process of loading it seems to stop and gives me the screen that says:
"Ensure a lens is attached. (which there is) Press start start/stop button to activate movie shooting."
The Alpha 2 doesn't seem to have loaded on the camera, or if it did I'm misunderstanding how to access it.
What am I doing wrong? Am I in a wrong setting and am unaware?
Thanks.
Peter-John
Quote from: Claymore Pictures on May 16, 2013, 07:37:16 PM
I need some help. I'm new to the ML world and learning how this all works.
I have a 7D with the FW 2.0.3
I downloaded the 7D Alpha 2 and pulled the contents onto a CF card and then went through the steps to load it on the camera.
However while it's in the process of loading it seems to stop and gives me the screen that says:
"Ensure a lens is attached. (which there is) Press start start/stop button to activate movie shooting."
The Alpha 2 doesn't seem to have loaded on the camera, or if it did I'm misunderstanding how to access it.
What am I doing wrong? Am I in a wrong setting and am unaware?
Thanks.
Peter-John
I've had no problems loading Alpha 1 or 2 on my 7D. What lens do you have attached? If it is a non-cpu lens, in other words it does not report aperture, focal length, or focus to the camera, then the camera may not know you have a lens attached to it. I cannot speack from experience because I have no such lens.
Quote from: Claymore Pictures on May 16, 2013, 07:37:16 PM
I need some help. I'm new to the ML world and learning how this all works.
I have a 7D with the FW 2.0.3
I downloaded the 7D Alpha 2 and pulled the contents onto a CF card and then went through the steps to load it on the camera.
However while it's in the process of loading it seems to stop and gives me the screen that says:
"Ensure a lens is attached. (which there is) Press start start/stop button to activate movie shooting."
The Alpha 2 doesn't seem to have loaded on the camera, or if it did I'm misunderstanding how to access it.
What am I doing wrong? Am I in a wrong setting and am unaware?
Thanks.
Peter-John
Maybe try taking it out of movie mode for the update
Quote from: mdwhaley on May 17, 2013, 03:29:41 AM
Maybe try taking it out of movie mode for the update
MD you rock that's all it was. I had it in movie mode. When I switched it over worked perfectly.
thanks
Claymore
Quote from: Mare on January 17, 2013, 11:39:58 PM
First of all
g3gg0 and the ML Team THANK YOU for all the work on 7D.
I have two minor reports - questions:
1. in Movie settings, REC/STBY notif: beeps - video is recording, but no sound recording (is it possible to turn mike on)
Keep On Rockin'
Quote from: g3gg0 on January 18, 2013, 01:01:07 AM
1) i dont understand this. what beeps?
Quote from: Mare on January 18, 2013, 07:46:33 PM
Well, sound recording on other settings work fine, just when you choose beep notification for start or stop recording, you can hear the beep (that's OK), video is recording, but no sound recording.
It would be fine and much easier for sync audio with video in post, because now with ML :D I can trigger (start and stop) video with remote controller, audio is anyway rec by other device.
:)
Quote from: Gippi on May 14, 2013, 07:49:52 AM
Hallo feureau,
I don´t mean in video hack modus ;-) but in normal modus.
Any ideea?
Thank you!
(Audio Menu - Magic Lantern alpha 2)
REC/STBY notify
Custom notifications for recording or standby:
Red Crossout (highly recommended if you forget to press record)
Message (it shows STBY or REC)
Beeps (it will beep when recording starts or stops) ------- I mean This Feature -------
Blue LED (obvious if your camera has it)
Hello, I have not solved this little problem with the beep, (normal video modus No bitrate hack)
I would like to know if it is a bug or if I do something wrong.
Thank You!
Quote from: g3gg0 on May 16, 2013, 01:50:42 AM
its not that easy.
the slave processor ML runs on, doesnt have access to the raw data stream as it seems :(
Hi,
I hope that you will succeed in making it possible to record in RAW for the EOS 7D.
Thanks a lot for your work. I will follow the evolutions (if they are possible :'( ).
Thx
Julian
In the latest push to bitbucket, there's a cleanup of a bunch of makefiles, and I notice there's one for 7D.203. Does anyone know if this will build a nightly that would run on the 7D 2.0.3 firmware??
It is just the actual one. The Alpha 2. Not for the EOS 7D RAW Video
g3gg0/a1ex only just registered but want to start out by saying thanks to you and thank you to the people around you that support you and make it possible for so many others to reap the rewards of your fantastic work!
Posting in here as for budget think 7D will be next purchase, I look forward to using ML and if something unexpected leads to unlocking RAW capabilities on dual digic then we will all be even more fortunate for receiving something through no efforts of our own.
See through the comments minority of people may have a few expectations that could tax your creative genius :)
Thanks again to you and the Team, love your work............
p.s. donated to EFF ;) Oh 40D ML!! w00t ;D
This thread feels like a ghost town.... hope never dies.
;D
Quote from: g3gg0 on May 14, 2013, 04:24:53 PM
if that would be the generic 7D user opinion ...
It is not.
Sorry, I have been away for a couple of days and I see a lot has already been said in this regard. But I need to say this and after that I'll be quiet again until I have something useful to contribute. I do not wish to be part of a group that makes complaints on behalf of 'all 7D users' because clearly they are not speaking for me. And I see not for a lot of other users too. There are unfortunately some loud individuals making a lot of fuzz, spoiling it for the developers and the patient, silent user group.
I am very happy with the 7D alpha 2, especially when looking back where we came from. The magic zoom is a godsend when working with fast primes. It is stable enough. Having to manually load it after every reboot is just a minor inconvenience.
Of course, I am as enthusiastic and anxious as anyone else to see new developments like RAW video of the newer Canons ported to the 7D too. But I am aware that the chance for this to happen is actually very small. I am glad that nowadays we at least have a functional alpha version for the 7D. A few years ago, the future did not look so promising. Look were ML is now. In the end there is just only one word fitting enough:
THANKS!
And back to my lurking mode again...
I think that we are all grateful.
It is sure.
I think we would all like this new feature is present on our EOS 7D. The price difference between the 7D and 5 is huge and many have a 7D. And the fact that there are two chips connected by a slow bus is the problem.
It is a little a hardware problem. Not a problem of performance. Many "little" Canon is able to record video in raw mode.
Dual core is not better ;-)
Let us be patient, respect team. It is a challenge for them, I'm sure that everything is done to succeed. If they can not do it, nobody can do it.
Thanks a lot at ML, g3gg0 and Alex.
How much is a possibility that raw video mode will be mounted in the future?
If it is a problem of hardware, is it impossible as a matter of fact?
Since it can give up purely if impossible, I want you to tackle the further development of the formal version of ML.
thanks g3gg0 and Alex.
Quote from: vegajay on May 21, 2013, 04:41:17 PM
How much is a possibility that raw video mode will be mounted in the future?
If it is a problem of hardware, is it impossible as a matter of fact?
You guys are asking questions that no-one can answer yet. The devs simply don't know until they go in and try, and see what is possible.
Currently, g3gg0 has mentioned that the 7D is tricky because of it's unique architecture. Whether this gets solved tomorrow, next month, or next year (or not at all) depends on a number of factors which are impossible to predict. All we can do is either use what we have and enjoy new stuff as and when it happens, or join the development effort if you have those skills to try and help move the project forward.
I totally agree but when you see the ambient enthusiasm , it is difficult for us. we are not members of the club...
That's why I am boring. Just like a child..at school. All the children have a toy, the must-have... and you are the only one who don't have it.
It is difficult. We feel excluded.
It is a sensation, it is not right. I know that they try. I know they make eventhing to manage. It is a challenge.
I thank them.
We don't want to be unpleasant.
Best Regards
Sure, we're all enthusiastic - that's why we are here, that's why we support the devs, and that's why we do what we can to help in the way of testing, bug reporting, feature suggestions and so on.
Enthusiasm is what made ML happen in the first place, and it's what keeps it moving forward, as long as the devs get a little respect and room to work - entitlement and impatience from the userbase doesn't really motivate these guys spending their time to do a quite difficult task...
EOS 7D needs You
(http://png-1.vector.me/files/images/7/4/741530/uncle_sam_thumb.png)
We support them. We encourage them like many people can be fans of a baseball team. Not really subtle but enthusiastic ... perhaps too.
It is not a lack of respect. We can just show us our motivation. I can not help them to develop.
I can pretend not to be interested and waiting They manage and download the FW after and don't participate.
I prefer (bad?) humor, some winks... It is my opinion. But I can wait in silence too.
Hi , this is my 1st post and as 7D owner I can only say congratulations for this well done job ! :)
I'm looking forward to a definitive porting of ML on 7D, and I've a question to put to developers : there is a evluation of power drain using ML on 7D ?
Bye
Sergio
Quote from: motopoppi on May 22, 2013, 03:32:12 PM
Hi , this is my 1st post and as 7D owner I can only say congratulations for this well done job ! :)
I'm looking forward to a definitive porting of ML on 7D, and I've a question to put to developers : there is a evluation of power drain using ML on 7D ?
Bye
Sergio
Hi, Sergio. There is no difference in power drain when using ML compared to the default canon firmware alone.
Just a quick question I read somewhere that magic lantern gives you the total number of shutter actuations taken with the 7D is that correct ?
That is correct. That number is actually stored by canon's default firmware. ML will display that information in the forms of: [number of times the shutter opens and closes for live view/movie mode] plus [number of times shutter has taken pictures] = [total number of actuation]
Menu-->DEBUG---> the 10th line
Quote from: edwmotion on May 16, 2013, 12:10:40 AM
7D isn't compatible with UDMA 7 cards, so maybe we'll never see full HD raw video working on 7D. :-*
I use a UDMA 7 card in my 7D, it works perfectly. It is from Trancend 400X
Although the 7D can record to UDMA7 cards, it seems the speed is limited to UDMA6 cards.
The 1000x cards on 5D3 can write at about 88MB/s, while on the 7d it tops out at about 66MB/s. A tad below the minimum needed for 1080p raw, it seems....
I'm seriously thinking of selling my 7D and get the 5D3 for the raw video...
This is not the same product and the same price. I can't make the same thing and I love believing that g3gg0 and the team will manage.
According the software media info I evaluated ML footage on my 7D and I am getting 89.6 Mbps on a UDMA6 card no less.
General
Complete name : Z:\Desktop\MVI_0285.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 438 MiB
Duration : 41s 8ms
Overall bit rate : 89.6 Mbps
Encoded date : UTC 2013-05-11 14:42:01
Tagged date : UTC 2013-05-11 14:42:01
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile :
[email protected]Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=15
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 41s 8ms
Bit rate : 89.6 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Original height : 1 088 pixels
Display aspect ratio : 16:9
Original display aspect ratio : 16:9
That's megabit not megabytes.
89.6 Mbps = 11.2 MBps. About 1/8th of a raw 1080 24p feed.
Quote from: feureau on May 23, 2013, 04:08:53 PM
Although the 7D can record to UDMA7 cards, it seems the speed is limited to UDMA6 cards.
The 1000x cards on 5D3 can write at about 88MB/s, while on the 7d it tops out at about 66MB/s. A tad below the minimum needed for 1080p raw, it seems....
I'm seriously thinking of selling my 7D and get the 5D3 for the raw video...
True, however you should consider this:
1920x1080 @ 24 fps --> 2,073,600 pixels, 14 bits @ 24 fps --> ~83.1 MB/sec
1920x900 @ 24 fps --> 1,728,000 pixels, 14 bits @ 24 fps --> ~69.2 MB/sec
1280x720 @ 60 fps --> 921,600 pixels, 14 bits @ 60 fps --> ~92.3 MB/sec
Drop 14 bit-depth to 12 bit-depth, which is about ~85.7%, and those numbers become:
~71.2, ~59.3, and ~79.1
This is dropping from 16,384 levels per channel to 4,096 levels per channel. In the real world, this is a negigable difference. Now, there will be a difference fropping from 12 bit to 10 bit, 4096 to 1024.
We can reduce the bandwidth a bit more by dropping the resolution and with how sharp and clean RAW is, we can upscale a touch to compensate. Not ideal, but if you have a clean image, there will not be any noticable difference. Let's try 1720x960:
1720x960 @ 24 fps --> 1,651,200 pixels, 12 bits @ 24 fps --> 56.7 MB/sec
This is a ~14% drop in bit-depth, ~11% drop in size, and voila! No one will notice the difference in resolution. You'll miss a focus pull more often than you will miss the resolution.
Now granted, the 7D's semi-unique architecture will make it insanely difficult to crack if we ever get RAW. But if it does, it will not be far behind the 5D3. It'll definately be better than the stock H.264.
Edit: We've had successful 1920x1280 recordings with the 5D3. This is a touch over 100 MB/sec
Those maths look really good, Digital Corpus! :D
I wonder if there's any work still being done on the 7D though. I haven't seen anything regarding the 7D in the bitbucket log or mentions of it anywhere lately.
Using -16 flag in ML's menu, I got around 12mb/s bitrate, only slightly more than the stock around 11mb/s bitrate, but the artifacts in screen are lookingly less than the stock bitrate.
Quote from: feureau on May 24, 2013, 06:47:59 AM
Those maths look really good, Digital Corpus! :D
I wonder if there's any work still being done on the 7D though. I haven't seen anything regarding the 7D in the bitbucket log or mentions of it anywhere lately.
Hi, I believe that an alpha 3 is ready and waiting for release, or the work was interrupted because the Dev wanted to invest his time to work on the 5D.
Quote from: g3gg0 on March 10, 2013, 11:52:32 AM
i hope too ;)
currently i am testing the new/changed features what effect they have on 7D and if their behavior is intended.
and there are a lot new features.
Quote from: g3gg0 on March 16, 2013, 12:53:51 AM
there are news. i am working on 7D.
oh wait, its not new :)
just added ML's vignetting correction to 7D, but needs some testing.
maybe HDR can also get implemented that way. we will see.
Quote from: g3gg0 on March 19, 2013, 12:39:48 PM
well, yes. there will be a next alpha in the near future.
but there is no date yet, as it is done as spare time job and depending on workload in main job and in family,
i have some more or less time for it.
Quote from: g3gg0 on March 28, 2013, 01:13:30 AM
well, currently i am implementing some very interesting stuff: modules
that is something i want to have in the next alpha.
as the 7D is quite popular, that new concept will get a broad user base that tests it ;)
didnt do much 7D-specific stuff yet
Quote from: g3gg0 on March 31, 2013, 12:32:26 PM
the current state has a stability problem.
sometimes when switching mode between play and recording, the camera screen stays black.
dont expect a new alpha the next days.
sorry for that.
Quote from: g3gg0 on April 08, 2013, 09:53:37 AM
@all:
about the alpha 3: we are currently finding out a lot of interesting stuff.
as long we are still in this process, it makes no sense to release an alpha.
we are currently enjoying finding out how to use it for cool features.
then let us make those cool new features user-safe, and you will see a new 7D/5D3 alpha that will amaze you.
Quote from: g3gg0 on April 26, 2013, 10:56:53 PM
i am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
Quote from: g3gg0 on April 26, 2013, 10:56:53 PM
Quotei am still working on YUV422 videos (continuous 12.5 fps works already).
i think it is able to record in RAW also, but first i want to get YUV422 working flawless.
will test it on 7D as soon it works on 5D3
I hadn't never read this. I am happy, it is hopeful.
I was not sure that they continue to be concentraded by the 7D. I was afraid that they prefer forget, a little, the 7D to work on the 5Dmk3 and all the cameras which are a little more simple to hack.
If you guys need any simple testing I'm here to help! I have no idea how to code but the least I can do is offer some testing and try to help that way. Thanks guys you're doing a sweet job!
Quote from: feureau on May 24, 2013, 05:42:36 AM
That's megabit not megabytes.
89.6 Mbps = 11.2 MBps. About 1/8th of a raw 1080 24p feed.
Your math is good but someone please correct me if I'm wrong but "All" canon cameras are measured in bits not bytes. Hence the term CBR=Constant bit rate, and I believe that's one of the reasons we install Magic Lantern to attain a higher "bit" rate, not bytes. Even in the panasonic GH2 ptools hacks that attain 72Mbps, again measured in only bits as with most audio and video data rate analysis.
Bytes are usually used for the storage required here is the constant bitrate formula for RAW (uncompressed video):
Storage and Data Rates for Uncompressed Video
Constant bitrate formula: Uncompressed data rate = color depths * vertical resolution * horizontal resolution * refresh frequency
Examples
24bit @ 1080i @ 30fps :24*1920*1080*30=1.49 Gbps.
24bit @ 1080p @ 60fps :24*1920*1080*60=2.98 Gbps.
The storage and data rates for the widely-used YCbCr 4:2:2 chroma subsampling uncompressed video are listed below:
525 NTSC uncompressed
8 bit @ 720 x 486 @ 29.97fps = 20 MB per/sec, or 70 GB per/hr.
10 bit @ 720 x 486 @ 29.97fps = 27 MB per/sec, or 94 GB per/hr.
Your error was in notation. Upper case 'B' is bytes, lower case 'b' is in bits.
g3gg0 does plan on returning back to the 7D's development, but his focus lies on the RAW video development and regular life (I assume). Right now ML is running off of the slave CPU in the 7D. As far as he can tell, now RAW stream touches the slave. So, for the time being, maybe until the end of time, we will not have RAW video. However, we will get a good copy of ML. In earlier tests I've recorded 220+ Mbps h.264 video with CRB 20 on my Samsung 16 GB cards.
Quote from: sharpmusic on May 25, 2013, 09:53:12 AMExamples
24bit @ 1080i @ 30fps :24*1920*1080*30=1.49 Gbps.
24bit @ 1080p @ 60fps :24*1920*1080*60=2.98 Gbps.
1080i @ 60 fps == 1080p @ 30 fps, fyi. Interlaced means that there are half as many rows.
Quote from: Digital Corpus on May 25, 2013, 10:01:34 AM
Your error was in notation. Upper case 'B' is bytes, lower case 'b' is in bits.
g3gg0 does plan on returning back to the 7D's development, but his focus lies on the RAW video development and regular life (I assume). Right now ML is running off of the slave CPU in the 7D. As far as he can tell, now RAW stream touches the slave. So, for the time being, maybe until the end of time, we will not have RAW video. However, we will get a good copy of ML. In earlier tests I've recorded 220+ Mbps h.264 video with CRB 20 on my Samsung 16 GB cards.
Yes sir, video and audio data rates have always been measured in bits hence CBR (constant bit rate, and High bit rate)
Quote from: sharpmusic on May 25, 2013, 10:07:03 AM
Yes sir, video and audio data rates have always been measured in bits hence CBR (constant bit rate, and High bit rate)
It's not necessarily audio and video. Its more the simple detail that it's a data rate. It's reduced down to bit for terms of how the controllers/processors interact, i.e. on a bit level. Storage is where bytes will come into play. Yes, we are still dealing with video in this context with RAW, but our storage devices for this medium are listed in the "X" notation for speed and MB/sec as well. As such, it's simpler for cmparing a RAW speed to teh card speed by using MB/sec instead of Mbps.
You know, considering that we're having a hard time with getting to the 7D RAW stream, which might never even happen, I wonder if it's possible to get an update for the 7D alpha that includes a lot of the stuff that's been added since alpha 2 came out?
Or just add it to nanomad's nightly build or something?
EDIT: Sorry if that offends anyone, didn't mean to come off as demanding/self-entitled or anything. Cheers.
Hi,
We are enthusiastic. We are not sure if it will be to catch the RAW stream to record it. Maybe we will be disappointed and frustrated. But I think that we must show Nanomad and the other that we are concerned and interested.
It is important to know that a lot of people intend for Nanomad and the team to motivate them.
I don't know if he has increased ?
At one point, he was optimistic. Maybe he is looking for a solution...Maybe he has abandoned. I don't know.
In the meantime, we are speculating to dream : The good CF speed by example...
Quote from: Digital Corpus on May 25, 2013, 10:03:48 AM
1080i @ 60 fps == 1080p @ 30 fps, fyi. Interlaced means that there are half as many rows.
In terms of raw bandwidth, yes. In terms of content and interpretation of the data, no.
-h
For the moment, no RAW video for the 7D... calculate the rate to buy the good CF if not necessary ;-) It is just for fun.
We have to be patient but we can expect. It is free :-) (not like a CF 1000x 128GB).
Hi, This is my first ever comment on this forum so it might sound rookie like but I'm wondering wouldn't it make MAGIC LANTERN happier if they work on EOS 7D for Raw shooting instead of 5D Mark III considering the fact that there are much more EOS 7D owners out there to download this amazing, time changing, Canon shivering software??
Quote from: Ozgur on May 27, 2013, 06:01:55 PM
wouldn't it make MAGIC LANTERN happier if they work on EOS 7D for Raw shooting instead of 5D Mark III considering the fact that there are much more EOS 7D owners out there to download this amazing, time changing, Canon shivering software??
Short answer: No.
Long answer: 5DMkII was what ML started on. Naturally, the successor would be the flagship model that ML works on. OTOH, the 7D Dual Digic makes it harder to work on compared to the single digic cameras, causing the 7D development to lag. We've only got to the first alpha in 3 years after the 7D was released. For a long time, it looks like the 7D was uncrackable, and it only got us to the slave processor of the two digic. RAW stream is on the master processor which is harder to access, if it is even possible anyway.
Add that to the constant nagging from the 7D community (me included), I imagine they'd be happier with developing the 5D-class cameras.
We must be patient.
I follow everything that is said about the EOS in general. I like it. I am sure that they work a lot : for all EOS and maybe for the 7D.
Will someone kindly tell me what is the interval of the jpg dump(which is located in the debug menu)?
Nevermind- finally found it in the audio menu....... very cool- able to push the set button after a pic and it will record a short audio message.
Dan
My old question:
I did a general search on the Magic Lantern Wiki and came up with nothing so here goes:
What are Audio Tags?
"We've enabled these features since alpha 1:
* Advanced Bracketing (HDR)
* Intervalometer
* Audio tags
* Bit Rate manipulation
* [EXPERIMENTAL] Modify card flush rate for higher bit rates
* [EXPERIMENTAL] Modify GOP size (down to ALL-I or up to 100 for better (?) details)
* a lot of minor fixes"
Thanks,
Dan B.
I have to buy a new card and will be prepared for raw 8)
what is the fastest write Speed for the 7D?, which card is working fast in 7D?
Lexar 1000x
(http://pel.hu/down/Lexar1000x7D.bmp)
Quote from: StefanKeller.AC on May 31, 2013, 10:56:30 AM
I have to buy a new card and will be prepared for raw 8)
what is the fastest write Speed for the 7D?, which card is working fast in 7D?
Nice, you're getting ready for raw.... :D
Maybe when we can shoot raw, 5000x cards will be released ;D
my Sandisk Extreme 16GB 60MB/s writes 53.8 MB/s
Quote from: edwmotion on May 31, 2013, 12:29:50 PM
Nice, you're getting ready for raw.... :D
Yes but... For the moment, it is not for now.... Just a dream...
Big THANKS to all the developers out there! Magic Lantern crew have made me very happy at many times.
1st when ML came to 7D- something I had decided was just not possible.
2nd when Alpha came out for 7D.
3rd when Alpha 2 came out. Really excited about bulb ramping + intervalometer.
4th a few days ago when I read that RAW rec had was working on non 5D cameras. -Have got a 50D winging its way to me right now because of this!
5th a few minuets ago when i read "uncompressed YUV422 and 14-bit RAW video recording " and 7D on the same page...
There seems to be a trend here. Things just keep getting better and better. THANKS!
I like reading that the developers are enjoying working on the 7D and thinking about all the cool things they can do with it. Happy to wait and wonder at what Alpha 3 may bring. Things like HDR video, YUV422 and not having to load ML each time are things that make me really excited for when Alpha 3 is released.
I would like to help in anyway possible for 7D developments. I know zero about code, but can follow instructions for tests etc :)
Thanks once again.
PS
Quote from: StefanKeller.AC on May 31, 2013, 01:14:03 PM
my Sandisk Extreme 16GB 60MB/s writes 53.8 MB/s
my Sandisk 8,16,32 all write at 40.9, 44.5,44.5 MB/s will see if I can get them faster.
Quote from: John-Jo on June 02, 2013, 01:56:48 PM
5th a few minuets ago when i read "uncompressed YUV422 and 14-bit RAW video recording " and 7D on the same page...
There seems to be a trend here. Things just keep getting better and better. THANKS!but can follow instructions for tests etc :)
Thanks once again.
Exactly the same thing. Wait...
I recently bought an aftermarket AC power adaptor so I wouldn't run out of power when filming. As the adaptor is not from Canon the camera says it cannot communicate with the battery. Unfortunately, it then asks for a soft restart (or whatever it's called) and this clears ML out of memory. Reloading ML manually causes the message about the battery to reappear, requiring another soft restart, sans ML. Bugger.
Not a big deal and I assume it won't happen when the final auto-loading version is released. I've been happily using the 7D Alpha 2 since Christmas and it's an incredible tool. I can manage fine with two batteries, I was just getting power hungry.
I wanted to give a heads up to anyone in the same situation. I apologise if this has already been covered, I haven't seen it anywhere but there's a lot of information around and I might have overlooked it.
I bought two cheap power adaptors ::). The last one claimed to be 100% Canon compatible, but non of those had the chip that is needed to be recogniced as an "original" battery so the camera wouldn't let me upgrade firmware (install ML).
I ended up with this nice-priced LanParte external battery which also can be charged when in use.
http://cheesycam.com/lanparte-external-battery-power-for-canon-dslr-test/
When ML autoload on 7d is released you can of course use your adaptor, but when setting the camera bootflag a battery with chip is needed.
Excellent option! Thanks, Breaker. I'd be more comfortable using DC into the camera if we're talking about unofficial gear. I can just imagine something shorting and giving the camera death by 240V (here in the UK). I know that anything sold in this country (such as my switching power adaptor) is extremely unlikely to do this but I have a vivid imagination. I'll check out the Lanparte.
Quote from: John-Jo on June 02, 2013, 01:56:48 PM
5th a few minuets ago when i read "uncompressed YUV422 and 14-bit RAW video recording " and 7D on the same page...
What? Raw video development on the 7D is not yet possible.. Where did you get that idea?
In the inside of this thread
According to the utterance of g3gg0, yuv422 has already operated by 12.5fps.
About rawvideo, there is no information yet.
Quote from: tonybeccar on June 03, 2013, 12:08:34 AM
What? Raw video development on the 7D is not yet possible.. Where did you get that idea?
My original quote is here:
Quote from: John-Jo on June 02, 2013, 01:56:48 PM
5th a few minuets ago when i read "uncompressed YUV422 and 14-bit RAW video recording " and 7D on the same page...
Happy to wait and wonder at what Alpha 3 may bring. Things like HDR video, YUV422 and not having to load ML each time are things that make me really excited for when Alpha 3 is released.
I read in this thread about uncompressed YUV422 @ 12.5fps as below...
Quote from: vegajay on June 03, 2013, 04:01:08 AM
In the inside of this thread
According to the utterance of g3gg0, yuv422 has already operated by 12.5fps.
About rawvideo, there is no information yet.
But djoulbdx says that RAW and YUV422 are the same thing?
Quote from: djoulbdx on June 02, 2013, 06:59:00 PM
Exactly the same thing. Wait...
Quote from: John-Jo on June 03, 2013, 07:03:40 AM
My original quote is here:
I read in this thread about uncompressed YUV422 @ 12.5fps as below...
But djoulbdx says that RAW and YUV422 are the same thing?
The same g3gg0 did not write anything more about it, and this suggests that he is not longer working on 7D
I 've wanted to say that I feel the same way when I saw "7D" on the same page of "RAW video" by example. But, we didn't knows if it will be possible.
We have to be patient. Of course, they are concentrated by the raw stuff, the raw buzz for the other cameras. We don't know if they progress but we are told to be patient. But it is very difficult.
Wait. Every day, I come on the forum (and on the chat) to seach "7D".
Regards.
Quote from: John-Jo on June 02, 2013, 01:56:48 PM
Happy to wait and wonder at what Alpha 3 may bring. Things like HDR video, YUV422 and not having to load ML each time are things that make me really excited for when Alpha 3 is released.
As I said I am happy to wait because each time they release anything it is much more than I ever thought possible. Love my 7D and the current ML. Smart cookies the ML crew. I have no idea about code / programming etc so always very impressed.
So.... Can someone please give me more info on YUV422 and RAW? Is YUV422 the colour spacing, and RAW the record format.? Could you have something that is YUV422 recording as a non RAW video file?
They way some of these posts read it is as if they are separate somehow.
"
old post:
Currently i am working on a module that records YUV422 data to card.
This code will only work when compiled from repository (there is no release yet)
5D3: can record 1904x1274 @ 12.5 fps
there are three major options
- Frame skipping: record every n-th frame. choose 2 on 5D3 in 25 fps mode to record with 12.5 fps *continuously*
- Single file: save some processing time by writing a single file. you have to split it later on your computer. (maybe the 422 converters will somewhen support this?)
- RAW mode: not working yet, just saving gibberish ;)
-g3gg0"
Quote from: John-Jo on June 03, 2013, 08:57:49 AM
So.... Can someone please give me more info on YUV422 and RAW? Is YUV422 the colour spacing, and RAW the record format.? Could you have something that is YUV422 recording as a non RAW video file?
Not knowing what the ML team thinks of, I will describe general understanding of the terms:
-Raw is something close to the image sensor raw data. Undeveloped, not applied demosaic, whitebalance, gamma, sharpening etc.
-YUV422 is a developed format, something resembling JPEG/h264, except that there is no lossy compression artifacts.
If compression artifacts is a problem to your application, then YUV422 may be the solution. If better highlight recovery, more accurate color correction, etc is what you need, then raw may be the solution.
-h
.
Well at first hello everybody,
Normally I just follow up this thread like every day since Alpha 2 released but I think now it is time for a post.
It seems that there is quite confusion about the differences between RAW and YUV 4:2:2 uncompressed.
At first RAW and YUV 4:2:2 uncompressed are not the same!
From now on it is getting technically, who does not care can skip from here.
What is YUV 4:2:2 uncompressed.
YUV defines the color space. While the camera Sensor gives out RGB Signal, it is being converted to YUV.
Y = luminance which we get by adding 0,299R + 0,587G + 0,114B
U = Cr which contains R-Y
V = Cb which contains B-Y
Cr & Cb are the digital Forms of U & V and later only called Cr & Cb
So you can see that our RGB Signal is splitted up and G (Green) is completely left out, but because Y Contains part of the green signal we are able to convert YCrCb back to our RGB Signal (this happens in your TV, monitor or any other playout device).
However, what is 4:2:2?
4:2:2 defines the Chroma subsampling and is defined the following
4 stands for full resolution while 2 stands for half resolution, but what does that mean for us?
Y : 4 = 1920x1080 pixels
Cr(U) : 2 = 960x540 pixels
Cb(V) : 2 = 960x540 pixels
So you can see that our Chroma is recorded by only the half of the real resolution
Now you might think NO WAY I don't this but now it comes
We are currently shooting with our 7Ds at 4:2:0 which states that our movie clips look like this
Y = 1920x1080 pixels
Cr(U) = 480x270 pixels
Cb(V) = 480x270 pixels
So far with YCrCb 4:2:2 now the uncompressed.
Uncompressed just means that we have no compression (well that seemed to be clear)
Since we have no compression on our Video the bitrate is defined by the sampling and our quantization which is normally 8 or 10 bit
So the bitrate for uncompressed YCrCb 4:2:2 at 8 bit and 25 Fps is calculated by this:
(1920x1080x8)+ 2x(960x540x8) x 25 = 791Mbit/s = 99MB/s
So now you now what YUV 4:2:2 is.
Now to RAW
RAW is simple, it is just data from the sensor completely untouched (in theory) in real life you will have some sort of compression in it.
Differences between RAW and YUV 4:2:2
RAW have to be interpreted by some programm before edit / YUV can be edited immediately
RAW gives you the most possibilities (and the need) for color correction
With RAW you set you white balance in the post / With YUV you have a fix white balance
What for what
If once we get all features we would have Uncompressed YUV 4:2:2 at the HDMI Port to record with an external device and for internal ether an compressed YUV 4:2:2 or a compressed RAW
If there is already a post like this then I wasted my time.
If there is anything wrong please correct
If you find any mistakes you can eat them ;)
Is there still no movie restart ability? That is a huge one for me. I can't use the 7D as my B camera without an operator in weddings since it turns off after 12-15 min. Is there any good solution yet?
Quote from: dswatson83 on June 05, 2013, 01:28:14 AM
Is there still no movie restart ability? That is a huge one for me. I can't use the 7D as my B camera without an operator in weddings since it turns off after 12-15 min. Is there any good solution yet?
Just finished testing the Auto restart in alpha 2 feature and sadly it did not restart. I turned On Movie Restart in the ML menu and hit record. My camera stopped recording at 12'08" and did not auto restart.
Quote from: mixed on June 04, 2013, 08:24:09 PM
What is YUV 4:2:2 uncompressed.
YUV defines the color space. While the camera Sensor gives out RGB Signal, it is being converted to YUV.
Y = luminance which we get by adding 0,299R + 0,587G + 0,114B
U = Cr which contains R-Y
V = Cb which contains B-Y
Cr & Cb are the digital Forms of U & V and later only called Cr & Cb
"YUV" is actually an error. There was an analog format back in the days called YUV, but YCbCr is not based on it. Possibly engineers and software developers thought that YUV was simpler to type than YCbCr. This is described in "Digital video for HDTV..." By C. Poynton
Quote
So you can see that our RGB Signal is splitted up and G (Green) is completely left out, but because Y Contains part of the green signal we are able to convert YCrCb back to our RGB Signal (this happens in your TV, monitor or any other playout device).
We can get back to rgb using the inverse mixing matrix, but if YCbCr and RGB are both limited to 8 bits, the conversion will be lossy (you need 9-10 bits for the YCbCr representation).
Quote
However, what is 4:2:2?
4:2:2 defines the Chroma subsampling and is defined the following
4 stands for full resolution while 2 stands for half resolution, but what does that mean for us?
There are (at least)
4:4:4
4:2:2
4:2:0
4:1:1
4:0:0
I don't know anyone that can explain the system to those number.
Quote
Y : 4 = 1920x1080 pixels
Cr(U) : 2 = 960x540 pixels
Cb(V) : 2 = 960x540 pixels
This is wrong, you are describing 4:2:0. 4:2:2 has half the horizontal resolution, but full vertical resolution:
Y : = 1920x1080 pixels
Cr(U) : = 960x1080 pixels
Cb(V) : = 960x1080 pixels
Quote
We are currently shooting with our 7Ds at 4:2:0 which states that our movie clips look like this
Y = 1920x1080 pixels
Cr(U) = 480x270 pixels
Cb(V) = 480x270 pixels
No, 4:2:0 is:
Y : = 1920x1080 pixels
Cr(U) : = 960x540 pixels
Cb(V) : = 960x540 pixels
Quote
Now to RAW
RAW is simple, it is just data from the sensor completely untouched (in theory) in real life you will have some sort of compression in it.
My Canon 7D produce uncompressed raw data in real-life. There likely is some processing (correction of bad/hot pixels) going on behind the scenes, though.
-h
@hjulenissen and @mixed.
Thanks for getting stuck right in to that topic! Always good to ask the questions you want answers to.
The main point for me being, RAW and YUV 422 are not the same thing.
Thanks again guys.
I would like to report a bug(or not) in this 7D Alpha2. While using LV>>jpg mode, which exists in the debug menu, the jpg sequence starts to record LV000001.jpg things like that. If I change battery or something else that will turn off the camera, the next time I tried to record jpg sequence through LV, as per the functions above, the new jpg sequence records in the same name LV0000001.jpg as the last ones recorded before turn off/restart the camera, so, eventually, the last jpg sequence was deleted, partially replacing by a new jpg sequence.
Another thing. My Lexar 800x CF is not fast enough to record the LV>>jpg jpg sequence. The jpgs were about 205k big, 24fps means that 205 x 24 = 4920k per second, times 8 into bit translate into around 40mb/s, the Lexar 800x CF should be fast enough to handle. I don't know what I have done wrong with the Alpha2 or the camera or the CF card.
I'm very impressed by all that work but I am starving to get a Stable Version for my EOS 7D.
Call me overprotective but I never trusted Alpha Versions ;)
The Stable Version for the 550D works great and I would like to see how it works on the much faster 7D.
S_3
I am working with alpha 1 and alpha 2 since they cam out and never had any problems. In this time i used my 7d for nearly 10 jobs, mostly documentary stuff, where i record hours of video. Have no fear;-)
Thanks for your time and effort working on this piece of code!
Hope to hear something positive about Raw + 7d, too:-)
Hey all you videoguys out there
When you bought a canon 7D was is for the 18 megapixel, rapid continous shooting and a better autofocus system OR do you buy it most for video shooting?
I think of my 7D as a still camera.
Seems to me that all yours demand on raw video for the 7D and higher output just delays any new release.
I,m happy with the auto AF microadjustments and other things i think that have been solved a while ago but after the alpha2
Just my thoughs ;)
We can be optimistic but I think that they favor the other developments for the EOS 5,6,600 etc... They have made us understand that they do not try to insist if it is too complicated and they preferred to work for other EOS. The Alpha 2 is surely the last version of ML for EOS 7D.
I have bought the 7D because it was the best DLSR for the price. The 5 and the 1 was really more expensive. The Video mode is good too and I have bought it for this function too.
I am sure that they can find bu .they have a life, a family, a job etc... and the Raw mode has their time. And for the other cameras, they can progress. They are stuck with the 7D.
Quote from: Jansten on June 08, 2013, 05:32:27 PM
When you bought a canon 7D was is for the 18 megapixel, rapid continous shooting and a better autofocus system OR do you buy it most for video shooting?
When I bought my 7D, was pretty much the only large sensor camera which has 1080p 24fps video. Plus I wanted a fast shooting camera at at least 8fps. The 5D Mk II didn't fit the bill at the time, this was before the community went ballistic over the 7D getting 24p and 5D2 had only 30fps.
If I were to buy a new camera for video today (regardless of system/lens ownership), it would probably a Nikon D5200, or the BMPCC (if it even comes out).
That being said, my favorite form factor seems to be the EOS-M right now. Only the soft video and slow autofocus (being addressed by firmware update) is keeping me away from it.
I think before everybody was talking about Raw-Video, the ML-Team had made some good impovements on their software and before eastern, there were comments saying "just a few more days". So in my impression there was work being done nearly to the final release of an alpha 3 but then Raw flooded the community. If i were a software engineer i would concentrate on this big thing too. But i don't think, that we won't see another version for our 7Ds. Perhaps if the major problems / implementations with raw are finished there will be time for stuff like an stable release for the 7D. I appreciate the work and time they invest for us so we can play around with these wonderful tools.
Personally I don't really care much for RAW. Sure it's great but it adds so much more work, processing power and filesizes. I'm pretty happy just shooting with Flaat on all-I, and would probably only use RAW for some testing fun. If I ever get to do big projects (that would need cinema quality), I'll probably rent a RED anyway. (even when they used 7Ds and 5Ds while shooting Avengers, so it'll be fine xD ).
I hear ya, the raw files do bring a shocking amount of detail though.
I'm pretty happy shooting Cinestyle and using Technicolor Cinestyle Color Assist for correction.
As far as the Red goes, have you ever used one? Talk about workflow! File sizes!!! While you're renting the Red (and all of its support gear) you might want to rent a crew too.
Quote from: Evil Flip on June 09, 2013, 09:30:26 PM
Personally I don't really care much for RAW. Sure it's great but it adds so much more work, processing power and filesizes. I'm pretty happy just shooting with Flaat on all-I, and would probably only use RAW for some testing fun. If I ever get to do big projects (that would need cinema quality), I'll probably rent a RED anyway. (even when they used 7Ds and 5Ds while shooting Avengers, so it'll be fine xD ).
7D's color and DR is seemingly fine, it only lacks details. How much I wish that Canon can give 7D stock 4:2:2 output.
Just a question about getting the highest possible detail with the current alpha 2 release. Do I max the bit rate (CBR) to the highest number possible without the video stopping? I can manage to get 2X CBR on my sandisk 60/mbs, and is there any other settings that I can enable to possibly pull out any more detail? Thanks!
Quote from: _iLiam on June 11, 2013, 01:28:43 AM
Just a question about getting the highest possible detail with the current alpha 2 release. Do I max the bit rate (CBR) to the highest number possible without the video stopping? I can manage to get 2X CBR on my sandisk 60/mbs, and is there any other settings that I can enable to possibly pull out any more detail? Thanks!
Look up a thread in this forum about details in All-I vs IPB shooting. (It's a huge thread, and a long debate. You won't miss it)
But I found the most detail I can get is by shooting All-I. Turn on video hacks, flush at your video framerate if you shoot with audio (you might need to lower your bitrate, naturally) and set the frames at 1. I can get about 350-400mbit/s with CBR at 20 with my 60MB/s sandisk.
You can't set the flush at 60 if you're shooting 60fps btw. It's set that way by the devs and no one would comment as to why.
Quote from: feureau on June 11, 2013, 07:01:05 AM
Look up a thread in this forum about details in All-I vs IPB shooting. (It's a huge thread, and a long debate. You won't miss it)
But I found the most detail I can get is by shooting All-I. Turn on video hacks, flush at your video framerate if you shoot with audio (you might need to lower your bitrate, naturally) and set the frames at 1. I can get about 350-400mbit/s with CBR at 20 with my 60MB/s sandisk.
You can't set the flush at 60 if you're shooting 60fps btw. It's set that way by the devs and no one would comment as to why.
Thank you so much for your help. I must be missing something huge though. I cannot find anywhere in ML to enable video hacks or shooting in ALL-I? I'm running alpha 2- 2.0.3. I just tried using the bitrate monster build to see if it was on there but it's not either. Any ideas? I seriously think i'm missing something very obvious but I just can't find it! Thank you
The first bitrate monster .FIR shoots All-I already. You just need to set the CBR/VBR to a high number. The second one is not All-I. Both do not have options to manually set this.
In the Alpha 2, in the screen where you set your CBR/VBR, there's an option for video hacks. Switch it to ON and you can then set the Flush and GOP (I forgot what it's called on that screen but it's the one immediately after Flush). Set the GOP to 1 and you're shooting All-I. (GOP stands for Group of Picture)
Good luck! :D
Hello,
what's the current state of ML-7D-development ? Anyone knows about that ? Haven't seen any posts from g3gg0 since a few weeks...
I would be very happy to have an auto-bootable version of ML, even if it's an alpha-version...
Thank you...
Quote from: feureau on June 13, 2013, 12:48:09 PM
The first bitrate monster .FIR shoots All-I already. You just need to set the CBR/VBR to a high number. The second one is not All-I. Both do not have options to manually set this.
In the Alpha 2, in the screen where you set your CBR/VBR, there's an option for video hacks. Switch it to ON and you can then set the Flush and GOP (I forgot what it's called on that screen but it's the one immediately after Flush). Set the GOP to 1 and you're shooting All-I. (GOP stands for Group of Picture)
Good luck! :D
I feel like such a fool. I wasn't pressing the Q button on the menu to bring up the sub menu! I knew I was missing something obvious. I've been going all of these months with only half of the settings ML shows! What a fool I am. Thank you so much Feureau. Fantastic help ;D
Quote from: _iLiam on June 14, 2013, 01:12:20 AM
I feel like such a fool. I wasn't pressing the Q button on the menu to bring up the sub menu! I knew I was missing something obvious. I've been going all of these months with only half of the settings ML shows! What a fool I am. Thank you so much Feureau. Fantastic help ;D
You're welcome! :D
Just a really quick question. I enabled sound on the canon menu. When I went into ML and enabled CBR video hacks and tried to record I get no sound. Does the video hack automatically disable sound ? Thanks for your help.
Go into the Canon menu and enable sound
Cheers...did that. Turned on sound on the canon menu. Went into ML and enabled video hacks. When I started to record it showed sound was disabled. Tried this a few times with no luck. Thanks for your reply.
Stay in ML set up the video hacks and after that enable Sound via menu.. If it stops recording right away you have too High X bitrate.. Or a too slow card.. Lower The values..
Thanks...that did it. :)
Quote from: jman on June 14, 2013, 07:48:53 PM
Cheers...did that. Turned on sound on the canon menu. Went into ML and enabled video hacks. When I started to record it showed sound was disabled. Tried this a few times with no luck. Thanks for your reply.
Yeah, that is rather quirky behavior the devs put in. If you turn on/change settings in the video hacks, ML automatically disables canon menu. It's maddening, but was told it was due to that people will set the flush/GOP incorrectly and crash the ML and then flood the forums about it.
Now we have people who got confused about not getting audio when using video hacks and flood the forums about it.
I'm having problems loading the ML. It used to work. When I press "Firmware Update" in the menu, it brings me to a screen that says the 7D is up to date. I hit update and immediately the entire camera shuts off and will not respond for an indefinite amount of time. nothing on either screen and the access light is off. Ive let it sit for quite some time and nothing. the only way get the camera to turn back on is to take out the CF card. upon removing the CF card a screen pops up that says the update file cannot be found. i have to then remove the battery and re-insert it to get the camera back to normal. I've tried with both ML and the canon 2.0.3 firmware. I currently have 2.0.3 installed. I've tried both a canon battery and an after market battery. the firmware is definitely in the root folder.
Any ideas? Ive searched and have found nothing.
Make sure the MAGIC.FIR is at the Root directory, your CF card should look like this...
DCIM
MAGIC.FIR
MISC
ML
Where DCIM, MISC, and ML are folders
Finally got some time to try focus stacking with ML. Got some really great results after figuring out how to get it working correctly and it saves a tremendous amount of time compared to manual focus stacking. Had to read the docs a few times to figure it out. I do have a few suggestions to make it easier to use and less frustrating.
The first issue I ran into was trying to move my 10x viewing spot around while trying to set the ending focus point. I have to get out of the ML menu, move the position, zoom in/out as needed, then go back into ML. That wasn't too bad but it would be much faster if I can zoom the display in/out and move the viewing point around while in the menus. Setting the starting point was more difficult when I had to be zoomed in 10x to ensure proper focus. This requires exiting the ML menu, moving the viewing point and zooming back in then going back to the ML menu. The problem arises when you start moving the focus setting (for setting the starting point) if you are not in the right place you can't see the part of the image you want for the starting focus point. If you exit the ML menu and come back in when you try to go back to the Set End Focus Point it always rezeros it. Since you can't zoom in and/or move the viewing point around while in the set focus menu item you only have one shot to get the starting focus point correct. If you mess it up or can't see the part of the image you want you have to start over. Plus, if you accidentally hit the wrong button, or press the multicontroller up or down vs left or right it zeros the focus point and you have to start over. I'd suggest two separate menu items for the start and ending points and an ability to exit and go back to either to fine tune the settings. Plus it would be tremendously time saving to be able to move the viewing point around and zoom in and out while setting the starting and ending focus points.
Quote from: mdwhaley on June 15, 2013, 10:16:48 PM
Make sure the MAGIC.FIR is at the Root directory...
yeah, it's definitely in the root directory.
A little heads up - I seem to recall someone having an issue with their autofocus with ML running. I was at an event this weekend, and someway through the event I was going to do some video, so I loaded up ML, shot some video, went back to shooting stills with ML still loaded.
At one point my 7D's autofocus stopped being able to focus - I was a bit concerned, checked all the usual stuff (lens on AF, changed auto focus modes and so on), but the camera wouldn't auto-focus on anything, even when the contrast should have given the AF no problems at all.
So I turned the camera off and on again to unload ML, and the auto-focus went back to being fine, lightning quick and accurate, as I'd expect.
So while this is not much of a bug report, there is a definite case of auto-focus failure shooting stills with ML loaded, for some reason. If I can I will try to play with this and check the settings of the auto-focus failed images and see if I can reproduce this or give some clues as to what might be happening...
-deleted-
Quote from: beej on June 16, 2013, 06:00:21 PM
A little heads up - I seem to recall someone having an issue with their autofocus with ML running. I was at an event this weekend, and someway through the event I was going to do some video, so I loaded up ML, shot some video, went back to shooting stills with ML still loaded.
At one point my 7D's autofocus stopped being able to focus - I was a bit concerned, checked all the usual stuff (lens on AF, changed auto focus modes and so on), but the camera wouldn't auto-focus on anything, even when the contrast should have given the AF no problems at all.
So I turned the camera off and on again to unload ML, and the auto-focus went back to being fine, lightning quick and accurate, as I'd expect.
So while this is not much of a bug report, there is a definite case of auto-focus failure shooting stills with ML loaded, for some reason. If I can I will try to play with this and check the settings of the auto-focus failed images and see if I can reproduce this or give some clues as to what might be happening...
I can confirm that this same thing happened to me before too.... I think there's some combination of settings that triggers this. I had to wipe ML and install from fresh.
Quote from: media100 on June 13, 2013, 11:51:15 PM
Hello,
what's the current state of ML-7D-development ? Anyone knows about that ? Haven't seen any posts from g3gg0 since a few weeks...
I would be very happy to have an auto-bootable version of ML, even if it's an alpha-version...
Thank you...
Yes, indeed!!! I wish that only we have the possibility to have an auto-bootable version... In the first post of this treat its say that was intentional...
Quote from: feureau on June 13, 2013, 12:48:09 PM
The first bitrate monster .FIR shoots All-I already. You just need to set the CBR/VBR to a high number. The second one is not All-I. Both do not have options to manually set this.
In the Alpha 2, in the screen where you set your CBR/VBR, there's an option for video hacks. Switch it to ON and you can then set the Flush and GOP (I forgot what it's called on that screen but it's the one immediately after Flush). Set the GOP to 1 and you're shooting All-I. (GOP stands for Group of Picture)
Good luck! :D
Didn't know about this! THANKS!!! Will trie this function :)
I'm LOVING THIS. I almost sh*t my pants when the 1st alpha came out. You guys are amazing! :D
Question: Is anamorphic desqueeze on the agenda for the 3rd alpha?
It would also help if the up/down functions on the multi-controllers (7D) were ignored when trying to move the focus to set the starting point for focus stacking. I've found an accidental up/down push on the multi-controller while trying to move the focus messes up the settings and I have to start over.
Since the beginning I noticed that the most of people are here to talk about video, very few of us talk about photographs and I wonder why: no interest about still images or what?
Quote from: angelom on June 20, 2013, 10:58:45 PM
Since the beginning I noticed that the most of people are here to talk about video, very few of us talk about photographs and I wonder why: no interest about still images or what?
Oh, there are interests alright. I've been using ML's intervalometer and focus stacking and bracketing. It's just that all those features are done and tested and ready to use at any time. I don't need to find out what I did wrong with ML in such that, I don't get audio with my video, for example.
Plus that RAW video is so hot right now...
Quote from: angelom on June 20, 2013, 10:58:45 PM
Since the beginning I noticed that the most of people are here to talk about video, very few of us talk about photographs and I wonder why: no interest about still images or what?
Well, i can't think of any more things needed to improve still shooting on our cameras.
Devs focus on video because that is the department in which these camera don't excel so there is a lot of room for improvement.
I guess that if any of us would come up with a feasible and really useful feature for still photography devs would be really keen to turn our words into reality.
Quote from: ilguercio on June 21, 2013, 06:07:51 AM
Well, i can't think of any more things needed to improve still shooting on our cameras.
Devs focus on video because that is the department in which these camera don't excel so there is a lot of room for improvement.
I guess that if any of us would come up with a feasible and really useful feature for still photography devs would be really keen to turn our words into reality.
Indeed! And there have been alot improvements since the 7D alpha 2 came out. Stuff like auto-ETTR and dot tune autofocus to name a few. And yet, we don't hear about the 7D port of them...
hi,
I just discovered this, thank you so much for the great efforts to get all these wonderful features out of my 7D!
I'm not sure if this is reported yet (I was trying Alpha2):
- LV gain shows no effect
- in Play-Mode "100% on AF point" just does 100% on center, independently of AF point
- ISO>6400 was not selectable in Movie mode
or maybe I'm doing something wrong :D... help would be greatly appreciated =).
Once again thanks and keep up the great work!
Quote from: charname on June 21, 2013, 02:02:55 PM
- ISO>6400 was not selectable in Movie mode
Disable highlight tone priority
Quote from: feureau on June 11, 2013, 07:01:05 AM
But I found the most detail I can get is by shooting All-I. Turn on video hacks, flush at your video framerate if you shoot with audio (you might need to lower your bitrate, naturally) and set the frames at 1. I can get about 350-400mbit/s with CBR at 20 with my 60MB/s sandisk.
You can't set the flush at 60 if you're shooting 60fps btw. It's set that way by the devs and no one would comment as to why.
Hi Feureau, I went to the ML MOVIE menu and enter in the submenu of CBR... and this is my configuration:
Mode: CBR
CBR factor: 20.0x
QScale factor: -8
Video Hacks: on
Flush every: 24 frames
GOP size: 1 frame
BuffWarnLevel: 70%
Wend i press the rec button it's start but stop immediately. The card that im using with this settings are a SanDisk Extreme 60MB/s 8GB. Im recording at 24fps (23.976) what you think that i should lower in my settings?
Quote from: feureau on June 21, 2013, 04:43:00 PM
Disable highlight tone priority
Hi, thanks for your quick reply. I disabled ALO (in camera) and HTP (both in camera and in ML ISO-submenu). What confuses me... I enabled "Warnings for bad settings" and he keeps telling me "ALO is enabled". Is there another location where to shut ALO off which I might have overlooked?
Btw: Bursting ISO to 25600 in camera mode works fine, but in video mode it's limited to 12500.
Does anyone know if the other features I adressed ("LV gain" and "100% on AF point") are just not working yet, or am I doing something wrong?
Quote from: arrinkiiii on June 22, 2013, 01:04:18 AM
Hi Feureau, I went to the ML MOVIE menu and enter in the submenu of CBR... and this is my configuration:
Mode: CBR
CBR factor: 20.0x
QScale factor: -8
Video Hacks: on
Flush every: 24 frames
GOP size: 1 frame
BuffWarnLevel: 70%
Wend i press the rec button it's start but stop immediately. The card that im using with this settings are a SanDisk Extreme 60MB/s 8GB. Im recording at 24fps (23.976) what you think that i should lower in my settings?
Change the flush to 4 and shoot without sound for maximum image quality. If you want sound, you need flush to stay at 24, so lower CBR to around 2.3
QuoteOh, there are interests alright. I've been using ML's intervalometer and focus stacking and bracketing. It's just that all those features are done and tested and ready to use at any time. I don't need to find out what I did wrong with ML in such that, I don't get audio with my video, for example.
+1
The sad thing is that "not-working video features" seem to stall developement completely.
I'd love just to have the working stills features in a Firmware that stays on my camera.
At the moment I feel like there is some featureitis: implementing *everything* (eventually RAW video either and whatever ideas come in future) in one complete package - but this may last an additional year - or two - and will eventually never come as the 7D becomes older and older, newer cameras come faster than the tiny community here can patch and it gets less interesting to the devs and users, as they give up and buy a ML-enabled camera second hand.
Probably it would be better to go small steps and give out what works already - at least to get out of alpha with a small subset of possibilities.
I do have the greatest respect for the devs here - they do fantastic work on something I don't understand a bit of.
Keep an eye on your private lives and don't care about the "I wannnnnt to have" posts - like mine :-)
--
owning two cameras - 7D and 40D - is not good for ones nerves at this forum ;-)
Quote from: feureau on June 22, 2013, 06:10:31 PM
Change the flush to 4 and shoot without sound for maximum image quality. If you want sound, you need flush to stay at 24, so lower CBR to around 2.3
Its work, THANK YOU =DD
Settings: (sound disable)
Mode: CBR
CBR factor: 20.0x
QScale factor: -8
Video Hacks: on
Flush every: 4 frames
GOP size: 1 frame
BuffWarnLevel: 70%
Do you need to have ON in the Video Hacks? One thing that i noted is that wend you turn of the camera the settings for the bit rate will go to default... its normal?
CBR 20.0x???? Is the quality much better than 1.0x?
Quote from: arrinkiiii on June 22, 2013, 09:26:31 PM
Do you need to have ON in the Video Hacks? One thing that i noted is that wend you turn of the camera the settings for the bit rate will go to default... its normal?
if you want to use the video hacks, setting the GOP and all, you have to turn it on. And yes, it doesn't save the settings. This is specific to the 7D. Devs said they don't want to have people complaining about settings that don't work, but now we have people confused over why the settings don't get saved. There were talks of how you can set the default values using the config file but no one would say which variables saved what.
Quote from: tonybeccar on June 23, 2013, 06:23:35 PM
CBR 20.0x???? Is the quality much better than 1.0x?
yes
Quote from: feureau on June 23, 2013, 06:53:59 PM
if you want to use the video hacks, setting the GOP and all, you have to turn it on. And yes, it doesn't save the settings. This is specific to the 7D. Devs said they don't want to have people complaining about settings that don't work, but now we have people confused over why the settings don't get saved. There were talks of how you can set the default values using the config file but no one would say which variables saved what.
Thanks for the info :D
It's already painful to upload ML every time, setting the bit rate and the ML FW it's to much for me :-\
I need to send a email to G3ggo, if he can make a Alfa 2.1 for not uploading every time the Magic Lantern Firmware. I know that every one that use a 7D wants this, more then everything... almost then everything (raw) ::) Petition?
Do you know any treat that I can read about the ML bit rate (GOP, CBR, Flush, All-I, etc) ?
Quote from: arrinkiiii on June 23, 2013, 08:33:35 PM
almost then everything (raw) ::) Petition?
Do you know any treat that I can read about the ML bit rate (GOP, CBR, Flush, All-I, etc) ?
Hi,
I think that they know many people are waiting for the RAW video feature for the 7D ( and crop zoom etc....)
But It is difficult and they maybe have cancelled to work on the 7D. They prefer working on the simple DIGIC camera to purpose many new functionnalities for the other DSLR.
Maybe, with a miracle, we will have a Magic Lantern Raw function. But... When I read what the developpers have said, I think we will never see an update of the ML2.3 α2
They don't write anything here, on this topic... no news....
Quote from: djoulbdx on June 24, 2013, 09:04:39 PM
They don't write anything here, on this topic... no news....
That doesn't mean this:
Quote from: djoulbdx on June 24, 2013, 09:04:39 PM
... When I read what the developpers have said, I think we will never see an update of the ML2.3 α2....
The fact they don't write anything here doesn't mean that they aren't working to the code, no need to loose time writing something here until they'll have really something to say.
Maybe you forgot that months ago there was no chance to have ML working on the 7D and probably no one would have make a bet on it, but then they found the trick and now we're enjoying it.
You all know that they must understand how to use/program the dual processors system, after that they probably will be able to upgrade ML with a lot of new features.
Right now we must let them work on it without any kind of pressure, asking the very same questions a lot of times is not useful for anyone.
+1 for autoboot version. My 7d is half broken (without any sort of AF), so I relay heavily on ML focus aids in photo mode.
Could I enable BOOTDISK flag on 7d with magic.disable_bootdiskf = 0 "like" operation under fir version of ML and then compile my own autoexec.bin using https://bitbucket.org/hudson/magic-lantern/src code?
Quote from: ty66 on June 25, 2013, 03:50:55 PM
+1 for autoboot version. My 7d is half broken (without any sort of AF), so I relay heavily on ML focus aids in photo mode.
Could I enable BOOTDISK flag on 7d with magic.disable_bootdiskf = 0 "like" operation under fir version of ML and then compile my own autoexec.bin using https://bitbucket.org/hudson/magic-lantern/src code?
Can you do this? I don't understand nothing about code =(( Yes, at least enable bootdisk flag for not upload everytime the ML. Is to much to ask anybody in this forum to make this? Any one knows how to do this? Forget RAW (not), just a simple (maybe not so simple) bootdisk flag for not uploading every time the beautiful ML.
autoexec.bin file should be generated by default when compiling ML. Unfortunately there is no bootdisk_enable stubs in 7d platform code.
Quote from: ty66 on June 25, 2013, 04:36:01 PM
autoexec.bin file should be generated by default when compiling ML. Unfortunately there is no bootdisk_enable stubs in 7d platform code.
Yes, is what i think :-\ :'( Damn, just a simple boot flag...
Quote from: angelom on June 25, 2013, 01:16:44 PM
That doesn't mean this:
The fact they don't write anything here doesn't mean that they aren't working to the code, no need to loose time writing something here until they'll have really something to say.
Maybe you forgot that months ago there was no chance to have ML working on the 7D and probably no one would have make a bet on it, but then they found the trick and now we're enjoying it.
They have written that It will be nearly impossible. It is written. You can read. Then, they don't need to come here to tell "nothing new" "nothing new"....
It is not the same problem that ML on 7D... They can not access to the 2 DIGICs for the RAW stream. They have managed to "enter", to hack the 7D but the problem is not that.
Then, they have written that if it is to difficult, there won't be any update for the 7D. The ML 2.3a2 may be the last one.
But I hope too... I have a 7D.
I have to send my 7d off to canon as it is refusing to talk to any of the batteries I have. quite a common fault apparently! annoyingly it stops me doing a firmware update >:(
its out of warranty so I have to pay myself but I wonder if they will be able to tell its done some above and beyond photography?
Quote from: djoulbdx on June 25, 2013, 06:42:57 PM
They have written that It will be nearly impossible. It is written. You can read. Then, they don't need to come here to tell "nothing new" "nothing new"....
It is not the same problem that ML on 7D... They can not access to the 2 DIGICs for the RAW stream. They have managed to "enter", to hack the 7D but the problem is not that.
Then, they have written that if it is to difficult, there won't be any update for the 7D. The ML 2.3a2 may be the last one.
But I hope too... I have a 7D.
"Nearly impossible" is not the same as "It's impossible".
They have written that's difficult and there're no reason not to believe them, only a fool can believe that's is simple to (re)write a firmware... again, "difficult" is not the same as 'it's impossible", so no reason to believe that the 2.3a2 could/would/will be the last one.
Quote from: edgardave on June 25, 2013, 10:32:13 PM
I have to send my 7d off to canon as it is refusing to talk to any of the batteries I have. quite a common fault apparently! annoyingly it stops me doing a firmware update >:(
its out of warranty so I have to pay myself but I wonder if they will be able to tell its done some above and beyond photography?
Try to pull out the little round battery for at least one hour... just a try...
Quote from: angelom on June 25, 2013, 10:56:26 PM
Try to pull out the little round battery for at least one hour... just a try...
Yes, I had the same problem last week, I pull out the little button battery 10 seconds and after no problem
Quote from: angelom on June 25, 2013, 10:55:08 PMso no reason to believe that the 2.3a2 could/would/will be the last one.
Of course but on one message we can feel their despair. I hope to have an new ML with Raw, but for the moment, now, they work on the Raw module for all the other cameras. You can read it too on the forum somewhere and I talked with a developper on the chat... idem...
As I wrote it here a few times before, anybody can make bootable 7D ML. Read back for details.
I use autoexec.bin from the beginning but the 7D ML has issues so I don't recommend to use it except for testing/playing.
Maybe 7D ML never come out from alpha stage because the developers always busy with exciting new findings like RAW video.
Don't forget ML was impossible on 7D almost for 3 years long...
So wait patiently or compile your own autoexec and enable your bootflag on your camera.
Quote from: Pelican on June 26, 2013, 09:51:00 PM
As I wrote it here a few times before, anybody can make bootable 7D ML. Read back for details.
I use autoexec.bin from the beginning but the 7D ML has issues so I don't recommend to use it except for testing/playing.
Maybe 7D ML never come out from alpha stage because the developers always busy with exciting new findings like RAW video.
Don't forget ML was impossible on 7D almost for 3 years long...
So wait patiently or compile your own autoexec and enable your bootflag on your camera.
Hi Pelican, can you post a link with the files already compile? For us, dumb people that don't know how to compile, have the possibility to have a bootable ML :D
Do you know what issues do you have with bootflag that you don't have without?
Thanks
+1 on showing us how to enable the bootflag. Somewhere on the forum a user explained how to compile ML from source. But of course my compiling skills are not good enough and don't wanna make mistakes with my expensive 7D! If you could show us would be GREAT!! And please tell us what issues there are with the bootflag enables! Or is it the same alpha with its current issues?
Thank you very much! You'll be a life saver!!!
PS: If g3ggo could warn us from making terrible unreversible mistakes because of doing this I would really appreciate it :D
Cheers!
I compiled 7D ML from repo with bootflag enabled.
To run, you actually need to downgrade to the older 1.3 7D firmware. It didn't work well. Like pelican said, I wouldn't recommend it to anyone. Ended up restoring to the 2.0 firmware and using the alpha 2.
If you want the full ML experience, better get another camera.
Quote from: feureau on June 27, 2013, 03:38:51 AM
I compiled 7D ML from repo with bootflag enabled.
To run, you actually need to downgrade to the older 1.3 7D firmware. It didn't work well. Like pelican said, I wouldn't recommend it to anyone. Ended up restoring to the 2.0 firmware and using the alpha 2.
If you want the full ML experience, better get another camera.
Damn :'(
Thanks for the info Feureau !!!
Quote from: Pelican on June 26, 2013, 09:51:00 PM
Maybe 7D ML never come out from alpha stage because the developers always busy with exciting new findings like RAW video.
Don't forget ML was impossible on 7D almost for 3 years long...
That's I wrote before.
A big challenge is to improve the ML alpha or to developp the Raw video on the 7D but it is less exciting..
Can't you downgrade firmware only to enable bootflags with dumper firmware and then upgrade firmware back to current version and then use ML alpha2 autoexec.bin. Or will firmware upgrade reset bootflags?
Quote from: ty66 on June 27, 2013, 11:23:50 AM
Can't you downgrade firmware only to enable bootflags with dumper firmware and then upgrade firmware back to current version and then use ML alpha2 autoexec.bin.
Yes.
Quote from: ty66 on June 27, 2013, 11:23:50 AM
Or will firmware upgrade reset bootflags?
No.
Quote from: ty66 on June 27, 2013, 11:23:50 AM
Can't you downgrade firmware only to enable bootflags with dumper firmware and then upgrade firmware back to current version and then use ML alpha2 autoexec.bin. Or will firmware upgrade reset bootflags?
Why this? Is better? will be more bug free ?
Quote from: arrinkiiii on June 27, 2013, 01:03:55 PM
Why this? Is better? will be more bug free ?
For run autoexec.bin automatically from the card.
Yes.
No.
Quote from: Pelican on June 27, 2013, 04:01:17 PM
For run autoexec.bin automatically from the card.
Yes.
No.
Thank you Pelican !!!
Stay in the same. I already appreciate having zebras, sound meters, etc... even always have to upload every time the ML FW.
Going to post an add in my local news paper:
"Urgent, Need an Developer for 7D ML " you never know ;D
hey guys!
I used to record a movie with cinemascop cropmark, but when I downloaded to the pc, the video was normal with no cropmark! what happened and how can I see the video as I shot it, with the cropmark?
Quote from: chris bouk on June 28, 2013, 10:28:30 AM
hey guys!
I used to record a movie with cinemascop cropmark, but when I downloaded to the pc, the video was normal with no cropmark! what happened and how can I see the video as I shot it, with the cropmark?
This is normal. The cropmarks are there as framing guide. You crop your video yourself on your own.
you mean that I have to crop the final video like the cinemascop crop marks? and which dimensions are the right dimensions about that? can you help me please?
Quote from: chris bouk on June 28, 2013, 11:40:39 PM
you mean that I have to crop the final video like the cinemascop crop marks? and which dimensions are the right dimensions about that? can you help me please?
What you editing in? If you shot at 1080p then you can drop your footage into a 1920x800 project and the project itself will be cropped correctly instead of having to do letterboxing with a mask.
I've got a little problem: Using compatible battery with no info chip I can't load ML. When I do firmware upgrade for ML, camera ask me to use the battery the same; then it restarts but without magic lantern. Is there a solution for this? Thanks
Quote from: danistuta on June 29, 2013, 02:40:16 AM
Is there a solution for this?
Buy a battery with the chip in it.
Hey!
I need help. I will use my waranty, so i need to delete ML alpha 2 from my 7D and don't know how. I did format the card, but that isn't enough. Does someone know how to delete it, so i can use my waranty on my camera?
Thanks!!
Just remove the card!
Do you have problems without a card? Please describe ...
Ciao, Walter
Yes. I have problem with AV button and i think that's the software problem. I've removed the card and reinstal canon firmware and it still doesnt work and than some friend told me, that i have to unistall ML from camera, not just from card
Reset all your camera settings to factory defaults and try again.
Remove both batteries (buffer battery = the small one, too) and let the camera rest for 5 minutes, reinsert both batteries and try again.
Ciao, Walter
To uninstall ML, all you have to do is format your memory card. Nothing is written to the camera. It runs from the card ONLY.
Using ML, even if it destroys your camera, does not void canon warranty. You can't void canon's warranty, you only have what's covered by the warranty and what's not.
70D is released and I have noticed that it has one exciting video capture feature of ALL-I encoding for me. Did a little search of ALL-I, and it brought me back to this thread. The greatest G3GG0 has already built-in this feature into 7D ML, test run a little and it doubles my file size. Can't wait to see when there will be an autoexec.bin released.
Quote from: Pelican on June 27, 2013, 12:23:42 PM
Yes.
No.
Thanks. Got it booting. Actually there is no need to downgrade firmware. Just run patched dumper firmware update on a camera with v2.0.3 firmware and that's all, you're ready to boot autoexec.bin. 7D alpha2 tag is compiling without any problems.
Quote from: ty66 on July 02, 2013, 10:18:52 PM
Thanks. Got it booting. Actually there is no need to downgrade firmware. Just run patched dumper firmware update on a camera with v2.0.3 firmware and that's all, you're ready to boot autoexec.bin. 7D alpha2 tag is compiling without any problems.
Wha-wha-wha-what????! We can???! Could you please be a GOD and orientate us OR better upload the compiled version??? DYING for a bootable alpha.. using it every day with my 7D!!!
Thank youuuu!!!! :)
Quote from: tonybeccar on July 03, 2013, 03:16:29 AM
Wha-wha-wha-what????! We can???! Could you please be a GOD and orientate us OR better upload the compiled version??? DYING for a bootable alpha.. using it every day with my 7D!!!
Thank youuuu!!!! :)
+1000 Pretty please :)
Quote from: ty66 on July 02, 2013, 10:18:52 PM
Thanks. Got it booting. Actually there is no need to downgrade firmware. Just run patched dumper firmware update on a camera with v2.0.3 firmware and that's all, you're ready to boot autoexec.bin. 7D alpha2 tag is compiling without any problems.
Do you having problems with the ML with the patch until now?
Can you upload for download?
Quote from: djoulbdx on June 26, 2013, 09:12:12 PM
Yes, I had the same problem last week, I pull out the little button battery 10 seconds and after no problem
thanks for the suggestion guys - tried that but no luck. looking at a few repair websites it is sometimes an earth connection on one of the boards... suppose i could take it apart and have a look.
now where's my hammer ;D
I've only just realised that this was available for my 7D - I've been looking forward to it for years! I must say, it's particularly good - so many great features.
I did just experience a lockup though - camera was sitting idle with the display on via an external monitor (HDMI). The display turned off and the red activity LED came on and stayed on. I couldn't turn the menu back on and even power cycled the camera (on/off switch). but it didn't clear the problem. I had to remove/replace the battery to get it working again.
I didn't have any custom bitrate settings etc - just the normal displays on.
I have the logs saved if you need them?
It seems that it doesn't care anyone at the moment. Seems nobody is working on ML for the 7D anymore.
Anybody can help me on this?
Wen i record at 24 fps in ML menu the best settings for the shutter speed is 1/48 and this is in green in the Lv. But wend i put in 60 fps what shutter speed i should use?
I can't go below 80 and its in red and at 125 of a second its stay in blue.
Best regards and thank youuuuu 8)
I'd like to know:
1) Is there a way to set AutoISO in ML for video?
2) What's procedure to autostart ML on 7d?
Thanks.
@danistuta: this will respond your second question:
Quote from: feureau on June 27, 2013, 03:38:51 AM
I compiled 7D ML from repo with bootflag enabled.
To run, you actually need to downgrade to the older 1.3 7D firmware. It didn't work well. Like pelican said, I wouldn't recommend it to anyone. Ended up restoring to the 2.0 firmware and using the alpha 2.
If you want the full ML experience, better get another camera.
I read there was no need to make a downgrade...really possible?
There is no need to downgrade firmware to enable bootflags. Dumper firmware is just a hacked/patch version of regular/official firmware image. You need to run it just like any other firmware update/downgrade but it will not actually downgrade nor update your camera firmware. Instead it just hacked code which will dump memory to CF card and enable bootflags.
Look http://magiclantern.wikia.com/wiki/7D_support#Before_g3gg0.27s_hack
Take a note that you need to use older version of EOS utility to run older versions of firmware images or you will get firmware image not supported or something like this error. I did use EOS utility 2.10.2.0
Quote from: ty66 on July 12, 2013, 06:34:15 PM
There is no need to downgrade firmware to enable bootflags. Dumper firmware is just a hacked/patch version of regular/official firmware image. You need to run it just like any other firmware update/downgrade but it will not actually downgrade nor update your camera firmware. Instead it just runs hacked code to dump firmware and enable bootflags.
Look http://magiclantern.wikia.com/wiki/7D_support#Before_g3gg0.27s_hack
Take a note that you need to use older version of EOS utility to run older versions of firmware images or you will get firmware image not supported or something like this error. I did use EOS utility 2.10.2.0
Thank you very much for the information. Though I still don't quite get it. There is the bspatch which it says you should apply it to firmware version 1.1.0. And then run the firmware update and it'll do what you say. It doesn't say to apply the patch to the 2.0.3 firmware. What should we do? The idea is to still use the 2.0.3 firmware on the camera.
Could you please do a step by step guide for us dummies?? It's a very risky process.
Thank you so much again!
Cheers!
Just follow the info from Google group http://groups.google.com/group/ml-devel/browse_thread/thread/9636782a8f25bb7d
Download patch.bsdiff from google group, bsdiff program to run the patch and 1.2.3 version of Canon 7D firmware. Then apply patch.bsdiff to v1.2.3 Canon 7D firmware file. I wish there would be some MD5 sums to verify the patched file but unfortunately there is not.
Then install EOS utility 2.10.2.0 and flash the patched 1.2.3 version. As said previously it just runs hacked code which will dump the memory to CF card and enable bootflags. It will not downgrade your firmware to 1.2.3.
I don't know the internals behind this patch so I can't comment on risk factor but I suggest you to be prepared (mentally and financially) to brick your camera. I know I was, I needed autoboot just that much.
Oh that's much more clear! Thank you so much!
So, now you are working just fine with an autobootable version of ML A2 in your 7D right??? Have you experienced any kind of problems??
I really do need the autobootable version, it's driving me crazy to start it every time.. will consider the risk factor after some time if nobody complains about some bricked 7D..
Would be so nice if g33go could comment something about the risk of doing this.. an advice would be nice :)
Thanks again man!!!
Cheers!
Hi, I'm a ML user from about 1 year, first on 55od and now on 7d.
I'd like to ask you something about the 7d, audio corner. After I boot ML, even if in the ML menù the light on 'audio' is turn to green, I can't see the audio meters on the live view top. This happen only in the pre-rec session, because then they appear when I press the recording button and they are active during the recording.
I've seen in a tutorial on youtube that the meters should be visible also in the pre rec situations, as it happens to me with the 550d. Is it possible? Eventually, how can I do ?
However. Thank you for what you did. Magic Lantern and Magic lantern team is something great.
ps. hope to see a autobootable version,first or then, it would help a lot !
Quote from: tonybeccar on July 13, 2013, 01:07:06 AM
So, now you are working just fine with an autobootable version of ML A2 in your 7D right??? Have you experienced any kind of problems??
It's running fine. You can also use non bootable CF card to run the
official alpha 2 version instead of autoexec/autoboot version.
Quote from: ty66 on July 13, 2013, 02:08:05 PM
It's running fine. You can also use non bootable CF card to run the official alpha 2 version instead of autoexec/autoboot version.
Did you have to build the autoexec version yourself or is it somewhere available for download?
Quote from: pfluger on July 13, 2013, 10:14:44 PM
Did you have to build the autoexec version yourself or is it somewhere available for download?
It's not available officially so I did not search. alpha2 tag is compiling without any problems but latest code had some problems few weeks ago.
There is tons of guides and even virtual machine images where everything is pre-installed, so you have to just check out the alpha2 tag code and run make 7D command.
Hello ty66.
I'd like to get to be able to compile by myself Alpha2.
But I'm so confused with what to do and how to do :o that I gave up :-[
Furthermore, I'm running a Mac with Snow Leopard, whiwh doesn't seem to best the best equipment to compile.
Would you please be kind enough to send me your compiled version of Ml Alpha2 ? Or tell me clearly what to do to compile by myself (the discussions about compiling are too complex for me)
Regards
Thierry
I tried this myself- could follow this tutorial (http://www.magiclantern.fm/forum/index.php?topic=6783.0) and generate the unified (all camera version) but not the 7D- would just give me and error 2. Still don't understand how to apply the alpha2 tag mentioned before but did see a new entry in the code for the 7D where Alex remove the playback tricks for the 7D. So I hope we will get a beta and/or someone will post an autoboot version.
Any build with the Dual ISO module coming soon?
Quote from: dbals on July 17, 2013, 03:27:40 PM
I tried this myself- could follow this tutorial (http://www.magiclantern.fm/forum/index.php?topic=6783.0) and generate the unified (all camera version) but not the 7D- would just give me and error 2. Still don't understand how to apply the alpha2 tag mentioned before
I'am not 100% sure but I must have used "hg clone -r ML-7D-Alpha2 https://bitbucket.org/hudson/magic-lantern" to check out code. Anyway ML-7D-Alpha2 is tag name you want to use to check out the code from server.
This looks promising?! http://www.slashcam.de/news/single/Canon-5DMK3-7D---Erweiterter-Dynamic-Range-durch-M-10771.html
Quote from: _iLiam on July 18, 2013, 12:42:28 PM
This looks promising?! http://www.slashcam.de/news/single/Canon-5DMK3-7D---Erweiterter-Dynamic-Range-durch-M-10771.html
Yep, but for us it's photo only (since it's by shooting RAW).
But any one have compile this Dual iso for the 7D ?
I want to trie but dont know how to compile.
Quote from: arrinkiiii on July 19, 2013, 03:46:30 AM
But any one have compile this Dual iso for the 7D ?
I want to trie but dont know how to compile.
I know how to compile, but I'm not brave enough to try my own build ;D ;D ;D
It took 3 months from the point I knew how to compile ML until I had courage to run it on my camera ;)
This anxiety definitely needs a name!
Seriously! There is - for example - a name for fear of bellybuttons and I don't know anyone suffering this.
And the "fear of installing a self compiled ML version on one's camera" seems more widely spread but unnamed!
Ciao, Walter
PS: Fear of bellybuttons is called Omphalophobia.
Quote from: a1ex on July 19, 2013, 08:56:04 AM
It took 3 months from the point I knew how to compile ML until I had courage to run it on my camera ;)
You know, if you compile ML for 7D and post it here, I bet some lunatic here has the balls to run it in their camera. Then we can take it from there...
Quote from: feureau on July 19, 2013, 01:54:59 PM
You know, if you compile ML for 7D and post it here, I bet some lunatic here has the balls to run it in their camera. Then we can take it from there...
Ok, I'll do it ASAP and see what happens.
I know some people are using the 7D with HIGH bitrates... does someone have like a comparison of the video with and without the better bitrate?? I've read that people are shooting in ALL-I and 20x CBR... that seems too much!!! I'm thinking of investing in high speed cards but I'm not too sure about it...
Thanks!
Quote from: tonybeccar on July 20, 2013, 04:40:28 AM
I know some people are using the 7D with HIGH bitrates... does someone have like a comparison of the video with and without the better bitrate?? I've read that people are shooting in ALL-I and 20x CBR... that seems too much!!! I'm thinking of investing in high speed cards but I'm not too sure about it...
Thanks!
I posted a comparison between ALL-I and IPB and max CBR and low CBR a few pages back.
Hi,
with the autoexec.bin, what files and directories must be installed on the camera card ?
I guess the ML directory included in the Alpha2 release, and ????
And I've just understood that the bootflag must be I don't know what ....
My poor brain has just exploded.
So I will wait someone to post the "ready to use" compiled ML-Alpha2 taht you just copy on the flash card and it works without any problem. you know, I've only got the "drag and drop" skill :-\
Thierry
Quote from: tonybeccar on July 20, 2013, 04:40:28 AM
I know some people are using the 7D with HIGH bitrates... does someone have like a comparison of the video with and without the better bitrate?? I've read that people are shooting in ALL-I and 20x CBR... that seems too much!!! I'm thinking of investing in high speed cards but I'm not too sure about it...
Thanks!
Hi @tonybeccar, did you find any video comparison between ALL-I and IPB and max CBR and low CBR ??? I went some pages back and didn't find anything.
Quote from: feureau on July 19, 2013, 01:54:59 PM
You know, if you compile ML for 7D and post it here, I bet some lunatic here has the balls to run it in their camera. Then we can take it from there...
Indeed !!!
Hi, I'm new in the forum and I would like to ask if there are any further improvements on the 7d. I understand that is hard to manage with a dual processor camera but I'm curious if there is anyone working on the 7d to solve the case with raw video , dual iso and maybe a next alpha release. It seems that there's more interest on the rest of the cameras since its easier on development, especially now with all this amazing new features that magic lantern team has succeeded.
It's sad that all this year's such a great camera like the 7d had and still has problems on further development. I'm asking this because magic lantern's software for canon's dslr's is a must for film making and 7d doesn't seem to catch up with the rest. In this case what do we do, buy a new camera to benefit all the features that ML has to offer or hopefully wait for someone to figure it out?
Thanks ML Team for all the effort and time that they given for as!!
Quote from: pest01 on July 24, 2013, 03:24:28 PM
Hi, I'm new in the forum and I would like to ask if there are any further improvements on the 7d. I understand that is hard to manage with a dual processor camera but I'm curious if there is anyone working on the 7d to solve the case with raw video , dual iso and maybe a next alpha release. It seems that there's more interest on the rest of the cameras since its easier on development, especially now with all this amazing new features that magic lantern team has succeeded.
It's sad that all this year's such a great camera like the 7d had and still has problems on further development. I'm asking this because magic lantern's software for canon's dslr's is a must for film making and 7d doesn't seem to catch up with the rest. In this case what do we do, buy a new camera to benefit all the features that ML has to offer or hopefully wait for someone to figure it out?
Thanks ML Team for all the effort and time that they given for as!!
Yes, it's all true. Better to buy a new camera. Nobody is able to continuous the work of g3gg0 on the 7D. Im waiting that anyone can make a compile version of the dual iso, and so far... nothing. Im on the wrong profession... i should be a programmer ;D
yep, the RAWvideo thing kinda stole our thunder.
Audionut uploaded a build with Dual Iso module here: http://www.magiclantern.fm/forum/index.php?topic=7139.msg61623#msg61623
You can try if you're brave (he didn't test).
I guess that I am one of those "luna"s. I load Audionut's autoexec.bin with Alpha 2 into 7D, nothing happens. I mean really nothing, the ML didn't load into camera. I download everything in Audionut's 7D build directory and put them all in CF card's root directory. And start up the camera again. Nothing happens, again. I don't visually see that my camera is damaged neither.
I assume the 7D needs a devkit first before being able to use these new builds.
Quote from: Audionut on July 25, 2013, 05:05:11 AM
I assume the 7D needs a devkit first before being able to use these new builds.
:( Damn...
See this for how to enable the bootflag: http://www.magiclantern.fm/forum/index.php?topic=3974.msg58898#msg58898
The only issue is that one can't legally distribute that FIR file, so you must create it yourself.
Quote from: a1ex on July 25, 2013, 05:51:38 AM
See this for how to enable the bootflag: http://www.magiclantern.fm/forum/index.php?topic=3974.msg58898#msg58898
The only issue is that one can't legally distribute that FIR file, so you must create it yourself.
Know i understand why not exist one compile version for the 7D... because it's not legal !!! Good to know the reason :D
...but still, went to see the link but can understand how to do it :-\ ...maybe Audionut can put a version with the bootflag and dual isso in one folder that you just need to put in the CF card and tries out this wonderful feature in the 7D ::)
Not a programer but i can be a tester !!!
Successfully enabled bootflag and loaded Audionut's autoexec.bin. Bootflag on card should be enabled too. But modules are refusing to load.
Some screens
https://dl.dropboxusercontent.com/u/4624786/VRAM0.png
https://dl.dropboxusercontent.com/u/4624786/VRAM1.png
Any tips?
Boot time on 133x card is 3 seconds, 400x - 1 sec.
Try just the Dual_ISO module on the card first.
Quote from: Audionut on July 25, 2013, 11:14:45 AM
Try just the Dual_ISO module on the card first.
No luck
https://dl.dropboxusercontent.com/u/4624786/VRAM2.png
I finally managed to get autoboot working. I thought it might help someone if I shared roughly the steps I took:
- Get the 7D 1.23 firmware file (7d000123.fir) and patch per the instructions at http://www.magiclantern.fm/forum/index.php?topic=3974.msg58898#msg58898
- Flash this patched firmware file using EOS Utility. I used a very old 2.8.1.0 version of EOS Utility. I got an error (something like cannot write to media card). I could work around it by putting the 1.23 fir file on the CF card and then starting the firmware update with EOS Utility. It still showed the error message but then started the firmware update using the .fir file I copied manually. I recommend using an empty CF card.
- Take the CF card out of the camera.
- If the flashing was successful you should see a couple of new files on the CF card (named something like ROM...bin). You can delete them.
- Copy the ML folder from the 7D Magic Lantern Alpha 2 to the CF card. Copy the autoexec.bin to the root folder of the CF card.
- Download the EOScard utility. You can find a link at http://wiki.magiclantern.fm/3rd_party_software
- Enable the EOS_DEVELOP and BOOTDISK flags (not sure if EOS_DEVELOP has to be enabled, but it didn't work without it for me)
- Put the CF card back in and start the camera. You should now be able to access Magic Lantern as usual by pressing the trash button.
Disclaimer: These steps worked for me, but I take no guarantee these will work for you :)
Quote from: xmd5a on July 25, 2013, 11:31:01 AM
No luck
https://dl.dropboxusercontent.com/u/4624786/VRAM2.png
Pretty sure those errors are relating to raw.c, and this won't be included for 7D as it doesn't do raw video.
Or,
#undef FEATURE_EXPO_ISO_DIGIC // not working, no idea why -> test on master?
I've removed that line from features.h and it appears to have compiled fine.
You can try the updated build here https://www.dropbox.com/sh/yp6dl9i104i1j2g/9Ta_9074YP
Big Fat WARNINGI have no idea of the consequences of my changes to the code. I don't have my own 7D to brick first.
And to be honest, I think the problems are more related to raw.c then anything else. The build is there for you to try and if are feeling brave. But it comes with no warranty.
Quote from: Audionut on July 25, 2013, 12:02:01 PM
Same error with the new version.
(http://pel.hu/down/DUALISOERR.BMP)
Quote from: Pelican on July 25, 2013, 01:30:04 PM
Same error with the new version.
(http://pel.hu/down/DUALISOERR.BMP)
Hey, Pelican. Can you add this build to use with the EOS card please? :D
Quote from: feureau on July 25, 2013, 04:37:09 PM
Hey, Pelican. Can you add this build to use with the EOS card please? :D
If somebody can produce regularly nightly builds on a constant link (like Nanomad do with other cameras) then I will set EOScard to use that link.
Edit:
Also, if someone could provide compiled modules then EOScard can install them too.
YESSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!! :D :D :D :D :D :D :D Will test it tomorrow as I don't have my camera with me!!! THANK YOUUUUUUUUUUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!! Hope everything works fine! And oh my, the new menu!! :)
Quote from: Pelican on July 25, 2013, 01:30:04 PM
Same error with the new version.
I've reverted a1ex's auto recovery option which I think will fix that error.
Updated build https://www.dropbox.com/sh/yp6dl9i104i1j2g/9Ta_9074YP
I'm confident it's going to get stuck on wanting DxO results, but I need to see what error message it's spits out after my last changes before I play with more changes.
edit: There's an updated module in the test build folder in the above link you can try. Not sure if you need to update the bin file, but I've included it anyway. It's an ugly hack to the module which will be missing menu entries (dynamic range gained - midtone overlapping), but if it works!
It works! Captured a dual-iso CR2 with "test build". Testing now. Thanks!
Hi folks,
Any chance to get a "ready to use" file - even with needs of reloading at each start?
wbr
I have no luck with Audionut's latest build @reply 721 neither.
Quote from: oli4h on July 26, 2013, 08:37:52 AM
Hi folks,
Any chance to get a "ready to use" file - even with needs of reloading at each start?
wbr
Only a few developer has the tool to make a .fir ML version but everybody can compile the autoexec.bin.
What do you mean ready to use?
Put an ML folder from the 7D alpha2, get the 3 files from the link below and it is ready to use.
Edit: put the 7D_203.sym and the dual_iso.mo to ML/MODULES
Quote from: Audionut on July 26, 2013, 04:53:08 AM
edit: There's an updated module in the test build folder in the above link you can try. Not sure if you need to update the bin file, but I've included it anyway. It's an ugly hack to the module which will be missing menu entries (dynamic range gained - midtone overlapping), but if it works!
It can load the dual_iso module. :)
Quote from: mucher on July 26, 2013, 10:32:00 AM
I have no luck with Audionut's latest build @reply 721 neither.
What's wrong?
Try the test build folder...
After testing both versions for 3 hours I can say that their behavior looks like identical. All of them hangs camera like a hell. It is hard to take pairs of photos - one with dual iso and regular one. Camera very often throws Err 70. Removing battery helps. Also camera often hangs while saving dual-iso photo to card, switching to LiveView (with Dual ISO module "ON" of course).
Current version of cr2hdr does not works properly with default settings (Recovery ISO 1600). It returns DNGs with strange colors. But if I set recovery ISO to 100 and camera ISO to 1600 it works as intended.
Option "Dual ISO - Alternate frames only" was throwing Err 70 every time I tried it.
Interesting...
For me it's worked like a charm. No hangout, no ERRxx, nothing.
Edit:
Yes, cr2hdr makes pink/magenta in the highlights in both situation (100-1600, 1600-100)
Quote from: Pelican on July 26, 2013, 12:30:49 PM
Interesting...
For me it's worked like a charm. No hangout, no ERRxx, nothing.
Edit:
Yes, cr2hdr makes pink/magenta in the highlights in both situation (100-1600, 1600-100)
Tried again both versions of dual_iso.mo from last build. Same results - there are very unstable. ML works like a charm until I enable dual ISO module :(
I would only use it in photo mode for now, not live view.
I have no idea where to start to fix pink highlight problem.
Quote from: Audionut on July 26, 2013, 01:32:00 PM
I would only use it in photo mode for now, not live view.
I have no idea where to start to fix pink highlight problem.
I just take 1 to 30 pictures in photo mode and it hangs with err70 or card led lights and camera does not respond forever.
Pink highlights looks like a problem of cr2hdr because CR2's embedded jpeg-preview is ok.
I'll try and post one more build tonight when I get home.
Try this build: https://www.dropbox.com/sh/yp6dl9i104i1j2g/9Ta_9074YP
Update all files from the link.
edit: removed, to buggy.
Quote from: Audionut on July 26, 2013, 05:08:12 PM
Try this build: https://www.dropbox.com/sh/yp6dl9i104i1j2g/9Ta_9074YP
Update all files from the link.
I'm about to try it. Already enabled autoboot, do you think is safe enough?
Quote from: britom on July 26, 2013, 05:21:28 PM
I'm about to try it. Already enabled autoboot, do you think is safe enough?
It's safer then the last build, as I added an undefine back in that I took out earlier.
I'd recommend staying under ISO 800 as per this post (http://www.magiclantern.fm/forum/index.php?topic=7139.msg59971#msg59971).
Still hangs with Err70. First time I took 3 photos and got Err70, second time - 5 photos, third time - 3 photos.
Quote from: xmd5a on July 26, 2013, 05:29:45 PM
Still hangs with Err70. First time I took 3 photos and got Err70, second time - 5 photos, third time - 3 photos.
Any error logs?
Only this. It is a log from previous version
https://dl.dropboxusercontent.com/u/4624786/CRASH00.LOG
I'm leaving for two days now
It seems that I'm doing something wrong.. I think I have another .FIR file... I don't have the new menu, it's exactly like the old alpha, I don't have the modules tab and it doesn't autostart after reboot... what am I doing wrong?? Is there a compiled .FIR that I'm missing?
Thanks!!!
Ok, I see I have to follow a series of steps first!! Now I can't find anywhere the 1.2.3 firmware :/
Putting the pieces together now.. it's quite complicated! Anyone can help me patch the 1.2.3 FIR with the bsdiff patch??? I have 2 files.. bsdiff and bspatch.. what to do? From the cmd I dont quite understand how to patch que .fir.. it asks for a newfile but never creates it.. Please a more detailed guide??? :)
Thanks!!
Quote from: tonybeccar on July 26, 2013, 08:11:47 PM
Ok, I see I have to follow a series of steps first!! Now I can't find anywhere the 1.2.3 firmware :/
Check out the signature of Pelican and click on the link.
In his folder you can find "eos7d123.exe".
Had multiple orgasms when the camera autobooted ml. Dual ISO module loaded without any error but shows Error 70 when i press the zoom button :/ Everything else that worked on the alpha2 is working. Plus now my camera autoboots ML!. Haven't tested movie restart yet.
This is awesome and i want to thank everybody who worked on this.
If someone needs and if i have some free time i can make a noob guide with detailed steps, with my weird english of course.
Pd: DAMN! WE NEED RAW VIDEO! :B
BTW the error logs:
https://dl.dropboxusercontent.com/u/43043701/CRASH00.LOG
https://dl.dropboxusercontent.com/u/43043701/CRASH01.LOG
https://dl.dropboxusercontent.com/u/43043701/CRASH02.LOG
I released a new version of EOScard with some bugfix of unzipping ML files/folders.
I've also made Audionut's release available for the software, so EOScard can install 7D ML alpha2 with dual iso and file manager modules from now.
I still haven't experience any crash or error with this build but others have serious problems so use it for your own risk...
Quote from: britom on July 26, 2013, 10:26:37 PM
Had multiple orgasms when the camera autobooted ml. Dual ISO module loaded without any error but shows Error 70 when i press the zoom button :/ Everything else that worked on the alpha2 is working. Plus now my camera autoboots ML!. Haven't tested movie restart yet.
This is awesome and i want to thank everybody who worked on this.
If someone needs and if i have some free time i can make a noob guide with detailed steps, with my weird english of course.
Pd: DAMN! WE NEED RAW VIDEO! :B
Just tested, auto restart does not work.
Quote from: britom on July 26, 2013, 10:26:37 PM
Had multiple orgasms when the camera autobooted ml. Dual ISO module loaded without any error but shows Error 70 when i press the zoom button :/ Everything else that worked on the alpha2 is working. Plus now my camera autoboots ML!. Haven't tested movie restart yet.
This is awesome and i want to thank everybody who worked on this.
If someone needs and if i have some free time i can make a noob guide with detailed steps, with my weird english of course.
Pd: DAMN! WE NEED RAW VIDEO! :B
PLEASE !!! Can you make a noob guide for the people that dont know what to do?
Thank you in advance my friend, thank you !!! :D
Quote from: Pelican on July 26, 2013, 10:53:13 PM
I released a new version of EOScard with some bugfix of unzipping ML files/folders.
I've also made Audionut's release available for the software, so EOScard can install 7D ML alpha2 with dual iso and file manager modules from now.
I still haven't experience any crash or error with this build but others have serious problems so use it for your own risk...
Were can i find this new version and the Audionut's realese for the software? So... with this i just need the EOScard software/program and then install direct to the 7D ?
Best regards and thanks for keeping the 7D alive =DD
Quote from: Pelican on July 26, 2013, 10:53:13 PM
I released a new version of EOScard with some bugfix of unzipping ML files/folders.
I've also made Audionut's release available for the software, so EOScard can install 7D ML alpha2 with dual iso and file manager modules from now.
I still haven't experience any crash or error with this build but others have serious problems so use it for your own risk...
Thank you! \o/
EDIT: Which .fir should we use with this? I used the alpha 2 .fir but it just loads regular alpha2 when firmware updating, wouldn't autoboot and has no modules on.
EDIT2: How do you use bsdiff with 1.2.3? I tried:
bsdiff oldfile newfile patchfileBut it produced nothing.
Quote from: feureau on July 27, 2013, 05:51:47 AMHow do you use bsdiff with 1.2.3? I tried:
bsdiff oldfile newfile patchfile
But it produced nothing.
You have to use bspatch instead. Is in the .zip.
Quote from: arrinkiiii on July 27, 2013, 02:06:32 AM
Were can i find this new version and the Audionut's realese for the software? So... with this i just need the EOScard software/program and then install direct to the 7D ?
Get the latest EOScard from it's site: http://pel.hu/eoscard
You don't need to get any ML stuff, just choose 7D alpha2 in EOScard and it will download and put it on your card.
But it install the autoboot version, so you have to prepare your camera first.
Quote from: Pelican on July 27, 2013, 09:26:00 AM
Get the latest EOScard from it's site: http://pel.hu/eoscard
You don't need to get any ML stuff, just choose 7D alpha2 in EOScard and it will download and put it on your card.
But it install the autoboot version, so you have to prepare your camera first.
THANK YOU, THANK YOU PELICAN :D
I have done this:
1-Format CF card in FAT32
2-Run EOSCard
3-In String menu i chose/check:
EOS_DEVELOP
BOOTDISK
SCRIPT
and then i click Save.
4-Wend i click Save, the EOSCard program writes to the CF card. In the root of the CF card are a folder with the name ML, a pdf call INSTALL, other pdf call UserGuide and a autoexec.bin file and nothing more.
-And now from here??
-since you say to "just choose 7D alpha2 in EOScard", but for me don't show that option (yet), so i did what i write before. Wend i click save and he writes to the CF card the EOSCard program open one more menu, the Magic Lantern menu. So, i unchecked the EOS_DEVELOP, BOOTDISK and SCRIPT and click Save, he delete the files in the CF. Then i just check again the the option EOS_DEVELOP, BOOTDISK and SCRIPT, chose Ports 7D 2.0.3 alpha2 in the Ports in progress(Magic Lantern menu, EOSCard program). Click Save and he writes the files in the CF card. I think that this is the files that i need to have in the card for the 7D, or not?
And now how i prepare the camera for the bootflag/autoboot? Do i need a .fir in the root of the CF card?
I have download the 7d000123.fir and i got 2 programs, the bspatch.exe and the bsdiff.exe what to do?
Sorry for all of this Pelican... but noobies/dumn must be like this... for sure that existe alot of people like me, that want to test the dual iso function and also have the boot enable but don't understand nothing about .fir, autoboot, bootflag, etc... thank you more one time for this :)
PS- Nice fotos that you got Pelican, like alot of the nudes 8) ... and the birds, good photos indeed. I see also in your travel map that you are missing a little big country... Portugal ::)
I need some help. Already enabled the dual iso module, but when i press the shutter it only shoots normal photos. Do i have to press some other button?
EDIT: Solved, the file_ma.mo file was missing from my modules folder :P
Quote from: britom on July 27, 2013, 06:39:35 PM
I need some help. Already enabled the dual iso module, but when i press the shutter it only shoots normal photos. Do i have to press some other button?
How did you make the 7D bootable? I use the Pelican EOSCard and already have the files in the CF card ready to gooo, just need enable autoboot or bootflag in the camera, can you help me?
I already have the old firmware (7d000123.fir) and the bspatch.exe and the bsdiff.exe. Wend i click, in any of the .exe programs, just appear, for a half of a second, one black window (command promp) and then it close without i can see what its there.
Quote from: tonybeccar on July 26, 2013, 12:57:54 AM
YESSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!! :D :D :D :D :D :D :D Will test it tomorrow as I don't have my camera with me!!! THANK YOUUUUUUUUUUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!! Hope everything works fine! And oh my, the new menu!! :)
Did you already have manage to make the 7D bootable?
@arrinkiiii
Hello, you made it? I also do not get ahead
:( :( :(
Quote from: tm8 on July 27, 2013, 07:16:36 PM
@arrinkiiii
Hello, you made it? I also do not get ahead
:( :( :(
Hello my friend, not yet. I just have the ML files in the CF card, using the EOSCard from Pelican. You can download from here
http://pel.hu/eoscard
Now im waiting for the firmware (.fir) file for put in the CF card for the 7D make autoboot, without the need to update the firmware every time that you want to use ML. This is because the ML files that the EOSCard put in your CF card just work with a autoboot/bootflag firmware in the 7D.
As soon i manage to do this i will post line by line for everyone that want to trie have the possibility... and lets keep the 7D ALIVE :D
Your camera may brick so DO IT AT YOUR OWN RISK!
You have to follow these steps in order to try the Audionut ML build and the dual iso module:
You'll Need This Files:
7D firmware v1.2.3 http://pel.hu/down/eos7d123.exe (Thanks to Pelican)
EOScard software http://pel.hu/down/EOScard.exe (Thanks to Pelican!)
EOS Utility 2.8.1 https://dl.dropboxusercontent.com/u/43043701/EOS.zip
patch.bsdiff https://ml-devel.googlegroups.com/attach/1608f00c71abc464/patch.bsdiff?part=6
bsdiff.exe and bspatch.exe http://download.pokorra.de/coding/bsdiff_win_exe.zip
Enabling Bootflag:
Unzip the bsdiff_win_exe.zip file in any folder. In my case i extracted to a folder in my desktop C:\Users\Miguel\Desktop\Magiclantern\
Double-Click eos7d123.exe and unzip it in the same folder. It should extract the 7d000123.fir file in the folder.
Place the downloaded file patch.bsdiff in the same folder
Open "cmd" by pressing WindowsKey+R and typing cmd
In the cmd screen change the directory by typing cd "folder where you put the files", in my case it was cd C:\Users\Miguel\Desktop\Magiclantern\
Type bspatch.exe 7d000123.fir firmware.fir patch.bsdiff and press enter
It should generate a file called firmware.fir that we are going to use with EOS Utility.
Copy the firmware.fir file to an empty CF card and put the card in your camera.
Extract EOS.zip in some other folder. In my case i extracted to C:\Users\Miguel\Desktop\Magiclantern\EOS Utility\
For me it worked well but is possible that this EOS Utility wont work because of some missing driver or registry key, so make sure you have installed any Canon EOS DIGITAL Solution Disk before.
Connect the camera to the pc via usb cable.
Go to the folder that you've extracted EOS.zip and double-click EOS Utility.exe *
Click Camera Settings/Remote Shooting option. Make sure your camera dial is in M mode and Liveview turn off.
In the middle of the window click the icon that looks like a cross and a tool, between the Lightning/Flash icon and the Star icon.
Click Firmware Ver. 2.0.3 at the bottom of the list.
Click OK and Select the firmware.fir file from the first folder. Click OK Again.
Wait until is done. **Be very Careful**
Installing ML:
Now put the CF card in your computer. Delete the firmware.fir and the other files.
Open EOScard.exe, click EOS_DEVELOP, BOOTDISK, right-click the ML icon, select Ports in progress and click 7d 2.0.3 alpha2.
Wait until is downloaded and click Save in the upper right corner.
DONE!
This build already contains the Dual Iso Module, It is not enabled by default and you can enable it for testing but some people are having issues with the module so do it at your own risk.
* If the Camera Settings/Remote Shooting option is greyed out follow this steps:
Go to Device Manager by pressing WindowsKey+R and typing devmgmt.msc
Expand the Portable Devices tree and Disable all of them except Canon EOS 7d by right-click - Disable.
Feel free to ask anything, i'll try to answer as soon as possible. Excuse my english :D
Oh my god thank you!!! It was driving me crazy.. have to go right now but i'll do it later.. I couldn't find anywhere the EOS Utilities (that version).
Again, THANK YOU!!!
THANK YOU BRITOM ;D
Im in this moment doing what you say. Let's wait and seeee :D
Thank you, thank you, thank you, thank you !!!
I really hope EOS utility works, otherwise i have to share the full Canon EOS DIGITAL Solution Disk (around 400mb) and it may take a white to upload... internet in ecuador sucks :/
Thanks for the clear instructions britom! :D
Finally got it working.
If anyone got that red light blinking every time you turn it on: Go to wrench > Warning for bad settings > turn them off.
Also, if anyone having problem when using the dual ISO module, don't go too high an ISO (800 max still the limit it seems?) or it'd only let you shoot once or twice and it'd stop shooting.
Quote from: britom on July 27, 2013, 08:41:34 PM
I really hope EOS utility works, otherwise i have to share the full Canon EOS DIGITAL Solution Disk (around 400mb) and it may take a white to upload... internet in ecuador sucks :/
Wend i finish to flash the firmware.fir in to the camera my camera, everything shout down, nothing work. I paste the EOScard files (ML software) to the card, that i have take from camera and connect the camera again and nothing !!! Believe me, i went totally crazy (cold and white face). Then i disconect and take battery, connect again... and voilá, ITS WORK !!! No more firmware boot !!!
Thank you BRITCOM u ROCK !!! And of course all of the ML team are wandeful !!!
Know im see how to work and enable with the dual iso. Will report some testes... but i think is better to post in the right place - Dual ISO - massive dynamic range improvement for 5D3 and 7D - no??
Quote from: feureau on July 27, 2013, 09:04:22 PM
Thanks for the clear instructions britom! :D
Finally got it working.
If anyone got that red light blinking every time you turn it on: Go to wrench > Warning for bad settings > turn them off.
Also, if anyone having problem when using the dual ISO module, don't go too high an ISO (800 max still the limit it seems?) or it'd only let you shoot once or twice and it'd stop shooting.
Me to ;D It's so nice the new GUI ;D
I also have that problem the red light is always blinking... Going to disable "warning for bad settings"
Do you know why we can't go more then ISO 800, do you know? I think that in 5D they go 1600 ISO, no?
I enable the dual iso module... and now? I can't see where i can chose my setting for the dual iso, do you know?
So... I enable de Dual ISO module in the M tab, then i go to the Expo tab (+/-) and click on set (button of the camera) for enable, then click on Q (camera button) to go to the sub-menu.
From there i change the iso to 800 and in the canon menu/camera i put 100.
Going take some photos now :D
.....
I take one photo after went to take another and nothing, the camera wont shoot. Disconnected camera and connect again (autoboot its wonderful) and is on again.
Take more one or two photos, change the iso in the ML menu from 800 to 640 and trie to shoot but nothing... Half-shutter press it focus confirm but then wend i press to take the picture its just don't take it. Disable camera and connect again and everything is good.
Any idea what is cause this?
I went to see the photos but only Jpeg's. In canon menu its raw+jpeg... going to check in the ML menu...
Quote from: arrinkiiii on July 27, 2013, 09:21:08 PM
I enable the dual iso module... and now? I can't see where i can chose my setting for the dual iso, do you know?
Go to Expo (second tab from the left), Dual ISO is third option from the bottom.
How do you process dualISO RAWs btw? Scale them by 50%? RTFM'd
Quote from: arrinkiiii on July 27, 2013, 09:57:27 PM
So... I enable de Dual ISO module in the M tab, then i go to the Expo tab (+/-) and click on set (button of the camera) for enable, then click on Q (camera button) to go to the sub-menu.
From there i change the iso to 800 and in the canon menu/camera i put 100.
Going take some photos now :D
.....
I take one photo after went to take another and nothing, the camera wont shoot. Disconnected camera and connect again (autoboot its wonderful) and is on again.
Take more one or two photos, change the iso in the ML menu from 800 to 640 and trie to shoot but nothing... Half-shutter press it focus confirm but then wend i press to take the picture its just don't take it. Disable camera and connect again and everything is good.
Any idea what is cause this?
I went to see the photos but only Jpeg's. In canon menu its raw+jpeg... going to check in the ML menu...
Yeah, it's also crashing randomly for me too. Haven't figured out what the consistent confounding variables though. It even crashes when at iso 400...
Quote from: feureau on July 27, 2013, 10:29:50 PM
Go to Expo (second tab from the left), Dual ISO is third option from the bottom.
Thanks Feureau. I find it thaks :D
I take one photo and after went to take another and nothing, the camera wont shoot. Disconnected camera and connected again (autoboot its wonderful) and is on again.
Take more one or two photos, change the iso in the ML menu from 800 to 640 and trie to shoot but nothing... With the half-shutter press its focus confirm but then wend i press to take the picture its just don't take it. Disable camera and connect again and everything is good.
Any idea what is cause this?
I went to see the photos but only Jpeg's. In canon menu its raw+jpeg... going to check in the ML menu... but nothing that i can change for take raw pic's in the ML Menu.
Now i take another photo and just show up the #70 error. Disconnected camera and connected again and everything is ok.
Any idea ???
Quote from: feureau on July 27, 2013, 10:36:06 PM
Yeah, it's also crashing randomly for me too. Haven't figured out what the consistent confounding variables though. It even crashes when at iso 400...
Thank you. Let's hope that a1ex can do something about this ::)
Also, when it crashes, it doesn't seem to write any error logs.
Not sure how I can help with debug...
But sometimes, the camera would let me shoot off 7-10 frames that would get unrecorded, then it err70s
Quote from: feureau on July 27, 2013, 10:51:06 PM
Also, when it crashes, it doesn't seem to write any error logs.
Not sure how I can help with debug...
But sometimes, the camera would let me shoot off 7-10 frames that would get unrecorded, then it err70s
Yes, is what happen to me. I take one photo and recorded good, raw+jpeg. Then i enable the dual iso i take a photo and just appear the error and didn't record anything.
Let's see if any dev can work on this.
I shoot raw only and it records some CR2 before it stops recording but still shoots, then err70.
Quote from: feureau on July 27, 2013, 11:18:50 PM
I shoot raw only and it records some CR2 before it stops recording but still shoots, then err70.
I shoot always raw+jpeg and in the begging, wend i install this new version with the modules, i able to shoot some pictures without the error... but the imagens in the card was only jpeg. After one crash or other i take a photo and show up this 70error.
Im going try only with raw and then again with raw+jpeg and report here.
The dual iso not suppose to record some kind of raw file (CR2)? That after you need the cr2hdr.exe program for post processing?
Intervalometer is working weird when i enable manual ramping. It always begins on 1/10th.
Quote from: britom on July 27, 2013, 11:56:28 PM
Intervalometer is working weird when i enable manual ramping. It always begins on 1/10th.
Are you on manual mode?
Forget, it just work in bulb.
Quote from: arrinkiiii on July 28, 2013, 12:02:26 AM
Are you on manual mode?
Forget, it just work in bulb.
I tryed in every mode. Same thing.
Quote from: britom on July 28, 2013, 02:03:42 AM
I tryed in every mode. Same thing.
Damn :-\ we need to get a good dev to work good in the 7D :-[
For those having issues with 7D crashing on DualISO: I think I found the problem.
After you installed your ML with eoscard, overwrite the respective files with this version: http://www.magiclantern.fm/forum/index.php?topic=3974.msg62012#msg62012
Autoexec.bin is in root. The other two files in \ML\MODULES
Interestingly, only the first file taken can be converted using cr2hdr. The rest fails with:
Input file : _MG_8342.CR2
Full size : 5360 x 3516
Active area : 5202 x 3465
Black borders : 158 left, 51 top
ISO pattern : dBBd GBRG
Interpolation : mean23-vsmooth3-contrast
Doesn't look like interlaced ISO
ISO blending didn't work
Thought the CR2 file would open just fine in photoshop. Is there a way to do the ISO blending in photoshop instead?
And just confirming the purple highlights: http://i.imgur.com/nH6SZXP.png
britom, thanks. I finally got it loaded.
arrinkiiii, thanks for solving the red light blinking issue.
Unable to boot twice, solved the issue easily by pulling the battery out, probably because I hot-pulled the CF card.
But the Qscale factor shrinks to -8 (used to be -16 plus GOP1), or it will stop recording in several seconds. Still unable to save that "Video Hack" option. But it is good enough for now.
Thanks again. G3gg0, Audionut, Pelican, britom, arrinkiiii, ...
@britom
Thank you, it rock's :D :D
Quote from: feureau on July 28, 2013, 07:50:59 AM
For those having issues with 7D crashing on DualISO: I think I found the problem.
After you installed your ML with eoscard, overwrite the respective files with this version: http://www.magiclantern.fm/forum/index.php?topic=3974.msg62012#msg62012
Autoexec.bin is in root. The other two files in \ML\MODULES
Interestingly, only the first file taken can be converted using cr2hdr. The rest fails with:
Input file : _MG_8342.CR2
Full size : 5360 x 3516
Active area : 5202 x 3465
Black borders : 158 left, 51 top
ISO pattern : dBBd GBRG
Interpolation : mean23-vsmooth3-contrast
Doesn't look like interlaced ISO
ISO blending didn't work
Thought the CR2 file would open just fine in photoshop. Is there a way to do the ISO blending in photoshop instead?
And just confirming the purple highlights: http://i.imgur.com/nH6SZXP.png
-I went to the link but the dropbox is empty. Can you or Audionut upload again the files?
-How do you use/convert the first file/photo with cr2hdr?
-Do you know how to set up the ML for ALL-I ? (With sound and with out sound)
Quote from: mucher on July 28, 2013, 08:44:24 AM
britom, thanks. I finally got it loaded.
arrinkiiii, thanks for solving the red light blinking issue.
Unable to boot twice, solved the issue easily by pulling the battery out, probably because I hot-pulled the CF card.
But the Qscale factor shrinks to -8 (used to be -16 plus GOP1), or it will stop recording in several seconds. Still unable to save that "Video Hack" option. But it is good enough for now.
Thanks again. G3gg0, Audionut, Pelican, britom, arrinkiiii, ...
Thanks mucher but was Feureau that give the hint for the red blicking. I have the same problem, that tell/warning me that im not working in the Av mode. Good to know that now is solve...but wod like to know why its react in that way...
Some times, most of the times, using dual iso camera crash... need to take battery out.
Let's keep the 7D ALIVE... !
Quote from: arrinkiiii on July 28, 2013, 12:33:25 PM
-I went to the link but the dropbox is empty. Can you or Audionut upload again the files?
-How do you use/convert the first file/photo with cr2hdr?
-Do you know how to set up the ML for ALL-I ? (With sound and with out sound)
Audionut's latest: http://www.mediafire.com/?9kme624ql66qkjq (the one from that dropbox link)
to use cr2hdr:
use command prompt > go to folder with cr2hdr
run:
cr2hdr IMG_1234.cr2And it should spit out a .dng files
With audionut's latest build, the highlights are all magenta though. But it doesn't crash when you take a lot of dual iso pics.
to set up ML with ALL-I
go to Movie tab (fourth tab from the left) > video hacks > set GOP size to 1
If you want to record audio with that, set the flush rate according to your video framerate. (i.e. if shooting 24fps, flush at 24) for some reason the flush rate is capped to 50. So if you're shooting 60fps, you can't use this to shoot All-I and flush at 60. Make a note that this needs a fast card. If your video keeps dropping, you need faster card. Or lower the bitrate.
What can i say?! Thank you Feureau, much appreciated. Going to try out this one, lets see what happen :D
You're welcome. Report back with pics! :D
Now, before i change the files i was able to take 2 pictures with no problem, with the old files. I will change now the files and take a few photos to compare and then use the cr2hdr.
::)
I use now the latest build from Audionut and everything is ok, but i just take 2 or 4 pictures. I will do more photos for see if it's stable.
-Wend i use the cr2hdr its prompt in the screen the next message:
Input file: IMG9958.cr2
Full size: 5360 x 3516
Active area: 5202 x 3465
Doesn't look like interlaced ISO
Any one knows why? I make a zoom in the photo and i can see the lines, so i assume everything is good with the picture, that is a interlaced iso, no?
Until now i don't see no magenta in the highlight, but i also have careful to not over-expose the photo. By the way, i don't yet manage to expose the photo good. I put iso 100 in canon menu and 1600 iso in dual iso menu. In the exposer compesation bar (in the camera) i need to take -4 stops for the sky don't(//) over-expose.
the cr2 image are here https://www.wetransfer.com/downloads/edbab4227c938bdb349772d7466b07b020130728140510/0d9855a665c27e776d96f9cf79385f6420130728140511/cfc7b6
HI,from where i can download cr2hdr.exe
With the new build, confirmation of pink/magenta in the highlights. Camera crash but i use iso 6400 in ML and iso100 in canon menu.
I have been able to use cr2hdr with this photos.
I will put the files of the first Audionut version for see what happen.
Quote from: szigiszmund on July 28, 2013, 05:06:07 PM
HI,from where i can download cr2hdr.exe
http://www.magiclantern.fm/forum/index.php?topic=7139.0
Thankyou.(Obrigado)
Quote from: szigiszmund on July 28, 2013, 05:36:39 PM
Thankyou.(Obrigado)
...de nada. (it's nothing) :D
..................................................Camera crash again with 70error. With 800 and 400 iso. Beside the pink/magenta problem in cr2hdr, its still crash with the 70error. Last build from Audionut.
Good evening from France.
Thank you for the 7d ML developpers. :-* :-* :-* :-* :-*
I have almost understood how I might create an autobootable ML for my 7d.......
BUT i'm running a Mac :D .......... which is completely and totally indifferent :o, apathic ???, unconcerned ::), uninterested :-[, blind :-X and insensible :'( to any .exe program.
Any chance to get a ready to download on the CF ML file in the near future ? ::)
Regards.
Please keep 7d alive. :)
Thierry
Quote from: ThLDQ on July 28, 2013, 09:42:44 PM
Good evening from France.
Thank you for the 7d ML developpers. :-* :-* :-* :-* :-*
I have almost understood how I might create an autobootable ML for my 7d.......
BUT i'm running a Mac :D .......... which is completely and totally indifferent :o, apathic ???, unconcerned ::), uninterested :-[, blind :-X and insensible :'( to any .exe program.
Any chance to get a ready to download on the CF ML file in the near future ? ::)
Regards.
Please keep 7d alive. :)
Thierry
Hello and greetings from Portugal.
I dont know how to do it in Mac but i can send you the files that you need to run the Magic Lantern with the dual iso... and the new GUI. Just tell me if you want.
Quote from: ThLDQ on July 28, 2013, 09:42:44 PM
Any chance to get a ready to download on the CF ML file in the near future ? ::)
EOScard use this link at the moment: http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip
I take my hat off!!!! THANK YOU!!!! ML auto-booting and new gui!!! Cant believe it guys!!! You are geniouses!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Quote from: ThLDQ on July 28, 2013, 09:42:44 PM
Good evening from France.
Thank you for the 7d ML developpers. :-* :-* :-* :-* :-*
I have almost understood how I might create an autobootable ML for my 7d.......
BUT i'm running a Mac :D .......... which is completely and totally indifferent :o, apathic ???, unconcerned ::), uninterested :-[, blind :-X and insensible :'( to any .exe program.
Any chance to get a ready to download on the CF ML file in the near future ? ::)
Regards.
Please keep 7d alive. :)
Thierry
Hi any news for Mac users how to install this version?
The only thing you actually need on to wait for the mac is EOSCard.
I'd try wine or just run windows on VM.
Hey guys, kind of new to ML so sorry if its a newbish question, is there like, a twitter feed or something i can get plugged into for development on the 7D? Half the sites i check say the 7D development is dead because no funding or they bricked the cameras or whatever, yet i come on the forums and every now and then i see life in a 7D forum...
I just want to make sure I keep up to date on the developments yet a lot of this stuff, compiling etc. is way over my head. Can someone please help point me in the right direction?
Is Alpha 2 the latest "release"? Does it have the newest 'developed' features or is it a watered down, "safe" version? Is there a pre-alpha that has the partially working features on it?
How do I go about getting the most recent stuff for my 7D?
@Britom,
Thank you for that guide. My 7D now autoboots. :)
Quote from: britom on July 27, 2013, 07:52:03 PM
Go to the folder that you've extracted EOS.zip and double-click EOS Utility.exe *
Click Camera Settings/Remote Shooting option. Make sure your camera dial is in M mode and Liveview turn off.
In the middle of the window click the icon that looks like a cross and a tool, between the Lightning/Flash icon and the Star icon.
Click Firmware Ver. 2.0.3 at the bottom of the list.
Click OK and Select the firmware.fir file from the first folder. Click OK Again.
Wait until is done. **Be very Careful**
Well i may have just bricked my camera... :(
Followed every step. Got to this point, opened EOS utility, navigated to the Cross / wrench icon, clicked firmware update, clicked firmware.fir, it asked if i wanted to update, i clicked OK, and nothing happened. My camera remained dark for several minutes, the EOS utility said press select to start but nothing happened on the camera... eventually I unplugged my camera and removed the battery (no button response, no lights, nothing) and now all that happens is the low battery icon flashes when i turn on camera and nothing.
Is there any hope or should I consider it a complete loss?
**EDIT**
Quick search for "Brick" and found another user with the same problem on a 5DIII or whatever, if he removes the CF card the camera booted so i figured wth i'll give er a try. SUCCESS! camera boots without the CF card. Now what do I need to do to fix this? That forum thread didnt go past that suggestion so now im stuck but mildly hopefull.
**Edit again**
Found a card that i had NOT changed the boot flags on (No magiclantern business), formatted it as NTFS, insterted in camera, camera started (yay!), formatted the card, now all seems to be working but no magiclantern.
well at least my camera isn't bricked, so thats some good news. nearly had a heart attack XD
I think my problem is I am running 2.0.3 and not 1.2.3, when the eos utility tried to "update" it got confused?
How can i made the firmware.fir file with 2.0.3 instead of 1.2.3 so the update actually works?
Remove card and *both* batteries and let it rest for about half an hour. Then try again without card inserted.
Ciao, Walter
After a brief heart attack, got my camera starting up again.
Quote from: britom on July 27, 2013, 07:52:03 PM
Click OK and Select the firmware.fir file from the first folder. Click OK Again.
Wait until is done. **Be very Careful**
I get to this point, everything goes perfectly and as explained. Then the EOS utility says to start the update press the set button on the camera. well on the camera it says "Firmware update program. Update file cannot be found. PLease check the memory card and reload the battery and try again"
Firmware.firm is in the root of the SD card, freshly formatted by the camera.
It seems the camera does not want to "update" to an older version, am I doing something wrong?
Additionally, I think the EOScard.exe did not download the files correctly, what files is it supposed to put on the CF card? It places no .fir files, which to me seems odd. How can I "reset" the EOScard application so it re-downloads all applicable files?
@ Arrinkiiii
Thanks. I guess Pelican gave me the link to the autoexecutable program, so I should not need yours.
@ Pelican
Thanks. i just download the files on the CF and i will work ?
Thierry
Quote from: britom on July 27, 2013, 07:52:03 PM
Your camera may brick so DO IT AT YOUR OWN RISK!
You have to follow these steps in order to try the Audionut ML build and the dual iso module:
You'll Need This Files:
7D firmware v1.2.3 http://pel.hu/down/eos7d123.exe (Thanks to Pelican)
EOScard software http://pel.hu/down/EOScard.exe (Thanks to Pelican!)
EOS Utility 2.8.1 https://dl.dropboxusercontent.com/u/43043701/EOS.zip
patch.bsdiff https://ml-devel.googlegroups.com/attach/1608f00c71abc464/patch.bsdiff?part=6
bsdiff.exe and bspatch.exe http://download.pokorra.de/coding/bsdiff_win_exe.zip
Enabling Bootflag:
Unzip the bsdiff_win_exe.zip file in any folder. In my case i extracted to a folder in my desktop C:\Users\Miguel\Desktop\Magiclantern\
Double-Click eos7d123.exe and unzip it in the same folder. It should extract the 7d000123.fir file in the folder.
Place the downloaded file patch.bsdiff in the same folder
Open "cmd" by pressing WindowsKey+R and typing cmd
In the cmd screen change the directory by typing cd "folder where you put the files", in my case it was cd C:\Users\Miguel\Desktop\Magiclantern\
Type bspatch.exe 7d000123.fir firmware.fir patch.bsdiff and press enter
It should generate a file called firmware.fir that we are going to use with EOS Utility.
Copy the firmware.fir file to an empty CF card and put the card in your camera.
Extract EOS.zip in some other folder. In my case i extracted to C:\Users\Miguel\Desktop\Magiclantern\EOS Utility\
For me it worked well but is possible that this EOS Utility wont work because of some missing driver or registry key, so make sure you have installed any Canon EOS DIGITAL Solution Disk before.
Connect the camera to the pc via usb cable.
Go to the folder that you've extracted EOS.zip and double-click EOS Utility.exe *
Click Camera Settings/Remote Shooting option. Make sure your camera dial is in M mode and Liveview turn off.
In the middle of the window click the icon that looks like a cross and a tool, between the Lightning/Flash icon and the Star icon.
Click Firmware Ver. 2.0.3 at the bottom of the list.
Click OK and Select the firmware.fir file from the first folder. Click OK Again.
Wait until is done. **Be very Careful**
Installing ML:
Now put the CF card in your computer. Delete the firmware.fir and the other files.
Open EOScard.exe, click EOS_DEVELOP, BOOTDISK, right-click the ML icon, select Ports in progress and click 7d 2.0.3 alpha2.
Wait until is downloaded and click Save in the upper right corner.
DONE!
This build already contains the Dual Iso Module, It is not enabled by default and you can enable it for testing but some people are having issues with the module so do it at your own risk.
* If the Camera Settings/Remote Shooting option is greyed out follow this steps:
Go to Device Manager by pressing WindowsKey+R and typing devmgmt.msc
Expand the Portable Devices tree and Disable all of them except Canon EOS 7d by right-click - Disable.
Feel free to ask anything, i'll try to answer as soon as possible. Excuse my english :D
Quote from: Pileot on July 29, 2013, 11:26:28 AM
Firmware.firm is in the root of the SD card, freshly formatted by the camera.
Are you sure you have 7D? ;)
Quote from: Pileot on July 29, 2013, 11:26:28 AM
After a brief heart attack, got my camera starting up again.
I get to this point, everything goes perfectly and as explained. Then the EOS utility says to start the update press the set button on the camera. well on the camera it says "Firmware update program. Update file cannot be found. PLease check the memory card and reload the battery and try again"
Firmware.firm is in the root of the SD card, freshly formatted by the camera.
It seems the camera does not want to "update" to an older version, am I doing something wrong?
Additionally, I think the EOScard.exe did not download the files correctly, what files is it supposed to put on the CF card? It places no .fir files, which to me seems odd. How can I "reset" the EOScard application so it re-downloads all applicable files?
I Almost had the same situation you described.
Followed Britom's Step-by-step in post #756 and I could not get the 7D to autoboot.
It turned out I tried this on a CF card I already used for ML.
I formatted the CF in the camera and tried Britoms's steps again.
At the end I manualy copied the contents of Pelican's magiclantern-7D.203.Alpha2.zip onto the CF card.
See also Post #791 for the ZIP file.
Now my 7D autoboots.
I cannot recall the precise steps but these two postings helped me.
@Britom: "Right-click the ML icon" was the eye opener for me! (RTFM?)
First, arrinkiiii since i linked to the instructions like 5 times i didnt need another link but thanks anways.
Quote from: Pelican
link=topic=3974.msg62551#msg62551 date=1375097947
Are you sure you have 7D? ;)
CF to SD adapter, perhaps thats the problem? Dont see how...
**edit**
Thought it was too stupid to cause the problem so i had to test it.
**edit 2**
Derp. I feel like a noob.
Downloaded the ML zip from this post:
Quote from: Pelican on July 28, 2013, 10:42:32 PM
EOScard use this link at the moment: http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip
put it on my CF card instead of my CF/SD adapter and guess what, worked no problem.
How dumb do you think I feel, fighting with this for the last 4 hours.... Its time for sleep :)
Thanks for help guys! Now we know this doesnt work too well with adapters :)
Quote from: ThLDQ on July 29, 2013, 01:15:20 PM
@ Arrinkiiii
Thanks. I guess Pelican gave me the link to the autoexecutable program, so I should not need yours.
@ Pelican
Thanks. i just download the files on the CF and i will work ?
Thierry
Yes, everything in that zip have the files for ML work. But that files in the ZIP that you put in the CF card are prepare for work with a camera that are autoboot. So, you need to prepare your camera to autoboot. You need bootflag your camera =)
@ Arrinkiiii
Damn, bootflag the camera ........ that's the problem.
Thierry
Quote from: ThLDQ on July 29, 2013, 03:04:12 PM
@ Arrinkiiii
Damn, bootflag the camera ........ that's the problem.
Thierry
Yes indeed but i must say... it was :)
You can do your on file (firmware.fir) with the instructions that britom says in the post. But you got mac... if you want, like said before, i can send you de file (firmware.fir). Then with this file you just need to flash you camera, delete and put the ML 203 files in the CF card and you are ready to goo :D
Hi. Thanks for your work. But iv got errors when try to shhot in dual ISO mode...Any suggestion?
Start off by not assuming we are mind readers!
Please Arrinkiiii !!!!!!!!!
send me your file
Thierry
Quote from: ThLDQ on July 29, 2013, 06:26:51 PM
Please Arrinkiiii !!!!!!!!!
send me your file
Thierry
MAC and PC always problem =DD
After taking 3-4 photos its usually hangs up with this message: "Err 70 Shooting is not possible due to an error..." When I trying to turn it off, its start to show this message: "Recording... Remaining images:1" Only battery extraction helps. After that, on a memory card Ive got only 1 image - first of that was taken.
Log:
ASSERT: 0
at DianaUSBConfig.c:192, task PtpDps
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jul26.7D203
Mercurial changeset : ac3f8247a551+ (unified)
Built on 2013-07-26 14:58:54 by magiclantern@magiclantern-VirtualBox.
Free Memory : 357K + 2536K
Quote from: mityazabuben on July 29, 2013, 09:17:12 PM
After taking 3-4 photos its usually hangs up with this message: "Err 70 Shooting is not possible due to an error..." When I trying to turn it off, its start to show this message: "Recording... Remaining images:1" Only battery extraction helps. After that, on a memory card Ive got only 1 image - first of that was taken.
Log:
ASSERT: 0
at DianaUSBConfig.c:192, task PtpDps
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jul26.7D203
Mercurial changeset : ac3f8247a551+ (unified)
Built on 2013-07-26 14:58:54 by magiclantern@magiclantern-VirtualBox.
Free Memory : 357K + 2536K
Yes, its happen with all of us! You need to take the battery.
Let see if any dev can solve this.
EOScard put this version to the card:
Magic Lantern v2.3.NEXT.2013Jul25.7D203
Mercurial changeset: ac3f8247a551+ (unified)
Built on 2013-07-25 09:50:21 by magiclantern@magiclantern-VirtualBox
The modules folder:
7D_203.sym 41881 bytes
dual_iso.mo 7660 bytes
file_man.mo 13700 bytes
I've just shot 70+ dual_iso shot without freezing or Err 70
I could take 21 images (RAW+JPG) in a row with 8 fps until the buffer filled up.
Edit:
Continued the test and finally got an Err70 :-(
@Pelican
Did u use only 100/800 iso or u went above the 800? Were u put your lower iso, in the canon settings or in ML Dual iso settings? ...and what card u r using?
First time poster,
Thanks everyone for working on the dual ISO for the 7D. When I can get it to work, it is awesome!
The previous build was working for a few photos then I would get an error 70, and the latest (http://www.magiclantern.fm/forum/index.php?topic=3974.msg62367#msg62367 (http://www.magiclantern.fm/forum/index.php?topic=3974.msg62367#msg62367)) is giving me the pink highlights and after a few photos, the red light will stay on. If I try to continue to shoot, I'll get an error 80, but no error log. I've tried swapping the ISO in the camera and ML (which was necessary in the build currently available in EOSCard (ISO 800 in camera and 100 for the dual ISO)).
Back to the build in EOS Card and using ISO 800 in camera and ISO 100 in ML for dual ISO. Solid red light random 1-9 shots and have to restart.
Quote from: arrinkiiii on July 29, 2013, 10:53:21 PM
Did u use only 100/800 iso or u went above the 800? Were u put your lower iso, in the canon settings or in ML Dual iso settings? ...and what card u r using?
100/1600,
last time I used the default setting (low ISO in Canon),
Transcend 400x 32GB
Quote from: Pelican on July 29, 2013, 10:23:36 PM
EOScard put this version to the card:
Magic Lantern v2.3.NEXT.2013Jul25.7D203
Mercurial changeset: ac3f8247a551+ (unified)
Built on 2013-07-25 09:50:21 by magiclantern@magiclantern-VirtualBox
The modules folder:
7D_203.sym 41881 bytes
dual_iso.mo 7660 bytes
file_man.mo 13700 bytes
I've just shot 70+ dual_iso shot without freezing or Err 70
I could take 21 file in a row with 8 fps until the buffer filled up.
Edit:
Continued the test and finally got an Err70 :-(
Pelican!
It's dangerous out there. Here. Take this: http://www.mediafire.com/?9kme624ql66qkjq
That's audionut's latest build. Timestamped 2013-07-26.
It doesn't err70 anymore.
Quote from: feureau on July 30, 2013, 09:22:37 AM
Take this: http://www.mediafire.com/?9kme624ql66qkjq
That's audionut's latest build. Timestamped 2013-07-26.
is this version work without the 7d autoboot enabled ?
if not, i prefer wait for a good version, to be sure to not break my 7d hu hu...
Quote from: Pelican on July 30, 2013, 03:22:05 AM
100/1600,
last time I used the default setting (low ISO in Canon),
Transcend 400x 32GB
Did you notice any difference in putting the lowest iso in canon or in ML?
Quote from: feureau on July 30, 2013, 09:22:37 AM
Pelican!
That's audionut's latest build. Timestamped 2013-07-26.
It doesn't err70 anymore.
Its also give me the 70error with the latest build from audionut or red light stay on forever, need to take battery.
Quote from: obiyan19 on July 30, 2013, 01:15:21 PM
is this version work without the 7d autoboot enabled ?
if not, i prefer wait for a good version, to be sure to not break my 7d hu hu...
No. You need to wait...maybe forever
Quote from: arrinkiiii on July 30, 2013, 02:41:27 PM
Its also give me the 70error with the latest build from audionut or red light stay on forever, need to take battery.
It doesn't err70 on mine. Took hundreds of DualISO pics with it.
Red light needs to be manually disabled in the ML menu.
Quote from: feureau on July 30, 2013, 03:23:07 PM
It doesn't err70 on mine. Took hundreds of DualISO pics with it.
Red light needs to be manually disabled in the ML menu.
The red light its not the warning light that you disable in the menu (warning for bad settings), that i already disable... the red light its like the camera stay forever recording to the card but nothing happen and the camera don't do nothing, its just block the camera... and then i need to take out the battery.
Anyways, i will put again the files from the last build from audionut and try again :D
SanDisk Extreme 60MB/s
8GB
Good news, no more pink/mangeta highlights
Quote from: a1ex on July 30, 2013, 05:35:34 PM
Updated the converters (download from first post):
cr2hdr:
- fix memory leak, tested with 100 GB of pictures
- white level autodetection (should fix pink highlights)
- exiftool fix from jpaana, not tested but looks OK
raw2dng:
- fix memory leak, not tested (should be OK with large clips)
I did not address the black level issues yet.
If you are having issues with image quality, please upload the raw files (*.CR2 or *.RAW).
It's working for me :D
Yeh a1ex updated cr2hdr i think, so people should redownload that from that first post (of the dual iso thread).
Btw, is there an auto-ETTR module for the 7D? I can't seem to find it.
Thanks
Quote from: arrinkiiii on July 30, 2013, 04:00:44 PM
The red light its not the warning light that you disable in the menu (warning for bad settings), that i already disable... the red light its like the camera stay forever recording to the card but nothing happen and the camera don't do nothing, its just block the camera... and then i need to take out the battery.
Anyways, i will put again the files from the last build from audionut and try again :D
SanDisk Extreme 60MB/s
8GB
I think I reproduced that.
Try not going as high up to ISO 12800.
Been shooting at max 6400 and it's doing great.
Shooting with 160-1600 - still err70 after a couple of shots...
Quote from: feureau on July 31, 2013, 11:46:34 AM
I think I reproduced that.
Try not going as high up to ISO 12800.
Been shooting at max 6400 and it's doing great.
Thank you feureau i will try today :D
Quote from: mityazabuben on July 31, 2013, 11:54:29 AM
Shooting with 160-1600 - still err70 after a couple of shots...
Make sure you're using audionut's latest (go to the help tab, look at the version at the bottom. It should be dated Jul26.
Always shoot round ISO. (100, 200, 400 etc)
Quote from: arrinkiiii on July 27, 2013, 09:21:08 PM
Wend i finish to flash the firmware.fir in to the camera my camera, everything shout down, nothing work. I paste the EOScard files (ML software) to the card, that i have take from camera and connect the camera again and nothing !!! Believe me, i went totally crazy (cold and white face). Then i disconect and take battery, connect again... and voilá, ITS WORK !!! No more firmware boot !!!
Hi,
have you had the same problem as Arrinkiiii when you upgraded your 7d with the "autobootable firmware" ?
I'm a little bit scared to explode my 7d :o
Thierry
Firmware date is 26 July, ISO - 100/1600, manual lens - Err70 after +-10 shots.
The same
Firmware date is 26 July, ISO - 100/1600, 17-85 Canon lens - Err70 after +-10 shots.
I've put the file date info to the file manager.
The brave ones can download here: http://www.magiclantern.fm/forum/index.php?topic=5522.msg62738#msg62738
Quote from: Pelican on August 01, 2013, 12:07:38 AM
I've put the file date info to the file manager.
The brave ones can download here: http://www.magiclantern.fm/forum/index.php?topic=5522.msg62738#msg62738
Sorry Pelican, what the file_man.mo have to do with the 70error? ...and what i should do?
Thanks for all your help and sorry for my lack of understanding on this subject ???
Quote from: a1ex on June 16, 2013, 08:15:28 PM
Rename support is very weak in DryOS (on some cameras the function is there, but it just doesn't work). So, copying is the only portable way.
You can create folders from Canon menu; ML can't help you with that (unless you are OK with ERR70 messages).
Quote from: arrinkiiii on August 01, 2013, 01:33:02 AM
Sorry Pelican, what the file_man.mo have to do with the 70error? ...and what i should do?
Thanks for all your help and sorry for my lack of understanding on this subject ???
Nothing.
Thats really Great news for 7d, i,m hungry to use the new interface in the latest build, but without the
autoboot, can i use the new build without autoboot ? Isn't that than cause frezze camera?
Is the auto micro adjust implented?
Quote from: Jansten on August 01, 2013, 03:31:20 AM
Thats really Great news for 7d, i,m hungry to use the new interface in the latest build, but without the
autoboot, can i use the new build without autoboot ? Isn't that than cause frezze camera?
Is the auto micro adjust implented?
I think the errors are only due to the Dual Iso function.. myself haven't had a chance to test it fully.. but as I'm not using that I believe I'm not going to have errors...
The only thing that crashes it is just the DualISO. If you don't turn that on, or don't load that module at all, the ML itself is as stable as running the alpha 2.
Speaking of err70 crashes. I've been trying out some things. It seems it doesn't tend to crash when it's at wide open aperture with reasonable shutter speed. (1/4th or faster) but when I go up to f/8 or above or shutter speed below 1/4th, it tends to err70 after a few shots.
Can anyone confirm this?
Disregard
Dual ISO 7D fixes from Alex (commit 7e8701a (https://bitbucket.org/hudson/magic-lantern/commits/7e8701aa097ae3b6b54eb087300fa7e8b3e12177)): http://pel.hu/ML/dual_iso.mo
That's a lot cleaner then what I was doing to the code (surprise, surprise)!
Here is a new build (https://www.dropbox.com/sh/6k0bh72mbb52fsi/k2Nx-hV2Aa)
Quote from: Pelican on August 01, 2013, 11:48:28 AM
Dual ISO 7D fixes from Alex (commit 7e8701a (https://bitbucket.org/hudson/magic-lantern/commits/7e8701aa097ae3b6b54eb087300fa7e8b3e12177)): http://pel.hu/ML/dual_iso.mo
Quote from: Audionut on August 01, 2013, 12:02:33 PM
That's a lot cleaner then what I was doing to the code (surprise, surprise)!
Here is a new build (https://www.dropbox.com/sh/6k0bh72mbb52fsi/k2Nx-hV2Aa)
You guys ROCK BIG TIME !!! :D
Let's go 7D fellows, it's time to try this one. No more 70ERROR.
Thats great! Sorry for my stupid question, but how do I replace the old build (26 July) with new? Just copy over in the cf card?
Quote from: Audionut on August 01, 2013, 12:02:33 PM
That's a lot cleaner then what I was doing to the code (surprise, surprise)!
Here is a new build (https://www.dropbox.com/sh/6k0bh72mbb52fsi/k2Nx-hV2Aa)
Noob question...just download those 5 Files and replace them on the lastest ML-7D 2.0.3 (Alpha 2) CF-Card???
I'm Just into ML....Made one Dual-ISO and put it through CR2HDR. Very impressed!!
So it's a lot of new things in a few Hours.
Quote from: pit3k on August 01, 2013, 12:20:55 PM
Thats great! Sorry for my stupid question, but how do I replace the old build (26 July) with new? Just copy over in the cf card?
Yes, all files :)
@Audionut
Wend i enable the pick_view module its just fail to load.
tcc: error: undefined symbol "raw_info"
tcc: error: undefined symbol "raw_set_geometry"
[E] failed to link modules
The rest i think its working good. Im going out to try the new build :D
Quote from: Audionut on August 01, 2013, 12:02:33 PM
That's a lot cleaner then what I was doing to the code (surprise, surprise)!
Here is a new build (https://www.dropbox.com/sh/6k0bh72mbb52fsi/k2Nx-hV2Aa)
I've refreshed the files in the zip here (http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip) so EOScard can download this version from now.
Also updated EOScard itself (bugfix).
The file_man.mo is the newest with the date info.
Quote from: Pelican on August 01, 2013, 12:56:14 PM
I've refreshed the files in the zip here (http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip) so EOScard can download this version from now.
Also updated EOScard itself (bugfix).
The file_man.mo is the newest with the date info.
What about pick_view module?
Quote from: arrinkiiii on August 01, 2013, 12:44:18 PM
@Audionut
Wend i enable the pick_view module its just fail to load.
tcc: error: undefined symbol "raw_info"
tcc: error: undefined symbol "raw_set_geometry"
[E] failed to link modules
The rest i think its working good. Im going out to try the new build :D
@Pelican Thanks for the update~! :D Where does EOSCard store the magiclantern-7D.203.Alpha2.zip file? I think I need to delete the old one first because it thinks the file is already downloaded and won't download the new download.
@Audionut Thanks for the update! This is awesome! :D
Quote from: pit3k on August 01, 2013, 01:06:45 PM
What about pick_view module?
The pic_view (picture viewer) module cannot load so I didn't include that.
Quote from: feureau on August 01, 2013, 01:24:27 PM
@Pelican Thanks for the update~! :D Where does EOSCard store the magiclantern-7D.203.Alpha2.zip file? I think I need to delete the old one first because it thinks the file is already downloaded and won't download the new download.
i Think here:
C:\Users\Hypermobile\AppData\Local\Temp\EOScard001
It works like a charm. I took almost 50 photos and no error.
Quote from: feureau on August 01, 2013, 01:24:27 PM
@Pelican Thanks for the update~! :D Where does EOSCard store the magiclantern-7D.203.Alpha2.zip file? I think I need to delete the old one first because it thinks the file is already downloaded and won't download the new download.
@Audionut Thanks for the update! This is awesome! :D
Thanks for the bug report I will repair EOScard soon.
It puts to the default temp folder of the user as hypermobile figured out...
Quote from: Pelican on August 01, 2013, 01:30:43 PM
Thanks for the bug report I will repair EOScard soon.
It puts to the default temp folder of the user as hypermobile figured out...
You're welcome! And thanks for this!
Btw, is there an auto-ETTR module for 7D?
EOScard 1.36 (http://pel.hu/down/EOScard.exe) can check the date of the zip files so it downloads again if necessary.
Please test it and report any errors.
Quote from: feureau on August 01, 2013, 02:02:56 PM
Btw, is there an auto-ETTR module for 7D?
It's not working.
Quick test for sharpness: 100% middle crop of 7d with 17-55/2.8. 17mm @ 2.8
No dual iso (iso 100):
(http://img713.imageshack.us/img713/5523/w7ij.jpg) (http://imageshack.us/photo/my-images/713/w7ij.jpg/)
Uploaded with ImageShack.us (http://imageshack.us)
Dual iso 100/1600:
(http://img843.imageshack.us/img843/3016/ennf.jpg) (http://imageshack.us/photo/my-images/843/ennf.jpg/)
Uploaded with ImageShack.us (http://imageshack.us)
Full ress cr2 and raw files here: https://www.dropbox.com/sh/tw3lo4kblurabkn/zjZGCfABR5 (https://www.dropbox.com/sh/tw3lo4kblurabkn/zjZGCfABR5)
Quote from: Pelican on August 01, 2013, 02:08:42 PM
EOScard 1.36 (http://pel.hu/down/EOScard.exe) can check the date of the zip files so it downloads again if necessary.
Please test it and report any errors.
It's not working.
I see.
What's pic_view.mo btw? It would cause errors on the module and wouldn't load with dual ISO and file manager if I load them all together
I think I've got raw histogram and zebras working in photo mode, sort of. Zebras say almost the entire picture is overexposed, most probably a wrong offset. Quick and dirty patch:
diff -r af0907c14c7d platform/7D.203/Makefile.setup.default
--- a/platform/7D.203/Makefile.setup.default Thu Aug 01 14:44:07 2013 +0300
+++ b/platform/7D.203/Makefile.setup.default Thu Aug 01 15:32:27 2013 +0300
@@ -12,5 +12,6 @@
video_hacks.o \
misc.o \
ptpbuf.o \
+ raw.o \
afma.o
diff -r af0907c14c7d platform/7D.203/internals.h
--- a/platform/7D.203/internals.h Thu Aug 01 14:44:07 2013 +0300
+++ b/platform/7D.203/internals.h Thu Aug 01 15:32:27 2013 +0300
@@ -102,3 +102,5 @@
/** We can record movies in regular photo modes - M, P, Tv, Av... */
#define CONFIG_NO_DEDICATED_MOVIE_MODE
+
+#define CONFIG_RAW_PHOTO
diff -r af0907c14c7d src/raw.c
--- a/src/raw.c Thu Aug 01 14:44:07 2013 +0300
+++ b/src/raw.c Thu Aug 01 15:32:27 2013 +0300
@@ -58,6 +58,8 @@
#define RAW_LV_EDMAC 0xC0F26208
#endif
+#define RAW_LV_EDMAC 0xC0F26208
+
/**
* Photo-mode raw buffer address
* On old cameras, it can be intercepted from SDSf3 state object, right after sdsMem1toRAWcompress.
@@ -67,7 +69,7 @@
* and http://a1ex.bitbucket.org/ML/states/ for state diagrams.
*/
-#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_500D) || defined(CONFIG_600D) || (defined(CONFIG_DIGIC_V) && !defined(CONFIG_FULLFRAME))
+#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_500D) || defined(CONFIG_600D) || (defined(CONFIG_DIGIC_V) && !defined(CONFIG_FULLFRAME)) || defined(CONFIG_7D)
#define RAW_PHOTO_EDMAC 0xc0f04A08
#endif
@@ -140,7 +142,7 @@
* It will also work with the values from some other camera, but colors may be a little off.
**/
-#ifdef CONFIG_5D2
+#ifdef CONFIG_7D
//~ { "Canon EOS 5D Mark II", 0, 0x3cf0,
//~ { 4716,603,-830,-7798,15474,2480,-1496,1937,6651 } },
#define CAM_COLORMATRIX1 \
@@ -242,7 +244,7 @@
* This is only used in photo LiveView, where we can't compute it
*/
-#ifdef CONFIG_5D3
+#ifdef CONFIG_7D
static int dynamic_ranges[] = {1097, 1087, 1069, 1041, 994, 923, 830, 748, 648, 552, 464};
#endif
@@ -531,6 +533,13 @@
skip_left = 72;
skip_top = 52;
#endif
+
+ #ifdef CONFIG_7D
+ width = 5360;
+ height = 3516;
+ skip_left = 160;
+ skip_top = 52;
+ #endif
dbg_printf("Photo raw buffer: %x (%dx%d)\n", raw_info.buffer, width, height);
dbg_printf("Skip left:%d right:%d top:%d bottom:%d\n", skip_left, skip_right, skip_top, skip_bottom);
@@ -559,6 +568,7 @@
prev_zoom = zoom;
}
+ #ifdef CONFIG_RAW_LIVEVIEW
/* in zoom mode: yuv position changed? force a refresh */
if (lv_dispsize > 1)
{
@@ -574,6 +584,7 @@
prev_delta_x = delta_x;
prev_delta_y = delta_y;
}
+ #endif
if (dirty)
{
@@ -700,6 +711,8 @@
int preview_skip_top = skip_top;
int preview_width = raw_info.jpeg.width;
int preview_height = raw_info.jpeg.height;
+
+ #ifdef CONFIG_RAW_LIVEVIEW
if (lv_dispsize > 1)
{
int delta_x, delta_y;
@@ -742,6 +755,7 @@
preview_height = vram_hd.height / zoom_corr;
}
}
+ #endif
raw_set_preview_rect(preview_skip_left, preview_skip_top, preview_width, preview_height);
diff -r af0907c14c7d src/state-object.c
--- a/src/state-object.c Thu Aug 01 14:44:07 2013 +0300
+++ b/src/state-object.c Thu Aug 01 15:32:27 2013 +0300
@@ -17,6 +17,7 @@
#ifdef CONFIG_7D
#define LV_STATE (*(struct state_object **)0x4458)
+#define SDS_FRONT3_STATE (*(struct state_object **)0x32DC)
#endif
#ifdef CONFIG_7D_MASTER
@@ -358,7 +359,7 @@
int ans = StateTransition(self, x, input, z, t);
int new_state = self->current_state;
- #if defined(CONFIG_5D2) || defined(CONFIG_550D)
+ #if defined(CONFIG_5D2) || defined(CONFIG_550D) || defined(CONFIG_7D)
// SDSf3:(0) -- 3 sdsMem1toRAWcompress-->(1)
// SDSf3:(1) -- 3 sdsMem1toJpegDevelop-->(1)
if (old_state == 0 && input == 3 && new_state == 1)
diff -r af0907c14c7d src/zebra.c
--- a/src/zebra.c Thu Aug 01 14:44:07 2013 +0300
+++ b/src/zebra.c Thu Aug 01 15:32:27 2013 +0300
@@ -827,6 +827,7 @@
int can_use_raw_overlays_photo()
{
+ return 1;
// MRAW/SRAW are causing trouble, figure out why
// RAW and RAW+JPEG are OK
if ((pic_quality & 0xFE00FF) == (PICQ_RAW & 0xFE00FF))
I'll be away for a few hours; if you can clean it up (e.g. by copying dynamic range values from DxO, color matrix from dcraw, and tweaking the offsets), it will be very helpful.
Some tests
NORMAL
(http://imageshack.us/a/img837/1861/r3mz.jpg)
DUAL ISO
(http://imageshack.us/a/img407/5785/80qu.jpg)
This is wanderful and never show up the 70error :D
I see some things happen that i don't know if it's normal
1- Wend i back home to see the photos, i see in the structure of the CF card (in canon folders) that after i take a few photos he creates another folder and put the rest of the pictures there.
2-Wend i pick-up all the photos and drag to the cr2hdr, he fail always the first pictures. The rest of the pictures, he transcribe good and make the dng file. But almost in the end of each file, wend cr2hdr are doing is work, its show up a message saying that the exiftool didn't work, like the image below. Evan with this error the cr2hdr make is job and make the dng that i can open in photoshop for making the right tweek.
3-A problem that i come across is that is hard for make the right exposure. Didn't, yet, get the best way to exposure.
(http://imageshack.us/a/img441/9287/uod5.jpg)
Beside this DUAL ISO is one more great function in the ML arsenal =D.
1) normal Canon behavior (ever used a Canon camera without ML?)
2) try working in a short directory (e.g. c:\test)
3) I expose to the right for ISO 100; if the scene needs dual ISO, it would look very dark in LiveView at ISO 100, but the histogram will touch the right side.
Is nice to see that in this forum there are new signs of life. I appreciate the effort to give even new features to 7d.
I would like to ask what steps should I follow to use the new firmware that you are testing in these days.
I have copied the new files in the folder modules in magic lantern alpha 2, but I have not seen anything changed. Not able to see the New gui interface,
I did something wrong?
Could someone kindly explain to me how to do even without autoboot.
Sorry for my bad english and Thanks!
@ Arrinkiiii
Impressive picture :P !!! I've understood the interrest of dual ISO ;)
I've tried to find cr2hdr.exe, but I failed.
I guess it's a programm that automatically blend the two pictures taken in the two different ISO.
I'm right ?
Where can I find it ? And can it be replaced by another program that runs on a Mac ?
Thierry
Quote from: a1ex on August 01, 2013, 07:03:52 PM
1) normal Canon behavior (ever used a Canon camera without ML?)
2) try working in a short directory (e.g. c:\test)
3) I expose to the right for ISO 100; if the scene needs dual ISO, it would look very dark in LiveView at ISO 100, but the histogram will touch the right side.
1- Never hehe :D always full ML (im not so from photography)
2- I will try, thank you.
3- Move the camera to the left for expose with the right part of the screen/viewfinder and then frame again your subject? ...and look to the histogram for see the correct exposure?
4- Im using 100 iso in the canon menu and 1600 in the dual iso menu. Do you think that is the best settings or is the same if i change?
5 - You wrote this,
Quote from: a1ex on August 01, 2013, 02:44:59 PM
I think I've got raw histogram and zebras working in photo mode, sort of. Zebras say almost the entire picture is overexposed, most probably a wrong offset. Quick and dirty patch:
diff -r af0907c14c7d platform/7D.203/Makefile.setup.default
--- a/platform/7D.203/Makefile.setup.default Thu Aug 01 14:44:07 2013 +0300
+++ b/platform/7D.203/Makefile.setup.default Thu Aug 01 15:32:27 2013 +0300
@@ -12,5 +12,6 @@
video_hacks.o \
misc.o \
ptpbuf.o \
+ raw.o \
afma.o
diff -r af0907c14c7d platform/7D.203/internals.h
--- a/platform/7D.203/internals.h Thu Aug 01 14:44:07 2013 +0300
+++ b/platform/7D.203/internals.h Thu Aug 01 15:32:27 2013 +0300
@@ -102,3 +102,5 @@
/** We can record movies in regular photo modes - M, P, Tv, Av... */
#define CONFIG_NO_DEDICATED_MOVIE_MODE
+
+#define CONFIG_RAW_PHOTO
diff -r af0907c14c7d src/raw.c
--- a/src/raw.c Thu Aug 01 14:44:07 2013 +0300
+++ b/src/raw.c Thu Aug 01 15:32:27 2013 +0300
@@ -58,6 +58,8 @@
#define RAW_LV_EDMAC 0xC0F26208
#endif
+#define RAW_LV_EDMAC 0xC0F26208
+
/**
* Photo-mode raw buffer address
* On old cameras, it can be intercepted from SDSf3 state object, right after sdsMem1toRAWcompress.
@@ -67,7 +69,7 @@
* and http://a1ex.bitbucket.io/ML/states/ for state diagrams.
*/
-#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_500D) || defined(CONFIG_600D) || (defined(CONFIG_DIGIC_V) && !defined(CONFIG_FULLFRAME))
+#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_500D) || defined(CONFIG_600D) || (defined(CONFIG_DIGIC_V) && !defined(CONFIG_FULLFRAME)) || defined(CONFIG_7D)
#define RAW_PHOTO_EDMAC 0xc0f04A08
#endif
@@ -140,7 +142,7 @@
* It will also work with the values from some other camera, but colors may be a little off.
**/
-#ifdef CONFIG_5D2
+#ifdef CONFIG_7D
//~ { "Canon EOS 5D Mark II", 0, 0x3cf0,
//~ { 4716,603,-830,-7798,15474,2480,-1496,1937,6651 } },
#define CAM_COLORMATRIX1 \
@@ -242,7 +244,7 @@
* This is only used in photo LiveView, where we can't compute it
*/
-#ifdef CONFIG_5D3
+#ifdef CONFIG_7D
static int dynamic_ranges[] = {1097, 1087, 1069, 1041, 994, 923, 830, 748, 648, 552, 464};
#endif
@@ -531,6 +533,13 @@
skip_left = 72;
skip_top = 52;
#endif
+
+ #ifdef CONFIG_7D
+ width = 5360;
+ height = 3516;
+ skip_left = 160;
+ skip_top = 52;
+ #endif
dbg_printf("Photo raw buffer: %x (%dx%d)\n", raw_info.buffer, width, height);
dbg_printf("Skip left:%d right:%d top:%d bottom:%d\n", skip_left, skip_right, skip_top, skip_bottom);
@@ -559,6 +568,7 @@
prev_zoom = zoom;
}
+ #ifdef CONFIG_RAW_LIVEVIEW
/* in zoom mode: yuv position changed? force a refresh */
if (lv_dispsize > 1)
{
@@ -574,6 +584,7 @@
prev_delta_x = delta_x;
prev_delta_y = delta_y;
}
+ #endif
if (dirty)
{
@@ -700,6 +711,8 @@
int preview_skip_top = skip_top;
int preview_width = raw_info.jpeg.width;
int preview_height = raw_info.jpeg.height;
+
+ #ifdef CONFIG_RAW_LIVEVIEW
if (lv_dispsize > 1)
{
int delta_x, delta_y;
@@ -742,6 +755,7 @@
preview_height = vram_hd.height / zoom_corr;
}
}
+ #endif
raw_set_preview_rect(preview_skip_left, preview_skip_top, preview_width, preview_height);
diff -r af0907c14c7d src/state-object.c
--- a/src/state-object.c Thu Aug 01 14:44:07 2013 +0300
+++ b/src/state-object.c Thu Aug 01 15:32:27 2013 +0300
@@ -17,6 +17,7 @@
#ifdef CONFIG_7D
#define LV_STATE (*(struct state_object **)0x4458)
+#define SDS_FRONT3_STATE (*(struct state_object **)0x32DC)
#endif
#ifdef CONFIG_7D_MASTER
@@ -358,7 +359,7 @@
int ans = StateTransition(self, x, input, z, t);
int new_state = self->current_state;
- #if defined(CONFIG_5D2) || defined(CONFIG_550D)
+ #if defined(CONFIG_5D2) || defined(CONFIG_550D) || defined(CONFIG_7D)
// SDSf3:(0) -- 3 sdsMem1toRAWcompress-->(1)
// SDSf3:(1) -- 3 sdsMem1toJpegDevelop-->(1)
if (old_state == 0 && input == 3 && new_state == 1)
diff -r af0907c14c7d src/zebra.c
--- a/src/zebra.c Thu Aug 01 14:44:07 2013 +0300
+++ b/src/zebra.c Thu Aug 01 15:32:27 2013 +0300
@@ -827,6 +827,7 @@
int can_use_raw_overlays_photo()
{
+ return 1;
// MRAW/SRAW are causing trouble, figure out why
// RAW and RAW+JPEG are OK
if ((pic_quality & 0xFE00FF) == (PICQ_RAW & 0xFE00FF))
I'll be away for a few hours; if you can clean it up (e.g. by copying dynamic range values from DxO, color matrix from dcraw, and tweaking the offsets), it will be very helpful.
I just learn pascal in my old years of school. I Don't understand this but if exist anything that i can do just tell me. Vacations time.
I think my doubts is the doubts of a lot of people here in this post. More one time thanks for thinking in the 7D and for this great function.
Quote from: ThLDQ on August 01, 2013, 07:58:44 PM
@ Arrinkiiii
Impressive picture :P !!! I've understood the interrest of dual ISO ;)
I've tried to find cr2hdr.exe, but I failed.
I guess it's a programm that automatically blend the two pictures taken in the two different ISO.
I'm right ?
Where can I find it ? And can it be replaced by another program that runs on a Mac ?
Thierry
Thank you ThLDQ :D could have been better if i know how to exposure correct, i will try the way that a1ex told to expose.
Here is the link for the app for past from cr2 (raw) to DNG = from interlaced iso to normal iso. For windows and mac.
http://www.magiclantern.fm/forum/index.php?topic=7139.0 it's in the first post.
Quote from: Gippi on August 01, 2013, 07:44:14 PM
Is nice to see that in this forum there are new signs of life. I appreciate the effort to give even new features to 7d.
I would like to ask what steps should I follow to use the new firmware that you are testing in these days.
I have copied the new files in the folder modules in magic lantern alpha 2, but I have not seen anything changed. Not able to see the New gui interface,
I did something wrong?
Could someone kindly explain to me how to do even without autoboot.
Sorry for my bad English and Thanks!
You need to bootflag your 7D for accept the new ML with the dual iso module, its the only way to do it. Go here to see the post of britom, he explain everything very well.
http://www.magiclantern.fm/forum/index.php?topic=3974.msg62242#msg62242
I think that this treat should be update with the new version of ML for the 7D and maybe also putting the explanation of britom for better achievement.
What ML community think?
DOOOH--- my bad.. Had the wrong folder.. sorry.. :o
Now I need to sound stupid.. I tried the tutorial britom did via Parallels (Yea yea I'm a mac dude). But when I try the "Type bspatch.exe 7d000123.fir firmware.fir patch.bsdiff and press enter" I get an error that says bspatch.exe is not recognized as an internal or external command, operable program or patch?!?! Any idea?
Quote from: arrinkiiii on August 01, 2013, 10:32:39 PM
I think that this treat should be update with the new version of ML for the 7D and maybe also putting the explanation of britom for better achievement.
What ML community think?
I think that this thread, as per his title, should be closed and a new one should be opened, now the topic is (almost) totally different than the original one.
I'd suggest that the new thread should be opened by Britom and then put sticky.
Quote from: a1ex on August 01, 2013, 07:03:52 PM
1) normal Canon behavior (ever used a Canon camera without ML?)
2) try working in a short directory (e.g. c:\test)
3) I expose to the right for ISO 100; if the scene needs dual ISO, it would look very dark in LiveView at ISO 100, but the histogram will touch the right side.
1) What a1ex was trying to say is that after picture nr 9999 Canon automatically creates new folder, because it would overwrite existing pictures (It's starts all over with nr 0001).
@arrinkiiii
I think that your example is misleading. Isn't it the same picture with different settings in cameraRAW? For appropriate test you should take two photos: one with dual iso off and another with dual iso ON. And expose for gray card.
Now i'm in the step that says: click OK and Select the firmware.fir file from the first folder. Click OK Again. Now is that the firmware.fir file I just made.. and should I select the one from the card or the same file from the folder where I made it?
Quote from: jphansen on August 01, 2013, 11:53:47 PM
Now i'm in the step that says: click OK and Select the firmware.fir file from the first folder. Click OK Again. Now is that the firmware.fir file I just made.. and should I select the one from the card or the same file from the folder where I made it?
"From the first folder" not from the cf card.
NOW I fucked up.. EOScard crash on my.. I was not able to select the 203 alpha and it crashed.. Here is the error log...
AppName: eoscard.exe AppVer: 0.0.0.0 ModName: kernel32.dll
ModVer: 5.1.2600.5508 Offset: 00012aeb
When hitting Ports in progress I get: Invalid argument to date encode??
Quote from: Pelican on August 01, 2013, 12:56:14 PM
I've refreshed the files in the zip here (http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip) so EOScard can download this version from now.
Also updated EOScard itself (bugfix).
The file_man.mo is the newest with the date info.
Quote from: pit3k on August 01, 2013, 11:52:15 PM
1) What a1ex was trying to say is that after picture nr 9999 Canon automatically creates new folder, because it would overwrite existing pictures (It's starts all over with nr 0001).
@arrinkiiii
I think that your example is misleading. Isn't it the same picture with different settings in cameraRAW? For appropriate test you should take two photos: one with dual iso off and another with dual iso ON. And expose for gray card.
Hi pit3k,
1- Thank you for the explanation, know i know why :D
2- OK, i will do that. Is just open the DNG in photshop (raw) and then cameraraw give me a picture with 0 settings (normal picture). Then i adjust the exposure, highlights, shadows, etc and is what gives me the (dual iso) picture. I think this method is how you can see the dynamic range that the dual iso gives you. So... im wrong :-\ ...damn!
Anyone knows why wend i see the picture in camera preview is different wend i open the dng? (light, exposure...)
Can someone upload a regular CR2 and a dual-ISO CR2 please and I'll have a look at getting alex's code fully functional.
Regular CR2 http://www.mediafire.com/?9hhpudxhxdn69ee
Dual ISO CR2 http://www.mediafire.com/?67v18257b4tjob2
Interestingly, this was shot at 100/12800 which is about 7eV, but the cr2hdr said it's only about 5eV. The resulting DNG looks a lot like regular CR2 but with less noise in the shadow.
If you look at DxO dynamic range numbers, you will notice there's no point in going above ISO 1600 on 7D. I've left the higher ISOs so you can experiment, but that doesn't mean you should use the extreme settings.
The 5 EV difference means the highest analog ISO is 3200, which confirms this: http://www.guillermoluijk.com/article/isos5dmkii/index.htm
BTW, got something cool for you: https://bitbucket.org/hudson/magic-lantern/commits/c2a01891156e
From now on, it's your job to get it fully working.
Quote from: a1ex on August 02, 2013, 08:39:19 AM
If you look at DxO dynamic range numbers, you will notice there's no point in going above ISO 1600 on 7D. I've left the higher ISOs so you can experiment, but that doesn't mean you should use the extreme settings.
The 5 EV difference means the highest analog ISO is 3200, which confirms this: http://www.guillermoluijk.com/article/isos5dmkii/index.htm
BTW, got something cool for you: https://bitbucket.org/hudson/magic-lantern/commits/c2a01891156e
From now on, it's your job to get it fully working.
WHHAAAT WHAT WHAT WHAAATTTT!!!!!!!!!!!!!!!!
OMG I'm about to literally cry!!!!! The gods must have listened cause I was browsing for used 5D's.... and of course the gods have the names of ALL the ML Dev team!!!!
Alex, does this actually means that it's *very* possible for this to happen?? :)
QuoteFrom now on, it's your job to get it fully working.
This means I'm confident you can do it ;)
Updated this chart (http://www.magiclantern.fm/forum/index.php?topic=6215) with theoretical values.
Haha yes! I read that after I replied.. me as a user would love to contribute by testing of course..
What I meant to say is at which stage is this AWESOME breakthrough? Is it at the same level of other cameras or is it just bursting silent pics? I'm asking 'cause I don't know how to compile it myself! (though it may be easy if I put my mind to it! ;) )
Thanksssss!!!!! If you're confident, then I'm confident! :)
For now it's just bursting silent pics without proper sync. Most of them are good.
:')
http://en.wikipedia.org/wiki/Orgasmatron
Canon DSLRs are getting a beating because the DR as a function of ISO measured at DxOMark starts to flatten asymptotically towards 11-12Ev at ISO1600 and below, while recent Nikon DSLRs (and everything based on Sony sensors) appears to improve their DR all the way to ISO 100 (14+ Ev):
http://www.dxomark.com/index.php/Cameras/Compare-Camera-Sensors/Compare-cameras-side-by-side/(appareil1)/795|0/(brand)/Canon/(appareil2)/792|0/(brand2)/Nikon
The difference appears to be Canon using off-sensor ADC (but perhaps on-sensor analog gain). Therefore, a significant amount of noise is added to the signal subsequent to analog amplification and prior to ADC. By raising the amplifier gain "just enough", the signal will be hot enough to travel this path without being affected that much by noise. DSLRs based on Sonys on-sensor ADC are not affected in the same way, and many are described as "ISO-less", i.e. raw shooters might just as well shoot in ISO 100 all the time, under-exposing when necessary and raising the brightness in their raw developer instead of worrying about ISO in camera.
The potential of using "dual ISO" ought to be to have the highlight capability of ISO100, but improving the shadow noise by increasing the gain.
The downside is that ISO cannot be applied as a function of regional signal level: having alternate line(pairs) having different ISO is a kind of "interlacing" that will amplify some sensels that should have been amplified, and not amplify some sensels that should have been.
I think that the image examples shown in this thread have been somewhat misleading in that they appear to compare a regular "flat" image with a tone-mapped dual ISO image. Just like when comparing HDR photography to LDR photography, I think that that is only 50% of the story. In order to really visualize the differences, we might want 4 images:
1. Regular captured, Regular processed image
2. Regular captured, Tonemapped image
3. DualISO captured, Regular processed image
4. DualISO captured, Tonemapped image
For most, the difference between image 2 and image 4 might be most telling, as the tonal range should be similar, but DualISO ought to have less visible shadow noise and some artifacting/loss of resolution.
Is it possible/feasible to pre-process dualISO images into something that appears like regular 7D images (only with less shadow noise) suitable for any raw converter?
-h
Cheers feureau.
I'm busy busy busy this weekend, but I'll try and spend some time on it tonight.
hjulenissen: you seem to know your stuff, but from your question, I bet you did not read my paper and you did not download any DNG samples.
Quote from: a1ex on August 02, 2013, 09:16:43 AM
For now it's just bursting silent pics without proper sync. Most of them are good.
"cry me a river..." No words :o
(http://www.whoateallthepies.tv/wp-content/uploads/2012/11/rod.gif)
hahahah good one britom and pit3k ;D
- LONG LIVE THE 7D -
(http://media.tumblr.com/tumblr_m8gkijAxEj1qalmot.gif)
Quote from: a1ex on August 02, 2013, 09:30:19 AM
hjulenissen: you seem to know your stuff, but from your question, I bet you did not read my paper and you did not download any DNG samples.
Correct. I have now read your paper and see that you answer my question (and then some). Excellent work!
Would have been cool if some Canon models applied ISO gain per color channel, but I guess that is inefficient from a low-level hw perspective. "white-balancing ISO" where weak color channels gets the benefit of higher ISO than hotter color channels.
It seems from your figures that you use MATLAB to some degree. Is this your personal stuff, or does the ML repository contain MATLAB models?
-h
Sorry I've missed something, haven't I?
Quote from: edwmotion on August 02, 2013, 10:18:49 AM
Sorry I've missed something, haven't I?
Look under "7D"
(http://a1ex.magiclantern.fm/bleeding-edge/raw/raw-chart.png)
And please, please 25p @ 1080p
(http://stream1.gifsoup.com/view1/1722442/begging-o.gif)
raw video? damn I sold my 7D :-\
Just kidding. ;D
Thank you Alex. I appreciate your hard work.
ML team finaly find the way for unlocked raw video on 7D at 1728 x 1156 max res ?
wow, its a christmas today. thanks to all developping team. so, happy to see the devollopement of 7d ML go ahead :)
Quote from: obiyan19 on August 02, 2013, 11:21:51 AM
ML team finaly find the way for unlocked raw video on 7D at 1728 x 1156 max res ?
wow, its a christmas today. thanks to all developping team. so, happy to see the devollopement of 7d ML go ahead :)
For now the values are theoretical as a1ex wrote.
Quote from: jphansen on August 02, 2013, 12:29:19 AM
NOW I fucked up.. EOScard crash on my.. I was not able to select the 203 alpha and it crashed.. Here is the error log...
AppName: eoscard.exe AppVer: 0.0.0.0 ModName: kernel32.dll
ModVer: 5.1.2600.5508 Offset: 00012aeb
When hitting Ports in progress I get: Invalid argument to date encode??
You can copy the files on your cf card from here: http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip (http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip)
But will that do the same job as EOScard do.. like enable bootflag and so on?
Quote from: pit3k on August 02, 2013, 11:29:42 AM
You can copy the files on your cf card from here: http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip (http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip)
Quote from: jphansen on August 02, 2013, 11:58:16 AM
But will that do the same job as EOScard do.. like enable bootflag and so on?
But you did enable bootflag in EOS utility, by changing the firmware. Now all you need to do is copy ML on cf card.
EOScard is just an app made by @Pelican that automatically downloads latest ML build.
just for the stupid like me.. when i'm running my 7d on the lastest canon firmware, do i need to downgrade to an earlier firmware to set the bootflag thing? the tutorial some pages ago is nice, but that's the point that's not completely clear to me.
but with the latest stuff happening here i really do need to step up from alpha2... :)
Quote from: mburgst on August 02, 2013, 12:29:45 PM
just for the stupid like me.. when i'm running my 7d on the lastest canon firmware, do i need to downgrade to an earlier firmware to set the bootflag thing? the tutorial some pages ago is nice, but that's the point that's not completely clear to me.
but with the latest stuff happening here i really do need to step up from alpha2... :)
Once you have latest stock canon firmware on your 7D, you do what tutorial says (make new firmware using cmd, then use eos utility... ).
Quote from: Audionut on August 02, 2013, 09:29:55 AM
Cheers feureau.
I'm busy busy busy this weekend, but I'll try and spend some time on it tonight.
You're welcome. Happy to help. :P
Are you working on the RAW video too, btw? :3
Quote from: jphansen on August 02, 2013, 11:58:16 AM
But will that do the same job as EOScard do.. like enable bootflag and so on?
Yes, is the same files. EOSCard just download the files and save in your cf card.
But for this new version of ML work you need to enable in your camera autoboot. In the old version in the root tree of your CF card you have a .fir file, that for work you need to go to canon menu and update your firmware. With this new version in your root tree of your CF card you will have a autoexec.bin file and with this your camera don't have the ability to read this autoexec.bin... so, you need to bootflag your camera.
How you do this? The only way is get a old version of a 7D firmware, patch that firmware that will produce a file with the name firmware.fir and with EOSUtility flash your camera with that file... then you just need your CF card with the new files, that EOSCard put in your CF card... or just take from the zip file and put in your CF card. I advice to use EOSCard from Pelican, works like a charm.
All the instructions are were, by user britom.
http://www.magiclantern.fm/forum/index.php?topic=3974.msg62242#msg62242
Quote from: mburgst on August 02, 2013, 12:29:45 PM
just for the stupid like me.. when i'm running my 7d on the lastest canon firmware, do i need to downgrade to an earlier firmware to set the bootflag thing? the tutorial some pages ago is nice, but that's the point that's not completely clear to me.
but with the latest stuff happening here i really do need to step up from alpha2... :)
No, will not downgrade. For bootflag the 7D you need a old version of a 7D firmware then patch it. It don't downgrade, is just a way the devs find to bootflag the camera. It will stay with the normal firmware version that you got in your camera, the latest.
With this action you camera will be reading the autoexec.bin file (bootflag). You never more going to need to upgrade your firmware for get ML in the 7D (like in the past) and you will have the new ML in you camera every time that you turn it on and of course having the new ML files in the CF card.
Any doubts just ask me, if i know i will answer... my english is not the best 8)
awesome, thanks for explaining (again)! :)
just two questions left:
1.) isn't the firmware.fir always the same so you could put it somewhere to download? for us lazy bastards.. ;-)
2.) why updating via eosutility? can't this done via camera?
so the firmware upgrade just get's launched and sets the bootflag, but doesn't change anything to/in the camera? i'm just curious about this bootflag thing.
Quote from: mburgst on August 02, 2013, 03:26:40 PM
awesome, thanks for explaining (again)! :)
just two questions left:
1.) isn't the firmware.fir always the same so you could put it somewhere to download? for us lazy bastards.. ;-)
2.) why updating via eosutility? can't this done via camera?
so the firmware upgrade just get's launched and sets the bootflag, but doesn't change anything to/in the camera? i'm just curious about this bootflag thing.
U welcome :D
1- Yes. But this patch firmware is illegal to distribute. If you make yours it's ok... and is so easy to do it. Just follow the instructions of britom.
2) Don't know. And must be with a older version of EOSUtility, like a old 7D firmware. I think is because the software that canon makes, losing any door open that people can enter.
Yes, its what it does.
*Im curiosity to see if they (canon) going to make any big change in there software, for blocking the ML.
Quote from: a1ex on August 02, 2013, 08:39:19 AM
If you look at DxO dynamic range numbers, you will notice there's no point in going above ISO 1600 on 7D. I've left the higher ISOs so you can experiment, but that doesn't mean you should use the extreme settings.
The 5 EV difference means the highest analog ISO is 3200, which confirms this: http://www.guillermoluijk.com/article/isos5dmkii/index.htm
I don't speak spanish. What's it about?
So, does it mean to use dual ISO at its maximum eV on 7D, one must use 100/1600? And if I need to shoot at higher sensitivity, the top value would not exceed 1600 even though I switch it to higher ISO?
Haven't tried this, but does inverting that helps? say, 12800/100?
also, what is this DXO dynamic range numbers everyone's talking about? The camera sensor ratings?
Having problems getting ML to boot on my 7D. Followed britom's instructions to set the bootflag. ended up with the 3 ROM bin files so I assume it worked. Manually put the autoexec and ML folders on the root of my CF card with the DCIM and MISC folders. When I turn on the camera and hit the delete key nothing happens.
Quote from: themichael on August 02, 2013, 08:30:46 PM
Having problems getting ML to boot on my 7D. Followed britom's instructions to set the bootflag. ended up with the 3 ROM bin files so I assume it worked. Manually put the autoexec and ML folders on the root of my CF card with the DCIM and MISC folders. When I turn on the camera and hit the delete key nothing happens.
Make the firmware again using cmd and carefully check what are you typing into console. It should create just one file: firmware.fir. Do the rest of steps as the tutorial says.
Awesome news just keep on coming! Thanks for the developers!
Just one question.. if I install this autoboot version with the bootflag, then what happens if I insert my eye-fi card that has no ML on it?
Will my camera still boot to canon firmware?
And what if I have the non bootable version of 7D alpha on my other card. Will something weird happen if I have the bootflag thingy enabled?
Thanks again!
Quote from: jalejake on August 02, 2013, 09:23:42 PM
Awesome news just keep on coming! Thanks for the developers!
Just one question.. if I install this autoboot version with the bootflag, then what happens if I insert my eye-fi card that has no ML on it?
Will my camera still boot to canon firmware?
And what if I have the non bootable version of 7D alpha on my other card. Will something weird happen if I have the bootflag thingy enabled?
Thanks again!
Bootflag only change stuff on your card. Your 7D is still the stock 7D like it used to be.
Nightly:
Magic Lantern v2.3.NEXT.2013Aug02.7D203
Mercurial changeset: 58580d531981 (unified) tip
Built on 2013-08-02 19:27:50 by Pel@pelslaptop
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym
Edit:
Typo fixed in the second link.
Quote from: Pelican on August 02, 2013, 10:20:23 PM
Nightly:
Magic Lantern v2.3.NEXT.2013Aug02.7D203
Mercurial changeset: 58580d531981 (unified) tip
Built on 2013-08-02 19:27:50 by Pel@pelslaptop
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D.203.sym
Pelican,
second file shows "bad link" file not found
I was able to do almost everything, but when trying to download ML, EOScard.exe just crashed on my windows. (I'm running VM windows inside mac, so that might be the reason.) Anyway, could someone please send the needed ML files to me? I'd appreciate that. My email is in my profile info. Or where can I find the needed files? I would have tried the ones pelican just posted, but the last link was bad..and I believe there might be something else too? Sorry if this has been mentioned before.
Thank you!
Quote from: feureau on August 02, 2013, 07:40:29 PM
I don't speak spanish. What's it about?
So, does it mean to use dual ISO at its maximum eV on 7D, one must use 100/1600? And if I need to shoot at higher sensitivity, the top value would not exceed 1600 even though I switch it to higher ISO?
Haven't tried this, but does inverting that helps? say, 12800/100?
also, what is this DXO dynamic range numbers everyone's talking about? The camera sensor ratings?
Hi feureau, you got a inglish flag in the website for getting the inglish version. It's albout the ISO. Raw and or Jpeg... about native ISO's, etc...
http://translate.google.com/translate?u=http%3A%2F%2Fwww.guillermoluijk.com%2Farticle%2Fisos5dmkii%2Findex.htm&langpair=es%7Cen&hl=EN&ie=UTF-8
Quote from: Pelican on August 02, 2013, 10:20:23 PM
Nightly:
Magic Lantern v2.3.NEXT.2013Aug02.7D203
Mercurial changeset: 58580d531981 (unified) tip
Built on 2013-08-02 19:27:50 by Pel@pelslaptop
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D.203.sym
What this version brings new?
Quote from: pit3k on August 02, 2013, 08:55:53 PM
Make the firmware again using cmd and carefully check what are you typing into console. It should create just one file: firmware.fir. Do the rest of steps as the tutorial says.
Sorry, I wasn't clearer. The three ROM bin files are after the update in the camera.
EOScard 1.36 crashed on two computers (Win7 and XP) even if nothing is clicked.
Will try once more with all new downloads.
**EDIT: Still no joy. The autoexec.bin goes in the root corrct? I am using a 16MB 133x card. Somebody have a checksum for the generated firmware file?
Quote from: themichael on August 02, 2013, 10:43:20 PM
EOScard 1.36 crashed on two computers (Win7 and XP) even if nothing is clicked.
EOSCard 1.36 crashes on my Windows 8 64-bit also.
After a few seconds an Application Error occurs.
"Exception EConvertError in module EOScard.exe at 00021E67."
"Invalid argument to date encode."
DANG!
https://dl.dropboxusercontent.com/u/43043701/SilentRAW.mp4
EOSCard crashes on Windows 7 64-bit, I also tried on virtual XP. Also crashes on XP.
"Exception EConvertError in module EOScard.exe at 00021E67."
"Invalid argument to date encode."
Quote from: pavel89l on August 03, 2013, 12:23:41 AM
"Exception EConvertError in module EOScard.exe at 00021E67."
"Invalid argument to date encode."
That's the same error I got..
I am going crazy trying to get EOSUtility to work. Under winodows7 x64 I have downloaded EOS Utility from the link above and when I try to run the firmware.fir update it says connection lost.
I have tried under osx it says out of memory
New versions say incompatible version when trying to downgrade.
Is there another solution for me to make the bootflag
It starts the loading the firmware program on the 7d and it disconects from the eos utility 7d restarts and on the card I get ROM0.bin ROM1.bin and ROM2.bin along with FIRMWARE.FIR
I delete all 4 files correct and place ML?
The correct link is http://pel.hu/ML/7D_203.sym
same problem here. newer version of eos utility wont let me, cause of an unsopported version. the connection gets lost with the supported version. i then also get the four files. eoscard worked for a few seconds when i started it for the first time. now same error as everyone else. also not working in win xp mode. placing the files on the card manually also wont work for me..
i really want this to work ... please support us with an even more detailed instruction (yes we are morrons )
thank you so much to everyone who is contributing to this project and making this happen. i was close to tears when i read that raw was coming for my beloved 7D earlier this evening. keep the good work up guys, you all are awesome!
why is loosing connections its beyond me I have tried even installing full solution disk but same thing :(
I guess I did everything right.. Flashed my 7D with the firmware.fir and loaded the newest "magiclantern-7D.203.Alpha2" to the card.. including the autoexec.bin. But nothing happines when I boot up my camera.. any idears? :-/
Are you using the EOS Utility software from this threat? it HAS to be that version..
Quote from: edingacic on August 03, 2013, 01:21:06 AM
why is loosing connections its beyond me I have tried even installing full solution disk but same thing :(
Quote from: jphansen on August 03, 2013, 01:22:15 AM
Are you using the EOS Utility software from this threat? it HAS to be that version..
yes! I am using the version from this thread version 2.8.1.0 connection lost when I hit ok for update to go
and you did the: Type bspatch.exe 7d000123.fir firmware.fir patch.bsdiff and press enter
Quote from: edingacic on August 03, 2013, 01:22:53 AM
yes! I am using the version from this thread version 2.8.1.0 connection lost when I hit ok for update to go
yes it gave me that firmware.fir I place that onto a CF card fire up eos utility downloaded form this thread and everything is fine up to the point where it says to go from version to version I hit OK and th eos utility looses connection
Sorry.. I'm new to the flashing part as well
Quote from: edingacic on August 03, 2013, 01:28:20 AM
yes it gave me that firmware.fir I place that onto a CF card fire up eos utility downloaded form this thread and everything is fine up to the point where it says to go from version to version I hit OK and th eos utility looses connection
Hello there,
first of all: Thank you so much everyone who spend their time developing this and helping other users!
This is fantastic!
Sadly, I seem to be unable to boot ML. I think setting the autoboot flag didnt work correctly for me. I tried serveral times.
While installing the FW update with the old EOS-Utility the red light on my camera flashes and the camera screen says 'loading...'.
After a few seconds, the camera looses the connection to the PC and goes dark (or maybe the process is just finished?).
During that process 3 files are created in the root directory of my CF card and some more files in \misc.
Now, does that mean that the autoboot-flag was set successfully?
Or should there be a kind of confirmation screen (as is does for other cameras as shown in the ML-wiki)?
Also EOS utility says to press "set" on camera to begin update process, but that doesnt help either.
After copying the ML-files to the card, the camera wont boot ML.
Im not sure what to try next, maybe someone knows an answer.
win7 64bit
thx
Quote from: britom on August 03, 2013, 12:06:43 AM
DANG!
https://dl.dropboxusercontent.com/u/43043701/SilentRAW.mp4
This is the burst of silent pics? How you manage to do it?
Quote from: britom on August 03, 2013, 01:10:43 AM
The correct link is http://pel.hu/ML/7D_203.sym
This link just go to the web page of Pelican. What i should do with this?
Quote from: jalejake on August 03, 2013, 12:33:49 AM
That's the same error I got..
My friends, the EOSCard from Pelican, just goes to a weblink and download the ML version and record on your CF card... you can just download a zip file and pass the files to your CF card.
But beside this, EOSCard from pelican, you need to bootflag your camera to able to read this new ML files in your CF card... And for do this you need a version of the 7D firmware (firmware 123.fir,that you can find in britom instructions) and pacth it... then in a format CF card you put the file firmware.fir (that you created with old firmware and pacth) in to your 7D.
After this, you format or deleted the firmware.fir and put the new ML files... that you record with EOSCard or just download it and copy/past to CD card.
This is the link for the files that you need to put in your CF card. But before this, you need to bootflag your camera, like i said before or like instructions of britom ( check a few posts/pages before).
LINK OF THE FILES THAT YOU NEED TO PUT IN YOUR CF CARD (NEW MLhttp://www.sendspace.com/file/nq43xx
LINK FOR THE FILES AND INSTRUCTIONS FOR MAKE YOUR CAMERA BOOTABLE (BEFOR YOU USE THE NEW ML http://www.magiclantern.fm/forum/index.php?topic=3974.msg62242#msg62242
Let's go people!!! It's easy... after comprehension :D
Quote from: arrinkiiii on August 03, 2013, 01:57:56 AM
This is the burst of silent pics? How you manage to do it?
This link just go to the web page of Pelican. What i should do with this?
My friends, the EOSCard from Pelican, just goes to a weblink and download the ML version and record on your CF card... you can just download a zip file and pass the files to your CF card.
But beside this, EOSCard from pelican, you need to bootflag your camera to able to read this new ML files in your CF card... And for do this you need a version of the 7D firmware (firmware 123.fir,that you can find in britom instructions) and pacth it... then in a format CF card you put the file firmware.fir (that you created with old firmware and pacth) in to your 7D.
After this, you format or deleted the firmware.fir and put the new ML files... that you record with EOSCard or just download it and copy/past to CD card.
This is the link for the files that you need to put in your CF card. But before this, you need to bootflag your camera, like i said before or like instructions of britom ( check a few posts/pages before).
LINK OF THE FILES THAT YOU NEED TO PUT IN YOUR CF CARD (NEW ML
http://www.sendspace.com/file/nq43xx
LINK FOR THE FILES AND INSTRUCTIONS FOR MAKE YOUR CAMERA BOOTABLE (BEFOR YOU USE THE NEW ML
http://www.magiclantern.fm/forum/index.php?topic=3974.msg62242#msg62242
Let's go people!!! It's easy... after comprehension :D
The problem is in EOSUtility I can not run it it disconnects itself when I hit final OK before the windows comes up about SET button , camera goes into loading program for firmware updated but then restarts because it lost connection with EOSUtility thats the main problem. Running win7 64 bit
anything I can do to keep the connection up?
Quote from: Haruki on August 03, 2013, 01:52:30 AM
Hello there,
first of all: Thank you so much everyone who spend their time developing this and helping other users!
This is fantastic!
Sadly, I seem to be unable to boot ML. I think setting the autoboot flag didnt work correctly for me. I tried serveral times.
While installing the FW update with the old EOS-Utility the red light on my camera flashes and the camera screen says 'loading...'.
After a few seconds, the camera looses the connection to the PC and goes dark (or maybe the process is just finished?).
During that process 3 files are created in the root directory of my CF card and some more files in \misc.
Now, does that mean that the autoboot-flag was set successfully?
Or should there be a kind of confirmation screen (as is does for other cameras as shown in the ML-wiki)?
Also EOS utility says to press "set" on camera to begin update process, but that doesnt help either.
After copying the ML-files to the card, the camera wont boot ML.
Im not sure what to try next, maybe someone knows an answer.
thx
This is what happen with me. I flash (use the old EOSUtilty and "update" my camera with the firmware.fir (that i creat with the old 7d firmware that i pacht it). My camera went black. I take the battery and format my cf card in the pc... put the new ML files in cf card... put the cf card in camera and turn on... and voilá the new Magic Lantern (ML) in there. No need to update firware again, is just there. Press the trash basket and you got the menu of ML (press two times) .
Quote from: Haruki on August 03, 2013, 01:52:30 AM
Hello there,
first of all: Thank you so much everyone who spend their time developing this and helping other users!
This is fantastic!
Sadly, I seem to be unable to boot ML. I think setting the autoboot flag didnt work correctly for me. I tried serveral times.
While installing the FW update with the old EOS-Utility the red light on my camera flashes and the camera screen says 'loading...'.
After a few seconds, the camera looses the connection to the PC and goes dark (or maybe the process is just finished?).
During that process 3 files are created in the root directory of my CF card and some more files in \misc.
Now, does that mean that the autoboot-flag was set successfully?
Or should there be a kind of confirmation screen (as is does for other cameras as shown in the ML-wiki)?
Also EOS utility says to press "set" on camera to begin update process, but that doesnt help either.
After copying the ML-files to the card, the camera wont boot ML.
Im not sure what to try next, maybe someone knows an answer.
thx
EOSUtility is loosing connection firmware update never actually starts as I understand because it disconnects? I have same problem.
Quote from: edingacic on August 03, 2013, 02:04:01 AM
The problem is in EOSUtility I can not run it it disconnects itself when I hit final OK before the windows comes up about SET button , camera goes into loading program for firmware updated but then restarts because it lost connection with EOSUtility thats the main problem. Running win7 64 bit
anything I can do to keep the connection up?
You dont need the EOSCard. EOSCard just donwload the zip file with the new ML files and save in your CF card. You can downlod the files from the link that i post. But you need still to bootflag your camera.
TWO STEPPS1- Bootflag your 7D
2-Paste the new ML files to your CF card and you are done
Quote from: arrinkiiii on August 03, 2013, 02:07:55 AM
You dont need the EOSCard. EOSCard just donwload the zip file with the new ML files and save in your CF card. You can downlod the files from the link that i post. But you need still to bootflag your camera.
TWO STEPPS
1- Bootflag your 7D
2-Paste the new ML files to your CF card and you are done
I am not talking about EOS Card i am talking about EOS Utility when flashing with patched firmware.
Quote from: arrinkiiii on August 03, 2013, 02:04:58 AM
This is what happen with me. I flash (use the old EOSUtilty and "update" my camera with the firmware.fir (that i creat with the old 7d firmware that i pacht it). My camera went black. I take the battery and format my cf card in the pc... put the new ML files in cf card... put the cf card in camera and turn on... and voilá the new Magic Lantern (ML) in there. No need to update firware again, is just there. Press the trash basket and you got the menu of ML (press two times) .
My camera just went black, it didn't crash. So you say I have to format the card again before copying the ML-files to it?
I just erased the files from the update as is told in the instructions...
Quote from: Haruki on August 03, 2013, 02:12:38 AM
My camera just went black, it didn't crash. So you say I have to format the card again before copying the ML-files to it?
I just erased the files from the update as is told in the instructions...
Does the old EOSUtility says lost connection on your? I am unable i guess to bootflag 7d because of that?
This is what I did.. I had no problem with the flash part.. BUT.. My camera will not auto boot in to ML.. :-/ The card has to just have the Autoexec.bin and the ML folder in root right? Than after the first boot of the camera it create the "DCIM" and "MISC" right? If I try to run the old way with the fake firmware update from the canon menu there is (of cause) no firmware on the CF card.. Something has went wrong some where.. Just dont know where??? BTW I dont see the dual ISO stuff in the ML menu if I take the latest ML and boot it the "old way" Where do I find it?
Quote from: arrinkiiii on August 03, 2013, 02:07:55 AM
You dont need the EOSCard. EOSCard just donwload the zip file with the new ML files and save in your CF card. You can downlod the files from the link that i post. But you need still to bootflag your camera.
TWO STEPPS
1- Bootflag your 7D
2-Paste the new ML files to your CF card and you are done
Quote from: edingacic on August 03, 2013, 02:15:37 AM
Does the old EOSUtility says lost connection on your? I am unable i guess to bootflag 7d because of that?
No it doesn't say that. Yes it says 'connection lost'. Then the window just closes and the camera screen goes black. No camera crash though.
Quote from: edingacic on August 03, 2013, 02:15:37 AM
Does the old EOSUtility says lost connection on your? I am unable i guess to bootflag 7d because of that?
Yes, my old EOSUtility lost connection and my camera went black... i just remove the battery, format my cf card and past the new ML files to the CF card and turn on the camera.
Some one in this treat post that you need to have some kind of file (file from EOSUtility) for the old version of EOSUtility work. So... i already have the new EOSUtility in my PC (win 7) and with the old EOSUtility that britom user post i just flash the firmware.fir to my camera. I lost connection and my camera went to black. I remove battery... format my cf card, put the new ML file and turn on the camera.
It's a little bit confuse but in the same time it's simple.
I'll try to help, my instructions worked on my pc with windows 8 x64 and some people tried in windows 7 without problems so please make sure:
Camera dial is set M mode
Battery is charged
You have the proper drivers (install the cd that came with your camera and then use the eosutility from my post)
Copied the firmware.fir to the card before flashing it from eosutility
Things to try if it still dont work:
***Go to Device Manager by pressing WindowsKey+R and typing devmgmt.msc
Expand the Portable Devices tree and Disable all of them except Canon EOS 7d by right-click - Disable***
Reset your camera to factory settings
Run eosutility in windows 7/vista/xp mode, or as Administrator
Format the CF before trying everything, from the camera
Tell me if nothing helps so i will upload the full cd from where i got the eosutility.
Quote from: jphansen on August 03, 2013, 02:25:33 AM
This is what I did.. I had no problem with the flash part.. BUT.. My camera will not auto boot in to ML.. :-/ The card has to just have the Autoexec.bin and the ML folder in root right? Than after the first boot of the camera it create the "DCIM" and "MISC" right? If I try to run the old way with the fake firmware update from the canon menu there is (of cause) no firmware on the CF card.. Something has went wrong some where.. Just dont know where??? BTW I dont see the dual ISO stuff in the ML menu if I take the latest ML and boot it the "old way" Where do I find it?
Than after the first boot of the camera it create the "DCIM" and "MISC" right?
YES BTW I dont see the dual ISO stuff in the ML menu
If you see the ML menu is because you have able to do the bootflag and run the new ML.Sooo... For activate the dual iso you go to the M TAB. Activat the dual iso module and then go to the Expose Module and chose the dual iso and the iso itself.
Quote from: britom on August 03, 2013, 02:33:30 AM
I'll try to help, my instructions worked on my pc with windows 8 x64 and some people tried in windows 7 without problems so please make sure:
Camera dial is set M mode
Battery is charged
You have the proper drivers (install the cd that came with your camera and then use the eosutility from my post)
Copied the firmware.fir to the card before flashing it from eosutility
Things to try if it still dont work:
***Go to Device Manager by pressing WindowsKey+R and typing devmgmt.msc
Expand the Portable Devices tree and Disable all of them except Canon EOS 7d by right-click - Disable***
Reset your camera to factory settings
Run eosutility in windows 7/vista/xp mode, or as Administrator
Format the CF before trying everything, from the camera
Tell me if nothing helps so i will upload the full cd from where i got the eosutility.
Thank you britom. It works with me. Win 7/32 bits
Quote from: britom on August 03, 2013, 02:33:30 AM
I'll try to help, my instructions worked on my pc with windows 8 x64 and some people tried in windows 7 without problems so please make sure:
Camera dial is set M mode
Battery is charged
You have the proper drivers (install the cd that came with your camera and then use the eosutility from my post)
Copied the firmware.fir to the card before flashing it from eosutility
Things to try if it still dont work:
***Go to Device Manager by pressing WindowsKey+R and typing devmgmt.msc
Expand the Portable Devices tree and Disable all of them except Canon EOS 7d by right-click - Disable***
Reset your camera to factory settings
Run eosutility in windows 7/vista/xp mode, or as Administrator
Format the CF before trying everything, from the camera
Tell me if nothing helps so i will upload the full cd from where i got the eosutility.
tried everything. no succsess.
i have to flash the patched firmware file from my harddrive and not from the cf-card where i copied it to, right?
Quote from: britom on August 03, 2013, 02:33:30 AM
I'll try to help, my instructions worked on my pc with windows 8 x64 and some people tried in windows 7 without problems so please make sure:
Camera dial is set M mode
Battery is charged
You have the proper drivers (install the cd that came with your camera and then use the eosutility from my post)
Copied the firmware.fir to the card before flashing it from eosutility
Things to try if it still dont work:
***Go to Device Manager by pressing WindowsKey+R and typing devmgmt.msc
Expand the Portable Devices tree and Disable all of them except Canon EOS 7d by right-click - Disable***
Reset your camera to factory settings
Run eosutility in windows 7/vista/xp mode, or as Administrator
Format the CF before trying everything, from the camera
Tell me if nothing helps so i will upload the full cd from where i got the eosutility.
Can you please answer the following question.
When you select the firmware.fir after in the EOSUtility and hit OK another windows comes up saying something about hitting SET and not touching any buttons right?
At that moment in the top of EOSUtility in RED Letters it says Lost connection.
7D goes into Initializing firmware update then in goes black and turns back on
On the card I am left with capital letters now FIRMARE.FIR and 3 more files.
When I delete those or format the card and place ML folder with autoexec in the root and boot 7d nothing happens.
I think it never gets flagged
I have done everything in M mode out of Live View , reset 7d to factory settings, ran EOS utility in different compatibility modes from XP to vista to whatnot in Admin mode.
I guess its the drivers then or I am stupid! :)
Exactly man, you have 2 copies of the firmware.fir file, one in the card, the other one on your hard drive. So the firmware "downgrade" process is with your cf card inside the camera, with the fir file in it.
Dont worry because it wont downgrade to 1.2.3 :)
Quote from: britom on August 03, 2013, 02:54:17 AM
Exactly man, you have 2 copies of the firmware.fir file, one in the card, the other one on your hard drive. So the firmware "downgrade" process is with your cf card inside the camera, with the fir file in it.
Dont worry because it wont downgrade to 1.2.3 :)
I select from the hard drive the patched one thats right from CF cant be selected anyhow... the problem is lost connection i guess or battery not fully charged _
does your EOS utility says LOST CONNECTION IN RED _
Quote from: Haruki on August 03, 2013, 02:49:21 AM
tried everything. no succsess.
i have to flash the patched firmware file from my harddrive and not from the cf-card where i copied it to, right?
I guess so thats what I am doing you can not select from CF card I have tried that to see if I am doing it wrong. I guess we never get to the process of booting the .fir firmware because our EOSUtility gets disconnected at the process of initialization...... then the camera goes into recycle without anything being done to the CF fir file
@britom
I have download and replace the new nightly files from Pelican. What is the dference from the old files? ...and how you manage to record the raw video ???
Tell me if nothing helps so i will upload the full cd from where i got the eosutility.
[/quote]
If u can upload the full cd maybe that is the issue but I am not sure..... I am fully charging my battery maybe it does not accept half full?
Quote from: edingacic on August 03, 2013, 03:01:45 AM
I guess so thats what I am doing you can not select from CF card I have tried that to see if I am doing it wrong. I guess we never get to the process of booting the .fir firmware because our EOSUtility gets disconnected at the process of initialization...... then the camera goes into recycle without anything being done to the CF fir file
exactly. so what could be the problem? drivers? i have all eos stuff installed...maybe some driver needs to be an old one?
Quote from: Haruki on August 03, 2013, 03:07:50 AM
exactly. so what could be the problem? drivers? i have all eos stuff installed...maybe some driver needs to be an old one?
maybe I think its that or I need to fully charge the bat. I am not sure man EOS Utility even on Mac is acting strange in old version with new updates.... i guess its the drivers or something.
It will accept with half charge. But try to install the EOSUtility from the CD and then run the EOSUtility from the link of britom( the old version of EOSUtility.
Quote from: arrinkiiii on August 03, 2013, 03:09:42 AM
It will accept with half charge. But try to install the EOSUtility from the CD and then run the EOSUtility from the link of britom( the old version of EOSUtility.
I even did that but I will do it again ... it recognizes 7d just fine everything works like expected until the last OK button is hit before the update after selection .fir from hard drive. Then it says that the connection is lost.... i even try different usb cables LOL hehehe ....
Quote from: edingacic on August 03, 2013, 03:11:39 AM
I even did that but I will do it again ... it recognizes 7d just fine everything works like expected until the last OK button is hit before the update after selection .fir from hard drive. Then it says that the connection is lost.... i even try different usb cables LOL hehehe ....
From now i don't know what to say more, im sorry. Try all the steps in a windows computer friend for see if it works :'(
With the new files from pelican wend i turn the camera on show up the message "scripts dir missing"
Tried this on two different computers, XP-32 laptop and Win 7-64 desktop. Both have the same results, connection lost no ML.
Grasping at straws - could it be the date of manufacture? Found this list and mine was made in Sept 2011 -
Date First 2 digits of serial #
Sep 09 01
Oct 09 02
Nov 09 03
Dec 09 04
Jan 10 05
Feb 10 06
Mar 10 07
Apr 10 08
May 10 09
Jun 10 10
Jul 10 11
Aug 10 12
Sep 10 13
Oct 10 14
Nov 10 15
Dec 10 16
Jan 11 17
Feb 11 18
Mar 11 19
Apr 11 20
May 11 21
Jun 11 22
Jul 11 23
Aug 11 24
Sep 11 25
Oct 11 26
Nov 11 27
Dec 11 28
Jan 12 29
etc etc
Quote from: themichael on August 03, 2013, 03:34:28 AM
Tried this on two different computers, XP-32 laptop and Win 7-64 desktop. Both have the same results, connection lost no ML.
Grasping at straws - could it be the date of manufacture? Found this list and mine was made in Sept 2011 -
Date First 2 digits of serial #
Sep 09 01
Oct 09 02
Nov 09 03
Dec 09 04
Jan 10 05
Feb 10 06
Mar 10 07
Apr 10 08
May 10 09
Jun 10 10
Jul 10 11
Aug 10 12
Sep 10 13
Oct 10 14
Nov 10 15
Dec 10 16
Jan 11 17
Feb 11 18
Mar 11 19
Apr 11 20
May 11 21
Jun 11 22
Jul 11 23
Aug 11 24
Sep 11 25
Oct 11 26
Nov 11 27
Dec 11 28
Jan 12 29
etc etc
my is 05 lost connection problem
@britom
I went to "shoot" menu and pick up Burst in the Silent Picture sub-menu. Then in Lv i half-press the shutter button and he start to record... I go to the cf card and he record some DNG files. This is the right process? How you put together the DNG files in a movie file?
new edit:
Now i went to the Shoot menu and chose Burst, End trigger. Press haf-shutter button and he make the magic. Wend i stop press the shutter button he start to record to the card, then i see in the camera screen that he is recording/save to the card the DNG files.
-beautiful-
How i can make a movie file with this dng's files?
You don't bud. The DNG's are your "movie file", each one a frame of video. Copy them to a folder and then import them into something like After Effects as raw sequence. Once things have developed further you will hopefully have "raw video files" on the camera instead of individual DNG's but this is the first step towards that 8)
Quote from: noisyboy on August 03, 2013, 03:59:16 AM
You don't bud. The DNG's are your "movie file", each one a frame of video. Copy them to a folder and then import them into something like After Effects as raw sequence. Once things have developed further you will hopefully have "raw video files" on the camera instead of individual DNG's but this is the first step towards that 8)
AHUUUUUUUUUUUUUUU =DDD
I know my friend, just giving some info for the next ML fanatics get here ;D
-I will try tomorrow to put the DNG's in AE to see if i can come with a video file ::)
-With burst picture it gives me 41 raw dng continuos pictures
-Go to after effects and:
Menu, Import, File
Chose the first dng file
He open the rawcamera, for make some ajustmans in the raw files
He make sequence in the time line of the dng pictures
Export as a movie file
*wend it open the rawcamera in after effects, in the botton it says 8bits, is this correct?
Quote from: edingacic on August 03, 2013, 03:09:16 AM
maybe I think its that or I need to fully charge the bat. I am not sure man EOS Utility even on Mac is acting strange in old version with new updates.... i guess its the drivers or something.
or maybe its the cf-card? i'm using a 32gb sandisk extreme.
Quote from: Haruki on August 03, 2013, 04:33:39 AM
or maybe its the cf-card? i'm using a 32gb sandisk extreme.
For this task almost any cf card is good. For raw video it will be the best that the market can offer you.
My card is a Sandisk 60MB/s 8GB
*wend i hit the info button in the camera with the ML, its say that cant found the help files, any solution for this?
Quote from: themichael on August 02, 2013, 10:43:20 PM
Sorry, I wasn't clearer. The three ROM bin files are after the update in the camera.
If you have the three ROM bin files this means the bootflag in camera was successfully set.
Quote
EOScard 1.36 crashed on two computers (Win7 and XP) even if nothing is clicked.
Will try once more with all new downloads.
**EDIT: Still no joy. The autoexec.bin goes in the root corrct? I am using a 16MB 133x card. Somebody have a checksum for the generated firmware file?
Copying the autoexec.bin and ML folder is not enough, you have to use the EOScard tool to enable the bootflag on the CF card. Even with the bootflag enabled in camera using the patched firmware, it will only boot the CF card if that too is marked for boot.
Excuse me, how can I start taking silent pics?? I downlaoded Pelican's nightly build.. but I can't seem to find the option.. @britom, how did you manage to get it working?? I need to know the bascis to start testing...
Thanks!!!
Quote from: tonybeccar on August 03, 2013, 07:15:34 AM
Excuse me, how can I start taking silent pics?? I downlaoded Pelican's nightly build.. but I can't seem to find the option.. @britom, how did you manage to get it working?? I need to know the bascis to start testing...
Thanks!!!
Nevermind, found it.. anyway.. @Pelican.. you'll be keeping up with the nightly builds then??
MAN I feel like a fool.. What is the M TAB?? "All" I got is Audio, Expo, Overlay, Movie, Shoot, Focus, Display, Prefs, Debug and Help. And The auto boot in to ML still doesn't work.. and yes I have ML folder and autoexec.bin in root on my CF card.
Quote from: arrinkiiii on August 03, 2013, 02:36:49 AM
Than after the first boot of the camera it create the "DCIM" and "MISC" right? YES
BTW I dont see the dual ISO stuff in the ML menu If you see the ML menu is because you have able to do the bootflag and run the new ML.
Sooo... For activate the dual iso you go to the M TAB. Activat the dual iso module and then go to the Expose Module and chose the dual iso and the iso itself.
AAAH.. there is my problem.. Now all I need is to get EOScard to work.. I get that damn error.. :-/
Quote from: pfluger on August 03, 2013, 06:20:38 AM
If you have the three ROM bin files this means the bootflag in camera was successfully set.
Copying the autoexec.bin and ML folder is not enough, you have to use the EOScard tool to enable the bootflag on the CF card. Even with the bootflag enabled in camera using the patched firmware, it will only boot the CF card if that too is marked for boot.
Because there are quite a few people having issues with installing ML on the 7D I have made a new thread for it. Perhaps we can have people with issues get help there instead of cluttering this thread? I find quite often people ask for help that was provided 'three pages ago'. 37 pages to find the answer is a lot :)
Anyways, new thread is here (http://www.magiclantern.fm/forum/index.php?topic=7464). I know I'm new here, hopefully I'm not stepping on anyone's toes or anything, I just thought maybe if the skilled people were focused on working out the bugs instead of helping us noobs things might progress a little faster, and it might help organization to boot!
Additionally, is there a way to manually flag the card for autoboot without using EOScard?
jphansen, I know it sounds silly, but try formatting the CF card with your computer with a different file system, say NTFS, then format that same card with your camera, then try EOScard again.
For those who experience crashed EOScard:
What language (locale) settings do you use?
Even if EOScard crash you can download the necessary zip from http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip
but you need to prepare your card with something else.
Edit:
I've uploaded the previous version here: http://pel.hu/down/EOScard1.35.exe
I had no problems a week ago with EOScard 1.3.6. When i rename that same .exe and start it up, it crashes. If i rename it back to what it was before, no crash. I think perhaps its crashing when trying to download the files? Maybe something doesnt line up properly and it dies.
1.35 has no issues for me thus far.
I'm in Canada so Canadian / US english for the Locale in case it still matters.
**EDIT**
Well im a happy guy! v1.35 seems to make my CF-SD adapter work! Tried formating the card then using 1.36, no dice. Format and use 1.35, ML autoboots no problem. *happydance*
Hi!
Quote from: g3gg0 on December 24, 2012, 10:06:32 AM
i also tried to put fps override into this release, which also requires master and slave patching.
it works but after some time (approx. a minute or less) the picture freezed or was crappy.
and this makes the feature useless, so its disabled.
Are there any news about the fps override for 7D?
For me, it is the most useful feature here, as I shoot timelapses.
Thanks in advance
Quote from: Pelican on August 03, 2013, 10:16:05 AM
Edit:
I've uploaded the previous version here: http://pel.hu/down/EOScard1.35.exe
I finally I got ML to boot.
Turns out that the 'connection lost" message in eos-utility is no error. (someone should have mentioned that, as some people thought this was an error). EosCard1.36 always crashes for me. So I tried EosCard1.35.
After using EOScard1.35 i got a lot of files on my card (also .fir-files for other EOS-camera-models) and the camera wouldnt boot.
I had to pull the battery and copy the ML flies manually. After this ML boots up =)
But now the light keeps on blinking and blinking...whats that about? --> nevermind, I now disabled bad settings warning and everything seems normal. Time to start experimenting!
for the record: i think my error was due to the fact that i didnt know that the bootflag must be set in the camera (by firmware 'update') as well as the cf-card must be made bootable (with eos-card). from some posts it sounded the eosCard just copies the ml-files, but i does make your card bootable as well!
=) Thx again everyone! this is going to be a fun weekend!
Quote from: Pileot on August 03, 2013, 10:02:36 AM
Because there are quite a few people having issues with installing ML on the 7D I have made a new thread for it. Perhaps we can have people with issues get help there instead of cluttering this thread? I find quite often people ask for help that was provided 'three pages ago'. 37 pages to find the answer is a lot :)
Anyways, new thread is here (http://www.magiclantern.fm/forum/index.php?topic=7464). I know I'm new here, hopefully I'm not stepping on anyone's toes or anything, I just thought maybe if the skilled people were focused on working out the bugs instead of helping us noobs things might progress a little faster, and it might help organization to boot!
Additionally, is there a way to manually flag the card for autoboot without using EOScard?
jphansen, I know it sounds silly, but try formatting the CF card with your computer with a different file system, say NTFS, then format that same card with your camera, then try EOScard again.
Good one :D
EosCard1.35 working here also, thank you! And to pelican, I have the finnish language version of windows 7 (x64).
(Also I started to think the connection lost message in EOS Utility was due to some error. )
But now it boots to ML!!! YESSS!
BTW, is the card light supposed to be blinking all the time now that I have the newest ML running? Seems kinda weird..
And how about the beeb? Is this some developement thingy, or why does the camera beeb when switching between the shooting modes or when I turn the camera on. I can disable it from settings of course, but will this also disable the minute beeps with long exposures when shooting in nighttime? (That I kinda liked).
Everything now worked for me with Eoscard 1.35!!! sooooo happy :D
thank you all guys! if any further questions appear i´ll be glad to help out with my experiences of the procedure
time to mess around with my "new" camera ;)
@Pelican
Can you upload a zip file with the ETTR module?
YEAHHHHHH WORKING ISSUE WAS THE EOScard now with EOSCard 1.35 everything is working....
My first video with the raw silent picture continuous burst.
-I got a lot of moire, a lot! But wend i upload in youtube it just take out, almost all, of the moire.
-In the first second its show up a corrupt frame. Half pink, maybe because of the card?
-In the sky its also create a kind of a grid. But you can't see here because of the compression of youtube.
Link for the exported file from after effects. For see the heavy moire.
http://www.sendspace.com/file/8doe62
Quote from: arrinkiiii on August 03, 2013, 12:37:58 PM
@Pelican
Can you upload a zip file with the ETTR module?
Can someone explain to me what exactly ettr module is?
It's the opposite of ETTL ;)
http://lmgtfy.com/?q=ettr
two quick questions, i hope someone can help me out:
1) i cant find the silent burst mode for dng sequences.. do i need an additional module? if so, where do i get it? if not, how exactly do i take silent bursts?
2) dual iso works fine in camera, however, hos is the post processing supposed to work? do i need some kind of program? in ACR the highlights are all pink
thank you in advance :) :) :)
Quote from: jemabaris on August 03, 2013, 02:45:50 PM
2) dual iso works fine in camera, however, hos is the post processing supposed to work? do i need some kind of program? in ACR the highlights are all pink
You need to use cr2hdr.exe for the pictures
You get it from this post: http://www.magiclantern.fm/forum/index.php?topic=7139.0
For those who experienced crash with EOScard 1.36:
Please download the latest http://pel.hu/down/EOScard.exe try it and report if it's still crashing or not.
Thanks!
Quote from: Haruki on August 03, 2013, 02:54:35 PM
You need to use cr2hdr.exe for the pictures
You get it from this post: http://www.magiclantern.fm/forum/index.php?topic=7139.0
thank you Haruki!! :)
Quote from: Pelican on August 03, 2013, 03:04:48 PM
For those who experienced crash with EOScard 1.36:
Please download the latest http://pel.hu/down/EOScard.exe try it and report if it's still crashing or not.
Thanks!
Still the same error. application crashes seconds after opening. how exactly would we bennefit from that update, since 1.35 works just fine.
Quote from: jemabaris on August 03, 2013, 03:16:18 PM
Still the same error. application crashes seconds after opening. how exactly would we bennefit from that update, since 1.35 works just fine.
1.35 use the same zip that once downloaded (you will miss the newer versions or have to delete the zip manually from your tem folder)
1.36 checks the date of the downloaded zip and download it again if necessary.
The bug is in the conversion routine (date to string) probably cause the different locale settings
I have download the 5DII ETTR module from https://bitbucket.org/a_d_/magic-lantern/downloads (the first zip file), this is correct?
Also have the autoexpo.mo, it will work in the 7D?
I don't see on the shot menu, the silence shot option...
dual iso and file man modules run OK without err
Quote from: yavaro on August 03, 2013, 05:14:46 PM
I don't see on the shot menu, the silence shot option...
dual iso and file man modules run OK without err
Put your camera in video mode. Go to camera/photo symbol menu. If you don't find it you need to upgrade 2 files. This 2 files you can find here
http://www.magiclantern.fm/forum/index.php?topic=3974.msg63547#msg63547
But i think if you use the EOSCard from Pelican you dont need to ugrade this 2 files
Quote from: Pelican on August 03, 2013, 03:25:44 PM
1.35 use the same zip that once downloaded (you will miss the newer versions or have to delete the zip manually from your tem folder)
1.36 checks the date of the downloaded zip and download it again if necessary.
The bug is in the conversion routine (date to string) probably cause the different locale settings
When I get back home I will try the new version so what is the correct procedure now if we only work with 1.35 to get latest built? Can we replace the new files manually on CF card?
@arrinkiiii
Thank you with this new file it works!!!!
Thank you
Quote from: Pelican on August 03, 2013, 03:04:48 PM
For those who experienced crash with EOScard 1.36:
Please download the latest http://pel.hu/down/EOScard.exe try it and report if it's still crashing or not.
Thanks!
This version also crashes after a few seconds with the same Application Error.
Version 1.35 works perfectly.
Quote from: yavaro on August 03, 2013, 05:49:06 PM
@arrinkiiii
Thank you with this new file it works!!!!
Thank you
U welcome :D
Yes, you can past the files directely to the cf card, in the respective place.
For those who do not use Eoscard.exe
Don't make the same mistake as me : install the two files (.bin and .sym)on the CF card
Thierry
Make a couple of shots on EOSCard 1.36. After upgrading with 1.37 - err70 again. Where can I download 1.36 version?
Im sorry, but is it working only in a Av mode?
Quote from: Pelican on August 03, 2013, 03:25:44 PM
1.35 use the same zip that once downloaded (you will miss the newer versions or have to delete the zip manually from your tem folder)
1.36 checks the date of the downloaded zip and download it again if necessary.
The bug is in the conversion routine (date to string) probably cause the different locale settings
Crashed on me too. US Locale settings.
Btw, is there a way to save to video hacks settings? I want to save the GOP and Flush settings. Probably something in the config?
Quote from: arrinkiiii on August 03, 2013, 05:08:39 PM
I have download the 5DII ETTR module from https://bitbucket.org/a_d_/magic-lantern/downloads (the first zip file), this is correct?
Also have the autoexpo.mo, it will work in the 7D?
Does it work?
How can we start helping into developing Raw Video?
I did some silly tests with silent pics burst but will do a more serious one.. For now I did not get any pink frames.. but only 2 to 3 seconds of video.. I noticed some green "aberrations" on some borders of objects, I saw that this had happened in the development of raw video.
So, how can we get at the same level of development as other cameras? What do we need? Testers we have, do we have a dev? Someone to program??
If the code is already done, isn't just a matter of changing a few values to address the proper "properties" of the 7D? Asking from my complete ignorance..
Would love to help by testing, tell me how please!! :)
Cheers!
BTW: I have only 133x Transcend CF cards... (will buy the KB in the future.. 1000x or 600x given that is the 7D?)
I think I've found the bug.
Please try it and report if it is OK.
http://pel.hu/down/EOScard.exe
New nightly:
agic Lantern v2.3.NEXT.2013Aug03.7D203
Mercurial changeset: a8db5666a3dd (unified) tip
Built on 2013-08-03 21:01:55 by Pel@pelslaptop
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym
7D is the only camera where writing is faster than reading.
(http://a1ex.magiclantern.fm/bleeding-edge/raw/7D.png)
Quote from: Pelican on August 03, 2013, 11:07:39 PM
I think I've found the bug.
Please try it and report if it is OK.
http://pel.hu/down/EOScard.exe
1. How do we delete the temp files? Where does it store them
**EDIT** Found them C:\Users\YourNameHere\AppData\Local\Temp Folder is in there.
2. What if instead of checking the date and downloading if newer, have a button for deleting the temp files to force a recheck, and always have it download the latest file?
Always have the same file name (7Dbeta.zip for instance) and always upload updates with the same name so the app always pulls the latest file from the server reguardless if we have MM/DD/YY, YY/DD/MM, etc.
Quote from: a1ex on August 03, 2013, 11:23:44 PM
7D is the only camera where writing is faster than reading.
(http://a1ex.magiclantern.fm/bleeding-edge/raw/7D.png)
I have no problem with that, the faster the write speed the better :) Strange tho, will have to test later with mine see if I get similar results. What card are you using?
A1ex, can you please split this thread in order to close the discussion about alpha 2 and open a new, clean thread about the new configuration?
I still think that the new thread should be opened by Britom using the 1st post as repository for instructions and all the links we do need, updated every time something change... I think he deserve this.
Quote from: a1ex on August 03, 2013, 11:23:44 PM
7D is the only camera where writing is faster than reading.
(http://a1ex.magiclantern.fm/bleeding-edge/raw/7D.png)
(http://i.imgur.com/1Eit8Q7.gif)
Quote from: angelom on August 03, 2013, 11:36:18 PM
A1ex, can you please split this thread in order to close the discussion about alpha 2 and open a new, clean thread about the new configuration?
I still think that the new thread should be opened by Britom using the 1st post as repository for instructions and all the links we do need, updated every time something change... I think he deserve this.
I disagree. Until there's a proper subset of ML that works perfectly (probably including the Raw video) and the devs decide to release the next version of ML for 7D (Alpha 3 or Beta 1) the thread should be kept to minimal. We're still talking about alpha 2 here, albeit with autorun now. It's confusing enough to hunt different modules etc across different threads. We don't need a new one to complicate that further.
Quote from: Pelican on August 03, 2013, 11:07:39 PM
I think I've found the bug.
Please try it and report if it is OK.
http://pel.hu/down/EOScard.exe
Works perfectly!
Thanks! And thanks for the new build! :D
I too disagree in splitting the thread for now... I've put a new thread up for installing on the 7D and its been getting a good response from everyone, Im trying to keep it updated with the most common questions asked and keep that organized (it can be found here: http://www.magiclantern.fm/forum/index.php?topic=7464)
For now this thread has evolved to general development / testing for the 7D. What we could use probably is deleting the old threads asking the same questions over and over and perhaps in the front add info thats buried in piles of posts. A general cleanup, or one of the first posts updating links to the latest files as they are posted.
Quote from: Pelican on August 03, 2013, 11:07:39 PM
I think I've found the bug.
Please try it and report if it is OK.
http://pel.hu/down/EOScard.exe
Yes! This version also works with my version of Windows 8 Enterprise 64-bit.
Thank you very much Pelican!
And to add to Pileot's suggestions:
When rightclicked the ML icon there is room for two buttons; [Clear cache] and [Download files]
Quote from: Pileot on August 03, 2013, 11:30:57 PM
1. How do we delete the temp files? Where does it store them
**EDIT** Found them C:\Users\YourNameHere\AppData\Local\Temp Folder is in there.
2. What if instead of checking the date and downloading if newer, have a button for deleting the temp files to force a recheck, and always have it download the latest file?
Always have the same file name (7Dbeta.zip for instance) and always upload updates with the same name so the app always pulls the latest file from the server reguardless if we have MM/DD/YY, YY/DD/MM, etc.
1. You don't need to delete anything if the program works as planned.
2. Yeah, there are thousands of solutions but I've chosen this...
Have you tested it?
Edit:
I see others tested it and worked.
Thanks!
So far its working great! Updated the links to 1.38b in my other thread.
I did some quick tests in my garden with silent pics burst this afternoon. ;)
https://vimeo.com/71649487
Quote from: a1ex on August 03, 2013, 11:23:44 PM
7D is the only camera where writing is faster than reading.
(http://a1ex.magiclantern.fm/bleeding-edge/raw/7D.png)
Nice, it's a fast camera, should be better than the 5D Mark II, isn't?
Quote from: edwmotion on August 04, 2013, 12:31:27 AM
Nice, it's a fast camera, should be better than the 5D Mark II, isn't?
I think it's at least comparable to the 5DMkIII ...
Quote from: Pelican on August 03, 2013, 11:53:45 PM
1. You don't need to delete anything if the program works as planned.
2. Yeah, there are thousands of solutions but I've chosen this...
Have you tested it?
Edit:
I see others tested it and worked.
Thanks!
Working now :) EOScard does not crash anymore. Do we need to put new nightly builds in there or it is done for us with EOSCard from the download server
Quote from: feureau on August 03, 2013, 11:39:27 PM
I disagree. Until there's a proper subset of ML that works perfectly (probably including the Raw video) and the devs decide to release the next version of ML for 7D (Alpha 3 or Beta 1) the thread should be kept to minimal. We're still talking about alpha 2 here, albeit with autorun now. It's confusing enough to hunt different modules etc across different threads. We don't need a new one to complicate that further.
I disagree too, as we're talking about all but the alpha 2, at least referring to the last 6/7 pages.
Anyway, no problem...
Quote from: Pelican on August 03, 2013, 11:53:45 PM
Edit:
I see others tested it and worked.
Thanks!
You're welcome! Thanks for the eoscard and the nightlies :3
Thanks for the nightly build!!
One question.. as the new 7D firmware said it accepted UDMA 7 cards.. BUT it will treat it as UDMA 6... which CF card should I buy?? The 1000x or the 600x? It was never enough clear to me what they were doing with the speeds...
Thanks!
Quote from: tonybeccar on August 04, 2013, 05:58:28 AM
Thanks for the nightly build!!
One question.. as the new 7D firmware said it accepted UDMA 7 cards.. BUT it will treat it as UDMA 6... which CF card should I buy?? The 1000x or the 600x? It was never enough clear to me what they were doing with the speeds...
Thanks!
The faster is better even in 7D. If you want maximum speed you have to buy the fastest card.
It will not as fast as the card's max. speed but you will use all the power of the 7D...
Quote from: flofifull on August 04, 2013, 12:00:50 AM
I did some quick tests in my garden with silent pics burst this afternoon. ;)
https://vimeo.com/71649487
The SilentPic Mode is beautiful, knocking H.264 out, but only it stops after 1-2 seconds, I really hope to get the jpg output from LV back as the Alpha2 used to do, but couldn't find the setting everywhere I looked. May somebody show me the way?
hello all,
I have a problem with ml alpha 2 (original version from december) on my 7d.
When I have fresh installed ml all things work fine, I can play around with the settings an so on.
But some times (I can not reproduce the behavior at the moment), after I want to load ML, the display don't show "Firmware update program loading" anymore. The camera will now do nothing. Switch on/off, remove battery, nothing helps do bring me back a working camera.
Than I have to remove the battery and delete the config-file in the settings-folder. Now the original firmware will start again.
config-differences:
working config:
beta.warn = 0
menu.first = 11835118
battery.drain.rate.rev = 239
don't working config:
beta.warn = 4
menu.first = 9738990
battery.drain.rate.rev = 0
I use a CF-adapter for SDXC/SDHC-cards from DELOCK.
Anyone has an hint, what's the/my problem? Do I am the problem? Anybody else with this problem?
cu
baumrasen
There's another user with a problem while using a CF adapter, after he moved to a CF card no problem at all so it seems that CF adapters are not a good choice when used with ML.
August 4 build:
http://www.mediafire.com/?z4ogo4t7atb1zow
Ok I hate to do this, but I'm going to ask a Noob question that others have also asked, but answers have yet to be provided that can help me.
Where the heck is the Silent Burst Sub menu. Have looked through every menu under SHOOT, but can't find it. Have I got to enable something first or do I have to add an extra module, if so, where can I get it?
For info, I loaded ML onto my bootable 7D using Pelicans 1.38b EOSCard (August 3rd). Dual ISO and File manager modules load ok.
Quote from: inky38 on August 04, 2013, 04:38:00 PM
Ok I hate to do this, but I'm going to ask a Noob question that others have also asked, but answers have yet to be provided that can help me.
Where the heck is the Silent Burst Sub menu. Have looked through every menu under SHOOT, but can't find it. Have I got to enable something first or do I have to add an extra module, if so, where can I get it?
For info, I loaded ML onto my bootable 7D using Pelicans 1.38b EOSCard (August 3rd). Dual ISO and File manager modules load ok.
I already answered that question in the other thread, but here once again
"download the following two files:
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym (right klick and save link)
find those two files in the ML folder on your CF card and replace them.
you will find the burst in the "shoot" tab.
good luck"
Quote from: jemabaris on August 04, 2013, 04:49:17 PM
I already answered that question in the other thread, but here once again
"download the following two files:
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym (right klick and save link)
find those two files in the ML folder on your CF card and replace them.
actually, autoexec.bin goes to the root and not /ML
Quote from: Haruki on August 04, 2013, 04:53:16 PM
actually, autoexec.bin goes to the root and not /ML
I have never said that...
I wrote to replace the two files. for my understanding that means leaving them where they are, but maybe thats just me. :D
i just read what i wrote again and yes,you are right :D it´s not all that clear. my bad
Quote from: jemabaris on August 04, 2013, 04:49:17 PM
I already answered that question in the other thread, but here once again
"download the following two files:
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym (right klick and save link)
find those two files in the ML folder on your CF card and replace them.
you will find the burst in the "shoot" tab.
good luck"
Ah my bad. I assumed that the latest build retrieved using EOSCard.exe would have included that.
All working fine now
Cheers
hello again,
Quote from: angelom on August 04, 2013, 02:45:42 PM
There's another user with a problem while using a CF adapter, after he moved to a CF card no problem at all so it seems that CF adapters are not a good choice when used with ML.
OK, thanks. I will give it a try.
cu
baumrasen
Yep v. 1.38 works.. I love you guys.. Such a great job you guys do.. BTW.. love the new GUI :-)
i assume there is no way i can put those 2 files on my CF-Card with the 7D itself...?!?!
my Cardreader...just passed away..rip AARG(^^%$&&*(*(* >:( >:( >:(
I've made a new patch file which works with the same 1.1.0 fw but creates a 2.0.3 fw update so you can skip the EU part...
http://pel.hu/ML/booton.bsdiff
Use the same way as the previous patch.
Also I made another patch which disables the bootdisk flag on the 7D so your camera goes back to the 'normal' state when doesn't load autoexec.bin at every start
http://pel.hu/ML/bootoff.bsdiff
Quote from: Pelican on August 04, 2013, 07:33:28 PM
I've made a new patch file which works with the same 1.1.0 fw but creates a 2.0.3 fw update so you can skip the EU part...
http://pel.hu/down/bootpatch203
Use the same way as the previous patch.
what do you mean by skip the EU part?
Quote from: pit3k on August 03, 2013, 09:28:55 PM
Does it work?
The ETTR module just load fine, i turn it on in ML menu... then i didn't try anymore how to figurout ETTR works.
The module autoexpo module didn't able to load.
What is the big differences from the last nightlybuild (4 august)?
Quote from: arrinkiiii on August 04, 2013, 08:12:48 PM
The ETTR module just load fine, i turn it on in ML menu... then i didn't try anymore how to figurout ETTR works.
The module autoexpo module didn't able to load.
What is the big differences from the last nightlybuild (4 august)?
Nothing big. Just minor fix and typo.
Also, ETTR for anyone interested: http://www.mediafire.com/?wkbc2nwiz3p9g6r
Quote from: edingacic on August 04, 2013, 08:04:51 PM
what do you mean by skip the EU part?
You don't have to download, install, run EU just skip the whole thing.
EU = Eos Utility , as far as i understood pelican he build a version of the patched firmware which enables bootflag WITHOUT needing to push the update via eos utility.
I appreciate the work all the pros do here but sometimes I would like to see less use of (not commonly used) acronyms. There are newcomers out there who will not understand all these terms and it will take longer to explain them afterwards then doing it in more detail first.
Quote from: feureau on August 04, 2013, 08:46:11 PM
Nothing big. Just minor fix and typo.
Also, ETTR for anyone interested: http://www.mediafire.com/?wkbc2nwiz3p9g6r
Thanks! RGB Zebras work now, I wish I would have waited for I went out to test RAW in crop mode.
Quote from: feureau on August 04, 2013, 03:26:26 PM
August 4 build:
http://www.mediafire.com/?z4ogo4t7atb1zow
Thanks works great I used to have this scripts folder not found now it is fixed.
I've got Alpha 2 copied on my Compact Flash. How can I upgrade to this version?
Please could you explain steps to use it?
Thanks.
Quote from: Pelican on August 04, 2013, 09:00:19 PM
You don't have to download, install, run EU just skip the whole thing.
Did I get this right.. with these two patches I can make firmware "update" files for the 7D,
I can rename the files to for example "7D_203_booton.fir", and "7D_203_bootoff.fir", and with the firmware update function INSIDE my 7D, I can now switch the bootflag on and off without a computer? Can I have the two files on my card simultaneously to be able to do this switch on the go too?
Two question:
- Is there a way to use last firmware (with raw video) witohout enable autoboot?
- I've got Canon 2.0.3 firware installed...is this the correct procedure? http://www.magiclantern.fm/forum/index.php?topic=3974.800
- Once do it, which firmware is on my 7d? 1.2.3 or 2.0.3? Possible disable autoboot ML and use camera in normal mode with 2.0.3 firmware?
Thanks
Quote from: pre10dr on August 04, 2013, 09:35:32 PM
EU = Eos Utility , as far as i understood pelican he build a version of the patched firmware which enables bootflag WITHOUT needing to push the update via eos utility.
I appreciate the work all the pros do here but sometimes I would like to see less use of (not commonly used) acronyms. There are newcomers out there who will not understand all these terms and it will take longer to explain them afterwards then doing it in more detail first.
Sorry if im slightly slow on the comprehension here but basically what your saying is we make the firmware.fir file, put it on the SD card, then run EOScard (the latest one, 1.38b) and eoscard does everything from there, no need to update the camera firmware?
How does the camera bootflag get set?
You just have to patch the original 2.0.3 firmware with the files provided by pelican using the bspatch.exe utility from my guide. Then you put the .fir file in the cf card and select firmware update so we dont have to use EOS Utility anymore to patch the older 1.2.3 version of the patch.
The only thing this does is to enable the bootflag so you can load autoexec.bin version of Magic Lantern. Your camera will still run 2.0.3 firmware after this.
I can edit my original guide if anybody wants, but some guy made a more detailed guide in a new thread so he should update that one.
Quote from: flofifull on August 04, 2013, 12:00:50 AM
I did some quick tests in my garden with silent pics burst this afternoon. ;)
https://vimeo.com/71649487
Hi! Im new i the ML because i just found out that my 7D can do RAW video. What do I need to record a RAW files? I just try it but it recorded only some *.422 files and no RAW files. I'll be happy for any answer or ling to some answers :)
Quote from: britom on August 05, 2013, 12:32:47 AM
You just have to patch the original 2.0.3 firmware with the files provided by pelican using the bspatch.exe utility from my guide. Then you put the .fir file in the cf card and select firmware update so we dont have to use EOS Utility anymore to patch the older 1.2.3 version of the patch.
The only thing this does is to enable the bootflag so you can load autoexec.bin version of Magic Lantern. Your camera will still run 2.0.3 firmware after this.
I can edit my original guide if anybody wants, but some guy made a more detailed guide in a new thread so he should update that one.
So generate firmware.fir
put on card
in camera do firmware update
then use EOScard to get latest MagicLantern on your card OR download the files manually and place on card
missing anything?
Im "some guy" and wanna make sure im 100% clear on the steps before I try to advise people to do something different. Will have the other thread updated right away.
Can we change the steps so we generate the firmware.fir file, run EOScard, and THEN move firmware.fir onto the card? Then update the camera through firmware update in the camera menu? Or should we run the update before EOScard? (meaning we would have to plug the card from the computer to the camera to the computer and back to the camera agin)
That should do, but might be necesary to rename firmware.fir so the camera recognizes as a update. Or probably not, magic lantern alpha 2 is named magic.fir and it works.
Haha Sorry i didnt recognize you and thank you by the way.
I think the order can be changed, just keep in mind that the camera will read the autoexec.bin file only if the bootflag is enabled. I think is more practical like this: Patch firmware file > Prepare CF card (Copy firmware file and magic lantern) > Firmware update. Camera should turn on with ML. It should work but someone needs to try it first.
I tried a quick and dirty crop mode test today, I'm impressed with what I see so far and will experiment a little more with it.
How did you enable crop video? Is another module required? Can you give a more in depth description to the video you shot? What is the framerate? How is it possible to record more frames than the usual 41 in silent pic burst mode at an even higher resolution? Please share those infos :)
Quote from: jemabaris on August 05, 2013, 02:09:10 AM
How did you enable crop video? Is another module required? Can you give a more in depth description to the video you shot? What is the framerate? How is it possible to record more frames than the usual 41 in silent pic burst mode at an even higher resolution? Please share those infos :)
I think you have to zoom in 5X and then do the burst.. that's how you get in crop mode if I'm not mistaken..
I wonder what crop factor would that be in the 7D...
I shot it the same way that I would shoot on the 5D Mark III. To enable the crop mode you just hit the magnifying glass and viola, you have 1:1 video with no line skipping. The resolution that was coming out of the camera was 2520x1200 and I assume the frame rate is either 29.97 or 30, we won't be able to have 23.976 until we have FPS override. I was hitting a consistent 59 frames, it might be more than others because I'm running the Komputerbay 64 GB 1000x card. In playback I'm hitting almost 92 MB/s and only 58 MB/s in record mode. Jemabaris, have you tried benchmarking your card to see how it's performing?
I like the performance in crop mode, it is very clean and compares to the 5D Mark III when light properly, the 5D however looks a lot better in crop mode when you start increasing the iso. I'd be interested in trying some super 16 glass if the crop mode can cover it.
Here's a link to the video file I uploaded to Youtube. https://docs.google.com/file/d/0BxvjJuCko_vAeTBudWNJZ1lTZ1U/edit?usp=sharing
Quote from: tonybeccar on August 05, 2013, 02:20:02 AM
I think you have to zoom in 5X and then do the burst.. that's how you get in crop mode if I'm not mistaken..
I wonder what crop factor would that be in the 7D...
The full sensor size is 22.3mm x 14.9 mm and the resolution is 5184 x 3456. Full crop mode is 2520 x 1200 which would create a sensor size of 10.84mm x 5.17mm, I think. This would put the 7D as a slightly smaller sensor than the Blackmagic Pocket Camera, it'll be even smaller at 1080p. Otherwise it should work with Super 16 glass. This is of course is assuming that my math is correct, someone should probably check it for me. :)
Edit, it probably won't work with Super 16, forgot about the EF mount that's in the way.
Yes you are right in your math!! But, if you hit the magnifying glass ONCE, you get into 5X... that FULL 1:1 crop mode? I mean there is NO line skipping? If there is NO line skipping then you are right, but if there is some, then we're talking about a bigger sensor in that crop mode :D.
Downloading the full res video now!!! Simply cannot believe the quality that we are getting.. will try and test myself but got crappy cards.. 166x... :/
Cheers!
Quote from: crazyrunner33 on August 05, 2013, 02:40:01 AM
The full sensor size is 22.3mm x 14.9 mm and the resolution is 5184 x 3456. Full crop mode is 2520 x 1200 which would create a sensor size of 10.84mm x 5.17mm, I think. This would put the 7D as a slightly smaller sensor than the Blackmagic Pocket Camera, it'll be even smaller at 1080p. Otherwise it should work with Super 16 glass. This is of course is assuming that my math is correct, someone should probably check it for me. :)
Edit, it probably won't work with Super 16, forgot about the EF mount that's in the way.
You're right about the sensor size and super 16 and 1/1.2" lenses would be perfect. But i don't know, they might not focus properly because of the distance of the mount to the sensor and may need modification, also might be some problems with the mirrior of the camera. It would be nice if someone clarifies this.
Quote from: tonybeccar on August 05, 2013, 03:04:41 AM
Yes you are right in your math!! But, if you hit the magnifying glass ONCE, you get into 5X... that FULL 1:1 crop mode? I mean there is NO line skipping? If there is NO line skipping then you are right, but if there is some, then we're talking about a bigger sensor in that crop mode :D.
Downloading the full res video now!!! Simply cannot believe the quality that we are getting.. will try and test myself but got crappy cards.. 166x... :/
Cheers!
Keep in mind that is still H.264, just really high quality H.264. Here's a couple random DNG frames, try to look for any moire or aliasing on the rocks. You'll have to bring the exposure down a little on some of them since I tried to ETTR, but I didn't know how far I could go since I didn't have the RAW zebras at the time.
https://docs.google.com/file/d/0BxvjJuCko_vAeVNlRlZjYng1VFU/edit?usp=sharing
Quote from: britom on August 05, 2013, 03:13:01 AM
You're right about the sensor size and super 16 and 1/1.2" lenses would be perfect. But i don't know, they might not focus properly because of the distance of the mount to the sensor and may need modification, also might be some problems with the mirrior of the camera. It would be nice if someone clarifies this.
That's what I'm worried about, I wouldn't be afraid to mod the camera strictly for this since I would sell I was originally going to sell it for the Blackmagic. A speedbooster might also work if we can adapt one of the current ones to an EF mount.
I'm noticing a grid pattern in my DNGs... Anybody else noticing this?
Quote from: codypowers on August 05, 2013, 05:02:56 AM
I'm noticing a grid pattern in my DNGs... Anybody else noticing this?
Yes me too.. will try and upload some pictures when I get the time!
Quote from: codypowers on August 05, 2013, 05:02:56 AM
I'm noticing a grid pattern in my DNGs... Anybody else noticing this?
Try putting the sharpening to zero, ACR always pushes the sharpness amount to 25. Are you seeing this pattern when pixel peeping?
Clear some things about make an autoboot version:
1. Download bspatch.exe, make a work folder copy the bspatch.exe there.
2. Download original Canon fw 1.1.0 (http://pel.hu/down/eos7d110.exe) and put it to the work folder and run it. It will make a fw file (7d000110.fir)
3. Download the patch (http://pel.hu/ML/booton.bsdiff) to the same folder, open a command prompt, go to the folder and type: bspatch 7d000110.fir 7dbooton.fir booton.bsdiff
4. Copy the created 7dbooton.fir to your CF cards root folder and put the card to your camera.
5. Start the firmware upgrade on your camera. It will loading for a while then red led will be on for a few seconds (it saves the ROM.bins) and that's it, your bootdisk flag is ON now.
6. Use EOScard to make your card bootable and install ML files on it.
For disabling the bootdisk flag:
1. same as above
2. same as above
3. Download the patch (http://pel.hu/ML/bootoff.bsdiff) to the same folder, open a command prompt, go to the folder and type: bspatch 7d000110.fir 7dnoboot.fir bootoff.bsdiff
4. Copy the created 7dnoboot.fir to your CF cards root folder and put the card to your camera.
5. Start the firmware upgrade on your camera. It will loading for a while then red led will be on for a few seconds (it saves the ROM.bins) and that's it, your bootdisk flag is OFF now.
Don't put the 7dbooton.fir and 7dnoboot.fir together on your card because you cannot choose which will run.
Quote from: crazyrunner33 on August 05, 2013, 05:24:28 AM
Try putting the sharpening to zero, ACR always pushes the sharpness amount to 25. Are you seeing this pattern when pixel peeping?
Video in the 7D is done not just through line skipping but pixel binning as well according to the release information. This is what is responsible for the grid like pattern. You need the VAF-7D. If either of you were local to SoCal, I'd consider loaning it out to you as I own one.
Quote from: Digital Corpus on August 05, 2013, 08:27:01 AM
Video in the 7D is done not just through line skipping but pixel binning as well according to the release information. This is what is responsible for the grid like pattern. You need the VAF-7D. If either of you were local to SoCal, I'd consider loaning it out to you as I own one.
I do live in SoCal, and was considering purchasing one. It would be great to test drive one. How effective is it in the raw files?
Quote from: Pelican on August 05, 2013, 08:21:17 AM
Clear some things about make an autoboot version:
1. Download bspatch.exe, make a work folder copy the bspatch.exe there.
2. Download original Canon fw 1.1.0 (http://pel.hu/down/eos7d110.exe) and put it to the work folder and run it. It will make a fw file (7d000110.fir)
3. Download the patch (http://pel.hu/ML/booton.bsdiff) to the same folder, open a command prompt, go to the folder and type: bspatch 7d000110.fir 7dbooton.fir booton.bsdiff
4. Copy the created 7dbooton.fir to your CF cards root folder and put the card to your camera.
5. Start the firmware upgrade on your camera. It will loading for a while then red led will be on for a few seconds (it saves the ROM.bins) and that's it, your bootdisk flag is ON now.
6. Use EOScard to make your card bootable and install ML files on it.
For disabling the bootdisk flag:
1. same as above
2. same as above
3. Download the patch (http://pel.hu/ML/bootoff.bsdiff) to the same folder, open a command prompt, go to the folder and type: bspatch 7d000110.fir 7dnoboot.fir bootoff.bsdiff
4. Copy the created 7dnoboot.fir to your CF cards root folder and put the card to your camera.
5. Start the firmware upgrade on your camera. It will loading for a while then red led will be on for a few seconds (it saves the ROM.bins) and that's it, your bootdisk flag is OFF now.
Don't put the 7dbooton.fir and 7dnoboot.fir together on your card because you cannot choose which will run.
I think this should be updated to the first post lest it gets buried in the pages.
Quote from: feureau on August 05, 2013, 11:24:58 AM
I think this should be updated to the first post lest it gets buried in the pages.
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Awesome. Thank you
A question...but in crop mode, with zoom 5x, how do you see the right video framing?
For now, you can see it by taking a few test pictures. You should be able to see them with the pic_view module (if it's not included, grab it from the regular nightly builds). Make sure you also have the file_man module.
There's a grayscale preview in raw_rec. Reminder: it's your job to port it, not mine ;)
Quote from: a1ex on August 05, 2013, 01:56:06 PM
For now, you can see it by taking a few test pictures. You should be able to see them with the pic_view module (if it's not included, grab it from the regular nightly builds). Make sure you also have the file_man module.
There's a grayscale preview in raw_rec. Reminder: it's your job to port it, not mine ;)
Wonderful :D
I have a problem, when used cr2hdr.exe (or cr2hdr_exp.exe)
"Doesn't look like interlaced ISO"
1) I load module
2) I use file from this msg
Quote from: Pelican on August 03, 2013, 11:16:08 PM
New nightly:
agic Lantern v2.3.NEXT.2013Aug03.7D203
Mercurial changeset: a8db5666a3dd (unified) tip
Built on 2013-08-03 21:01:55 by Pel@pelslaptop
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym
cr2 file: http://yadi.sk/d/5AA94pfJ7aIeN
Quote from: Sairon on August 05, 2013, 02:55:18 PM
I have a problem, when used cr2hdr.exe (or cr2hdr_exp.exe)
http://www.magiclantern.fm/forum/index.php?topic=7139.msg64337#msg64337
I can't find pic_view module, is there a download direct link?
Thanks.
Quote from: Audionut on August 05, 2013, 03:10:23 PM
http://www.magiclantern.fm/forum/index.php?topic=7139.msg64337#msg64337
I did it...Not work...(((
Quote from: a1ex on August 05, 2013, 01:56:06 PM
There's a grayscale preview in raw_rec. Reminder: it's your job to port it, not mine ;)
Speaking of which, is anyone working on a port?
If not, can anyone point me to the docs or some sort of pointer to do some sort of porting? Looking at bitbucket it seems there's only one version of the module whereas, there's supposed to be several versions for each camera?
Thanks
Quote from: Sairon on August 05, 2013, 03:25:35 PM
I did it...Not work...(((
what exactly did not work?
That CR2 is not a dual ISO picture, it's a regular picture. Try Photoshop or dcraw ;)
For porting raw_rec, just look at how the others did for 50D, 550D, 60D and pretty much all other cameras except 5D3.
@A1ex
I load the pic_view module and wend i press the play/review button its just show up the message "NO IMAGE", after i use the silent picture.
And the ETTR module wend i use its just put some artifacts (grey blocks) in the shadows... its this behavior normal?
Quote from: danistuta on August 05, 2013, 03:22:34 PM
I can't find pic_view module, is there a download direct link?
Thanks.
I have download this module here:
http://nanomad.magiclantern.fm/nightly/archive/ In side of the first folder.
Hello
Is the file manager working?
What kind of artifacts are you getting? Zebras?
Quote from: mmughal on August 05, 2013, 03:45:54 PM
Hello
http://www.magiclantern.fm/forum/index.php?board=29.0
Quote from: a1ex on August 05, 2013, 03:50:15 PM
Is the file manager working?
Yes, its load fine with no problem. If its real work? Never try it, but it loads fine.
What kind of artifacts are you getting? Zebras?
-Yes, its load fine with no problem. If its real work? Never try it, but it loads fine.
No zebras (red lines), were is dark in the scene it's just show up this kind of grey blocks. Im going take a photograph and post here.
I believe the "artifacts" you are talking about are just the zebras, which is normal.
The problem im comming across though is, that ettr measuring sometimes just wont really work. I have set it to be on the "set" button and when i press it the mirror goes up and back down again immediately. pressing and holding the set button then often does the trick.
in average it works like every second or third try. After the mirror snaps back up, take a normal photo and it will be exposed to the right.
Quote from: jemabaris on August 05, 2013, 04:10:23 PM
I believe the "artifacts" you are talking about are just the zebras, which is normal.
The problem im comming across though is, that ettr measuring sometimes just wont really work. I have set it to be on the "set" button and when i press it the mirror goes up and back down again immediately. pressing and holding the set button then often does the trick.
in average it works like every second or third try. After the mirror snaps back up, take a normal photo and it will be exposed to the right.
Thank you. I think is that, what you say. The grey squares is the zebras of ETTR, but it's for the underexpose... for the overexpose it's give me from green (lines) to other colors, but just in the overexpose/highlights.
Quote from: a1ex on August 05, 2013, 03:50:15 PM
Is the file manager working?
What kind of artifacts are you getting? Zebras?
I noticed the file manager was not working on the August 4th build, but it worked on the August 3rd build. I'll try reinstalling later today in case if it was an issue on my part.
Please crazyrunner33, after re-install to the 3 august version report were for see if its that. Thank you :D
Quote from: a1ex on August 05, 2013, 03:35:20 PM
That CR2 is not a dual ISO picture, it's a regular picture. Try Photoshop or dcraw ;)
Why is that rc2 not a dual ISO?
Module was running.
And enable in expomenu(+/-)
I don't know, it's your job to find out.
:( I'd help if i had the skills but i suck at programming.
@Sairon: Is your problem reproduceable or not?
If so: Please describe the steps you took to reproduce the problem.
Ciao, Walter
Quote from: britom on August 05, 2013, 06:24:01 PM
:( I'd help if i had the skills but i suck at programming.
...and i just know Pascal programming language (very, very time along ago). I also want to help more :-[
my first little test on the silent pic burst.
i uploaded it to vimeo first, but since the 720p limitation really screws up the sharpness i reuploaded it to youtube.
i love the gradeability and the sharpness. moire and aliasing can be serious issues in some shots though.
i tested both the regular and the crop (x5) mode.
https://vimeo.com/groups/raw/videos/71744783
http://youtu.be/e8G_1lA2SGg
enjoy ;)
Good day! Please tell me how to include shooting mode RAW. Updated the firmware, there is only the possibility of installing a high bit rate ... I was also interested in the same opportunity to shoot in silent picture. Thank you!
Quote from: Serdcelov on August 05, 2013, 08:29:31 PM
Good day! Please tell me how to include shooting mode RAW. Updated the firmware, there is only the possibility of installing a high bit rate ... I was also interested in the same opportunity to shoot in silent picture. Thank you!
Dont get me wrong, but I´m explaining this for the third or fourth time now. If you would have read to at least a few pages in this thread you would have known how to. But here, once again, just for you ;)
"download the following two files:
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym (right klick and save link)
find those two files in the ML folder on your CF card and replace them.
you will find the burst in the "shoot" tab.
good luck"
Thank you very much !!!!
Files replaced, click video capture is not possible to record in RAW. Silent picture works.
@Serdcelov
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Found this in the forum
(Auto) ETTR (Exposure to the Right): -- History & Beginners Guide
http://www.magiclantern.fm/forum/index.php?topic=5693.0
Quote from: Walter Schulz on August 05, 2013, 06:34:37 PM
@Sairon: Is your problem reproduceable or not?
If so: Please describe the steps you took to reproduce the problem.
Ciao, Walter
all work...
I don't know why it not work in the day...
I read the link several times already, I need a module for the raw video, I have it I can not find in the settings of the firmware as I understand it, without this module, shooting in raw materials is not possible, please share the link on the Raw unit.
If someone wanted to post a list of the most recent modules I'll add them to the other thread (read 1600 times holy crap!)
I don't use ML for video, focus peak is the thing I use the most, but since i'ts being asked for quite a lot I figure I might as well link em in the other thread.
Sorry for asking this, but for the love of god, I couldn't find it in this thread, so I hope you don't mind asking...it's confusing...to say the least.
So: At the moment: What is possible with the 7D? Are there any other Versions than alpha 2? And if so, how can I install them? Or is the talk going on the last couple weeks only for autobooting the firmware?
Thanks in advance!
-A noob in this field.
Yeeeeh
I find a problem, why raw not made dualISO
dualISO raw not made, if you shot when LiveView zoom (x5 or x10) turned...
Quote from: NessD on August 05, 2013, 09:34:01 PM
So: At the moment: What is possible with the 7D? Are there any other Versions than alpha 2? And if so, how can I install them? Or is the talk going on the last couple weeks only for autobooting the firmware?
Lots of talk that I dont fully understand, lots of raw video type stuff, general development of functions. HDR, dual ISOs, lots of fun stuff. Basically, every function of MagicLantern is being tested and made to work as it should. Its cool to watch it happen right in front of me :) Use EOScard from Pelican, from what I understand it downloads the latest files and applies them to your CF card. Not always 100% solid but it is beta so you can expect a few bugs.
I always suggest reading the last 10 pages in this thread, usually theres a link to the latest files somewhere in that 10 pages.
http://pel.hu/down/EOScard.exe
Quote from: Serdcelov on August 05, 2013, 09:23:03 PM
I read the link several times already, I need a module for the raw video, I have it I can not find in the settings of the firmware as I understand it, without this module, shooting in raw materials is not possible, please share the link on the Raw unit.
Read the manual. It will explain all functions. You were already provided links to the files you need in your last post.
When you shoot in crop mode, how do you see the correct framing in liveview, if it 5x? Is there a way to see correct view in LCD? Thanks.
Quote from: NessD on August 05, 2013, 09:34:01 PM
Sorry for asking this, but for the love of god, I couldn't find it in this thread, so I hope you don't mind asking...it's confusing...to say the least.
So: At the moment: What is possible with the 7D? Are there any other Versions than alpha 2? And if so, how can I install them? Or is the talk going on the last couple weeks only for autobooting the firmware?
Thanks in advance!
-A noob in this field.
Time for a little summary!!!
alpha 2 and what is being discussed here right now are not quite the same thing. Well basically it is the alpha 2, but with added features. The current release number is 2.0.3.
So why all the discussion about it?
A) this version added a big new feature: Silent picture, and especially silent picture burst mode... NO, not RAW video yet!!!!
BUT... this is the first step towards RAW video, as it also was with the 5D Mk III
and B) because a lot of people have had and still have trouble installing this version, because they (including myself) have and had a hard time getting the camera to boot from the CF card.
THIS PROCESS IS ALL COVERED HERE!!!
http://www.magiclantern.fm/forum/index.php?topic=7464.msg63820#msg63820
You will NOT have silent picture after that procedure! I have explained that in the same thread a few posts later. Please refer to that and don´t ask that anymore.
What else comes with this release?
Dual ISO is a part of it. the module is already onboard and works. See this thread for more information
http://www.magiclantern.fm/forum/index.php?topic=7139.0
Dot Tune AFMA is part of it. It´s an automated way of the AFMA Dot Tune method to fine tune your lenses autofocus.
Several other features from previous releases for other cameras are on board, like the follow focus, audio tags and many more, which have been around for a while, but not available for the 7D yet.
What does not come with this release but can be enabled through modules?
ETTR (expose to the right ) An automated, pretty food working way of exposing to your histograms right. link for this module:
http://www.mediafire.com/download/wkbc2nwiz3p9g6r/ettr.zip
Pic_view module: Im not to sure about this one, but i believe its a module to playback DNG frames which you have taken with silent picture and cant normally be viewed in Canons original picture playback function. (If im wrong with this one and if anyone´s got a link, let me know and i will update this post
Please keep in mind: I´m only a user and not a programmer of any kind. Everything I wrote here is how i understand it, but im pretty positive that i got everything more or less right.
I hope this helps you guys out there. good luck and a big thank you to the guys out there who are doing the real work (the devs)
Greets Jemabaris
https://vimeo.com/71755562
Here's a quick test, wanted to get a glimpse of what skin tones might look like, and try some high detail landscapes. I did get some pink frames every now and then, but in general, the 41 frames I could shoot at a time went smoothly. Thanks for all the work developing this, its coming along great. I can upload some DNGs if that is useful in any way.
Thank you all for hard work!
Amazing things happening here ;-)
Quote from: jemabaris on August 05, 2013, 09:54:57 PM
Greets Jemabaris
Thanks to you and pileot. Helped me a bunch!
Hi everyone , this is great news and got me really excited , was about to sell my 7D for the BMPC4k but this might make me keep my money
I have a question , from Florian's footage it seems that only the "1736 x 1156" resolution is supported so far , what about this impressive footage from our user "crazyrunner33" in 2.5K resolution , from what i read it has to do with "crop mode" , does this have any drawbacks , could RAW 2.5k be possible at some point ?
Great work everyone and the least i can do is support the team and perhaps use my own equipment to help test these features.
Best
Quote from: kh3naz on August 05, 2013, 11:34:24 PM
Hi everyone , this is great news and got me really excited , was about to sell my 7D for the BMPC4k but this might make me keep my money
I have a question , from Florian's footage it seems that only the "1736 x 1156" resolution is supported so far , what about this impressive footage from our user "crazyrunner33" in 2.5K resolution , from what i read it has to do with "crop mode" , does this have any drawbacks , could RAW 2.5k be possible at some point ?
Great work everyone and the least i can do is support the team and perhaps use my own equipment to help test these features.
Best
The drawbacks are that you cant frame it properly (at this point). As far as i understand, 2.5k will never be available in coninuous 24 fps, because write speeds just won´t be enough.
Hey dudes! Was gonna split this thread as it's all getting a bit all over the place in here but it's so all over the place it's gonna be a pain to split so for now I have started a new thread here (http://www.magiclantern.fm/forum/index.php?topic=7503.new#new) which you can continue the discussion of getting started and shooting raw on your lovely 7D :)
This thread should now continue to be used for general 7D development discussion.
If you wish to find more info on installing then Pileot has started a nice little guide to help get you started here:
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Any assistance in (politely) directing people to the new thread would be appreciated.
Cheers 8)
Edit: Updated with correct link :P
Quote from: noisyboy on August 05, 2013, 11:57:10 PM
Hey dudes! Was gonna split this thread as it's all getting a bit all over the place in here but it's so all over the place it's gonna be a pain to split so for now I have started a new thread here (http://www.magiclantern.fm/forum/index.php?topic=7503.new#new) which you can continue the discussion of getting started and shooting raw on your lovely 7D :)
This thread should now continue to be used for general 7D development discussion.
If you wish to find more info on installing then Pileot has started a nice little guide to help get you started here:
http://www.magiclantern.fm/forum/index.php?topic=7503.new#new
Any assistance in (politely) directing people to the new thread would be appreciated.
Cheers 8)
Hello noisyboy, both links point to your thread, the 2nd link should point to Pileot's one?
Quote from: angelom on August 06, 2013, 01:05:50 AM
Hello noisyboy, both links point to your thread, the 2nd link should point to Pileot's one?
Well spotted that man (or woman) 8)
Corrected.
i installed ML via the tutorial perfectly easy on my 7D. yay!
question now - what's in, what's not? as for photo as for video. can anybody make a list of what's still to fix maybe? like FPS override which seems to be missing. haven't got that much time yesterday for testing, but it seems like the option for audio meters is missing now, too?
i'm a windows programmer by work, so maybe i can be of a little help. just give me pinch what's still to be found and i'll see if i can find a little time for hunting.. :)
Quote from: codypowers on August 05, 2013, 08:43:44 AM
I do live in SoCal, and was considering purchasing one. It would be great to test drive one. How effective is it in the raw files?
My presence here is just to follow where things are. I have an embedded solutions electronics project, day job, automotive work, and Life® that consume my time. As such I haven't had a chance to try RAW. Hit me up via a PM if you're serious about borrowing and we'll see what we can do.
Quote from: mburgst on August 06, 2013, 11:19:34 AM
i installed ML via the tutorial perfectly easy on my 7D. yay!
question now - what's in, what's not? as for photo as for video. can anybody make a list of what's still to fix maybe? like FPS override which seems to be missing. haven't got that much time yesterday for testing, but it seems like the option for audio meters is missing now, too?
i'm a windows programmer by work, so maybe i can be of a little help. just give me pinch what's still to be found and i'll see if i can find a little time for hunting.. :)
7D RAW THREAD
http://www.magiclantern.fm/forum/index.php?topic=7503.new#new
7D RAW MODULE DEVELOPMENT
http://www.magiclantern.fm/forum/index.php?topic=7508.0
Thank you dear team..i read all the posts from the first...and if i liked a ML version audionut,with dual iso and with raw video but not autobootable?
no raw video yet, as per previous messages.
Quote from: herrfox on August 06, 2013, 03:16:11 PM
Thank you dear team..i read all the posts from the first...and if i liked a ML version audionut,with dual iso and with raw video but not autobootable?
http://www.magiclantern.fm/forum/index.php?topic=7464.0
I have a bit of money to donate. Please link.
No, this is not a spam. I have owned the 7D since it came out and it's my to go camera over the 5D-II.
Quote from: Trey T on August 06, 2013, 07:17:23 PM
I have a bit of money to donate. Please link.
I think that the donations link are close, at least for now. But send a PM to a1ex and ask him.
7D RAW THREAD
http://www.magiclantern.fm/forum/index.php?topic=7503.new#new
7D RAW MODULE DEVELOPMENT
http://www.magiclantern.fm/forum/index.php?topic=7508.0
7D INSTALLING AND MAKE CAMERA BOOTABLE
http://www.magiclantern.fm/forum/index.php?topic=7464.0
..where have the audio-meters gone? can't find the option to switch them on in todays 7D build from audionut?
any chance to make the camera beep when recording starts? maybe be useful to sync others recorders/cams..
Quote from: arrinkiiii on August 06, 2013, 07:16:39 PM
http://www.magiclantern.fm/forum/index.php?topic=7464.0
I'm asking for a ml version with recent features but not bootable.
Quote from: herrfox on August 06, 2013, 07:36:07 PM
I'm asking for a ml version with recent features but not bootable.
You are not lucky, that version doesn't exists.
Quote from: jemabaris on August 05, 2013, 09:54:57 PM
THIS PROCESS IS ALL COVERED HERE!!!
http://www.magiclantern.fm/forum/index.php?topic=7464.msg63820#msg63820
You will NOT have silent picture after that procedure! I have explained that in the same thread a few posts later. Please refer to that and don´t ask that anymore.
Wait, isn't silent picture the same as the raw burst thingy but set to 1 shot?
Quote from: feureau on August 06, 2013, 08:55:34 PM
Wait, isn't silent picture the same as the raw burst thingy but set to 1 shot?
the burst IS silent picture. Silent picture can be set to different options such as; simple (one shot), burst (the thingy we are currently using to get 41 frames long "videos"), burst end trigger, best shots, and slit-Scan.
Test Canon 7D Raw - crop mode - Magic Lantern - Handheld + sharp + VSCO
http://vimeo.com/71834341
@ crop mode I only get 35 frames... not so fast card...
Quote from: yavaro on August 06, 2013, 09:00:15 PM
Test Canon 7D Raw - crop mode - Magic Lantern - Handheld + sharp + VSCO
http://vimeo.com/71834341
@ crop mode I only get 35 frames... not so fast card...
7D RAW THREAD http://www.magiclantern.fm/forum/index.php?topic=7503.new#new
7D RAW MODULE DEVELOPMENThttp://www.magiclantern.fm/forum/index.php?topic=7508.0
7D INSTALLING AND MAKE CAMERA BOOTABLE http://www.magiclantern.fm/forum/index.php?topic=7464.0
Quote from: jemabaris on August 06, 2013, 08:59:38 PM
the burst IS silent picture. Silent picture can be set to different options such as; simple (one shot), burst (the thingy we are currently using to get 41 frames long "videos"), burst end trigger, best shots, and slit-Scan.
I see. But that raw burst works. I think the guide should be updated to note that silent picture works.
Quote from: feureau on August 06, 2013, 10:50:21 PM
I see. But that raw burst works. I think the guide should be updated to note that silent picture works.
Which guide are you talking about? Plus I think that everyone knows that by now.
Hi Devs,
Was wondering about the frame flush and GOP parameters, under video hacks. Do they actually work? or do I need the build from the Halloween bitrate monster thread? ( http://www.magiclantern.fm/forum/index.php?topic=3404.100 ) I've been doing experiments and have read about the ISO-bitrate relationship and all that. I've read the threads and all but am wondering if it actually does anything. I am using VideoSpec to see the details but according to it the GOP is no different even when I change it. Further, I seem to get higher bitrate per ISO with it turned of all together.
Or is it only with VBR i get to see the diff?
And another thing, are nanomod's nightly builds for the 7D? I see in the change log pelican's update to 7d stubs.
Quote from: John Kesl on August 07, 2013, 04:49:47 AM
Hi Devs,
Was wondering about the frame flush and GOP parameters, under video hacks. Do they actually work? or do I need the build from the Halloween bitrate monster thread? ( http://www.magiclantern.fm/forum/index.php?topic=3404.100 ) I've been doing experiments and have read about the ISO-bitrate relationship and all that. I've read the threads and all but am wondering if it actually does anything. I am using VideoSpec to see the details but according to it the GOP is no different even when I change it. Further, I seem to get higher bitrate per ISO with it turned of all together.
Or is it only with VBR i get to see the diff?
bitrate hack works. Just make sure you know what you're doing. It can crash the camera needing battery pull.
Quote from: feureau on August 07, 2013, 07:38:27 AM
bitrate hack works. Just make sure you know what you're doing. It can crash the camera needing battery pull.
Yeah, I know the bitrate hack works. It's not what I'm taliking about. I'm talking about the GOP and frame dump hack.
Did you even read my post? Because you didn't answer my question. You seem to just make up some other question and answered that instead. Do you think you where being constructive? What exactly did you contribute by your answer? Did you even think about what you blurted out?
Quote from: mburgst on August 06, 2013, 07:22:11 PM
..where have the audio-meters gone? can't find the option to switch them on in todays 7D build from audionut?
any chance to make the camera beep when recording starts? maybe be useful to sync others recorders/cams..
noone knows?!
Quote from: mburgst on August 07, 2013, 08:19:39 AM
noone knows?!
Push record and you'll see em (make sure audios enabled in canon menu obviously). as far as the beep. still havent found it.
Hi Devs,
Was wondering about the frame flush and GOP parameters, under video hacks. Do they actually work? or do I need the build from the Halloween bitrate monster thread? ( http://www.magiclantern.fm/forum/index.php?topic=3404.100 ) I've been doing experiments and have read about the ISO-bitrate relationship and all that. I've read the threads and all but am wondering if it actually does anything. I am using VideoSpec to see the details but according to it the GOP is no different even when I change it. Further, I seem to get higher bitrate per ISO with it turned of all together.
Or is it only with VBR i get to see the diff?
And another thing, are nanomod's nightly builds for the 7D? I see in the change log pelican's update to 7d stubs.
Quote from: mburgst on August 07, 2013, 08:19:39 AM
noone knows?!
You could always clap loudly, it would register a sharp peak on the audio and you could sync that up with any cameras taking video...
Or use a flash and set it off, would easially show on all the video and you could sync the video to the white light and roll from there.
Quote from: John Kesl on August 07, 2013, 08:26:39 AM
Hi Devs,
Was wondering about the frame flush and GOP parameters, under video hacks. Do they actually work? or do I need the build from the Halloween bitrate monster thread? ( http://www.magiclantern.fm/forum/index.php?topic=3404.100 ) I've been doing experiments and have read about the ISO-bitrate relationship and all that. I've read the threads and all but am wondering if it actually does anything. I am using VideoSpec to see the details but according to it the GOP is no different even when I change it. Further, I seem to get higher bitrate per ISO with it turned of all together.
Or is it only with VBR i get to see the diff?
And another thing, are nanomod's nightly builds for the 7D? I see in the change log pelican's update to 7d stubs.
So to answer my own question. The Autoload version of the 7d alpha2 doesn't do the GOP or Frame Dump. I understand the push for RAW but I honestly think the ability to shoot all I frame is impressive as well, more impressive even than the 41 frame raw burst. That being said, I think that the 7D once unlocked will be quite a beast. Of particular interest here is the N=1 followed by no M meaning that I am shooting a 1 Frame GOP which is by definition an I Frame. Beautiful boys, beautiful.
And before anyone starts asking I am using the non Autoload version here. And of interest is that I have not removed the boot flag from my 7D so I can still load the autoload version, just thought you all would like to know.
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 324 MiB
Duration : 46s 129ms
Overall bit rate : 58.9 Mbps
Encoded date : UTC 2013-08-07 03:07:53
Tagged date : UTC 2013-08-07 03:07:53
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile :
[email protected]Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : N=1
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 46s 129ms
Bit rate : 58.9 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Original height : 1 088 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.184
Stream size : 324 MiB (100%)
Language : English
Encoded date : UTC 2013-08-07 03:07:53
Tagged date : UTC 2013-08-07 03:07:53
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.601
Quote from: John Kesl on August 07, 2013, 08:25:42 AM
Push record and you'll see em (make sure audios enabled in canon menu obviously). as far as the beep. still havent found it.
mhh, so the audio levels are only visible when actually recording, not all the time? would be easier to get the levels right before recording a clip..
Quote from: Pileot on August 07, 2013, 08:28:53 AM
You could always clap loudly, it would register a sharp peak on the audio and you could sync that up with any cameras taking video...
Or use a flash and set it off, would easially show on all the video and you could sync the video to the white light and roll from there.
used to clap and such, but i thought that beep feature should/could be used for that. okay, cam is not that loud enough for distanct mikes, but may be useable for onboard/onrig stuff..?
Quote from: feureau on August 07, 2013, 07:38:27 AM
bitrate hack works. Just make sure you know what you're doing. It can crash the camera needing battery pull.
Yes, indeed. Works like a charm, with the old and new version. ALL-I is good :D
Thank you.
Quote from: arrinkiiii on August 07, 2013, 11:26:06 AM
Yes, indeed. Works like a charm, with the old and new version. ALL-I is good :D
Thank you.
Really? How are you determining that you are actually shooting All-I on the autoload firmware? How do you know?
Quote from: John Kesl on August 07, 2013, 11:43:06 AM
Really? How are you determining that you are actually shooting All-I on the autoload firmware? How do you know?
I might be wrong, but this is how I try and determine which frames are I frames. I guess if it's all I frames each frame would come through.
ffprobe -show_packets -pretty yourmovie.mov | grep flag |grep -o -n "flags=K"
Quote from: John Kesl on August 07, 2013, 11:43:06 AM
Really? How are you determining that you are actually shooting All-I on the autoload firmware? How do you know?
able in the menu and if you are not pleased just compares with regular video
Quote from: arrinkiiii on August 07, 2013, 11:57:05 AM
able in the menu and if you are not pleased just compares with regular video
My God Really? Idiot. let me show you the difference, between All-I, and regular IPB.
This is regular IPB:
General
Complete name : /Users/johnkesl/Desktop/100EOS7D/MVI_0281.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 271 MiB
Duration : 41s 625ms
Overall bit rate : 54.7 Mbps
Encoded date : UTC 2013-08-06 21:04:49
Tagged date : UTC 2013-08-06 21:04:49
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile :
[email protected]Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=12
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 41s 625ms
Bit rate : 54.7 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Original height : 1 088 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.100
Stream size : 271 MiB (100%)
Language : English
Encoded date : UTC 2013-08-06 21:04:49
Tagged date : UTC 2013-08-06 21:04:49
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.601
This is All-I:
General
Complete name : /Users/johnkesl/Desktop/100EOS7D/MVI_0298.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 324 MiB
Duration : 46s 129ms
Overall bit rate : 58.9 Mbps
Encoded date : UTC 2013-08-07 03:07:53
Tagged date : UTC 2013-08-07 03:07:53
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile :
[email protected]Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : N=1
Codec ID : avc1
Codec ID/Info : Advanced Video Codaing
Duration : 46s 129ms
Bit rate : 58.9 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Original height : 1 088 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.184
Stream size : 324 MiB (100%)
Language : English
Encoded date : UTC 2013-08-07 03:07:53
Tagged date : UTC 2013-08-07 03:07:53
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.601
Look by GOP. That's the difference.
Now go google GOP.
Quote from: danmonaghan on August 07, 2013, 11:55:32 AM
I might be wrong, but this is how I try and determine which frames are I frames. I guess if it's all I frames each frame would come through.
ffprobe -show_packets -pretty yourmovie.mov | grep flag |grep -o -n "flags=K"
As far as that goes:
Format settings, GOP : M=1, N=12
So that answers that.
For the Developers:
Is it possible to implement the master digic hack for the GOP and Frame dump hacks in the autoload version of the 7D alpha2. I've tried all the autoload versions and the settings aren't affecting the actual .mov file like they are in the magic.fir version. In fact they don't work at all. I was wondering if it's intentional or if it can be enabled?
Thank you.
P.s. if you aren't a developer or a contributor please don't answer.
Quote from: John Kesl on August 07, 2013, 12:15:32 PM
My God Really? Idiot.
You don't need to speak about yourself like this. Go slow, for be quick.
nevermind.
Quote from: John Kesl on August 07, 2013, 12:26:46 PM
You are an Idiot. Sorry.
Dont be sorry im not for you.
For the Developers:
Is it possible to implement the master digic hack for the GOP and Frame dump hacks in the autoload version of the 7D alpha2. I've tried all the autoload versions and the settings aren't affecting the actual .mov file like they are in the magic.fir version. In fact they don't work at all. I was wondering if it's intentional or if it can be enabled?
Thank you.
Hi!
Am i missing something or the HDR Video is not yet impemented?
Quote from: oli4h on August 07, 2013, 02:53:31 PM
Hi!
Am i missing something or the HDR Video is not yet impemented?
Not yet... but with dual-iso and raw will be better then hdr video :D
Quote from: John Kesl on August 07, 2013, 12:21:50 PM
P.s. if you aren't a developer or a contributor please don't answer. I unlike many here know how to use the search function and also how to read forums, so please spare me the retarded answers.
Take it slow pal. You might know how to read them, but not how to act proper. Insulting other people isn´t quite this forums purpose.
With kind regards, Jemabaris
Quote from: jemabaris on August 07, 2013, 05:30:29 PM
Take it slow pal. You might know how to read them, but not how to act proper. Insulting other people isn´t quite this forums purpose.
With kind regards, Jemabaris
who did I insult?
Quote from: John Kesl on August 07, 2013, 05:41:36 PM
who did I insult?
In the first place Arrinkiiii and second, everyone except the devs, for describing our posts as retarded... But I think you know that ;)
Quote from: jemabaris on August 07, 2013, 05:43:22 PM
In the first place Arrinkiiii and second, everyone except the devs, for describing our posts as retarded... But I think you know that ;)
Have you read the answers that this person leaves? Do they seem like they answer any question I actually asked? Not just me actually, most people who are blessed an answer by this person. As a matter of fact there are many who post who don't do anything, but blurt out their question, or answer. I think it's insulting. And rude. To not read a post. To not use the search function. To not read the other Forum Posts before asking questions for the 40,000,000 time. To not take the time to construct a meaningful question. Or to take the time to actually answer. To show proof, Logs, anything to support conclusions. it's Lazy and it's rude. And if I insult those who are lazy, and rude. so be it.
Quote from: John Kesl on August 07, 2013, 05:47:55 PM
And if I insult those who are lazy, and rude. so be it.
Wow, that's a great way to contribute! (Sarcasm). Please man be polite, we're all just trying to help, there's no need to be an asshole.
Anyway, i just want to ask about the write speed. In the doc here https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5 says that the CF controller top writing speed is 80mb/s, but in this image http://a1ex.magiclantern.fm/bleeding-edge/raw/7D.png publishied by a1ex in a earlier post tops at 91mb/s.
So my question is, knowing that the top liveview res is 1728x1156, should i get a 1000x CF card? Will the extra transfer speed be worth it?
Thank you in advance :)
"
Quote from: John Kesl on August 07, 2013, 05:47:55 PM
And if I insult those who are lazy, and rude. so be it.
A) I aggree with you to some degree. BUT that does not mean that it justifies how you treat poeple. Calling someone an idiot does help just as much if not less than asking stuff over and over again.
B) As i mentioned before, it´s not only him who you insulted but basically 90% of the users here, by classifying their posts as "retarded".
You might consider thinking about what I said. That´s it from me.
with kind regards, Jemabaris
Quote from: jemabaris on August 07, 2013, 06:14:31 PM
B) As i mentioned before, it´s not only him who you insulted but basically 90% of the users here, by classifying their posts as "retarded".
You might consider thinking about what I said. That´s it from me.
I did think about it. and it seems you think 90% of the users are retarded, judging by your point B.
Who is insulting whom, I ask you?
maybe because the 90% of users here are not developers nor contributors, the only people that you seems to consider as per your original post.
Woah - it's getting a bit crazy in here! Time out 8)
Quote from: John Kesl on August 07, 2013, 06:23:17 PM
I did think about it. and it seems you think 90% of the users are retarded, judging by your point B.
Who is insulting whom, I ask you?
This isn't that kind of forum and yes you are being offensive. Bare in mind that it is the entire community that makes this work, not any individual.
Hi folks!
By using ML, each time I press on shutter a .dng which I can not open in photoshoo is written to the card.
WHat is it good for and how can I disable it??
THanks in advance for supporting and greeat job . just waiting for the HDR Video and I'll be 100% happy !!
wbr+
I wanted to know if it's possible to port the headphones function?? Also, what is necessary to port the remaining of ML functions to the 7D? Are there certain limitations? I don't understand about programming.. about the work that Pelican is doing.. what are 'stubs' for example??
Thanks!!
Quote from: oli4h on August 07, 2013, 09:54:55 PM
Hi folks!
By using ML, each time I press on shutter a .dng which I can not open in photoshoo is written to the card.
WHat is it good for and how can I disable it??
THanks in advance for supporting and greeat job . just waiting for the HDR Video and I'll be 100% happy !!
wbr+
For open try after effects
This DNG's are the beginning for raw video. With Silent Picture you can record almost 2 seconds of raw (dng files), then you can compile in after effects and export as one video, raw video.
For disable you need to go to the Shoot tab and disable Silent Picture
Dual-iso + raw video is better then hdr video. Dual-iso you already can make in your 7D (only photo).. now is waiting for the raw video (continuous raw and not small bursts (silent picture) .
Quote from: britom on August 07, 2013, 06:09:35 PM
Wow, that's a great way to contribute! (Sarcasm). Please man be polite, we're all just trying to help, there's no need to be an asshole.
Anyway, i just want to ask about the write speed. In the doc here https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5 says that the CF controller top writing speed is 80mb/s, but in this image http://a1ex.magiclantern.fm/bleeding-edge/raw/7D.png publishied by a1ex in a earlier post tops at 91mb/s.
So my question is, knowing that the top liveview res is 1728x1156, should i get a 1000x CF card? Will the extra transfer speed be worth it?
Thank you in advance :)
I feel that it's too soon to decide on that just yet, it would be better to wait and see what happens when we have the raw_rec module working and have more benchmarks posted. If we can achieve write speeds of over what the card controller is listed as in movie mode then I would highly recommend the 1000x card, especially since we can record up to 2520x1200 in the 1:1 crop mode.
Have you run a benchmark yet to see how your card is performing?
crazyrunner33 thanks a lot for your advice
@arrinkiiii : Ahhh..now I understand a bit better - but why a size of 1736*1156?
Quote from: oli4h on August 08, 2013, 10:11:01 AM@arrinkiiii : Ahhh..now I understand a bit better - but why a size of 1736*1156?
I asked the same question not long ago: http://www.magiclantern.fm/forum/index.php?topic=5494.msg49854#msg49854
Ciao, Walter
EDIT-DELETED
I put 3 august ML version...but normal bitrate control doesn't work anymore?!?
HI ALL,
I put ML Alpha2 and created ML/MODULES AND PUT ALL FILES GIVEN FOR DUSL ISO
PUT autoexec.bin in Root and started camera and installed firmware.
Unfortunately I dont get Load Modules Tab.
Any help I get working DUAL ISO would be so appreciated.
I am totally NooB.
If you had to *create* this folder you have either the wrong version or didn't follow the instructions or (sh*t happens) the installation went wrong. Do as advised here (http://www.magiclantern.fm/forum/index.php?topic=7553.msg65178#msg65178).
If done properly the folder exists after installation.
Ciao, Walter
thank you all seniors.
finally I got DUal ISO.
Made my first shot just test 200/1600
now need to process it.
When I connect turned on camera to computer, its always shows err70 (on info screen, thats located on upper part of the camera) and I cant use remote shooting throw EOS Utility. Can browse files on a card normally. If I push halfshutter, error is dissapear and all works fine. EOSCard 1.38.
Quote from: mityazabuben on August 08, 2013, 02:34:21 PM
When I connect turned on camera to computer, its always shows err70 (on info screen, thats located on upper part of the camera) and I cant use remote shooting throw EOS Utility. Can browse files on a card normally. If I push halfshutter, error is dissapear and all works fine. EOSCard 1.38.
This happen with me also but in the beginning of the new ML for the 7D, but only in camera 70error.
http://www.magiclantern.fm/forum/index.php?topic=7464.0
And upload with the last version.
Read this threat http://www.magiclantern.fm/forum/index.php?topic=7503.0 and you will find the latest version of the files for you update your CF/ML after using the latest EOSCard. Regarding the EOSUtility... i don't know.
Today observed Weird behavior by my 7D.
Last evning I fully charged battery and put in camera just made two three clicks and switch off the camera.
Just 5 minutes ago it didn't turned on and when I put the battery into charger it showed drain and started to charge from 0.
Anyone encountered such issue ?
Let me guess: You opened card door, too and did it very fast after turning the switch?
Then we have this issue (http://www.magiclantern.fm/forum/index.php?topic=1455.msg3943#msg3943) on 7D, too.
Ciao, Walter
It's not about how fast you open the card door, it's about how fast you remove the card after opening the door. When you open the door, the camera wakes up (even if it was turned off 2 hours ago).
Good to know this...
I always wait, then i remove the card. I never have this kind of thing happen with me but a estrange behavior i got wend i turn off the camera and the next day i turn on and the camera don't turn on, nothing... i remove the battery and put again. Everything load as should be.
Quote from: arrinkiiii on August 09, 2013, 11:32:19 AM
next day i turn on and the camera don't turn on, nothing... i remove the battery and put again. Everything load as should be.
Has happened to me too a few times too.
Quote from: Magic 7D on August 09, 2013, 04:50:03 PM
Has happened to me too a few times too.
Yes, same here.
Hi.
1) Can we use cropmode video?
2) my battery is discharge, when it insert in camera, But my camera is turn off. This happens only when ML setup. What's the problem may be?
Sorry for my bad English.
Sairon, seems like your battery drain is similar to what is happening here
Quote from: Walter Schulz on August 09, 2013, 08:27:18 AM
Let me guess: You opened card door, too and did it very fast after turning the switch?
Then we have this issue (http://www.magiclantern.fm/forum/index.php?topic=1455.msg3943#msg3943) on 7D, too.
Ciao, Walter
In case you missed it (I missed it too the first time reading), read this:
http://www.magiclantern.fm/forum/index.php?topic=1455
I've noticed this problem too. My question is: is it bad to leave your camera "on" and let it time out (i have mine set to time out after 30 seconds or a minute or something short) or is it better to turn off, then wait a couple seconds, open the door, wait some more, THEN remove the card?
I agree with CrazyRunner33 response to Britom's card speed question.
I own a Canon 50D with Raw_Rec and I have a Komputerbay 64GB 1000x card. The card may be capable of recording 125MB/s. However, due to the write limit of the 50D we are getting about 80MB/s. But yet, it also appears that the 50D is totally relying upon the extreme write speed in order to achieve writes upwards of 60MB/s.
Back to the 7D, I presume that a 600x is going to provide you with up to 60MB/s without trouble. However, we don't know how the 7D will handle the Raw_Rec module, just like what CrazzyRunner 33 had mentioned. We may find astonishing results with a 600x card in the 7D compared to that of the 50D due to the cameras different write speed capabilities...
This will definitely be something to post about when the time comes.
Quote from: Pileot on August 09, 2013, 07:57:39 PM
Sairon, seems like your battery drain is similar to what is happening here
In case you missed it (I missed it too the first time reading), read this:
http://www.magiclantern.fm/forum/index.php?topic=1455
I've noticed this problem too. My question is: is it bad to leave your camera "on" and let it time out (i have mine set to time out after 30 seconds or a minute or something short) or is it better to turn off, then wait a couple seconds, open the door, wait some more, THEN remove the card?
I have the same problem here. It happened twice since I started using ML this week. I have a really big concern about this issue, no battery = no camera :D
I'll try the "wait to remove card" thing, to check if it happens again.
EOScard downloads Audionut's ML with the 4 modules:
Magic Lantern v2.3.NEXT.2013Aug06.7D203
Mercurial changeset: 32338f9d75a0+ (unified) tip
Built on 2013-08-06 08:09:17 UTC by magiclantern@magiclantern-VirtualBox
How cumbersome would it be to add a changelog in there? Would be nice to know what differences there are between releases, if its not something Im gonna use why update and potentially break something thats perfectly fine?
There's already a changelog showing the code commits for the 7D at bitbucket - https://bitbucket.org/hudson/magic-lantern/commits/all/
More one video in 2.5k raw
-I didn't use a tripod, only what exist in the street for give me some kind of stabilization and after in post i used the warp stabilizer from cs6.
-Color correction, i have done some and in some scenes heavy grading, just to see how 14bits can handle and i must say, awesome. Wend i past the dng to after effects i just adjust the levels of blacks and whites with camera raw, then some grading in the timeline.
-It's was difficult to me to handle the dng files and for grading it's to ward to me/computer. I move a slide and just after a few seconds it will do the job.
-For exporting it take me about 35 minutes.
-My workflow: Put each scene (dng's) in different folders. Open AE and import each folder with dng's files, it will open camera raw , i just level the blacks and whites. Make sequence, color correction and some grading. Export with h.264 (1080p vimeo preset) at 30fps.
-I think i have to transcribe from dng's to other format, for handle better in premiere or after effects. I want to go ProRes but im using pc and i think is only for mac... if some one can give me hint would be nice =))
What i can say about this experince? Once you go 2.5k you'll never go back !!! ;D
(damn vimeo... it just let me upload one HD video per week :'( im going upload in youtube)...and youtube only 720p . But evan at 720p it's amazing the 2,5k downscale to 1080p...needed to wait to get 1080p in youtube =)))
The raw_rec module is working on 7D but not really usable right now.
In 640x360 I got 261 frames...
If you want to try:
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym
http://pel.hu/ML/raw_rec.mo
Quote from: Pelican on August 10, 2013, 06:10:22 PM
The raw_rec module is working on 7D but not really usable right now.
In 640x360 I got 261 frames...
If you want to try:
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym
http://pel.hu/ML/raw_rec.mo
Unbelievable ;D Thank you, going to try !
I can record 1152x576 continously with a Trascend 400x card.
The maximum that he let me is:
1728x972 = 101frames (skip one)
Others:
1152x576 = 241 frames (also skip one frame)
960x540 = 42,8MB/s = 51% idle = continuous recording
SanDisk 60MB/s
8GB
*after recording some raw footage the liveview stay in the same frame. For get the normal Lv and without turn off the camera i go to raw module and preview the raw video, after this he back to the normal Lv without stay forever in the same frame. If i hit the preview in raw module i need to go till the end, no button work for stop the preview.
^ Yes i have the same issue, only when i zoom in 10x to check focus. I got rid of it by switching to photo mode and back.
And i am also having continuous recording at 1728x648* 1600x600 with the same card. Getting there :)
*Correction: Although i didn't get any in camera errors at 1728x648 the actual files are unreadable. At 1600x600 it is no problem however.
so, raw video finaly unlocked ? its not the silent picture burst with the only 2 sec shots ? or its same ? dont understand realy how that work.
just have to buy 1000x fast card now. so, i can test with my 633x i have...
Quote from: BVG on August 10, 2013, 07:45:17 PM
^ Yes i have the same issue, only when i zoom in 10x to check focus. I got rid of it by switching to photo mode and back.
And i am also having continuous recording at 1728x648* 1600x600 with the same card. Getting there :)
*Correction: Although i didn't get any in camera errors at 1728x648 the actual files are unreadable. At 1600x600 it is no problem however.
What card you are using?
Quote from: obiyan19 on August 10, 2013, 07:51:47 PM
so, raw video finaly unlocked ? its not the silent picture burst with the only 2 sec shots ? or its same ? dont understand realy how that work.
just have to buy 1000x fast card now. so, i can test with my 633x i have...
Yes, is RAW :D Just download the last files that Pelican upload.
Nobody has a 1000x CF card?
Quote from: arrinkiiii on August 10, 2013, 08:11:46 PM
What card you are using?
No sorry I only have a Sandisk at 60mMB/s max
When I load it, the screen displays "Scripts dir missing" and it seems that every frame is coming out corrupted... Thanks for all the hard work...
Quote from: BVG on August 10, 2013, 08:18:06 PM
No sorry I only have a Sandisk at 60mMB/s max
Same thing, same card! ...no money :'(
Quote from: codypowers on August 10, 2013, 08:19:33 PM
When I load it, the screen displays "Scripts dir missing" and it seems that every frame is coming out corrupted... Thanks for all the hard work...
You can create the missing scripts dir manually or use the latest EOScard (v1.39) which creates the empty folders too.
is this last built compatible with exFAT ? just for know if file bigger than 4 gb would be possible ?
I have a small problem with MagicZoom window.
When I use x10 and back at normal view , magic zoom window don't hide.
What the problem?
Hello,
I'd like to make my 7D autoboot.
Is there any installation guide written for newbies to get an auto-bootable magic lantern version ? Do I have to use EOS Card ? How do I do this ?
Thank you !!!
yes, the tutorial is here: http://www.magiclantern.fm/forum/index.php?topic=7464.0
Quote from: obiyan19 on August 10, 2013, 09:18:03 PM
is this last built compatible with exFAT ? just for know if file bigger than 4 gb would be possible ?
The raw_rec module automatically cut the RAW video file into 4GB pieces...
Quote from: Sairon on August 10, 2013, 09:34:51 PM
I have a small problem with MagicZoom window.
When I use x10 and back at normal view , magic zoom window don't hide.
What the problem?
Exactly, me too. I gotta change to photo mode back and forth to make liveview visible again. I think it was mentioned before! Also, it has happened that when I hit record the liveview freezes. I know there's an option to do that.. it was set to Auto, maybe ML decided to set that option on.
Will be converting my footage soon, using a 166x card, and getting 135 frames in 2.35:1 and 109 I think on 16:9, maximum res available of course. I think the first video I recorded was corrupted... will see!
THANK YOU SO F*** MUCH PELICAN!!!! :D
How do I install this raw rec module? Am I missing something blatantly obvious or something? Sorry if it's been mentioned before!
Many thanks,
Matt
Quote from: Pelican on August 10, 2013, 06:10:22 PM
The raw_rec module is working on 7D but not really usable right now.
In 640x360 I got 261 frames...
If you want to try:
http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym
http://pel.hu/ML/raw_rec.mo
replace the same files you have on cf card with this ones
Quote from: szigiszmund on August 10, 2013, 11:31:58 PM
replace the same files you have on cf card with this ones
It doesnt seem to boot when i replace these files. It boots with the original files but when i replace them then it doesn't work? Any ideas please?
cheers,
Matt
Made it work! Turns out i clicked the links instead of right clicking and saving as! Thanks for the advice, keep it up!
Matt
I replaced files that were listed, and get an error on all modules. I remove the raw_rec module, and they all function correctly. Am I missing something?
probably one of the other two remaining files was not properly substituted
Tested my new 1000x card ,
got 69 frames of 1736x1156
got 59 frames of 2520x1200
tried testing the raw module but after copying the 3 files to my card the cam would not boot up , had to remove the battery and reformat the card
trying to figure it out , will try re-downloading as Miffy has suggested
Working now ;)
possible cause is if you remove cf card after shooting down camera end you left camera in movie mode,it wold refuse to start again.
battery need to be removed.
Congratulations ML Team on the 7D Raw_Rec and Silent Pic_Burst!
Thanks too.
Tested the RAW module with a 1000x Lexar card and
1728x972 = 107 frames
1152x576 = 243 frames
get weird glitches in 1728 see this picture (http://i.cubeupload.com/OIzfZZ.jpg)
also liveview seem to freeze alot , after recording and 10x crop makes it freeze
Lastly a question related to silent burst , the * button to change the aperture starts the burst , is this intended ?
Quote from: kh3naz on August 11, 2013, 02:09:36 AM
Tested the RAW module with a 1000x Lexar card and
1728x972 = 107 frames
1152x576 = 243 frames
get weird glitches in 1728 see this picture (http://i.cubeupload.com/OIzfZZ.jpg)
also liveview seem to freeze alot , after recording and 10x crop makes it freeze
Lastly a question related to silent burst , the * button to change the aperture starts the burst , is this intended ?
Strange... with my sandisk 60MB/s im getting the same number of frames.
Quote from: Pelican on August 10, 2013, 06:24:47 PM
I can record 1152x576 continously with a Trascend 400x card.
I can only record continuously at 960x540 on a 1000x card :-\
Here's a list of raw continuous recording resolutions using 1000x cf card
24P & 30P
1728 x 576
1600 x 534
1472 x 626
1344 x 610
1280 x 582
1152 x 622
60P
1728 x 308
1600 x 382
1472 x 420
1344 x 436
1280 x 486
1152 x 464
Quote from: ted ramasola on August 11, 2013, 05:49:09 AM
Here's a list of raw continuous recording resolutions using 1000x cf card
They all work fine , thanks !
What i'm wondering is , will we ever be able to capture longer 2520x1200 with no line skipping
after playing around with this all night it's really hard to look back , it really is a tease
Quote from: kh3naz on August 11, 2013, 02:09:36 AM
Tested the RAW module with a 1000x Lexar card and
1728x972 = 107 frames
1152x576 = 243 frames
get weird glitches in 1728 see this picture (http://i.cubeupload.com/OIzfZZ.jpg)
Exactly the same results with 1000x Lexar and 400x Transcend.
And like Pelican, I can record 1152x576 (ratio 2:1) continously.
A surprise from pravdomil:
http://pel.hu/ML/arkanoid.mo
Quote from: Pelican on August 11, 2013, 08:55:28 PM
A surprise from pravdomil:
http://pel.hu/ML/arkanoid.mo
What is this??? :)
Arkanoid game :o ?
https://bitbucket.org/hudson/magic-lantern/pull-request/171/some-arkanoids/diff
Quote from: arrinkiiii on August 11, 2013, 09:15:15 PM
Arkanoid game :o ?
https://bitbucket.org/hudson/magic-lantern/pull-request/171/some-arkanoids/diff
If you play good Arkanoid will unlock 4k raw recording
lol ...secret level take you to 6k ::)
Quote from: arrinkiiii on August 11, 2013, 09:25:03 PM
lol ...secret level take you to 6k ::)
unlocks dragonREC.mo
Quote from: edingacic on August 11, 2013, 09:29:12 PM
unlocks dragonREC.mo
..the end of last big boss will open the ultimate reward... arri7D.mo ;D
Quote from: Thomas Worth on August 11, 2013, 09:21:23 PM
Here's raw_rec.mo with Pelican's changes:
http://www.mediafire.com/download/17wrac41a1oi4bu/raw_rec.mo
Quote from: Pelican on August 10, 2013, 08:47:54 PM
You can create the missing scripts dir manually or use the latest EOScard (v1.39) which creates the empty folders too.
Sorry Pelican, I can't find the v1.39 :-[
Quote from: ArturoKiwi on August 11, 2013, 10:02:04 PM
Sorry Pelican, I can't find the v1.39 :-[
http://lmgtfy.com/?q=eoscard
;););)
Quote from: ArturoKiwi on August 11, 2013, 10:02:04 PM
Sorry Pelican, I can't find the v1.39 :-[
Somebody reported an error so I reverted back to 1.38.
Until I find what was wrong you have to create the scripts folder manually.
-For who stay stuck in LiveView, just hit the menu button from camera.
Quote from: Pelican on August 11, 2013, 08:55:28 PM
A surprise from pravdomil:
http://pel.hu/ML/arkanoid.mo
Bug report and feature request.
1. There should be a tool tip or info text indicating what to press to start. I discovered by accident that the joystick does it.
2. I have reached the second level, is there a way to record previous score so I can brag to other ML users?
3. There should be a realtime points indicator to indicate your progress and to stoke the player's ego.
Overall I like that the current level starts again when you miss and not start from level 1. Keep up the great work guys! :)
Quote from: ted ramasola on August 12, 2013, 12:34:54 AM
Bug report and feature request.
1. There should be a tool tip or info text indicating what to press to start. I discovered by accident that the joystick does it.
2. I have reached the second level, is there a way to record previous score so I can brag to other ML users?
3. There should be a realtime points indicator to indicate your progress and to stoke the player's ego.
Overall I like that the current level starts again when you miss and not start from level 1. Keep up the great work guys! :)
I hope this was a joke :D People here are working on Raw_rec for a dslr and you write bug reports about a game? Don´t get me wrong, the feature is awesome and really funny, but i personly would prefer proper raw over this game^^ you have a smartphone to play games, dont you :P
no offense intendet :)
greets
Quote from: jemabaris on August 12, 2013, 01:10:55 AM
I hope this was a joke :D People here are working on Raw_rec for a dslr and you write bug reports about a game? Don´t get me wrong, the feature is awesome and really funny, but i personly would prefer proper raw over this game^^ you have a smartphone to play games, dont you :P
no offense intendet :)
greets
Its good that they installed the game so you can do something instead of getting impatient while dngs export from AE or Resolve. Resolve takes 30 min to export 15 min footage while AE takes more than an hour. So while waiting you can run ARKANOID! :D
What level have you reached? :D
Quote from: Thomas Worth on August 11, 2013, 09:21:23 PM
Here's raw_rec.mo with Pelican's changes:
http://www.mediafire.com/download/17wrac41a1oi4bu/raw_rec.mo
On a serious note. I tried this compiled by Thomas but in modules Tab Raw_rec was marked as file error.
Other modules were all ok.
edit.
I copied it again and the file error is now ok.
Also tested with ext monitor via hdmi hoping maybe live view won't freeze but it still does. Have to press either caon menu or switch to photo then back to video to unfreeze liveview.
Quote from: ted ramasola on August 12, 2013, 01:22:42 AM
On a serious note. I tried this compiled by Thomas but in modules Tab Raw_rec was marked as file error.
Other modules were all ok.
He loaded the raw module fine for me.
I have also to make a folder with the name SCRIPTS inside of ML folder, for stop the message "...dir scripts..."
Quote from: ted ramasola on August 12, 2013, 01:17:34 AM
Its good that they installed the game so you can do something instead of getting impatient while dngs export from AE or Resolve. Resolve takes 30 min to export 15 min footage while AE takes more than an hour. So while waiting you can run ARKANOID! :D
What level have you reached? :D
How are you exporting? when i export H.264 from Resolve it takes less than 10 minutes for 15 minutes.
Quote from: jemabaris on August 12, 2013, 01:34:11 AM
How are you exporting? when i export H.264 from Resolve it takes less than 10 minutes for 15 minutes.
My nvidia card is older.
h264 takes 24 min.
but I do my finishing on the NLE so I export a qt yuv422, for those clips that need further work on the NLE. I use Edius.
I don't usually go the resolve route only when it needs more grading. Most stuff I do for corporate and ads are short clips.
Since I'm helping DVXuser put a workflow guide I was doing time tests based on a full 64gig card.
For documentation and comparative purposes these are the clock time for export using different codecs.
Based on a 3 yr old i7 system. (you can interpolate the time based on your own system)
15:06:19 length DNGs
DNG to QT uncompressed YUV 422 10bits (112 gig exported mov)
Resolve: 00:56:32
AfterEfcts: 01:30:15
DNG to QT MP4
Resolve: 00:45:00
AfterEfcts: 01:26:00
DNG to QT H264
Resolve: 00:24:00
AfterEfcts: 01:29:00
DNG to TIFF
Resolve: 00:58:00 16bit 11.8mb/frame
00:43:00 8bits 5.43mb/frame
AfterEfcts: 01:33:00 LZW 1.87mb/frame
Quote from: ted ramasola on August 12, 2013, 01:44:04 AM
My nvidia card is older.
h264 takes 24 min.
May I ask for your system specs?
Quote from: jemabaris on August 12, 2013, 01:48:08 AM
May I ask for your system specs?
window 7 64 bit i7 930cpu.
with 12gig ram
slow by today's standards.
Quote from: ted ramasola on August 12, 2013, 01:54:39 AM
window 7 64 bit i7 930cpu.
with 12gig ram
slow by today's standards.
weird, i have an i7 2600k and 20 gigs and it handles it a lot faster. maybe due to the gtx 680s cuda cores
Quote from: jemabaris on August 12, 2013, 01:57:31 AM
weird, i have an i7 2600k and 20 gigs and it handles it a lot faster. maybe due to the gtx 680s cuda cores
oh, resolve is cuda dependent, AE also uses Cuda. I only have a gtx460. :) thats why my exports from resolve and AE are slow.
I don't want to upgrade a component for now since I plan to get a new system from scratch since I plan to use my other PCs as part of a render network for my 3D work.
Quote from: obiyan19 on August 10, 2013, 09:55:11 PM
yes, the tutorial is here: http://www.magiclantern.fm/forum/index.php?topic=7464.0
The instructions appear to be for Windows -- is there a procedure for those of us who use Linux?
Quote from: ygor on August 09, 2013, 11:05:59 PM
I have the same problem here. It happened twice since I started using ML this week. I have a really big concern about this issue, no battery = no camera :D
I'll try the "wait to remove card" thing, to check if it happens again.
I've got this problem again, even waiting to remove card (after red light blinks, after sensor cleaning). Battery was full, but at the morning, battery was empty.
Is there any I can help to investigate this issue?
Quote from: ygor on August 12, 2013, 04:26:26 AM
Is there any I can help to investigate this issue?
I can't really help, but it has happened to me too. But for me I don't know if it's related to the card door (I was told it's not related...) anyhow, if I turn my camera off on the main switch and then leave the camera for the night, then the batteries are drained in the morning. But if I leave the camera to turn off by itself (power save mode usually keep mine on 1 min) then it's fine.
But I noticed yesterday if I have a lens with IS and the IS is turned on and I leave the camera in movie mode, then it keeps the IS motor going constantly...
My conclusion...
Leave the camera in photo mode
Set power save to something that will be convenient for you (1, 2, 5min etc)
Leave the main power switch on at all times
Ok, perhaps this is a little sidetracked but I'm having issues accessing the complete user guide from the camera. Trash bin, Help tab, Complete user guide, then its just an empty box (used to show everything you could want to know about ML)
Is this just me or other people too?
v2.3.NEXT.2013Aug04.7D203
The reason I was wanting to check is because I'm wondering about the silent picture mode. I know it takes info from the live view and from the search its supposed to make .422 files. When I tried it it made .dng files that I have no idea how to open or process.
I am also curious about the Silent Picture modes, Simple, Burst, End Trigger, Best Shots, and Slit Scan. Search did not yeild very many results on these, wiki seems slim in these areas, I just want to know what the differences are so I know when to use em.
Thanks!
**EDIT**
Downloaded the latest EOScard, deleted ML off my card, ran EOScard and now i have ML version Aug01? Isnt the latest version Aug06? Im a little confused... Also seems the Aug01 is missing the silent picture function (or at least its hiding really good)
Quote from: Magic 7D on August 12, 2013, 09:18:49 AM
My conclusion...
Leave the camera in photo mode
Set power save to something that will be convenient for you (1, 2, 5min etc)
Leave the main power switch on at all times
Impractical if your going to leave your camera in a bag where buttons might get pushed, draining the battery.
When you turn your camera off for the night, try turning the switch to OFF then removing the battery and plugging the battery back in again. Perhaps that will solve the drain issue? (A pain but less of a pain than a dead battery)
Quote from: Pileot on August 12, 2013, 10:17:25 AM
Impractical if your going to leave your camera in a bag where buttons might get pushed, draining the battery.
I can't confirm that. I never turn off my camera since my 20D and never got empty battery.
Well it depends how tight your bag is, I have a backpack style bag with big heavy lenses in it (like the 100-400) so its possible for enough pressure to be put on buttons to register a press and wake the camera. Everyone's setup is different, just depends how your bag is set up.
Does the problem still happen if you let the camera sleep, THEN turn it off? Can you confirm if turning the camera off then removing and replacing the battery will prevent any battery drain or is it useless to try?
Quote from: Pileot on August 12, 2013, 11:06:29 AM
Well it depends how tight your bag is, I have a backpack style bag with big heavy lenses in it (like the 100-400) so its possible for enough pressure to be put on buttons to register a press and wake the camera. Everyone's setup is different, just depends how your bag is set up.
Maybe the 300/2.8 is not heavy enough in my backpack... :-)
Have you ever heard that an accidentally pressed camera button drained the battery of somebody's camera?
Quote from: Pelican on August 12, 2013, 10:59:12 AM
I never turn off my camera since my 20D and never got empty battery.
I can confirm that, never turn my 7D off lugging it around in my Lowepro classified 160 AW or my Kata 3N1-20 never had empty battery part from the time I thought I should be good and turn the camera off to save battery.. Ironic isn't it ;)
Quote from: Pileot on August 12, 2013, 11:06:29 AM
Everyone's setup is different, just depends how your bag is set up.
Does the problem still happen if you let the camera sleep, THEN turn it off? Can you confirm if turning the camera off then removing and replacing the battery will prevent any battery drain or is it useless to try?
I'd agree on that, but as I said I've never had issues. (I've got 7D with 17-55 2,8 attached, 70-200 2,8, 50 1,4, 85 1,8, 2x extender, speedlight 580 and 420, 4 extra batteries, speedlight collapsible octabox, 2 chargers, a bunch of cables card reader and a few other extras don't know if this is heavy enough.. :) )
I'll try your take on letting it go to sleep and then turn off tonight, you might want to try with battery remove/insert then we'll know tomorrow if either of them work :)
Quote from: Pileot on August 12, 2013, 10:14:58 AM
The reason I was wanting to check is because I'm wondering about the silent picture mode. I know it takes info from the live view and from the search its supposed to make .422 files. When I tried it it made .dng files that I have no idea how to open or process.
I loaded my .dngs into lightroom got a warning that lightroom didn't recognize them, but I could process them fine. Haven't tried any other program.
Quote from: Pelican on August 11, 2013, 10:52:43 PM
Somebody reported an error so I reverted back to 1.38.
Until I find what was wrong you have to create the scripts folder manually.
No problem at all for the directory. I ask you because with 1.38 I must flash twice; when I open the program it doesn't show me the bottom part, but it appears (and remain :) ) while writing on the card.
Quote from: ArturoKiwi on August 12, 2013, 11:49:14 AM
No problem at all for the directory. I ask you because with 1.38 I must flash twice; when I open the program it doesn't show me the bottom part, but it appears (and remain :) ) while writing on the card.
RTM! Or follow the tutorial.
"Hint: If you want to install different ML version (not the latest stable unified) right click on the ML button to open the Magic Lantern window. "
My workflow for silent pictures,
-Put each different scene (dng's) in different folder. After this open after effects, import or just drag the folders to after effects. For each folder he will open ACR, you make the adjustments that you need and click ok.
After this you just need make your video sequence. For open again the ACR, if you need to give more a few adjustments, you click on the dng file that you want, go to interpret footage, sub-menu and then hit options tab and he will open again the ACR. (exist a different way to do this but i dont remember)
I must tell that the dng's are heavy... my computer have problem to handle. Better to pass then to ProRes or DNxHD and then make the edition.
- It's strange that some ML fanatics have this battery problem and others don't :-\ I never had this, but i always take my battery out.
-For don't have the warning in the begging of turning on the camera "...dir scripts missing..." Just go to ML folder in your CF Card and create a new folder with the name SCRIPTS and the warning message will disappear.
Hello,
My report after 4 days holidays with it:
-it takes much longer to wake up from standby
- I have had the battery problem once
- also had issues with AF pumping (not LV), which could only be resolved by removing the battery
If someone want to add WiFi (file transfer only). Combined with ML.
I just tested the Toshiba Flashair 16GB class 10 (W-02) on a 7D.
In this case i also need a '3rd generation' CF adapter'
Both available on Ebay.
The big advantage of Toshiba is....> you Don't need a Dedicated app...works on a SmartPhone, Laptop (and Mac i think).
(https://sphotos-a.xx.fbcdn.net/hphotos-ash3/p206x206/555620_176579309147728_846908963_n.jpg)
(http://www.muamat.com/adpics/51de65c490d7289b41cae2678.jpg)
Also thinking....
it must me technically possible to remote control some features with a SmartPhone app. With this WiFi Card.
For example By checking the Write-protectingness of dedicated pictures....to use features.
(To enable the Wifi...i Use FileProtection on the DSLR...if enabled the Wifi is On...Disabled the Wifi is off)
Try removing the metal plates from the front and back of the CF adapter, you might get faster speeds / stronger connection.
What was your transfer rate? Can you take a video of you using it so we can see how slow it is? most reviews of the EyeFi cards say its OK for one or two shots at a time but if your doing lots of pictures it takes forever.
Been eyeing the WFT grips from canon but $500+ is too steep for me. Been considering making a wifi grip using USB wifi parts (lots of guides on google)
@pileot, If i shoot at regular burst (8fps 7D) and you fill up the camera's buffer...it takes 50 seconds to write it to the Toshiba card....so that's not fast.
Sending pictures by wifi.....it takes 30 seconds for 1,5Mb. (i prefer shooting Raw Large + JPG Small)
So it's only usefull when you're on location...and you want to share just 1 or 2 Pictures with someone.
But Maybe ...with a Module in ML...it's maybe possible to use it in a different way
sent me a Link for a DIY Wifi USB for EOS 7D
such a thing should be made for the EOShttp://cameraconnect.files.wordpress.com/2012/04/nikon_wu-1a_wifi_adapter.jpg (http://cameraconnect.files.wordpress.com/2012/04/nikon_wu-1a_wifi_adapter.jpg)
http://www.homebrewusb.com/DIY/DIY%20%20Portable%20Wireless%20USB.html
The problem is Cables Unlimited is dead. But the basic idea is still the same.
Well I picked up a WFT-E1A for REALLY cheap today, gotta track down some batteries and see if I can get er working on the 7D, but I digress.
As to my previous question about silent pictures... im finding that the current EOS utility is pulling an older version of ML that does not have silent picture enabled. Is this by design or am I doing something wrong?
Quote from: Pileot on August 13, 2013, 02:25:36 AM
Well I picked up a WFT-E1A for REALLY cheap today, gotta track down some batteries and see if I can get er working on the 7D, but I digress.
How much btw?
Quote from: Pileot on August 13, 2013, 02:25:36 AM
As to my previous question about silent pictures... im finding that the current EOS utility is pulling an older version of ML that does not have silent picture enabled. Is this by design or am I doing something wrong?
You are doing it wrong. Don't use EOS Utility. Get EOSCard from pelican's home. http://pel.hu/down
Quote from: Pileot on August 12, 2013, 11:06:29 AM
Does the problem still happen if you let the camera sleep, THEN turn it off?
Tried your suggestion last nite, and it seems to work fine like that. So last nite I left the camera to go to sleep, then I turned the main power switch off and this morning battery is still full.
Did you try the battery remove/insert Pileot?
Quote from: rlk on August 12, 2013, 03:35:21 AM
The instructions appear to be for Windows -- is there a procedure for those of us who use Linux?
A quick summary how to do it on linux.
install the bsdiff package (should come with your distribution)
get the http://pel.hu/down/eos7d110.exe, use unzip to extract it (it's a selfextracting zipfile, unzip knows how to handle them)
get the patch http://pel.hu/ML/booton.bsdiff
create the new 7dbooton.fir with
'bspatch 7d000110.fir 7dbooton.fir booton.bsdiff'
Put the the 7dbooton.fir on a CF. Put the CF in the camera and update the firmware.
You now have a bootable 7D (or if it false an expensive brick)
To make a bootable CF use https://bitbucket.org/hudson/magic-lantern/raw/74fa78df490372263aef62800e98d9c33e885aa6/make_bootable.sh, edit the dev=/dev/disk1s1 line. Point it to the CF partition (something like /dev/sdb1)
Run the script and you have a bootable CF, (i noticed that i had to format the CF first to make recognize the filesystem)
Mount the CF on your system, download http://pel.hu/ML/magiclantern-7D.203.Alpha2.zip , and unzip it on the CF.
This should be enough to get it working on linux. (all is done on the console)
Quote from: Pelican on August 12, 2013, 12:22:20 PM
RTM! Or follow the tutorial.
"Hint: If you want to install different ML version (not the latest stable unified) right click on the ML button to open the Magic Lantern window. "
Doh! :-[
Thanks :)
Quote from: themichael on August 13, 2013, 02:20:43 AM
http://www.homebrewusb.com/DIY/DIY%20%20Portable%20Wireless%20USB.html
The problem is Cables Unlimited is dead. But the basic idea is still the same.
i like this one more http://www.davidhunt.ie/?p=2641 (http://www.davidhunt.ie/?p=2641)
since the other is wUsb...so not direct compatible with you smartphone.
Derp ment EOScard not EOSutility.
Paid $150 for the WFT but I gotta order a battery and charger on ebay or something.
I dont generally have issues with power drain so its not something I worry about regularly.
Dear all,
what I'm wondering about: what has this all (RAW-Video) to do with the original post from MAgic Lantern about the 7D alpha 2 release.
Is is not better to place this in a own post? I'm not interested in Video-RAW, I'm interested in a serious continued 7D ML-release, to get sometime a final release ....
Regards
Gerd
Done nine days ago:
http://www.magiclantern.fm/forum/index.php?topic=7503.0
Ciao, Walter
Hi,
hopefully all the other will read it and NOT CONTINUE HERE WITH RAW-VIDEO!
Regards
Gerd
Maybe I've missed it, but is there a way in Alpha 2 to shoot 1080p at 50 or 60fps? I hate having to drop down to 720p to shoot overcranked.
Hi,
I haven't been able to find "Focus Patterns" in ML.
Does anyone know if this has been implemented for the 7D?
Quote from: stevelucky on August 17, 2013, 07:01:35 PM
Maybe I've missed it, but is there a way in Alpha 2 to shoot 1080p at 50 or 60fps? I hate having to drop down to 720p to shoot overcranked.
Hi! I don't think it's possible yet. Would be cool indeed, so hopefully at some point . I was wondering if it might be possible to shoot at even higher framerates by lowering the resolution? I mean how fast is the raw image buffer? Would higher than 60fps even be possible?
Thanks to ML for making this .FIR available for 7D. Just installed, doing some tests and noticed:
1. ML doesnt work when cam is wakend after power save(sleep) mode. ML need to be reInstalled. No auto load.
2. Magic Zoom, does'nt work with f.ring (tested with tamron 18-270mm), only half shuter works.
3. NO audio meters in normal L.View, (while in REC is OK).
4. No audio control, too much bg noise.
5. Hope for HDR video soon.. :)
Quote from: Dorian on August 18, 2013, 04:58:35 PM
Thanks to ML for making this .FIR available for 7D. Just installed, doing some tests and noticed:
1. ML doesnt work when cam is wakend after power save(sleep) mode. ML need to be reInstalled. No auto load.
2. Magic Zoom, does'nt work with f.ring (tested with tamron 18-270mm), only half shuter works.
3. NO audio meters in normal L.View, (while in REC is OK).
4. No audio control, too much bg noise.
5. Hope for HDR video soon.. :)
You may want to go back several pages and read up. Auto boot has been enabled but you've got to follow the instructions. Several of those other points have been addressed as well.
@Dorian
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Quote from: Dorian on August 18, 2013, 04:58:35 PM
Thanks to ML for making this .FIR available for 7D. Just installed, doing some tests and noticed:
1. ML doesnt work when cam is wakend after power save(sleep) mode. ML need to be reInstalled. No auto load.
2. Magic Zoom, does'nt work with f.ring (tested with tamron 18-270mm), only half shuter works.
3. NO audio meters in normal L.View, (while in REC is OK).
4. No audio control, too much bg noise.
5. Hope for HDR video soon.. :)
i have asked about 3 and 4 already, but noone cared and i got no reply on that. no audio meters when not recording is not really helpful. afaik in alpha2 it was different..
In this new ML version the audio meters only work after you start record. We hope in near future the dev's can fix it. For now is just like it is.
But for you get around with this bug you can hit the menu button in your camera and see the audio meters working live in the canon menu. After you adjust the volume you just need to hit again the menu button and you are in the liveView ready to record.
I just noticed a problem that I THINK it is related to Magic Lantern.. cause I read it around here but now cannot find the specific posts.
I use my 7D for filming only, hardly ever take any photos. So last friday I got a photo job.. ok, let's do it! But it looks like the autofocus works like crap!! At first it wasn't working at all.. half-pressed my shutter button and nothing, completely dead.. Tried swapping batteries, cards, removing ML, nothing.. still the same.. the lens worked ok, because I tested it on another camera earlier.. So after several tried, workarounds, taking pics in manual mode, then turning autofocus on, etc etc I managed to get it partially working.. it didnt work all the time.. every now and then I had to swap the AF-MF button on the lens.. :/
I think it is ML related because I think I read around this thread that people had 7D's with autofocus broken... truth is I am really scared about this.. if this is true I won't be able to sell the camera, or take pictures.. am I hallusinating or does this happened before? If so, is there any fix??
BTW I haven't been able to test it with another lens.. but the one that was given was good I believe!!!
Thank you very much to all, I love ML and hope there's a way out to this!!!!
Cheers!
Quote from: tonybeccar on August 20, 2013, 06:12:41 AM
I just noticed a problem that I THINK it is related to Magic Lantern.. cause I read it around here but now cannot find the specific posts.
I use my 7D for filming only, hardly ever take any photos. So last friday I got a photo job.. ok, let's do it! But it looks like the autofocus works like crap!! At first it wasn't working at all.. half-pressed my shutter button and nothing, completely dead.. Tried swapping batteries, cards, removing ML, nothing.. still the same.. the lens worked ok, because I tested it on another camera earlier.. So after several tried, workarounds, taking pics in manual mode, then turning autofocus on, etc etc I managed to get it partially working.. it didnt work all the time.. every now and then I had to swap the AF-MF button on the lens.. :/
I think it is ML related because I think I read around this thread that people had 7D's with autofocus broken... truth is I am really scared about this.. if this is true I won't be able to sell the camera, or take pictures.. am I hallusinating or does this happened before? If so, is there any fix??
BTW I haven't been able to test it with another lens.. but the one that was given was good I believe!!!
Thank you very much to all, I love ML and hope there's a way out to this!!!!
Cheers!
Have you checked your camera settings? Due to some ML error, my camera settings had once changed and I didn't have the shutter button assigned to AF no more. This can be found in Canon menu - C. Fn IV - 1 settings. (The very first one)
I thought for a minute too that my shutter button was broken, as I hadn't touched the settings myself..
Quote from: jalejake on August 20, 2013, 07:49:07 AM
Have you checked your camera settings? Due to some ML error, my camera settings had once changed and I didn't have the shutter button assigned to AF no more. This can be found in Canon menu - C. Fn IV - 1 settings. (The very first one)
I thought for a minute too that my shutter button was broken, as I hadn't touched the settings myself..
Thanks for your response! I checked all the settings fast as I was going to the shoot.. I don't have my camera here but will look for that setting tomorrow. Also, good idea, maybe I had some button assigned to half-shutter, I know I usually do it with Magic Zoom. Bad thing is I'm returning the AF lens tomorrow.. don't know when I'll be able to test it again as I have all old Nikkor manual lenses.. (awesome stuff!!!).
Will check when I can.. but the question still stands if anyone knows another thing that may be causing it!
Again, thank you jalejake!!! :D
Hi. Im using EOSCard 1.40 and found that in ISO submenu I dont have a full range of options - ML Digital ISO, for example.
Just a little issue (not sure it's from ML)
But i made a picture....i looked to the Preview....and it said exposure +1 stop.
So i thought...my mistake...but it wasn't....the camera Exposure was on 0.
Restarted the camera without ML...same problem.
Then i took a Picture with -1 stops....and the picture preview said 0...
What i did to solve this problem......
I put the exposure to +5 (max) and -5 (minimum)...and set it back to 0
For some reason....my light meter was Exposure set +1
Quote from: mityazabuben on August 20, 2013, 02:06:35 PM
Hi. Im using EOSCard 1.40 and found that in ISO submenu I dont have a full range of options - ML Digital ISO, for example.
ML Digital ISO is currently not working on the 7D so they took it out of the menu for now.
Quote from: wheezl on August 20, 2013, 07:34:53 PM
ML Digital ISO is currently not working on the 7D so they took it out of the menu for now.
Thanks. And whats the best ISO using for photo/video/raw video for now?
Quote from: mityazabuben on August 20, 2013, 10:09:06 PM
Thanks. And whats the best ISO using for photo/video/raw video for now?
I have been getting the best results from 160 YMMV.
Quote from: hypermobile on August 20, 2013, 07:13:37 PM
Just a little issue (not sure it's from ML)
But i made a picture....i looked to the Preview....and it said exposure +1 stop.
So i thought...my mistake...but it wasn't....the camera Exposure was on 0.
Restarted the camera without ML...same problem.
Then i took a Picture with -1 stops....and the picture preview said 0...
What i did to solve this problem......
I put the exposure to +5 (max) and -5 (minimum)...and set it back to 0
For some reason....my light meter was Exposure set +1
The same happened for me a few month ago.
I tried to reset the camera settings remove both batteries and reupdate the firmware and finally solved the problem but I don't remember which step was the solution.
Quote from: Pelican on August 20, 2013, 10:23:33 PM
The same happened for me a few month ago.
I tried to reset the camera settings remove both batteries and reupdate the firmware and finally solved the problem but I don't remember which step was the solution.
My solution was for Sure: >>Max and Min the Exposure with the wheel.
(in my world....that resets the Min or Max value...so the exposure 0 is actually 0 again.)
easy fix....but i was wondering where it went wrong!
Quote from: tonybeccar on August 20, 2013, 06:12:41 AM
I just noticed a problem that I THINK it is related to Magic Lantern.. cause I read it around here but now cannot find the specific posts.
I use my 7D for filming only, hardly ever take any photos. So last friday I got a photo job.. ok, let's do it! But it looks like the autofocus works like crap!! At first it wasn't working at all.. half-pressed my shutter button and nothing, completely dead.. Tried swapping batteries, cards, removing ML, nothing.. still the same.. the lens worked ok, because I tested it on another camera earlier.. So after several tried, workarounds, taking pics in manual mode, then turning autofocus on, etc etc I managed to get it partially working.. it didnt work all the time.. every now and then I had to swap the AF-MF button on the lens.. :/
I think it is ML related because I think I read around this thread that people had 7D's with autofocus broken... truth is I am really scared about this.. if this is true I won't be able to sell the camera, or take pictures.. am I hallusinating or does this happened before? If so, is there any fix??
BTW I haven't been able to test it with another lens.. but the one that was given was good I believe!!!
Thank you very much to all, I love ML and hope there's a way out to this!!!!
Cheers!
It sounds like your focus got taken off the shutter half press and is only on the af/on button on the back of the cam next to the * button. If this is what happened you can change it back in the custom functions. This is called back button autofocus && is a feature some (most) prefer. HTH
Cheers ....
--
K.C.
Quote from: Dorian on August 18, 2013, 04:58:35 PM
Thanks to ML for making this .FIR available for 7D. Just installed, doing some tests and noticed:
1. ML doesnt work when cam is wakend after power save(sleep) mode. ML need to be reInstalled. No auto load.
2. Magic Zoom, does'nt work with f.ring (tested with tamron 18-270mm), only half shuter works.
3. NO audio meters in normal L.View, (while in REC is OK).
4. No audio control, too much bg noise.
5. Hope for HDR video soon.. :)
Kindly read the first post in this thread. The big red letters, they are very hard to miss.
Magic zoom only worked intermittantly for me on the T2I. Considering this camera is in ALPHA its not something I am going to complain about. Features are added daily it seems, lots of people are working hard I'm not going to complain about features not working as they should before porting is finished. Its like telling builders that the elevator doesn't go to the top of the building when its still not finished being built.
Anyways, read the first post again, or if your lazy click here:
http://goo.gl/NmIUja :)
Quote from: frogcement on August 21, 2013, 12:55:07 AM
It sounds like your focus got taken off the shutter half press and is only on the af/on button on the back of the cam next to the * button. If this is what happened you can change it back in the custom functions. This is called back button autofocus && is a feature some (most) prefer. HTH
Cheers ....
--
K.C.
Thank you so much man!! Will borrow an AF lens today and let you know if I solved it!! :D What a great support!! ;)
Cheers!!!
Quote from: tonybeccar on August 20, 2013, 06:12:41 AM
So after several tried, workarounds, taking pics in manual mode, then turning autofocus on, etc etc I managed to get it partially working.. it didnt work all the time.. every now and then I had to swap the AF-MF button on the lens.. :/
I think it is ML related because I think I read around this thread that people had 7D's with autofocus broken... truth is I am really scared about this.. if this is true I won't be able to sell the camera, or take pictures.. am I hallusinating or does this happened before? If so, is there any fix??
BTW I haven't been able to test it with another lens.. but the one that was given was good I believe!!!
I experience a similar behavior:
When exchanging lenses I always have to pull the battery. Otherwise the lens will focus somewhere but not at the spot I want it to. If I pull the battery everything is fine again. I can live with this workaround for now and since I was not sure if anybody is already working on the bug I did not mention it till now. My build is timestamped last week, I think (but I will check).
Maybe related: Dot Tune AFMA is not working properly. It always gets values of +9 to +12 and complains to double check the focus chart.
My manually adjusted values are in the range of -3 to +4.
I really appreciate the work done so far! It's just my feedback to the great developers.
My Version is timestamped aug-06 8:00 something.
Is there a newer one? I tried using EOSCard but I alwas gat this one.
Quote from: naturalsound on August 23, 2013, 08:09:26 AM
My Version is timestamped aug-06 8:00 something.
Is there a newer one? I tried using EOSCard but I alwas gat this one.
You can download here
https://www.dropbox.com/sh/9w5t3lcmgugo32g/Xmn6H066DY
But for you been updated with the latest version's go here
http://www.magiclantern.fm/forum/index.php?topic=7503.0
Less of a raw question and more of a general development question:
Has any progress been made on the video recording, especially the FPS override? and exposure overrides? This sunday I was hoping to use these features on the 7D, im not asking for perfection or completely bug free or anything, but if the devs have anything that generally works I would greatly appreciate it.
Many thanks! Keep up the great work!
Good evening Arrinkiiii.
I am lost :
I updated ML Alpha2 from the first link (https://www.dropbox.com/sh/9w5t3lcmgugo32g/Xmn6H066DY), and ML doesn't work any more ! Snif
(I noticed that the ML directory only contains a "Modules" directory.
What have I done wrong ?
Regards
Thierry
Maybe I missed something, but there should be only one place where to download the complete ML-7d program
Quote from: ThLDQ on August 24, 2013, 07:20:23 PM
Good evening Arrinkiiii.
I am lost :
I updated ML Alpha2 from the first link (https://www.dropbox.com/sh/9w5t3lcmgugo32g/Xmn6H066DY), and ML doesn't work any more ! Snif
(I noticed that the ML directory only contains a "Modules" directory.
What have I done wrong ?
Regards
Thierry
Maybe I missed something, but there should be only one place where to download the complete ML-7d program
Hi ThLDQ
Uhmmmmm, can be everything and can be nothing... for sure in no time we will have your 7D RAW machine working like a swiss watch...
-The link from dropbox contains the 2 last versions that britom make to try to fix the freeze of Lv. Im going put in the same link the working and more stable version. Also what is in that link is just for update your CF card.
-Format card, use EOSCard from Pelican (the last version, i think) and i will update right now the link with the files. With this files you just need to put in your cf card (updating what is necessari. For update we don't need to have all the files that eoscard make and put in cf card) ..and everything will be alright.
EDIT:This is the link
https://www.dropbox.com/sh/9w5t3lcmgugo32g/Xmn6H066DY
After format and use eoscard just update your autoexec.bin in the root of cf card and the Modules folder en the ML folder is cf card.
Wend you turn on your camera if it say something like " no dir found" just go to ML forlder in cf card and make one folder with the name SCRIPTS.
Hope this help. Anything just let me know, glade to help :D
Quote from: ThLDQ on August 24, 2013, 07:20:23 PM
Maybe I missed something, but there should be only one place where to download the complete ML-7d program
I full agree with you. But some times a dev make a version for we try on the fly... I think we should put this working version in the 7D Raw threat http://www.magiclantern.fm/forum/index.php?topic=7503.0
Thanks Arrinkiiii,
Something went really wrong : my cf card now freezes my 7d ????!!!! I can't formlat it neither by my Mac, nor by my 7d :o
Eoscard is surelly a good way to update ML but I'm running a Mac whiwh ignores what Eoscard can be.
Regards
Thierry
Hi Arrinkiiii
I finally succeeded in formating my cf card, which is now recognized by my Mac and by the 7d.
My problem is that I only have now the modules directory and the autoexec.bin.
Where can I find all the missing directories and files ?
Regards
Thierry
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Since you dont use eoscard and you need to make your card bootable and have all the folders, go here
http://www.magiclantern.fm/forum/index.php?topic=7752.msg67944#msg67944
I just installed your Dropbox version - and when I boot it up I get a "scripts dir missing" message? Any idea?
sorry found my answer.. "Wend you turn on your camera if it say something like " no dir found" just go to ML forlder in cf card and make one folder with the name SCRIPTS."
Quote from: Pileot on August 24, 2013, 01:42:20 AM
Less of a raw question and more of a general development question:
Has any progress been made on the video recording, especially the FPS override? and exposure overrides? This sunday I was hoping to use these features on the 7D, im not asking for perfection or completely bug free or anything, but if the devs have anything that generally works I would greatly appreciate it.
Many thanks! Keep up the great work!
Thank you Arrinkiii,
I finally succeeded in reinstalling ML.
I followed the Mac instructions, but there was still a problem (7d freezed), I guess it was because the DCIM and MISC directories had not been created by my 7d... Who knows ???
I formatted twice or three times, on my Mac, on a PC, on the 7d, changed AUTOEXEC.BIN in autoexec.bin and now it works.
The electronic-informatic world is very very very strange :o
Regards
Thierry
Next time I'll try to use Eoscard on an old PC (it's not because I run Mac that I should not own an old PC - everybody has got candles at home, although everybody uses electrivcity) ;)
Quote from: ThLDQ on August 25, 2013, 07:13:21 PM
Thank you Arrinkiii,
I finally succeeded in reinstalling ML.
I followed the Mac instructions, but there was still a problem (7d freezed), I guess it was because the DCIM and MISC directories had not been created by my 7d... Who knows ???
I formatted twice or three times, on my Mac, on a PC, on the 7d, changed AUTOEXEC.BIN in autoexec.bin and now it works.
The electronic-informatic world is very very very strange :o
Regards
Thierry
Next time I'll try to use Eoscard on an old PC (it's not because I run Mac that I should not own an old PC - everybody has got candles at home, although everybody uses electrivcity) ;)
hahaha ;D
Good to see that you have manage to put working the new ML.
Here are some good news to 7D ML users ;)
http://www.magiclantern.fm/forum/index.php?topic=7503.msg70000#msg70000
Where is the Canon 7D ML Alpha 2 Firmware download link for Mac please?
Quote from: Thierry on August 30, 2013, 10:56:55 PM
Where is the Canon 7D ML Alpha 2 Firmware download link for Mac please?
Please kindly read the first post. Or even the last two or three pages. You will find a link to a thread explaining in great detail how to install the latest beta.
Please carefully read that thread as there is information there on how to install on a Mac.
Or if you are lazy, click here:
http://goo.gl/NmIUja
** edit**
As a side note, i personally find it amusing how many people have clicked that link. Would you believe a hundred! lol.
haven't tried the latest builds, but have the audio meters return also to the screen when NOT recording? i'd find this a major design flaw or bug to be honest.. but that's just my two cents.
Quote from: mburgst on September 03, 2013, 12:25:20 PM
haven't tried the latest builds, but have the audio meters return also to the screen when NOT recording? i'd find this a major design flaw or bug to be honest.. but that's just my two cents.
Still work in progress. You can follow here http://www.magiclantern.fm/forum/index.php?topic=7503.0
Quotebut have the audio meters return also to the screen when NOT recording?
If its like EOSM there is an ALV task, it doesn't run unless canon volume meters are on. It powers off the audio IC when canon audio meters aren't running or you're not recording. Granted on 7D its probably patchable, on EOSM it froze the camera.
So who's design flaw is it?
Has anyone ever had focusing issue with the 7D with ML?
In particular, using the 28mm 1.8, sometimes when I mount the lens, it just won't focus, the focusing would hunt and just stops at the closest position, not unlike when failing to focus in dark conditions. Using other focusing method, it would sometimes focus but with horrendous back focus.
I would have to remove the card, and focus a few times, which would nail the focus perfectly, then it would work great. Loading the ML again, it would work perfectly.
This happens to me several times before, only with this lens and I can't seem to reproduce it because it happens so randomly....
Any ideas?
I don't remember but some one already have that problem here in ML forum.
with the first 2 alpha Versions sometimes all but the center focuspoint refused to work (in easy situations to focus)
after restart they all worked properly...
with the latest raw-versions this diddnt happen until now, but I didnt photograph very much with it, more playing with raw-video ;D ;D
Well, I'm trying out 1%'s new build he just posted yesterday, and the focusing problem has gotten worse. Now my other lenses would fail to focus. (it would hunt and rest at the closest focus point or have extreme backfocusing).
Restarting without ML wouldn't make it go away. I had to do a battery pull and turn the camera on with MAGIC OFF or use a non-ML card to get the focusing back.
I wonder if anyone else can confirm this? I find that other guy with the same problem with his 7D buried several page back.
Quote from: feureau on September 09, 2013, 05:55:52 PM
Well, I'm trying out 1%'s new build he just posted yesterday, and the focusing problem has gotten worse. Now my other lenses would fail to focus. (it would hunt and rest at the closest focus point or have extreme backfocusing).
Restarting without ML wouldn't make it go away. I had to do a battery pull and turn the camera on with MAGIC OFF or use a non-ML card to get the focusing back.
I wonder if anyone else can confirm this? I find that other guy with the same problem with his 7D buried several page back.
The same happened with me yesterday when I've installed the latest ML from the main repo: the lens couldn't find focus just hunt and rest at the closest focus point.
That's why I'm not using ML when I want to take photos... but I couldn't resist to see some new stuff...
I think this is the biggest issue on 7D which needs to fix if we want to go further...
Quote from: Pelican on September 09, 2013, 06:20:13 PM
The same happened with me yesterday when I've installed the latest ML from the main repo: the lens couldn't find focus just hunt and rest at the closest focus point.
That's why I'm not using ML when I want to take photos... but I couldn't resist to see some new stuff...
I think this is the biggest issue on 7D which needs to fix if we want to go further...
I concur. Just glad this is not specific to my 7D. I carry some extra CF cards for non-ML shootings now.
How's Brasil working out for you btw? :3 got some nice pics you could share?
QuoteThe same happened with me yesterday when I've installed the latest ML from the main repo: the lens couldn't find focus just hunt and rest at the closest focus point.
Shot a bunch today and I even set AF patterns from canon (yay, maybe portable?), no problems. Hopefully I can reproduce this and see what is going on.. in audio 7D had some bad stubs so maybe its related to that, I'll have to check them all.
Quote from: 1% on September 09, 2013, 08:48:24 PM
Shot a bunch today and I even set AF patterns from canon (yay, maybe portable?), no problems. Hopefully I can reproduce this and see what is going on.. in audio 7D had some bad stubs so maybe its related to that, I'll have to check them all.
I'm going to be on the lookout for how to reproduce this, but it usually happens when I'm changing lens. As in the previous lens would autofocus fine, then changes lens, and it would fail.
Got a random error70 while shooting liveview. Log file: http://www.mediafire.com/?7kvay228dkoifk7
Btw, it seems changing lenses causes the autofocusing issue.
Changing lenses while camera is off? In that log I just see a bunch of AFing/face detection and not the actual error.
Same thing happened to me today, randomly.. Err 70. And also the 7D froze randomly too.. was changing lenses all day but *I THINK* the err70 was during that, not sure though.. will post the log in a little while as I forgot my card reader and gotta find my old one.
Here, the 2 Logs. The first one the camera froze suddenly.. liveview froze and if I turned the camera off or touch any buttons liveview was still active but frozen. Had to remove the battery to make the camera shut down.
The second one, also randomly, Err 70.
Hope the logs are ok: http://www.mediafire.com/?l7x0b9zylrns4u6
Thanks!
Quote from: feureau on September 09, 2013, 06:56:20 PM
How's Brasil working out for you btw? :3 got some nice pics you could share?
One of my favourite:
(http://pel.hu/pic/IM7_126569.jpg)
more on my site
Quote from: 1% on September 10, 2013, 10:14:20 PM
Changing lenses while camera is off? In that log I just see a bunch of AFing/face detection and not the actual error.
While camera is on, mostly.
I'm not sure what caused the err70, but that's the only log file I see in the card...
Quote from: feureau on September 11, 2013, 01:03:51 AM
While camera is on, mostly.
I'm not sure what caused the err70, but that's the only log file I see in the card...
As an aside, I was told never to do that since the electronics can act like a magnet for dust... Am I missing something?
@Pelican Looks amazing!
-Edit-
How make files cropmark.bmp?
I made it, but it have 1,4 Mb, instead of 7 Kb of origin ML. Finally I finish to create a littke bmp 7kB with XnView (Great software photo free), but once selected in the menu ML,it does not display known the LCD screen, as if it was transparent.
With what free software we can save as a little kB bmp, and which is compatible with the ML menu?
All it tells me is that LV crashed when the player tried to run... (PUB) ReleaseImagePlayDriverResource 2395 then err 70.
Were you taking photos in LV?
Quote from: 1% on September 11, 2013, 04:43:23 PM
All it tells me is that LV crashed when the player tried to run... (PUB) ReleaseImagePlayDriverResource 2395 then err 70.
Were you taking photos in LV?
Yes, taking photos in LV going back and forth between that and previewing photos.
Makes sense, probably raw zebra or something like that crashed it when grabbing the CR2 data. I'll see if I can reproduce it.
Quote from: 1% on September 09, 2013, 08:48:24 PM
Shot a bunch today and I even set AF patterns from canon (yay, maybe portable?), no problems. Hopefully I can reproduce this and see what is going on.. in audio 7D had some bad stubs so maybe its related to that, I'll have to check them all.
I noticed autofocus problems after i turned it on after an auto-power off. It was focusing right when i started, it auto powered off. After that it lost the will to focus.
Quote from: Thierry on September 11, 2013, 04:33:52 PM
How make files cropmark.bmp?
I made it, but it have 1,4 Mb, instead of 7 Kb of origin ML. Finally I finish to create a littke bmp 7kB with XnView (Great software photo free), but once selected in the menu ML,it does not display known the LCD screen, as if it was transparent.
With what free software we can save as a little kB bmp, and which is compatible with the ML menu?
Hi,
This will help.
http://magiclantern.wikia.com/wiki/Cropmarks
A newbie questions, I hope I'm on the right thread.
1. For the 7D without ML hack, what format is its' HDMI output?
2. Does the ML hack change the HDMI output format? If yes, into what?
Btw, why is it that H.264 video hacks settings aren't saved when shut down?
Is there a way to make it default to GOP 1? (I can't seem to find a setting in the CFGs for this)
Quote from: feureau on September 13, 2013, 03:53:35 AM
Btw, why is it that H.264 video hacks settings aren't saved when shut down?
Is there a way to make it default to GOP 1? (I can't seem to find a setting in the CFGs for this)
It'll be nice for the settings to be saved upon reboot. I think it is like that cause the bitrate module was still experimental.. haven't fully tested it myself..
Quote from: tonybeccar on September 13, 2013, 05:12:30 AM
It'll be nice for the settings to be saved upon reboot. I think it is like that cause the bitrate module was still experimental.. haven't fully tested it myself..
It's quite stable by now, though you need to know which settings work according to the framerate being recorded or it will keep crashing when you record.
Also, the flush rate is still limited to 50, which means you can't flush right at 60p.
Maybe adding a preset alongside having these settings saved upon reboot would help.
Hey guys, Stupid question. I got the alpha 2 setup on my camera and everything seems to be working as it should. However, I cannot figure out how to make it record raw? I read around the forum and saw there should be some option to enable it, but I cannot find it.
Any help would be great!
7D Raw Builds: http://www.magiclantern.fm/forum/index.php?topic=7987.0
7D Raw Thread: http://www.magiclantern.fm/forum/index.php?topic=7503.0
Installing ML on the 7D/Enabling Bootflag: http://www.magiclantern.fm/forum/index.php?topic=7464.0
Hi guys, will there be a release in the near future, which only can be copied on the memory card and be loaded automatically without these workarounds and stuff?
Thanks for your feedback.
Quote from: SLVRBCK on September 15, 2013, 02:08:25 PM
Hi guys, will there be a release in the near future, which only can be copied on the memory card and be loaded automatically without these workarounds and stuff?
Thanks for your feedback.
Already happened. Look one post above you for updated files.
Wondering, will the EOSutility download the latest version? or should we keep downloading from this thread?
For me is highly unlikely that Canon will modify EOS Utility in order to download/install an alternative/not official firmware, but never say never.
Quote from: Pileot on September 16, 2013, 11:13:08 AM
Wondering, will the EOSutility download the latest version? or should we keep downloading from this thread?
If you mean EOScard:
Magic Lantern v2.3.NEXT.2013Aug26.7D203
Mercurial changeset: ae3d28ed855c+ (unified) tip
Built on 2013-08-26 04:01:59 by magiclantern@magiclantern-VirtualBox
Derp sorry, yeah EOScard.
It would be nice to list in the program somewhere what verison of ML is being downloaded instead of loading it on the cam, then going through various menus to check the version and date info.
Is there a mostly stable FPS override? Last I knew you could set the settings but it wasnt applying and I havnt noticed anyone mention its fixed. that being said there is a lot of movment in these threads and it is easy to miss something like that. Anyways thanks for the replies! Progress on this project is amazing!
Quote from: Pileot on September 16, 2013, 08:33:01 PM
Is there a mostly stable FPS override? Last I knew you could set the settings but it wasnt applying and I havnt noticed anyone mention its fixed.
FPS override still needs a workaround. If you want to use in especially in crop mode, you have to load the fir everytime you turn on the camera by firmware update in canon menu.
Greetz to all.
now it's nearly one year @ Alpha State,
is there any eta for release Candidate?
bye
Lothar
Hi!
Yesterday I played around with "Silent Picture" and I wonder why my DNGs are all 868x578.
I couldn't find any post regarding this topic. I also thought, I could change the picture size by increasing the liveview size in the "raw record" menu.
But it won't allow for anything bigger than 1728px...
Cheers, ray
Quote from: ray_tracer on September 19, 2013, 10:19:06 AM
Hi!
Yesterday I played around with "Silent Picture" and I wonder why my DNGs are all 868x578.
I couldn't find any post regarding this topic. I also thought, I could change the picture size by increasing the liveview size in the "raw record" menu.
But it won't allow for anything bigger than 1728px...
Cheers, ray
At 1x, maximum is 1728. At 5x, maximum is at 2.5k
Quote from: feureau on September 19, 2013, 12:02:15 PM
At 1x, maximum is 1728. At 5x, maximum is at 2.5k
It seems my picture viewer "Irfanview" interprets the ML DNGs as 868x578. Wonder why...
Tried it with ACDSEE Pro; size is now 1736x1156, but the picture get rendered totally black. (And no, I did not take a picture of my lens cap :) )
Each 'pixel' in the 868 x 578 image is actual four channels of the raw unprocessed image. If you magnify the image 400% you will see the color mosaic raw image in all its pre-bayered glory.
Some error70 logs: http://www.mediafire.com/download/cesha2anryhunfw/error_logs.zip
I think it's mainly from turning on defishing and/or raw videos....
At least I can reproduce defishing errors every time. Just have defishing on and go to live view with raw video.
The memory manager fixes this but breaks signed FIR stuff.
Quote from: 1% on September 24, 2013, 04:19:48 AM
The memory manager fixes this but breaks signed FIR stuff.
Memory manager? Is this a module or something?
ALso, is there a way to get video hacks to be saved? And make video hacks to not disable canon audio every time it's loaded?
Yea, memory needs to be fixed in the FIR, then you get video hacks, fps, more stable H264, headphone, etc. And no crash with defish.
Maybe you can change the gop and leave sound on but flush rate shuts it down and stop the video unless there is a way to patch audio.
Quote from: tech411 on September 23, 2013, 04:36:05 PM
Each 'pixel' in the 868 x 578 image is actual four channels of the raw unprocessed image. If you magnify the image 400% you will see the color mosaic raw image in all its pre-bayered glory.
Switched to Raw Therapee. This did the trick...
thx!
Quote from: 1% on September 25, 2013, 01:16:23 AM
Yea, memory needs to be fixed in the FIR, then you get video hacks, fps, more stable H264, headphone, etc. And no crash with defish.
Maybe you can change the gop and leave sound on but flush rate shuts it down and stop the video unless there is a way to patch audio.
I see. thanks for the explanation.
Sorry if this is the wrong thread, pls move if it is.
I am running
V2.3.NEXT.2013Sep02.7D203
Mercurial changeset 63c523d7a208 (unified) tip
Built on 2013-09-02 01:42:29 UTC
and when the camera is physically turned off the battery goes dead after a few days. It used to last at least a month in sleep mode while I used film cameras. If I let the camera go to sleep (switch on, camera off) the battery also dies in a few days. The card door has not been opened. Does not happen with a plain card or no card in the slot.
This also happen to me sometimes... but i take the card out and for that i think is because of that (need wait until red light shut off) but if you say that you don't take the card out... What i do sometimes, after i turn off the camera i take out the battery and insert again... just for in case... Maybe some one got the same dry battery here in the forum.
Hello,
What is the maximum permissible temperature for the CMOS?
Quote from: maxim34 on September 28, 2013, 11:07:27 AM
Hello,
What is the maximum permissible temperature for the CMOS?
Above 200 and the CMOS police will pull you over.
I want to refresh the ML zip used by EOScard.
Which one do you recommend?
(The one which is more or less stable and worked for many of you.)
I think the last one is good 24/09/2013
but maybe is possible for britom to make a new build with the update's and also in the others modules
http://www.magiclantern.fm/forum/index.php?topic=7987.0
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/all
The latest Britom's build is quite stable to me, test shooting raw one afternoon, no ERR encountered. Cannot remember any significant issues, but the write speed varies a lot.
Quote from: britom on September 14, 2013, 10:46:56 PM
...
Installing ML on the 7D/Enabling Bootflag: http://www.magiclantern.fm/forum/index.php?topic=7464.0
This one is for the latest features. The latest features don't work for me (because of previous features are missing). Is there a way to make the original 7D beta2 into auto reboot?
For now no and don't know if in the future will be possible. For getting the latest features you need to bootflag your camera.
Quote from: Pelican on September 30, 2013, 02:00:08 PM
I want to refresh the ML zip used by EOScard.
Which one do you recommend?
(The one which is more or less stable and worked for many of you.)
Like arirnkiii said. the 24th works flawlessly.
I'm trying out the 29th build but it seems to work just great too. Might want to try this build and use that for the EOSCard update instead.
I've uploaded ML_britom_1%_29_Sep_2013_.zip (http://pel.hu/ML/ML_britom_1%_29_Sep_2013_.zip) to my site, so EOScard uses this from now.
(I hope the % sign doesn't make any trouble...)
Edit:
Renamed to ML_britom_1_29_Sep_2013.zip (http://pel.hu/ML/ML_britom_1_29_Sep_2013.zip)
Awesome. Thanks, Pelican!
It give's me a error 400: bad request
http://pel.hu/ML/ML_britom_1%25_29_Sep_2013_.zip
To use % in HTML you have to use %25 instead. ;-)
Ciao
Walter
Thanks. I've renamed the zip.
Excellent work all. I was perfectly happy with using the Alpha 2 for video, except for the one thing - I wanted a bootable version. This was because I am using a non Canon AC adaptor and the camera won't allow the installation of ML (it asks me if I know that I'm not using a factory battery and when I say yes, reboots back into the vanilla system).
I made my usual changes, CBR 1.2, turn off x5 zoom option and tweaks to allow me two profiles - one with zebras, focus peaking using yellow dots in greyscale and the setting to bring up the 3x focus box in the top left at a half press of the shutter which also restores colour (this is the main profile I use) and another profile with false colour and the level line which I use to check brightness ranges and, of course, horizontal leveling. This is how I've used ML since the alpha 2 came out and it's a very useful addition to my 7D, in combination with the VAF-7D anti-moire filter.
However, whenever I used an external mic (I use a small clip-on, not really lavalier, that came with my Microtrack II audio recorder) the system was flaky. I was disappointed as this meant I was likely going to have to go back to the non-booting alpha. I spent an hour or so switching parameters on and off to see if anything was causing this and lo and behold - the wind filter! When I switched it off, the audio came back, the camera stopped freezing and it was back to normal. I just wanted to give this hint in case anyone else was having the same problem. I haven't used the system for long, so it may still have issues, but for now it seems great. I don't need the wind filter with my external mic, it has it's own foam covering that seems to do the job. This is meant to be for sync audio, or at least that's the intention but it seems I end up using a lot of audio from the camera, in particular when I don't have time to setup and switch on the Microtrack. With the mic plugged in, I get reasonable sound as I can position the mic several feet from the camera closer to the subject which is often a better solution than a higher-end mic mounted on the hotshoe (I'm an audio professional by trade, not in the video world).
The only things to comment on are that the full-frame equivalent display (50mm for example) is sort of overlaid with other text, but I can read it fine. I also have some weird characters displaying on the screen in various locations on playback but I can certainly live with both of these.
I'm not using any of the extra modules (for now) as I just want to get video recorded with a minimum of fuss and a maximum of feedback and I have that without trying any of the new features.
Thanks everyone for their help, instructions and utilities that have allowed this. I love the new look as well.
Hi guys, does anybody know the complete process to get to shoot raw video with the 7D through ML alpha 2 ? Thanks in advance for the help...
Alpha 2 does not support raw:
Try this:
HOW TO: A guide to installing ML on the 7D with recent features
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Hello Guys ,
I got last firmware Canon V2.0.3 & Magic Lantern Alpha2 (via CF) on my Canon 7D, but I can't find the Raw Video Module on my 7D, did I miss something ?...
Thanks for sharing :D
@Eddy: Look at the post exactly above yours
What was it doing to audio with wind filter on? I can hardly tell the difference with it on/off.
Quote from: 1% on October 04, 2013, 03:59:04 PM
What was it doing to audio with wind filter on? I can hardly tell the difference with it on/off.
supose to cut some frquencies (wind frequencies) ?
Its supposed to be a HPF/LPF but I'm wondering what it did to his external and if 6d actually needs the setting added (same audio ic)
Yes for hi frequencies and low. Can be helpful in camera but in post u can do it easily. For me audio in post is the best, with good speakers. in camera only need good meters and of course a good input/sound. Some mic's also have this feature of hi and low pass.
@ Pelican
Im having problems with the download of EOScard... it's seems that it don't download
I don't know if Pelican has already fixed the problem but the download is ok for me, tried right now.
Quote from: arrinkiiii on October 04, 2013, 07:17:24 PM
@ Pelican
Im having problems with the download of EOScard... it's seems that it don't download
What is the problem?
Downloading EOScard itself or downloading the ML zip?
Two days ago i have problem enter in your website and download the eoscard... going to try again :)
Edit: I go here http://www.pel.hu/eoscard/ and it's stay for ever for enter in the web site, maybe is my computer/internet but this never happen to me and i can go to other websites =(
Don't know if it's been mentioned: Is it possible to disable the automatic audio gain? For me the most important feature.
What do you mean?
Auto gain control? This is optional in Canon's menu with firmware 2.0.3.
Ciao, Walter
Perhaps I'm mistaken: I don't mean controlling the levels of an audio track, but rather an automatic gain when using an external mic. If a scene becomes too quite, the 7D raises the volume, creating a hissing effect. I had 2.0.3 from the get go, so I can't think of a way of disabling it for external mics. If I'm wrong, can you point me to a solution? Thanks :)
Strangely enough: As I tried it just now, the hissing was gone. Maybe I did something wrong the last time. Thanks anyway. :)
Quote from: arrinkiiii on October 06, 2013, 03:29:34 PM
Edit: I go here http://www.pel.hu/eoscard/ and it's stay for ever for enter in the web site...
Working fine for me.
Quote from: angelom on October 06, 2013, 05:35:33 PM
Working fine for me.
Just downloaded eoscard. Works fine for me. Almost accidentally hit the donate button. *phew* That was close.
Quote from: feureau on October 06, 2013, 07:05:39 PM
Almost accidentally hit the donate button. *phew* That was close.
Huhh. Almost got my first donor... :P
I have manage to download 2 times that take me more that 5 minutes to download 839kb and the third time still is downloading (more than 5 minutes).
Never have this problem but tomorrow will try on other computer to see and also try to use in the card (that i didn't manage to do yesterday). For sure that the problem is in my computer or in my web connection. I download a file in piratebay with 700Mb in 5 or 10 minutes.
Purposely i have click in donation button, but just don't go anywhere... please, let me be the first one!
Edit: fixed my issue. thanks.
Quote from: arrinkiiii on October 07, 2013, 12:19:59 AM
I have manage to download 2 times that take me more that 5 minutes to download 839kb and the third time still is downloading (more than 5 minutes).
Never have this problem but tomorrow will try on other computer to see and also try to use in the card (that i didn't manage to do yesterday). For sure that the problem is in my computer or in my web connection. I download a file in piratebay with 700Mb in 5 or 10 minutes.
Purposely i have click in donation button, but just don't go anywhere... please, let me be the first one!
I've checked the site but looks OK from here.
The donation button didn't work until now (Thank you for report it!) but I've fixed it so if you are quick enough you can be the first... :)
Now to even can enter in website =(( Today i didn't have the oportunity to try in different machine and different internet service. Hope tomorrow i can.
Now yes, download it in 2 seconds =)) I have send you paypal, for now is like that, need to wait :)
Following the steps given by britom on page 31, it seems to me that the EOS Utility 2.8.1 no longer exists in the linked dropbox location. Any help? To my understanding it needs to be this exact version of EOS Utility, or will the newer ones do as well?
BTW big thanks to the amazing Magic Lantern Team for their great work and to everyone involved!
Quote from: Moon on October 09, 2013, 01:05:48 PM
Following the steps given by britom on page 31, it seems to me that the EOS Utility 2.8.1 no longer exists in the linked dropbox location. Any help? To my understanding it needs to be this exact version of EOS Utility, or will the newer ones do as well?
BTW big thanks to the amazing Magic Lantern Team for their great work and to everyone involved!
You don't need the EU at all...
Quote from: Pelican on October 09, 2013, 04:22:19 PM
You don't need the EU at all...
Are there some detailed instructions how to do it without the EU? I tried to look around this thread but maybe I missed it. I'm a bit hesitant to start working outside of the instructions because even in the simplified steps on the wiki page it says that the second step involves using EOS Utility..
you don't need EU. use pelican's Eoscard instead.
OK I have been trying to follow the instructions step by step, but I'm sure I did wrong somewhere because when trying to update the firmware with the patched one on the camera menu, I get the following message: "Firmware older than ver. 2.0.0 is on memory card. Delete old file and update using later version."
The firmware on my 7D is version is 2.0.3 and the version I dowloaded from britom's link is 1.2.3, so my question is should I download the newest firmware version and try to patch that one with the given instructions?
I think you read the wrong installation guide. Use this one:
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Ciao, Walter
Pelican,
Can you do a version (even command line only) of EOScard for Linux (perhaps in source form)?
Hi guys,
I used ML Alpha 2 on my 7D a lot lately and really loved it. But today i ran into some trouble.
I was taking pics as usual, camera went in standby and then it happend. I couldn't power the camera on again.
So here is what i did:
-) Remove the battery(both of them[battery grip]) and waited
-) Removed the batterygrip and tried with one battery
-) made sure the battery was fully charged
-) removed the buffer battery for about 20 minutes
-) removed my primary CF card(with magic lantern in it) for 20 minutes
-) changed the lens
None of the above worked, i couldn't turn the camera on again. No red light when putting the card or battery in, just no reaction
So, what got my camera back to life?
-) Removed the magic lantern CF card,
-) removed the batteries for 5 minutes
-) inserted a fresh formatted card
Camera booting again, everything fine
But: i wanted to read out the images of the (corrupted) card on my PC. Windows told me, that the card has to get formatted. Linux(Arch) told me, the card contains a bad superblock.
So I'm here right now, rescuing the data from the card. This whole thing caused me no real damage, but it would be a pain in the ass, if I really would need my camera and this would happen again.
Long story short: Still in love with magiclantern BUT: how did this happen? Is there a way I can get a log file or something I could send the developers? How can I avoid such failure?
Thanks and keep up the great work
Flash cards fail. Its a fact of life. I'm going to bet its less of a problem with magiclantern and more of a problem with the card itself.
Basically, each memory slot in the card has a limited life span, a limited number of read/write cycles before it will wear out, kind of like tread on your car tires. There are lots of fancy ways that the card controllers can wear the cards evenly (cycling through every memory 'slot' before starting at slot 1 again, etc) but eventually the cards will fail.
Usually these cards are rated at the tens or hundreds of thousands of cycles and its a non issue, the card will be obselete before it fails (how many of you are still using your 50mb cards from 5 years ago? thats what I thought) HOWEVER...
Most people buy the least expensive card they can because, lets face it, we are limited by our budget.
Most people will keep using a old card as long as they can before its not worth using (like most of my friends using 4gig cards in their current gen camera bodies).
A lot of people buy cards from ebay or third parties
Some stores sell counterfeit cards without even knowing it!
This is a problem because the lower quality flash chips (the ones with the memory 'slots' holding your picture information) will either wear faster (always write to slot 1 first, then slot 2, etc. instead of sequentially) or have a lower number of cycles before it fails.
What can you do? Well personally, I research my cards before I buy them. How fast the card is is only half the equation. What sort of warrenty do they have on their cards? How do I get a broken card replaced (varies from manufacturer to manufacturer), is it a trusted name brand? do they have a PSA about fake cards and how to identify them?
The last cards I bought have a lifetime warrenty. Other's that I was looking at had a 3 month warrenty. Which one do you figure is going to fail faster? Any pro photographer who has been in the business a while can tell you horror stories of cards failing. When the shot really counts its worth having quality equipment.
TL:DR - You get what you pay for. :)
Forgot to mention, this is why I always carry a couple cards when shooting events, not in case they fill up (64 gig cards ftw) but if one were to fail I wouldn't want to be dead in the water :)
Thanks for your reply.
Well it could be the card, but i don't believe so. The card isn't the cheapest one(Kingston 600x), sure not a fake nor is it very old(2 months) and hasn't many read/write cycles.
So, of course it could be, that the card is broken, but i will figure this out with a bunch of tests.
[edit] ran some tests with linux and windows on the card. No errors, everything fine :-X
Curious, which program did you use to test? I know some will only test accessable sectors (not written) where others will format the card and test every sector. Any test that will erase data on the card likely tests every sector.
Some cards fail prematurely, some last longer than advertised, but if you did a readwrite test on every sector and it ran through several times with no problems chances are your card is fine. :)
It is also possible there was a glitch when files went to be written and that caused the data to be corrupted. Could be any number of things, loss of power while trying to write to the card, battery or card door was opened or card was ejected before the data could be written, non OEM battery running out of power unexpectedly, random surge of power, hell the list of things that COULD under the right conditions cause problems is as long as my arm.
If your card is fine and you can't see any problems personally I'd get the latest version of EOScard, throw the current "stable" build of ML on there and not worry about it. As previously mentioned I have several cards but only once have had issues where I didnt properly set the bootflag on one of my cards. The only time i'd have cause for concern is if the problem is repeatable but I think its unlikely (tho possible under the right conditions) that ML is causing your headaches.
Good luck!
I tested the card with ChkFlsh under Windows and with Linux, i wrote random data at it with dd if=/dev/random of=/dev/sdd1 bs=1k and vice versa tested for reading with dd if=/dev/sdd1 of=/dev/null bs=1k.
No errors occured with the Windows nor with the Linux version. So i would i say, the card is fine.
Thanks for your reply, I'm aware of the causes that might lead to corrupted data. I just wanted to ask here, if maybe this behavior is know and if this was really was triggerd by magiclantern, if there would be a chance to get a log or so.
But, regarding all facts, it might really just have been corrupted data. So i'll install ML again and be happy :)
thanks :)
Hi!
Sorry, but I'm a little bit confused, because of the RAW developement ;-)
Which version do I have to use, to get the best Bitrate-features for h264? You know, before RAW came up, there was the Bitrate-Monster Thread with the settings for All-I and so on. I wanna use them...
Greets
Quote from: _7D_ on October 23, 2013, 08:31:34 PM
Hi!
Sorry, but I'm a little bit confused, because of the RAW developement ;-)
Which version do I have to use, to get the best Bitrate-features for h264? You know, before RAW came up, there was the Bitrate-Monster Thread with the settings for All-I and so on. I wanna use them...
Greets
Go with britom's fps disabled bundle. Check his signature for download links.
I don't understand it. So, do I have to choose a version without a signed fir or with a signed fir? Or should I just install the latest ML (09/10/2013)? Sorry for that ;-)
Video hacks only worked on signed fir.
Thanks. I've just installed TL from yesterday (Nightlys...-.fir included), but if I do the firmware update to get the video hacks, my camera freezes when I want to turn on video hacks. So I guess I've installed the wrong ML/TL, if I want to use Bitrate Settings with Flush-Rate etc.
EDIT: It seems like the 12/09/2013 firmware works. So this is the best and newest firmware, if I don't wanna use RAW Video, but wanna use the h264 hacks like GOP and things like that. Right?
Yep, use older signed fir and if you want modules make sure to use the sym file that came with it.
Toggling video hacks too much seemed to freeze it but otherwise worked OK. I haven't made too many new firs because really this is the only thing left in them, I don't recall the vignetting working right.
i can replicate the symtoms of sort of dead camera
i follow this guide:
http://www.magiclantern.fm/forum/index.php?topic=7464.0
update the firmware and camera went "dead"
Follow the same solution.
remove the CF card
remove the 2 batteries (no need of 5 minutes)
even if i use the cf card camera just froze. no lcd, nothing. like dead.
careful.
isn´t the CF. is posible that magic lantern.
Put CF-card into cardreader, format with NTFS, insert CF-card into cam, format there.
Results?
Ciao
Walter
Wow what a ton to read thru, but 7D raw video is worth it !! ;D
Looks like most of these files are .exe, anyone have a how to link for mac users ?
Can we use our existing cards or do we need something faster ?
http://www.amazon.com/Sandisk-Extreme-CompactFlash-Memory-SDCFX-016G-A61/dp/B007XZKMKI/ref=sr_1_16?s=electronics&ie=UTF8&qid=1383324481&sr=1-16&keywords=sandisk+64mb+16GB+compact+flash
Quote from: twocik on November 01, 2013, 05:57:30 PM
Wow what a ton to read thru, but 7D raw video is worth it !! ;D
Well, in my opinion, this is a mess. One shouldn't have to read through nearly 60 pages of forum posts to get something working. I hope some day soon the core ML devs will advance the official development and release new, official, alpha, beta or stable versions!
Quote from: twocik on November 01, 2013, 05:57:30 PM
Looks like most of these files are .exe, anyone have a how to link for mac users ?
Here's a how to for the Mac: http://www.magiclantern.fm/forum/index.php?topic=7752.0. Note that it uses an outdated build, though. But I don't have the time to read through half the ML forum to figure out which build to use, where to get it and how to install it. So I'll just wait for the next official build.
Hi all
Really excited about some of the new developments here!
Been using the alpha for a while shooting some bits at a mates club every couple of months and just checked here the other day before their Halloween do.
Being kind of busy with other stuff, I read about the bootloading version but decided to go with what I already had working rather than risking something new before trying it out.
Now that's done I've managed to use the EOScard utility to bootload one card - seems to work great.
The new version seems to download all the latest modules too - is that right?
All the modules seem to be there and their info screens when I press "Q" are all saying 2013-09-25 or dates close to that.
Do I therefore need to look for newer builds/releases to try out new features or does the download function for EOScard deliver the most recent automatically?
On another note I read that you can't just copy files from one card to your others but need to make the card "bootable" using EOScard.
Now, previously with the non bootable version this was what I did after setting everything the way I liked I just copied to my other cards.
Therefore, is it now possible to copy my specific settings from a working, setup the way I like it, bootable card to my pc, then make bootable my other cards with EOScard, and then copy my specific settings back across from my pc?
Been reading through a bunch of recent posts so sorry if this has already been covered and I missed it!
And finally - and this is just a wishlist item and I don't know if it is even possible - but some of the stuff you guys have already managed is pretty amazing so I figured I'd ask:
One problem I have is with overheating when shooting for too long. The little red thermostat warning comes on and I know I'm on thin ice!
Once I pushed it as what was happening in front of the lens was amazing and I very nearly got everything but the camera shut itself down before doing itself permanent damage.
It happened again the other night as I was filming too much in a row, so I shut down for a bit and unfortunately missed a really good performance.
What I'm wondering is if there might be some way of introducing a temperature meter of some kind?
Doesn't have to be hyper accurate, just something that reminds me "better think about giving it a rest soon" before it gets to the red flashing symbol and I know I'm already in the danger zone.
Just like a battery percentage type meter maybe?
Just a thought as that would be really handy for me.
Anyone else think this would be useful?
Cheers for all the hard work anyway!
From here you can get the latest version for your 7D.
http://tl.bot-fly.com/
Replace the files from the cf card with the new ones.
Thanks for that!
I've just replaced the ML folder on my CF card with the one from the new build - is this the correct procedure?
Thanks again!
Thanks bkummel & Szigiszmund !
I download the zip file tragiclantern-Tragic - http://tl.bot-fly.com/builds_2013.10/tragiclantern-Tragic.2013Oct31.7D203.zip
Now all I need to do is figure it out :P Any step by step how to videos ?
Thanks guys for all the hard work!
I've upgraded from the alpha 2 to the latest version by szigiszmund by copying the new files to my cf card.
But every time I activate a module, restart the camera and load ML, the camera just stops at the sensor cleaning screen. Even if I turn it off, the screen doesn't turn off and I have to take out the battery. So I cannot test any of the modules.
Does anybody know why that happens?
Thanks in advance!
Take a look here http://www.magiclantern.fm/forum/index.php?topic=7464.0 to see if you do everything its says.
Quote from: robs on November 10, 2013, 06:11:31 PM
Thanks guys for all the hard work!
I've upgraded from the alpha 2 to the latest version by szigiszmund by copying the new files to my cf card.
But every time I activate a module, restart the camera and load ML, the camera just stops at the sensor cleaning screen. Even if I turn it off, the screen doesn't turn off and I have to take out the battery. So I cannot test any of the modules.
Does anybody know why that happens?
Thanks in advance!
There's something about the module not compiling/broken on some of the newest compile. Try downloading the Nov.2 version. Delete everything in your card, and use that. See if that fix anything.
The 9th has MLV_REC + raw_REC
Hi. Can someone explain for me about CHDK and its relationship with ML. Im using Pelican software and it says that CHDK enabled (with ML), but I cant figure it out where is it and how can I use its functions. Actually, Im interesting in a hot peixel removal function. Thanks.
Quote from: szigiszmund on November 10, 2013, 07:05:43 PM
Take a look here http://www.magiclantern.fm/forum/index.php?topic=7464.0 to see if you do everything its says.
I don't know, what I had done wrong, but I have just reinstalled everything and now it's working.
Thanks again.
Btw, 1%, what happened to video hacks in TL? Running Nov.9th version and I can't see the video hacks? Was hoping to shoot some All-I.
Hi, I see errors on Aperture Value in ML Menu 7D alpha 2!
Source :http://en.wikipedia.org/wiki/F-number
My work : http://www.flickr.com/photos/thierrydauga/10839428615/in/set-72157629104813911
Thanks ML for great 7D alpha2 and thanks to correct it :)
http://www.flickr.com/photos/thierrydauga/10840227836/
Sensitivity
http://www.flickr.com/photos/thierrydauga/10873096105/in/photostream/
Time speed
http://www.flickr.com/photos/thierrydauga/10873236924/in/photostream/
Good morning everybody.
Does stack focus work on 7d ?
I can't start it.
Thierry
Test this:
Tripod.
Lens AF on.
Liveview.
Select target (minimum focus distance you want) by AF.
Open Focus Stacking submenu and choose "Num. pics behind" = 10.
"Focus steps /picture" 3 or higher.
Highlight "Run focus stack" and press SET.
Report results.
Ciao
Walter
Hi, Walter.
I followed your procedure and it works.
So, I undestand that "Focus end point" is used just to show how many steps are needed to get the desired DOF.
And that the number of steps are the result of "number of pictures x focus steps/pictures).
For example :I need 12 steps to achieve the DOF I want, I decide either "4 pictures x 3 steps" or "3 pictures x 4 steps"
Then according to the focus start or end point I choose how many pictures I want "in front" if I choosed the focus end point, or "behind" if I choosed the focus start point.
Correct me if I'm wrong
That was not clear at all to me.
Thank you Walter.
Regards
Thierry
This was just a test procedure to find out if your camera/lens combination is able to deal with focus stacking at all.
This workflow fit my needs (static macro objects, M about 1:3 to 2:1) and I'm a beginner for all other options. I'm waiting for Marsu42 to jump in for the rescue. Those are "his" routines (if I got it right) and the coding involved is beyond me.
Ciao
Walter
Ok Walter.
Do you think that the delay between two pictures is long enough for the internal flash to rearm (the battery of my 7d is down so I can't check).
Thierry
"Fokus Settings" -> "Flash Delay"
Quick question. Have any of you noticed that the 7d chews more battery than other canons. Mine regularly pulls around 50%/hour. Is that normal?
That is not normal. What is your battery health status?
It's an old battery. I think it's two out of three bars. I just assumed it was a 7d thing. How long do they normally last shooting video?
The several times that I have test shot with ML raw video shows that ML raw recording is quite savy on battery, a fully charged battery can last pretty long time (say an afternoon plus). That is unexpected because I have piles of batteries in stock (some were prepared for the flashgun).
Btw, anyone knows how to get CHDK working on 7D? I have some quite slow old cards lying around, and I am contemplating shooting dng instead which is directly stolen from some buffer inside the 7D, for I don't trust Canon for its CR2 very much.
Hi, Walter.
Can't find any "Flash Delay" in the Focus setting submenu.
There is only a "Rack Delay". Is it the same ?
I hope it is in seconds, not like the Step delay which is in ms.
Regards
Thierry
Quote from: ThLDQ on November 26, 2013, 06:15:48 PMCan't find any "Flash Delay" in the Focus setting submenu.
Which ML version do you use? My 7D is out of reach for est. 13 hours and I have to verify there is Tragic Lantern from the second november decade installed.
Ciao
Walter
My version is :
v2.3.NEXT.2013Aug25.7D203
Built on 2013-08-25 23:13 UTC by Miguel@Miguel-Pc
Thierry
Found this option in Tragic Lantern Nov22 build. Looked up ML Next Aug06 and feature not available.
Ciao
Walter
Hi Walter,
I'm discovering TL...
Is the TL build this one : "600DNewMem.zip" that I have found here : https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads (https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads)
Thierry
I use 1%'s build. First link in http://www.magiclantern.fm/forum/index.php?topic=7987.0
Ciao
Walter
OK.
I downloaded the latest nightly buid.
I noticed there is a 7D_203.fir in the zip file.
Do I have to update the .fir of my 7d ?
Or only copy the .bin and the directories on my flash card ?
Thierry
Forget FIR, just delete the old ML dir and copy ML dir and BIN onto the card's root.
Ciao
Walter
Thank you Walter.
Good night.
Thierry
New battery and it drains 16% per hour
Hello,
I don't use Alpha Versions for Production!!
AGAIN!!!!
Is there any eta for release?
bye
Quote from: Digi-Quick on September 19, 2013, 04:18:25 AM
Greetz to all.
now it's nearly one year @ Alpha State,
is there any eta for release Candidate?
bye
Lothar
Quote from: Digi-Quick on December 08, 2013, 01:15:24 PM
Hello,
I don't use Alpha Versions for Production!!
AGAIN!!!!
Is there any eta for release?
bye
Bye
*waves*
Quote from: Digi-Quick on December 08, 2013, 01:15:24 PMIs there any eta for release?
Top of page -> User Guide -> FAQ -> Troll Questions. Last one.
lulz... TIL: software developed/used for 6 months+ is "alpha"... the magic stable fairy is going to come down on the code base and fix any bugs in one swoop then christen it what? gamma?
Has anybody tried the new 2.0.5 fw?
I've upgraded my 7D to fw 2.0.5
My third party batteries are still working so there is no big harm in it (like Canon did with 5D3 and 6D).
Dumped the ROM and made a new stubs.S for the new fw version.
very nice, thanks
can anyone halp me understand why I dont see audio lever bars in h264 mode ?
Edit:
If someone want to play with the new platform: https://bitbucket.org/Pelican/7d205/commits/all
For wat i can read the fw update is for FTP protocol via USB... it's only this update?? For photo is good but not so much for video?
Quote from: Pelican on December 12, 2013, 04:16:33 PM
I've upgraded my 7D to fw 2.0.5
Dumped the ROM and made a new stubs.S for the new fw version.
check-stubs output:
05.S
STUB OLD NEW DELTA
next_task_ctx 0x0000067c -> 0x0000067c [0x000]
current_task_ctx 0x00000680 -> 0x00000680 [0x000]
task_dispatch_hook 0x00001934 -> 0x00001934 [0x000]
pre_isr_hook 0x0000193c -> 0x0000193c [0x000]
post_isr_hook 0x00001940 -> 0x00001940 [0x000]
gui_main_struct 0x00001bf4 -> 0x00001bf4 [0x000]
sounddev 0x00001f54 -> 0x00001f54 [0x000]
dm_names 0x00002b18 -> 0x00002b18 [0x000]
task_max 0x00002b24 -> 0x00002b24 [0x000]
gui_timer_struct 0x00003624 -> 0x00003624 [0x000]
mvr_config 0x0000a39c -> 0x0000a39c [0x000]
additional_version 0x00016fb8 -> 0x00016fb8 [0x000]
gui_task_list 0x0001a904 -> 0x0001a904 [0x000]
sd_device MISSING -> 0x000208d8 [?????]
cf_device 0x00022938 -> 0x00022938 [0x000]
bmp_vram_info 0x00029a60 -> 0x00029a60 [0x000]
LCD_Palette 0x00029a9c -> 0x00029a9c [0x000]
vram_info 0x0007e9e8 -> 0x0007e9e8 [0x000]
camera_engine 0xc0220000 -> 0xc0220000 [0x000]
cli_save 0xff0104bc -> 0xff0104bc [0x000]
sei_restore 0xff0104d0 -> 0xff0104d0 [0x000]
cstart 0xff010fb0 -> 0xff010fb0 [0x000]
get_current_task 0xff014c10 -> 0xff014c14 [0x004]
create_init_task 0xff01559c -> 0xff0155a0 [0x004]
_malloc 0xff0162f0 -> 0xff0162f4 [0x004]
_free 0xff01634c -> 0xff016350 [0x004]
init_task 0xff018734 -> 0xff018738 [0x004]
gui_main_task 0xff021b44 -> 0xff021b48 [0x004]
GUI_Control 0xff021f04 -> 0xff021f08 [0x004]
GUI_ChangeMode 0xff022004 -> 0xff022008 [0x004]
gui_init_end 0xff022680 -> 0xff022684 [0x004]
PD_RemoteRelease 0xff0372b4 -> 0xff0372b4 [0x000]
StartASIFDMAADC 0xff061a88 -> 0xff061a5c [0x02c]
StartASIFDMADAC 0xff061c44 -> 0xff061c18 [0x02c]
StopASIFDMADAC 0xff061d20 -> 0xff061cf4 [0x02c]
SetNextASIFADCBuffer 0xff0621c4 -> 0xff062198 [0x02c]
SetNextASIFDACBuffer 0xff06227c -> 0xff062250 [0x02c]
sounddev_task 0xff063d64 -> 0xff0638a0 [0x4c4]
SoundDevLock 0xff064034 -> 0xff064008 [0x02c]
SoundDevActiveIn 0xff0640ec -> 0xff0640c0 [0x02c]
sounddev_active_in 0xff0640ec -> 0xff0640c0 [0x02c]
SoundDevShutDownIn 0xff064304 -> 0xff0642d8 [0x02c]
SoundDevStopIn 0xff06494c -> 0xff064920 [0x02c]
SoundDevStopOut 0xff064a1c -> 0xff0649f0 [0x02c]
SamplingParamInRate 0xff064d80 -> 0xff064d54 [0x02c]
SetVolumeInVolume 0xff064ff8 -> 0xff064fcc [0x02c]
SetWindCutMode 0xff0650bc -> 0xff065090 [0x02c]
_prop_request_change 0xff067fac -> 0xff067f80 [0x02c]
prop_deliver 0xff06858c -> 0xff068560 [0x02c]
prop_register_slave 0xff068614 -> 0xff0685e8 [0x02c]
prop_unregister_slave 0xff0686a4 -> 0xff068678 [0x02c]
_prop_cleanup 0xff068734 -> 0xff068708 [0x02c]
prop_get_value 0xff0687c8 -> 0xff06879c [0x02c]
PROP_GetMulticastProperty 0xff0687c8 -> 0xff06879c [0x02c]
PROPAD_GetPropertyData 0xff06934c -> 0xff069320 [0x02c]
MuteOn_0 0xff06d6a8 -> 0xff06d67c [0x02c]
EnableImagePhysicalScreenParameter 0xff06e8b0 -> 0xff06e884 [0x02c]
AsyncEnableImagePhysicalScreenParameter 0xff06edd0 -> 0xff06eda4 [0x02c]
SetBitmapVramAddress 0xff06f2fc -> 0xff06f2d0 [0x02c]
set_brightness_registers 0xff0705e4 -> 0xff0705b8 [0x02c]
MuteOff_0 0xff072290 -> 0xff072264 [0x02c]
_audio_ic_read 0xff072f7c -> 0xff072f50 [0x02c]
_audio_ic_write 0xff0730c8 -> 0xff07309c [0x02c]
PowerAudioOutput 0xff07365c -> 0xff073630 [0x02c]
SetSamplingRate 0xff0736f4 -> 0xff0736c8 [0x02c]
SetAudioVolumeOut 0xff073944 -> 0xff073918 [0x02c]
LoadCalendarFromRTC 0xff075210 -> 0xff0751e4 [0x02c]
DryosDebugMsg 0xff0776ac -> 0xff077680 [0x02c]
dm_set_store_level 0xff077990 -> 0xff077964 [0x02c]
call 0xff07842c -> 0xff078400 [0x02c]
oneshot_timer 0xff078e6c -> 0xff078e40 [0x02c]
BulkOutIPCTransfer 0xff07a704 -> 0xff07a6d8 [0x02c]
BulkInIPCTransfer 0xff07a7d4 -> 0xff07a7a8 [0x02c]
RegisterRPCHandler 0xff07aed4 -> 0xff07aea8 [0x02c]
RequestRPC 0xff07af84 -> 0xff07af58 [0x02c]
gui_timer_something 0xff07b708 -> 0xff07b6dc [0x02c]
create_named_semaphore 0xff07b7c4 -> 0xff07b798 [0x02c]
take_semaphore 0xff07b924 -> 0xff07b8f8 [0x02c]
give_semaphore 0xff07ba0c -> 0xff07b9e0 [0x02c]
msleep 0xff07bdf8 -> 0xff07bdcc [0x02c]
task_create 0xff07beac -> 0xff07be80 [0x02c]
GetMemoryInformation 0xff07cac8 -> 0xff07ca9c [0x02c]
_AllocateMemory 0xff07cd24 -> 0xff07ccf8 [0x02c]
_FreeMemory 0xff07d0b4 -> 0xff07d088 [0x02c]
GetRemainOfMemoryChunk 0xff07de88 -> 0xff07de5c [0x02c]
GetMemoryAddressOfMemoryChunk 0xff07dee8 -> 0xff07debc [0x02c]
GetFirstChunkFromSuite 0xff07e4a0 -> 0xff07e474 [0x02c]
GetNextMemoryChunk 0xff07ec38 -> 0xff07ec0c [0x02c]
msg_queue_create 0xff07fc28 -> 0xff07fbfc [0x02c]
CreateRecursiveLock 0xff07fe0c -> 0xff07fde0 [0x02c]
dma_memcpy 0xff080224 -> 0xff0801f8 [0x02c]
AllocateMemoryResource 0xff080e78 -> 0xff080e4c [0x02c]
AllocateContinuousMemoryResource 0xff080ec4 -> 0xff080e98 [0x02c]
FreeMemoryResource 0xff080fdc -> 0xff080fb0 [0x02c]
task_trampoline 0xff084ca4 -> 0xff084c78 [0x02c]
get_obj_attr 0xff08779c -> 0xff087770 [0x02c]
is_taskid_valid 0xff087940 -> 0xff087914 [0x02c]
SetGUIRequestMode 0xff0a8738 -> 0xff0a870c [0x02c]
gui_massive_event_loop 0xff0a9384 -> 0xff0a9358 [0x02c]
gui_change_mode 0xff0aabc4 -> 0xff0aab98 [0x02c]
gui_local_post 0xff0ab1c0 -> 0xff0ab194 [0x02c]
gui_other_post 0xff0ab5dc -> 0xff0ab5b0 [0x02c]
gui_post_100000a1 0xff0ab858 -> 0xff0ab82c [0x02c]
gui_change_shoot_type_post 0xff0ab8e4 -> 0xff0ab8b8 [0x02c]
gui_change_lcd_state_post 0xff0ab97c -> 0xff0ab950 [0x02c]
gui_init_event 0xff0ac000 -> 0xff0abfd4 [0x02c]
GetJpegBufForLV 0xff11a8e0 -> 0xff11a8b4 [0x02c]
GetJpegSizeForLV 0xff11a8ec -> 0xff11a8c0 [0x02c]
RemoteRelease 0xff15fd74 -> 0xff15fd48 [0x02c]
PtpDps_remote_release_SW1_SW2_worker 0xff16004c -> 0xff160020 [0x02c]
mvrSetDeblockingFilter 0xff1e0870 -> 0xff1e0844 [0x02c]
mvrSetDefQScale 0xff1e08e0 -> 0xff1e08b4 [0x02c]
mvrFixQScale 0xff1e0e04 -> 0xff1e0dd8 [0x02c]
mvrSetPrintMovieLog 0xff1e0e24 -> 0xff1e0df8 [0x02c]
SetEDmac 0xff1f5360 -> 0xff1f5334 [0x02c]
ConnectWriteEDmac 0xff1f5418 -> 0xff1f53ec [0x02c]
ConnectReadEDmac 0xff1f54dc -> 0xff1f54b0 [0x02c]
StartEDmac 0xff1f5660 -> 0xff1f5634 [0x02c]
RegisterEDmacCompleteCBR 0xff1f5850 -> 0xff1f5824 [0x02c]
UnregisterEDmacCompleteCBR 0xff1f5864 -> 0xff1f5838 [0x02c]
PopEDmac 0xff1f5864 -> 0xff1f5838 [0x02c]
RegisterEDmacAbortCBR 0xff1f5878 -> 0xff1f584c [0x02c]
UnregisterEDmacAbortCBR 0xff1f58b8 -> 0xff1f588c [0x02c]
RegisterEDmacPopCBR 0xff1f5980 -> 0xff1f5954 [0x02c]
UnregisterEDmacPopCBR 0xff1f5994 -> 0xff1f5968 [0x02c]
shamem_read 0xff1f664c -> 0xff1f6620 [0x02c]
_EngDrvOut 0xff1f675c -> 0xff1f6730 [0x02c]
_engio_write 0xff1f6b20 -> 0xff1f6af4 [0x02c]
FIO_Open 0xff1fc224 -> 0xff1fc1f8 [0x02c]
FIO_CreateFile 0xff1fc2e0 -> 0xff1fc2b4 [0x02c]
FIO_RemoveFile 0xff1fc38c -> 0xff1fc360 [0x02c]
FIO_ReadFile 0xff1fc434 -> 0xff1fc408 [0x02c]
FIO_SeekFile 0xff1fc5b4 -> 0xff1fc588 [0x02c]
FIO_WriteFile 0xff1fc5d4 -> 0xff1fc5a8 [0x02c]
FIO_CloseFile 0xff1fc684 -> 0xff1fc658 [0x02c]
FIO_GetFileSize 0xff1fc800 -> 0xff1fc7d4 [0x02c]
FIO_CreateDirectory 0xff1fccf4 -> 0xff1fccc8 [0x02c]
FIO_FindFirstEx 0xff1fd2b8 -> 0xff1fd28c [0x02c]
FIO_FindNextEx 0xff1fd42c -> 0xff1fd400 [0x02c]
FIO_FindClose 0xff1fd554 -> 0xff1fd528 [0x02c]
LightMeasure_n_Callback_r0 0xff202814 -> 0xff2027e8 [0x02c]
msg_queue_receive 0xff205c70 -> 0xff205c44 [0x02c]
msg_queue_post 0xff205e5c -> 0xff205e30 [0x02c]
msg_queue_count 0xff205e9c -> 0xff205e70 [0x02c]
AcquireRecursiveLock 0xff205fa8 -> 0xff205f7c [0x02c]
ReleaseRecursiveLock 0xff2060bc -> 0xff206090 [0x02c]
vsnprintf 0xff209670 -> 0xff209644 [0x02c]
register_func 0xff20ae48 -> 0xff20ae1c [0x02c]
_alloc_dma_memory 0xff20da50 -> 0xff20da24 [0x02c]
_free_dma_memory 0xff20da84 -> 0xff20da58 [0x02c]
GUI_SetRollingPitchingLevelStatus 0xff236e9c -> 0xff236e70 [0x02c]
GUI_GetFirmVersion 0xff23f414 -> 0xff23f3e8 [0x02c]
GuiEdLedOn 0xff242ef0 -> 0xff242ec4 [0x02c]
GuiEdLedOff 0xff242f14 -> 0xff242ee8 [0x02c]
GuiEdLedBlink 0xff242f38 -> 0xff242f0c [0x02c]
ptp_register_handler 0xff2885cc -> 0xff2885a0 [0x02c]
vram_get_number 0xff2cb1e0 -> 0xff2cb1b4 [0x02c]
ctrlman_dispatch_event 0xff2fe9f4 -> 0xff2fe9c8 [0x02c]
gui_task_create 0xff2feb44 -> 0xff2feb18 [0x02c]
gui_task_destroy 0xff2fec64 -> 0xff2fec38 [0x02c]
DeleteDialogBox 0xff2ff7c4 -> 0xff2ff798 [0x02c]
CreateDialogBox 0xff2ffd3c -> 0xff2ffd10 [0x02c]
dialog_redraw 0xff300640 -> 0xff300614 [0x02c]
RedrawDisplay 0xff317ee8 -> 0xff317ebc [0x02c]
ErrForCamera_handler 0xff336d60 -> 0xff336d34 [0x02c]
LiveViewApp_handler 0xff347918 -> 0xff3478ec [0x02c]
PlayMain_handler 0xff3552dc -> 0xff3552b0 [0x02c]
OlcAFFrameApp_handler 0xff35ac90 -> 0xff35ac64 [0x02c]
ShootOlcApp_handler 0xff35df58 -> 0xff35df2c [0x02c]
dialog_set_property_str 0xff361bdc -> 0xff361bb0 [0x02c]
LiveViewWbApp_handler 0xff3674a4 -> 0xff367478 [0x02c]
GUI_SetCFnForTab4 0xff375998 -> 0xff37596c [0x02c]
GUI_GetCFnForTab4 0xff3759f0 -> 0xff3759c4 [0x02c]
PackMem_SetEDmacForMemorySuite 0xff3d24a0 -> 0xff3d2474 [0x02c]
PackMem_StartEDmac 0xff3d2598 -> 0xff3d256c [0x02c]
PackMem_PopEDmacForMemorySuite 0xff3d2644 -> 0xff3d2618 [0x02c]
PackMem_RegisterEDmacCompleteCBRForMemorySuite 0xff3d26ec -> 0xff3d26c0 [0x02c]
PackMem_RegisterEDmacPopCBRForMemorySuite 0xff3d275c -> 0xff3d2730 [0x02c]
PackMem_RegisterEDmacAbortCBRForMemorySuite 0xff3d27cc -> 0xff3d27a0 [0x02c]
fsuDecodePartitionTable 0xff3d7798 -> 0xff3d776c [0x02c]
StopPlayProtectGuideApp 0xff41dde0 -> 0xff41ddb4 [0x02c]
StartPlayProtectGuideApp 0xff41e17c -> 0xff41e150 [0x02c]
PlayMovieGuideApp_handler 0xff42b700 -> 0xff42b6d4 [0x02c]
ErrCardForLVApp_handler 0xff430250 -> 0xff430224 [0x02c]
cfReadBlk 0xff44ebb0 -> 0xff44eb84 [0x02c]
sdReadBlk 0xff454540 -> 0xff454514 [0x02c]
GetCFnData 0xff4c621c -> 0xff4c61f0 [0x02c]
SetCFnData 0xff4c6424 -> 0xff4c63f8 [0x02c]
bzero32 0xff50cdec -> 0xff50cdc0 [0x02c]
Didn't look in the firmware, but you may want to double-check sounddev_task and PD_RemoteRelease.
I've commented them out.
/*
NSTUB(0xff0372b4, PD_RemoteRelease) // pel: 2.0.3 stub points to the middle of the "NotifyPrcmRecStartFromSlave %d" code... probably wrong
*/
/*
NSTUB(0xFF0638A0, sounddev_task) // pel: 2.0.3 stub points to the middle of the SoundDevice code... probably wrong
*/
Hi ALL
I am sorry, I did not check this thread before....I also post a comment about the Magic Lantern on Canon 7D with firmware 2.0.5, see below.
I did first the update 2.0.3 to 2.0.5. After update, I tried to re-install my Magic Lantern. As usually, first on the Compact Flash card (CF) and after this, to start a fictive update again. Also, according to normal procedure. The problem was that as soon as I pressed the button "OK" (for fictive new firmware, in order to start Magic Lantern), the screen become black for ever! Nothing happened. This, two times. After that, I realize that the Magic Lantern for Canon 7D, clearly indicate as been valid only for firmware 2.0.3 since the name of the file is "eos7d-v203-win"! I was never prompted to back-update to 2.0.3! However, since the Canon 7D did not more worked, I must back-update, what, fortunately, was possible! This is a very important point since there are a lot of software which CANNOT be back-updated! In this moment I have 2.0.3 and ML works fine. Now, I would be very glad if somebody from Magic Lantern could inform the Canon 7D users if ML intends to issue a version for 2.0.5 firmware?
Best Regards, Eugene
yes
Wow they released new fw this long after?
Quote from: 1% on December 17, 2013, 04:39:38 PMWow they released new fw this long after?
It's Canon's flagship in their APS-C fleet up to this very day. Ole Alloybottom you may call err ...
It certainly does feel like it... would be cool if instead they fixed exfat support and the like.
* also anyone have a backup of 2.0.3 unmodified/stock fir? Canon pulled it off their site already.
pel is currently trying to get 7D to work with 2.0.5, but this would take some time.
https://bitbucket.org/Pelican/7d205
Quote from: 1% on December 17, 2013, 04:55:49 PM
* also anyone have a backup of 2.0.3 unmodified/stock fir? Canon pulled it off their site already.
I have a collection of Canon EOS firmwares on the bottom of the EOScard page.
(I hope my site will alive from now... they still not finished working on it.)
Quote from: g3gg0 on December 17, 2013, 05:34:16 PM
pel is currently trying to get 7D to work with 2.0.5, but this would take some time.
https://bitbucket.org/Pelican/7d205
I shared the code that I've made for the new 2.0.5 platform because I'm not at home so I cannot test it myself...
https://bitbucket.org/Pelican/7d205/commits/c582c63009434e5f06ce32b6e5f290a23b53ce01
I found another mirror of 2.03 as well so in case a downgrade is required:
http://drivers.softpedia.com/dyn-postdownload.php?p=292050&t=0&i=1
Did it look like much changed in the fw? I have to load it up.
Yes, I have it (backup of 2.0.3 unmodified/stock fir)
I just wanted to jump in here and say how awesome Magic Lantern on the 7D is. I'm shooting time lapses like a fiend now. Thanks to everyone for all their hard work, and I eagerly look forward to future developments.
I am about to install the ML firmware for my Canon 7D. I am at Canon version 2.3. Any gotchas or tips that I should be awre of before proceeding? I would install this alpha2 version on an Extreme 16GB CFII card.
Thanks in advance.
Sorry meant firmware version 2.0.3.
http://www.magiclantern.fm/forum/index.php?topic=7464.0
You have to decide: Tragic Lantern offers more features, ML nightly has not all features implemented (yet).
Ciao
Walter
Any news when the dottune module will be avaible for the 7d?
[edit] nevermind, was able to use the dot_tune.mo from the 5d3 nightly build :) awesome work, thanks
does anyone know if i can put magic lantern on my 7D if my firmware is the new 2.05?
Downgrade your cam's firmware to 2.0.3.
I am a newbie with my 7D and ML and have tried to go through the process of first time install on card..but as all newbies...failed...... :-[
Installation
1) Update camera firmware to 2.0.3 - Yes " Canons own Version "
2) Format your CF card from the camera - Yes
3) Extract contents of ML .zip into your card's root folder - Yes " magiclantern_7D_203_Alpha2 "
4) Upgrade firmware - yes from downloaded firmware for 7D out of ML 7D zip.
5) Used EOScard1.40 as well.
But does not have a autoexe file for booting...
anybody got any ideas....as i have rechecked forum...and im still not certain..
I am most likely using the incorrect download file and wrong install method...
If you don't have an AUTOEXEC.BIN file in the root directory of your card - after using EOScard *and* extracting files - I suppose your explorer settings are hidding them. It is highly unlikely using two different methods producing exactly the same error.
Redo the EOScard utility method once more and follow instructions.
1-4 will fail to get you a bootable card. EOScard will do.
Ciao
Walter
Installing ML can be summarized in three steps, keep this in mind in case you are getting lost in the process!
1. You need to set the bootflag in your camera.
2. You need to make your SD card (or CF for some cameras) bootable with EOScard
3. Only then you can use the nightly builds. http://builds.magiclantern.fm/#/
Copy the files to the new SD card from 2.
-----------------------------
You are having troubles with step 1
I dont know where to get the special file to set the bootflag in the 7D, but I do know how to make it!
Follow the steps here:
http://www.magiclantern.fm/forum/index.php?topic=7464.0
Hello,
I have updated my firmware to 2.0.5 version and then found out the ML alfa 2 doesnt run on he newest version. And I couldn't find the older one even googling it and surfing for hours. Please, does any of you have the 2.0.3 version (Win) saved somewhere by any chance?
Thanks a lot.
Ondrej
http://pel.hu/down/eos7d-v203-win.zip
Timeout
http://pel.bencemate.com/down/eos7d-v203-win.zip
Quote from: britom on July 27, 2013, 07:52:03 PM
Your camera may brick so DO IT AT YOUR OWN RISK!
You have to follow these steps in order to try the Audionut ML build and the dual iso module:
You'll Need This Files:
7D firmware v1.2.3 http://pel.hu/down/eos7d123.exe (Thanks to Pelican)
EOScard software http://pel.hu/down/EOScard.exe (Thanks to Pelican!)
EOS Utility 2.8.1 https://dl.dropboxusercontent.com/u/43043701/EOS.zip
patch.bsdiff https://ml-devel.googlegroups.com/attach/1608f00c71abc464/patch.bsdiff?part=6
bsdiff.exe and bspatch.exe http://download.pokorra.de/coding/bsdiff_win_exe.zip
Enabling Bootflag:
Unzip the bsdiff_win_exe.zip file in any folder. In my case i extracted to a folder in my desktop C:\Users\Miguel\Desktop\Magiclantern\
Double-Click eos7d123.exe and unzip it in the same folder. It should extract the 7d000123.fir file in the folder.
Place the downloaded file patch.bsdiff in the same folder
Open "cmd" by pressing WindowsKey+R and typing cmd
In the cmd screen change the directory by typing cd "folder where you put the files", in my case it was cd C:\Users\Miguel\Desktop\Magiclantern\
Type bspatch.exe 7d000123.fir firmware.fir patch.bsdiff and press enter
It should generate a file called firmware.fir that we are going to use with EOS Utility.
Copy the firmware.fir file to an empty CF card and put the card in your camera.
Extract EOS.zip in some other folder. In my case i extracted to C:\Users\Miguel\Desktop\Magiclantern\EOS Utility\
For me it worked well but is possible that this EOS Utility wont work because of some missing driver or registry key, so make sure you have installed any Canon EOS DIGITAL Solution Disk before.
Connect the camera to the pc via usb cable.
Go to the folder that you've extracted EOS.zip and double-click EOS Utility.exe *
Click Camera Settings/Remote Shooting option. Make sure your camera dial is in M mode and Liveview turn off.
In the middle of the window click the icon that looks like a cross and a tool, between the Lightning/Flash icon and the Star icon.
Click Firmware Ver. 2.0.3 at the bottom of the list.
Click OK and Select the firmware.fir file from the first folder. Click OK Again.
Wait until is done. **Be very Careful**
Installing ML:
Now put the CF card in your computer. Delete the firmware.fir and the other files.
Open EOScard.exe, click EOS_DEVELOP, BOOTDISK, right-click the ML icon, select Ports in progress and click 7d 2.0.3 alpha2.
Wait until is downloaded and click Save in the upper right corner.
DONE!
This build already contains the Dual Iso Module, It is not enabled by default and you can enable it for testing but some people are having issues with the module so do it at your own risk.
* If the Camera Settings/Remote Shooting option is greyed out follow this steps:
Go to Device Manager by pressing WindowsKey+R and typing devmgmt.msc
Expand the Portable Devices tree and Disable all of them except Canon EOS 7d by right-click - Disable.
Feel free to ask anything, i'll try to answer as soon as possible. Excuse my english :D
7D firmware v1.2.3[/b] http://pel.hu/down/eos7d123.exe (Thanks to Pelican)->done
EOScard software[/b] http://pel.hu/down/EOScard.exe (Thanks to Pelican!) ->done
EOS Utility 2.8.1[/b] https://dl.dropboxusercontent.com/u/43043701/EOS.zip ->dropbox error 404
patch.bsdiff[/b] https://ml-devel.googlegroups.com/attach/1608f00c71abc464/patch.bsdiff?part=6 ->done
bsdiff.exe and bspatch.exe[/b] http://download.pokorra.de/coding/bsdiff_win_exe.zip ->done
Click
Firmware Ver. 2.0.3 at the bottom of the list.
Click
OK and Select the
firmware.fir file from the first folder. Click
OK Again. --->> click from the first folder in my computer or camera? if i click from my computer the file is unsuported file and when i click in my camera firmware update to 1.2.3
Wait until is done. **Be very Careful**Installing ML:
Now put the CF card in your computer. Delete the firmware.fir and the other files.
Open
EOScard.exe, click
EOS_DEVELOP, BOOTDISK,
right-click the
ML icon, select
Ports in progress and click
7d 2.0.3 alpha2.Wait until is downloaded and click
Save in the upper right corner. ----> Nothing happend :-[ :-[
help me please.... :'(
Got it all working on my 7d thanks for the help... ;D
Quote from: Deware on January 06, 2014, 06:49:39 AM
Now put the CF card in your computer. Delete the firmware.fir and the other files.
Open EOScard.exe, click EOS_DEVELOP, BOOTDISK, right-click the ML icon, select Ports in progress and click 7d 2.0.3 alpha2.
Wait until is downloaded and click Save in the upper right corner. ----> Nothing happend :-[ :-[
1. Format card on PC (must use card reader) and then format on Camera.
2. Just get the latest ML files from here: http://builds.magiclantern.fm/#/
3. Put these files on the card.
4. Open EOScard
5. Make sure EOS Develop box is selected, Bootdisk box is selected and simply click on Save. If all goes well the card will be made bootable and a "write sucessfull" message will appear on the bottom of EOScard.
6. Card back on 7D...
In the nightly builds of the 7D I´m missing the Menu item "Shutter Lock".
Is it possible to insert it there somehow?
You have a dedicated button for it ;)
http://www.outdoorphoto.co.za/forums/showthread.php?17465-canon-7D-lock-button
Sorry, but with this button I can lock the shutter?
On my 7D I can lockk the aperture, but not the shutter
Am I wrong?.
On 5D3 I can choose which wheel(s) I want to lock. On 7D, I think you need to go to custom controls and assign the shutter speed to the rear dial (there may be an easier way, didn't look too hard).
http://www.learn.usa.canon.com/resources/blogs/2013/20131112_chan_lockswitch_blog.shtml
http://reviews.cnet.com/2300-6501_7-10001790-6.html
Thanks for your answers and sorry for my bad english.
But, I film with three cameras (7D, 5Dm2 and 600D) and would like to have always the same worklfow.
The 5Dm2 and 600D have the Menu item "Shutter Lock", therefore, I would like to use it also on my 7D.
But if that is not possible I have to make it just as you have recommended.
Thank you.
I installed 10 jan firmware.
With kit lens and RAW video worked fine.
one things I found, Canon 50 f1.8 was not auto focusing. Overlay under trap focus was showing wrong aperture value. It was identifying the lens but not the f value. I had uninstall.
Can Anyone suggest where to report bugs? For current firmware?
the download link at forst post do not work it give to me 403 error. can you give me please the safest and updated files to downlad to install ML on my 7D?
thanks,
Brawl
Quote from: BushanBengaluru on January 12, 2014, 06:38:15 AM
one things I found, Canon 50 f1.8 was not auto focusing. Overlay under trap focus was showing wrong aperture value. It was identifying the lens but not the f value. I had uninstall.
do you mean for photos? if you do not start magic lantern does the autofocus work? I have the canon 50 1.8 as my primary lens for work and it's important. thanks
Firstly greetings all !
Has anyone done an installation tutorial for the 7D Raw ML on youtube or other video site ?
That could save so much confusion ?
I do apologise if this has already been done.
Marv_B
Click here (http://lmgtfy.com/?q=magic+lantern+7d+installation+tutorial+site%3Awww.youtube.com)
Or here (http://lmgtfy.com/?q=magic+lantern+7d+installation+tutorial+site%3Avimeo.com)
Thank you Walter point noted !
there are indeed multiple instances, ML here I come.
ML Dev team rocks !
I cannot see the 7D download in the nightly build dropdown menu at http://builds.magiclantern.fm/#/ .. am I missing something here .. thanks in advance
Quote from: RenatoPhoto on January 09, 2014, 02:15:38 PM
1. Format card on PC (must use card reader) and then format on Camera.
2. Just get the latest ML files from here: http://builds.magiclantern.fm/#/
3. Put these files on the card.
4. Open EOScard
5. Make sure EOS Develop box is selected, Bootdisk box is selected and simply click on Save. If all goes well the card will be made bootable and a "write sucessfull" message will appear on the bottom of EOScard.
6. Card back on 7D...
Quote from: kphadke on January 21, 2014, 02:56:46 PMam I missing something here ..
http://www.magiclantern.fm/forum/index.php?topic=3072.msg97314#msg97314
Don't know anything about the discussions in the background but this thing doesn't sound good ...
Ciao
Walter
Sorry for the silly question, it's awhilethat I don't update ML on my 7D if I need the most updated files where I could find them?
Thanks
http://www.magiclantern.fm/forum/index.php?board=58.0
Quote from: Walter Schulz on January 24, 2014, 12:38:51 PM
http://www.magiclantern.fm/forum/index.php?board=58.0
Thanks :)
does magic lantern.7D.203.Alpha2 supports new Eos 7D Firmware 2.0.5 ?
magic lantern.7D.203
^^^ hinthinthint
Woops.
Sorry..
I upgraded to 2.0.5, maybe that gives me error.
- If you want to stay on 2.0.5 you won't be able to use ML until ML for this very firmware version is done.
- If you want to use ML now, you have to downgrade to firmware 2.0.3.
As time of writing ML checks for the proper firmware version and will not load if check fails.
Ciao
Walter
you are doing a stirling job Walter - thanks
HI, I just installed ML alpha 2 on my 7d and noticed that my Sandisk extreme 32gb CF card gets hot...even when I am not trying to record raw. Any Idea why this is happening?
Quote from: Walter Schulz on January 25, 2014, 01:21:19 AM
- If you want to stay on 2.0.5 you won't be able to use ML until ML for this very firmware version is done.
Any news on 2.0.5 ML btw? Haven't heard anything since the first flurry
Nothing new yet, haven't had the chance to work on it or much of anything. :(
won't let me download. says i don't have permission to access the page. any help?
I have the same problem!
I too can not download ML....but I'm a SUPER NOOB! SOmeone point me in the right direction!
use the alternative bitbucket.
hey everybody!
is there any post where can I find some explanationsor infos about fps override?
I'm trying different methods, also changing bitrate but I want something in more, I want to find more infos about fps...
is there any way to film with fps at 80 or more fps fpor freezing action...or for exampe with 8 fps for doing like timelapse?
thank's in advance for your time!
...sorry, but...nobody knows something about fps override? how can be explained it?
it's the 3rd day that I'm reading ML forums and searching something more specific about fps override but I can't find a really nice article to describe it and explain how you can reach a good result.....there is not either one post called for example " fps override" or similar....
can someone please start a post with an article?
my best regards for every kind of try!
Thanks! You explained these problems very well. Having watched video tutorials for other Canon cameras it seems some of them have much better designed menus.
Development of the ML software for the 7D is a long way behind unfortunately. :'(
Quote from: Royward on February 05, 2014, 09:24:51 AMHaving watched video tutorials for other Canon cameras it seems some of them have much better designed menus.
Example?
Hi everyone
Thank you for your effort and time, and everything ;)
I want to ask, how can I downgrade from 205 to 203? If I copy the 203 fir o the card, and want to go to firmware update, it sais "Memory card containing firmware is required to update", eventhough I have both 203 and 205 on the card. Is it possible? Should I rename the file to 206?
Thanks
Csongor
EOSutility
Quote from: CsongorMatyas on February 05, 2014, 06:16:02 PM
Hi everyone
Thank you for your effort and time, and everything ;)
I want to ask, how can I downgrade from 205 to 203? If I copy the 203 fir o the card, and want to go to firmware update, it sais "Memory card containing firmware is required to update", eventhough I have both 203 and 205 on the card. Is it possible? Should I rename the file to 206?
Thanks
Csongor
No. Just put the fir file to the root of your card.
If the camera cannot see it (according to your error message) then you have not copied it to the right place.
Do I have to copy the MAGIC.FIR (330 kbytes) file to the root directory, no?
Do I have to rename it? When I go in to menu in the camera, at the firmware I see the option to upgrade to 205, I go there, then I'm upgrading, it's starting, but after that it stops, black screen, no responding, have to take out batteries.
I have the autoexec.bin file, ML folder and MAGIC.FIR from alpha 2 zip, all these in the root. Do I need anything else?
I'm downloading EOS utility, unfortunately I don't have it (I bought the camera used, without the cd).
When I go in menu, and go to firmware, what should I see? (I don't want to brake my camera with allways blocking it, and taking out the batteries)
Thank you
Csongor
Sorry, I realized, that you were talking about the 203 fir file. I have that in the root, just where I had the 205 as well, and it worked.
I've tried to have both of them, 203 and 205, just 203, with or without ML, but same thing happens. If I have ML starts to upgrade and freezes, if I don't have ML, it can;t be seen.
Problem solved, card has some defect.
Updated back to 203, and ML is working fine. I'm starting to experience with it :)
Thank you very much ;)
Csongor
@CsongorMatyas
Modify your posts rather then posting multiple times in a row please.
Locking thread, please continue the discussion here: http://www.magiclantern.fm/forum/index.php?topic=9848