Quote from: a1ex on December 20, 2013, 02:38:01 PM
Nightly compiled, you may try it: http://builds.magiclantern.fm/
Thank you!
Installation:1) Format the card from the camera.
2) Make sure you are running Canon firmware
2.0.3 (http://pel.hu/down/eos7d-v203-win.zip).
3) Copy ML files on the card and run Firmware Update.
Uninstallation:1) Run Firmware Update from your ML card.
2) Follow the on-screen instructions.
(http://a1ex.magiclantern.fm/bleeding-edge/new-installer.png)
Quote from: nerezko on December 15, 2013, 01:27:39 PMYesterday I tried to update the ML firmware decided to do everything with a "clean" card.
Good news: Pelican's site is up and running and 7D has jumped the night train!
http://www.magiclantern.fm/forum/index.php?topic=7503.msg92348#msg92348
Quote from: a1ex on December 20, 2013, 02:38:01 PMNightly compiled, you may try it: http://builds.magiclantern.fm/
Thanks and bug report!
Had a problem with AF (Phase AF not working at all) after copying the files to the card.
Reset all cam settings, including custom functions and ML, too. Removed both batteries. Worked again.
Bug: Phase AF not working properly with certain lenses after lens change.
Reproducable. Used settings: All AF points are activated in One Shot mode.
Step 1: Mount "older" lens (Canon EF 100/2.8 Macro USM, Canon EF-S 10-22, Sigma 18-125 OS): Phase detect AF is working as expected.
Step 2: Mount "newer" lens (Canon EF 100/2.8 L, Canon EF-S 18-55 IS II, Canon EF-S 55-250 IS II): Phase detect AF is working as expected.
Step 3: Mount "older" lens (Canon EF 100/2.8 Macro USM, Canon EF-S 10-22, Sigma 18-125 OS) again: Fokus hunt. Always missing to focus properly.
Steps tried to make it work again.
- Tried to turn cam off and on: Nope, error is still there.
- Mounted other lens: Phase detect AF is working but only with "newer" lenses. "Old" lenses won't work with Phase AF.
- Removed battery: "Old" lenses are working with Phase detect AF again.
Error is reproducable in AI Servo when single AF point other than center is selected. Works with center AF point though.
10-22 (or any other ultra wide lens) is not recommended for doing this test because deep DOF may cause false focus confirmation.
Ciao, Walter
Okay, now start the camera by holding SET (so you load ML, but it should not be active). Is the bug still present?
Pressed SET during startup, waited until menu arrived and tried: Bug is there.
Started without card inserted: Bug missing.
Ciao
Walter
This sounds much like the EOS M bug, which I haven't been able to diagnose yet (see www.magiclantern.fm/forum/index.php?topic=8347 ).
Note that you can't boot with a minimal binary on 7D because you need to poke both DIGICs (so don't try the autoexec from there; it will work on any other camera except 7D).
Anything I can do assisting to solve the 7D riddle? Dumps, running diagnostics?
Missing equipment? Both EF-S 18-55 IS II and 55-250 IS II will *not* be missed by me that much ...
Ciao
Walter
Yes, here's the minimal bin for 7D:
autoexec.bin (http://a1ex.magiclantern.fm/bleeding-edge/7D/minimal/autoexec.bin)
asm(
".text\n"
".globl _start\n"
"_start:\n"
"LDR R0, .val\n"
"LDR R1, .reg\n"
"STR R0, [R1]\n"
"B 0xF8010000\n"
".val: .word 0x80000010\n"
".reg: .word 0xC0A00024\n"
);
All it does is:
1) pokes the master CPU (see reboot.c, 0xC0A00024 = 0x80000010)
2) jumps to Canon startup address on the slave CPU (this is ML startup procedure without the patching part).
If there's no focus bug with this autoexec, I know where to start digging. If it still has the bug... I'm lost.
Start digging, the error is not there using this Autoexec.bin.
Just removed battery, mounted 100/2.8 Macro, then 100/2.8 L, then 100/2.8. No focus hunt.
Ciao, Walter
Great!
This means it will be solved.
hmmm... with this latest build (2013-12-20 14:35:15 +0100) I can not get continuous recording even on 1780x960... I was managing that with old builds..... Am I doing something wrong?
Quote from: hbr on December 20, 2013, 09:38:52 PM
hmmm... with this latest build (2013-12-20 14:35:15 +0100) I can not get continuous recording even on 1780x960... I was managing that with old builds..... Am I doing something wrong?
Quote from: Pelican on December 20, 2013, 10:56:51 AM
As I and g3gg0 said it in your commit's comments the 7D platform was not outdated at all.
I hope you now understand why I said it's outdated.
Thanks for including the 7D back in official magic lantern nightly builds.
http://builds.magiclantern.fm/#/
For the purpose of informing those coming in recently to this thread is it possible to add in the logs or here in how this differs from the tragic lantern or other versions out there?
What safety checks have been put in and what features were removed?
At this point, it's simply the old 7D ML code, which - to me - still looks outdated, even if Pelican and g3gg0 have a different opinion. But I have high hopes that it will be brought back to speed.
QuoteWhat safety checks have been put in?
None. The correct question is what safety checks were removed in TL. This may help (//http://://www.magiclantern.fm/forum/index.php?topic=9510.msg78084#msg78084), but it's 3 months old, so you may need to review the code again. I doubt anything changed since then, but who knows.
Quotewhat features were removed?
None. You should do a comparison (both by reviewing the code differences and by experimenting with both versions) to see what features were enabled in TL and not backported to the main repo.
Wow. Lot of things happened here... Cool. 8)
For those who are using any TL versions:
The "official" nightly build contains the ML from the main repo.
None of the changes of 1% merged back to here until now so don't start to complain about it.
If you are using any TL build then keep using it.
These nightly builds are for people who want to check the state of the main 7D ML.
Backport TL changes to the main repo is a time consuming task but I prefer to keep 7D ML up to date.
Any help appreciated.
If you want a stable ML on your 7D you can help testing different functions and compare these functions in TL and ML.
What the developers need mostly is feedback.
Hi guys,
So I've been following the forum since first 7D alpha 1 released. And then Raw video came out of nowhere for Mark II and of course like any other 7D owner started to dream for the day that it may be released for 7D. At first, most people kept saying "Raw video shooting will never be possible for 7D because the main processor of the 7D is unhackable" bla bla... And ofc Magic Lantern community proved those people wrong again. I've been paying close attention to this specific post for almost half a year now. Amazing improvements have happened since, major thanks to Pelican, %1, g33gl and everybody else helped out.
At this point I can't wait any longer hoping that stable version for 7D raw video may be release any time soon. So I'll give it a try. I just downloaded the 2.0.3 nightly build 12/21/2013. I wanted to ask you guys where can I find the exact workflow to make it work in the camera and the workflow for post?
Best!
Quote from: Ozgur on December 22, 2013, 09:56:37 PM
At this point I can't wait any longer hoping that stable version for 7D raw video may be release any time soon. So I'll give it a try. I just downloaded the 2.0.3 nightly build 12/21/2013. I wanted to ask you guys where can I find the exact workflow to make it work in the camera and the workflow for post?
That's the nightly build of MagicLantern. I think you'll find the raw recording performance (at least regarding the newer mlv_rec) with that version is not so polished as 1%'s TragicLantern (which doesn't have nightly builds at the moment, but has been the basis of the versions most recently discussed in this thread).
Hopefully some of the performance-related changes in TL will be integrated back to the ML source in the near future so the ML 7D nightly builds are usable for RAW/MLV.
Maybe you should still hold off a bit longer until that happens?
Hi! i put the new version of magic latern in my camera but i cant find fsp overwrite now?¿ where is it??
what is the new things of this version??
thanks!!
Quote from: baldand on December 22, 2013, 11:18:02 PM
That's the nightly build of MagicLantern. I think you'll find the raw recording performance (at least regarding the newer mlv_rec) with that version is not so polished as 1%'s TragicLantern (which doesn't have nightly builds at the moment, but has been the basis of the versions most recently discussed in this thread).
Hopefully some of the performance-related changes in TL will be integrated back to the ML source in the near future so the ML 7D nightly builds are usable for RAW/MLV.
Maybe you should still hold off a bit longer until that happens?
Thank you for the feedback. Can't I simply write the autoexec.bin file of TL to 2.0.3 nightly build to have the latest 7D raw shooting update?
Quote from: javyelow on December 24, 2013, 01:22:13 PMwhat is the new things of this version??
Please read http://www.magiclantern.fm/forum/index.php?topic=7503.msg92516#msg92516 and read it carefully.
Ciao
Walter
Hi! i put the new version of magic latern in my camera but
i cant find fsp overwrite now?¿ where is it??
Quote from: javyelow on December 26, 2013, 01:35:34 AM
Hi! i put the new version of magic latern in my camera but
i cant find fsp overwrite now?¿ where is it??
http://www.magiclantern.fm/forum/index.php?topic=7503.msg92854#msg92854
You're using ML now. You may want to use Tragic Lantern as intended in the linked post.
ML or TL?
If ML: http://www.magiclantern.fm/forum/index.php?topic=7503.msg92516#msg92516
Can i help in some way to back porting TL to the main ML ??
You can download the latest nightly from here: http://builds.magiclantern.fm/jenkins/job/7D.203/lastSuccessfulBuild/
and write down the differences between ML and TL, so developers should know exactly what to backport.
Once there will be significant progress in backporting these things, I will enable the nightly builds again.
Where some stuff from ML that don't exist or not working correct,
-Zoom 10x stay hang, pressing play button it get out of that freeze state.
-No MLV
-No Audio
I have made some tests with raw_mo but i don't know if it's worth to write here or to do more tests... Wait for the MLV? Other stuff looks to work good. I need more modules for try out, this build/version just have this modules.
raw_mo
dual_iso.mo
ettr_mo
autoexpo.mo
file_man.mo
pic_view.mo
Easiest on the list
*Audio
*Display filters (just like 5DII/50D)
Harder:
Headphone from slave --- it has to be toggled on, there is no way to detect connection
FPS override for H264 -- It can be done from slave, needs help with unexpected video stops
If I use EOSCard from Pelican to make new bootable card for 7D, it already includes an MLV.mo, I still updated the install from jenkins Jan 21 build which does not have an mlv.mo.
Is this MLV mo from eoscard considered from ML or TL? so I'd know if I should test it and report.
This build Lacks:
Audio:
-The option to choose channels
-Headphone monitoring
-External mic controls
-Gain controls
-MLV Sound
Movie:
-FPS Override
_don't know yet if MLV from eoscard is TL or ML so holding report on this.
I think is just the modules that are in the folder. From EOScard is from TL... but for sure that someone will tell better then me.
I thought EOScard went ML->TL->ML... really I don't think it should be downloading any builds, just making the card bootable/etc. Maybe verify file/folder placement instead.
So for this, just make another repo from the current tree and add the audio/display filter? Then I guess we can see how to port the other things which are left... also the dual ISO preview never made it into main + what is the word on named bracketing like B01, etc... it was much more reliable than dual ISO custom prefix.
After 2.03 is brought up to par... I guess can move to porting 7D. 205
Quote from: 1% on February 04, 2014, 11:57:58 PM
After 2.03 is brought up to par... I guess can move to porting 7D. 205
Yes :D
I'm not that excited with 205... I don't think they modernized any parts of the FW. Im predicting it will just be like 6D112 -> 6D113, a bunch of changed addresses and thats it.
5DIII going to 123 has completely changed stuff.
I think that your talking about ML stable version and not canon fw. The fw 2.05 i think just have one update, having to do with FTP with a USB cable and WFT-E5 transmitter.
Both... 2.03 needs all features in main and then 2.05 update needs to be ported over in both.
Where can we find the new builds for the updates in ML Nightly 7D (with MLV_MO) ? It was removed from here http://builds.magiclantern.fm/#/
You'd have to compile. 7D was never that far behind, could have had a nightly for people to chose, stable, experimental. The first pull request is up with 90% of audio. Just needs headphone ported and the wav is disabled because it can't use the memory backend or the memory leak gets out of control.
Ok, thanks 1% Sometimes i think i understand and then... nikles. I think that wend dev's start to porting stuff from TL 2 ML it show up here http://builds.magiclantern.fm/#/
Anything that i can help for putting the 7D ML on the branch/nights/main/maintenance just let me know.
give it a go when someone compiles it.
Which version is suggested for bracketed HDR work?
Besides the naming of bracketed shots to B01 they should be identical for this feature.
Sorry for the totally NOOB question but where do we dl most recent version of ML for the 7D?
You need to compile... or wait that someone compile it.
What is the latest compiled version and where to find it?
You need to compile it yourself or wait for someone to share their build but someone already to you this....
Quote from: Stedda on February 09, 2014, 08:03:15 AM
You need to compile it yourself or wait for someone to share their build....
Then what is this?
https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern.7D.203.Alpha2.zip
Quote from: 1% on February 08, 2014, 05:37:56 PM
the wav is disabled because it can't use the memory backend or the memory leak gets out of control.
Nope, the memory backend catches the bug, and by disabling the memory backend you are simply ignoring the error message (and the bug is still there).
Moreover, this bug causes the wav recorder to write on unallocated memory => undefined behavior.
QuoteNope, the memory backend catches the bug, and by disabling the memory backend you are simply ignoring the error message (and the bug is still there).
Then why no crashes and missing memory? With the back-end on I get an error 70 from canon after the memory counts down. Without it, looks like all or most memory is released and no ERR70. Wavs record for a long time. I know the leak is still there for like a few kb but its not the monster that happens otherwise. Either way it will need a fix as the cameras make a really nice sound recorder. Esp. if you have more than one and no digital recorder.
The effects of undefined behavior range from nothing noticeable to anything you can imagine.
http://blog.llvm.org/2011/05/what-every-c-programmer-should-know.html
Hope there is a way to solve this properly.
edmac memcpy will cause issues while writing H264 since the channels will probably be in use.
I pushed a new pull request for 7D audio recording fix because the issue g3gg0 had with the previous one. It was working fine for me but it may be a case with wave recording with the things I read there so this time I left out the wave recording, only focusing on mlv_snd.
I hope it's ok this time !
If you like your food without vitamins ...
Quote from: 7Dphotos on February 10, 2014, 07:05:38 AM
Compiled and ready to use?
That file is old, we need that someone compiles a new version or that someone ad to the ML nigtly's http://builds.magiclantern.fm/#/
Quote from: arrinkiiii on February 10, 2014, 07:22:25 AM
That file is old
Sure, but does HDR bracketing work in that version? That is all I need right now.
I don't remember if that version works the HDR bracketing, maybe someone from the forum can tell you... or better, just try in your camera.
I can't remember a version *not* supporting advanced bracketing. Don't know about HDR video, though.
Quote from: Walter Schulz on February 10, 2014, 09:21:21 PM
I can't remember a version *not* supporting advanced bracketing. Don't know about HDR video, though.
lol something that i never have used... or test.
Its cool when you don't want to dual iso but want a stacked image.
Quote from: 1% on February 11, 2014, 01:56:05 AM
Its cool when you don't want to dual iso but want a stacked image.
for maKro stacked image is good.
Well for macro you would stack with focus, the bracketing stacks with exposure. It would be like sky + ground for AEB
Yes indeed. Bracketing is for exposures, good for interiors/architecture stuff.
Hello, I'm new in the forum, but following this project since the beginning.
I had the Alpha2 installed when it came out and tested
http://tl.bot-fly.com/tragiclantern-v2.3.NEXT.2014Feb11.7D203.zip
as well as
http://builds.magiclantern.fm/jenkins/job/7D.203/33/
recently.
Booting into ML/TL via FW update works in both cases without problems.
Now my big problem:
Both firmwares hang up/freeze my 7D after reboot as soon as I activated any module.
Can you please help me out here?
If I can test anything to help, just say, what I have to do. (most wanted are dual iso & RAW video)
Have to match the symbols file with autoexec.bin when you switch them.
We need a volunteer with skillz to compile an updated version for the 7D. Anyone?
Quote from: 7Dphotos on February 13, 2014, 03:26:41 AM
We need a volunteer with skillz to compile an updated version for the 7D. Anyone?
Fixes to make audio working are still pending to be incorporated in the mainstream ML, the pull request https://bitbucket.org/hudson/magic-lantern/pull-request/377/back-port-some-code-from-tl-to-make-audio awaits...
Quote from: 1% on February 12, 2014, 03:30:41 PM
Have to match the symbols file with autoexec.bin when you switch them.
You're a pro, I'm not. Switching what, matching how?
I just wanna have a ML/TL version that works with modules like dual iso or raw video on without freezing.
I downloaded both, copied them (one after another in different tests - not together) on a in camera fresh formatted SD card and tried it.
I didn't tweak anything, just activated the module(s). Then I resetted like ML/TL said and after the reboot everything freezes every time.
New clean copy on fresh formatted card runs again (without modules activated).
Sadly I didn't find a noob tutorial here. Everyone posts "cool, now I have dual iso" and stuff... no word about freezing. No mention what's to do to get modules working.
Make sure the modules folder that came with the bin is on the card. The symbols file is in ml/modules/[camera name].sym
Quote from: vyskocil on February 13, 2014, 09:10:58 AM
Fixes to make audio working are still pending to be incorporated in the mainstream ML, the pull request https://bitbucket.org/hudson/magic-lantern/pull-request/377/back-port-some-code-from-tl-to-make-audio awaits...
Nice, thanks!
Now, all those guys with 7D and coding skills who got mad at me for declaring this port "unmaintained" are now invited to try it and give feedback ;)
Alright :D Thanks guys!!! Rock on !!!
The link is the same?
Quote from: a1ex on February 13, 2014, 03:21:37 PM
... all those guys with 7D and coding skills ...
First code review, then user testing.
Grrrrrr damn lol =))
Quote
First code review, then user testing.
Will def need code review for headphones and H264 FPS override.
Also should port the display filter... its just like 50D, no reason to not have it on 7D
Quote from: 1% on February 13, 2014, 02:36:41 PM
Make sure the modules folder that came with the bin is on the card. The symbols file is in ml/modules/[camera name].sym
I'm a well experienced Win/Mac user and am working as a creative pro for over 10 years.
When I unzip a package I can handle it to copy all the files (incl. the modules folder) onto a correctly formatted SD card (I also posted the links of the latest packages I used).
I'm just new to the use of ML with modules and have freezes, when I activate any module from the modules folder on the card (e.g. ml/modules/dual_iso.mo).
QuoteHave to match the symbols file with autoexec.bin when you switch them.
What I don't understand: do the symbols files in http://tl.bot-fly.com/tragiclantern-v2.3.NEXT.2014Feb11.7D203.zip and http://builds.magiclantern.fm/jenkins/job/7D.203/33/ not match?
Does everyone have to edit them who wants to test the packages?
If yes, how?
7D_203.sym has 1.490 lines of code.... (and yes, of course I have 2.0.3 on my 7D, NOT 2.0.5)
The ML menue only says that the activated module(s) will be loaded after a reboot. Nothing about editing work.
I just beg for a little help on a level, a beginner can understand (whole sentences or a tutorial link I've missed).
Quotehttp://tl.bot-fly.com/tragiclantern-v2.3.NEXT.2014Feb11.7D203.zip and http://builds.magiclantern.fm/jenkins/job/7D.203/33/
Nope, they won't match between the 2. So you have to update and overwrite the folder every time. ML has to have the ML zip modules and TL has to have the TL zip modules.
If you load too many or unsupported modules you can also crash or black screen on boot. The too many part is worked out as of today, knock on wood.
Yea i downloaded the alpha 2 and my camera freezes when i try to shoot video raw. any help? i have a high speed udma 7 san disk cf card.
alpha 2 is very very very very very... old. I can see using a nightly or self compiled bin to test where the code is at the moment. At least try with that jan 21st build.
ok, can someone post the most updated version? i would love to be able to shoot raw footage with my underwater housing this weekend! thanks
g3gg0 merged the mlv_sound pull request => nightly builds are back: http://builds.magiclantern.fm/
Next thing that needs merging is the display filter. Its as stable as on 50D/5DII.
Quote from: a1ex on February 14, 2014, 07:40:10 AM
g3gg0 merged the mlv_sound pull request => nightly builds are back: http://builds.magiclantern.fm/
TGIF! ;-)
Sorry if this is something I should have read about somewhere (I tried to find it) but I just downloaded the latest (magiclantern-v2.3.NEXT.2014Feb14.7D203) and it's missing a bunch of modules, including the mlv ones. Is that normal?
Bugs:
Not fixed yet:
Focus hunt after dismounting "newer" lenses (100/2.8 L IS, 18-55 IS II, 55-250 IS II ...) and mounting "older" lenses (100/2.8 Makro USM, 50/1.8 II, Sigma 18-125 OS ...).
http://www.magiclantern.fm/forum/index.php?topic=9848.msg92378#msg92378
Needs confirmation, please test:
Card benchmark test will not terminate properly. Will get stuck at
[9/9] Reading: 99/100 (buf=128k)
Red LED is off.
Ciao
Walter
Heh, I'm getting a freeze toggling MLV or RAW if going right into movie mode from startup. Does it work the same on the nightly for 7D?
..ok I checked on the nightly... the bug is there, its not me.
can't seem to find how to shoot raw with this new nightly build. anyone else have the same issues? I'm kind of a newb at this ML.
Module tab -> Enable RAW_REC.MO and restart cam.
Movie tab -> RAW video -> ON
ok got it. and one last thing. whats the best settings to shoot on for 60fps raw? like resolution? i shot at 1280x514 and ML says crop it by 1.40 in post. did that and its still pretty stretched out. any ideas? thanks
I use the search tab and i come acroos with this, hope it helps you
http://www.magiclantern.fm/forum/index.php?topic=10195.0;topicseen
7D official nightly now has MLV modules.
Quote from: a1ex on February 14, 2014, 07:40:10 AM
g3gg0 merged the mlv_sound pull request => nightly builds are back: http://builds.magiclantern.fm/
Hi,
I am trying to install this last build of ML for 7D. I noticed there is just the autoexec.bin and the ML folder in the ZIP file. I know that i should use an installer. There is an EOS Card installer that I have, but this one is installing a ML build from september. How should I do with this new one? Do you have a link where I can find the info?
Thanks,
Yes, would be nice if some 7D users could create an install guide from scratch for Magic Lantern (not for Tragic Lantern).
Hi, sorry if this is the wrong place to ask this, but do I need Canon's 2.02.03 installed in order for ML to work? I can't find 2.02.03 anywhere to download.
Quote from: 1% on February 13, 2014, 10:17:36 PM
Nope, they won't match between the 2.
Sorry didn't mean it that way. I don't know how I have to write it, that you do understand my problem.
Read tons of posts and all infos I found here but didn't find an answer, so I try to explain here for the third time:
I have a 7D 2.0.3.
I download ONE firmware version (ML, link see above, OR TL link see above).
I format a checked and working CF Card internally in the 7D.
I copy ONE firmware (whole ZIP content) on that fresh SD card.
I power on the 7D.
I start firmware update process and get ML (OR TL) running just fine.
--------------------------------------------------------------------------------------------
SO FAR IT WORKS
--------------------------------------------------------------------------------------------
I go into the modules menu.
I chose (simplest way) one module (say dual_iso).
I activate it and get the text info that I have to reboot the 7D in order to get the module running.
I reboot the 7D.
After that reboot, the 7D ends up in a frozen Q-Screen.
No buttons work, even the on/off switch doesn't work.
To get the 7D running again I have to take out the (original) LP-E6 of the original Canon battery grip.
All I want(ed) to know from you is what I might do wrong and how I get running modules instead of a total freeze.
(On every try I format the card in cam and copy the whole zip-package. No mixed data. Always proper ML (or TL) but every time a full freeze after reboot with an (or more) activated module(s)).
I hope, now I explained it in a way you understand. If not, please ask, what you don't understand or have to know to help me.
Quote from: a1ex on February 14, 2014, 07:40:10 AM
g3gg0 merged the mlv_sound pull request => nightly builds are back: http://builds.magiclantern.fm/
I just tested with the zip downloaded above.
No fw upgrade possible, but with a 7D_203.fir that works.
ML runs proper again, but freezes with an activated module again :-[
As I scrolled through the ML features I only saw one thing that could be helpful:
In the Debug section there is a point called Memory Error. This has a red circle left of it and to the right the info "underflow, overflow".
When I go into that row ("mouse over") the bottom help text says in the 2nd line in a yellow font "underflow, overflow[31](0) at menu.c:866, task IPCTask."
Could that be the problem?
Or what does it mean?
Can't reproduce (tried with both current source and current nightly on fresh card).
Quote from: a1ex on February 17, 2014, 02:46:57 PM
Can't reproduce (tried with both current source and current nightly on fresh card).
Thank you for the test.
I thought that because otherwise there would be corresponding posts to be found here...
What about
QuoteIn the Debug section there is a point called Memory Error. This has a red circle left of it and to the right the info "underflow, overflow".
When I go into that row ("mouse over") the bottom help text says in the 2nd line in a yellow font "underflow, overflow[31](0) at menu.c:866, task IPCTask."
?
Is that normal or could the problem be here?
Are there incompatible boot-firs out there?
I use the 7D_203.fir from tragiclantern-v2.3.NEXT.2014Feb11.7D203 to boot from the CF card.
(The ML nightly has no FIR in the package)
It's not normal, but I don't get any warnings here. Tried with only dual_iso, with only raw_rec, with only mlv_rec and with all nightly modules loaded, took a few pictures, recorded a few raw videos... no warning in the Debug menu. Also ran a few memory tests and stub tests, all fine.
A video should help (include the card contents, the About page in the menu, and the exact steps from starting the camera until you get the error).
I've not seen the underflow ever. I've just had the cold boot to video -> toggle mlv rec freeze.
Quote from: RolandTJ on February 17, 2014, 12:53:45 PM
Hi, sorry if this is the wrong place to ask this, but do I need Canon's 2.02.03 installed in order for ML to work? I can't find 2.02.03 anywhere to download.
Anyone? I'd really like to use ML. I've found nowhere so far which tells me whether or not I need to go back to 2.02.03 from 2.02.05 to run it. If I need the 2.02.03 firmware, where can I download it? I can't find it via google.
Suffix of ML link for a given cam in the nightly area= required firmware version.
http://chdk.wikia.com/wiki/Official_Canon_firmware_updates
Quote from: Walter Schulz on February 17, 2014, 07:07:04 PM
Suffix of ML link for a given cam in the nightly area= required firmware version.
http://chdk.wikia.com/wiki/Official_Canon_firmware_updates
Thank you so much. I know it must seem like a silly/lazy question, but I did look very hard for a solution.
Quote from: Walter Schulz on February 14, 2014, 05:44:18 PM
Bugs:
Not fixed yet:
Focus hunt after dismounting "newer" lenses (100/2.8 L IS, 18-55 IS II, 55-250 IS II ...) and mounting "older" lenses (100/2.8 Makro USM, 50/1.8 II, Sigma 18-125 OS ...).
http://www.magiclantern.fm/forum/index.php?topic=9848.msg92378#msg92378
Seems to be fixed in today's ML nightly. Thanks, a1ex!
Quote from: Walter Schulz on February 14, 2014, 05:44:18 PM
Needs confirmation, please test:
Card benchmark test will not terminate properly. Will get stuck at
[9/9] Reading: 99/100 (buf=128k)
Red LED is off.
Still there and no confirmation. That's an easy one to verify/falsify. Come on, guys ...
Ciao
Walter
Made a few testes with MLV_Rec and still got corrupted frames in the beginning of the MLV file.
GD= On
Buffer= 2
Any chance of bringing GOP back to h.264?
Hi guys. I finally took the plunge and installed the latest ML nightly for the 7d. I know there is a lot of focus on RAW video, but I am wondering if it is possible to get 1920x1080 60p continuous without RAW? I see I can get 960x386 60p RAW. Would this be something in the FPS override module that hasn't been back ported yet? Thanks
Quote from: rdickerson on February 22, 2014, 06:36:58 PM
Hi guys. I finally took the plunge and installed the latest ML nightly for the 7d. I know there is a lot of focus on RAW video, but I am wondering if it is possible to get 1920x1080 60p continuous without RAW? I see I can get 960x386 60p RAW. Would this be something in the FPS override module that hasn't been back ported yet? Thanks
Not possible
1920x108060P is impossible to encode even if you got the LV that high. Remember its a HW encoder.
Gop and that stuff is on the other processor and while you can alter addreses and things like that I'm not sure how you'd make a cache hack from slave. So either that has to be figured out or have to find a way to run code on the 2nd proc without signed bins.
ML nightly feb 22.
The black border framing overlay is buggy and is off centered.
During standby its framed low and cuts off a portion of the top.
Upon start of recording, it becomes correct.
this stays correct from here on, while in standby/record/standby... and so forth.
It can be triggered to be off centered again, if you enter ml menu, go to file manager and view a file for instance, upon
going back to LV, its off centered again, until you start recording.
Quote
../../Makefile.user.default:24: *** missing separator. Stop.
This is what is busted... but my make -C works
the good news for the feb 22 ML nightly is.
Initial tests indicate no more pink/corrupt frames
Buffer-4, GD-on, reserve-on, ICON -on.
tested at 1X and crop mode.
Though crop mode is at 30fps for now since FPS over ride is not yet implemented in the ml nightlies.
Quote from: ted ramasola on February 23, 2014, 07:14:36 AM
The black border framing overlay is buggy and is off centered.
This one sounds like a 4:3-screen quirk. Did you ever notice it on 5D2? (or can you reproduce there?)
Quote from: a1ex on February 23, 2014, 07:25:54 AM
This one sounds like a 4:3-screen quirk. Did you ever notice it on 5D2? (or can you reproduce there?)
tested various layout options aside from 4:3 and its still there. A reboot or a lv switch off/on does not correct it. Only a press of record corrects it.
Didn't mean the setting from ML menu, but Canon's screen layout for the 7D (it's a camera with a 4:3 screen).
I wanted to know if the problem is specific to 7D or to 4:3 cameras in general (the other ones relevant for raw video being 5D2 and 50D). This hint would tell me where to look first.
The behavior is also present in the 5D2, feb 22 nightly.
hello, i´ve tested the lastest ML dev on 6D, everything worked fine, sometimes in RAW record when i´ve hit the button to stop recording it freezes, (had to remove the batery in order the screen to go off)
other report is, when i hit zoom, it did not record Raw with the cropped zoom. only normal
Hey everyone,
2 questions:
1.) Can anyone give me a recap of where 7D Raw development is at this point? I only started reading the forums recently and I'm a little overwhelmed by all the information and multiple threads. It seems that 7D RAW work went became a Tragic Lantern project for awhile but now that's stopped (?) and all the Tragic Lantern features are being brought back into the main ML stem? Yes No? Is development on Tragic Lantern halted at this point? I'm just wondering what threads I should follow for news.
2.) I'd like to donate, but I don't immediately see any option on the website aside from Bitcoin (which I don't have set up and would rather not use.) Do donations get spread out to all ML folks, or to the team working on a specific camera?
Tragic is with more features but without safe "rules", like the name say it, tragic. Now the dev's are porting stuff from TL to the main ML.
You can download here and try/test the ML for your 7D
http://builds.magiclantern.fm/#/
This is the right thread for you port your tests.
Testing the Nightly from Feb 24.
1. FPS override not yest implemented. (crop mode recording is still limited due to this)
2. Overlay/black border bug- Sometimes it is off centered upon start up-way to correct is to cycle through magnify button and it will be corrected.
3. HDMI monitoring is now OK - no more errors and pink frames
4. HDMI overlays not yet working well so is best to turn off GD when recording.(This is the gd switch in raw video sub menu)
5. Playback of raw video when HDMI monitor is connected.- Lock up when Global Draw in overlays tab is OFF -this bug is for 7D only and not found in 5D2.- Solution I found is to have Gloabal draw in overlay tab -ON and GD-OFF in Raw Video sub menu.
6. 30P Recording is continuous at 1728 x 736 2.35:1 - Tested this with audio and is OK no sync or drift problems.
7. High Framerates recording Now Possible with no errors and corrupt frames.
For 60 FPS (set in canon menu)
2.35:1 AR
1600x486 --25"
1536x466 --1'53"
1472x448 --continuous recording
2:1 AR
1408x504 --1'31"
1344x480 --continuous recording
16:9 AR
1344x540 --1'
1280x514 --continuous recording
If FPS override will be ported back from TL, higher resolutions is possible.
From TL at 50fps
2.35:1 AR
1664x506 --continuous recording
16:9 AR
1408x566 --continuous recording
Quote from: arrinkiiii on February 27, 2014, 10:35:25 PM
Tragic is with more features but without safe "rules", like the name say it, tragic. Now the dev's are porting stuff from TL to the main ML.
You can download here and try/test the ML for your 7D
http://builds.magiclantern.fm/#/
This is the right thread for you port your tests.
Awesome, thanks for the link!
So Tragic Lantern 7D is still in development then, but the features are being merged back into the main ML?
Also, is Bitcoin the only way to donate?
U more then welcome.
I think TL will stop, don't know really. But ML nightly is almost update with the TL. I think yes, that unfortunately bitcoin is the only way to donate.
With ML i still get pink/corrupted frames in 60fps with TL everything is ok.
just a quick question from work, as i don't have access to my 7d at home..
for a coming project i'd need to record stuff at 60fps (video playback will be direct from pc to beamer via h264 codec). most preferably non-raw but yet 1080p, shooting normal mpg will be sufficient.
is the current magic lantern (with FPS override i guess) working on 7d without problems in this mode/configuration?
h.264 can record 60fps but only at 720p
raw can do full HD in crop mode (x5 zoom) But only TL have fps override.
Quote from: arrinkiiii on March 10, 2014, 02:05:36 PM
h.264 can record 60fps but only at 720p
raw can do full HD in crop mode (x5 zoom) But only TL have fps override.
mhh sad, i'll stick to 30fps then. worked last year that way, too.
maybe i'll shoot raw though. depends on if i find time to test it out this week.
The fps override and good 60fps is already been porting from TL to ML ?
Mar 14 ML.
1. FPS override not yet ported back.
2. FIXED: Overlay offset bug mentioned in post http://www.magiclantern.fm/forum/index.php?topic=9848.msg104184#msg104184
3. Crop modes @30FPS
1728x972 16:9 -23"
1728x864 2:1- 1'30"
1728x786 2.20:1- continuous
1920x1080 16:9- 9"
1920x804 2.39:1- 46"
2048x872 2.35:1 -15"
2048x856 2.39:1 -16"
4. 60P
1728x516 2.39:1- 10"
1600x478 2.39:1- pink corrupt frames
1344x408 2.35:1- continuous
Not try yet the solved overlay bug but it's good to know that is already gone. Yes, fps override its a must and trying to get the same resolution that TL can achieve with 60 fps with the ML version. I think after this 2 things the 7D is quiet good for recording, at least video... not making so much testing in photo mode.
With this 2 problems solve + the dark frame subtracted or + PFN pattern/noise problem solve = a great video machine.
Another thing that would greatly "extend" the usability of these cameras in professional environments would be a solution on how to get a faster refresh at the same time the ability to see proper framing in the higher resolution of crop modes.
With a lot of shooters getting all excited with these new 4K cameras, having a "free" working 2K-2.5k cam already in your hands would make you think twice if the difference is worth it.
Right now, using crop modes would be limited to locked down shots.
You can frame, hit info for fast refresh, do some short moves, pan or tilt, but at that point framing would be guesswork.
I'm no coder, but somehow if in 1X mode a black crop/frame shows whats recorded, perhaps somehow the camera can be "tricked" not to magnify/zoom and allow cropped3x recording. I really don' know if that is technically possible.
or perhaps via HDMI? That through hdmi a whole view of the sensor is shown while the camera records in crop mode, that way we can just mask out the area recorded area.
Again, I'm just throwing ideas out here with no technical basis whatsoever, purely speculation.
Speculation, imagination, need... is the father of invention. It's all good and is needed =))
Yes, good Lv in crop mode would be neat and can get the camera in more professional work/environment.
Related to new cameras that start to show up with the capability of 4k.... Sooner or later we must face the cruel reality, i think our beloved machines will be obsolete. But until there let's rock this beautiful machines.
Testing Mar 14 and 15 ML nightly.
If you switch from photo to movie and quickly press start/stop button, h264 recording will start even if MLV Raw module is loaded.
Tested on both Manual (since you have to press start/stop to open LV) and EF lens.
I'm not sure what I can do about this.
If I remove the LiveView check (that is, hook the record button only when LiveView is up and running), there will be major side effects (e.g. with manual lens you will not even be able to enter LiveView).
I could try to autodetect when LiveView is starting up, but not yet initialized, and hook the button in this case too. However, this one is fairly invasive (core changes) and requires some more thought. It does improve things, but it does not solve it completely (you just need to be faster when pressing the button).
For now, a clean workaround may be to allow H.264 stop cleanly if you managed to start it.
Faster refresh... with the grayscale preview we are limited by CPU power and by our coding skills, and reconfiguring LiveView resolution is well beyond our current understanding of Canon code.
...and the fps override? It's possible to porting from TL to ML? Also good 60fps to ML?
Yes, but all these take time and effort in understanding how they work. Again, if you have coding skills, don't just sit down and wait for me to port everything.
No, no im not waiting for nothing, i just want to understand good/better things for my self (for not posting wrong things) and for explaining to others that arrive with questions here in the forum.
I would like to know code (only pascal from 20 years ago that i already forgot =))
Didn't mean you personally, but anyone who has coding skills and 7D.
ok, sorry =))
GUYS !!! CODING SKILLS ARE NEEDED !!!
BTW, I've compiled the latest installation for 7D (the same one that I wrote these days for 5D3.123 (http://www.magiclantern.fm/forum/index.php?topic=11017)) and... it worked!
Let me know if it works for you (the latest nightly includes the FIR). If it does, the installation will be as simple as unzipping ML file and running Firmware Update.
If i understand good you can download this in here http://builds.magiclantern.fm/#/ ?
and just follow this instructions?
Installation:
1) Format the card from the camera.
2) Make sure you are running Canon firmware 1.2.3.
3) Copy ML files on the card and run Firmware Update.
Uninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.
Yep, just don't put the 5D3 firmware on 7D :D
Quote from: a1ex on March 16, 2014, 04:14:09 PM
Yep, just don't put the 5D3 firmware on 7D :D
lol, all most did that =DD ...but is good to wright this things here for other people also understand better.
Wend i format the card in camera should i chose delete the ML files?
If you want to mimic a first-time install, yes.
Uhmmm, yes i already got bootflag my camera, just need to copy the other files to the card. Just want to test the fir and make the update thing and see...
With the .bin everything go's good, make 2 video clips and no pink frames. will see with 50fps and 60 fps and also using the fir uninstall and install.
(love the proper framing in LV, now i can see the white left boarder and also the previewing the clips in camera and return to Lv also good).
EDIT: Im notice that wend in LV the image is a little bit (don't know how to say this is english) but kind of jerky, not smooth.
The new installation procedure doesn't work for me.
I used the "old" bootoff.fir to reset the bootflag. Verified that bootflag is missing with a second card.
Deleted bootoff.fir, copied all ML files to the card, tried firmware update. After initial screen display went white. Red LED not doing anything, display remained white, had to pull out battery.
Ciao
Walter
No luck with today's ( 2014-03-17 00:31:14) build, either.
Bootflag set (old booton.fir), all cam settings set to default, dialed M: Tried to update. Initial update message appears, after some seconds screen went white.
Where is the error? Build or cam?
Ciao
Walter
Will double-check today; don't use the FIR until further notice.
Solved, sorry for trouble.
You don't have to apologize! Shit happens and no harm was done!
Ciao
Walter
BTW, does the FIR work with 64GB cards or larger?
On 5D3 I had to rename the FIR to 8.3 characters (not shorter); is this renaming also needed on 7D?
Can't test it. As yourself I'm a still shooter. I'm experimenting with video on a very low level and therefore had no need for such a big card.
And my 7D is resting at home.
Ciao
Walter
My card is 8GB (yes, is what i still use for video) Maybe Ted can try this.
Makes one think about funding a big and very fast card for a1ex ...
Quote from: Walter Schulz on March 17, 2014, 03:28:28 PM
Makes one think about funding a big and very fast card for a1ex ...
Yes, good idea. If he agree we can make this easily and fast =))
a1ex, give it a nod! ;-)
BOT:
Installation procedure works now. I tried several times.
During first test 7D_203.FIR went missing from the card but I was unable to reproduce this error.
As said I couldn't test with 64 GB.
Ciao
Walter
I tried new installation method on a 64 gb card from Komputerbay, and everything went smoothly.
Quote from: a1ex on March 17, 2014, 12:08:27 PM
BTW, does the FIR work with 64GB cards or larger?
On 5D3 I had to rename the FIR to 8.3 characters (not shorter); is this renaming also needed on 7D?
Tested to remove bootflag and install fir from mar 17 ML 203.
Successful installs using
64gig 1000x and
128gig 1050x Komputerbay CF cards.
Finally I've bought a new card reader and test the new .fir installer/uninstaller. It worked like a charm without any problem.
Thanks Alex!
Testing Mar 18 Nightly.
At 1728x 972 I notice the image would tear when there is HDMI monitor attached. With no HDMI attached the image is ok.
Link to a sample frame with tearing.
https://scontent-a-dfw.xx.fbcdn.net/hphotos-prn1/t31.0-8/1115948_454560808008042_1036050560_o.jpg
Tested Mar 20 Nightly.
Still the same behavior as above. When HDMI monitor is attached, there is tearing of image and occasional pink/magenta corruption.
Without HDMI monitor, all frames clean.
Quote from: arrinkiiii on March 16, 2014, 04:11:48 PM
If i understand good you can download this in here http://builds.magiclantern.fm/#/
and just follow this instructions?
Installation:
1) Format the card from the camera.
2) Make sure you are running Canon firmware 2.0.3.
3) Copy ML files on the card and run Firmware Update.
Uninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.
Confirmed today. Works like a charm.
Mar 20 nightly.
Some pink corrupt frames when recording in 60P.
1728x526 - has corrupt frame
1600x644 - clean
1472x592 - has corrupt frame
FINALLY! No hang up after reboot with activated modules! I'm finally into ML - Yess! :D
(some may remember - I'm maybe the only guy who had that kind of trouble with Alpha, TL and so on...)
@Ted
With the few last nigtly ML you don't feel that the Lv is kind of with delay (can't find the correct word) ? The best buffer is 1 ??
No, I did not notice a delay in LV. I'm still testing with buffer 1, so far its ok. Tested mar 24.
OK, thanks Ted. It's just a small delay, kind... Will test more and see what going on.
mar 25 nightly
Tearing in image still present. Tested 1729x 972
Tested with or without HMDI monitor.
Theres a slight pattern in my tests.
A.)after removing hdmi connection and toggle LV off then on, the first 1st take is clean, 2nd take tearing and pink corruption in several frames.
B.)switch OFF then ON/then LV ON, 1st take with tear and pink corruption, 2nd take clean.
When at last comes "frames override"?
The Nightly of Tragic has not all modules. (DUAL-ISO)
So that makes no fun to strike up there on the Cam.
Greeting
Confirming tearing still exists.
* 2014 May 25 Nightly Build ML7D.203
* Raw 2.0 (mlv)
* 1532 x 1148 resolution
Using HDMI out.
Hi, I'm new here and while I've been meaning to install ML for awhile, I'm only now getting around to it. My question is: For photographers, what is the best build to use for the 7D? Should I go for the nightly build (2.5)? Sounds risky. What is the latest, most stable build and where do I find it?
Thanks so much.
Hi, from here http://builds.magiclantern.fm/#/ you can download for 7d the latest ML version.
Overwrite the firmeware and you are ready to go.
Cheers.
1. Can someone tell me if it is possible to record for 130 minutes continuously using ML on a Canon 7D. If so, then what are the settings?
2. BTW there is a bug in the nightly build 2014Mar29.7D203.zip
On auto the 7D only records video for a few seconds before switching itself off. Not sure where to report this.
So i installed 2014Mar24.7D203.zip and i got the same bug error message. Settings RAW video ON 1728x972. I think i need to set the write speed to 70.0 MB/s at 25.000 FPS but the FPS Overide item has disappeared from the Movie menu.
3. In Modules menu - what is the difference between the raw_rec and the mlv_rec.mo items. Both are 14bit raw but the second one seems to be a version 2.
Quote from: abbyeagle on March 29, 2014, 01:16:30 AM
1. Can someone tell me if it is possible to record for 130 minutes continuously using ML on a Canon 7D. If so, then what are the settings?
2. BTW there is a bug in the nightly build 2014Mar29.7D203.zip
On auto the 7D only records video for a few seconds before switching itself off. Not sure where to report this.
So i installed 2014Mar24.7D203.zip and i got the same bug error message. Settings RAW video ON 1728x972. I think i need to set the write speed to 70.0 MB/s at 25.000 FPS but the FPS Overide item has disappeared from the Movie menu.
3. In Modules menu - what is the difference between the raw_rec and the mlv_rec.mo items. Both are 14bit raw but the second one seems to be a version 2.
1. If shooting h264 you could fit that time in a 64gig card. Auto restart will let you record with your 7D unattended, everytime a 4gig limit is reached and it stops ML will automatically start recording. Gap is 1 sec.
If shooting raw, a 256gig will do about an hour. You'll need a very fast CF for that, at least 1000X. Pray it won't overheat.
2. what auto setting is that specifically? I tested the latest posted now and its continuous with no errors filling up a 32gig CF card.
3. raw_rec has no sound recording. mlv_rec has sound and metadata. DO NOT LOAD THEM BOTH AT THE SAME TIME. choose one you'll use. Loading both will affect camera performance.
As a test report for Latest build with timestamp Mar 29.
1728x972 MLV Raw+Sound
1.tearing and corruption of video image if HDMI monitor is attached.
2. all clips in test clean and OK when NO HDMI is attached.
3. Capacity tested a 32gig CF. So far, the video was clean, audio remained in sync.
Essential features not yet implemented.
1. FPS over ride
2. Headphone monitoring
Yes, that 2 features are very important and needed very bad.
Essential features not yet implemented.
1. FPS over ride
2. Headphone monitoring
Hey guys - ML noob here. I grabbed the 3/29 nightly for 7d and was in the process of learning it. I noticed my time was off a couple of minutes, so I went into the Canon menu and adjusted it. Now, once a minute, it appears to flicker the time selection on top of the ML menu.
I grabbed a video with my phone to show what I mean:
https://www.dropbox.com/s/y1bvnhe0w918jk3/time%20flicker.mp4
Thanks to all working on this project. I'm truly excited about learning what I can do with ML!
-Jason
Is it still flickering after a camera reboot?
I had the 2.0.5 firmware on my 7D. I just downloaded the 2.0.3 firmware from the first page and downgraded without a problem. then i installed ML and works great.
I read that you couldn't downgrade, but it worked. Maybe this will help someone else too.
sorry to sound like a newb, but i just updated my magic lantern to the latest 7D build but i have no options for frame rate, RAW, resolution etc under Movie menu.
thanks
Did you past all folders to the CF card? Did you enable the MLV raw module in the module menu?
hey arrinkiiii
thanks for the reply, that helps I've installed modules mlv_play, mlv_rec, and raw_rec. what modules do you have installed on your 7D? whats the difference between the 2 record modules.
also when i recorded the video and played it back it was really slow is this normal?
thanks matt
U welcome.
In the modules you just need to load the mlv_rec for raw and if you want sound in your raw load the mlv_snd, if you want to preview raw video in camera load the module mlv_play. Never load the mlv_rec and raw_rec at the same time. ram_rec is the first version of raw module, not have sound or metadata.
Yes, it's normal, camera cpu is slow. Thanks to the god's of ML we got preview in camera, even if is slow is just great.
Use search tab or navigate in the forum, all the questions/answers are here =))
also what the optimum setups for shooting RAW on a 16GB CF card canon 7D. what frame rate and resolution/aspect ratio should i be shooting?
its says it can't write 1920 x 1080p to my card, because it requires 67.1 MB/s at 24 fps. is my CF card not quick enough?
thanks matt
Yes - just confirmed.
Quote from: ted ramasola on March 30, 2014, 06:57:01 AM
Is it still flickering after a camera reboot?
Quote from: ffunky on March 30, 2014, 03:54:40 AM
Now, once a minute, it appears to flicker the time selection on top of the ML menu.
Move Canon menu to a tab that does not show the clock.
That's all it took to fix. I feel stupid now. Perhaps this can take the lowest priority position for a bugfix. ;)
Quote from: ffunky on March 30, 2014, 10:50:11 PM
That's all it took to fix. I feel stupid now. Perhaps this can take the lowest priority position for a bugfix. ;)
Make sure you don't put the date/time/zone on the "My menu" if 'My menu' is your default setting.
I am running the nightly build from March 23, 2014 and was shooting today. My camera ran into an Error 30 in the middle of my shoot then displayed I had a dead battery. I removed the battery and replaced it with a fresh battery. I shot five frames and the battery displayed it was dead again and the camera would not respond.
I took the battery out and changed memory cards to one without ML and the battery was full and camera fully functional.
Thank you for continuing to work on this amazing software!!
Chris
As i can't find the tragic lantern Thread for 7D anymore i post it here..
The last 2 weekends i've been shooting with tragic lantern (as magic lantern hung up on my cam three times at random actions and that i don't want to have in production..) with the cam set to ntsc and shooting at 30fps (which seems to be 29,97 infact..?!). audio was set to separate wav as i thought i would have any benefit from it.
recording with focus peaking to standard canon mpg went pretty flawless so far. i'll post the numerous crash logs when i get home. had to pull the battery a couple of times which was not really mounting faith in the current development.. :-/
with separate wavs i missed onscreen audio meters, so it was pretty much a guess-and-run filming stuff. luckily i have the audio from my rode videomic pro passed through a zoom h1 to the camera. i hope this saves me from unuseable audio if needed..
and i got me quite unawared that separate audio needs canon audio to be deactivated. i noticed that before shooting the actual clips luckily..
the worst problem sofar was the on some clips i have a severe drift between audio and video! an other clip from the later day without changed options (only battery because it died on me), the audio for the 30seconds we needed seems to be consistent.
the earlier day clips show a drift even after some 30 seconds. how the hell can that be?! i hope i can compensate with the H1.
editing is done via premiere with project and clips set to DSLR at 30fps.
so what build and options can be used for serious production shooting? no raw needed, just some stable and consistant working stuff...
Quote from: mburgst on March 31, 2014, 03:16:27 PM
so what build and options can be used for serious production shooting? no raw needed, just some stable and consistant working stuff...
Easy: Don't use a 7d at all (port not stable yet). The T-Word might be tested more on 7d atm, but code-wise it's more experimental so your best bet is to support a stable 7d ML version with filing good bug reports and testing nightly.
Quote from: Marsu42 on March 31, 2014, 03:19:31 PM
Easy: Don't use a 7d at all (port not stable yet). The T-Word might be tested more on 7d atm, but code-wise it's more experimental so your best bet is to support a stable 7d ML version with filing good bug reports and testing nightly.
as said i tried a ML nightly and it locked up my camera when doing some testshooting.
without all those bells and whistles (raw and such) i had hoped ML would be stable to offer basic recording stuff + focus peaking (if canon doesn't make it include this... *le sigh*
oh btw.. this i completely forgot.
when i import the audio clips from the cam into premiere those wavs are always way way way too long. like several minutes when a videoclip recorded is just like 30 seconds long. the wavs themselves seem to be ok'ish judging the content. after clip has ended there's only empty audio..
didn't the wav clip get ended until a new videoclip was started?! or something like that?
Something that I notice that I didn't know. When you press the picture style button it will appear one menu in screen, depend how many times you press it will leave you to WB menu or to Sound menu, then with joystick you can choose/control the settings without the need to go in ML main menu. Just so practical.
Other thing that I notice is when your are in crop mode if you half-press and stay press the shutter button you can change from gray preview to full color preview but if you leave the button you return to the default preview. In the past you have the ability to just click/half press one time and he stay in that preview, you press again and change the preview. Now you need to stay press for stay in that preview. It's possible to change this?
Quote from: mburgst on March 31, 2014, 03:25:11 PM
as said i tried a ML nightly and it locked up my camera when doing some testshooting. without all those bells and whistles (raw and such) i had hoped ML would be stable to offer basic recording stuff + focus peaking (if canon doesn't make it include this... *le sigh*
... which is exactly why the T was abandoned by the ML devs (except for one :-)): stability fixes weren't backported, giving ML a bad name and making T* (= almost solely ML code) the premier choice for all 6d, 7d an m users.
I understand your "I just want to use it no matter the future development" perspective, but right now you can either use _L and deal with issues elsewhere, or try ML once again & report bugs - with my 6d, I did the latter.
Quote from: arrinkiiii on March 31, 2014, 04:21:23 PM
Other thing that I notice is when your are in crop mode if you half-press and stay press the shutter button you can change from gray preview to full color preview but if you leave the button you return to the default preview. In the past you have the ability to just click/half press one time and he stay in that preview, you press again and change the preview. Now you need to stay press for stay in that preview. It's possible to change this?
full color preview in crop mode using ML
-Press Half Shutter.
To leave it on
Go to Prefs>Misc Key settings>sticky half shutter ON
Note: Start /Stop rec button will not work when half shutter (HS) is ON so,
Start rec/Press half shutter to view in color-(when ready to stop)-press again to turn OFF/Stop rec.
Thanks Ted, I have been looking for that option in ML menu. But if I chose that option the start/rec button don't work? It always have been like this? I think I remember half press change and then press rec button for record, no? I remember see this in bitbucket but didn't think it was for the 7D.
Will try and see the best way to work with it =))
Quote from: Pelican on December 21, 2013, 09:55:34 PM
If you want a stable ML on your 7D you can help testing different functions and compare these functions in TL and ML.
What the developers need mostly is feedback.
I am more than willing to help out here. I've been making bug reports on the bitbucket repository's "Issues" track: is this the best way? If so, can someone add a "7D" option in the "Version" pop-up?
I'm also willing to try some coding if that will help.
Quote from: bischofftep on March 31, 2014, 08:55:15 PM
I am more than willing to help out here. I've been making bug reports on the bitbucket repository's "Issues" track: is this the best way? If so, can someone add a "7D" option in the "Version" pop-up?
I'm also willing to try some coding if that will help.
If you know some code for sure that you can help the dev's.
I just installed ML nightly build (march 26) for my 7D. Overall, it seems like a great improvement over the alpha that I tried a long time ago.
I did experience what seemed like occasional gui glitches (everything but the selected text item disappeared, pressing "Q" brought me back.) Is this a known issue, or would you like a reproducable case/screenshot?
-h
hey there everyone! i have just a stupid question as i am very confused right now. :-[ had tl on card. now want to install ml. do i have to remove bootflag from camera? and how do i do that? and do i have to remove bootflag from card too? and how do i do that?
Quote from: Haruki on April 01, 2014, 03:42:56 PM
hey there everyone! i have just a stupid question as i am very confused right now. :-[ had tl on card. now want to install ml. do i have to remove bootflag from camera? and how do i do that? and do i have to remove bootflag from card too? and how do i do that?
Just remove/copy the files to your card.
Quote from: Pelican on April 01, 2014, 03:45:40 PM
Just remove/copy the files to your card.
thanx a lot for the quick answer. so the bootflag thing is still needed!?
because i see that there is a .fir file in the ML nightlies. Do i need that too? or is that just for people with no autoboot?
and do i have to do the firmwareupdate like its said in the first post?
sorry for the dumb questions...
Do as told and you'll be fine!
FIR is needed to make your cam bootable. Once. And it treats your card the same way (bootable).
ML still requires the bootflag enabled to allow autoexec.bin to run on startup. The .fir firmware update just toggles the bootflag and marks your memory card as bootable. In your case both are already done so you don't need the .fir file, you only need to delete the TL files then copy the ML files over to your card.
In the future if you do want to remove the bootflag (and hence disable ML completely), just flash that .fir and wait 30 seconds (as per the onscreen instructions). It'll toggle the bootflag off for you. To make the card no longer bootable, just format it from your computer.
Thank you guys! Now I understand. I will test MLnightlies and can hopefully give some feedback/bugReports afterwards. cheers.
hey guys, maybe a stupid questions but do I now not need to do any permanent bootflag changes on my 7d? I can just load the files and then uninstall the firmware to be back exactly how it was before? (unless something unanticipated happens?)
Bootflag can be removed.
Sorry for maybe the stupid question... can ML be installed on a 2.0.5 firmware upgraded 7D? Is it too late?
No, too early. ;-) Downgrade to 2.0.3. Can't be done according to Canon but several users have done it with success.
Quote from: Piergiorgio on April 02, 2014, 03:32:28 PM
Sorry for maybe the stupid question... can ML be installed on a 2.0.5 firmware upgraded 7D? Is it too late?
Downgrade to 2.0.3 then install ML...
Hi all:
Is there a "lead" developer working on 7D issues, or who did the 7D port? I'd like to PM them with some questions and thoughts about the 7D problems that seem to be related to having an HDMI monitor plugged in.
Thanks in advance,
Okay so to run it on a camera with no previous versions of ML on it I have to copy the following files onto my card and then run the installer in-camera?
"ML" folder
7d_203.fir
autoexec.bin
And that's it? Thanks for the clarification.
correct.
Quote from: Walter Schulz on April 02, 2014, 03:43:09 PM
No, too early. ;-) Downgrade to 2.0.3. Can't be done according to Canon but several users have done it with success.
Ok i'll try, thx!
IT WORKS!!! :D
Hi all, i've installed ML on the 7D camera but there is'nt the headphone monitor option under the audio menu, so i can't use the AV cable and the live view at the same time. Is it different form previous version or the feature is not implemented yet?
Quote from: Piergiorgio on April 03, 2014, 05:48:13 PM
Hi all, i've installed ML on the 7D camera but there is'nt the headphone monitor option under the audio menu, so i can't use the AV cable and the live view at the same time. Is it different form previous version or the feature is not implemented yet?
Frames override not yet implemented in ML for the 7D and i think monitoring the sound from camera not yet also (don't use so much the sound in this days).
Quote from: bischofftep on April 02, 2014, 10:35:59 PM
Is there a "lead" developer working on 7D issues, or who did the 7D port? I'd like to PM them with some questions and thoughts about the 7D problems that seem to be related to having an HDMI monitor plugged in.
I think the best place for talk about this is here in the forum. For code maybe it's good to start here http://www.magiclantern.fm/forum/index.php?board=25.0 or here https://bitbucket.org/hudson/magic-lantern/commits/all
I have installed ML Alpha2. And as soon I press record the first time the sound by it self sets -40 on the meter and there are no sound.
Can anyone help me?
Has anyone experienced the following GlobalDraw issue:
After installing the Magic Lantern nightly build 2014-04-06 00:31:11 +0200, GlobalDraw seems to only work in LiveView anymore. All the additional information has disappeared from the Canon menu, and the "Don't click me" test produces only a black screen. ML text information such as the CPU usage is displayed though, but no graphics are drawn (I assume the additional information in the Quick settings menu that are not displayed anymore are rendered graphics).
Yes, GlobalDraw is switched "On, all modes". :)
It's not a big issue, but I'm wondering if anyone has the same problem and if there's a solution to it.
Delete card's ML directory and copy latest nightly to card. Try again. Results?
Hi there I am trying to install this on my 7D, however it just says 'update file cannot be found, please check memory card and reload the battery and try again'
The file is DEFO on the memory card so not sure why its going wrong.
Tried this on my axtremex 128gb card, kingston 32gb card, and sandisk 8gb, no joy, any ideas?
You're using latest nightly?
http://builds.magiclantern.fm/#/
Quote from: Walter Schulz on April 07, 2014, 07:00:22 PM
You're using latest nightly?
http://builds.magiclantern.fm/#/
Yes defo, tried both Apr 6th and 7th, firmware is 100% 2.0.3
1.) Format card in cardreader (NTFS or anything other than FAT32/exFAT)
2.) Format card in cam
3.) Copy contents of latest nightly to card via cardreader.
4.) Try to install via Canon's firmware update menu again.
Just tried that, same error message :/, tried without a lens attached and with a lens attached (No idea if this makes any difference)
Go to http://chdk.wikia.com/wiki/Official_Canon_firmware_updates and download firmware version 2.0.3 and install it. It's possible that your 2.0.3 differs a bit. Sorry for the bad pun but I'm told such things happened.
If this doesn't help: Have you tried to reset the cam to factory defaults (including Fn)?
Ok done, and nothing works :( , new firmware, tried, no go, reset all, no go, nothing :(
What's happening here?, is it 'safe' to change the file name ?
Just tried again and it worked, ??? random, but pleased! lol
Iirc you must use a cf card 8 GB or smaller to install ML. Mine worked the first time I tried it and was using a Lexar 8 GB 200x.
Limit was(!) 32 GB and today with built-in installer the sky is the limit.
4 GByte was a CardTrick limit.
hi guys,
i got a question relating cropmode 3x/5x in raw video. Would it be possible to bind a camera key to a function which toggles the 5x preview from canon to 3x grayscale preview? In my opinion it would really speed up the exposure, framing and setting up the focus.
Quote from: arrinkiiii on March 29, 2014, 01:43:18 PM
Yes, that 2 features are very important and needed very bad.
Essential features not yet implemented.
1. FPS over ride
Last week I back ported FPS over ride in RAW rec mode (not H264) from TL, I pushed a pull request to the main that await validation.
Yes, i saw that, THANK YOU SO MUCH !!! Why it's taking so much time to validation? The dev's need to try the code first?
Do you think back porting the audio also?
Quote from: arrinkiiii on April 09, 2014, 01:33:13 PM
Yes, i saw that, THANK YOU SO MUCH !!! Why it's taking so much time to validation? The dev's need to try the code first?
Yes.
Quote from: arrinkiiii on April 09, 2014, 01:33:13 PM
Do you think back porting the audio also?
I'll try to look at it but before that I need to figured out how this work in hardware... Do I need to build a custom audio cable ?
Uhmmmm i hear some people use the AV cable for the headphone and others use this "special cable" that you can buy or make one. I think someone here in the forum can tell you better then me, don't use so much the sound from camera... but i want =))
Anyone?
The Canon 7D ships with a AV cable, which looks almost like a mini-firewire on one end, and has analog video and audio plugs on the other.
But that is to send audio out, to headphones or the like.
To record audio with RAW footage, I think you have to use the MLV module.
Are these the correct instructions for installing on the 7D?
http://wiki.magiclantern.fm/install
Close enough. Give it a try.
1. Download latest nightly build and expand contents to card.
2. Run firmware upgrade from Canon menu
3. Restart cam before 30 second timeout
32 GByte restriction doesn't apply anymore.
Quote from: vyskocil on April 09, 2014, 02:30:29 PM
I'll try to look at it but before that I need to figured out how this work in hardware... Do I need to build a custom audio cable ?
The "special" cable from sescom sold by BH is $44 http://www.bhphotovideo.com/c/product/765530-REG/Sescom_DSLR_550D_HOCF_DSLR_550D_HOCF_AV_Out_Headphone.html
So I used the usb av out cable that comes with the camera.
You can buy an rca to mini phone jack cable like this, http://www.rakuten.com/prod/c2g-6in-value-series-one-3-5mm-stereo-female-to-two-rca-stereo-male-y/208181495.html?listingId=231860064&scid=pla_google_BisonOffice&adid=18165&gclid=CIvIufzu1L0CFSsQ7AodF0sAyg
What I did was cut off the rca from both cables and soldered them into a short compact adapter for use with my headphones.
Quote from: ted ramasola on April 10, 2014, 04:27:52 AM
The "special" cable from sescom sold by BH is $44 http://www.bhphotovideo.com/c/product/765530-REG/Sescom_DSLR_550D_HOCF_DSLR_550D_HOCF_AV_Out_Headphone.html
Fuck!!! This guys abuse of the price =((
Quote from: ted ramasola on April 10, 2014, 04:27:52 AM
What I did was cut off the rca from both cables and soldered them into a short compact adapter for use with my headphones.
Nice one =))
Hi guys,
Good contact to you all after being reading about all the amazing progress of the 7D Raw for the last months. I need some help. Is there any way to avoid the below issue with red dot when shooting Raw? My 7D has no issues with death pixels (just came from Canon...which I sent to make sure). I have tried different builds and all imaginable settings of ML and camera itself, and the red dot still there. Any idea how I could fix that, or I am just the blessing one to have a 7D to happen to show that problem? I would really appreciate any help. :'(
<a href="http://www.pixentral.com/show.php?picture=1El1xTtQhVEamFdkAhYQPKCiz0ey00"/><img alt="Picture hosted by Pixentral" src="http://www.pixentral.com/hosted/1El1xTtQhVEamFdkAhYQPKCiz0ey00_thumb.png" border="0"/></a>
<a href="http://www.pixentral.com/show.php?picture=1tsI1l5mZonIEhzqn5KZLGqOQIq6f"/><img alt="Picture hosted by Pixentral" src="http://www.pixentral.com/hosted/1tsI1l5mZonIEhzqn5KZLGqOQIq6f_thumb.png" border="0"/></a>
Thank you!
Hey guys, I finally got the balls to upgrade from the alpha 2 to the latest nightly build and it seems to work like a charm, though I can't seem to find the GOP setting (to allow all-I frames). I did some searching on the forum, but that trail just seems to end. Is it no longer there (or not yet?) or am I looking in the wrong place?
It's not working, yet....
Yet?
Is there a developer working on GOP/ALL-I?
"Failed to create file. Card full?" What does this message mean? Today I wanted to see how long it would continuously record to 128gb CF card since I never shoot continuously longer than 4-5 minutes at a time and I was curious. After first 10 minutes or so, it stopped recording with this message so I turned it off and back on to try again and it stopped after around 10 minutes with the exact same message. Does anyone know what it is?
i hope everyone is aware of LYTRO ILLUM??
probably we can expect that with ML
Quote from: arrinkiiii on April 22, 2014, 10:11:39 AM
It's not working, yet....
Thanx for the update, I hope it comes back soon.
Hi guys,
I was really happy with ML on my 7D. But unfortunatly I gave it to a CPS partner to check the AF with my 70-200 on the 7D. Now I have the 2.0.5 firmware running and therefore no ML possible.
Is it possible to downgrade to 2.0.3(with Linux)? I found something online but it requires Windows, but I have no Windows avaible until next week.
Any hints? Thanks
Hey all! Been away from a while.. is the ML build up to date to the Tragic Lantern build? Or are still some features missing?
Thanks!
Quote from: r4ptor on April 25, 2014, 10:21:31 AMIs it possible to downgrade to 2.0.3(with Linux)?
Download http://pel.hu/down/eos7d-v203-win.zip from http://pel.hu/getpage.php?pg=eoscard
It's just a zip compressed file containing the FIR you have to copy to your card. Run Canon's firmware upgrade process to downgrade to 2.0.3. Sounds funny but works.
Ciao
Walter
Oh well ok, i thought it would be more complex since maybe Canon doesn't want us to downgrade.
Thanks, I'll try it.
Quote from: tonybeccar on April 26, 2014, 12:31:23 AM
Hey all! Been away from a while.. is the ML build up to date to the Tragic Lantern build? Or are still some features missing?
Thanks!
Has anyone managed to get FPS override working on ML for 7D? I've been away also.
I've also gone to 2.0.5 and want to try to downgrade to 2.0.3 to run ML but I can't find the camera firmware anywhere. I found lots of links to it but when you actually follow them they are either broken or take me to the latest 2.0.5 version. Does anyone know a working location yo download it?
Thanks!
Quote from: brantz on April 30, 2014, 04:17:51 AM
I've also gone to 2.0.5 and want to try to downgrade to 2.0.3 to run ML but I can't find the camera firmware anywhere. I found lots of links to it but when you actually follow them they are either broken or take me to the latest 2.0.5 version. Does anyone know a working location yo download it?
Thanks!
http://chdk.wikia.com/wiki/Official_Canon_firmware_updates
Quote from: jayzed on April 26, 2014, 10:56:05 PM
Has anyone managed to get FPS override working on ML for 7D? I've been away also.
https://bitbucket.org/hudson/magic-lantern/pull-request/464/fps-override-for-7d-in-raw-recording
Hi
Is there known problem with battery consumption? I have left my camera off couple of days and battery was near empty. Have replaced with full battery, but it was 40% empty after 3 days. Camera was off all the time. Batteries are OK.
Installed ML Nightly.2014Apr23.7D203
Keep on
Same here. Full battery - let it sit a couple of days - dead battery.
Quote from: Walter Schulz on April 30, 2014, 05:12:46 AM
https://bitbucket.org/hudson/magic-lantern/pull-request/464/fps-override-for-7d-in-raw-recording
Excellent. Thanks Walter.
Hi mates,
Time for a noob question:
I'm preparing to install ML on my canon 7D.
1-Downgrade to 2.0.3
2-Download a Nightli builds from the ML website and follow the guide.....but.....
:-\ Where can I find the last guide for my 7D to make a bootable card and install ML from Mac?
Any suggestions?
Grazie,
Ciao!
http://magiclantern.fm/forum/index.php?topic=9848.msg110958#msg110958
Quote from: Walter Schulz on May 02, 2014, 06:14:40 PM
http://magiclantern.fm/forum/index.php?topic=9848.msg110958#msg110958
So you're suggesting i don't need a to make a bootable card anymore?
The don't talk about bootable cards there... It seems easier...
http://magiclantern.fm/forum/index.php?topic=9848.0
I'm using the April 30th build on my 7D. Using a Sandisk Extreme 32gb 60MB/s. Using the 4:3 mode at 1344x1008 that's supposed to just require 54.2MB/s I'm still getting weird frames, random shifts in colour temperature, and occasional corrupt .raw files that raw2dng won't recognize.
Is this because of my card? I'm buying the 1000x Lexar 32GB. Will that do?
Is there a 4:3 or 3:2 resolution that's stable (no drop frames, pinkish frames, shifts in temperature) and in use right now? I ask mostly because I intend to use if with a 2x anamorphic adapter.
Thanks to anyone that might enlighten me on this.
EDIT:
Here are some sample images. Now that I look more closely, it's not so much temperature change but like a saturation loss in certain parts of the image:
(http://img.photobucket.com/albums/v332/betamax/ScreenShot2014-05-03at82608PM_zps26f023c7.jpg) (http://smg.photobucket.com/user/betamax/media/ScreenShot2014-05-03at82608PM_zps26f023c7.jpg.html)
(http://img.photobucket.com/albums/v332/betamax/ScreenShot2014-05-03at82559PM_zps47b9dcbb.jpg) (http://smg.photobucket.com/user/betamax/media/ScreenShot2014-05-03at82559PM_zps47b9dcbb.jpg.html)
(http://img.photobucket.com/albums/v332/betamax/ScreenShot2014-05-03at82138PM_zps4891e831.jpg) (http://smg.photobucket.com/user/betamax/media/ScreenShot2014-05-03at82138PM_zps4891e831.jpg.html)
(http://img.photobucket.com/albums/v332/betamax/ScreenShot2014-05-03at82120PM_zpsbec96eda.jpg) (http://smg.photobucket.com/user/betamax/media/ScreenShot2014-05-03at82120PM_zpsbec96eda.jpg.html)
Can you try using mlv instead of raw?
Yeah I could give it a try! I haven't yet because I haven't found an easy way to process .mlv files though, and I'm on a Mac... What do you recommend?
Can you upload the DNG files?
Raw is raw, whether it's .RAW or .MLV (the image content is the same).
Quote from: a1ex on May 04, 2014, 10:54:39 PM
Can you upload the DNG files?
Raw is raw, whether it's .RAW or .MLV (the image content is the same).
Now that you mentioned that a1ex, I checked the .dngs with Photoshop Camera Raw and they all seem to be fine...
Still, there's something weird going on with Da Vinci and the .dngs then because when I export them (anamorphic desqueeze plus a simple correction node) I still get those weird frames. I think it's safe to say it's not the .raw or .dng files themselves, but the way Resolve is working with them. Thanks anyways, all. Sorry for not checking thoroughly in the first place.
My first question still stands though, if anyone has more experience using the 4:3 or 3:2 shooting modes with the 7d, what's the "sweet spot" resolution wise, using a Lexar 1000x?
I'm rather new to the ML, but I was looking for answer and did not find.
Power indication in my 7D seams to not work correctly, canon menu says for example 39% left, ML shows 100% yet yellow. It even turns red when battery is going out but still 100%? I'm pretty sure it is not how it is supposed to be. I have tested multiple batteries, and versions of Nightly Builds the issue is there. Has anybody else the same issue, not a major one but annoying and should I make a bug report?
Do you have some screenshots?
(http://ansius.lv/ml/VRAM0.png)
and it was blinking the red battery, and as well the one on top LCD and of course in the same is in [Q] menu as well.
some more screenshots with other half full battery, also tested with switching all modules off, clean ML build on formatted card, etc.
(http://ansius.lv/ml/VRAM1.png)
(http://ansius.lv/ml/VRAM2.png)
(http://ansius.lv/ml/VRAM3.png)
Hi
After deleting ML Nightly.2014Apr23.7D203 from my camera the battery consumption after 4 days was only 4%. That's normal. Camera was off all the time.
I have used 7D_203_Alpha2 more than a year and can't remember that behavior of battery consumption.
Keep on
Quote from: ansius on May 06, 2014, 12:17:17 AM
Power indication in my 7D seams to not work correctly, canon menu says for example 39% left, ML shows 100% yet yellow. It even turns red when battery is going out but still 100%?
Quote from: ansius on May 07, 2014, 01:09:20 PM
which in my case is easy because of battery grip
When you checked the battery indicator, was it with grip, without the grip, or both ways?
It did not occur to me at first to check all possibilities, but I did now. Without grip it works correctly, and it does with the grip if battery is in the left compartment, Canon can read them both, ML does only the left one, and if you have the battery in the right one - it reads the 100%, but color warning works. Somewhat I'm used to stick battery in the right side. Sorry, my bad...
Would it be possible to add the second battery indicator? or have a menu choice? There are quite many who use battery grips (especially with video and time lapses) and that would benefit us. thanks, anyway!
It requires reverse engineering (I don't know how to read the second battery indicator).
it might be a stupid question, but can I help? I do have some understanding of assambler (atmel's, but I can learn) and some spare time, I have done some research in IDA, but haven't done that for like 7 years. Thanks anyway
Maybe you can start here,
http://www.magiclantern.fm/forum/index.php?topic=991.0
and
http://www.magiclantern.fm/forum/index.php?board=25.0
For sure that the dev's will help you.
Hey guys.. Even I'm facing issue with battery drain.. I was on 26Apr build. 1st i thought issue with grip, now it seems that issue with firmware. Any fixes now?
anyone else getting random stops in recording RAW w/o a warning as to why? Ive had that and a few w a dropped frame warning at the size 1728x size with a lexar 1000x.
Can anyone recommend a generally semi stable build with RAW? Recent tests of all the nightlies are showing either tearing, which Ive reported and the above. Many thanks!
Quote from: ansius on May 07, 2014, 01:41:59 PM
it might be a stupid question, but can I help? I do have some understanding of assambler (atmel's, but I can learn) and some spare time, I have done some research in IDA, but haven't done that for like 7 years. Thanks anyway
See the battery.c in the src folder (https://bitbucket.org/hudson/magic-lantern/src)
Check the PROP_BATTERY_REPORT (0x8003001D) property values in your camera when the grip is attached.
Edit battery.c or share your experiences here.
Reporting a bug with the latest nightly version of ML (and TL, but that makes no difference...just noticed it was in both).
WHen recording (I happen to be using raw, but seems to be universal issue), with expo override enabled, I begin with the ability to use my wheel to adjust my aperture but sometime throughout the recording, the wheel loses the ability to control the aperture. The GUI displays a change in f-stop but there is no physical change in the aperture until I stop recording, cycle the camera, or cycle expo override on\off . ANyone else? If so, what should I report officially so its useful info to debug?
Before one percent separated between magic lantern and tragic lantern, I had his firmware. I was able to record 1280 at 60 fps for 2000 to 4000 frames without skipping. I installed new night firmware (5/7/14) and could not record at the same setting as I did. It will record only 10 to 20 frames. I tried to change some setting to improve performance, but it did not. Is there a way to change an option to increase performance? or turn off "safe"?
Has anyone been able to avoid the half pink frames? I'm using a Lexar 1000x 32Gb, with various builds and seem to be getting them quite randomly. I'm trying various 4:3 and 3:2 resolutions and to no different effect.
Quote from: tehellet on May 19, 2014, 07:36:07 AM
Has anyone been able to avoid the half pink frames? I'm using a Lexar 1000x 32Gb, with various builds and seem to be getting them quite randomly. I'm trying various 4:3 and 3:2 resolutions and to no different effect.
try the branch nobody is allowed to speak off ;)
Sorry .... Just the Noob question... :-\
1. Is this the major thread here for 7D? developments, testing and happenings around 7D ML builds?
2. is the TL still a separate development or is it already merged with ML?
All i want to know, where are we now and a summary of ML features.
My 7D currently loaded with 18 Apr ML build.
Thanks in advance guys.
Quote from: bumkicho on April 23, 2014, 09:37:24 PM
"Failed to create file. Card full?" What does this message mean? Today I wanted to see how long it would continuously record to 128gb CF card since I never shoot continuously longer than 4-5 minutes at a time and I was curious. After first 10 minutes or so, it stopped recording with this message so I turned it off and back on to try again and it stopped after around 10 minutes with the exact same message. Does anyone know what it is?
I have this same problem when recording with mlv raw with sound enabled with a Lexar 64gb 1000x card. The recording stops at 10 minutes with the above error: "Failed to create file. Card full?"
Any ideas as to what could be causing this error? I can fill up the card which is about 15 minutes of recording when using standard raw.rec mode, but I would love to have sound which is only possible with mlv.
Thanks
Hello people,
I do not understand the world anymore:
1 I go to the NightlyBuilds
2.I go to 7D 2:03
3 I read the changelogs
4 I read various improvement in FPS
5 I invite the Nightly at the camera
6 I have no FPS override on my 7D >:( >:( >:( >:(
Can you enlighten me?
Today I updated the pending pull request I pushed some time ago with fps override in RAW recording. This code is ported from TL and there are parts I don't fully understand, but now it is working for me. For example I was able to record in 5x crop mode in 25fps continuously in 1728x972 when the default 29.97fps isn't continuous.
I hope this could be soon integrated in the main branch.
The fps addition would be a godsend.
Quote from: vyskocil on May 24, 2014, 07:46:40 PM
Today I updated the pending pull request I pushed some time ago with fps override in RAW recording. This code is ported from TL and there are parts I don't fully understand, but now it is working for me. For example I was able to record in 5x crop mode in 25fps continuously in 1728x972 when the default 29.97fps isn't continuous.
I hope this could be soon integrated in the main branch.
Thanks for the update and not give up =D
Observation:
The sound cannot be muted completely on playback on current nightly. This was happening before but was fixed as I recall; can this be pulled from the other branch?
Thanks.
Hey guys,
I just got my 7D this morning! Very happy with it, if anyone in the states is looking for a good deal on a used body, try adorama, their cust. service is great, and they are very conservative with the way they rate their used gear, so if you buy something in fair condition, chances are it's actually in VERY GOOD condition!
I know the layout will be slightly different than my 50D or T3i, but there seems to be something missing completely which I didn't see mentioned before. On my other cameras, I can set ML iso to a negative value for less noise. I cannot find this option in the ML menu on 7D, is this not available?
Also, I have read a lot about fps override not working, but I'm able to select 24p from canon menu and it displays as such in MLRaw module as well. I used to have to used FPS override on 50D to get 24p, (or 23.976) I guess I don't need it here since 7D natively supports 24p?
Quote from: dpjpandone on May 28, 2014, 04:07:25 PM
Also, I have read a lot about fps override not working, but I'm able to select 24p from canon menu and it displays as such in MLRaw module as well. I used to have to used FPS override on 50D to get 24p, (or 23.976) I guess I don't need it here since 7D natively supports 24p?
fps override is not yet implemented on the current ML for 7D.
OK, fortunately it seems that I don't require it since I rarely shoot anything other than 23.97 or 29.97 - I do look forward to experimenting with overcranking for slow-motion when it is implemented. If I set the canon digital iso to a negative value in iso menu, is this the same as ml iso in 50D an 600D ?
Lastly, it seems that the iso display on the back lcd is always fluctuating (as if set to automatic) but the exposure does not change, (which is a good thing) is this the expected behavior? or is the iso display buggy? I've seen the top window iso read incorrect on other models, but the back was always the one I trusted.
Should I report this?
Quote from: dpjpandone on May 28, 2014, 06:07:12 PM
it seems that the iso display on the back lcd is always fluctuating
I guess this was because I had it on Creative 3 instead of manual. ISO display functions as expected when dial is set to "M"
Thanks for this forum and for all the outstanding work done by the Magic Lantern crew. I've been considering buying a monitor to help me see well enough to pull a good focus. I would like to make sure that when recording raw video the hdmi output is functional with the 7D? I'm sure it's been discussed but I can't sort it out enough to be sure so I apologize in advance. ST
Quote from: Rainmanwalking on May 29, 2014, 03:44:56 AM
Thanks for this forum and for all the outstanding work done by the Magic Lantern crew. I've been considering buying a monitor to help me see well enough to pull a good focus. I would like to make sure that when recording raw video the hdmi output is functional with the 7D? I'm sure it's been discussed but I can't sort it out enough to be sure so I apologize in advance. ST
even without ML the 7D maintains HD resolution via hdmi during record. Note that unlike the 5d3, when you plug an hdmi monitor on the 7d the camera lcd is off, so you only view via hdmi.
Thank you Ted.
Quote from: dpjpandone on May 28, 2014, 04:07:25 PM
On my other cameras, I can set ML iso to a negative value for less noise. I cannot find this option in the ML menu on 7D, is this not available?
I found the answer. It seems that digic digital ISO is not implemented on 7D. I am guessing this is because the setting is controlled by a register that is different from all the other eos cameras. I have been reading the thread about "brute force" searching for registers. If I can find it, will it be easy for an experience dev to implement? Or has it already been found and for some other reason not implemented?
On 7D, for these things you also need to setup the master processor. It's not a matter of brute force searching, but a matter of understanding the low-level Canon code (how it does things and where to patch it).
If you simply enable the code that works in all other cameras, you will alter only the preview image, not the recorded one. This trouble is only on 7D, because of the dual processor.
Thank You for explaining this to me. I had a feeling that if it was that simple it would have been done already.
Quote from: Rainmanwalking on May 29, 2014, 03:44:56 AM
I would like to make sure that when recording raw video the hdmi output is functional with the 7D?
My experimentation with that setup has been NO, it will NOT work RAW + HDMI output. There will be significant tearing of the recorded image. That said, I've been pretty aggressive with the frame sizes I'm working with, so it may be that it works at lower resolutions than what I'm trying to do. But at anything approaching 1080 it does NOT work with HDMI output. Unplug the monitor and you're fine. (Which for me, as I suspect it is for you, is a deal-breaker, sadly.)
I'm still trying to understand how to "bang on the code" to try and fix this, but alas it seems out of my skill range for now.
Btw, the nightly build for the 7D 2.0.3 has failed for 3 consecutive builds, does anyone know what's up with that?
http://www.magiclantern.fm/forum/index.php?topic=3072.msg117299#msg117299
I've added the missing stubs and made a PR.
Next time if something is missing please send an email or PM to me.
Quote from: Pelican on June 01, 2014, 01:20:36 PM
I've added the missing stubs and made a PR.
Next time if something is missing please send an email or PM to me.
Hallo iam sorry for my english, i am senior from czech republic ;-) Please help me, where is stabil ML for 7D 2.0.3. download? I did not find, only nightly and not kompletly (dual iso...). Please send me on my email
[email protected] Thank you!
There is no stable, only nighties and Dual ISO module is included there. To find out what is covered or not, refer to
http://builds.magiclantern.fm/#/features
Ciao
Walter
I'm currently trying to jump into ML and having a problem just getting the firmware onto my camera.
- I have updated the 7d to the correct Canon firmware.
- I have followed the steps here: http://www.magiclantern.fm/forum/index.php?topic=9848.0 (and tried a few different nightly builds)
My camera allows me to select the option for loading a new firmware, the firmware update screen flashes for a moment and then I just get black. Top screen still works and responds to inputs but the rest of the camera is unresponsive. I have to remove the battery to get it back to normal - once I do the camera functions fine on the standard Canon firmware.
I have never had ML on this camera. I have spent the last couple days reading what I can here but the information is so scattered around I guess I must have missed something. Anyone have any advice? And once this is installed, will I be able to record raw or do I have to install some other module separately?
You installed Canon's firmware 2.0.3: Link found in step 2?
If not: Redo
Format card in cardreader, insert into cam, format here again, reinsert into cardreader again, copy expanded nightly contents there (AUTOEXEC.BIN, ML directory, FIR-file) and reinsert into cam and run firmware update.
If it doesn't work, reset cam to factory defaults including Fn settings, switch to M, redo firmware update with ML's FIR file.
Quote from: Walter Schulz on June 03, 2014, 06:39:43 PM
You installed Canon's firmware 2.0.3: Link found in step 2?
If not: Redo
Format card in cardreader, insert into cam, format here again, reinsert into cardreader again, copy expanded nightly contents there (AUTOEXEC.BIN, ML directory, FIR-file) and reinsert into cam and run firmware update.
If it doesn't work, reset cam to factory defaults including Fn settings, switch to M, redo firmware update with ML's FIR file.
Thank you Walter. Once I formatted the CF card on my computer (and not a quick format) it worked just fine.
Quote from: ted ramasola on March 21, 2014, 07:09:28 AM
Testing Mar 18 Nightly.
At 1728x 972 I notice the image would tear when there is HDMI monitor attached. With no HDMI attached the image is ok.
Link to a sample frame with tearing.
https://scontent-a-dfw.xx.fbcdn.net/hphotos-prn1/t31.0-8/1115948_454560808008042_1036050560_o.jpg
Have these issues been resolved?
Quote from: Rainmanwalking on June 03, 2014, 08:30:13 PM
Have these issues been resolved?
No: in RAW still exists.
Quote from: Pelican on December 20, 2013, 02:57:02 PM
Thank you!
Installation:
1) Format the card from the camera.
2) Make sure you are running Canon firmware 2.0.3 (http://pel.hu/down/eos7d-v203-win.zip).
3) Copy ML files on the card and run Firmware Update.
Uninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.
(http://a1ex.magiclantern.fm/bleeding-edge/new-installer.png)
Hallo iam sorry for my english, i am senior from czech republic ;-) Please help me, where is stabil ML for 7D 2.0.3. download??? I did not find, only nightly and it is not kompletly (dual iso...). Thank you! pemu
I tried re-installing and the same: dual iso - will load (?)
Quote from: Walter Schulz on June 03, 2014, 06:20:04 PM
There is no stable, only nighties and Dual ISO module is included there. To find out what is covered or not, refer to
http://builds.magiclantern.fm/#/features
Ciao
Walter
Ted, On your website you say that it's possible to record at 3X Crop mode
up to 2048 x 930 at 23.976fps. Your video "Textures of Winter" which is superb was recorded in that format as well. I don't have that option, I can only record at 29.99 fps. I'm using the June 1 nightly on my new Lexar 32gb 1066x card. What am I missing?
Rainmanwalking,
It was done using features only found in TL which is not yet ported back into ML nightlies.
vyskocil, already submitted a pull request as stated here;
http://www.magiclantern.fm/forum/index.php?topic=9848.msg116516#msg116516
hopefully it will be reviewed and ported into ML soon.
I see..... I can shoot at 1920x872 30fps continuous and it looks great. Would just rather save the frames and shoot at 24fps. I'll try to get some video posted soon. I'm converting using raw2dng opening in Lightroom Making adjustment as needed and than exporting to tiff's and pulling into Vegas. I'm than using Magic Lantern to color grade. Any suggestions?
Hi, I am new to the forum. I am a 600D user. I want to upgrade to 7D only for ML RAW. Since 5D Mark iii is too expensive I have the only choice of 7D. Can anyone say at what maximum resolution 7D can shoot continuous RAW with a LEXAR 1000X CF?
Yes, would be nice if someone have the time to review the pull request. Hope soon we can have FPS override in the 7D =))
Quote from: onlypapai on June 04, 2014, 05:44:40 PM
Hi, I am new to the forum. I am a 600D user. I want to upgrade to 7D only for ML RAW. Since 5D Mark iii is too expensive I have the only choice of 7D. Can anyone say at what maximum resolution 7D can shoot continuous RAW with a LEXAR 1000X CF?
I would start at 1920x872 in crop mode. In standard mode I was shooting at 1600x900 with similar card with no problems. You might get a step better than that.
Quote from: onlypapai on June 04, 2014, 05:44:40 PM
Hi, I am new to the forum. I am a 600D user. I want to upgrade to 7D only for ML RAW. Since 5D Mark iii is too expensive I have the only choice of 7D. Can anyone say at what maximum resolution 7D can shoot continuous RAW with a LEXAR 1000X CF?
Maybe you would want to wait for 7D mark II. Many developers don't like to work on 7D.
Check this chart:
http://www.magiclantern.fm/forum/index.php?topic=6215.0
Thank you all for your replies.
The 50D does close to 1600 x 900 and it upscales really well. The 7D does a bit higher resolution but it doesn't seem as stable, although I've been debating getting one if the resolution makes any noticeable difference in quality.
The 7D has "5x" (about 3x) crop mode which is essentially free of aliasing artifacts and can reach fullHD resolution and above (not necessarily continuously...), I don't know if 50D also has this feature ?
vyskocil, any update regarding your pull request and FPS override implementation?
Yes I updated the code yesterday and asked for a review. I hope it'll be ok this time. O
Quote from: vyskocil on June 06, 2014, 09:51:36 PM
Yes I updated the code yesterday and asked for a review. I hope it'll be ok this time. O
That is good to know. Thank you for your contribution!
Hi, I upgraded to the latest 7d nightly (Nightly.2014Jun09.7D203). When running burn in test, I got the following errors:
ASSERT: IsSuiteSignature( hSuite )
at PackMemory\PackMem.c:976, task run_test
lv:1 mode:2
ASSERT: IsChunkSignature( hPos )
at PackMemory\PackMem.c:1001, task run_test
lv:0 mode:2
Any need to worry about that? I don't want to brick my Cam. :)
What burn-in test did you run, and starting from what mode (on the mode dial)?
Hello
Well i'm finally on my way to get a second hand 7D and the guy i'm getting it from is another city which i'm traveling into 2 days from now
and i'll stay there for 2 days which means i don't really have much time.
I have two questions:
-Beside general tips for buying second hand camera body is there anything that i should be concerned about ML working properly?
like the firmware version? i heard it's not possible to downgrade.
-When i got the camera what do you guys suggest i install to get good amount of features while preventing the camera from having problems (Nightly builds , the one in website , etc)
other than a nature problem of 7d working with ML like a problem that only 7D has with it , is there?
If someone has more information i would really appreciate it.
Quote from: Danialdaneshmand on June 09, 2014, 01:24:25 PMi heard it's not possible to downgrade.
Nope, downgrade is possible
Quote from: Danialdaneshmand on June 09, 2014, 01:24:25 PM-When i got the camera what do you guys suggest i install to get good amount of features while preventing the camera from having problems (Nightly builds , the one in website , etc)
other than a nature problem of 7d working with ML like a problem that only 7D has with it , is there?
Either you want to use ML (for whatever reason) or you dont want to use ML. If you run into bugs: Please fill out a bug report. The only way to get better code is to try and test the one at hand.
Ciao
Walter
Really tempted to try ML but cannot afford to brick my camera until they release the successor.
It seems like the build has come really far, how often do people report permanent damage to the cam?
Quote from: eskapeproduction on June 11, 2014, 04:08:28 AM
Really tempted to try ML but cannot afford to brick my camera until they release the successor.
Bad for you. We all are millionaires and brick a 7D on every other day.
Hello
I'm new here but hope this is the good place to ask.
I wanted to try ML with my 7D so I've dowloaded the lastest version of the nightybuild. But I can't copy the ML files into my CF card. Each time i'm trying to do this, it's a crash : "The Finder can't complete the operation because some data can't be read or written.(Error code -36)"
I'm quite sure to follow the installation guide
The firmware of my 7D is 2,0,5 (and not 2,0,3)... does that matter ?
Thanks for your help
You have to downgrade cam firmware to 2.0.3.
Every ML version dedicated to a cam (aka: not unified) has a suffix showing the cam's proper firmware version.
If you google for
finder error 36
you will find the solution to your cf-card problem.
It's quite a common one ...
Thanks Walter
I'll downgrade the firmware... as soon as I fix the error36
It's a common one, sure of that, but the usual solution (terminal > "dot_clean ") is not working
Still searching
Regarding buying a 7D (and assuming you haven't bought it yet), here's an excellent article about buying 2nd hand:
http://www.dpreview.com/articles/4701677448/how-to-inspect-a-used-canon-eos-7d
He even specifies which firmware versions you're looking for.
There in nothing specific you need to look for regarding Magic Lantern. If the 7D passes all your other tests then it will be ok for Magic Lantern (you might need to fiddle with the firmware, but that's all).
Enjoy!
Robert
What would it take to get ML working with 2.0.5?
I already have a 7D
I've downgraded the firmware to 2.0.3
But I can't copy ML files into my CF Card... Error -36... I've tried many ways (dot_clean etc...) but still doesn't work
So I'm stuck...
Thanks for helping
You were able to copy the firmware file to your CF card but unable to copy ML contents?
No, I couldn't copy the firmwarre.
I changed it with Eos Utility...
Weird...
Suggestion: Try a different cardreader or update your cardreader firmware. Solved error -36 for some people.
Thank you.
I'm afraid there's no driver for that reader...
I'll try an other one...
that's a little boring...
I'm not talking about a driver. I'm talking about uploading the newest firmware to your cardreader. Yes, a cardreader has something like that. Don't know if there is an update for your cardreader, though.
I didn't know about firmware... Can't find that for my card reader...
Thanks
Quote from: ted ramasola on June 06, 2014, 09:46:07 PM
vyskocil, any update regarding your pull request and FPS override implementation?
Quote from: vyskocil on June 06, 2014, 09:51:36 PM
Yes I updated the code yesterday and asked for a review. I hope it'll be ok this time.
Sort of. I had to do some significant cleanup (that's why it took a bit longer), but now it passes my sanity tests (there was a memory leak) and it also passes the menu usability guidelines (http://www.magiclantern.fm/forum/index.php?topic=10422).
You may try it in the current nightly.
Quote from: a1ex on June 16, 2014, 10:14:20 AMbut now it passes my sanity tests
FPS is coming home, FPS is coming home ...
Thanks so much everyone. FPS override, will test as soon as it's up.
Thanks A1ex and Vyskocil 8)
Thanks very much for bringing this to main!
I have a question, on the T3i I was able to overcrank from 24 to 36 fps and it maintained full quality.
It seems that on 7D, I must set canon video mode to 720 60p and undercrank to 36, I have set my resolution to 1728 wide at 2.35 aspect ratio. Will I get the same quality as when canon mode is set to 1080p ? Or is there more line-skipping/aliasing/loss of quality happening (regardless of resolution set in MLV RAW menu mode) because of 720p 60p mode?
Hi,
I have just installed ML latest nightly on 7D with 2.0.3.
Would like to do timelaps, but can not find menu item 'Bulb/Focus Ramping'
in shoot section.
Any idea why it is not available?
Thanks
http://www.magiclantern.fm/forum/index.php?topic=5705.0
Hi Walter,
is your link reffering to my question, as it is about timelaps?
There is also no ETTR menu item in EXPO settings on my 7D with latest nightly.
Thanks
okay, found the modul... ;-)
Quote from: a1ex on June 16, 2014, 10:14:20 AM
Sort of. I had to do some significant cleanup (that's why it took a bit longer), but now it passes my sanity tests (there was a memory leak) and it also passes the menu usability guidelines (http://www.magiclantern.fm/forum/index.php?topic=10422).
You may try it in the current nightly.
Thanks a1ex for the cleanup and the merge ! Hopefully we now do have FPS override in the main !
Hello again
I Have the 7D now , Yeepe :D and it's running on 2.0.3 firmware.
Considering i want these features
-FPS Override
-Motion Detect
-Rack Focus
-Trap Focus
-5x Crop mode Video
-Dual ISO
What should i install?and i'm not sure if the first post of this topic is updated
"Last Edit: March 18, 2014, 11:36:15 PM by a1ex"
Two conclusions possible:
No, it is not up to date.
Yes, it is up to date.
Now read the last word in the quotet section ... ;-)
Quote from: Walter Schulz on June 17, 2014, 02:13:56 PM
"Last Edit: March 18, 2014, 11:36:15 PM by a1ex"
Two conclusions possible:
No, it is not up to date.
Yes, it is up to date.
Now read the last word in the quotet section ... ;-)
Well for one thing i could not find the download link
Quote from: Danialdaneshmand on June 17, 2014, 10:20:55 PM
Well for one thing i could not find the download link
top right corner. then browse nightly builds.
much awaited
Quote from: ted ramasola on June 17, 2014, 10:25:28 PM
top right corner. then browse nightly builds.
I'm looking for the Alpha 2 actually (does it count as a nightly build?)
and i'm still a bit concerned about the whole thing
should i try the nightly builds tragic lantern or alpha?
any suggestion?
another problem i'm having is in this page : https://builds.magiclantern.fm/#/
i can't choose sth , nothing happens after clicking on it , i tested on different browsers , same problem.
http://builds.magiclantern.fm/#/
https://builds.magiclantern.fm/jenkins/job/7D.203/
the links work on chrome and firefox.
Quote from: Walter Schulz on June 18, 2014, 08:29:57 AM
https://builds.magiclantern.fm/jenkins/job/7D.203/
Ok thanks now it's working , i see the fps override is finally here , anyone tested it?
also i wanted to know can nightly builds be removed in case i want to go back working with camera normally?
http://www.magiclantern.fm/forum/index.php?topic=9848.msg92351#msg92351
I compiled the latest code for 7D and did some tests with it connected in HDMI to my TV set to emulate the setup with a small external LCD screen and it worked very well in the menus, the live view and MLV recording but in MLV playback I noticed some problems as shown in the picture below : the playback is off centered (shifted to the left) and there is garbage below and above the image :
(http://img.tapatalk.com/d/14/06/18/4uguty5y.jpg)
In my experience with previous builds, the garbage on top and bottom of image during playback is actually outside of the crop area and is actually not there in the extracted dngs and when viewed in resolve timeline.
Is this the same case?
I recommend adding image buffer support to QEMU (http://www.magiclantern.fm/forum/index.php?topic=2864.msg117430#msg117430) (maybe by loading image data from a DNG sequence) and using it to emulate the framing in various monitor configurations. Should be much easier than plugging the monitor cable back and forth, and it could also be used for automated tests on the nightly builds server, for example.
I want to work on this also. I would like to fix some of the hdmi issues, I have an inexpensive hdmi coupler I will use for plugging/unplugging to reduce wear on my monitor and camera while I test, but emulating different monitor configurations from QEMU is a better idea!
Cool, got a proof of concept somewhat working: https://bitbucket.org/hudson/magic-lantern/commits/f70d49ad4702
(the emulator can resize its window according to display type, and ML menu can recognize the display mode changes and scale the menu fonts)
Just tried FPS Override... i extracted the MLV file and frames doesnt hold the data.. all i received is vertical lines in those DNG files.
https://drive.google.com/file/d/0B3HtquGOmHVmRG1xTVlsTEkteTQ/edit?usp=sharing
Anyone else tested??
Quote from: BushanBengaluru on June 19, 2014, 03:23:17 PM
Just tried FPS Override... i extracted the MLV file and frames doesnt hold the data.. all i received is vertical lines in those DNG files.
https://drive.google.com/file/d/0B3HtquGOmHVmRG1xTVlsTEkteTQ/edit?usp=sharing
Anyone else tested??
Works fine for me (at 23.976).
Quote from: BushanBengaluru on June 19, 2014, 03:23:17 PM
Just tried FPS Override... i extracted the MLV file and frames doesnt hold the data.. all i received is vertical lines in those DNG files.
https://drive.google.com/file/d/0B3HtquGOmHVmRG1xTVlsTEkteTQ/edit?usp=sharing
Anyone else tested??
Never mind, I tried another test and found it works. I think I screwed some setting last night.
Finally got my hands on the Magical lantern last night (last nightly build)
One word , Wonderful.
a big thank to whoever worked on this project it's absolutely brilliant.
Anyway , one of the things that got me into buying a 7D for magic lantern was the "Audio trigger shutter" , i couldn't find it in menus or subs and modules.
Is this feature missing for 7D or its name has changed?
Quote from: blackjack102 on June 20, 2014, 05:23:04 AM
Never mind, I tried another test and found it works. I think I screwed some setting last night.
sorry guys, Yes it worked for mine too.. just tried with 1frame per 24fps.. worked well..
will try for slower fps soon..
thank you
Quote from: Danialdaneshmand on June 20, 2014, 03:42:21 PM
Finally got my hands on the Magical lantern last night (last nightly build)
One word , Wonderful.
a big thank to whoever worked on this project it's absolutely brilliant.
Anyway , one of the things that got me into buying a 7D for magic lantern was the "Audio trigger shutter" , i couldn't find it in menus or subs and modules.
Is this feature missing for 7D or its name has changed?
FEATURE_AUDIO_REMOTE_SHOT seems to defined only for 650 & 700 build...
I just defined it in 7D features.h, compile it and give it a try : seems to works very well !
I don't know why this is not included by default ?
[Update] in fact this feature depends on CONFIG_AUDIO_CONTROLS and this had been disabled recently for 7D because some features were untested/or perhaps not working (?)
I don't understand (in all_features.h) :
#ifdef CONFIG_AUDIO_CONTROLS
#define FEATURE_AUDIO_REMOTE_SHOT /* requires audio controls, otherwise there's no sound in photo mode */
#endif
It doesn't really depend on CONFIG_AUDIO_CONTROLS, but it's enabled by default if you have ML audio controls (because ML implementation simply keeps the sound chip on all the time, while Canon's implementation turns it off in photo mode, for example).
Without audio controls, ML has to use some tricks to enable audio. These tricks were implemented for 7D, 6D, 650D and 700D, so these cameras should have CONFIG_AUDIO_CONTROLS in features.h. It's not defined because I didnt't notice it's missing.
edit: enabled and did a small cleanup; can you try? (can't test it right now, but looks OK)
Quote from: a1ex on June 20, 2014, 11:05:16 PM
It doesn't really depend on CONFIG_AUDIO_CONTROLS, but it's enabled by default if you have ML audio controls (because ML implementation simply keeps the sound chip on all the time, while Canon's implementation turns it off in photo mode, for example).
Without audio controls, ML has to use some tricks to enable audio. These tricks were implemented for 7D, 6D, 650D and 700D, so these cameras should have CONFIG_AUDIO_CONTROLS in features.h. It's not defined because I didnt't notice it's missing.
edit: enabled and did a small cleanup; can you try? (can't test it right now, but looks OK)
I quickly tried it and it seems to works ok.
But at the end why CONFIG_AUDIO_CONTROLS had been disabled on the 7D ?
It seems also all right when I enable it on my 7D...
Do you get audio menus up and running? I don't remember seeing them, but will double-check.
Quote from: a1ex on June 21, 2014, 12:23:37 AM
Do you get audio menus up and running? I don't remember seeing them, but will double-check.
Yes and live audio meters even when not recording (very useful :)
Alex, Thanks for all the recent work on the 7d. It's really added a lot to my old camera. :)
I don't get it is there an Audio Trigger option somewhere in number 140 nightly then?
Hello , I just upgraded from a t3i to a 7D , I had ML on my t3i and liked some of the features, I read that the 7D doesn't have a stable version , can someone please tell me if it would be safe for me to install the nightly build version? , or is a stable version for the 7d in the way? , I literally had to borrow money to buy this camera, so I can't really afford to break it ..
Where would I get the latest version of the software?,In case I decide to test it out.
I appreciate everyone's time thank you :)
have been using ML on 7D for some time, I had to restart it by force once in a while, but if you do use the basic features most of them work without hiccup, raw is not that stable, and I've had some problems with ETTR / dual_iso, but have not been able to find what I have to do to repeat the problem (either ETTR strops adjusting or dual_iso is not triggered). Fut for most, really, it's fine
Thank you for sharing your own experiences !
So I should just download the last nightly build version from the website?
Thanks again .
Quote from: vyskocil on June 21, 2014, 12:26:25 AM
Yes and live audio meters even when not recording (very useful :)
This is VERY useful indeed! It's a pain to not be able to monitor audio in standby, since this is when you would want to trim your levels! Thank you again for helping to get 7D current Vyskocil!
Speaking of audio meters I'm having the same issue , is there a way to have them when not recording?
Anyone tested the Audio remote shot yet , I don't if i should get the nightly #149 or #145 if tested?
Quote from: Danialdaneshmand on June 25, 2014, 08:29:37 PM
Speaking of audio meters I'm having the same issue , is there a way to have them when not recording?
Anyone tested the Audio remote shot yet , I don't if i should get the nightly #149 or #145 if tested?
You talking in RAW mode or in normal video mode (h.264) ? In raw mode you need to enable the sound module.
Quote from: arrinkiiii on June 25, 2014, 08:39:34 PM
You talking in RAW mode or in normal video mode (h.264) ? In raw mode you need to enable the sound module.
Normal mode , since i'm not recording what could be different?
Do we actually know why there is tearing \ pink frames occasionally when using an HDMI monitor attached? Sorry if this has already been discussed, trying to catch up\follow along the development.
Using an external display adds overhead to the overall processing load, I get less of these artifacts when i record at a lower resolution or frame rate. Until this is investigated further, the best performance can be obtained by setting global draw to "don't allow" in the mlv menu, then using a monitor that has a cropmark feature to frame your shot accurately.
Quote from: dpjpandone on June 26, 2014, 08:53:23 PM
Using an external display adds overhead to the overall processing load, I get less of these artifacts when i record at a lower resolution or frame rate. Until this is investigated further, the best performance can be obtained by setting global draw to "don't allow" in the mlv menu, then using a monitor that has a cropmark feature to frame your shot accurately.
I'm not a monitor user but doesn't ML transfer files like you see it back in the screen itself so we can use the cropmarks internally?
Yes, the external monitor will display cropmarks (at the cost of more performance overhead, which causes tearing) this is why I suggest disabling all ML overlays and using the cropmarks on external monitor. Does that make sense?
I just got my 7d it has the firmware 2.0.5 , can I install ML , is there a tutorial anywhere ? Please help !
Downgrade to firmware 2.0.3 and follow instructions on page one of this thread.
You will find links to older firmware here (http://magiclantern.fm/forum/index.php?topic=11108.msg107864#msg107864)) and other infos, too.
Hi! Could someone please help me. I installed latest Nightly build on Canon 7d without having Magic Lantern installed on camera.
Now it gives me a bunch of errors about missing everything. Is there a way to uninstall nightly build or I should install Magic Lantern over it?
Format card using a cardreader. Insert card into cam and format again. Download latest nightly and expand contents. Copy contents to card (cardreader again). Insert card into cam, run firmware update procedure.
Quote from: walter_schulz on June 28, 2014, 04:38:53 PM
Format card using a cardreader. Insert card into cam and format again. Download latest nightly and expand contents. Copy contents to card (cardreader again). Insert card into cam, run firmware update procedure.
Thanks! Mistake was that I didn't copy the ML folder when putting files on CF card. I followed your steps and everything works fine!
Quote from: najor on June 28, 2014, 05:05:45 PM
Thanks! Mistake was that I didn't copy the ML folder when putting files on CF card. I followed your steps and everything works fine!
Funny thing is i did the exact mistake , wonder why that is.
Now I'm struggling with terrible frame skipping and can't find a way to record continuous MLV.
I have Lexar 1000x 64GB and can get only 1sec of footage at 1728 resolution, 24fps. At 1280p it records 3sec.
I tried setting to ignore frame skipping, but the footage becomes unusable because of skipping anyway. Any tips?
Global draw off. And try RAW, too.
Card benchmark looks okay or not?
Quote from: walter_schulz on June 28, 2014, 07:38:01 PM
Global draw off. And try RAW, too.
Card benchmark looks okay or not?
Hmmm.. I checked card's speeds and compared it to my Lexar 600x which works fine. Unfortunately looks like I bought fake cf card from Ebay. But at least now I know why frames are skipping ;)
Hey guys, if you set your display options to "force vga" there is no tearing in the recorded mlv. Unfortunately, we cannot use 1080i hdmi out on 7D (I don't know about other cameras, but my guess is that any digic4 camera cannot do raw capture and 1080i hdmi out simultaneously, so using the force VGA option sets the hdmi output to 480p (just like when recording h264 on 5D or 550D. This is probably the reason 7D was the first and last digic4 came that had 1080i out during recording....
I hope this helps someone, I would hate to see anyone ruin their footage like I did today!
I had ML and accidentally reformatted my ML card on the camera, it seemed to delete everything and now I'm trying to reinstall it but it won't work, I:
-clear settings
-transfer ml and firmware to card
-update firmware
-try to open ML using Info or Picture Style and it just seems to ignore all of it and act as if ML isn't there, any suggestions would be greatly appreciated,
Don
Format card using a cardreader. Then format card using your cam. Download latest nightly, extract contents, copy extracted contents to card (cardreader again). Insert card into cam, startup and run Canon's firmware update procedure. Restart cam before timeout runs off. After cam has started press trashcan button.
When recording raw on 7D, can you still use external monitor via hdmi? I mean without any negative impact on recording speed etc.
Thinking of buying an external monitor like http://www.coollcd.com/lilliput-668gl70nphy-7-on-camera-lcd-field-monitor-w-hdmi-component_p708.html
Exciting news: http://www.magiclantern.fm/forum/index.php?topic=12528.msg120665#msg120665
Quote from: Pelican on July 05, 2014, 12:29:03 AM
Exciting news: http://www.magiclantern.fm/forum/index.php?topic=12528.msg120665#msg120665
Yupie.... extra buffers. 8)
Can i ask what that's gonna do?
increase the cache so it has more space to put files into and then write them into memory card?
Quote from: Danialdaneshmand on July 07, 2014, 07:53:44 PM
Can i ask what that's gonna do?
increase the cache so it has more space to put files into and then write them into memory card?
Yup exactly. Depending on what resolution you're recording with, it could mean an extra 1-5 seconds of footage.
Hello,
Wasn't sure if I should open a new thread or not so decided to ask my questions here since it appears suited.
I have the Canon 7D
It still runs firmware 2.0.3 (which apparently is a good thing)
I have a 64gig UDMA 7 x533 CF card
I'm somewhat new(ish) to DSLRs.
I bought the camera because I'm both an enthusiastic sports / wild life photographer while at the same time I also make videos on YouTube so require both worlds.
I have recently encountered ML and... at face value it appears to be a game changer.
Granted, from my understating, Full Frame is full frame and obviously the quality of the sensor is superior on the 5D Miii but it does appear that with (or maybe not even) an anti-aliasing filter and with ML you get high quality HD video with further control.
I know absolutely NOTHING about hacked firmware.
I saw that there are no 'stable' current versions of ML for the 7D.
Is this correct?
what are the risks with using ML?
How much can I trust nightly versions or even a stable version?
I ask this because coming from the mobile phone world and having tried numerous Custom ROMs I know for a fact that many who claim to release a stable version have in fact released a version that is not even suited to be called 'snapshot' or even a 'nightly'.
I tried to understand the process of "installing" ML but I don't fully understand... you need to "update" the firmware unto ML and then when you turn off the camera it automatically restores back to Canon's 2.0.3 firmware? Or, do I physically have to keep both ML firmware and Canon's 2.0.3 firmware on the memory card (or even two different cards?) and keep installing and uninstalling each?
I ask this because having but this one camera it seems a bit of a hassle and not very time effective.
As an example, coming September my sister is getting married and as a present I thought to take photos and record the actual "marriage" event.
That means that I'll need ML for the 15 minutes (where I need high quality video) when they give their promises, etc, and then normal photographs.
I'm actually not even sure if ML is supposed to be good for stills as well as video or whether it's entirely a video designated firmware hack.
So I would really highly appreciate it if someone could explain it to me like I'm a 4 year old :-)
Many thanks.
David.
Could not grant the wish to be handled as an 4 year old child. Therefore:
Top of page -> User Guide -> F.A.Q.
Come back with any questions not answered there.
Thanks but I did actually read it.
I just don't really understand some of the technical talk and in some of the "answers" the 7D is not mentioned so I can't determine what is "true" for the 7D.
I honestly don't understand the difference between ML being an "add-on" or a replacement.
Also, in some cases it seems that ML cannot be run with a 64gig card and in others it's mentioned. It's also unclear to me whether I can load it using a smaller card and then use my 64gig card or whether having a 64gig card (as my primary card) prevents me from using it altogether.
It just seems that on every regard, in the FAQs, they mention or talk about the 5D Miii or the 600D or the 60D and never on the 7D so I can never understand what that entails about the 7D.
Replacement:
Overwriting a given firmware (equivalent to "Operating System" (Windows 7, Mac OS X, Linux ...)) with another one. Like in "Replacement".
Imagine ML as a program running on top of a given Operating System. Just like Notepad is running with Windows serving as platform. Or Photoshop, Lightroom on Windows/Mac OS. Or GIMP on Linux.
ML doesn't replace Canon's firmware.
You don't have to use a small card to initialize your cam for ML (aka: setting cam's bootflag).
Format card using a cardreader.
Insert card into cam and format again.
Insert card into cardreader
Download nightly build and extract contents
Copy extracted contents to card
Insert card into cam and run Canon's firmware update.
Follow instructions and restart *before* timeout runs off.
Quote from: C7D203 on July 08, 2014, 09:53:42 AM
... it does appear that with (or maybe not even) an anti-aliasing filter and with ML you get high quality HD video with further control.
Yes, sortof!
With ML installed the 7D can shoot H.264 and raw video in two modes - regular and crop. Regular video uses the full area of the sensor but only samples some of the pixels (called line-skipping) - this is what introduces the nasty moire/aliasing. In crop mode, the camera only uses the center portion of the sensor and samples every pixel, so the skipping problem goes away (in theory it's as good as a still photo). You cannot shoot full-HD (1920x1080) RAW in non-crop mode, it's a limit of the way the sensor is read, so if you're after 1080p footage you either have to shoot in crop mode (which creates a very narrow field of view, similar to using the "5x" zoom button in Live View), or stick with H.264. Until very recently we had no fps control for crop mode raw recording, so the data rates being sent to the card were so high it was impossible to shoot full-resolution for more than a couple of seconds. Even now, you need the fastest possible cards (1000x or above) to record at the larger sizes. You're OK with a 64G card on the 7D, but a 533x speed rating will limit what you can shoot in raw video. These days the 'workhorse' card is Komputerbay's 64GB 1000x.
Your mention of 'further control' is a little different for raw video - yes, you do get to change your white balance and push the exposure much more in post-production, and as it's basically a series of still photos the quality is far higher, but the price you pay is
needing to do that post-production; which involves extracting the footage, color grading in Resolve or Speedgrade, then rendering out a new file. Unprocessed, the raw file is flat and often has messed-up black and white values, plus it'll be a long while before you can upload an MLV file to YouTube! If you've never done grading before, that's a big leap from "copy from card and press upload". Raw video is rightly something that we're all passionate about, but some days you're just hoofing a clip of your cat onto Facebook, and plain old H.264 recording is the way to go. ML doesn't stop you from doing that.
ML's very stable in photo mode these days - occasionally you can crash the firmware by pushing some of the obscure features too far (like focus stacking with motor speeds too high) but you just pull the battery and restart. If you have a
fast card the raw video recording is also pretty stable, nobody's blown up their 7D yet, but you're at the limit of what's possible so even things like attaching an HDMI field monitor can mess up the recordings, so you need to play with it and learn what works with your methods - don't install it the day before a commercial job! Personally I think raw video is good enough for B-cam work and personal projects, I don't know of anyone who'd rely on it to A-cam a one-off event like a wedding; but then the same was true in the early days of RED.
Adding a VAF filter from Mosaic will reduce the aliasing in regular mode
only - it has no benefit in crop mode, if anything it'll make the image a bit worse. It's also designed for dedicated video shooting, you remove it to take stills as the filter wedges the mirror up, making your viewfinder useless (it's possible to shoot stills via Live View, but that's a real pain and there will be a slight blurring of the image). The filter will work for both raw and H.264 footage, indeed with the huge increase in fidelity you get from raw files, having a filter is arguably much more important. I've been using one since they launched, but if you're doing mixed-media location work you need a second body for stills. Anything that ships with a set of tweezers isn't going to be installed in a field!
ML has made a huge difference to the 7D's video performance, and while it doesn't alter still image files the focus/exposure/automation tools are a massive help to folks shooting macro, timelapse, etc. The thing to remember is you don't
have to use it even if it's installed - ML doesn't remove any of the 7D's factory features, it simply adds more.
Hi ML team
After testing ML-Nightly.2014Jul02.7D203 I have noticed that when I'm using Live view with Exposure override ON (I have couple of manual lenses) and changing time value down, the time values are incorrect in Live view, but on LCD panel on the top of camera are correct. The opposite way (time value up) is everything OK.
Can someone confirm that bug?
Best regards :)
Quote from: Mare on July 10, 2014, 01:11:47 PM
Hi ML team
After testing ML-Nightly.2014Jul02.7D203 I have noticed that when I'm using Live view with Exposure override ON (I have couple of manual lenses) and changing time value down, the time values are incorrect in Live view, but on LCD panel on the top of camera are correct. The opposite way (time value up) is everything OK.
Can someone confirm that bug?
Best regards :)
I have the same issue but with a little play , back and forth it does correctly.
I have a issue with Auto ETTR
it tends to always go for a high iso like 3200 even though i'm letting it go for lower shutter speeds.
Quote from: Danialdaneshmand on July 10, 2014, 04:55:10 PM
I have a issue with Auto ETTR
it tends to always go for a high iso like 3200 even though i'm letting it go for lower shutter speeds.
Make sure ISO is not set to Auto. Whenever it uses a high ISO, is the shutter speed it chooses already at the slowest shutter speed you set in the ettr menu? If so, there's no issue, you just need more light (or allow even slower shutter speeds) ;) If not, you should provide a lot more info, like what
exactly are the shutter speeds and ISOs it's choosing (also try different lighting conditions) and what are your
settings?
Hello.
could you tell me if it takes a minimum speed of the card to run magic lantern?
thanks :)
Literally: No, no minimum speed required.
If you want to shoot RAW video for more than a few seconds: Yes, there are issues.
Quote from: Santo on July 10, 2014, 08:46:55 PM
Hello.
could you tell me if it takes a minimum speed of the card to run magic lantern?
thanks :)
if you want to record the highest resolution that the 7D is capable of, don't bother with anything less than 1000X
Quote from: Walter Schulz on July 08, 2014, 10:31:45 AM
Replacement:
Overwriting a given firmware (equivalent to "Operating System" (Windows 7, Mac OS X, Linux ...)) with another one. Like in "Replacement".
Imagine ML as a program running on top of a given Operating System. Just like Notepad is running with Windows serving as platform. Or Photoshop, Lightroom on Windows/Mac OS. Or GIMP on Linux.
ML doesn't replace Canon's firmware.
You don't have to use a small card to initialize your cam for ML (aka: setting cam's bootflag).
Format card using a cardreader.
Insert card into cam and format again.
Insert card into cardreader
Download nightly build and extract contents
Copy extracted contents to card
Insert card into cam and run Canon's firmware update.
Follow instructions and restart *before* timeout runs off.
Thank you for explaining it to me.
BTW, can't I just change the timeout to something ridiculous and not worry about it?
Quote from: DFM on July 08, 2014, 02:53:18 PM
Yes, sortof!
With ML installed the 7D can shoot H.264 and raw video in two modes - regular and crop. Regular video uses the full area of the sensor but only samples some of the pixels (called line-skipping) - this is what introduces the nasty moire/aliasing. In crop mode, the camera only uses the center portion of the sensor and samples every pixel, so the skipping problem goes away (in theory it's as good as a still photo). You cannot shoot full-HD (1920x1080) RAW in non-crop mode, it's a limit of the way the sensor is read, so if you're after 1080p footage you either have to shoot in crop mode (which creates a very narrow field of view, similar to using the "5x" zoom button in Live View), or stick with H.264. Until very recently we had no fps control for crop mode raw recording, so the data rates being sent to the card were so high it was impossible to shoot full-resolution for more than a couple of seconds. Even now, you need the fastest possible cards (1000x or above) to record at the larger sizes. You're OK with a 64G card on the 7D, but a 533x speed rating will limit what you can shoot in raw video. These days the 'workhorse' card is Komputerbay's 64GB 1000x.
Your mention of 'further control' is a little different for raw video - yes, you do get to change your white balance and push the exposure much more in post-production, and as it's basically a series of still photos the quality is far higher, but the price you pay is needing to do that post-production; which involves extracting the footage, color grading in Resolve or Speedgrade, then rendering out a new file. Unprocessed, the raw file is flat and often has messed-up black and white values, plus it'll be a long while before you can upload an MLV file to YouTube! If you've never done grading before, that's a big leap from "copy from card and press upload". Raw video is rightly something that we're all passionate about, but some days you're just hoofing a clip of your cat onto Facebook, and plain old H.264 recording is the way to go. ML doesn't stop you from doing that.
ML's very stable in photo mode these days - occasionally you can crash the firmware by pushing some of the obscure features too far (like focus stacking with motor speeds too high) but you just pull the battery and restart. If you have a fast card the raw video recording is also pretty stable, nobody's blown up their 7D yet, but you're at the limit of what's possible so even things like attaching an HDMI field monitor can mess up the recordings, so you need to play with it and learn what works with your methods - don't install it the day before a commercial job! Personally I think raw video is good enough for B-cam work and personal projects, I don't know of anyone who'd rely on it to A-cam a one-off event like a wedding; but then the same was true in the early days of RED.
Adding a VAF filter from Mosaic will reduce the aliasing in regular mode only - it has no benefit in crop mode, if anything it'll make the image a bit worse. It's also designed for dedicated video shooting, you remove it to take stills as the filter wedges the mirror up, making your viewfinder useless (it's possible to shoot stills via Live View, but that's a real pain and there will be a slight blurring of the image). The filter will work for both raw and H.264 footage, indeed with the huge increase in fidelity you get from raw files, having a filter is arguably much more important. I've been using one since they launched, but if you're doing mixed-media location work you need a second body for stills. Anything that ships with a set of tweezers isn't going to be installed in a field!
ML has made a huge difference to the 7D's video performance, and while it doesn't alter still image files the focus/exposure/automation tools are a massive help to folks shooting macro, timelapse, etc. The thing to remember is you don't have to use it even if it's installed - ML doesn't remove any of the 7D's factory features, it simply adds more.
I won't presume to fully understand what wrote but thank you for writing it!
Honestly, though, after reading it... I'm not sure what benefits ML has for me.
It might just be that I have no experience using it and comparing it to Canon's firmware or that I don't understand the technical aspects well enough to appreciate it.
Since I've never done any post-production video editing it's all alien to me... for now.
But I must learn it either way.
I need to shoot myself for youtube videos but part of what I'll use the 7D is "an extra camera" to my brother's 5D Mii when we do serious documentary work. Will probably use the 7D for close-ups from a different angle, etc.
All that aside, in September my sister is getting married and I wanted to be proficient enough to capture the ceremony itself in video and follow up by shooting stills for the rest of the evening.
The whole thing will likely be outside, at night, in dark(er) conditions.
I was wondering if ML allows for better ISO performances because as much as I love my 7D and as much as it is a huge upgrade to my previous 20D (!!) I'm not impressed by it's high ISO shooting at all. Anything above 800 is meh at best.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
So, for the record (and I'm sorry to repeat myself)...
It is safe.
It's only an add-on.
I CAN do everything with my 64gig card (and require no additional cards).
I simply format the card, put the ML files and update the firmaware and follow up by entering ML via long pressing the SET button.
Correct?
Quote from: C7D203 on July 12, 2014, 03:52:05 PM
I simply format the card, put the ML files and update the firmaware and follow up by entering ML via long pressing the SET button.
Correct?
Press Trashcan to open ML Menu. Holding Set during startup tells it NOT to load ML and run Canon Firmware.
Quote from: Stedda on July 12, 2014, 04:08:09 PM
Press Trashcan to open ML Menu. Holding Set during startup tells it NOT to load ML and run Canon Firmware.
If I need to press the trash to load it, why do I need to press set to NOT load it? Can't I just not press anything not to load it?
Quote from: C7D203 on July 12, 2014, 05:35:17 PM
If I need to press the trash to load it, why do I need to press set to NOT load it?
Wrong. ML is loaded if SET is *not* pressed. If you need to access ML menu you have to press trashcan button.
But ML is working in the background all the time (if not bypassed by pressing SET during startup).
ML
loads each time you turn on the camera - as in the code is run, and the extra functions are all defined into memory. Pressing the DELETE button simply pops open the menu. It's ML's equivalent of pressing the MENU button (that still opens Canon's menu as it always did). To put it bluntly, the DELETE button was the only one that isn't used in record mode and is present on every camera, so it was the logical choice when ML needed its own menu button.
Quote from: C7D203 on July 12, 2014, 05:35:17 PM
If I need to press the trash to load it, why do I need to press set to NOT load it? Can't I just not press anything not to load it?
As to your other questions:
Quote
I need to shoot myself for youtube videos but part of what I'll use the 7D is "an extra camera" to my brother's 5D Mii when we do serious documentary work. Will probably use the 7D for close-ups from a different angle, etc.
If the main camera is shooting raw video, it would make sense to do the same just so the footage can be edited through the same workflow - but it's entirely down to what your brother's doing. Irrespective of what type of video is being shot, ML does offer a bunch of useful features - such as zebras and focus peaking - which are present on true video cameras but not on the 7D. They make it a lot easier to get your exposure and focus points right but don't affect the recording at all. Before ML came along, pro operators using a DSLR had to plug in an expensive field monitor that had those tools, in effect all ML has done is move them onto the LCD panel on your camera.
Quote
I was wondering if ML allows for better ISO performances because as much as I love my 7D and as much as it is a huge upgrade to my previous 20D (!!) I'm not impressed by it's high ISO shooting at all. Anything above 800 is meh at best.
ML does nothing to reduce high-iso noise or make the sensor more sensitive - it cannot make your 7D perform like an A7S, that's a hardware problem. What it can do is assist in getting the perfect exposure (via ETTR) so the noise is minimized, and help you to see what you're shooting by changing the LCD view. Fundamentally you're still using a 7D, which was designed for sports. If you're shooting black cats in a coal mine, you need another camera.
Quote from: C7D203 on July 12, 2014, 05:35:17 PM
If I need to press the trash to load it,
Read what I wrote.. pressing the Trashcan opens the ML Menu. I said nothing about it loading anything. Then I explained the only thing a long press on set does.
Is it me? Maybe start with the User Manual since you should get at least the basics down before trying anything. :o :o :o :o :o
Hello again.
I'm having a issue with Raw recording.
when i press the record button it says allocating 51mb data i think then it fails and says memory full which is not.
also couple of questions about installation:
-I wanna format my current memory which i have ML on , what's the protocol here?
-I have the Nightly #140 and i want to update to the latest one should overwrite ML files on my memory with the new nightly? does that fresh up my settings?
-Generally should ML files be copied to the DCIM folder or the memory index?
Thanks , Daniel
When you format in-camera it keeps ML and only deletes media
When you want to update ML, you:
1) pop the card into the computer
2) delete everything except native Canon stuff (DCIM and MISC). In other words, you delete: ML, autoexec.bin, and 7D_203.bin
3) Copy new nightly stuff onto card (ML, autoexec.bin, and 7D_203.bin). These sit on the root of the card, PARALLEL to DCIM and MISC- not inside either of those.
Actually, I'm not sure about 7D_203... maybe that's just necessary for creating first time booting? Not sure, I just copy it anyway because it doesn't seem to hurt anything and it's easier to just copy the whole thing then to actually have to think about what's what :P
Quote from: dmk on July 14, 2014, 07:18:10 AM
When you format in-camera it keeps ML and only deletes media
When you want to update ML, you:
1) pop the card into the computer
2) delete everything except native Canon stuff (DCIM and MISC). In other words, you delete: ML, autoexec.bin, and 7D_203.bin
3) Copy new nightly stuff onto card (ML, autoexec.bin, and 7D_203.bin). These sit on the root of the card, PARALLEL to DCIM and MISC- not inside either of those.
Actually, I'm not sure about 7D_203... maybe that's just necessary for creating first time booting? Not sure, I just copy it anyway because it doesn't seem to hurt anything and it's easier to just copy the whole thing then to actually have to think about what's what :P
Thanks man , that really helped.
I have the nightly #157 up and running now I tested the Audio remote shot works well.
the problem with Raw recording is gone and it's working perfectly fine.
The issue with Auto ETTR was a mistake i made in SNR settings after tweaking it a little it's now good.
About the recent Ram solution which in it 7D was shining how does it apply to our shooting?
should i enable something or it's a new algorithm which is running already?
With SanDisk 8GB Ultra 50 MB/s I could only shoot at 960 , 16:9 properly which is kinda sad.
the additional memory is not yet implemented in nightly builds, it's still part of a pull request, you have to set up the dev environment and compile it yourself. Don't worry about it too much, it will give you a few more seconds of recording at the higher resolutions, it's not going to give you a higher continuous res, because once it fills up you're relying on your card to keep up with the data rate. Just get a 1000x card, you won't regret it.
It's in the nightlies now, and its great. 372 MB buffer for MLV, no need to use the sJpeg setting anymore (keep it on raw through the Canon menu), indicate SRM Memory under the MLV menu, and you're in business. 13 full seconds of 23.976 fps 2496x1044 (2.39:1), which may not seem like much for a full-scale production, but would be awesome for compilation videos like car shows or promotional videos. Write speed seems to be more consistent now as well, mostly averaging 79-81 MB/s on my Lexar 1000x except when pushing it to max resolution.
Seems like buffer: 4, sound off, GD off and extra hacks: On equals out to the fastest write speed and performance, although having sound on hardly effects performance. Raw_rec gives more stable write speeds but of course doesn't have the amenities that MLV does.
Still gotta put it through the paces in normal production use but this little upgrade looks very promising.
I've been using magic Lantern for a long time on my T2i(550D) and my 7D. But I upgraded my firmware on the 7D to 2.0.5, I know that I cannot use ml now, this fixed the issue with my photos being too soft, now they are a lot sharper. Cannon still claims that fw2.0.3 had nothing to do with the autofocus (bs) and they also say that 2.0.5 has nothing to do with the AF(bs again). Either way, my question is are yinz working on a way that ml can work with fw 2.0.5 or is it possible to install both fw2.0.3 and ml on the same card to install at will? :o :-\
Thanks
I would suggest to use three cards for this. One with Canon's firmware version 2.0.3, one with 2.0.5 and a card running ML (bootable + files + directories).
The cards holding Canon's firmware may be some cheap or small capacity cards.
Quote from: fableblue2010 on July 19, 2014, 03:07:33 PM
I've been using magic Lantern for a long time on my T2i(550D) and my 7D. But I upgraded my firmware on the 7D to 2.0.5, I know that I cannot use ml now, this fixed the issue with my photos being too soft, now they are a lot sharper. Cannon still claims that fw2.0.3 had nothing to do with the autofocus (bs) and they also say that 2.0.5 has nothing to do with the AF(bs again). Either way, my question is are yinz working on a way that ml can work with fw 2.0.5 or is it possible to install both fw2.0.3 and ml on the same card to install at will? :o :-\
Thanks
I don't believe these claims, do you have proof that there is actually a difference in the image between 2.03 - 2.05?
I didn't believe either but this is just off-topic as it gets. Suppose "General Discussion" -> "General Chat" might be a better place.
First time post. Hope it is ok to report bugs here.
I am using the 2014/July/19th Nightly build for the 7D. I have turned on "Movie Restart" in the Movie tweaks section. It works fine, but manually stopping the recording by pressing the record button isnt actually stopping recording. It seems the only way to stop the camera from continously recording is to go back into the Magic Lantern menu and toggle the "Movie Restart" setting again.
The user guide states that "Movie Restart" can be over-ridden by manually stopping recording, and this is the case with ML on my EOS-M.
Hope this gets fixed.
Thanks
Hey guys, so I shoot on a 50D and a wondering how stable the 7D is - Im going to test my 50D vs my 60D for noticeable resolution differences and if I prefer the 60D I may wanna grab a 7D (based on initial tests the differences seem very minimal). But if it's not gonna be stable I may as well stay with the 50D which is pretty stable.
So yeah, how stable would you say? Is FPS override working yet? Random stops? Pink frames or weird lines? Color shifts or random errors that ruin files and make you have to do footer edits?
And lastly, does Dual ISO work for video (it doesnt on the 50D yet and this is killing me altho I can always do 10s clips on the 60D :/ )
Quote from: dpjpandone on July 19, 2014, 10:50:02 PM
I don't believe these claims, do you have proof that there is actually a difference in the image between 2.03 - 2.05?
Thanks for the help.
No proof. If there is not a thread started in the General discussion on this I will start on, maybe it is just me. ::)
Again thanks
Quote from: Danialdaneshmand on July 14, 2014, 02:00:10 PM
About the recent Ram solution which in it 7D was shining how does it apply to our shooting?
Sorry to have to ask (I tried searching), but what is the RAM solution? Seems like there have been a lot of awesome new developments in the nightlies this month, but I'm not quite following exactly what they are, except for the crucial addition of FPS override (thank goodness!!)
http://magiclantern.fm/forum/index.php?topic=12528.0
Where can I find the Magic lantern file for the 7D to download from the Mac?
Quote from: denhaan on July 21, 2014, 05:27:49 AM
Where can I find the Magic lantern file for the 7D to download from the Mac?
go here and choose your 7d
http://builds.magiclantern.fm/#/
Hello guys,
just wandering if there is a way to have monitor on HDMI output and still have the LCD showing on 7D?
Tks
Quote from: samotmanam on July 22, 2014, 12:00:11 AM
Hello guys,
just wandering if there is a way to have monitor on HDMI output and still have the LCD showing on 7D?
Tks
Not possible.
UPDATE!
I am now able to record with hdmi in 1080i mode with no tearing if set canon Q menu to 1080 30p, and use FPS override to get 23.976
can someone else test with these settings and confirm?
I upgraded my 7D firmware to v2.05 before finding out Magic Lantern will not work with this version. I understand I can downgrade to firmware version 2.03 but the problem is searches of this forum and the general internet turned up no firmware v2.03 file to downgrade with. I did find this post further up in this thread:
Downgrade to firmware 2.0.3 and follow instructions on page one of this thread.
You will find links to older firmware here and other infos, too.
But the link does not lead to the instructions nor the v2.03 firmware?
Apparently Canon does not allow you to download old firmware as searches of their site turned up nothing.
Quote from: fkloskowski on July 23, 2014, 04:20:05 AMBut the link does not lead to the instructions nor the v2.03 firmware?
http://pel.hu/getpage.php?pg=eoscard&ac=1
Download the file, expand content, copy content to a card, insert card, run Canon's firmware update.
Hello everyone,
I have been happily testing ML nightly(from 18.07.2014) - Just updated from an old old TL-version.
So far everything seems to work just fine. Thnx everyone btw for ML - its just awesome!
One problem though: I turned off my Camera last night with ~35% Battery left, only to find the Battery completely drained this morning. :o
Never had this before. I will test it again today for confirmation. Is this common? Does anyone know what could be causing this?
cheers!
Common it is but only if done wrong. Don't remove card before camera had the chance to shutdown properly.
If shutdown is done correctly but battery is draining: Please drop a line and the bug (if any) will be put down by the devs.
Further instructions after your tests.
Ciao
Walter
thx for the reply.
Strange, i didnt remove the card (only for updating ML).
And when i do, i always wait several seconds after shutdown before removing the card.
But I will test further and report back.
Quote from: Walter Schulz on July 23, 2014, 05:13:30 AM
http://pel.hu/getpage.php?pg=eoscard&ac=1
Download the file, expand content, copy content to a card, insert card, run Canon's firmware update.
Thanks Walter,
I was able to poke around the site at the URL you provided and find what I was looking for.
Has anyone tried the digital dolly feature? It doesn't seem to work. I turned on Digital Dolly, started the recording, and the joystick did not move the view. I tried this in crop mode.
Quote from: Walter Schulz on July 23, 2014, 05:13:30 AM
http://pel.hu/getpage.php?pg=eoscard&ac=1
Download the file, expand content, copy content to a card, insert card, run Canon's firmware update.
An easier to remember form: http://eoscard.pel.hu
(or http://pel.hu/eoscard)
Just wanted to report back on my battery draining issue. Had a fully charged battery inserted over night and checked this morning. No battery draining whatsoever (at least for tonight), so everything seems to be okay for now. :D Nervertheless I will be keeping an eye on it.
Another thing I noticed is, that sometimes (after some playing around with ML) the red LED keeps blinking (once every 4-5 sec). This does not happen always and I dont know whats causing this or whether its even supposed to be blinking. It stops when the camera is turned off and on again though. Anyone any ideas on this?
cheers!
Just in case , i didn't have any issue with battery either.
although the usage of it is pretty high but considering how much it calculates everything it's pretty good.
Something I always thought was strange is the LCD screen's backlight flashes for a second when I open the cf card door, even when power switch is set to off.
Not happening here ...
Hi!
Flashing LED happened to me as well but long after completion of file transfer from camera to PC
using Canon EOS Utility
ML Build: 08-MAY-2014
No errors after LED flashing, everything functions normally.
Have downloaded and installed ML build 22-JUL-2014 but can't verify if the behaviour is the same.
You guys are doing a great job with ML, really love the application.
Rgds.
>>> Ulf
Canon EOS 7D+BG-E7, EF-S 10-22, 18-200, EF 50/1.8, EF 70-300 IS USM, Speedlite 580 EX II
Previously (digital) EOS 50D, 400D
Previously (analog) Hasselblad 2000 FCW, Hasselblad SWC, Canon New F1, A1
Still trying to work my way around first installation.
I'm confused about this statement, taken from the 'install guide':
Quote"For first install, use a simple SD/SDHC/CF card (32 GB or smaller). 64GB cards and larger will not work for first install (but you can use them with ML, see below)."
But someone in this thread told me that I don't need a smaller card (since I only have a 64gig card).
Is this true?
Have they changed it so that 64gig is ok too?
Also... seeing that I have a lot of "simple" questions I was wondering if someone will be willing to help me via PM (if that even exists here) or emails?
First page of this thread contains everything you need to know about installation procedures for recent nightlies.
I don't see where it addresses my question about a 64gig card.
That's up to your logical conclusion.
If there isn't anything about card size found and I tell you all you have to know will be found there ...
what's up guys,
new to the forum, but long time reader.
I just wanted to comment on the battery drain a member above was talking about, i also had the battery drain. woke up the next morning after going to sleep knowing i had juice in my battery, and it was completely dead. I removed ML from my card, charged my battery and it is still full, (or what like 90 something % lol) after 3 days of sitting.
As I use the nightly builds I am in the habit of popping the battery out and in again if I'm not going to use the camera for a while to prevent the 'not shutting down fully, thus flattening the battery overnight' thing.
It's no big deal, I suspect certain combinations of parameters (IIRC, it tended to happen whenever I used 50p and FPS over-ride) get confused. I also recall that the indication this was happening was a lack of sensor cleaning cycle, although there are situations where this doesn't happen even if the camera does shut down completely - perhaps if it's been cleaned recently?
Anyway, the battery thing is just part of my workflow now. I suspect there are higher priorities for the devs, so after it's been reported, just don't worry about it.
As of today the devs were not able to reproduce the issue.
No user having had this problem was able to reproduce it.
Your suspection is ... well ... not that well placed ...
Hi
After almost one month testing ML night test2_7_14 I have no issue with the battery drain, but I do have once lack of sensor cleaning cycle and improper shut down (on/off switch is not working). That bug I was not able to reproduce it :).
Keep on rockin'
Hi everyone, I'm new in ML forum.
I mostly interested with raw video capabilities of 7D. The think that I'm understand 7D's raw resolution limitation is all about bandwidth of cf cards and/or 7D's CF connection that does not allow more than 80 MB/s. And this is roughly (1728 x 972 px) x (14 bit) x (24 frame/s) continuous. And this equation is about 67-70 MB/s. Well, is this mean I can record continuous with 2048 x 820 px or something like 1990 x 845 px resolution (Almost same data rate but more close to 2K DCI standard) raw video with 7D?
P.S: I'm asking because I'm going to buy fast CF card if only this works.
Quote from: Walter Schulz on July 25, 2014, 02:30:34 PM
That's up to your logical conclusion.
If there isn't anything about card size found and I tell you all you have to know will be found there ...
Honestly, I don't understand this sort of behaviour.
What purpose does it serve?
If you have some problem with my questions just don't answer them but you constantly take time out of your day to reply with answers that don't help, so what exactly is the point?
I have read the FAQs (which you told me to do on your first reply).
If the FAQs are incorrect then either change them or at least don't tell me to read them if all they do is add confusion.
The 7D is not mentioned or addressed in the FAQs. Therefore, a fairly logical step forward will be to verify whether everything that is true for the rest of the cameras is true for the 7D.
I still have no answer to that question and seeing that ML is not 100% safe it's not a baseless concern.
One person tells you that 'X' is fine while the FAQs says the opposite while someone else constantly directing you to places where while there is information it is not concrete.
I realise that for some people here who are either programmers or well informed with all things ML all my questions seem silly and they've seen them a thousand times before.
But honestly, wasting time on replies that don't help and insulting my logic seems childish, futile and a waste of time not just for me but for anyone who's going to read this thread now or in the future.
With all that said...
I'm very interested in ML but feel that I need more reassurances and more explanations and to be sure about each step.
I will still very much appreciate it if someone with experience and a pleasant demeanour will agree to help me either here – assuming I'm not going to be banned for doing nothing but asking questions, pleasantly, or via email at
[email protected]
awgthtgtta?
http://www.magiclantern.fm/forum/index.php?topic=9848.msg121701#msg121701
Quote from: Walter Schulz on July 26, 2014, 05:57:35 PM
awgthtgtta?
http://www.magiclantern.fm/forum/index.php?topic=9848.msg121701#msg121701
Ok, I missed that post. I checked raw capabilities document but I was not fully understand "no crop max resolution". I thought it was about bandwidth limitation. That answers my question. Thanks.
I'm not sure if your question is answered because the post you just answered wasn't intended as an answer to your post.
Quote from: Walter Schulz on July 26, 2014, 09:56:51 PM
I'm not sure if your question is answered because the post you just answered wasn't intended as an answer to your post.
It means that your answers are universal. ;)
Quote from: Walter Schulz on July 26, 2014, 09:56:51 PM
I'm not sure if your question is answered because the post you just answered wasn't intended as an answer to your post.
Oww :) I thought it was for me. I noticed a line;
"You cannot shoot full-HD (1920x1080) RAW in non-crop mode, it's a limit of the way the sensor is read"
Then I remember that document. And I thought 7D allowing only 1726 lines vertical and 1156 lines horizontal most. Is it wrong? I mean can I record 2048x820 px continuous 24p in no crop at least in theory? Or these are the limitations, top limits?
There are limits. As time of writing "uncropped" mode in 24p is limited to liveview's resolution.
Most recent development is "full resolution silent" mode but 24p is out of reach by far.
If you want Full-HD uncropped you may want try to upscale and decide if quality is sufficient for your needs.
I was looking at change logs and bumped into this "SRM memory: allow autofocus while allocated, but keep full shutter locked. Test on "don't click me"
i never found a useful explanation about this thing and i always taught maybe it's Voyeur Detector or something :D
Hint: go to the SRM memory thread and type "autofocus" in the search box ;)
Quote from: a1ex on July 27, 2014, 05:22:55 PM
Hint: go to the SRM memory thread and type "autofocus" in the search box ;)
I did and i tried it though i have Big picture question here
The don't click me is freeing access to take pictures while recording and you're using the SRM memory solution to get this done?
i'm just a bit confused but it's nothing new since i heard about ML a year ago :D
hey guys,
after an afternoon of more testing to find the best settings for use with hdmi monitor at 1080i, I am happy to report that there is no tearing or pink frames in the recorded image when I set region to PAL so that 1920 25p becomes available in the canon Q menu. Then use fps override method "exact" to get 23.976
This is currently the only combination of settings that allows reliable performance with hdmi monitor on ML.
Hi there,
since the last builds (28-30.07) formatting does not work in the camera.
It will delete all files except the settings-folder.
greeting
Can you record a video of the camera screen, to show the problem?
Quote from: Wartburg-Entertainment on July 30, 2014, 06:35:26 AM
since the last builds (28-30.07) formatting does not work in the camera.
It will delete all files except the settings-folder.
Hi,
same problem here with 60D - after formating, ML files are not written back to sdcard (only settings)
edit: looks like ML files are not copied before formating - sorry cant record a video
last working version is: 2014-07-25 00:15:34 +0200
Reproduced and solved.
Hi guys,
first of all, thank you so much for all the features that Magic Lantern offer,
it's a few months that I'm using it, and always I found something new :)
This time I was trying the Digital Dolly feature,
but when I enable it ML seem to slow down, and the crop on live view it's "locked",
I can't switch from 5x to 10x, or viceversa,
and also the joystick is stuck in the live view, isn't impossible for me to move it, also if it is not in crop mode.
I need to switch off the live view end turn off the Digital dolly to "enable" the zoom and the joystick again.
Anyone have found this "issue"?
Thank you so much again,
Elia
Hi all,
This is my first post so do forgive me if this is in the wrong place or suchlike......But i have an issue with the audio function settings on my 7D.
I have 2.0.3 on to which the ML version - nightly.2014jul307d203 - successfully installed, so far as i can tell.
Although, the options available to me on the audio page in ML seem somewhat lacking.
I have only these options visible:
Beep, test tones
MLV Sound
I have enabled all the audio modules as far as i can tell but no further options are readily available.
Any ideas....? Is there a later or stable version available. The link i see on ML itself are dated 2012 hence my using the nightly build.
I'm genuinely excited about the prospect of shooting RAW, but it'll only work for me if the sound works too.
Here's hoping.
Thanks
N
this is correct. To adjust your levels you have to enter the canon menu. The 7D nightlies do not have all the options for sound as the 5D or others. Since the preamps on all these cameras are garbage, most people just use internal sound for reference to sync with external recorder (myself included) so audio on the 7D works well enough for reference sound.
Hi everyone,
I installed Nightly2014Aug02.7D203 successfully and played around with it. I noticed that after removing the CF card and putting it back in, the camera won't start when setting the power button to ON. I need to remove the battery to recover from that situation. I couldn't find anything about this issue neither in the bug reports nor in this thread, hence this post.
Anyway, great thanks for the fantastic work!
Quote from: iazz on August 07, 2014, 07:52:27 AM
Hi everyone,
I installed Nightly2014Aug02.7D203 successfully and played around with it. I noticed that after removing the CF card and putting it back in, the camera won't start when setting the power button to ON. I need to remove the battery to recover from that situation. I couldn't find anything about this issue neither in the bug reports nor in this thread, hence this post.
Anyway, great thanks for the fantastic work!
Try some nightly builds from earlier dates and see when that bug started, and if it happens with all of them there may be another problem.
Quote from: brihan on July 20, 2014, 08:35:20 AM
First time post. Hope it is ok to report bugs here.
I am using the 2014/July/19th Nightly build for the 7D. I have turned on "Movie Restart" in the Movie tweaks section. It works fine, but manually stopping the recording by pressing the record button isnt actually stopping recording. It seems the only way to stop the camera from continously recording is to go back into the Magic Lantern menu and toggle the "Movie Restart" setting again.
The user guide states that "Movie Restart" can be over-ridden by manually stopping recording, and this is the case with ML on my EOS-M.
Hope this gets fixed.
Thanks
Just want to bump this bug since nobody responded when I first reported it.
I can confirm the rec bug with magiclantern-Nightly.2014Aug07.7D203.zip build, did clean ML test (I did reset all the preferences to defaults) Movie restart triggers when start / stop button is pressed
Quote from: iazz on August 07, 2014, 07:52:27 AM
Hi everyone,
I installed Nightly2014Aug02.7D203 successfully and played around with it. I noticed that after removing the CF card and putting it back in, the camera won't start when setting the power button to ON. I need to remove the battery to recover from that situation. I couldn't find anything about this issue neither in the bug reports nor in this thread, hence this post.
Anyway, great thanks for the fantastic work!
After opening the card door, always wait for LED confirmation (or for 5 seconds) before removing the card!!! During that period, Canon firmware accesses the card without turning on the LED, and if you remove the card too early, the camera will freeze and will drain the battery. Exception: 550D users don't have to wait.
http://www.magiclantern.fm/install.html
Quote from: dpjpandone on August 07, 2014, 05:43:23 AM
Hi dpjpandone,
sorry for the late reply,
do you know more about the problem I've found?
Hi,
I have a simple problem. It might sound stupid but I really would appreciate your help. I am trying to make my first MLV Raw video. I use the 2014-08-08 build.
The Start/Stop button starts the recording but I can not stop it. I press it and again and nothing happens. I quit the video mode, the CF card LED remains red forever (I have a Lexar 32Gb 1066x).
Is there another way to stop recording? I don't know where to look. I searched the forum, google, youtube ... no one seem to have this issue. There is 360.1 MB for the MLV_REC.TMP file but nothing in the video folder.
Thank you for your kind help.
Kim, what are your settings? 24 or 30 fps? Audio on or off? Does the cam freeze up or continue to record indefinitely? List your settings under the MLV menu too.
Thanks N/A for caring.
My settings:
On Canon menu video PAL 24 fps at the highest resolution.
On ML menu: Beep test on, SoundMLV audio on, Global draw on, Raw video MLV on at the resolution 1728x972, create directory is on. Everything else is off in other menus.
The screen is as if it still recording: it wrote prepare, then something about creating the MLV_REC.TMP and then it seems like recording. Only the ML menu can be toggled on/off but I can not navigate in it. No other button is responding. That is a bit scary.
I tried changing a few things in the menus. This did not improve. Letting my camera record, as some point the LCD becomes black and the camera freezes.
May be I should try an older build? May be I am doing something wrong in the Canon menu? but, I have reproduced the problem five or six times. I am afraid now this will brick my camera.
I sometimes get a CRASH00.LOG created but it is empty so I can not find the issue.
If I put the Raw video "off", everything is ok. So the RAW video is not compatible with some other settings.
Hi KIM!
Select 1280x720 in Canon menu, and test another MLV resolution. Compact Flash needs to write at 55MB/s for 1280x540, check it! Look at Tweaks on ML video menu, and deselect the infinite recording.
Hi Ocbarrio,
Thanks for your message. Unfortunately, it did not help stopping recording (or trying to record? because there is no recorded file, just an empty folder created).
I went to the ML menu, put MLV off but that did not help. When I exited the Movie mode by putting the camera in viewfinder mode, the LED became red and the top lcd was blinking "err". I got a CRASH00.LOG file with the content:
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_RESET_PSAVE_LV, NULL, 0 ) )
at LVState.c:608, task ?
lv:1 mode:2
Magic Lantern version : Nightly.2014Aug08.7D203
Mercurial changeset : 3288e152d8ae (unified) tip
Built on 2014-08-08 11:47:40 UTC by
[email protected].
Free Memory : 255K + 2554K
Do you have both RAW and MLV loaded and turned on? Or just MLV? Having them both on will cause it to crash.
Only MLV.
The problem seems to be that no file is recorded. Using the .MOV video works well.
Try another CF, even slower, make it bootable and copy files and test it. I heard some problems with some cards. And you can reset all settings from canon menu, and then begin all process.
Thanks Ocbarrio. It worked!!!!
I tried another card, and it worked for small size raw. Then, I reinstalled the files on the former card and it worked. At 1600x644 the "camera icon" is most of the time red, time to time it skips a frame. At 1728x694 the "camera icon" is always red and skips frames.
So, something was wrong with the files on the card when I installed ML.
Awesome, now get a 1000x Lexar and give 2k raw a shot ;)
This is a 1066x Lexar! I was on 50 fps. On 24 fps it starts red, yellow and then a smiling green :)
You´re welcome, Kim!
This is my first post here... :-)
I´m with ML less than a month... and I´m learning too...
So, Lexar 1066x is enough for 1600x644? My first thought was that 1066x should be enough for all sizes...
Why do you record 24fps? 50fps brings more definition on moving objects.. I always record on 720 50fps. If ML could record at 100fps...
Can you test your LEXAR to see the better size? with no skipped frames...
Hello,
First, let me thank all of the developers and coders who have contributed to this project. The features in this package are amazing.
I am a new user, with a problem that probably has a simple solution that I just haven't found. That, or I have misunderstood how ML works.
I have downloaded the nightly build for the 7D and have successfully installed ML on my camera. I am able to adjust the settings and activate modules with no problems. However, ML is only active when the boot card is in the camera. If I put any other CF card in the camera, even without restarting the camera, ML no longer functions. In fact, the firmware version displayed in the menu goes back to 2.0.3 and ML is not accessible, even though the camera has not been restarted and the "countdown" procedure to disable ML has not been carried out. When I put the boot card back in, ML is fully functional, again without any restart of the camera.
My impression from several videos and the forums was that ML would remain active when starting the camera until the disable procedure was performed. It would be odd, IMO, if you couldn't change CF cards while using ML, or if you had to have the ML files on every card you use.
Again, I suspect that I am overlooking something, or that perhaps it has been discussed by coders (which I am not) in such a way that it was over my head. Any suggestions would be appreciated. Thanks.
Quote from: pknight on August 15, 2014, 04:03:58 PM
My impression from several videos and the forums was that ML would remain active when starting the camera until the disable procedure was performed. It would be odd, IMO, if you couldn't change CF cards while using ML, or if you had to have the ML files on every card you use.
I've never once seen or heard of anyone do this.
ML installs nothing to the camera. Only sets a flag telling the camera to look on the card for a file and run it. So you'd need the card with the bootflag set and ML files on it in the camera for ML to run. I can't understand why you'd pull a card out of the camera in use without shutting it down first or any plus side to doing it. In fact that would be a bad habit to get into while using ML.
ML is working the way it was intended. If you want other cards to run ML make them bootable and copy the ML files to them.
Thanks! Like I said, I suspected that I misunderstood how it works. I was relying on one YouTube video that was apparently confusing to me.
BTW, I have been removing CF cards from Canon cameras while they are on for years (as when one fills up and is replaced by a blank one). The cameras handle this with no problem. Obviously, with ML it is a different story.
Thanks again. You have been a great help.
***Attention 7D HDMI USERS***
I am trying to fix the image tearing issue that is present when using HDMI monitor with 7D
I have made some very small changes (using different edmacs) and I am seeing a lot of improvement. Can the other 7D HDMI users please test this build and tell me your results:
http://www.filedropper.com/magiclantern-nightly2014aug157d203
Please Use all of the features you would normally and tell me if you experience any problems or instabilities that are not present in current nightly builds. The only thing that should be different is that tearing should NOT be present in the recorded raw video files. As long as these changes do not introduce any new problems I will will submit a pull request so we can have this change in the nightly builds.
Thanks!
PS. here is another build with audio controls enabled, as far as I know the only problem was with "wind filter" which is still disabled, so the rest of these should work fine, please test and report if any new instabilities are found: http://www.filedropper.com/magiclantern-nightly2014aug157d203audio
Just remember, You are using magic lantern at YOUR OWN RISK! and using builds from newbs like me presents a HIGHER RISK than usual........ but I have tested these builds on my own 7D with no problems so I'm sharing them here so they can be tested over a wider range of circumstances/use cases than my own settings.
@ ocbarrio: at 1536x618 50fps, it did not complain about skipping frames.
Quote from: ocbarrio on August 15, 2014, 03:54:31 PM
Why do you record 24fps? 50fps brings more definition on moving objects.. I always record on 720 50fps. If ML could record at 100fps...
The line skipping/aliasing in 720p mode is horrible, you have to stretch out your dng's after recording to get them back to the proper aspect ratio. Also, movies are usually shot in 24p, and many digital filmmakers want to emulate the look of film as much as possible.
@dpjpandone, I'll test out the audio controls, thanks for the builds. Could you possibly make one with full res silent pics enabled? Would like to test that also.
Quote from: N/A on August 15, 2014, 06:37:17 PM
The line skipping/aliasing in 720p mode is horrible, you have to stretch out your dng's after recording to get them back to the proper aspect ratio. Also, movies are usually shot in 24p, and many digital filmmakers want to emulate the look of film as much as possible.
@dpjpandone, I'll test out the audio controls, thanks for the builds. Could you possibly make one with full res silent pics enabled? Would like to test that also.
Thank u! I´m new user and this is my first time with RAW video.
Quote from: N/A on August 15, 2014, 06:37:17 PM
.
@dpjpandone, I'll test out the audio controls, thanks for the builds. Could you possibly make one with full res silent pics enabled? Would like to test that also.
I haven't looked at this feature yet, but I would definitely like to see it supported on 7D.
Hello everyone. I am testing the latest build of ML (Aug 08). I have been testing out the different features and was wondering if it would be possible for me to utilize MagicZoom and the Digital Dolly at the same time. When I enable the Digital Dolly I loose the ablility to use the joystick to change the position of the focus box. How can I accomplish this? Thanks for this tool, and for the help.
Could anyone confirm whether this card will work fine with ML RAW (I presume so but does anyone use one)
http://www.amazon.co.uk/dp/B00J9OS7LW/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=35UOQ14ORE0BO&coliid=IY6H88WGS9YVN&psc=1
@ dpjpandone: Thanks for the latest development! I´m using the audio-display of your latest build, it´s pretty amazing! Thank you for your work, that are great news! That´s what I wanted to have the last months ...
Now ... there is one last wish I have: Could it be made possible to send the audio levels over the USB that I can see it within DSLR-Controller from Chainfire? He told me, that the level has to be given out parallel to the other informations, maybe ML can fix this ... if you need testing, I´m here ;-)
Many greetinx,
Markus (from Germany)
I am using the Aug 8 version, and working on understanding Auto ETTR. I have it set to "Press SET" and a slowest shutter speed of 1/90 sec. It routinely uses much slower shutter speeds. I have not found any mention of situations in which the slowest shutter would be ignored, although clearly it can happen. I suspect that the setting is interacting with another setting in a way that is not clear to me. Any suggestions would be greatly appreciated. Thanks
Quote from: Spooke on August 17, 2014, 05:23:00 PM
Could anyone confirm whether this card will work...
http://www.magiclantern.fm/forum/index.php?topic=12630.0
http://www.magiclantern.fm/forum/index.php?topic=11428.0
Short answer - in terms of speed, if you get a good copy it's OK. In terms of reliability, the 64gb version is much better. Unless a larger card is essential for longer recordings, a bunch of 64s is safer as if one dies you aren't totally USC. Eggs - basket - etc.
I'm running 64gb 1066x cards on 7D bodies without any problem, but realistically since the CF bus in the 7D isn't too hot, they benchmark the same as the 1000x.
Quote from: DFM on August 17, 2014, 06:18:39 PM
http://www.magiclantern.fm/forum/index.php?topic=12630.0
http://www.magiclantern.fm/forum/index.php?topic=11428.0
Short answer - in terms of speed, if you get a good copy it's OK. In terms of reliability, the 64gb version is much better. Unless a larger card is essential for longer recordings, a bunch of 64s is safer as if one dies you aren't totally USC. Eggs - basket - etc.
I'm running 64gb 1066x cards on 7D bodies without any problem, but realistically since the CF bus in the 7D isn't too hot, they benchmark the same as the 1000x.
Great thank you! I don't really need 128GB at the moment, I've been surviving on my 650D with a 32GB Card although I can easily fill it 3x over.
Will go for the 64GB for better performance and cheaper cost :)
Quote from: Sukram on August 17, 2014, 06:00:21 PM
@ dpjpandone: Thanks for the latest development! I´m using the audio-display of your latest build, it´s pretty amazing! Thank you for your work, that are great news! That´s what I wanted to have the last months ...
Now ... there is one last wish I have: Could it be made possible to send the audio levels over the USB that I can see it within DSLR-Controller from Chainfire? He told me, that the level has to be given out parallel to the other informations, maybe ML can fix this ... if you need testing, I´m here ;-)
Markus, I didn't have anything to do with getting audio working, (other than re-enabling it) I still haven't gotten a clear answer about why it was disabled, so if you can please test ALL the audio features and let us know if you experience any problems, that would be great. I submitted a pull-request to get it in nightly builds, so hopefully it will show up there soon.
audio levels over PTP/USB - don't know if it's possible, but you may want to make a thread in the "Feature Requests" section of the forum. Maybe a skilled coder who uses a different camera will see it there and take some interest. At this point I don't have the skillset to add new functionality like that, but if someone else gets it working, I can copy and paste it, HA!
One thing you will have to explain is your use case, and a very compelling reason for why you need to see audio levels remotely, somebody will probably say "Just get an external audio recorder...."
/off-topic ON
Sadly wit the most of such collaborative attempts, work is done on the fancy features, and not the ones mere users would really use. Yes I'm grateful that there are such breakthroughs like full res silent pictures, and if that gets developed enough - my camera would survive much more time lapses. Raw is grate, but recently having to do many promotional videos I have hit a frustration with the audio side on 7D, especially that audio monitoring works only while recording, and that you have to use canon's menu to set up gain. Nut much, but still frustrating, especially that ML came to being as a fix for 5Dmk2 audio problem fix, irony (for those who would say sarcasm - please go an check dictionary ;) I would, as many videographers using 7D would really appreciate somebody who is able (I have found me unable to learn C, DryOS and ARM) to fix this, really, especially because somewhat it was working in the first releases, but now is just simply stripped out.
/off-topic OFF
@dpjpandone: Thank you for your answer - I will continue testing ...
Concerning the audio via USB: Well, that´s a great wish for everybody, who is monitoring (field-monitoring) the DSLR Liveview to an external Monitor (Tablet)! The best App for this is at the moment "DSLRController" from Chainfire. And this app CAN display the audio levels for the 5dIII and ??? - but not the 7D - I dont´know why.
For your information: This is, what someone wrote to Chainfire in the xda-Forum: http://forum.xda-developers.com/showpost.php?p=38278477&postcount=2310
Originally Posted by swaproot View Post
Hi, just a suggestion for future releases, would it be possible to monitor audio in video mode via headphones plugged into my android device? I know that with the right adapters and the AV (RCA) cable that Canon supplies with its cameras, you can actually monitor the audio in real time on some cameras such as the T2i or 60D, and since this cable plugs in directly into the mini USB, just like the OTG cable, I thought that it might not be that hard to get the audio from the camera
here are some links showing how it works:
youtube.com/watch?v=BnEtj5l3acs
youtube.com/watch?v=liR6GBc8Vus
His Answer: "As I understand it, the audio comes from special pins in the port, and is not actually transmitted using traditional USB to the client device. I have no personal experience with this, but I know at least one user was looking into making a splitter of some kind to separate the audio signal from the USB signal, and use both at the same time. There was some mention of Magic Lantern in that combination as well, possibly to force the camera to send out both signals at the same time (which I guess would normally be an either/or situation). I have no idea about the current status of this, though, or if it's even possible at all."
And at last MHO: Recording with an external recorder is no option, when it´s possible to do with the tethered tablet ;)
Greetings,
Markus.
Hi to all;
I'm new ( Just joined today ) been reading some posts for over a hr. already trying to find a link where to download the late's Magic Latern software for my 7D F:2.03 because at the magic latern site, there's only downloads for all other canon cameras but the 7D.
Can anyone help with the link?
Thanks in advance to all, and i'm sure that I will be here almost every day from now and on, I'm glad to a part of such a great community.
Attn. Andre
Quote from: ACS1112 on August 18, 2014, 07:41:31 PM
Hi to all;
I'm new ( Just joined today ) been reading some posts for over a hr. already trying to find a link where to download the late's Magic Latern software for my 7D F:2.03 because at the magic latern site, there's only downloads for all other canon cameras but the 7D.
Can anyone help with the link?
Thanks in advance to all, and i'm sure that I will be here almost every day from now and on, I'm glad to a part of such a great community.
Attn. Andre
Here: http://builds.magiclantern.fm/#/
Thanks Jman, very well appreciated, will give it a try.
Attn; Andre
as for the AV out of 7D and many other newer cameras with the USB type of plug, Canon just uses the free space in the USB plug to add some extra pins (compare that with other usb sockets) to facilitate the extra connections for analog video and sound, so in fact it has nothing to do with USB as such. It would be grate to have the analog way of monitoring sound live, because it is most convenient and rather lag free (almost). 7D is a bit trickier, because of the two processors and their relationship, and that is way beyond me to be able to fix. Other thing, 7D preamps are noisy, thus external preamps are must have for any serious work anyway.
I need help here.
My 7D was at 1.2.2 firmware, so I followed online instructions to upgraded to 2.0.3. Then I followed this video https://www.youtube.com/watch?v=ixlBsai0NDM to upgrade to ML-2.0.3 for 7D. the problem is after update, I don't ML interface, instead I still see Canon menu and firmware version shows 2.0.3-ml-Nightly.2
So did I miss any steps?
thanks
You missed reading the user guide.
Top of page -> User Guide -> User Guide
A question from newbie, before installing the Nightly build I have to cancel all settings? and if do not have to delete them, when I get back to the original firmware I find my settings or the camera returns to the factory settings?
Thanks
Sorry for the novice question, can I install 2.0.3 and ML without a CF Reader? All through the inbuilt USB? I think I read no.
http://www.kingston.com/us/support/technical/products?model=fcr-hs3
< 20 Bucks
Anyone else getting pink pixels in highlights when shooting 2.5k raw?
Crop Mode, 2496x1044 2.39:1, fps override 24 (actual fps 24.028), no sound, Global Draw off, extra hacks on. 8s - Pink pixels
Crop Mode, 2496x1044 2.39:1, no fps override, no sound, Global Draw off, extra hacks on. 5s - No pink pixels
Quote from: Walter Schulz on August 21, 2014, 01:12:21 PM
http://www.kingston.com/us/support/technical/products?model=fcr-hs3
< 20 Bucks
Thanks, I do have one but its quite old and slow. I have already ordered a USB 3 one delivery tomorrow - just wondered if I could do it all now. No problem!
Quote from: kiCKYou on August 21, 2014, 01:46:10 PM
Crop Mode, 2496x1044 2.39:1, fps override 24 (actual fps 24.028), no sound, Global Draw off, extra hacks on. 8s - Pink pixels
Can you upload a DNG?
Quote from: a1ex on August 21, 2014, 04:25:33 PM
Can you upload a DNG?
Heh, looks like it's a problem with MLRawViewer...
When exporting to DNG sequence, pictures are fine, but when exporting to .MOV I get pink pixels. Also, a MLRawViewer itself is showing pink pixels in highlights.
You can find dng, mov and print screen here:
https://www.dropbox.com/sh/6ipcrpsu1oa45cw/AACY-exAPgvHP28BgmXT2v85a
Edit: Disabling zebra stripes fixes the issue.
Here: http://builds.magiclantern.fm/#/
[/quote]
i have 3 diferrent computers with windows xp pro, win 7, & win 8, and the folding menu dont work on both... so i think its not just me...
for the moment i download here https://builds.magiclantern.fm/jenkins/
but is it the same built on the first link ?
On my computer https://builds.magiclantern.fm/# is working with IE11 (very much default installation) but fails to open dropdown menu with Firefox 31 ESR (with various blockers).
This is the download link found in http://builds.magiclantern.fm/#
https://builds.magiclantern.fm/jenkins/job/7D.203/174/artifact/platform/7D.203/magiclantern-Nightly.2014Aug20.7D203.zip
This are the download links found in https://builds.magiclantern.fm/jenkins
https://builds.magiclantern.fm/jenkins/job/7D.203/lastSuccessfulBuild/artifact/platform/7D.203/magiclantern-Nightly.2014Aug20.7D203.zip
or
https://builds.magiclantern.fm/jenkins/job/7D.203/174/artifact/platform/7D.203/magiclantern-Nightly.2014Aug20.7D203.zip
EDIT: Argh, I should have tried harder. Answers to both my questions, I think: http://www.magiclantern.fm/forum/index.php?topic=3072.msg126036#msg126036 Sorry for the unnecessary post.
I'm using a build from April (2014Apr06) which works well for me, but in every build I've tried since then up to and including the latest, tested today, enabling the "movie restart" option makes it impossible for me to stop recording - Magic Lantern just restarts it again, and continues to do so until I go into the menu, disable movie restart, and stop recording. Is anyone else experiencing this?
Also, is there a reason the audio options have been removed from the ML menu?
I apologize if this is the wrong place to post this. I'm not entirely clear where this discussion should be had, so if it should be somewhere else, just let me know and I'll move there.
The movie restart is a known issue.
Could anyone tell me when processing 7D Raw, do I need to do any Chroma smooth? If someone could post a small tutorial on what they do that would be awesome!
Quote from: mrtorrent on August 22, 2014, 06:10:45 AM
EDIT: Argh, I should have tried harder. Answers to both my questions, I think: http://www.magiclantern.fm/forum/index.php?topic=3072.msg126036#msg126036 Sorry for the unnecessary post.
I'm using a build from April (2014Apr06) which works well for me, but in every build I've tried since then up to and including the latest, tested today, enabling the "movie restart" option makes it impossible for me to stop recording - Magic Lantern just restarts it again, and continues to do so until I go into the menu, disable movie restart, and stop recording. Is anyone else experiencing this?
Also, is there a reason the audio options have been removed from the ML menu?
I apologize if this is the wrong place to post this. I'm not entirely clear where this discussion should be had, so if it should be somewhere else, just let me know and I'll move there.
Just have a look at #510 ;-)
Markus.
I have installed Magic Lantern on my 7D 2.0.3, all is well. However I feel my AutoFocus isn't very sharp - I've read to remove the small 3V battery and leave it out for a minute and it should fix that.
My question is am I safe to do this with ML installed? I don't see why not but I don't want to break anything.
Quote from: Keyo on August 17, 2014, 06:26:05 AM
Hello everyone. I am testing the latest build of ML (Aug 08). I have been testing out the different features and was wondering if it would be possible for me to utilize MagicZoom and the Digital Dolly at the same time. When I enable the Digital Dolly I loose the ablility to use the joystick to change the position of the focus box. How can I accomplish this? Thanks for this tool, and for the help.
Hi Keyo,
I've the same problem, also with "older" release, for now I haven't found a solution =/
Sorry I am looking at purchasing a 7D. I see that it does RAW in video quite nicely, but does it do dual iso yet?
Quote from: ShootMeAlready on August 23, 2014, 09:49:15 PM
Sorry I am looking at purchasing a 7D. I see that it does RAW in video quite nicely, but does it do dual iso yet?
It does have Dual ISO. I've only just tested it on mine so I'm not sure whether they come out ok! Someone else will have to confirm.
Does anyone have tips for soft focus? On 2.0.5 it was sharp, now it seems to sometimes have soft focus - sometimes its fine.
Quote from: ShootMeAlready on August 23, 2014, 09:49:15 PM
Sorry I am looking at purchasing a 7D. I see that it does RAW in video quite nicely, but does it do dual iso yet?
http://www.magiclantern.fm/forum/index.php?topic=7553.0
Quote from: jman on August 24, 2014, 03:03:47 PM
http://www.magiclantern.fm/forum/index.php?topic=7553.0
The above link is about still photos. I am trying to find about video with dual iso?. I understand the 50D does not do video dual iso but was wondering about the 7d?
Quote from: ShootMeAlready on August 24, 2014, 07:22:08 PM
The above link is about still photos. I am trying to find about video with dual iso?. I understand the 50D does not do video dual iso but was wondering about the 7d?
http://www.magiclantern.fm/forum/index.php?topic=11108.0
https://builds.magiclantern.fm/#/features
Quote from: Stedda on August 24, 2014, 09:29:03 PM
http://www.magiclantern.fm/forum/index.php?topic=11108.0
https://builds.magiclantern.fm/#/features
Hi I looked at the forum rules and always try to adhere. I looked at the features table even before I posted my initial question, but its not clear and misleading. Firstly if I read that table it appears that for the 7D neither raw 1.0 record, or MLV raw is supported. To someone who does not own a 7D and trying to determine in practical terms what that means would assume that it does not shoot raw video at all (raw 1.0 or MLV). Well fortunately Ive looked at raw videos shot on Vimeo and realize that that's not the case.
So its clear as mud to me what raw it does? Ive asked alex if he could update a column on the table below, as a module being listed on the feature table does not clarify if both raw video and still still photo are supported.
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5
Thanks for all help in advance.
Try the following link for an up to date list of supported features on the cameras supported by ML.
http://nanomad.magiclantern.fm/jenkins/features.html (http://nanomad.magiclantern.fm/jenkins/features.html)
Hi,
I tried to day the August 20 build and went back to August 08. With the "August 20 build ":
- I do not see neither the MLV record nor the MLV sound menu. I re-installed twice.
- It froze my camera on "sensor cleaning" at my last attempt.
No problem here. Delete ML dir first before copying downloaded contents to card.
Thanks Walter. It works now. I had the autoexec of the previous version :-[ .
I am I in a deadlock, can not pass the "sensorcleaning" wait for XX sec = nothing is blinking on the Red LED. Switched Firmware back and forth with Canon 2.03 and 2.0. ML. Low level format different cards /nightly builds...
Download Canon's firmware version 2.0.3 and install it. And if 2.0.3 is already installed: Do it anyway!
http://www.magiclantern.fm/forum/index.php?topic=11108.msg107864#msg107864
Format card using a cardreader.
Then format card using your cam.
Follow linked instructions.
Post results.
Still all troll deadlock maybe on the correct term ist is not installing ML
CF CARD KINGSTON 32 GB 133x
First Clean Canon 2.0.3 Firmware and then with MacBoot under Mountain Lion or Mavericks, download this zip file did only "Prepare card" without any checkbox klicked-- no Info wich box need to klick on for ML Firmwire installing.
Situation: Can only Remove the Booflag but not install ML to the Body loaded Canon batt grip removed door closed...
Do as described (= Don't use MacBoot) and post results.
Done this bevore posting the same situation...
The camera is dead, two minutes ago format CF in camera but ML was still there swich on nada new charged Canon Orginal nada...
After cooling down a few minutes with no Bat it is alive trie again...
Do as told, please.
Format card inside cardreader. Don't use FAT32.
Insert card into cam. Cam should startup now. Format card again inside your cam.
I can ExFAT or Free Space, Windows NT Tuxera on my Mac
TNX for thaaa Help
Made it flat with Freespace Format in Cam in cam but I did not se it on my desktop only in the Harddisk Utilty
Sorry, I'm not able to understand your post.
I have no idea if you're telling me your status or asking a question or or or.
Hi...
I followed the instructions, 1. Format the card in Computer, not FAT32 then 2. Format the Card in the Camera, 3. Copy ML Files into the card via Computer, put it back in cam und 4. Update ML Firmware in Camera
Now it made it so, but the is not showing on the desktop after Step 1. + 2. it seems it is unformated
So I go to the Step 1 Card is now on the Desktop copyed the ML Firmware into it.
4. Updated the Firmware In camera: Dialog Please switch Off your camera ( Bootflag installed)
THEN Switched ON Camera No ML Booting over over again...
I am in endless loop please can you help me
Quote from: headroom on August 29, 2014, 03:22:49 PM
THEN Switched ON Camera No ML Booting over over again...
I am in endless loop please can you help me
Please clarify:
Does the camera start or will the camera get stuck during startup?
It is Starting but still as a Canon EOS 7D :'(
Press trashcan button
Upps !!
tankyou! here we go now...
:) or
not really put back the Batterie Grip Camera does not Switching On
Put the Grip Off, Doors on 1 x Batt only, back to Grip On, an now it is working !
Hip Hip Hurra!
Hi guys, I'm looking to install ML. Currently my 7d has 2.0.3 (from factory) but I just read here that I should reinstall it first...anyone have a link to it?
You might want to read the first page of this thread ...
Walter, lately I have watched you support several new users who can't figure out how to install magic lantern on their 7D. I just wanted to tell you that you are a really nice guy for doing this. You are very patient with everyone, even those who refuse to read or follow directions. Thanks for being so kind and helpful to everyone here.
"I sort of enjoy the fact that I'm misunderstood most of the time. That's fine."
Billie Joe Armstrong
Hi,
first time posting. I've got a 7D and I've heard that ML do a 7D version, but on the downloads page it doesn't have a version to download for the 7D - it only lists:
5D Mark ii 2.1.2
50D 1.0.9
60D 1.1.1
500D 1.1.1
550D 1.0.9
600D 1.0.2
Is there a version for the 7D, and if so, how do I get hold of it?
Many thanks :)
You might want to read the first page of this thread, too ...
Hi,
thanks. I wasn't sure if that was a "proper" build, as it wasn't on the downloads page.
I'll give it a go tonight.
Many thanks :)
Quote from: Trabimanuk on September 02, 2014, 11:07:44 AM
I wasn't sure if that was a "proper" build, as it wasn't on the downloads page.
Don't know what "proper" means to you. You will find some reading about "Nightly Builds" on ML's download page.
Can someone tell/advise me if the 7D version of ML is likely to havethe feature of shooting at 50 ISO ?
Thanks in advance.
Standard answer: Already there! Overexpose by 1 EV at ISO 100.
http://www.magiclantern.fm/forum/index.php?topic=950.50
I like to report about Aug 20 2014 version on 7D and went to an anime convention. I filmed at 1280x514, 16:6 and 60fps, and I was surprised the version can record in continue on my fastest card. However, I still get few corrupted pink frames. It is headache to look for the pink frames. When I worked with a cosplayer, I turned my camera on and adjust exposure and focus right way. Sometime, it crashed like won't allow me to start the record after the adjust. I had to turn off and turn on to record! I don't have time to reproduce the problem. I think it crashed because I did not let the camera to load magic lantern program first when I start work with my setting. I will look at it this weekend. Is there a program can detect a bad pink frame, remove it and rename whole image sequence?
Anyone got any idea why after recording RAW I get BUSY shown on the screen and have to turn it off and on to take photos?
Hello guys,
I've tried to make a new card bootable but no matter what method used (in camera via firmware or via eoscard), it wouldn't work.
I thought it was a bargain because of the cheap price but it's finally a fake card: slow speed and the pictograms on the back are badly reproduced compared to the two other cards I have (the front is different too, like the fonts used).
You can see all this on that pic: https://dl.dropboxusercontent.com/u/14585948/cf-lexar-test.png
Ok, I've got a *** card (I'll return it) but I don't understand why I couldn't get it to boot ML because the same tests with the Lexar 8GB 800X worked well. Do you think I might have done something wrong or is it just because it's a fake?
Quote from: Spooke on September 03, 2014, 09:20:36 PM
Anyone got any idea why after recording RAW I get BUSY shown on the screen and have to turn it off and on to take photos?
Probably something wrong with the memory backend. Find a way to reproduce and submit a bug report.
Hi ppl fresh user here;) after ive been reading post after post after post..... here it seems i cant use the stable ML thats out for my 7D but i'll have to go with this awesome looking knightly build from amongst others A1ex... correct? my question is which rls is the most stable one if we dont look at the super RAW video part?
since i dont have any intrest in that, i just want a stable "bug free" rls with all the other gems ;)
Stay safe
Quote from: a1ex on September 04, 2014, 02:57:30 PM
Probably something wrong with the memory backend. Find a way to reproduce and submit a bug report.
The strange thing is I had the same issue with my 650D (only when recording with a 50mm f1.8 on that one though!).. Different cards.
I'll try and reproduce it and add it to the bug report.
Hi All,
Long time listener, first time caller. Just wanted to report some of my findings with y'all, that have very likely been touched on in other threads, but just to let y'all know. I'm running the 8-20 nightly on my 7D, with pretty good results. @dpjpandone - I've yet to DL and run some test shots with your build, but going to try and see I can do so once things slow down at work and I'll be sure to report back.
I finally gave up on the hope of using the RAW module for paid work after I kept having sporadic test shots with occasional corrupted pink frames, and the vertical lines issue also cropped up here and there. I've read that it's fixable with a little bit of coding and post, but with our workflow, we need to shoot, and be ready to deliver the following day, so no bueno for me.
For me, the working setup thus far has been using MLV, 1724x968 @ 23.976. I run a lilliput 663 on my glidecam, with a nyrius aeries pro sending video wirelessly to a marshall directors monitor. I shot a :30 a few days ago with these settings and every shot that came off the card looked great.
RE the HDMI out - I experience a lot of tearing when not using "Force VGA" option, which is why I'm itching to try dpjpandone's build. FWIW, I've also disabled global draw for good measure, which from my last batch of test shots didn't seem to have an effect either way. (wasn't using peaking or anything fancy, just histo and all the standard info like ISO, SS, aperture, etc.)
For me, initially, I had a ton of pink frames via RAW when i was doing my first tests on my sandisk extreme CFs, while I was waiting for my new card to arrive. I opted for this one, and have no complaints or issues thus far:
http://www.amazon.com/Lexar-Professional-1066x-CompactFlash-LCF128CRBNA1066/dp/B00IAYFDJG/ref=sr_1_1?s=pc&ie=UTF8&qid=1410052349&sr=1-1&keywords=cf+card
For post, I run it all through the paid version of RAWMagic (heresy, I know. :/) It does a quick job of cranking it all out though, and working with the DNGs in premiere for a rough edit with scratch audio is a lifesaver.
Lastly, wanted to give a big "Thank you" to all the devs that have made this possible. I have been hating my canons for the last year or so, and couldn't wait to upgrade to something better. With Magic Lantern I feel like I've got a whole new camera now. Really top-notch, and really appreciate all of you!
Volta88:
I think we are actually very close to having the changes merged into main nightlies so you can use your external monitor at full resolution (no more force vga) I have had very good results recording up to 1728x864 with full hdmi output and no tearing with the build I posted. Sadly, this isn't quite 16x9, it's 2:1, but a huge improvement over previous results (which exhibited tearing at EVERY resolution) so you will still have to use force vga for 1728x968, but I'm reading everyone's notes and digging through the code every day to try to get the same performance with full 1080i hdmi out, as is possible with force vga (480p output)
Something I noticed is that one of the most resource hungry features is the raw histogram, (it makes the cpu load jump from 27% to almost double, and drastically reduce raw performance. Leaving global draw on seems to be fine, as long as I turn the histogram off when I'm using my monitor at full-res.
Solving this tearing issue completely, remains the highest priority for me because the 7D is still the only Super 35mm (aps-c) sensor camera (ml supported) that records reference sound and has a fast CF card, and this will likely be true for a while, so I really feel that it's a good investment for me and anyone else who wants to use Canon DLSR for serious cinematography.
I would love to see some of your work. I too work in video production for a living, in a fast turnaround environment. I shot the entire season of "Let's Go Youngstown" on aps-c canons (t2i, t3i, 7D) which you can watch here if you are interested:
http://www.dpvisualmedia.com/home/home-3/lets-go-youngstown
it's a television show that airs weekly on the CW in my city, it is broadcast in HD, and the IQ of these cameras is nothing short of amazing. Magic Lantern made it possible for me to leave my old boring job as a graphic designer and follow my dream to become a DP, and for that I am truly grateful!
Our intro for next season, and some of the segments will be shot in MLV RAW this year, and I'm really looking forward to sharing those with you after they air.
Quote from: dpjpandone on September 07, 2014, 04:19:49 AM
Volta88:
I think we are actually very close to having the changes merged into main nightlies so you can use your external monitor at full resolution (no more force vga) I have had very good results recording up to 1728x864 with full hdmi output and no tearing with the build I posted. Sadly, this isn't quite 16x9, it's 2:1, but a huge improvement over previous results (which exhibited tearing at EVERY resolution) so you will still have to use force vga for 1728x968, but I'm reading everyone's notes and digging through the code every day to try to get the same performance with full 1080i hdmi out, as is possible with force vga (480p output)
Something I noticed is that one of the most resource hungry features is the raw histogram, (it makes the cpu load jump from 27% to almost double, and drastically reduce raw performance. Leaving global draw on seems to be fine, as long as I turn the histogram off when I'm using my monitor at full-res.
Solving this tearing issue completely, remains the highest priority for me because the 7D is still the only Super 35mm (aps-c) sensor camera (ml supported) that records reference sound and has a fast CF card, and this will likely be true for a while, so I really feel that it's a good investment for me and anyone else who wants to use Canon DLSR for serious cinematography.
I would love to see some of your work. I too work in video production for a living, in a fast turnaround environment. I shot the entire season of "Let's Go Youngstown" on aps-c canons (t2i, t3i, 7D) which you can watch here if you are interested:
http://www.dpvisualmedia.com/home/home-3/lets-go-youngstown
it's a television show that airs weekly on the CW in my city, it is broadcast in HD, and the IQ of these cameras is nothing short of amazing. Magic Lantern made it possible for me to leave my old boring job as a graphic designer and follow my dream to become a DP, and for that I am truly grateful!
Our intro for next season, and some of the segments will be shot in MLV RAW this year, and I'm really looking forward to sharing those with you after they air.
Well in that case, I'm a little bummed I missed out on the party to help test this out for yah! :) Eagerly looking forward to running it through the paces regardless of whether it appears in a nightly soon or if I use the build you posted previously. VGA out on the monitors isn't all that bad, and certainly sufferable IMO, but there's nothing like seeing a crisp HD image on the monitor. Even at 2:1, in a pinch a usable HD image is a good tradeoff for making sure my focus stays sharp when I'm wide open on a quick tracking shot. Appreciate all your hard work on this!
Also - appreciate the quick note on the histo - I had no idea it ran the CPU that hard, I'll be sure to keep that in mind next time I'm trying to keep my usage down.
Just checked out the link (and the whole site! :) you shared - great stuff, very solid edits, and nice color! I don't need to tell you this, but the color on any of the canons h264 image is just a pain to work with, so it's awesome to see folks that are able to push it far enough to achieve some really nice grades. (I know I never can, haha!)
IF you're interested, here's some of our stuff, a documentary we shot about a year ago, all on a 60D and a 7D with a gopro H2 for timelapses and the like:
http://youtu.be/DF_o_omA3l0
And an (old and in need of update) reel, again, shot on our 7D and 60D:
http://youtu.be/1s5u_oDVwDw
Sadly, no RAW footage to share just yet aside from test shots of my long-suffering wife and kids, but hoping to have some online soon after another round of shooting out in North Carolina this week! I shall report back with an update for y'all. In the meantime, I'm happy to make myself useful for anything you folks may need, no idea how to code, but have lots of gear I've accrued over the years and more than happy to configure it in any form or fashion to run some tests for the good of the order! :)
-Dan-
Dan:
The intro for your gambling documentary is AWESOME! Lighting in the interviews looks great too. Love the timelapse sequences as well!
Your demo reel is... Phenomenal! I really love the coloring and all the slider shots, it's very well sequenced too, it shows that your company is capable of producing a broad range of content.
I'm really happy to have you on board, it will be great to have someone who is using the 7D often in a production environment to help with testing and feedback.
if you have time, and want to help, please test this build: http://www.filedropper.com/magiclantern-nightly2014sep077d203
please provide your feedback regarding HDMI performance here:
https://bitbucket.org/hudson/magic-lantern/pull-request/589/use-faster-edmacs-to-fix-tearing-on-7d/diff
and feedback regarding audio controls here:
https://bitbucket.org/hudson/magic-lantern/pull-request/586/audio-controls-are-working-on-7d-wind/diff
Thanks!
~Jon
dpjpandone, I have a FANTASTIC opportunity to shoot a campaign video for a man running for US Congress in two weeks, so of course I'll be using 7d MLV with sound to shoot it. I'll probably be using your build with audio options if they're not in the nightly by then. Do you have a build of the latest nightly with audio options and anything else that needs testing? Thanks, man!
the one in the post above is latest nightly with audio controls enabled, and faster edmacs. It's a good idea to do some camera tests before your important production.
Cool, thanks. Don't worry, I've been testing since M0000001.RAW ;)
hi!
i'd like to install magic lantern on my canon 7d, but i've noticed in "downloads" section that 7d is not indicated in cameras supported by latest stable release 2.3
how can i do to get magic lantern on my poor 7d?
thankssss
First post of this very thread ...
Hello all,
I've noticed way earlier on in this thread, there's talk of headphone monitoring on the 7D, and it seems a few people have been able to do so either using the t2i special cable (http://www.bhphotovideo.com/c/product/765530-REG/Sescom_DSLR_550D_HOCF_DSLR_550D_HOCF_AV_Out_Headphone.html) or the Canon mini USB to RCA cable with stereo adapter (https://www.youtube.com/watch?v=liR6GBc8Vus)
I've just upgraded from a t2i, I've been using the Canon mini usb/RCA/stereo adapter hack on the t2i and it works fine, but on my new 7D it doesnt work and causes the screen to go blank.
Is this still a known issue? I'm using the latest nightly build "magiclantern-Nightly.2014Sep01.7D203"
Thanks!
+1
Also want to have audio out over USB to have control in the android-app dslr-controller ... (im)possible? Got still no answer ...
Markus.
jessdev:
Audio controls are not in nightly builds for 7D (yet). And When they are, headphones will still be disabled (for a while). You might find them working in the alpha build (that eoscard downloads automagically) but you have to enable headphone monitoring in the menu, then plug/unplug a few times to get your screen back on.... and if you can't figure it out, you will likely have a hard time getting support for such an old build, you'll also be missing a lot of improvements that happened since then...
Short answer: Your best bet is to pick up an external audio recorder, or a preamp that has a headphone out (the preamps in these cameras suck pretty hard anyways)
We are filming with external Microphone pluged to the cam, BUT my thing is, that I can SEE the audio-level in dslr-controller, because we film a lot tethered (1m to 5m distance to the cam), it is ugly for us, to walk to the cam, to see the levels ... it would be a very big improvement to have them displayed in the app ;)
Greetings,
Markus.
Markus,
I understand your use-case, I'm suggesting you use an external recorder (which will greatly improve your sound quality) and you can keep it right next to your tablet so you don't have to "walk to the cam, to see the levels"
I think for the most part, the tethered tablet apps have the same functionality as canon eos utility. Can you monitor the audio levels in canon eos utility? If not, then it's probably not possible.
If you want to get a definitive answer without waiting for someone else to take interest/initiative in your requested feature, you should research "PTP protocol" then look into how ML handles audio levels, and see if there is a way to pass the value that corresponds to audio level, over PTP, after you do that, you'll have to work with the developer of DSLR controller to get these values interpreted on the other end. A good question to ask might be: "Can the values that correspond to audio levels be passed over PTP?"
It will probably take much less effort to acquire an external audio recorder and integrate that into your workflow. I'm not trying to kill your dreams of audio levels on DSLR controller...I'm just suggesting a solution that will work TODAY... rather than waiting with fingers crossed for several people to spend their time developing a solution for your unique case.
What about ML on 7D mark II?))
"Canon EOS 7D MKII: AF and Processor
There are a bunch of very important changes underneath the hood, though. The Canon EOS 7D MKII uses two DIGIC 6 processors rather than just the one, giving it simply excellent shooting speeds.
You can shoot in full resolution at 10fps. That's 4fps faster than the Canon 5D MKIII and 3fps faster than the Canon 70D – extremely fast.
If you shoot in RAW you'll be able to shoot up to 31 photos before the buffer is filled, but with JPEG shooting you'll be able to carry on continuously. It helps to explain some of the Canon EOS 7D MKII's price, which feels quite high for an APS-C model when cameras like the Sony Alpha A7 are bringing full-frame sensors to smaller frames and prices. "
Hey guys,
Does anybody have any RAW video footage from the 7D that I can get my hands on?
I'd like to do some tests with it before I try it out on my camera.
Thanks!
Hi everybody, i'm new here ;D
i try to understand why there's no stable version of ML for 7D and why audio doesn't exist.
I install ML today from the link at the begining of this post, do you know if this is the latest nightly build ?
Thank you
Quote from: KevinG on September 15, 2014, 10:49:45 PM
Does anybody have any RAW video footage from the 7D that I can get my hands on?
Do a search of the forums for raw2cdng when they were developing that they shared some raw files to test the software and posted the download links here.
Quote from: Gwarf on September 19, 2014, 01:25:17 AM
Hi everybody, i'm new here ;D
i try to understand why there's no stable version of ML for 7D and why audio doesn't exist.
I install ML today from the link at the begining of this post, do you know if this is the latest nightly build ?
The latest build is always shown first. There is no stable version because that takes time, Money and skilled developers. You can help accelerate progress by testing, providing feedback and donating.
I'm not sure what you mean by audio doesn't exist, so can't help you there.
In my not so humble opinion the effect of donations on getting closer to a stable version is vastly overrated.
Quote from: walter_schulz on September 19, 2014, 07:28:12 AM
In my not so humble opinion the effect of donations on getting closer to a stable version is vastly overrated.
Probably true, although it does help a little. No one like to work for free.. If I had more time, I would jump on trying to develop myself.
I have just installed the latest nightly build and I only get the Beep/Test tones option in the audio menu as well.
What and I missing? Are all the files included here (magiclantern-Nightly.2014Sep12.7D203.zip) or
do I need to combine files from somewhere else?
Thanks
John
Read through the thread from the beginning, audio controls are not available.
I feel like the 7d has so much possibility for more Raw features, and more tools in general. I'm extremely hopeful that the developers don't let the recent controversy discourage them from continuing to develop ML for our dear 7d's.
Is finally a possibility to record raw video on 7D without any crop? Becouse on yt or viemo a have found videos only recorderd with crop (x3 or x5).
Native RAW video resolution for 7D is 1728x1156. See
http://www.magiclantern.fm/forum/index.php?topic=6215.0
There's a new update for 7D apparently , could someone explain about audio controls , the change log is another language for me :D
https://builds.magiclantern.fm/jenkins/job/7D.203/changes
just install it and page over to the audio menu to see these features.
With the latest sources I could record about 1 mn 40s (2423 frames) of full HD raw video at 1920x1080@24p (FPS override) in 5x crop mode with Canon Liveview, sound and global draw ON with Zebras and Focus Peak !
I think this is outstanding, a great achievement :-)
My CF is a Komputer Bay 64GB 1000x.
Quote from: vyskocil on September 27, 2014, 03:10:47 PM
With the latest sources I could record about 1 mn 40s (2423 frames) of full HD raw video at 1920x1080@24p (FPS override) in 5x crop mode with Canon Liveview, sound and global draw ON with Zebras and Focus Peak !
I think this is outstanding, a great achievement :-)
My CF is a Komputer Bay 64GB 1000x.
Wow! Magic or tragic lantern? Can you give us the download link? Many thanks!
Quote from: dlrpgmsvc on September 27, 2014, 03:27:59 PM
Wow! Magic or tragic lantern? Can you give us the download link? Many thanks!
Magic Lantern of course ! I built it from source but I suppose that nighty build should be up to date now.
GD :off 23.976
2:00 MLV/Snd
2:40 MLV
4:09 Raw Rec
Both versions should have identical speeds with SRM and the same edmacs being used.
There are questions on 7D concerning edmac flags, break after xGB (this went away and returned), some irregularity in write speed on mlv, not present in raw_rec. Finally looks like we're approaching 50D continuous recording.
A sidequestion. 1percent. Are you saying mlv and rawrec should get the same rec speeds now under same settings?
I still get longer recordings with rawrec than with mlv with my 5d mark 3.
no, magic/tragic record times should be the same on 7D.
Ok, thanks
I'm trying to catch up with the 7D developments. What seems like ages ago, I installed the 2nd alpha release. I liked the fact that everything was only temporary. Is such a setup with the latest version possible too?
With "temporary" you mean that ML won't be loaded at startup? No bootflag and ML has to be reloaded each time your cam is turned off?
If that's what you want: No, this one has gone for good.
I don't see exactly which problem this makes apart from slower reaction time at startup and leaving sleep modus.
Very nice version!! thanks a lot!
a litle bit sad because i read dual iso in video is impossible in 7d :-( is that right?
what is the future of raw video? what features you will improve??
thanks a lot for your work, thanks thanks thanks
Quote from: thefrost on September 28, 2014, 12:21:38 PM
I'm trying to catch up with the 7D developments. What seems like ages ago, I installed the 2nd alpha release. I liked the fact that everything was only temporary. Is such a setup with the latest version possible too?
What walter is saying is that you no longer have to install ML every time you start the camera (and this is a good thing!)
If you want to disable ML, hold Q or Set when you turn the camera on.
Won't get rid of delay during startup/recovering from sleep, though.
Quote from: Walter Schulz on September 28, 2014, 03:15:15 PM
Won't get rid of delay during startup/recovering from sleep, though.
It's a bit annoying , although i did not miss a shot from it but still takes about 3 seconds to run up.
Hi!
i notice now we can not use frames override in hs264 mode,
why?
i thinks is very usefull to quickly video timelapses
camera locks up or crashes when fps override is used on h264 therefore disabled
I haven't been following for a while, so it might be a huge task to follow up. May someone spare a second to kindly tell me if that 1/3 stop reduction in highlight register trick in 7D been solved (I forgot what it was called)?
Oh, correct. I found it here:
http://builds.magiclantern.fm/#/features
EXPO_ISO_DIGIC is called, isn't it? Unsolved.
EXPO_ISO_DIGIC is an old ISO tweak for H.264.
The new one will be a module, so it will appear at the top of the list.
So i'm a noob at this but have a few questions.
Installing ML is easy as - formatting CF card, placing the ML zip file inside root of CF card and running "firmware update" through canon's firmware?
Also ML is installed to the CF card, meaning if i insert another CF card, will canon's firmware bootup?
Uninstalling is as easy as running "firmware update" from ML?
Would i need a CF card reader or the usb cable -> 7d will suffice?
Thankyou.
You need a cardreader. I recommend Kingston FCR-HS3.
All other questions are covered in FAQ, user guide and first post of this thread.
I got a card reader, but the first page has no mention of making the card "bootable" via EOSCARD.
Edit : The EOS card method is to avoid the firmware update method, got it :)
So, i followed the instructions, when it said restart the camera, I turned it off then on.
Nothing changed, the canon menu shows up. Just the firmware now reads 2.0.3 ml - off
Did i do something wrong?
Edit: Got it working by a restart :p
Hi all!
I've been losing track on the Raw status on the 7D... can somebody that has been using it tell me a stable version for it?
I tried a couple last week but during shooting I got several errors and skipped frames on a KP 64GB 1066x, weird right? 30% idle the buffer said.
Thanks a bunch!
i think 1066x cards are more slow then 1000x
Ironically with this last version i could get a clear shot for 10seconds w/o a single skipped frame on full resolution with a 8GB Sandisk 50mb/s.
Really amazing!
Thanks for your answers!
Anyone using it on a regular basis? A version number? Tragic lantern or magic lantern?
Tony, the latest magic lantern for 7D has been working fine for me. It is also faster than most older versions, thanks to some recent improvements.
This is a first post for me and I curious how stable the current version of ML for my 7D will be. Will it brick my camera or will my raw footage be 90% corrupt frames?
I'm not a noob to shooting just a noob to ML.
Any feedback helps.
thanks.
Quote from: b4vendetta on October 09, 2014, 09:56:06 PM
This is a first post for me and I curious how stable the current version of ML for my 7D will be. Will it brick my camera or will my raw footage be 90% corrupt frames?
I'm not a noob to shooting just a noob to ML.
Any feedback helps.
thanks.
Take the time to read through this thread and many others and you'll quickly realize that the ML devs go to great lengths to avoid putting out code that will brick your camera or ruin your footage. I've shot dozens of commercials, music and promotional videos, even campaign ads with ML on the 7d and T3i over the past few years and have yet to experience any major issues.
As long as your reading comprehension and direction following skills are up to par, you and your camera will be fine, and better off with ML installed, imho.
QuoteI've shot dozens of commercials, music and promotional videos, even campaign ads with ML on the 7d and T3i over the past few years
Wow... would love to see some of your work with the 7D! Is it online? :)
Check the "Share your Videos" section, just posted one.
Wow it looks really good!! Congrats!! Any advice on shooting crop mode on the 7D? I mean, the preview it's awful! hehe. Also, th versions that I use only let me chose until 2046 res horizontal i think, and the 25xx it's not available. Do you know something about that?
Thanks, the uncompressed version is MUCH better looking, though. I submitted a feature request to have the ML preview display on half shutter while in Canon preview crop mode, but I'm not sure if its possible.
Depends on what you're framing, I find that if I keep the person's face framed in the upper right or left corner, it's almost always properly framed. Choose 2560x1200, or whatever max rez is, and it limits the rez to 2496x whatever height you pick
is there a possibility by upgrading to Magiclantern , I could attached the canon 7d to a motion sensor to shoot video when the trigger is activated.
Denis
Where I can open a technical topic on a specific 7D porting feature (for example dual_iso for video) where to discuss and share programming results until the goal is reached ?
Many thanks !
Oh wise ones!
I had just THREE questions:
a) Is there a stable release or any other nightly build with reasonable success for 7d that i can try (First timer!!). Can i run it with the latest firmware 2.0.5?
b) Once we have the ML on the CF card and run it, is removing ML as simple as removing that memory card and putting in a new memory card into the camera? Does it affect the baseline functionality (if the ML is running alongside only from the card).
c) Related to Question b) --> If ML runs only from the Memory card and if we dont switch off between installs, remove memory card when the red light is still flashing (or) run out of battery mid-way etc (or) dont do anything stupid which is a combination of these 3.....is there a real chance to BRICK the device?
Nightly Builds only.
Rest of a) and b) is answered in first post of this thread or FAQ/User Guide.
Remark to b): There will be a delay (<2 sec) during camera startup and wake from powersave mode even if a card is not enabled to run ML.
Number of bricked 7Ds by nightly builds (outside devs dungeon) = Zero (known to me).
And of course there is a chance because it is absolutely impossible to exclude such failures.
Can someone P L E A S E tell me why I can't shoot more than one dual iso photo. What happens is that I shoot a pic. When I review it, it has the dual scan lines. Then I try to shoot the next pic and no scan lines. W H A T do I have to do to reset this or what am I doing wrong??? Cheers !!
Expo -> Dual ISO -> Alternate frames only
Up...
Can someone P L E A S E tell me why I can't shoot more than one dual iso photo. What happens is that I shoot a pic. When I review it, it has the dual scan lines. Then I try to shoot the next pic and no scan lines. W H A T do I have to do to reset this or what am I doing wrong??? Cheers !!
Thanks Walter.....Expo -> Dual ISO -> Alternate frames only
I took pics without alt frames only. When I turn the camera on and take a pic it has both scan lines. I really don't want to take 2 pics of the same subject with alt frames. I find that I have to turn the camera off and on between each shot if I do not use Alternate frames only. I was wondering why there is no reset type of thing. Anyway the single pics process fine in cr2hdr.
(http://a05.imageupper.com/1_t/8/Q14132162721168006_1.jpg) (http://imageupper.com/i/?A0500010080011Q14132162721168006)
Do you use this setting or not?
Hey Walter... I used with the setting OFF. Works fine for the first pic. Then I have to turn the camera off and on to reset. Strange.
Hello everyone.
I just downloaded the current nightly, I've haven't gotten a new version since TL was banned, so I've been out of the game for a while. Everything was going swimmingly until I switched to crop mode to try some 1080. First shot went good. Tried a second shot and got a crash. Rebooted, tried again and got a crash and error 70. I'm posting the logs (hope I do it right)
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTR_LV, NULL, 0 ) )
at LVState.c:485, task ?
lv:1 mode:3
Magic Lantern version : Nightly.2014Oct08.7D203
Mercurial changeset : a27e3b9df491 (unified) tip
Built on 2014-10-07 22:30:35 UTC by [email protected].
Free Memory : 196K + 2639K
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_RESET_PSAVE_LV, NULL, 0 ) )
at LVState.c:608, task ?
lv:1 mode:3
Magic Lantern version : Nightly.2014Oct08.7D203
Mercurial changeset : a27e3b9df491 (unified) tip
Built on 2014-10-07 22:30:35 UTC by [email protected].
Free Memory : 196K + 2635K
ASSERT: !IS_ERROR(err)
at LiveView.c:2357, task shoot_task
lv:0 mode:3
Magic Lantern version : Nightly.2014Oct08.7D203
Mercurial changeset : a27e3b9df491 (unified) tip
Built on 2014-10-07 22:30:35 UTC by [email protected].
Free Memory : 220K + 2780K
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_RESET_PSAVE_LV, NULL, 0 ) )
at LVState.c:608, task ?
lv:0 mode:3
Magic Lantern version : Nightly.2014Oct08.7D203
Mercurial changeset : a27e3b9df491 (unified) tip
Built on 2014-10-07 22:30:35 UTC by [email protected].
Free Memory : 219K + 2776K
I haven't used ML lantern much in a while so I'm not up to date with all thats happened lately. Can anyone sort out whats happening to my camera?
Thanks
What's the latest on Magic Lantern for the 7D? I can't find any recent posts on the subject. Is the current "nightly build" solid? I just picked up a used 7D to go with my 60D and 5DII. Love ML on the other cameras. Hope it works as well on the 7D
Whilst I don't use all of the features of ML, for those that I do, I've found it to be very stable.
Cheers... Otto
Hello!
I'm new ;-).
I started using ML mainly for the higher quality movie features - i had the time to get into it, but i came up with some problems and i'm not shure if it's me or magic lantern.
I'm using the latest nightly build form the 8. October
There are some issues, but i think probably half of them can be solved with this one:
My raw video is significantly darker than H264 or a jpeg shot with the same settings - the live Fiew is matching the jpeg/h264.
With mlv_rec: Superdark, additionally the camera doesn't save the raw correction data, i have to adjust everying afterwards from zero.
with raw_rec: Still to dark, but it saves all the raw information and looks a little bit lighter - even if it's still useless.
Is there a way to fix this through make the right settings? I have to make some really strong correction, and it looks crappy before it get's back to a comparable value.
You have to be more specific and you should post some examples (like a DNG from the raw video and a frame from the h.264).
Quote from: Joper on October 20, 2014, 12:28:20 AM
significantly darker ... Superdark ... Still to dark
By how much, exactly?
Quote from: Joper on October 20, 2014, 12:28:20 AM
I have to make some really strong correction
What kind of "correction"?
Quote from: Joper on October 20, 2014, 12:28:20 AM
it looks crappy
How so (post example)?
What's your post processing workflow?
What settings were you using?
Quote from: Joper on October 20, 2014, 12:28:20 AM
the live Fiew is matching the jpeg/h264.
You should not be using the screen to judge correct exposure for raw video (since the image on the screen does not and cannot reflect what is truly in the raw data), instead you must rely on the raw exposure aids (http://www.magiclantern.fm/forum/index.php?topic=12096.0) (like: histogram, zebras, spotmeter) or use AutoETTR (http://www.magiclantern.fm/forum/index.php?topic=5200.0)
I reinstalled Magic Lantern and changed a few settings (i deactivated the custom setting for 1/3 ISO stops), since the i didn't had the error anymore, everything looks fine - but i'll keep the final word to the long term study, looking forward to it. :-)
Anyway, where here to make ML better, so here's the more precise description:
By dark i mean that the basic color of the raw image was black with a normal exposure (EV±0). I was able to push it so i can see some details, but from black as a base instead of a normal exposed picture. I think the difference between the raw_rec and mlv_rec came through the (from camera) uncorrected raw data i had for the mlv-dngs (corrected in adobe raw, either in photoshop or after effects) while the raw-dngs kept the cameras information.
I photographed in M mode, my exposure was always based on the informations ML gave me on the screen/in the settings. I used the histogram for comparison with raw, but it didn't help with the buggy raw movie files.
Ah, my raw movie workflow: i used the mlvtodng script /rawtodng application on mac os x, imported the dngs to Adobe After Affects (as said adobe raw for correction) and exported the data as Prores 4:2:2
I'll try to recreate the error in the next time to possibly understand moe of it and get some example data.
I'm having a problem recently which i don't know the cause but it's making my 7D to a 3-4 Fps camera.
even though i'm putting the camera on High Continuous , it's really slow.
only though that came to mine was the buffer being nearly full all the time.
Any ideas?
First: Is it ML related? Start with SET button pressed and try again.
Result?
Quote from: Walter Schulz on October 23, 2014, 12:49:59 PM
First: Is it ML related? Start with SET button pressed and try again.
Result?
That's the problem , i tried it w/o and with.
sometimes it's fine and sometimes it's not.
Is there a way i could reset the whole thing (ML and 7D together)
If you start up with SET pressed: Is the fps thing occuring or not?
I have noticed that if ETTR module is loaded and you have forgotten and left it on, that might happen. so make sure that modules are off and do you have the problem. also if you debug change only one setting until you catch the error, otherwise it is hard to find what is to be the fault.
That's why I asked him to start with SET button pressed.
Quote from: Walter Schulz on October 25, 2014, 01:38:06 PM
If you start up with SET pressed: Is the fps thing occuring or not?
basically what i said , even without ML running the problem stays better say sometimes it does and sometimes it doesn't.
Quote from: ansius on October 25, 2014, 01:44:02 PM
I have noticed that if ETTR module is loaded and you have forgotten and left it on, that might happen. so make sure that modules are off and do you have the problem. also if you debug change only one setting until you catch the error, otherwise it is hard to find what is to be the fault.
Running the camera w/o ML (what Walter suggested) will basically solve this problem.
i taught this had to do with Buffer so i pulled the memory out and still Continuous shooting at 3/4 frames per second.
Looks like an error unrelated to ML. Try to reset the cam to factory defaults (including Fn-settings) but I'm not that convinced it will do any good. Anyway, just to make sure ...
Before i reset it.
I found that camera tends to slow down when light decreases.
here's a video: http://www.mediafire.com/watch/4k9hcpotin59out/Shutterproblem7D.mp4
My apologies for the quality but i feel it's enough for demonstrating the problem.
Press SET at startup, use modus M, Auto-ISO off. Test again.
Nothing changed.
try with auto focus set off, how is then?
@ansius: Ever tried changing focus mode on a cam without lens mounted?
Maybe he didn't download the video , come on Walter :)
Hi. This is my first message, so I'd like to thank everyone involved in this really nice feature for our Canon babies.
I hope this is the right place to ask my question. I recently tried the ML night build for the 7D and everything works fine except for the fact that I don't have the raw video option in my screen. I tried an older night build and have the same result. I also tried a faster card, in case ML was able to see the card speed and was hiding the raw option for this reason, with no result. Here's a picture of my video menu.
(http://i1060.photobucket.com/albums/t449/alexsocal/Photobucket%20Desktop%20-%20alex/no_raw_zps31dd0ca2.jpg)
Do somebody know why is this happening?
Thank you very much!
Module tab -> Enable RAW_REC or MLV_REC -> Restart
Thanks!!! :D
What is the reason for choppy/lagging playback for raw video? Also I can't seem to record longer than 11 or 12 seconds before frames start being skipped. Any solution to this?
I suppose you're running RAW/MLV videos.
Lags: There is not enough processing power in your cam to allow lagless playback.
Skipping: Debug tab -> Benchmarks -> Card R/W benchmark (5 min). Compare write performance with the numbers required by the resolution/fps rate you're using. Turn Global Draw off.
thanks for the reply
so my settings for video are
bitrate - 0.9x
FPS override - off
vignetting - off
RAW video (MLV) - off
RAW VIDEO - on 1728 x 972
my write speeds are averaging around 70 MB/s
read speeds 728 MB/s
What am I doing wrong?
Thanks
also my aspect ratio is 16:9...I can't go any higher on resolution
Hey Walter,
I changed the settings and I met the R/W numbers and Im still losing frames at 12 seconds REC time. Another thing I just learned was that I can't open MLV files on my computer. I keep getting a notice that says the file is unreadable. Any advice or help?
As always thanks!
Benchmarks are just benchmarks. They are not telling the whole truth.
Reduce resolution and test which one is giving enhanced recording times.
And use bitrate 1.0 for starters.
Have you tried to open a MLV recorded without skipping (< 12 seconds)? Which program do you use?
Wondering how to get MLV files when using RAW video ...
my card reader displays it as an MLV file. ... I either use EOS utility or iPhoto or Final cut to pull data from the card.
I changed bitrate to 1.4 then back to 1.0 as recommended by ML. I'd like to REC longer than 12 seconds if possible. I had the bit @ 0.9 and that didn't work either.
If I reduce resolution what do you recommend I reduce it to? Just go back to full HD? Then whats the point of ML to begin with?
As always thanks
The settings you posted will not produce MLV. Therefore I'm suspicious about your settings before and now.
Basics about MLV processing:
Magic Lantern Forum » Using Magic Lantern » Raw Video » Raw Video Postprocessing
I recommend that you experiment with your equipment to find out the resolution supported by your equipment for the duration you want.
Faster card will do better.
EDIT: Just tried to record 1728x972 with a card specified for 60 MByte/s (SanDisk Extreme 32 GB). Stopped after 19-21 seconds.
Sometimes After processing MLV's with MLV Converter (MLV to DNG) i found that some frames got skipped anyway also half of a frame was kinda like raw gray noise applied to it.
i'm preparing for a shooting , and i feel Raw is a bit unstable to work with , last thing i want to happen is to find out afterwards a footage is not usable.
any suggestions? part of it maybe because of my card but it could handle a scene up to 7 seconds.
Also any difference with shooting Raw and MLV?
i couldn't find about it in FAQ or User guide.
7 seconds in which resolution?
MLV: http://www.magiclantern.fm/forum/index.php?topic=7122.0
Since the card is a bit slow i always change the Aspect ratio to a tighter version other than 16:9
it's not always the same but i'm sure it's not the full resolution.
Thanks for the link by the way.
Isn't there any 7D owner plans to buy the new Mark II?
I opened a new topic (http://www.magiclantern.fm/forum/index.php?topic=13746.0) for that camera on the other day but nobody interested in.
Maybe here I can find somebody who already own one.
(My old 7D has about 150k expo and I'll go to Costa Rica for three months and I don't want to risk a dead shutter during my stay there so I've decided to buy a Mark II before I go there.)
Thought about it but other money sucking projects (not related to photography) have priority right now.
But if there is a developer wanting to get hold of a 7DII: Crowdfunding will help and I promise to participate.
My shutter speed options don't allow for 1/48, 180. I can either choose 1/45 or 1/50. Using the latest build. How can I set to 1/48?
You can use the shutter finetune option. Truth is, you never really could chose 1/48 by default, the display was just round it up, but now it shows actual shutter speed.
Shutter fine tuning doesn't works on 7d ! -> http://builds.magiclantern.fm/#/features
When i try the Focus stacking feature on my 7D it stops working and shuts down the camera (latest build)
Anything i need to check?
Also i found that when when i try to go on the crop mode in Movie mode (5x crop)
i cant go back unless i switch to photo mode and come back
which im pretty sure im missing some settings but i dont know which one?
Delete ML directory and AUTOEXEC.BIN and copy extracted nightly build contents to card.
Try again.
did it , works like a champ.
thanks!
when I shoot videos without magic lantern on my 7D I take h.264 files. those files are 1920x1080. is it the true resolution? why when I shoot MLV RAW the max resolution is 1728 x 972 instead of 1920x1080? thx
And here we go again:
Canon's H.264 implementation for full HD is actually upscaled liveview resolution.
Except 5D3 where liveview is true full HD.
-> Search function, please.
Look for crop mode, too.
why the hell Canon sell 7D and tell to anyone it's Full HD when it is not? is not this a fraud? someone complained to the authorities? :'(
which is the true resolution of the liveview? thx
Quote from: Brawl on November 09, 2014, 03:39:53 PM
why the hell Canon sell 7D and tell to anyone it's Full HD when it is not? is not this a fraud? someone complained to the authorities? :'(
Full HD resolution = 1920x1080. That's the specification and it's met.
If you think it's fraud because internal generated lower resolution got upsampled to achieve this: Look for a lawyer willing to go to court.
I have got my 7D after years of savings, got a preowned one. I have money problems and I cannot pay the lawyer if I should. I do not have even the receipt of my canon. :'(
I hope that not always what is unfair remains unfair. this is misleading advertising. canon lied for selfish purposes (and I made free advertising to them for years, I recommended it to my friends of buying a canon). I feel stupid.
Canon won't be the only manufacture doing this. So you should probably start a class action lawsuit against the industry. There was once an discussion on doom9 about what constitutes full HD, resolution alone, or some image quality also.
In either case, we like Canon, so please start your lawsuit elsewhere.
@Brawl: Sorry, but what is *your* problem with Canon's native video output?
I dunno friends, really. Maybe I just feel a little bit teased. You know when you want to buy something new, and you weigh all the pros and cons of the devices that you are looking for?
for example the DSLR X have better ISO. the DSLR Y have better lenses. so you spend years to weigh all the features. then if you can you buy it?
now imagine that if, after years of weigh and balance, you discover that the company lied over one very crucial feature (example fake 1080p vs true 1080p screen resolution and sharpness). I imagine that well you would think that you wanted to weigh this crucial differences before buying it. I like canon. but perhaps the true 1080p would make me buy another Canon model. or another brand.
7D video recording is sub-HD canon had to tell to us but they wrote HD on the box of the camera. this is what I think. I do not think to lawyers or class actions.
They didn't lie. The 7D delivers full HD output.
Anyway, this topic is not suited to the direction you are taking it. Feel free to start a thread in general chat, if you must.
Bigger shocker... the sensor isn't even 16:9, its 3:2. Actually "fuller" HD, 1728x1152. If you want wide vs tall do 2k and like 928 in crop mode.
Hello there i want to know how make the frame High frame size like 1920 ... and i have Damaged frames ... may CF card 128GB 120mb/s
I want shoot 1920 x 720 without Damaged frames ... i am new with ML .. Help plz
try to install the last nightly build, the compact flash valor is in Mb or MB? it's different.
That damaged frame is kind of a bummer since it doesn't happen on certain part of a shot to avoid.
and sometimes it happens (for me mostly happened when camera was moving either handheld or slider , etc)
Sample : (http://imageserver.ir/502/MLV_A001_272145_C00017.000063.jpg)
I figured it could be due to a average speed of my card (Sandisk Ultra 50MB/s)
then i tried it with a slower card to see if i could increase the chance of this and to me it seems like it still happens occasionally.
Again reinstalled ML and problem solved itself.
I can get a roughly 7 to 8 seconds with a 45MB/s (Advertised) Memory card at Full Res and 2:1 Aspect Ratio
which is really useful considering a project with short takes and cuts.
I wanted to know that is this due to the 7D's High SRM memory value or something else?
I am considering a switch to 5D Mark II for better low lights and some extra features (ML+In camera) but i wanted to make sure about this first.
Any advice is welcome!
5DII also has the same shitty sync functions as 7d. You're just going from a 2 proc camera with crop sensor to a 1 proc camera with an FF. You can still get bad frames there. The only things that mitigate bad frames on this generation are faster cards and less doodads turned on while recording.
About faster cards: Komputerbay 1066x 128 GByte. Received this week and therefore still experimenting.
ML benchmark shows about 90 MByte/s (write).
1920x960/25 good for about 30 sec. 1728x972 (16:9) is good for about 23 minutes = card full.
Have to compare 1920 out of the cam with 1728 upscaled.
Quote from: 1% on November 16, 2014, 10:18:19 PM
5DII also has the same shitty sync functions as 7d. You're just going from a 2 proc camera with crop sensor to a 1 proc camera with an FF. You can still get bad frames there. The only things that mitigate bad frames on this generation are faster cards and less doodads turned on while recording.
I was going to switch for a better low light performance (1 and 1/3 of stop) and some lens options. (I do photography mostly)
Those damaged frames didn't happen for me after re-installing.
but i don't get what do you mean "Sync functions"
While we're on memory:
last night a camera store that i go to gave me a new card to Test (Sandisk Extreme 32GB 800x)
Using the formula (Speed as X / 1024 * 60) which for this one goes about 45MB/s was actually accurate , ML benchmark showed the same.
I could record 1728x972 (16:9) MLV for more than 20 seconds which is enough for me w/o any skipped frames and it looks good.
BTW I had a question for a while , Is there a way to record MLV's on higher frame rates for slow motion?
FPS override doesn't go up when i'm on 1080 on Canon's menu.
And it's cropped on 720.
QuoteML benchmark shows about 90 MByte/s (write).
How fast does it write while recording? The 64gb previous gen Komputerbay cards were continuous at 1728x972 or 1728x1156 @24P. ~82 MB/s writing.
QuoteIs there a way to record MLV's on higher frame rates for slow motion?
Nope. The live view can't get that fast. You can override the 60P modes to 48fps though. Or 50P if you're on pal.
Quotei don't get what do you mean "Sync functions"
How ML overlays/display filters (ie ML preview)/etc are synced up with the LV image. These functions take more CPU and are less reliable on this generation of DigicIV cameras. The magic zoom actually relies on making the CPU busy to slow it down enough to not flicker.
Quote from: 1% on November 17, 2014, 04:38:24 PM
How fast does it write while recording? The 64gb previous gen Komputerbay cards were continuous at 1728x972 or 1728x1156 @24P. ~82 MB/s writing.
Test 1:
1728x1156@24, MLV, no other modules loaded, just default but GD turned off.
Manual stopped after 2 min. File size 9,38 GByte. Equals to 80 MByte/s. I recorded the cam's display with a second cam:
https://www.dropbox.com/s/49hlm2sopbdyszv/MVI_4990.MOV?dl=0
As you can see the write rate is quite "nervous". I have no problem to fill the card with this resolution/frame rate.
Test2
1728x1156@24, RAW, no other modules loaded (only RAW_REC), just default but GD turned off.
Stopped by itself after 2:42 (but have had breaks after about 1:30, too). File size 12,6 GByte. Equals to about 79,65 MByte/s. Here is the record:
https://www.dropbox.com/s/b784hxoacytr4x0/MVI_4991.MOV?dl=0
Write rate is quite good dampened, it seems. The rate displayed, I mean.
If there is anything else I might be able to test: Here I am, willing to take some risks if it might be helpful to free the beast (aka: 7D).
So it still seems a little slower than the 64gb 1000x but not by much.
Nothing really new on the 7D side. There is the black level fix PR and I wonder what that will do to write speeds. It doesn't work for crop mode though.
Quote from: 1% on November 17, 2014, 04:38:24 PM
Nope. The live view can't get that fast. You can override the 60P modes to 48fps though. Or 50P if you're on pal.
What about other bodies?
Quote from: 1% on November 17, 2014, 04:38:24 PM
How ML overlays/display filters (ie ML preview)/etc are synced up with the LV image. These functions take more CPU and are less reliable on this generation of DigicIV cameras. The magic zoom actually relies on making the CPU busy to slow it down enough to not flicker.
I See , although personally i didn't have a issue with GD at least , Seems synchronized to me using Zebras Under/Over , Focus peeking , Magic zoom etc.
Quote from: 1% on November 18, 2014, 12:01:40 AM
Nothing really new on the 7D side.
What about an old one? ;-)
Bringing Soundrecorder/Voice tag into the main branch?
There is the new audio system branch and a module that has a wav rec. I'm checking it out on EOSM (so far: headphone, on/off and volumes). It definitely needs polishing (i.e it doesn't set settings at rec start and only alters digital volumes) but its a start. I always had classic recording patched up on my 7D stuff so never really noticed it was missing.
Now for something completely different:
Well, I just opened a support issue on Canon's official support site and asked about adding ExFAT support to 7D. Call me a naif but it has been added to some cinema gear via firmware update. And it doesn't hurt to ask ...
So: If you have some time to spend, you may chime in and open your own support issue and ask Canon to do so.
I expect "smother" operation (=less likely to stop when 4 GByte block is reached) with ExFAT in 7D.
@Walter: good idea but... if Canon will release another fw, ml will have to update to it! It is not for the last... imagine how many time it will require for another one... eheh!
Quote from: Walter Schulz on November 22, 2014, 10:25:38 PM
Now for something completely different:
Well, I just opened a support issue on Canon's official support site and asked about adding ExFAT support to 7D. Call me a naif but it has been added to some cinema gear via firmware update. And it doesn't hurt to ask ...
I'd love to see this happen as well, but with it being discontinued and all focus on the 7dmkII now, I don't have high hopes.
Sometimes image appears to be darker in live view which is most of the time for checking accurate exposure.
I have Exp Simulation:on too.
http://www.magiclantern.fm/forum/index.php?topic=12096.0
Hey guys, i have a 7D since 3 days and a 128GB 1066x Komputerbay. And i have a few questions.
1. how do i set up the camera for best performance Raw rec. which buffer fill method, which resolution,warm up,......?
2. how do i set up the camera for mlv rawrec, i wasn't able to figure out how to shoot in mlv, it just shows that it is preparing when i hit rec button and when i want to stop or sth. else it doesn't response to my actions, so i have to remove the battery.
3. when i rec. in crop mode, even at 1080 i get loads of pink frames. not really important which resolution, pink frames everywhere :D
4. Do i have to make any changes in the canon camera menu to increase the performance of ML, or just those settings like disabling auto off,.......
please help, thanks.
Btw, any news on Dual ISO MLV on the 7D?
http://www.magiclantern.fm/forum/index.php?topic=13597.msg131347#msg131347
Thanks
Btw, anyone else experiencing random crash when recording MLV with Dual ISO enabled?
I was taking photos while occasionally shooting MLV and sometimes the camera would just turn off with the top LCD displaying ERR with no crash log.
I'm curious: You just thanked jman for linking the thread about 7D's incompatibility with Dual-ISO video and now you're asking about crashing with this non-working feature enabled?
I Took some Dual Iso shots with the latest version , i think due to updates the old software i have can't process it (Cr2hdr)
Could someone link me if there is a new one?
Thanks.
What about searching the Dual-ISO-postprocessing thread?
Quote from: walter_schulz on December 05, 2014, 04:59:48 PM
What about searching the Dual-ISO-postprocessing thread?
None led or confirmed me of a new one to download.
Can you upload an unprocessible file?
Quote from: Walter Schulz on December 05, 2014, 06:37:57 PM
Can you upload an unprocessible file?
I'm not sure if that's the right word to put it.
It's like , before i selected the files and drag'em to cr2hdr.exe and it did its thing.
but now the command just get stuck!
Btw my network is kind of unstable right now to upload/download a file , messages should come a bit late too i guess.
Sorry, but I have to sum up.
There is an error and you haven't gave any details yet.
You haven't tell us which versions you're using.
You haven't specified which updates you are referring to.
You haven't provided a file to reproduce your error.
No offense but what do you expect?
I thought asking more questions was implied...maybe not. :-\
Anyway i think the problem was that one of the images i was dragging to the App was a normal image
that caused an interruption or something.
Hi all,
Sorry for the noob question. I have recently installed ML on the 7D, I'm trying to shoot RAW but the files don't seem to be saving to my CF card as .RAW files. It plays back ok in-camera. I've gone through step by step in setting up the menu's etc. Am i doing something wrong??? One other question, is it possible for the crop marks to say on whilst recording? I've noticed they disappear.
Thanks in advance.
That's because you're using MLV_REC and therefore generating MLV files which have to be processed as such.
http://www.magiclantern.fm/forum/index.php?board=54
And cropmarks will disappear because this is default for MLV recording. Movie tab -> RAW video (MLV) -> [Q] -> Global Draw OFF -> ON
Thanks! If I can ask one more, also having trouble with hdmi out from camera. Our monitor reads no signal. Thanks.
Can't find magic ball in this mess ...
Hahahahahaha! Walter is having a GREAT time! :)
Ok so i'm shooting at 1728x736 in an 2.35:1 aspect ratio. The card i'm using is an SanDisk Extreme 16gb @ 60MB/s. ML tells me I need 50MB (so I'm sweet there). Everything records fine but once i extract the dng's from the raw file i notice single frame glitches in pink (i'll post a still). Is this my doing? The card? Shooting size? Also when i stopped recording i get an audio error message. "couldn't stop...state 4" etc. Might need some help. http://postimg.org/image/orqmvza0l/
I think u need a faster card.
Sounds like the limiting factor due to the card speed...
Get a fast card. Then go buy one that's faster. Then go buy the fastest.
Just tried my Sandisk Extreme 60 MByte/s 32 GB with 1728x736@25fps. MLV_REC loaded but no other module. Global draw off but cam icon visible. Because ML's benchmark test indicates the card does better when warmed up I used a 1 GByte warm up run and started recording just after warm up. Cam stopped when storage run out. Quite often/a long time after start the cam icon turned yellow.
But this doesn't tell that much about your card. Controller chip may be different.
Thanks for the feedback guys, I'll have a play around. :)
Lexar 1000x or up, I can top out at a near steady ~82.3 MB/s in 24p crop mode legacy raw format sometimes, no GD, sound or any other processor hogs running. MLV is only a second shorter usually, as far as recording times go. I believe that there is still potential inside the 7d somewhere to perform even better, but it's going to be quite a while before we find out, if ever.
Are u using the latest ML version? With Komputerbay 1000x im getting all good, green icon on the screen.
Sorry, please clarify. What are we talking about?
@N/A: 82,3 MByte/s comes from? ML telling the frame rate? Numbers beyond camera icon? File size/duration?
@arrinkiii: Sorry, this doesn't tell anyone anything. Numbers and configuration, please.
(http://s28.postimg.org/7vngt72el/20141219_074145.jpg)
My apologies, I should've clarified. The settings for this screenshot were ntsc 30p with override set to 23.976 fps, sound off, gd off, iso 400, 1/50, f2.4. Expo override on. Raw video (not MLV), 2496x1044, HaCKeD preview, indicator on screen. Srm mem on, extra hacks on, card warmup on 256 MB. Only 6 modules loaded.
Fresh format, warm card and cold camera, I think this was my highest write speed yet.
That file was 346 frames, ~15 seconds.
And on a separate note, trying to take an in-camera screenshot while recording that resulted in a mem error under the ML menu, and no screenshot was saved.
I'm just beginning to experiment with high bit rates on my 7D and at the moment I only have a single card to play with. It's a Komputerbay 1066x 128 GByte.
I don't know how the number below duration is calculated. Behaves quite different in RAW vs. MLV, BTW.
If I compare the calculated number (shown by ML when choosing resolution) with "data file size"/duration match is very good.
Just tested crop mode
[email protected] (ML calculation 83.6 MB/s in yellow) which stopped "magically" after 4:08. Green cam displayed, BTW. File size is 20.3 GByte which gives about 83.8 MByte/s. Few frames with colours out of order.
RAW_REC, no other modules, global draw off.
Movie settings in Canon menu: NTSC, 1920x1080@24.
Have to experiment a bit more but I suppose somewhere between 80 and 84 MByte/s recording duration is going to be unreliable with this card.
Komputerbay 1066x 128 GB
(http://picload.org/image/cllilgd/bench0.jpg)
(http://picload.org/image/cllilgc/bench1.jpg)
I know benchmarks and real life performance aren't that much related but I'm indeed a bit confused about the benchmark numbers in movie mode. I'm able to use data write rates around 80 MByte/s with RAW_REC but benchmark numbers are lower by quite a margin.
Is this a 7D specific issue?
Second one: I'm not able to access photo mode benchmark. When benchmark is started (no liveview, not video mode) it will enter playback mode regardless if play button is pressed or not.
I don't think my benchmarks have ever broken 100 MB/s, impressive! I think my movie and playback benchmarks were pretty similar to each other, I'll check on that. When you run benchmark in photo mode the speeds are most accurate in playback mode I believe, I thought it was strange as well that a picture displayed while benchmarks were running but it's normal, afaik.
AFAIK, in playback mode there are a lot of Canon tasks that aren't running, so more resources can be devoted to reading/writing to the card. This approximates what raw recording does when it's running (disables/slows down lots of Canon tasks, so itself has as much priority as possible). That's why numbers are much better in playback mode.
Canon 7D Raw footage. Testing Magic Lantern ver. Nightly.2014Oct08.7D203 on Canon 7D: http://builds.magiclantern.fm/#/
Original footage res. 1729x 972 and 2240x1200 (5x zoom on Live view) using 24-105 mm Canon Lens.
It took me 32 GB for presented video. CF 64GB-600x speed.
No color grading when editing. I add a little clarity and sharpness.
7d RAW x5 test shoot, I'm impressed. 17-40F4L and 100F2.8L with Lexar 32gb 1000x CF, minor adjustments in Camera Raw
http://youtu.be/6zEfa8o4GV8
VOW. One of the best 7D footage I ever seen!!! Man, this is great. Are all footage in 5x? Could you please describe your settings & how many frames/shot did you manage? Thanks.
Still not quite sure what ur question is... Clarify some more, if possible?
Any news on the port to 2.0.5? What's the main issue?
Main issue: Someone has to code it.
Do you really need to use 2.0.5?
Maybe not, but I don't like downgrading something.
I could try and help (I'm in computer science), but I don't know what the status is and how to move forward :/
7d 2.0.5 development-
https://bitbucket.org/Pelican/7d.205 (https://bitbucket.org/Pelican/7d.205)
QuoteVOW. One of the best 7D footage I ever seen!!! Man, this is great. Are all footage in 5x? Could you please describe your settings & how many frames/shot did you manage? Thanks.
All in 5x, 23.9fps, 1/50th of a second for everything with about 270-305 frames before automagically stopping. Seems like 15 seconds is the max so far.
Has anyone had a look at 2.0.5 yet?
https://bitbucket.org/Pelican/7d.205
Your mileage may vary but I don't need any of the improvements coming with 2.0.5. Do you?
To be honest I haven't even looked into what improvements were added. I'm pretty happy with the latest build so far.
http://www.usa.canon.com/cusa/support/consumer?pageKeyCode=prdAdvDetail&docId=0901e02480a9f038
Only (official) item:
=====
Firmware Version 2.0.5 incorporates the following fix:
Fixes a phenomenon in which the image files cannot be transferred using the FTP protocol via USB cable after the Canon EOS 7D camera has established a wireless connection to the Wireless File Transmitter WFT-E5A.
=====
I see no urge, really.
Due to its price, Very few people are using that Grip anyway.
Agreed, It is rather pricey.. Thanks for the info Walter.
I'm happy sticking with 2.0.3 w latest build...
Happy new year guys and gals!
I found 2.0.5 to produce sharper images, I downgraded to run ML which seemed to cause soft-focus on my 7D, but the benefits of ML are worth it... Maybe just me though.
Please post images from each fw for comparisons between 2.0.3 & 2.0.5 @Spooke!
The "soft focus", have you checked if the 7D is forward or back focusing?
Hello. I am new to magic lantern and i am having trouble finding settings on my 7D. How do I access raw video for instance?
Module tab. Restart. Movie tab.
I have a 7D but was always afraid of trying ML out. I finally got the courage to install it. But I've got a problem. I have a 133x card (I know its too slow but I'm plan on upgrading).
The firmware installed fine (latest nightly build). I enable raw video module. I hit the record button. Stop record but the recording doesn't stop. So I just switched the camera off. After I shut down the camera, the led blinks for quite a while (about a minute).
I connect the card to my pc to check the files recorded, the only file I find is a 300mb .tmp file. Thats it!
What am I doing wrong?
Thanks.
133x card is too slow to write the raw frames on your CF. Remove card and switch ON the camera. It should boot. My suggestion, determine the card write speed first and then try the modules.
Thanks. It boots. I have removed ML. Is there anyway I could test the raw capability with 133X before buying a better CF card?
Sure. Take very short clips in high resolution or longer ones in low resolution.
But the problem persists. When I press the rec button the recording does not stop. And later I have to raw files in my CF card.
maybe you shouldn't double post, and check my reply to your other thread
http://www.magiclantern.fm/forum/index.php?topic=14261.msg137238#msg137238
Sorry for the infringement.
Hi
Is there any known situation like this?
1. Camera off
2. take the CF card out of camera
3. leave camera off and without CF card about 4 or 5 hours
4. the battery will be total empty
I can repeat this. If I remove the bootflag and run camera just on Canon firmware it works OK (the battery level stays the same).
Anyway ;)
Best Regards
I LOVE ML
Quote from: Mare on January 09, 2015, 12:49:38 PMIs there any known situation like this?
Yes. You may use search button above (left side) and look for battery drain.
If following proper procedures still drains battery: Please tell us which ML version (date) you're using.
hello guys I wanted to ask which is it the right session of the forum to post magic lantern bugs? I wish to do not do cross post bacause I already started a topic in "General Q&A". But iI need people to do a little experiment and there nobody reply me.
Maybe I posted in the wrong session and I had to post here? I had problems with Nightly.2014Oct08.7D203 and Nightly.2015Jan03.7D203. I really need for you guys to try to reply my actions on your camera, bacause I wish to understand it this bug is for all, or only on my camera.
Can I ask to a moderator the permission to do a little "cross post" for once? If is not possible I will edit this post.
the bug should be in the "movie tweaks/ movie restart" option, bacause if I turn it off the bug stop. if I turn on again "movie restart" the bug come back.
this is a video of the problem.
https://www.youtube.com/watch?v=8UNjAuBY0Do&list=UUSXF-xJlFBpj52lhmKXcO_A
can you do the experiment and post the result here please?
I wish to tell that with the Nightly.2014Oct08 the bug was not present with a fresh installation, it come out only after using the camera for a while (expecialy if I used ML Raw video and then come back to h.264). So I had this bug after one or two weeks, where the option "movie restart" was always ON, and I switched from RAW video to H.264.
Different story with the new firmware Nightly.2015Jan03, here the bug started since the first power on of the camera.
really thanks a lot for help if it's possible! :)
My Mark II drains the battery at night even without ML installed...
I've never used the On/Off button since the 20D and not happy if I have to do it from now.
It's not the GPS, maybe it is just need more power than the 7D.
I haven't made a proper test, but almost every time I want to take photos I have to change the battery.
Anything about this on the net yet? I have a workaround for you so you don't have to use the switch: Take the battery out.
Duck&running for cover very fast
Hi
I'm testing latest build 2015Jan03 and the same is with Nightly2104Oct07. I just remove the ML bootflag and than is everything OK, no need for removing the battery.
Problem is known. But only if proper procedures are ignored. Remove card just after shutting down -> ML will not shut down properly and drain the battery. Wait for some seconds (-> wait for LED inactive) and CF card removal will not drain battery.
If you waited for several seconds after LED went dormant: Problem to solve for devs.
Until now nobody was able to reproduce such errands.
Lately I also have noticed that my 7D seams to hung (and drain battery) when I remove the card even If that was done in a while after, like after shooting camera has been in bag switched off and I remove the card when I'm at home. I have not been able to find what settings / modes are the cause, but it happens once in a while, so I now always when I remove the card switche the camera on, if it starts, grate, of not - do the battery reset.
An idea, can the red led been switched on until camera really switches off?
As I wrote earlier: Until now it was not possible to reproduce such errands.
If you are able to do so and offering a procedure reproducing this error for us: Fine! We're listening. If an error is reproduceable it is likely to get fixed.
Quote from: Brawl on January 09, 2015, 01:49:03 PM
can you do the experiment and post the result here please?
Reproduceable in 2014Oct08 and 2015Jan03:
Run H.264 recording and turn Movie Restart to ON and you will not be able to stop your record by pressing record button.
Fine with module RAW_REC.mo loaded and RAW recording ON.
Tested build 2014Aug20, too. Same error.
Tested build 2014Apr29: Running fine!
EDIT: Last build without bug: Build #148 (23.06.2014 00:30:54)
First build with bug: Build #149 (25.06.2014 00:30:55)
650D build 2014Oct07 is running fine.
EDITEDIT: Issue 2173 (https://bitbucket.org/hudson/magic-lantern/issue/2173/movie-restart-h264-recording-wont-stop) opened.
Thanks a lot for testing Walter awesome job!! :)
But I was not that awesome checking open issues:
https://bitbucket.org/hudson/magic-lantern/issue/2065/movie-restart-7d-stuck-in-loop-cannot-stop
So this in fact has been fixed?
Because I have been using the Playback button to get myself out of the loop or if I don't need to record more than the limit time then I usually just disable it.
But for the most part it definitely comes in handy, for obvious reasons!
@DeafEyeJedi not yet.
@Walter I didn't know it, I posted my video also on Issue 2173 I hope it will be fixed. Do you think is dangerous to do a work with this bug (using movie restart)? Do you believe there is the danger to lost my data? I use so much "movie restart" for work is often essential (it was the first reason why I installed ML).
I really wish to do not downgrade my ML firmware because I wish to use the most updated ML RAW video module. I do not know if it's me but with the lastest version I had better performance with my 60mb/s 16gb sandisk card, I can now record MLV at max resolution no crop mode (for about 23 seconds then it stops). I hope to have the money for a bigger card soon to make some job with it. I'm studyng Lightroom and DaVinci to understand how to grade it. It's awesome. :)
@brawl -- Confirmed, Yes it is in fact true that performance wise of the ML core from Jan 3 build has somehow given both my 7D & 5D3* (haven't tested others yet) the capabilities to push it a few more MB/s in MLV/RAW recordings than in previous nightly builds.
*EDIT: This was all done in 1.1.3 for 5D3 -- haven't confirmed yet for 1.2.3 but others can welcome their experiences.
I was checking out Silent Picture module and realize Full Res is not there , is this feature for 5D MK III only?
In development
It was a while that i didn't shoot a video with my 7D , i got a slider and gave it a shot.
Turned on the MLV Raw at Full res (though at 2:1 Aspect ratio) did some test and what i encountered was
the footage going back and forth in some frames , imagine if frame number 50 for example goes between 20-21.
This is probably more likely due to post process i did after but
I thought maybe this is related to camera so i posted it here.
Nightly #181 , FPS override turned off , yellow camera icon indicator during the shooting.
Workflow: MLV converter 1.00 > Output DNG > Import in Lightroom > simple processing > Export Jpeg > Premiere CC as Seq
Problem can be seen while i hold down right arrow key in lightroom's library.
PS: In case you're interested in the slider, it was a very cheap though nicely built Kamerar 47" Slider , Smooth and easy to use.
Tiny update... : )
Has anyone ever used Digital Dolly successfully on 7d? When I have it enabled under MLV menu, it doesn't move at all in 5x view, and when it isn't enabled moving the joystick while recording crashes the camera and I get the following log-
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTR_LV, NULL, 0 ) )
at LVState.c:485, task ?
lv:1 mode:3
Magic Lantern version : Nightly.2015Jan29.7D203
Mercurial changeset : 703ee626326d (unified) tip
Built on 2015-01-28 23:30:43 UTC by [email protected].
Free Memory : 263K + 2568K
want to know the dangers of using ML on my 7d? has anyone had problems or bricked their camera?
See FAQ and disclaimer found in download page.
Quote from: N/A on January 29, 2015, 10:04:12 PM
Has anyone ever used Digital Dolly successfully on 7d? When I have it enabled under MLV menu, it doesn't move at all in 5x view, and when it isn't enabled moving the joystick while recording crashes the camera and I get the following log-
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTR_LV, NULL, 0 ) )
at LVState.c:485, task ?
lv:1 mode:3
Magic Lantern version : Nightly.2015Jan29.7D203
Mercurial changeset : 703ee626326d (unified) tip
Built on 2015-01-28 23:30:43 UTC by [email protected].
Free Memory : 263K + 2568K
Anybody want to double-check this for me so we can know it is an issue and not just my camera? If it is an issue I'll submit it to the bugs page.
Confirmed.
Tried with 2014Apr29, too. Dolly didn't work either but it won't crash when Digital Dolly is disabled and joystick is used.
EDIT: Last one not crashing in crop mode with Digital dolly = OFF and joystick used is Build #147 (21.06.2014 17:03:04).
Quote20. 5D3/5D2/50D/7D: refactored joystick menu navigation with GUI timers (and enabled it on 7D) (detail / bitbucket)
in #148 but IANAD
Ok, submitting bug data now
Hi!
I'm new to Magic Lantern and I'm most likely posting on the wrong thread. Please guide me to the correct one if so.
My question is about whether the Canon 7D Mark II camera is supported, or is it only for the 2009 basic Canon 7D that is being discussed here?
Thanks.
7D as in "7D". 7D Mark II not supported at time of writing.
Had the same problem with the Digital Dolly and I (and another user) wrote here in August '14, nobody has replyed :o
I'm happy that now someone else have also saw this bug.
So, I seem to have made a dumb mistake. I got asked to do some realestate video, and figured the HDR video function on Magic Lantern would be a great way to go about doing this. So I went out and bought a 7D.
Now it seems this is not possible with the current firmware. Woops. Does anybody know if this function will be added? Or should I just go ahead and try to trade it for a 60D. (7D vs 60D, what else should I know?)
Thanks!
Feature matrix (https://builds.magiclantern.fm/#/features)
A detail not visible in that list: 50D and 7D are - at time of writing - not able to do Dual-ISO in video mode.
For the record, HDR video and Dual Iso video are two different features, HDR video uses 60p h264 video at alternating iso's. But neither are available for 7d.
Not sure if this one is reproduceable out there.
magiclantern-Nightly.2015Jan29.7D203
MLV_REC.mo is the only module loaded.
MLV 1920x960 and FPS override set to 24. (Actual 24.028)
Tried 2 runs and recording stopped after 9:17 both times.
Recorded <filename>.MLV - <filename>.M08 (10 files each set) with 39.9 MByte.
First set size: 42,888,790,016 Bytes
Second set size 42,862,936,064 Bytes
Stopped with message "Failed to open file. Card full?"
Will not shut down. Had to remove battery and modules won't load because of shutdown problem.
Card: Komputerbay 1066x 128 GByte
EDIT: Checked RAW_REC.mo and had no problem to fill the card.
Somebody out there having similiar issues? What is going on here?
How did you manage to load ml on a 128gb card with 7d? However kb cards are known to be slow and or defective in sone parts. A full scan of the card with verificatoon tools is recommended
Quote from: dlrpgmsvc on February 19, 2015, 08:39:45 PM
How did you manage to load ml on a 128gb card with 7d?
Why should there be a problem? This is not "stable" and nightly works just fine with bigger cards.
Quote from: dlrpgmsvc on February 19, 2015, 08:39:45 PMHowever kb cards are known to be slow and or defective in sone parts. A full scan of the card with verificatoon tools is recommended
The card is just fine. Tested with h2testw.
EDIT:
To all with a card 64 GByte (or bigger) and fast enough to write at least 30 MByte/s. Please select resolution and frame rate to adjust data rate above 25 MByte/s (or higher the better). If your MLV recording stops and message "Failed to open file. Card full?" is shown check file set size. Is it just 39.9 Gbyte?
And if recording doesn't stop before card is full: Please report back, too!
Did you set your card to eXFAT?
I would love to do but 7D doesn't support ExFAT.
"What is going on here?"
This?
http://www.magiclantern.fm/forum/index.php?topic=12686.0
Yes, that's it. This one surely flew under my radar.
Thanks!
I don't suppose you could make that change?
Not a dev, sorry!
Well the change itself is very easy.
But an more appropriate fix would be one where MAX_PRECREATE_FILES is defined based on card size. This fix could then be included in the nightlies, rather then just defining some large number that is only appropriate for large card sizes.
I'm not sure how ML determines card size (if it even does), and I don't currently have the time for research.
It would be neet to have this solution :o
"rather then just defining some large number that is only appropriate for large card sizes."
I think the large number is actually appropriate for all card sizes. At least, it won't do any harm to someone using a smaller card. Those files take up virtually no space until they are filled.
Quote from: Frank7D on February 21, 2015, 09:58:06 PM
I think the large number is actually appropriate for all card sizes. At least, it won't do any harm to someone using a smaller card. Those files take up virtually no space until they are filled.
Are the files currently deleted automatically if not used (recording stops early, whatever), or do they remain on the card? If they are deleted when recording stops, I agree, having a larger number would seem preferable. If this is the case, I'll find some time to make the changes, test quickly, and make an pull request for the nightlies.
They are deleted unless recording stops unexpectedly.
Here is a build for the 7D with MAX_PRECREATE_FILES set to 32.
Please test and report back.
Testing done, build removed.
Quote from: Walter Schulz on February 19, 2015, 09:37:32 PM
I would love to do but 7D doesn't support ExFAT.
D'oh! Thats's right. Haven't used the 7D as of much lately.
Thanks, Audionut!
I will test it tomorrow.
Is it possible the CF card R/W benchmark is inaccurate on the 7D? I'm getting read speeds of 35mbs and write speeds of 50mbs on 1066x cards, but when I actually record in RAW it works flawlessly and says it is writing at over 70mbs.
Press Play button after starting benchmark to access playback mode.
What does that do?
oh now it's writing at 90mbs and reading at 57 so that's good, why does it work like that?
In play mode there are a lot fewer Canon tasks actively doing stuff, so there's more resources available to the benchmark code.
This is on a 128gb card, i just read up there that exfat doesn't work, but the menu shows 120gb available? and i think i formatted as exfat. Is that not actually how much I can use?
Doesn't have anything to do with ExFAT or FAT32. Please check your file system again.
120 GiByte = 128,849,018,880 Byte
Storage manufacturers are using
kilo = 1000
Mega = 1000 x 1000
Giga = 1000 x 1000 x 1000
Computers use
kilo = 1024
Mega = 1024 x 1024
Giga = 1024 x 1024 x 1024
Right i just mean i heard that 7d can not use more than 64gb but it appears to work - is this actually true?
I'm sure it is true you heard that.
No one yet have try the solution from Audionut regarding the limit of 30 minutes?
PS - Im away from my camera until next week.
@arrinkiiii
The solution from Audionut is for allowing more than 10 "chunks" of mlv/raw video (it allows 32). The amount of time you get in those 32 chunks will depend on frame rate and frame size. I am testing Audionut's build now.
Using Audionut's test build, I just finished shooting as long as I could on my 128 GB CF card with 1280x720 @ 23.976 fps.
I filled up 29 placeholder files plus part of a 30th.
I realize now that my math was off when I calculated 32 as the max number of files for the 128 GB card. In GiB (as opposed to GB) the card has a capacity of 119.21 instead of 128, so 119.21 / 4 = 29.8 files instead of 32.
I think the build is fine as it is though, since it's okay to have more placeholder files than you need, and card capacity will only go up in the future.
Works for me, too. No problem recording +80 GBytes.
g3gg0 pushed some fixes for MLV that should fix PRE_ALLOCATE problems also. Can you guys please test the latest nightly and let us know.
Looks good. +40 GByte recording works with 7D and 650D.
https://builds.magiclantern.fm/#/features
7D column:
- No mark on HEADPHONE_MONITORING but a mark on HEADPHONE_OUTPUT_VOLUME?
Robot error?
Hi all. A simple question. It is possible right now shoot RAW in 7D with a external monitor plug in?. Im working in some complex shoots and i need the help of an focus assistant.
The last time i tried it, i get a lot of pink frame and some buffer problems (the clip ussually stops reccording in just a few secconds).
Thank you so much.
PLS HELP !!!
After installation ML, I had high expectations, but unfortunately opposite happened!
My pictures was full of white banding, very strange colors etc...
I tried to uninstall ML a couple of times but it did not work so I decided to overwrite the installation files from the card ...
But disaster ..
After rebooting my 7D was completely dead!
I tried to take out the battery, card, restart ... but nothing ..
Drama ... need help. How do I get my 7D in life?
Remove card, remove battery, remove lens. Insert battery. Startup. Results?
Format card using a card reader. Insert into cam. Startup. Results?
Don't forget to remove battery after testing.
Done ... and it works until I put the card in the camera.
After that, the camera is dead again.
Only when I repeat the whole procedure (without inserting the card) 7D revive.
Unfortunately I do not have another card right now..
What can I do next?
Format card using a card reader. Format card in cam again. Copy extracted nightly contents to card. Run firmware update.
Thank a lot...Now is working...
Pls, link me original WWW to recive ML for my 7D..
Thank U again...
First page, first post.
ok.
Work nice...but one question...
My main reason for using the ML is Dual ISO.
I'm only use photo, not a video.
How to process DUAL ISO images ?... conventional way is not going ...
otherwise, for processing I usually use Photoshop.
-> Postprocessing forum
My canon 7d got bricked when i was trying to shoot 2k using magic zoom. Got this suggestion in the blue screen-
- Go to LiveView and enable DIGIC peaking.
- Take a photo of a calendar, focusing on today's date.
- Try pressing the magic button quickly enough.
Tried this, but the error is recurring. Tried restarting, reinstalling and everything else. But it keeps giving this message.
Please help.
Quote from: mssrihari1 on April 01, 2015, 09:06:04 AM
- Take a photo of a calendar, focusing on today's date.
Probably the photo wasn't focused very well, can you upload it?
I got the error before I even was able to take the photo. :(
Thanks in advance for any help possible.
I got the error as soon as I enabled DIGIC peaking and I was about to zoom in and I see the blue screen immediately.
You are sure you focussed on the correct date in your calendar?
Tried again and got the blue screen immediately after i got the photo. Trying to attach. Not happening.
I'm not sure, but maybe I found a workaround:
Turn on movie mode in 1080p25, make sure to have audio recording enabled (manual mode). Focus on today's date in calendar, activate recording and repeat month's name at least 2 times. Avoid clipping! Replay on computer.
If this is an April Fool Day joke, then I'm relieved!!!! :D
But please do let me know how to fix this.
Now you're focussed!
Change cam's date and your problem is gone.
Of all the days I could have tried this, I had to pick today!
Thanks so much for the heart attack!!! But what a way to open my account on this forum?!!! :D
QuoteMy canon 7d got bricked when i was trying to shoot 2k using magic zoom. Got this suggestion in the blue screen-
- Go to LiveView and enable DIGIC peaking.
- Take a photo of a calendar, focusing on today's date.
- Try pressing the magic button quickly enough.
I got the same message, i did tried the ML before but never have this problem . Now , i have to use the camera without it.
Try again April 2.
(http://s8.postimg.org/w9amyph0h/11134399_448471128636764_774653920_n.jpg) (http://postimg.org/image/w9amyph0h/)
Thought I'd also jump in on this. Had a shoot the other day and this popped up whilst trying to review an image that was just taken. After a reboot the camera was fine and shooting back to normal. I did find it strange that after turning the camera off and removing the battery, the image was still displayed on my external monitor which I turned off also. Running the latest ML nightly.
Hi. I'm using an older nightly build (don't have the exact version at hand, ill get back on that).
There are a few hiccups when shooting raw. For example, no overlays work. If I activate any I get corrupted frames in the material etc.
Is this issue fixed in later builds?
Without any further information it's impossible to answer.
If you're running at the edge of performance slips will occur, that's for sure.
1728x692 48 fps slow mo. But wait a minute... When I play it back, the footage is normal aspect, no stretching required! I'm kinda running on no sleep in 2 days, I need someone to confirm this ASAP. I noticed when I set the cam to 1280x720 60p, and set the fps override to 23.976 exact fps, the liveview display was stretched vertically, so when recording it and playing it back records it in normal aspect! Timer A under 23.976 exact is 422 (FT -76). So I set the fps to 48, and Timer A back to 422. Mlv settings-
1728x692
3:2
GD Off
Canon preview
256 MB warmup
SRM On
Hacks on
4 buffers
Reserve on
Global Draw off
Expo override on
Rokinon 35mm manual cine lens
After messing with it a little bit more, the black and white levels get all wacky sometimes and the exposure is super glitchy. At first, I noticed this while testing out different settings in 640x480 mode, going to do some more tests soon as I charge my battery.
:edit: Yeah definitely a bug in the fps override control. I just downloaded the latest nightly, same thing. How exactly does fps override cause LV to stretch? Or is this a new feature I completely missed?!
:edit2: Ok, just figured out that this bug has been in the nightly since 7d fps override was implemented.
:edit3: To fix this issue, Timer A needs to be set to 498 (FT +76) for 23.976 exact and 440 (FT +10) for 60 exact.
Is it possible to run ML without autoboot like it was working in version Alha 2?
And the benefit?
Faster wakeup?
Another configuration to support and sparce dev time ...
Hi Spameris
You can always update ML firmware in your camera and wait couple of seconds until the bootflag is removed.
Benefits??
I love ML because I often use exposure override (great to work with manual lenses) and other great thinks, ... but sometimes ML have little bugs, so I can use Canon firmware (for example must be some kind of bug in ML firmware with remote flash communication, ...).
You can always have best of both worlds. :)
What about 7D mark II ?
Is it mandatory to wait that a firmware upgrade is released by Canon before starting to look at a ML port on this beast ?
I ask because I ordered mine yesterday to replace my venerable 7D...
I already did some ML dev for the 7D and I'm asking if there is something to look at the mark II to initiate a port before Canon release a downloadable firmware upgrade ?
ML on 7D mark II would be great with such new features as : moire free video "a la" 5D mark III, CF/SD dual slots, 60fps in 1080p, dual Digic 6 processors, phase detection AF in live view,....
Downloadable firmware is not needed to start porting. See 70D thread.
Supposedly mark ii firmware update is coming next week. I enjoyed using ML on my original 7D. Maybe the wait for ML on the mark ii will be shorter then the original. ;)
I've just registered for this forum, so forgive me if I'm asking an old question - I had a quick search and haven't yet found an answer to my query, which is: I've just upgraded my Canon firmare to 2.0.5 - I notice that the latest ML f/w for the 7D is designed for 2.0.3, I'm assuming it would be foolhardy to try and install this over native Canon 2.0.5? If so, when will a 2.0.5-compatible version be released? Many thanks. Pierre.
Quote from: PierreK on April 29, 2015, 07:29:51 PM
I'm assuming it would be foolhardy to try and install this over native Canon 2.0.5?
You need to downgrade to 2.0.3 until a version for 2.0.5 appears.
Or stay with Canon 2.0.5 until an appropriate ML f/w comes out before trying it, is probably what I'll do... thanks.
Quote from: PierreK on April 30, 2015, 12:54:29 AM
Or stay with Canon 2.0.5 until an appropriate ML f/w comes out before trying it, is probably what I'll do... thanks.
don't hold your breath while you wait ;)
@PierreK:
It's definitely worth to downgrade to 203 in order to have a working copy of nightly ML...
You won't regret it... but you will if you don't try!
jm2c.
And the only fix mentioned in 2.0.5:
=====
Fixes a phenomenon in which the image files cannot be transferred using the FTP protocol via USB cable after the Canon EOS 7D camera has established a wireless connection to the Wireless File Transmitter WFT-E5A.
=====
As Licaon_Kter said: Don't hold your breath waiting for ML to be ported to 2.0.5 ...
Quote from: Walter Schulz on April 09, 2015, 11:19:04 AM
Downloadable firmware is not needed to start porting. See 70D thread.
Unfortunately the 7D mII (and the original 7D) is a different story...
Thanks for correction. Yes, now I rememver, dual-processor architecture and long, long wait for 7D to become ML-member.
Quick question , When i'm recording MLV when the file reaches Fat32's limit the new file's Type is different.
It looks like a sequence that starts with .M00
Is this an option to change because i can't convert these , i tried renaming it but it got crazy.
Wend it pass the limit Magic Lantern start to make this files, that is the rest of the file. If you use one of the Magic Lantern app you will get all file. You can read about more here in the forum, use the search.
Quote1728x692 48 fps slow mo. But wait a minute... When I play it back, the footage is normal aspect, no stretching required! I'm kinda running on no sleep in 2 days, I need someone to confirm this ASAP. I noticed when I set the cam to 1280x720 60p, and set the fps override to 23.976 exact fps, the liveview display was stretched vertically, so when recording it and playing it back records it in normal aspect! Timer A under 23.976 exact is 422 (FT -76). So I set the fps to 48, and Timer A back to 422. Mlv settings-
1728x692
3:2
GD Off
Canon preview
256 MB warmup
SRM On
Hacks on
4 buffers
Reserve on
Global Draw off
Expo override on
Rokinon 35mm manual cine lens
After messing with it a little bit more, the black and white levels get all wacky sometimes and the exposure is super glitchy. At first, I noticed this while testing out different settings in 640x480 mode, going to do some more tests soon as I charge my battery.
:edit: Yeah definitely a bug in the fps override control. I just downloaded the latest nightly, same thing. How exactly does fps override cause LV to stretch? Or is this a new feature I completely missed?!
:edit2: Ok, just figured out that this bug has been in the nightly since 7d fps override was implemented.
:edit3: To fix this issue, Timer A needs to be set to 498 (FT +76) for 23.976 exact and 440 (FT +10) for 60 exact.
Here are two frames from these settings. The first frame is with the modified fps settings, opened in MLVFS and rendered out into jpg through LR with no editing done. The second is normal 48 fps override, distorted frame rendered the same way. And also a screenshot of MLVFS to verify that it's 48 fps. Camera was mostly in the same position, with same exposure settings. Looks like the dng's get stretched downward, the top of each frame is in the same place. Interesting...
(http://s15.postimg.org/xt6qhuszr/M03_1345_000040.jpg) (http://postimg.org/image/xt6qhuszr/)
(http://s24.postimg.org/f4ox4fie9/M03_1346_000040.jpg) (http://postimg.org/image/f4ox4fie9/)
(http://s4.postimg.org/nb1wxjf89/Screen_Shot_2015_05_03_at_3_09_05_PM.jpg) (http://postimg.org/image/nb1wxjf89/)
This is definitely going to come in handy, it's not quite 60 fps but the aliasing is very minor compared to a stretched dng.
I'm having a problem when trying to install ML on my 7D with 2.0.3 firmware. I have 3 CF Cards, 1x 8Gb and 2x 16Gb wich have ML installed and all working.
I have bought a Lexar Professional 32GB 1000x CF card and put it in the camera, formatted, copied ML with the card reader, then when i insert it in the camera and tried the firmware update, i get this error message: "Update file cannot be found. Please check the memory card and reload the battery and try again."
Anyone else managed to get passed this problem? I will also be getting a 64Gb card in a few days, so i hope to get ml installed on that one too.
PS: I noticed that when starting the camera with the 32Gb card inside, takes a bit longer to power up, then with a smaller card inside. But I guess this is normal.
Not able to reproduce your error.
Workaround: Use EOScard or Macboot to make card bootable. Wipe all content (don't format!) from your card and copy latest nightly content to card.
Thanks for the reply. I tried, but doesn't work with this card.
Format in the camera, used EOScard to make card bootable, selected everything from the card and deleted the files, unzipped the latest nightly on the card, put it in the camera, same error.
Then i also tried formating the card in the card reader from windows and got the same error.
After using EOScard and wipe/copy: Just startup cam with card inside and press trashcan button. ML showing up?
Download h2testw and verify card's integrity.
After using EOScard and wipe/copy: Just startup cam with card inside and press trashcan button. No, ML isn't showing up.
I am testing with h2testw. I did a quick format then performed the test. It's halfway done now and no problem.
You won't see any problem with h2testw halfway.
Any update on this one?
yes... i was away while the test finished and no errors.
Change FIR's file name to uppercase and retry.
tried... didn't work
Make a screenshot of card's root directory and link it here.
Yes, here it is link (https://www.dropbox.com/s/l50f8xyqigu6fy4/Screenshot%202015-05-12%2017.09.35.jpg?dl=0)
I have no idea where you got this totally outdated autoexec.bin. Delete ML directory, FIR and Autoexec.bin (as in "wipe card") and copy extracted nightly build contents to card.
but i used the latest nightly build, 2015 May 03. that's where i have the files from. maybe i downloaded from the wrong place (https://builds.magiclantern.fm/#/)
Download again and check, please.
yes, i did download again, it shows a newer date on the autoexec.bin, but the same error.
I tried with an older build from 2014 May, same error.
Okay, start from scratch:
- Set cam to factory defaults, including C.Fn settings
- Switch to photo mode M, liveview off.
- Insert card to cam and format there
. Insert card into cardreader and copy extracted nightly build contents to card
- Insert card into cam and run firmware update
I tried this too and i can't believe it, still same error.
I tried to run software update with the card that has ML on it, the 16Gb one, and that was working even before the reset.
Retry using EOScard, please. Make card bootable.
Wipe card's content after doing so (do *not* format card).
Insert card into cam and startup. If EOScard has done its job cam will get stuck and you have to remove battery. If Canon menu appears EOScard failed to make card bootable.
Report result.
Still not working. Something must be wrong with the card. i put the 16gb card in, and pressed trash can button, ML appears. Used update software procedure, works.
New 32Gb card, can't seem to manage to get it to work. I did make it bootable via EOScard, deleted everything from the card, but the camera started normaly, so i guess no bootable card. Copied ML, tried again, nothing.
I think it's time to try another cardreader and/or another computer.
Oh yes... i do have another card reader and another computer. i will retry and report.
for this kind of card, does a command promt with a format f:/u work?
Why do you want to do this? Skip that. Format card in cam and go on.
Moved to another PC, another card reader, downloaded the files again... same thing. i don't get it, it should work.
Last try: Format card in cardreader using NTFS. Insert into cam and format again.
Copy ML files on card and retry.
That's it, didn't work, going on sale for half the price.
Something must be wrong with this card.
I've heard so much about Magic Lantern I finally decided to try it. Downloaded it on to my 7D, tried it out for a few days. Then out of no where the camera shut off and now won't power on. I charged multiple batteries and tried different batteries to no avail. Does any one know how to restart my camera?
JaiCanon, did you try starting the camera without the card inserted?
yes, tried starting w/out card
i think i accidentally erased the card when downloading photos, what would happen if this was the case.
Put it back on the card, it should not care.
thanks, I reloaded the software and found it must have been a battery issue
Hi
Is it possible to turn off weird things in photo preview? I have tried everything, ... It's sometimes better to see just photo, ...
Thx
INFO button. Works the same way without ML ...
Please try yourself and then write down something. My teacher for photography told me the first rule RTFM. I know the manuals.
Describe "weird things" or just post a screen snapshot.
Hi
It must be a bug, the ML overlay conflicts with Canon prewiev, link https://dl.dropboxusercontent.com/u/1280234/VRAM0.jpg (https://dl.dropboxusercontent.com/u/1280234/VRAM0.jpg).
And can someone confirm this. I use manual lens with ML exp override. If I turn auto ISO on does not work. This was tested on manual mode. Tried with magiclantern-Nightly.2015Jan29.7D203
Best regards
Not able to confirm this. Backup directory ML\Settings somewhere and go to Prefs tab -> Config Files -> Restore ML defaults. Retry and report back.
Here is another screenshot https://dl.dropboxusercontent.com/u/1280234/VRAM1.jpg (https://dl.dropboxusercontent.com/u/1280234/VRAM1.jpg)
About auto ISO. Works, but there is wrong number on live view.
Sorry, unable to tell what you have done or not.
Please backup ML\Settings and restore ML defaults. Then test again and - if able - give steps to reproduce error.
If unable: Restore ML\Settings from backup and retry.
Maybe try this setttings:
Zebras
Color space__________luma fast
Uderexposure________disabled
Overexposure________90% (230)
When recording_______show
Use raw zebras________photo only
Raw zebra underexp.___0EV
Nope. All fine.
Backup ML\Settings and restore ML factory defaults. Retry.
Or upload ML\Settings somewhere and link here.
Here is ML with my settings.
https://dl.dropboxusercontent.com/u/1280234/ML.zip (https://dl.dropboxusercontent.com/u/1280234/ML.zip)
And yes it's a little random bug - not always with the same settings. :)
This bug is only shown with preview turn on 2sec or more (in Canon menu).
Best regards
Turned preview off years ago. And I don't think it's a bug but intended.
a1ex, g3gg0?
Hi
Now I can repeat this bug. Try preview ON (2 sec or more - Canon menu), and
ML Zebras
Color space__________luma fast
Uderexposure________disabled
Overexposure________90% (230)
When recording_______show
Use raw zebras________photo only
Raw zebra underexp.___0EV
If I turn:
Use raw zebras________OFF
Raw zebra underexp.___OFF
I can't repeat this bug in auto preview.
PS
7D is fast camera and with crop factor is suitable for fast action - sports shooting, so auto preview is a good option.
Keep on rockin'
Hi guys,
Awesome work here! I have a quick question I haven't found an answer to in here or on the 7D install instructions.
I'm sure it's a stupid question but I seriously don't need a brick :o
I'm running the latest 2.0.5 firmware and need to know if it's possible to downgrade to 2.0.3?
On Canon's website they say you can't downgrade to previous version, so that gives me pause to verify here.
I have the 2.0.3 firmware and ML for 7D from here, so I'm ready to go, and have read a lot already and am super excited.
But just wanted to verify that I can downgrade even though Canon's site says you can't.
Thank you!
Bill
You can. Been there, done that.
Hey guys is anyone working on the Crop Mode Hack for the 7D? Love this on my EOS M :D
Hello,
I have the latest version of Magic Lantern on my 7D. When I press the button for Live View, I am immediately in the video Live View. It is then no longer exposure time 1/30 - the built-in flash does not go also. Start video recording does not work - it's as expected only the live view again.
What's wrong?
Best Regards
Rigo
Remove card and startup. Same results?
Hello,
Oh yeah! Is still so! Is there a Canon software problem?
Hello,
I have now tried the following with no memory card in the Canon menu ->
"Live imaging" suppressed and then reactivated. Now it's back! Previously, under the live image recording no entry - not "suppressed" and not "activ"
postscript
with ML it is now possible again! everything OK
Thinking of upgrading from the 550D to the 7D. How long can you record in RAW at 1280x544 at 50fps and at 1280x720 in 50fps?
Quote from: rtf on June 05, 2015, 09:34:49 AM
Thinking of upgrading from the 550D to the 7D. How long can you record in RAW at 1280x544 at 50fps and at 1280x720 in 50fps?
Here's a good thread to refer to for high fps times and combinations-
http://www.magiclantern.fm/forum/index.php?topic=10195.0 (http://www.magiclantern.fm/forum/index.php?topic=10195.0)
Quote from: N/A on June 05, 2015, 04:15:30 PM
Here's a good thread to refer to for high fps times and combinations-
http://www.magiclantern.fm/forum/index.php?topic=10195.0 (http://www.magiclantern.fm/forum/index.php?topic=10195.0)
Okay thanks.
some crash logs
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_RESET_PSAVE_LV, NULL, 0 ) )
at LVState.c:608, task ?
lv:0 mode:3
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 159K + 2641K
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTR_LV, NULL, 0 ) )
at LVState.c:485, task ?
lv:0 mode:3
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 159K + 2645K
Issue with FRSP?
Liveview screen goes blank after taking pic. Using half-shutter button (short press) brings LV back).
Someone able to confirm this? Don't have a second cam at hand right now ...
Used latest build.
Hi.
I can't help about this issue, but last week I shot video
link:
with ML-Nightly.2015Jun09.7D203 without any problems.
I did not use RAW video because of long recordings (more than 90min), MLV was great.
Big thanks for Focus peaking. Magic Lantern rules.
Best Regards
Hey guys,
Thanks for your great work on magic lantern! I've used it on multiple cameras for a while and it's been really helpful.
Today I installed the latest build (magiclantern-Nightly.2015Jun23.7D203.zip) on my 7D. When auto-restart is on, it restarts the camera even when I stop recording by pressing the button myself (rather than only restarting when the camera stops recording on its own). Is that a known bug?
https://bitbucket.org/hudson/magic-lantern/issue/2065/movie-restart-7d-stuck-in-loop-cannot-stop
Some assert logs
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:2
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 238K + 2706K
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:2
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 238K + 2706K
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:2
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 238K + 2706K
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:3
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 267K + 2707K
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:2
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 266K + 2711K
More assert logs:
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:2
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 239K + 2692K
ML ASSERT:
!DISPLAY_IS_ON
at ../../src/zebra.c:4179 (idle_display_off), task cls_task
lv:0 mode:3
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 238K + 2603K
ML ASSERT:
!DISPLAY_IS_ON
at ../../src/zebra.c:4179 (idle_display_off), task cls_task
lv:0 mode:3
Magic Lantern version : Nightly.2015Jun20.7D203
Mercurial changeset : db3ebdf8fd05 (unified) tip
Built on 2015-06-19 22:31:00 UTC by [email protected].
Free Memory : 238K + 2706K
Hi all,
Issue: Corrupted 7D CROP RAW video
Background:
Canon 7D 203 firmware with ML nightly.2015Jul02.7D203
CF card: Komputerbay Professional 64GB 1066x
Did not use any other modules than raw_rec with RAW video on.
When recording normal raw video everything is ok.
But when recording with raw video in CROP mode, then the video will be corrupted (can already be seen during recording in live view - there is all kind of textured areas jumping around in the view...)
I did try an earlier nightly build with the same problem, so I'm sort of irresolute on what to do next.
Please advice!
Thanks,
Jan
Could you try with mlv_rec as raw_rec is somewhat deprecated and tell us ?
I did try with mlv_rec also earlier, which caused the camera to crash during recording ONLY in raw CROP mode (this was with an earlier nightly version)
Now I tried again with the latest nightly in mlv_rec mode, and again it crashed only in raw crop mode (normal size raw worked just fine).
Here are the log files I found on the card:
CRASH00.LOG:
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTR_LV, NULL, 0 ) )
at LVState.c:485, task ?
lv:1 mode:3
Magic Lantern version : Nightly.2015Jul02.7D203
Mercurial changeset : bcd2d84120a5 (unified) tip
Built on 2015-07-01 22:30:47 UTC by
[email protected].
Free Memory : 241K + 2640K
CRASH01.LOG
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_RESET_PSAVE_LV, NULL, 0 ) )
at LVState.c:608, task ?
lv:0 mode:3
Magic Lantern version : Nightly.2015Jul02.7D203
Mercurial changeset : bcd2d84120a5 (unified) tip
Built on 2015-07-01 22:30:47 UTC by
[email protected].
Free Memory : 240K + 2724K
So the problem is associated with only CROP mode in both raw_rec and mlv_rec
I did new tests with less video resolution on the crop raw video, but the problem did remain.
All my raw crop video tests up to now were made using the ML view on the live view.
BUT!!, when I changed to one of Canon's views in live view (by toggling the INFO button), then I were able to get raw crop video without failure both in raw_rec and mlv_rec mode!
So I can circumvent the problem this way, but I loose a live view with correct display of what area I'm filming.
I think I have a sort of halfway solution to my problem...
Did you have Global Draw turned on? Turn it off.
Yes Walter, I did have Global draw on, but when I tested in off position I were able to capture raw crop video. So it seems that this issue has to do with all tree ML live views in raw crop video mode.
"All three ML live views"? Sorry, please explain.
Is it just me or does 7D ML seems very unstable lately? lots of ERR70
anyway, crash log:
ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1154, task RscMgr
lv:0 mode:3
Magic Lantern version : Nightly.2015Jul02.7D203
Mercurial changeset : bcd2d84120a5 (unified) tip
Built on 2015-07-01 22:30:47 UTC by [email protected].
Free Memory : 237K + 2697K
Sorry Walter, By "all tree" I mean the "LiveView", the "QuickReview" and the "ON, all modes" in Global Draw.
Another issue, I have experiensed it twice now, that the 7D battery was flat after having my ML CF card in the camera over night, even though the cameras power button was in OFF position? I'm I dreaming or what?
Zip contents of ML\Settings, upload it somewhere and link it here. Will try to reproduce.
I'm used to remove and reinsert battery. Power off setting isn't breaking power line but just telling the cam to shutdown.
Hi Walter
Hope these settings was the one you requested.
Regards,
Jan
https://www.dropbox.com/s/t2xhfjnajq923kd/Frojdman_7D_settings.zip?dl=0
ML nightly June 9,2015. In MLV record in regular mode the movie menu, raw video(mlv) shows the resolution and below it show write speed needed at 23.976fps. Which is the fps I want to shoot in. But when I move into crop mode it shows additional resolution setting but only at 29.951fps. Does that mean in crop mode you can only shoot at 29.951 fps? I'm sure this is covered elsewhere but couldn't find. Thanks.
You have to tweak fps settings.
OK. I've done that before but you loose sound. I was hoping to have both. It's essential that you import video into editor (I use Sony Vegas) at the exact fps setting you choose to override to keep audio and video synced. I learned that the hard way. :) Thanks Walter.
Just recorded in crop mode with 23.974 fps and sound.
So, quick backstory, i recently bought a Komputerbay 1066x 64GB
testing on MAC i got 149mbs read max, and 122mbs write max
Blackmagic on MAC 133 read max, and 121mbs write max
Testing today from a Windows Surface 3 CrystalDisk -- 149mbs read, 129mbs write
i was thinking of returning this card as it is still not quite 155 / 160 or consistently 140 write and my Magic Lantern benchmarks were poor
:64.8mb/s in movie mode, 54mbs read
74mb/s in photo and playback write
best results 86
(http://i1027.photobucket.com/albums/y333/ChameleonNinja/BENCH5_zpsgoym8fjg.jpg) (http://s1027.photobucket.com/user/ChameleonNinja/media/BENCH5_zpsgoym8fjg.jpg.html)
today i installed the new july build and did a few restarts and in playback i got a massive result across the board:
(http://i1027.photobucket.com/albums/y333/ChameleonNinja/BENCH10_zpskkyu4uck.jpg) (http://s1027.photobucket.com/user/ChameleonNinja/media/BENCH10_zpskkyu4uck.jpg.html)
But movie mode was still lacking...
(http://i1027.photobucket.com/albums/y333/ChameleonNinja/BENCH11_zpsczi2o6vw.jpg) (http://s1027.photobucket.com/user/ChameleonNinja/media/BENCH11_zpsczi2o6vw.jpg.html)
I understand the limitations of the Canon 7D but want to maximise my speeds and have seen results nearing the 90mbs write
currently i am hitting around 78/79 maybe 81mb/s but it skips a frame and freezes up trying to write the data, sometimes its able to stop after a skipped frame write the 5/10 seconds and move on but others it will freeze the entire system.
So
1. should i return the card - the chipset is the old AB so could get an AC and i am still only getting 120mb/s write?
2. is this freezing normal what can i do to prevent it?
Thanks everyone great work so far very impressed.
IMO: Card absolutely ok and within expected performance range.
Freezing needs to be explored, though.
Sounds great if the latest version works in crop mode and 24 fps/s.
Just tested 24 fps and this works as well.
Two questions here...
1) If I haven't upgraded in several months, but last time I shot it was great- should I wipe it clean and re-install before my shoot tomorrow, or just use the older version since it worked fine?
2) if I don't touch any fps override, then it's 23.976 fps right (assuming 24fps is selected in canon menu)? Should I rather use fps override and set it to 24?
I've tested recent relise, and it is fine. Haven't had a power down / cf eject / freeze in couple recent releases, tough I never could really pinpoint he cause, previously it froze up if I ejected card on switched off camera and putt an other one, had to eject battery as well. not always, could not understand why, but it happened once in a while. for last 2-3 releases, have never had this bug.
but yes, I've tested it, seams stable.
if you select the 24 in canon menu, then it is indeed 23.976, if you have no particular reason you should not touch the fps override.
8) thanks!
Followup question... when planning the shot (before hitting record) I like all the widgets on the screen like zebras, meters, etc. but when I magnify-zoom in it's b&w with a horrible lag, and then the zoom out button doesn't work so I need to hit play in order to get back out, and then it refreshes the screen for a few seconds (not terrible, but kinda annoying)
Is there a way to tell it to use the native camera mode when zooming in (5x or 10x), then ML with all the global draw stuff when at normal?
is it while shooting RAW? for RAW that is the way it is, it is called crop mode, for 1:1 pixel binding and no moire
Before hitting record, just while composing the shot...
How can you compose a shot zoomed in with incorrect framing?
That's the point :)
I like to go back and forth between zoomed in (to check focus) and zoomed out / regular (to compose the shot).
With ML installed- the regular (zoomed out) view is great since I can see the scene as-is and also get meters, but the zoomed in view is not great since there's a delay (esp when going back to regular), it doesn't go to 10x, and it defaults to b&w.
I'd like the zoomed out / regular view to be ML with all the bells and whistles, but zoomed in (both 10x and 5x) to be native canon- and to be able to quickly switch between them.
Is that possible?
simply switch off the raw shooting while composing/checking focus and then switch it back on. this is a normal raw behavior because the zoom function is used for remapping how the sensor is read so no lines would be skipped, sadly the debrayering is cpu consuming (and ml cant directly access the canon fw one, as i have understood, maybe I'm wrong) hence the b&w.
if you press zoom again it turns color while pressed... ouch, turning raw on and off would also be time consuming for the way I like to work :\
Need to get me one of those EVF things or a large monitor so I can judge focus more easily ;)
Hey guys,
Considering buying a 7D for RAW Video shooting only. Has the record time improved from the last couple of nightly builds? The longest time I've seen so far was 11 seconds.
Recording times of this length are indicating wrong settings and are not related to build versions.
I had one question...
when I using dual ISO on my 7D, can I view the photos on the camera without those lines ??
Not implemented.
is this in the near future plan?
Well, if you tell me where to find such a thing ...
hmm...If I ever find them, I'll will call you... :)
thank you anyway...
Why would you want to do this in camera when it still looks as good and can even notice the increase in DR when reviewing them on LCD despite the lines.
Play with the Zoom button a little in and out to see where the lines starts to become less/more noticeable. Jm2c.
Hi, this question has probably been asked millions of times, but I've just installed the newest nightly build onto my 7D and when I turn on Movie restart, I can't stop the camera recording once I start it (unless I turn off the camera). Basically when I hit record again to stop recording it, it stops for a second, then restarts again. Is this a common issue or is possible I have some settings set wrong?
Thanks!
https://bitbucket.org/hudson/magic-lantern/issues/2065/movie-restart-7d-stuck-in-loop-cannot-stop
You need movie restart only when recording H.264. RAW/MLV doesn't require this setting anymore for recordings > 30 min.
If I use an 8mm lens and shoot video in crop mode (3x) what is the equivalent lens size ? Is it 24mm? 38mm? Does anyone have experience with the Rokinon, Bower, Sayang, 8mm lens they would like to share? Thanks.
Quote from: Rainmanwalking on August 18, 2015, 04:43:32 PM
If I use an 8mm lens and shoot video in crop mode (3x) what is the equivalent lens size ? Is it 24mm? 38mm? Does anyone have experience with the Rokinon, Bower, Sayang, 8mm lens they would like to share? Thanks.
I had the same idea but i tend to use really good glass in crop mode, since my Samyang isn't really that sharp i don't use it.
And about the lens, i keep myself out of f/3.5 as much as i can. it has a good improvement on f/5.6 and maximum sharpness at f/8.
This is "Camera-specific discussions" forum and this thread is dedicated to 7D issues. Keep chatter down and discuss such items elsewhere, please! "Hardware and accessories" will do just fine.
Mr. Schulz, my interest is only with the 7D as it's the only camera I own and I sincerely appreciate your help with my questions in the past. My question might not have been stated clearly, I was wanting to know how wide angle lenses perform in crop mode (3x) on the 7D, and how to estimate the equivalent lens size. Thanks.
3x crop mode on the 7D should be about the same as the other APS-C cameras in 3x crop mode. Note that you can choose various frame sizes for recording and that also changes the amount of cropping. 3x will get you in the ballpark. In other words:
8mm x 3 ≈ 24mm equivalent on an APS-C sensor
8mm x 3 x 1.6 ≈ 38mm equivalent on a FF sensor
Now for my very 7D specific request. Can someone that knows how to look into the ML/LOGS directory on the SD card please PM me?
Thanks dpjpandone. Now to make sense of all the gibberish.
I am enjoy to work with magic lantern. One thing is I hate about view play video on camera because it can't do the back. When I am at play mode and wanted to check out another video, I have to exit the magic lantern and go to view another video. I film blind most time, so I need to look few videos before I film again.
I'm unable to understand what your problem is. Please rephase your issue and add issue in you native language.
Looking for someone willing to test this bugfix: https://bitbucket.org/hudson/magic-lantern/issues/2202/create-directory-on-recording-doesnt-start
You need newest build or the one before.
Hi there,
I've got a 7D and would like to start using Magic Lantern on it. I've spent hours on the internet learning about this magical hack...
I do a lot of slow motion (action sports) and am wondering what the current capacities of the 7D are on the latest build (oct/1/2015) mainly for recording 60/50 fps? And does anyone know what is the max/best quality resolution it is possible to record continuous at 60/50p? (with the right type of cf card of course).
Thanks for your expertise!
Seriously guys after months, if not a year or so goes by and there are bugs that seems to be either unreported or unable to fix as of yet on this remarkable 7D even with the latest nightlies.
It feels good to be back in this league and definitely never gets old with this semi beast after scooping up a solid used one off Craiglist's for incredibly cheap!
Missed the half-shutter magnified zoom hot key!
[emoji108]
*edit*
Is there a certain work around to get crop-mode to record MLV Raw? Because whenever I set it into 10x crop (pressed it twice) and it won't record but if I go into 5x crop mode (pressed once) which starts recording but with that crappy grayish look.
On top of my head I remember being able to shoot in crop modes on 7D especially in the older builds -- guess I'll have to dig through and find one that works?
Quotewhenever I set it into 10x crop (pressed it twice) and it won't record but if I go into 5x crop mode (pressed once) which starts recording but with that crappy grayish look
Not with my 7D right now, but the gray look is because of the magic lantern preview (which shows the correct cropped image). To avoid that, you need to switch it to Canon (somewhere in ml menu).
It used to be that if you hit the zoom button twice (10x) it would freeze. I don't know if that has been fixed. You only want to push it once, though, for shooting raw. Somewhere in the ml menu you can set the zoom to only do 5x.
10x feature was disabled in build #139 (17.06.2014):
3: 7D/5D2/550D/500D: disabled LV RAW mode in 10x zoom (should fix issues #1587, #1990, #1961 and others). Other cameras requiring this workaround?
Makes sense guys... Will dive into this some more this weekend and share results.
Thanks again as always!
Hi there, new user, many thanks to developers, excited to get our next short movie done in raw. I am having trouble controlling IRIS(rotating wheel) while shooting Raw. any help will be apreciated. Thanks in advance.
I have used 7D for about 4 years, now my bright boy has been borned last mouth ,that I want to make many many good videos for him , so I came here...
I sent my trusty 7D to Canon for repair (a new sensor) and it came back with firmware 2.03 replaced by 2.05. I miss my ML. Canon says
QuoteFirmware Version 2.0.5 is for cameras with firmware version 2.0.3. If the camera's firmware is already Version 2.0.5, it is not necessary to update the firmware. Once the camera is updated to version 2.0.5, it cannot be restored to a previous firmware version.
Discussion on this forum nonetheless implies I can revert to 2.03 by putting that version on the card and using "update firmware." Can someone please confirm that - thanks.
in post http://www.magiclantern.fm/forum/index.php?topic=9848.msg122566#msg122566 (http://www.magiclantern.fm/forum/index.php?topic=9848.msg122566#msg122566) Walter Schulz, responding to a post about ML not running under firmware 2.05, said
QuoteI would suggest to use three cards for this. One with Canon's firmware version 2.0.3, one with 2.0.5 and a card running ML (bootable + files + directories).
The cards holding Canon's firmware may be some cheap or small capacity cards.
I don't understand that - could Walter or someone explain? is the idea that all 3 cards would be independantly bootable by using EOScard.exe? would the "card running ML" have 2.3 on it? If the firmware installed on the camera remains 2.05, why the 3rd card with 2.05 on it?
Linked post was an answer to someone who wanted to use ML (which requires Canon firmware 2.0.3) and Canon's firmware 2.0.5. Not at the same time, of course but he wants to change between both options. Do you want this, too? If not, the answer does not apply to your needs.
To switch to 2.0.3: Format a card using your cardreader, format again in cam. Copy Canon firmware file (2.0.3) to card and run firmware update.
After successful downgrade delete firmware file from card (or just format again in cam) and copy extracted nightly build contents to card. Run firmware update again to get card and cam running ML again.
thanks for so quick a response. I was alarmed by Canon's statement that you can't go back from 2.05.
For the moment I see no reason why I'd want to also run 2.05, as well as 20.3. although I do have two cards, only one of which has ML on it.
Quote from: OldYogi on October 29, 2015, 08:05:29 PM
I was alarmed by Canon's statement that you can't go back from 2.05.
Don't know why they use "can't" instead of "shouldn't" which would be the proper term.
Walter --
Thanks again for the response.
If like that other post I did want to run both 2.03 & 2.05, am I right that you are suggesting that
a. to switch to 2.05 from 2.03 just load the card with 2.05 on it and run firmware update. after that you could use the ML card, but ML itself wouldn't load.
b. To go back to 2.03 do the same with the card with 2.03, and
c. to run ML after reverting to 2.03 insert the ML card and run firmware update again.
I ask in part because I have my card with ML on it as I had been running it -- if I format that card I lose its configuration -- whereas if I understand, I could revert to 2.03 from another card, then insert the ML card and run firmware update again. That way I'd be running the same ML as before.
Do I have it right?
Thanks.
a. Nope. Cam won't start.
b. Yes
c. "Firmware update" is not needed.
Greetings
not sure if i am posting the the correct section,I have just dot the canon 7 D mark 11, i previously had the 600d with a 50mm f.8 and a 18 to 250mm, i recently started shooting very low light live music gigs/ clubs, this camera is very different to my 600d and i am in need of setting it up for low light photography, any help will be greatly appreciated, flash use in not permitted in these venues, thank you kindly..regards
7D is not that grate at low lights, almost never go above ISO 1250, you would be better of with 5Dmk2.
No special setting is going to help concerning the limits of the camera, just go with the best and fastest lens you can get. If you do video in h264 then cranking up bit-rate helps at high ISOs, it is easier to remove it with Denoiser or NeetVideo.
If it is photography with high dynamic range, you should look into dual-iso
He's asking about 7D2, not 7D.
sorry guys my mistake , it is the mark two, not for video, just photos only
Thanks And sorry for the mistake.
regards
Walter,
I fear I'm being profoundly dumb, and I don't want to exhaust your patience -- but I remain puzzled.
I had asked if, with firmware 2.03 on one card, 2.05 on another, and ML on a 3rd, whether it would work as follows:
Quote
a. to switch to 2.05 from 2.03 just load the card with 2.05 on it and run firmware update. after that you could use the ML card, but ML itself wouldn't load.
b. To go back to 2.03 do the same with the card with 2.03, and
c. to run ML after reverting to 2.03 insert the ML card and run firmware update again.
you replied:
Quotea. Nope. Cam won't start.
b. Yes
c. "Firmware update" is not needed.
I think I don't understand why in (a) the "Cam won't start." If I update from 2.03 to 2.05, I know I can't run ML, but isn't the camera then restored to running 2.05? It seems to make no difference whether the card I then use (under 2.05) has ML on it or not -- right now the camera has 2.05 and has no problem booting with the card that has my 6 month old copy of ML on it although of course ML itself doesn't load.
what am I missing?
If the camera has the bootflag enabled, and the wrong version of autoexec.bin on the card it won't boot.
The cam won't start because updating/downgrading firmware does not affect cam's bootflag (which is set by ML installation and used to look for a bootable card). If you insert a ML enabled card the cam will locate card and try to load autoexec.bin. And because ML is designed to work with a dedicated firmware version you will get an error and will be forced to remove battery before proceeding.
If your cam is starting up with firmware 2.0.5 installed you either haven't the bootflag set or your card is not bootable.
Cam's bootflag can only be set/removed by ML installation. And this requires firmware 2.0.3.
An "ML enabled card" is bootable (part of ML installation, too) and has ML files and directories on it.
ah --- thank you both -- this now makes sense.
The cam has no bootflag enabled, I assume, because when servicing the cam Canon upgraded the firmware. The card presumably remains bootable -- because it is the same card that was booting before, when the camera had 2.03.
So, indeed, to reenable ML I have to both "update" to 2.03, and then reinstall ML from a card, so the bootflag will be set on the camera.
I feel much more comfortable doing stuff when I know why I'm doing it. Thanks.
Quote from: OldYogi on November 03, 2015, 02:23:22 AM
ah --- thank you both -- this now makes sense.
The cam has no bootflag enabled, I assume, because when servicing the cam Canon upgraded the firmware.
Again: Updating firmware d o e s n o t affect cam's bootflag!
Hello,
I try to install ML on my 7D
My firmware is 2.0.3
I have copy all ML files on my SD card from my computer and insert it in an adaptator CompaqFlash/SD into my camera
When I try to update firmrware to install ML when I click to OK, screen shut down and nothink append.
My Camera is freeze.
I remove my memory card and after my camera write no firmware found ...
I remove battery
And after my camera work well.
Do you have a idea ?
Thank
Concerning compatibility most CF-SD-adapters are just a major PITA. Use CF-card.
I can't copy ML program to my CF.
I have no external CF adaptator.
When I try with my 7D connect with cable to my computer, I was unable to write to CF (no right ?)
Is there any option to active this ?
(windows seven 64bits)
20 bucks and your problem is solved.
http://cameramemoryspeed.com
Quote from: F83eric on November 15, 2015, 05:00:58 PM
I can't copy ML program to my CF.
I have no external CF adaptator.
When I try with my 7D connect with cable to my computer, I was unable to write to CF (no right ?)
Is there any option to active this ?
(windows seven 64bits)
Get card reader - that is the only solution! you cant copy ml trough camera, and from my experience you should always use card reader to read as well, have had problems with ML cards and usb file download.
Hi
Thank you for your response.
I get card reader.
After I have installed ML
Is it possible for me to replace my CF with my SD card and adaptor ? Is it necessary to copy more file on SD card ?
If no, is it a problem to use some time ML with my CF, and start my camera without ML with my SD ?
Eric
Never tried to use CF-SD adapters for ML. So you have to find out.
You have to make SD-card bootable by using EOScard/Macboot.
Then wipe card's content and copy extracted nightly build content to card.
I have no idea if cam's card interface will able to boot from SD via CF-SD-adapter.
Grabbed my Jobo SD/SDHC/SDxC CF Adapter (Art #SE9109) and my SanDisk Extreme SDHC card 32GB.
Fired up EOSCard and used a CF Cardreader and enabled ML and Bootflag on the SD Card, which was inserted in the CF Adapter.
EOScard copied the ML files, then I downloaded the latest build (magiclantern-Nightly.2015Aug18.50D109) and copied those files to SD, overwriting existing files.
Inserted the CF adapter with the SD in the 7D and switched on the 7D.
ML loads but on the first boot the red LED flashes for about 20 seconds.
Probably because a lot of things need to be written to SD and the throughput is not as fast as a CF card.
Eventualy I have ML running on an SD with a CF-card adapter in my 7D.
Now I have to keep track of the various memory cards with their ML versions. :)
Thanks for testing it.
I recommend to delete contents written by EOScard. There is an almost endless line of people who had problems because they are not that good telling copying with/without overwriting.
with first boot happens the ROM dump, 7D makes 2 - ROM0 UN ROM1 in ../ML/LOG/ each is 16MB, if I remember correctly, correct me if I'm wrong
Hello
ML ok on a CF :).
ML ko on a sd with cf adaptor, I try a lot of procedure with EOSCard but my 7D doesn't start. >:(
Eric
F83eric:
Honestly, I'm afraid if you do it this way with an adapter (never tried it on my end) then you probably won't be able to achieve the 7D's sweet spot with recording times/resolution in terms of maxing out the writing speed.
Just get a card reader and stick with CF cards (at least 1066x) which works well for 7D.
Keep it simple and Happy Shooting!
Which one i'll buy? 7d or 70d? I now have the eos M. :)
No details/use cases given -> No advice in return.
I am trying to use the Restart Rec. Feature in the Movie Extras menu, and it doesn't seem to be working at all.
Here is my settings:
Crop Mode: 2048x1152
FPS: 24
I usually get about 6-8 seconds of recording in this mode, but to be able to have it auto restart recording at the end of each of these segments would be awesome because I could put it on a tripod during a shoot and get a bunch of 7 second clips that were basically sequential and could be cut into A-cam footage in post.
Any help would be appreciated!
QuoteI usually get about 6-8 seconds of recording in this mode
With 1000x card from Transcend, i can get 14-15 seconds in 2048 x 1200 pixels (24 fps, crop mode).
Quote from: kamranjon on November 18, 2015, 04:53:14 PMI am trying to use the Restart Rec. Feature in the Movie Extras menu, and it doesn't seem to be working at all.
I'm not a programmer but this feature seems to be developed for H.264 recording only and covering movie stop caused by 29:59 and/or 4 GByte limit in this mode. It does not work with RAW/MLV.
Hi guys,
Im recording some footage against the sun and im getting a pink circle (the size of the sun) in the sun. Using MLVProducer or MlRawViewer. Anyone knows about this?
Thanks
I'm not sure if this is a problem but my CF benchmarks at 152 MB/s Read, 134 MB/s Write but on my 7D I only get 42.4 MB/s Read, 64.8 MB/s Write?
Doesn't seem right to me, generally I get around 70+ MB/s whilst recording and it seems to be quite stable.
Edit - Re-ran the test in Movie Mode 1080p24 (was in the main camera screen before) and got 81.5 MB/s Read, 66.2 MB/s Write which sounds better, is that the best I can expect from a 7D?
Komputerbay 1066x 64GB Card
Lies, damned lies, benchmarks.
Use photo mode -> Start benchmark -> Press Play button
Quote from: Walter Schulz on November 30, 2015, 08:36:59 PM
Lies, damned lies, benchmarks.
Use photo mode -> Start benchmark -> Press Play button
Ahah! Read 108.3 MB/s, Write 87.2 MB/s. Thanks a lot Walter, I guess they don't really mean much I was just worried that something was amiss with my camera :)
Hallo!
Is there any headphone monitoring for the 7D yet?
Kind regards from Vienna
Markus
Top of page -> Downloads -> Download Nightly Builds -> Top of page -> Features -> Audio
Please go to Top of page -> Downloads -> Download Nightly Builds -> 7D.203 and follow instructions there. Forget anything you ever seen or heard about bspatch and related FIR files.
Hallo Walter!
Use bspatch and EOScard in case of emergency?
Thanks for help and kind regards from Vienna
Markus
Schreibe ich undeutlich?
Hallo Walter!
Bitte entschuldige meine Fragen.
Angenommen ich habe nur eine ML Karte und die ist
dann defekt, kaputt oder verloren, was mache ich dann?
Einfach eine neue Karte erstellen und FW-Update durchführen?
LG und DANKE aus Wien
Markus
Top of page -> User Guide -> Install Guide
Hallo Walter!
I have installed ML yesterday. Works nice!
Lets see about the future ...
Is there any chance in the near future for
the 7D to get headphone monitoring?
Thanks for help and kind regards from Vienna
Markus
Hi! :)
I used always 64Gb cards till now. Now i would like to try a bigger one.
Does Macboot work on a 128Gb Card? Are there other app to make the card bootableon MAC? (sometimes Macboot doesn't work fine and i have to re-format many times - Maybe and old version? :o)
Thanks for help and kind regards from Italy.
Umberto
Read first post of this thread.
You can use MacBoot or you can run firmware update making the card bootable.
thank you, I just want to be sure before buying it.
Hi everyone, I'm hoping that this is the right place to ask :) My 7D used to record RAW/MLV no problem until a few months ago. I've been using my 2 Komputerbay 64GB 1000x CF cards since Dec 2014. Now it says both cards are unreadable. Can't even format them in camera. They both work fine in my 7D2 and I can read/write to them using my Transcend TS-RDF8K USB 3 reader. The 7D firmware is 2.0.3 and as far as I can see, nothing has changed with the camera itself. Anyone else experience this? Thought on how to fix? Thanks for any suggestions.
Sounds like an incompatible format type on the cf card. Or some activity done on the 7D2 has caused it to be incompatible with the 7D.
Suggest that you take one card and reformat it to default ntfs settings on your computer then reinsert into the 7D. If the 7D recognizes it, reformat in the camera. Make the card bootable and reinstall ML from the latest nightly.
If that works l'd also suggest having separate cards for each camera.
Hello,
I've only heard of ML yesterday. Tried to look for a specific answer to my question in the UM but I'm not it's there.
I have the 7D with 2.0.3FW. There are no options to set anything regarding mics. I hear the 2.0.5 have some controls but if there are any at all at the 2.0.3 I can't find them.
I've made a video recording with a mic straight to the camera... it was nearly unusable! So much noise.
My question is double-fold:
Will I be able to control the camera's pre-amp with ML?
Will it be better than using something like the Tascam DR60D-MII ?
Will it still be better to use both?
Thank you
Hi Ottoga, thanks for the suggestion. I did as you suggested, but it didn't work. the 7D still says 'Change Card' I had tried to format to MS-DOS with the OS X Disk Utility, but when you mentioned NTFS, I thought maybe I needed to get a different app to do that. I downloaded a trial of "NTFS for Mac OS X" and formatted the card to NTFS. Same result. I do appreciate the help :) Merry Christmas
Is there a way to get the EOS Utility to work with the latest nightly yet? I like to try to use the laptop as a monitor through the EOS.
Can't find any downloads for Magic Lantern on the website. Only Nightly Builds. Am I missing out on something?
Nightly builds are the download...
Ahhh... got it.
I also only looked into ML for the first time last night and installed it on my 7D today. I was particularly interested in the dottune feature, but it doesn't seem to have this tool afterall.
Am I missing something? I have done a brief search here and did come across the following post:
"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
« Last Edit: December 31, 2013, 09:59:36 AM by r4ptor »"
Am I to believe from this that the ML software for the 5D Mark III can be used on the 7D?
If there is no dot_tune.mo in your 7D download something went terribly wrong. Download once again, check contents in ML\modules. Delete ML directory from card and copy nightly build over once again.
Oops, my mistake! I hadn't looked for it in the right place. It is there. :)
I have try to record sound with raw (MLV) but i don't see the .wav files in the card. I have switch on in canon menu and in ML, i can see the levels and everything is alright, i hit record and then wend i going to see the files in computer nothing is there, no wave files =/
It's not working in the 7D or im doing something wrong?
Did you forget to enable MLV sound in Audio setting within ML menu?
Quote from: arrinkiiii on January 10, 2016, 06:47:12 PM
I have try to record sound with raw (MLV) but i don't see the .wav files in the card.
The .wav files are embedded in the .mlv wrapper--you won't see them on your card unless you run MlRawViewer (http://www.magiclantern.fm/forum/index.php?topic=9560.0) on them. For some reason that program extracts the .wav files and leaves a copy along side the .mlv files. It is ok to delete those .wav files because the ones inside the .mlv files are still intact.
That's correct, @dfort!
wowwwww damnnn i thought on that but... Thats why one time i have soo many wav files outside of the mlv files, wend using MlRawViewer... thanks for point that out.
I almost never use sound in camera but i bought the new rode wireless mic and want to see/experiment the ratio/noise floor using the audio amp's of camera. Since i have deleted all files, tomorrow will try again =)
Thanks dfort and deafeyejedi =))
Guys, i have install the last version and still have the pink color in the highlight that are blow, special if you are pointing the camera to the sun, in old versions i never have this issue. Any recommendation beside not pointing the camera to sun?
I now that BlackMagic and Sony cameras have this issue but with firmware update they fix this (i think).
Here a jpeg
https://www.dropbox.com/s/ixxfrzqra6y9iib/M28-171500000.jpg?dl=0
and tre DNG
https://www.dropbox.com/s/2typqcml07w2ijz/M28-171500000.dng?dl=0
Hello
I want to sell my 700D and buy 7D. Inportant for me is RAW recording, 7D MKI record full screen (1728x972 with 67,1mb/s in 24p) movie in unlimited time? What with stability of software? Some man of FB movie group says that ML destroy his card.
He is sure it was ML and not Canon?
Cards in CF-slot get hot if driven with RAW data all the time, that's for sure.
1728x972@24 is not a problem with a fast card. Temperature can be. Full exposure to sun on a hot day may cause trouble.
I understand this is unsafe - RAW recording and sun. High temperature can destroy the body ant card. But it's problem on any Canon with ML. I prefer to use umbrella on sun :P 7D write speed is 60mb/s or 80mb/s?
http://www.magiclantern.fm/forum/index.php?topic=9848.msg135955#msg135955
90 MB/s is just benchmark. Stable recording requires some distance to the edge.
Hi there,
I have some problems installing ML on my 7D 2.0.3 . After a successful installation of ML a text message instructs me to restart my camera. I wait till the power is off. After restarting the cam nothing happens. After switching the power button from off to on there is neither a red blinking LED nor an active display. It's just a black screen. No key is detected if pressing it.
What I did so far:
a) format the CF in the camera
b) deleted all my custom preferences
c) set the camera mode to M
d) tried several builds:
-magiclantern-Nightly.2016Jan14.7D203
- magiclantern-Nightly.2015Dec20.7D203
e) I took out the battery for several minutes and pluged it in again
I reflashed the firmware to 2.0.5 and back to 2.0.3 and did the same procedure starting with a) - had no effect...
My camera restarts after releasing the battery for seconds and formatting the CF-card.
Sometimes I got this error when trying to install directly from the card: http://fs5.directupload.net/images/160118/n8pws8cy.jpg (http://fs5.directupload.net/images/160118/n8pws8cy.jpg).
Installation works fine, if I copy the folders and autoexec manually and start the Update through the EOS Utility. But after restart > black screen
Are there any advices?
You cannot use EOS Utility for installing ML. It won't do. EOS Utility will work fine with Canon's native FIR file.
Format card in cardreader.
Format card in cam.
Copy extracted nightly build contents to card.
Insert card into cam and startup.
Run firmware update.
After success message restart cam before timeout (60 seconds) sets in.
Press trashcan button.
Report results.
ok I followed your steps and end up in getting this error egain: http://fs5.directupload.net/images/160118/n8pws8cy.jpg when I try to run the update process.
Card type used?
Show contents of card's root.
My card is a SanDisk Extreme Compact Flash 16GB 60MB/S.
contents of card's root: http://fs5.directupload.net/images/160118/2qjjvfa6.jpg (http://fs5.directupload.net/images/160118/2qjjvfa6.jpg)
Use EOScard to make card bootable.
Wipe Autoexec.bin, ML directory and *.FIR from card.
Copy extracted nightly build contents to card.
Insert card into cam and startup.
Report results.
ok I used EOScard enabling EOS_DEVELOP and BOOTDISK.
Wiped the data and extracted it back again. After inserting the card and turning it on nothing happens. Just a black screen.
I suppose nothing happens after pressing trashcan button.
Remove battery, remove card.
Do you have a spare card?
yep nothing happens after pressing any button. I don't have a spare card.
Try to get one. 1 GB (or up to 32 GB) will do fine.
ok none of my friends uses a CF. So I would have to buy a new card. Is this a ScanDisk problem, should I buy a Lexar instead? - what if ML doesn't work either with the new card?
greetings
The cheapest one will do. Slow and outdated 4 GB cards are about 8 Euro here (new). Just ask around local photogs for a used one.
And I tend to cross bridges when I'm there.
If I record RAW can I use hdmi Apurture screen in one time?
Just a quick reply regarding to my problem: I bought a new CF card, a Lexar Professional 16GB 1066x. Now it works like a charm!
I thinks it's an issue with old CF cards perhaps. My Scandisk is 6 years old ...
Thanks for the useful help =)
@arrinkiiii did you solved the pink dot problem? which is it the latest safe firmware? thx
Hi Brawl,
No =/ i think this in the past didn't happen or maybe i never have film in to the sun... But like sony and blackmagic camera this can be solve with software change.
Quick question PLEASE. I push the zoom button to 5x and then go into the ML menu and set resolution to 2240 16x9. I get about 15 seconds of video. Once this is set is there any way of filming without the 5x zoom on? Kind of makes it hard to compose. Any help with be great. Cheers.
"... is there any way of filming without the 5x zoom on?"
Look here for framing tips (#14 and note 6):
http://www.magiclantern.fm/forum/index.php?topic=5451.0 (http://www.magiclantern.fm/forum/index.php?topic=5451.0)
Bear in mind that using the true-frame previews while filming may causing "tearing" of frames due to processor overload.
Arrinkiiii,
I downloaded your DNG image and put it into Adobe Camera Raw... I noticed that the processing presets were set to "Camera Default" and not "Landscape, Portrait, Faithful, and/or others." The processing presets are located on the tabs adjustment area. It's a pull-down menu.
I think what's happening is that the "Camera Default" preset is putting too much emphasis on highlights and the details stored in the highlights. Switch over to "Landscape or Portrait" and there is no funky banding, stitching, or pink sun at the native exposure values.
FYI; Almost all DNG images, when lowering the highlights far too much, will produce pink sky and pink sun effects. What changing the processing preset does is better defines where shadows, mid-tones, and highlights actually reside.
Hi
Can someone confirm little bug with LiveView display presets?
If I in movie mode change display preset, the second display preset has two audio meters (see the screen shot).
(https://db.tt/7OhKkigd)
Tested with magiclantern-Nightly.2015Dec20.7D203
You can find my settings here https://db.tt/jODGmBYw (https://db.tt/jODGmBYw)
Best regards
Thanks LEVISDAVIS, I going check that =)
Hey guys, I was updating firmware on my 7D to be able to put Magic Lantern on it. Everything was going well, but when I came back in 5min, the camera was off (maybe battery died) and now when I turn on/off there are no signs of life in it. Have read quite a bit about this problem online and tried everything- removing, putting battery in multiple times, changing to different battery (OEM), removing both batteries (the small, clock battery) and letting it sit for couple of hours, with/without lens, different CF cards... but no signs of life, still bricked. Any ideas what else can help or is there a way I can flash firmware myself?
Thanks!
Btw, what happened to the beep feature when starting or stopping recording? I've been trying to make my 7D beep when I start or stop recording MLVs and I just can't seem to get it to work. It seems the option for that is gone from the ML video section?
#Dombra, read this? http://www.magiclantern.fm/forum/index.php?topic=12441.0
No micro switch at the battery hatch or memory card hatch?
1. Tried with a small screwdriver pressing both small knobs by memory card and battery, nothing :(
2. Tried what said in the thread shared above- deep format the card and remove and insert battery. Did it MANY times no changes. Tried copying firmware on the card and starting camera couple of times still no luck
Tested batteries on other camera, all charged..
I was wondering could I fry the main board or something while updating the firmware?
There is something to try:
- Make card bootable using MacBoot (OS X) or EOScard (Windows). If using EOScard: Wipe all contents from card after.
- http://www.magiclantern.fm/forum/index.php?topic=2296.0 1) Copy diagnostic autoexec.bin to card.
- Power off (switch), remove battery. Insert battery, insert card. Close doors. You don't have to power on.
Do you see a diagnostic screen after some seconds? Report back and don't forget to remove battery first, then card!
Thank you for your reply!
This is what I did:
Check the battery in other camera - shows fully charged
Erase card with disk utility to MS-DOS (Fat), Name UNTITLED
Open Macboot, found the card, set to Make DSLR-bootable, Prepare Card
Card must be FAT16 to make bootable for CHDK
making FAT32 DSLR-bootable
Making card scriptable ...
Card has been successfully prepared
Copy autoexec.bin to the card
Eject Card from computer
Take out battery, put battery back in, put card in, close door, wait for 10 sec....nothing :(
Am I doing correctly?
Big question now: Was ML installed on your cam or not? Means: This diagnostic works if the cam's bootflag is set.
My intention was to install ML, but I did not get so far. Camera bricked while I was updating firmware to 2.03
Please clarify:
You tried to update Canon firmware with Canon firmware file 7D000203.FIR
or
you tried to install ML on a cam running Canon firmware 2.0.3?
I tried to update Canon firmware with Canon firmware file 7D000203.FIR
This is bad news.
- Remove battery, remove card.
- Select C1/2/3 mode, insert battery and try to startup.
Anything working? LED? Screen?
Tried doing what you mentioned above, no signs...
Regards McBoot do I have to choose Make DSLR-bootable or Make CHDK-bootable or maybe even some other option, as I got the message
Card must be FAT16 to make bootable for CHDK
making FAT32 DSLR-bootable
Making card scriptable ...
Card has been successfully prepared
You can discard this message. It makes no difference in this case. If cam's bootflag is not set (part of ML installation) cam will not be able to use a bootable card.
If you excluded problems with compartment switches, there is not that much you can do. There are some resources on the web where people digged into cam's PCBs and reanimated broken cams by replacing blown fuses but I really don't know if it will help in your case.
Others replaced boards on their own with replacements bought from various sources. Be aware you may have to deal with calibration issues then.
Standard recommendation for dealing with this kind of error is contacting Canon service centers.
ok, gotcha. thats unfortunate but thank you for detailed answer
so you think it is hardware, not software error?
No, I don't know what is wrong with your cam.
Thanks for trying to figure it out!
Hello dombra,
I guess the loss of power during FW upgrade bricks the cam.
Better take it to a service center an tell them you want
2.0.3 FW version on it.
Kind regards from Vienna
Markus
hi guys, I'm searching for this feature called gradual expo
http://nofilmschool.com/2012/10/magic-lantern-alpha-2-canon-5d-mark-iii
is it avaiable on 7D?
thx
hello i am looking a feature can shot high speed 2 shot (not 3) thanks
I don't know any "High Speed 3 shot" setting in native Canon menu or ML menu.
I suppose there is something lost in translation.
Please rephrase your request and add your question in your native language, too.
A couple of questions re: raw video recording (MLV and MLV_lite) on a 7D using the latest 24/02/2016 nightlies if I may.
With either of the raw video modules I'm no longer able to select resolutions above the 7D's rated maximum of 1728 x 972. I can highlight them but they won't select. From memory I've been able to do this in the past and capture a few frames before the buffers overflowed and the recording crashed. I'm using 128gb KB 1000x CF cards tested at a continuous write speed of 110 MByte/s so they should be capable of handling anything the 7D can throw at them.
Also, with either of the raw video modules enabled and before starting recording: I am able to enable both 5x and 10x crop modes. 5x crop mode works fine however when I press record start in 10x the message "Raw detected error" or "Raw Defect error" flashes up and disappears really quickly and the recording fails. A 1kb mlv file is created for each attempt.
Is this potentially a bug in ML or is the 7D not capable of 10x crop recording?
I don't do a lot of video but I was trying to generate variety of test MLV_lite files with as many different capture settings as possible. I'm reasonable certain that I have done both of the above scenarios successfully in the (distant) past and was surprised when I couldn't do them today.
Any thoughts, enlightenments, guidance will be much appreciated. If I need to log a bug report just point me in the right direction and I'll get that done.
Thanks in advance.
Higher Resolutions:
Crop mode via ML menu "Crop Mode ON" or in movie mode press 5x. Adjust settings in RAW menu.
10x: Not supported.
@Walter, thanks it works a treat. I was just doing it back to front.... must be getting old and senile.
Can I record 60fps without being raw? The widest I have is a 28mm lens, and the problem is that it in 5x crop it's like telephoto :/
Also, I can only record raw 1080p (I want 1080p) in 5x, I have a Sandisk 120Mb/s 32Gb card.
I just wanted to know: Can I record 1080p 60fps without being raw or 5x?
Thanks!
Morning, I'm a new entry in the magiclantern world, I want to try to install the magic lantern firmware, I formatted a lexar card, upgrade the firmware from 2.0.0 to 2.0.3 and copy the ML file into CF lexar. Now I only put the Cf into camera and upgrade the firmware? right? and After instalation can I use every CF or only that with ML?
thank you for any answere
Fulvio
First page, first post. Follow instructions.
Top of page -> User Guide -> FAQ/Install Guide
Quote from: Walter Schulz on February 27, 2016, 08:57:52 AM
First page, first post. Follow instructions.
Top of page -> User Guide -> FAQ/Installation Guide
Ok thank you, I wanted only sure
I bought on amazon.de CF card Komputerbay 64GB 1066x and I have 92mb write speed - no lag and contious recording on 24p full possible resolution 1728x1152 (3x2) and 18 sec in 50p in 1728x~500 (I forgot exacly, this is ~65mb/s). You need to notice record 50p with connected preview causes frame drop.
Here my test movie RAW with color grading in Davinci Resolve.
https://youtu.be/fpEnfcjPBnM
Is it technically possible to crop the sensor at ratios other than 5x? I am curious because I wonder if the censor were cropped only slightly maybe we could bring the continuous recording resolution up to 1080p?
Data rate required for 1080p:
Vertical pixel x horizontal pixel x bit depth x frame rate / 8 = Byte/s
You can do the math. See? No matter which part you take, which part you omit ...
kamranjon, you can't do better than one-to-one 1080 crop. Anything else and you're diverting processor power into resizing the image.
Is a bit depth of 12 instead of 14 possible?
Don't know. But at time of writing it's 14.
But according to your calculation there, if 12 bit color depth were possible (the Digital Bolex shoots at 12 bit), the data rate would be low enough for 1080p continuous? Just making sure I'm doing the calculation right.
Quote from the FAQ (http://www.magiclantern.fm/forum/index.php?topic=11108.0):
"Dude, you should totally develop 10 bit raw recording. I could record full HD footage if you did!
That's nice. Here's a hint, we already tried, and you aren't the first person to ask. Try searching before asking anymore questions."
That's really interesting! Unfortunately searching for 12 bit raw recording on the forums returns zero results. What would be helpful would be the documentation on those attempts at recording 10 bit raw! I'd love to learn more about it :)
This has been already discussed, and it is not possible. The raw data cannot be processed at all by the DIGIC processor, even for discarding bits, the processor is not fast enough for such high data rate.
Here's (http://www.magiclantern.fm/forum/index.php?topic=5601.250) a discussion.
Here's a pertinent quote:
"Sigh, for the nth time...it's not possible since the Canon CPU's aren't fast enough to perform the necessary calculations. They can barely keep up with writing the data to a CF card as it is."
Hi all,
I'm new to ML, but I can't seem to find an answer by searching, so I'll ask here.
I have a SD to CF adapter for my 7D.
http://www.bhphotovideo.com/c/product/816112-REG/Digieffects_SDXCF_Extreme_SD_HC_XC_to_CF.html
I cannot get ML to boot from a 16Gb SanDisk Extreme (60Mb/s rated) card in this adapter. It works fine with my old Kingston 45x CF card. Is this a bug, a limitation in ML (can't boot from SD cards in adapters), or just something that will work with another SD/ CF adapter with ML?
FYI, when I try to load the ML firmware with the SD/ CF adapter, it starts to go, then the camera basically shuts off. It doesn't get to the load screen. Also, if I load the ML firmware with the CF card, turn it off, then try to turn the camera on with the SD/CF card installed, the camera simply doesn't turn on. But it's fine with the CF card, and can uninstall just fine.
Thanks for any information!
Jeremy
0.) Remove battery. Remove card. Insert battery.
1.) CF-SD-Adapters suck.
2.) Use MacBoot (OS X) or EOSdisk (Windows) to make card bootable. Wipe disk contents but do not format. Copy extracted nightly build contents to card and insert card into adapter and adapter into cam.
3.) If cam doesn't start up -> 1) applies.
Honestly if I were you @jjlee I'd rather get CF cards because why in the world would you want to use an adapter that would have to work its way through which I'm afraid won't allow you to get the most out of your precious 7D -- get yourself a decent CF card and KomputerBay 1066x 128GB works great on it afaik.
Hmm- interesting- thanks! I didn't think that the adapter would be such a red herring, but interesting to hear that it might be the issue. SD is simply easier to deal with since the MacBook Pro has a built-in slot, SD cards work directly with the iPad, my video camera/ audio recorder uses them, and they're smaller. I guess there's more going on in the adapter than simply changing the form factor.
Is there some reason that you're recommending the super fast CF cards? Can the 7D actually take advantage of that speed in some way? I've been shooting Raw+JPEG and not really run into any issues with my 45x CF cards or the SD cards with adapter regarding speed. I don't really do video on the camera as the live view focus seems extremely slow at best.
Thanks again!
Jeremy
I want to ask when approximately ml to 7d mark ii will release ... I can not wait ... hopefully quick release
Nobody is working on it. Nobody is planning to work on it -> Act like there will be no ML for this cam ever.
edit
Selftest.mo:
Should it work like this?
Starting Stubs API test in photo mode M (non-liveview) shows a black screen only. If I start it in LV I get screen messages. 650D shows screen messages in non-LV.
EDIT: Issue not exclusive to Selftest.mo. Same for Lua scripts. Running "Hello, World" script in non-LV shows a black screen. Press trashcan and message is there. LV will show screen messages (a lot, of course), too.
Stub API test:
Inconsistent results. Should it work like this?
- Test complete, 5747 passed, 2 failed.
- Test complete, 6384 passed, 5 failed.
- Test complete, 6545 passed, 4 failed
Have I mentioned lately 15 minutes forum timeout sucks?
That's an issue with the cameras that are normally used with the main display off. A simple workaround would be to switch to PLAY once we have something to print on the console.
What are the failed tests in the stub API? Sometimes the timer ones fail, especially if some other CPU-intensive process (such as LiveView) is running.
[Pass] f = FIO_CreateFile("test.dat") => 0x3
[Pass] FIO_WriteFile(f, (void*)0xFF000000, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)0xFF000000, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize("test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = (void*)_alloc_dma_memory(0x20000) => 0x409777e0
[Pass] f = FIO_OpenFile("test.dat", O_RDONLY | O_SYNC) => 0x3
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
_free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] buf = fio_malloc(0x1000000) => 0x422700c4
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000000
[Pass] f = FIO_OpenFile("test.dat", O_RDWR | O_SYNC) => 0x3
[Pass] FIO_SeekSkipFile(f, 0, SEEK_END) => 0x82000000
[Pass] FIO_WriteFile(f, buf, 0x10) => 0x10
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_END) => 0x81fffff0
[Pass] FIO_WriteFile(f, buf, 0x30) => 0x30
[Pass] FIO_SeekSkipFile(f, 0x20, SEEK_SET) => 0x20
[Pass] FIO_SeekSkipFile(f, 0x30, SEEK_CUR) => 0x50
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_CUR) => 0x30
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000020
[Pass] FIO_RemoveFile("test.dat") => 0x0
[Pass] SetTimerAfter(0, timer_cbr, overrun_cbr, 0) => 0x15
[Pass] timer_func => 0x2
[Pass] SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0xb2
msleep(900)
[Pass] timer_func => 0x0
msleep(200)
[Pass] timer_func => 0x1
[Pass] ABS((timer_time/1000 - t0) - 1000) => 0x1
[Pass] ABS((timer_arg - ta0) - 1000) => 0xa
[Pass] timer = SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0xb4
msleep(400)
CancelTimer(timer)
[Pass] timer_func => 0x0
msleep(1500)
[Pass] timer_func => 0x0
[Pass] SetHPTimerAfterNow(0, timer_cbr, overrun_cbr, 0) => 0x15
[Pass] timer_func => 0x2
[Pass] SetHPTimerAfterNow(100000, timer_cbr, overrun_cbr, 0) => 0x6440
msleep(90)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 100000) => 0x153
[Pass] ABS(DeltaT(timer_arg, ta0) - 100000) => 0x11f
[FAIL] ABS((get_us_clock_value() - t0) - 110000) => 0x2624
[Pass] SetHPTimerAfterNow(90000, next_tick_cbr, overrun_cbr, 0) => 0x644a
msleep(80)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x3
msleep(80)
[Pass] timer_func => 0x3
msleep(20)
[Pass] timer_func => 0x1
[FAIL] ABS(DeltaT(timer_time, t0) - 300000) => 0x26f7
[FAIL] ABS(DeltaT(timer_arg, ta0) - 300000) => 0x26bf
[FAIL] ABS((get_us_clock_value() - t0) - 310000) => 0x2734
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x191cc0
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x191c40
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x191c20
[Pass] bar => '*****hjkl;'
bzero32(bar + 5, 5)
[Pass] bar => '****'
t0 = *(uint32_t*)0xC0242014 => 0x10ebc
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0x4f6f4
[Pass] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x6
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x7
Date/time: 2016/05/04 09:44:07
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x8
[Pass] MOD(s1-s0, 60) => 0x1
[Pass] MOD(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x36ef8
[Pass] p = (void*)_malloc(50*1024) => 0xd0258
[Pass] CACHEABLE(p) => 0xd0258
m1 = MALLOC_FREE_MEMORY => 0x2a6e8
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x36ef8
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x2d70d8
[Pass] p = (void*)_AllocateMemory(256*1024) => 0x9777a0
[Pass] CACHEABLE(p) => 0x9777a0
m1 = GetFreeMemForAllocateMemory() => 0x2970cc
_FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x2d70d8
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x36ef8
m02 = GetFreeMemForAllocateMemory() => 0x2d70d8
[Pass] p = (void*)_alloc_dma_memory(256*1024) => 0x409777e0
[Pass] UNCACHEABLE(p) => 0x409777e0
[Pass] CACHEABLE(p) => 0x9777e0
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x409777e0
_free_dma_memory(p)
[Pass] p = (void*)_shoot_malloc(24*1024*1024) => 0x422700a4
[Pass] UNCACHEABLE(p) => 0x422700a4
_shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x36ef8
m12 = GetFreeMemForAllocateMemory() => 0x2d70d8
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[Pass] suite = shoot_malloc_suite_contig(24*1024*1024) => 0xbc850
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1800000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbc878
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1800000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x422700a0
[Pass] UNCACHEABLE(p) => 0x422700a0
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0xbc850
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1f80000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbc878
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1f80000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000064
[Pass] UNCACHEABLE(p) => 0x4a000064
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(64*1024*1024) => 0xbc850
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0xd
[Pass] suite->size => 0x4000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbc878
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x188c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x422700a0
[Pass] UNCACHEABLE(p) => 0x422700a0
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc8d8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1990000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42000064
[Pass] UNCACHEABLE(p) => 0x42000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc910
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3910000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000064
[Pass] UNCACHEABLE(p) => 0x4a000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc948
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x398c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5bf800e4
[Pass] UNCACHEABLE(p) => 0x5bf800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc980
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3a08000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x59f800e4
[Pass] UNCACHEABLE(p) => 0x59f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc9b8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3a84000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x57f800e4
[Pass] UNCACHEABLE(p) => 0x57f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc9f0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3b00000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x55f800e4
[Pass] UNCACHEABLE(p) => 0x55f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbca28
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3b7c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x53f800e4
[Pass] UNCACHEABLE(p) => 0x53f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbca60
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3bf8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x51f800e4
[Pass] UNCACHEABLE(p) => 0x51f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbca98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3c74000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4ff800e4
[Pass] UNCACHEABLE(p) => 0x4ff800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcad0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3cf0000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4df800e4
[Pass] UNCACHEABLE(p) => 0x4df800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcb08
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3d6c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4bf800e4
[Pass] UNCACHEABLE(p) => 0x4bf800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcb40
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4c000064
[Pass] UNCACHEABLE(p) => 0x4c000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4000000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0xbc850
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x14
[Pass] suite->size => 0x13700000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbc878
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x188c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x422700a0
[Pass] UNCACHEABLE(p) => 0x422700a0
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc8d8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1990000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42000064
[Pass] UNCACHEABLE(p) => 0x42000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc910
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3910000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000064
[Pass] UNCACHEABLE(p) => 0x4a000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc948
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x398c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5bf800e4
[Pass] UNCACHEABLE(p) => 0x5bf800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc980
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3a08000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x59f800e4
[Pass] UNCACHEABLE(p) => 0x59f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc9b8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3a84000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x57f800e4
[Pass] UNCACHEABLE(p) => 0x57f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbc9f0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3b00000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x55f800e4
[Pass] UNCACHEABLE(p) => 0x55f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbca28
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3b7c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x53f800e4
[Pass] UNCACHEABLE(p) => 0x53f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbca60
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3bf8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x51f800e4
[Pass] UNCACHEABLE(p) => 0x51f800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbca98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3c74000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4ff800e4
[Pass] UNCACHEABLE(p) => 0x4ff800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcad0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3cf0000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4df800e4
[Pass] UNCACHEABLE(p) => 0x4df800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcb08
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3d6c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4bf800e4
[Pass] UNCACHEABLE(p) => 0x4bf800e4
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcb40
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x5cec000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4c000064
[Pass] UNCACHEABLE(p) => 0x4c000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcb78
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x7c6c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4e000064
[Pass] UNCACHEABLE(p) => 0x4e000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcbb0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x9bec000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x50000064
[Pass] UNCACHEABLE(p) => 0x50000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcbe8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xbb6c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x52000064
[Pass] UNCACHEABLE(p) => 0x52000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcc20
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xdaec000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x54000064
[Pass] UNCACHEABLE(p) => 0x54000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcc58
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xfa6c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x56000064
[Pass] UNCACHEABLE(p) => 0x56000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbcc90
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x119ec000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x58000064
[Pass] UNCACHEABLE(p) => 0x58000064
chunk = GetNextMemoryChunk(suite, chunk) => 0xbccc8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x13700000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5a000064
[Pass] UNCACHEABLE(p) => 0x5a000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x13700000
shoot_free_suite(suite); suite = 0; chunk = 0;
EngDrvOut(LCD_Palette[0], 0x1234)
[Pass] shamem_read(LCD_Palette[0]) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(1000);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(1000);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
task_create("test", 0x1c, 0x1000, test_task, 0) => 0xd7200c8
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id(get_current_task()) => 'run_test'
[Pass] task_max => 0x68
[Pass] task_max => 0x68
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x9500090
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0x95202bc
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0x9540092
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
SW1(1,100)
[Pass] HALFSHUTTER_PRESSED => 0x1
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
EDIT: Thanks for the Play-trick. Now "Test complete, 5749 passed, 0 failed". Mission accomplished!
SRM memory test (5 minutes):
Able to take pics according to screen message.
Do you need anything from this test? There is a VRAMx.PPM showing some values.
OK, so only the timer ones. If you press PLAY right before the test starts, they should be fine.
(I should probably update the test so they only run in this mode)
Does the "Delayed Start" script work on a 7D? I'm using April 17, 2016 nightly. Camera in "M" mode and Global Draw is Off.
With the movie mode enabled, I have tried it with normal movies, raw (MLV) enabled and raw_rec enabled. It doesn't appear to work.
Steps taken:
normal movies
Switch camera into movie mode
Set Delay amount value
Set Stop After value
Highlight the run option and press play (nothing happens), press Set (nothing happens)
Pressing the start/stop recording button just starts recording without any delay.
Raw movie modes
Switch camera into movie mode
Enable raw video mode (mlv or raw only)
Set Delay amount value
Set Stop After value
Highlight the run option and press play (nothing happens), press Set (nothing happens)
Pressing the start/stop recording button just starts recording without any delay.
the lua module is loaded and appears to work. I can access the calculator, editor and play pong.
Fundamentally, even though I can set the required run time paramaters, I don't seem to be able to get the script to actually run. Am I missing something or just doing it wrong?
You can try it again after I'll merge lua_fix (it didn't work on 5D3 either). I still have to run some tests on it to make sure it doesn't break other core features I've tweaked.
@a1lex
Ok, thanks for the reply.
Hey guys,
I was wondering if there are any significant improvements to the 7D ML that have happened over the last year and a half? I am running a build from October 2014 and because it can run raw w/ audio and is rock solid I am hesitant to update, but I do not know if there have been any image quality improvements or any other must-haves.
I've looked at the last several pages here and in other places but there is so much discussion it's hard to pin down exactly where the software sits right now.
Thanks!
Backup card's ML directory and Autoexec.bin and *.FIR (or just rename them) and copy extracted nightly build contents to card. Done: You have installed latest nightly build.
Rollback: Delete ML directory and Autoexec.bin and ML-SETUP.FIR and copy/rename from backup/copy.
All the changes: https://builds.magiclantern.fm/jenkins/job/7D.203/changes
Hi, I'm obviously missing something very simple. I can't seem to get ML to install on my 7D that has 2.0.3 installed.
I've read most all of the threads here and it seems to fail to install.
What I've done:
1. Formatted card in camera
2. Copied nightly build to card
3. Run firmware update
The update takes all of 3 seconds and says restart camera. I do so and the menu is the same. Nothing new is available. The Firmware does report the ML firmware. So, I remove the card that I updated from and put in a card to record to. Now my firmware is back to 2.0.3. I thought that maybe I had to put the ML files on every one of my cards. That might be the case. But, even with the ML file card in my camera, I have no new features.
Then, I made a card bootable with EOSCard and did the same thing. Same results. Nothing updated or changed in my menu or features.
What am I overlooking?
Top of page -> User Guide -> Install Guide/FAQ
I know, I did read a lot but somehow missed the "push erase button" step. I've found that and it now works. Thanks for tolerating a newbie.
I going to download ML to my 7d! Is it still only working with canons 2.0.3 firmware? or is it possible to use the 2.0.5 version?
@_OLLE_
ML does not work with v2.0.5.
Quote from: Ottoga on May 05, 2016, 03:05:11 AM
@_OLLE_
ML does not work with v2.0.5.
Ok thanks! :'(
hi, again! My installation of nightly build from 30 april was sucessful, but I think it missing some features! The maximum MLV.rec is only 1600 and there is now benchmark! Now I wonder if you guys know a stable and good build for video work with ML!?
Best regards Olle!
Hello! I have a Canon 7D Magic Lantern installed and running smoothly. One day without realizing pulled the CF memory without turning the camera off , thereafter the camera was turned off and has not returned to work more . It is as if dead , not turn on lights, sounds does nothing . She's dead, you know I can do ? Thank you!
I just ordered a Canon 7D from Amazon (just like new) and don't know what firmware version it has til it arrives. My question is this, what if the firmware for the camera was already updated to a higher version than 2.0.3, can I then re-install a lower firmware version, in other words is 2.0.3? Thanks.
Quote from: plasty82 on May 11, 2016, 09:55:05 PM
Hello! I have a Canon 7D Magic Lantern installed and running smoothly. One day without realizing pulled the CF memory without turning the camera off , thereafter the camera was turned off and has not returned to work more . It is as if dead , not turn on lights, sounds does nothing . She's dead, you know I can do ? Thank you!
Remove battery, remove card.
Insert battery only.
Startup cam.
Startup okay? If not: LED blinking? LCDs working?
Report back.
Quote from: Roberto Mena on May 12, 2016, 03:47:38 AM
I just ordered a Canon 7D from Amazon (just like new) and don't know what firmware version it has til it arrives. My question is this, what if the firmware for the camera was already updated to a higher version than 2.0.3, can I then re-install a lower firmware version, in other words is 2.0.3? Thanks.
Yes you can! I did just that a week ago!
Thanks _OLLE_ !
Is anyone else having a problem using the auto restart recording feature on their canon 7D. Mine is restarting without a problem but I cannot stop recording by hitting the record button because it just restarts again. The only way I can get it to stop is by turning off the camera. It did it on an older build but I just updated to magiclantern-Nightly.2016May16.7D203 and it still is not working right. Any ideas?
Hey pedrotyler,
This is occuring with my 7D as well. Have always had this issue with ML installed since last summer. I just turn the camera off, which seems to be the only solution I've found as well.
- Paul Harwood
You have to hit the button a second time. The problem occurs when your record a big file, because the camera pops up that message about the file being split because it's too big. That message triggers the restart of the recording. If you push the button again right after that restart, the recording will stop.
Hey sgofferj,
Can you elaborate? I don't know which button you're talking about. This happens to me regardless of a big file or small file. Thanks.
- Paul Harwood
I meant the start-stop button :).
That's odd that it happens to you with any file size... For me it works perfectly fine for short recordings.
Hey sgofferj,
When I hit the start stop button it records, but when I hit stop it keeps recording. I'll have to experiment with the double tap method :)
- Paul Harwood
Is it possible to install the eos7d-v203-win.zip even though I already went to v2.0.5 or will it brick?
Top of page -> Downloads -> Download Nightly Builds -> 7D.203
Read and follow instructions.
Does anyone know what the 7D's dynamic Range is for shooting RAW/MLV video? According to what I have read online the 5DIII can do 13 stops at this point? And so can the 7D but only on RAW photos, so what is it with video?
Thanks.
Run raw_diag.mo to find out (use simple silent pictures, they are the same data as raw video).
More info here: http://www.magiclantern.fm/forum/index.php?topic=10111.0
13 stops is only possible with dual ISO.
I started playing with the Auto White Balance feature on ML and I like it because it also seems to do auto exposure ... what I don't like though is that its auto exposure messes with the shutter speed also. I don't mind the auto exposure messing with ISO's but is there a way to do this keeping the shutter speed at 1/50? Thanks.
Quote from: Roberto Mena on May 27, 2016, 12:15:41 AM
I started playing with the Auto White Balance feature on ML and I like it because it also seems to do auto exposure
No, it doesn't.
If it does, it's a bug.
Didnt want to raise a bug in the bug reporting page as I'm fairly sure its already been seen but i thought i should still say something, just in case.
My 7D is crashing after using raw video. It started happening after i did a fair bit of shooting. But it seems to happen at random and normally fairly soon after starting the camera up. Less than a minute.
At the moment Im assuming its Raw or at the very least one of the associated modules as turning them all off seems to stop the crash. Ill experiment later.
When it crashes the screen shows a random colourful pattern and the camera becomes unresponsive. Turning the camera off by the button doesn't turn it off. I have to remove the battery to get it to reset.
When it starts up Magic lantern says it didnt shut down properly and wont load the modules. And doesn't appear to crash then.
This is the may16th build...
Is this a known issue?
Quote from: Nutsy on May 27, 2016, 01:58:11 PM
one of the associated modules as turning them all off seems to stop the crash
Could be lua.mo. If you have lua loaded, it's most likely causing the problem (lua is memory hungry and all of the scripts load by default). Otherwise it could be just having a lot of modules loaded in general. Does the crash still happen if you load only the raw recording module?
Managed to narrow it down to the mlv_raw module.
Maybe the installation has corrupted... Might redownload and copy on to the cf card.
Hi - I am having problems installing ML - installation of magiclantern-Nightly.2016May16.7D203.zip = after restart 7D is dead - comes alive after card and battery removed but dies the moment the card with ML is reinserted? Help
Format card in cardreader.
Format card in cam.
Redo installation.
If it is not working: Try another card.
Report results.
Hi Walter,
I Formated card in cardreader.
then Formated card in cam.
Redid installation.
Same result Tried another card and then directly another after that card (both same result = both Sandisk Extreme 60mb/s 16GB UDMA)
I will try a Sandisk 30MB/s (my photography disk - last disk I have)
Will report if anything is different or not.
Hi Walter,
the 30mb/s card also did not work it failed even before the installation could start - gave me this error message in yellow on the camera screen:
update file error
please check memory card
and reload battery and try again
Froze on this screen until battery was removed
- Any Idea how to move forward?
I am stuck.
Format card again in cardreader and cam.
Reset camera to factory defaults. Don't forget C.Fn settings!
Restart cam in photo M mode.
Retry installation.
Post results.
Hi Walter,
Reset camera to factory settings -(cleared all settings inkl. C.fn settings)
Reinstalled Canon Firmware 2.0.3
Reset date and time to today
Cards Formatted in Card reader
Cards Formatted in Camera
re-downloaded Nightly build (magiclantern-Nightly.2016May16.7D203.zip)
unzipped and copied contents to CF cards Root
Run firmware update on cam - everything goes smooth
restart camera prompt (green)
Camera led flashes (probably because of the uninstall counter?)
when camera is turned off - sensor cleaning message appears along with restart camera prompt (this time red)
Then Camera turns off and won"t turn on unless battery and card are removed -
It turns back on as long as ML card is not inserted/reinserted
when ML card is put back in the whole battery out procedure needs to be repeated before it turns back on
Help...
Turn off cam and remove battery.
Insert battery and card.
Press SET button and turn on cam.
Results?
Hi Walter,
Turned off cam and removed battery.
Inserted battery and card.
Press SET button and turn on cam.
Results = Camera is still dead
I am willing to dance around the table at this point if you think it might help!
No dancing involved. Yet.
Backup/rename autoexec.bin and replace file with autoexec.bin found in first chapter of http://www.magiclantern.fm/forum/index.php?topic=2296.0
Remove battery. Insert card. Insert battery.
Cam will startup without power on! If able, of course.
Is this one working?
Remove battery and remove card.
Hi Walter,
Yippy yay! that worked - screen powered up and showed text etc.
so what next?
Status:
Cam's bootflag set: Ok!
Card bootable: Ok!
Test:
Restore "original" autoexec.bin (= the one in Nightly Build).
Delete contents in ML\Settings
Check contents in ML\LOGS
- Are ROM0.BIN and ROM1.BIN presents? File sizes for each?
Retry startup. I suppose it will not work. Report back.
Hi Walter,
both ROM0.BIN + ROM1.BIN present
ROM1.BIN = 16,8 MB
ROM0.BIN = 16,8 MB
ML\Settings -can't find?
Restored - autoexec.bin
retrying now will report - results
Hi Walter,
nope no luck.
still dead = like you suspected
as I wrote earlier I could not find the file/folder ML/Settings
Yes, ML\Settings will be written if ML startup/shutdown is successful and that's the problem.
Existence of ROM0.bin and ROM1.bin does tell ML can write files during installation and I'm out of options.
Do you have log files in card's root or ML\LOGS?
Dr. Unbrick (aka: a1ex, the person actually able to dig into code/logs/ROM dumps) told he is occupied with other stuff at the moment. Please post your problem in our Camera Emergency Department http://www.magiclantern.fm/forum/index.php?board=45.0 and wait for his return.
Best of luck! I'm out!
EDIT: One last ... not that optimistic but try to startup with C-modes dialed.
Hey Walter,
thanx for all the time and effort -
@KingKon -- I think this may be worth the try...
Since you were the original owner of this 7D and previously had v2.3 installed in the past. Why not try re-installing v2.3 and then run the uninstallation process (rerun firmware update from Canon menu and wait for the timeout after 60 seconds) and hopefully that will uninstall the good old v2.3.
If so, then you should be able to go ahead and run the latest nightlies with no problems. Please let us know what you have discovered when you can!
? There is no v2.3 for 7D.
And the only thing "uninstall" does to the cam is setting/unsetting cam's bootflag. It doesn't reset other settings.
Okay then I assumed wrongly after reaching out to him via PM earlier. My apologies for the misunderstanding. I guess I'm just rather perplexed by this semi brick of his 7D.
BUT it just sounds like once he loaned his 7D to a friend and "didn't want" ML which then he decided to format the card thinking he was uninstalling it. But obviously that doesn't work that way, right?
In other words maybe he just needs to figure out which older build did he last used in order to revive it somehow?
Could that be the culprit here?
Indeed it doesn't hurt trying an old build. Not that optimistic but here you go:
https://builds.magiclantern.fm/jenkins/job/7D.203/
Any build with FIR included should do. #91 for example.
https://builds.magiclantern.fm/jenkins/job/7D.203/
Not to distract from the current trend in the topic, but are there any new 7d builds coming? Hopefully with some bug fixes? 3x crop function? any other new feature?
Unless im mistaken the latest build is still 16th may?
Hi Walter,
thanx for the links:
I found the old ML files (magiclantern-Nightly.2014Aug02.7D203) tried the unistall - no luck got this message:
update file error
please check memory card
and reload battery and try again -
any other suggestions - should I try dancing now?
Please format card in cam. Take card out and use computer to include ML files on card. Put card back into 7D and run firmware update from canon menu.
Report back when you can.
Stop!
Kingkon: Please clarify! You are able to startup cam with ML enabled card inserted?
Dear Walter & DeafEyeJedi,
Status report:
I managed to run ML magiclantern-Nightly.2014Aug02.7D203 - and did an uninstall with this version(magiclantern-Nightly.2014Aug02.7D203) - seemed to work.
Then ran ML magiclantern-Nightly.2016May16.7D203 - and managed to get to where I was when I started = Semi Brick!
camera works as long as I don't insert card with ML magiclantern-Nightly.2016May16.7D203.
So Logic says: Unistall magiclantern-Nightly.2016May16.7D203 and Reinstall the one that worked - magiclantern-Nightly.2014Aug02.7D203 -> a lot of formating in cardreader and in cam and loading and reloading of files onto cards - in case error lies with the card...same result no matter which card
Then Tried to run the process and I keep getting the same message:
update file error
please check memory card
and reload battery and try again
Oh man I sound like a stuck record!
Sorry Chaps - she is still a Semi Brick...
Any other suggestions?
Follow this procedure:
Remove card, remove battery.
Wipe ML directory and autoexec.bin from card.
Copy extracted nightly build content (2014Aug02) to card.
Insert battery.
Insert card into cam and startup.
Q: Is the camera starting up and are you able to access Canon and ML menu?
If not: Report back
If able: Delete ML directory and autoexec.bin from card.
Copy extracted nightly build contents to card (2016May16) to card.
Insert card into cam and startup.
Report back results. (Do *not* try to install/uninstall anything)
Hi Walter,
quick Question:
Before I copy the nightly build onto the card - should I format the card in camera or should I skip this step?
Hi Walter,
Okay I am impatient - so I went for the version with Cam format before and first tried to just run ML with the card in cam (no install) but nothing - like no ML is installed so I tried running the firmware update/install - that just gave me the good old:
"update file error
please check memory card
and reload battery and try again"
message - so I removed the battery and wrote you this message -
Without following this too closely, it sounds to me like your camera runs the old 2014Aug02 build just fine but hangs/crashes when booting the newer 2016May16 version. If so, try this (might take a while...):
- Get 2014Aug02 installed and working again.
- Turn off camera, remove battery and card.
- Put card in PC. Delete ML directory and autoexec.bin from card.
- Copy 2016May16 ML directory and autoexec.bin onto card (don't format or anything else).
- Replace battery, insert card, turn on camera. Presumably it will fail to start again.
- Now go back and repeat from step 2, except try a build from e.g. mid 2015 at step 3.
- If the build works, go back to step 2 and try a newer build (e.g. from late 2015). If it fails, try an older build (e.g. from early 2015).
Once you narrow down exactly which build introduces the problem it should be easier for a developer to figure out what's wrong.
Also, you shouldn't have to reload the firmware. This was only necessary before the autoloader was perfected for the 7D.
@KingKon:
There are three things ML needs to startup:
- A camera with "bootflag" set (that's the only change done to cam during installation/uninstallation)
- A bootable card (that's done by using tools (MacBoot/EOScard or during installation)
- ML files and directories on card
Uninstall/install procedure is not necessary after first install: You have a bootable card, a cam with bootflag set. To switch from one Nightly Build to another just replace the files on card.
That's all.
By formatting card in cardreader card will become non-bootable. So don't format until advised to do so.
To put things together:
Old Nightly Build works without troubles.
New Nightly Build stalls cam.
You can try other builds between those to determine which change is the one causing your problem
or
just wait for a1ex to hunt down the bug.
Hey I have some problems with my 7D.
I just installed for the first time yesterday ML on my 7D and my first impression was "Wow!".
But then I realized that something is a bit weird.
1. The Live View when taking Videos is pretty dark. First I though it is because of the LCD Brightness, but it is not. Even when I make the aperture to 3.5 and exposer time to 30, the picture is still very dark, even if I am in a lighted room. When I turn the ISO up to 900 it is okay, but that is not that what I want. ISO should be low because I don't want some dirty noise in my video.
So I checked the Video mode in my 700D with Canon firmware if it was really not ML's fault. I set the 700D also to f3.5 and exposer time 30s, but Iso to 100 (same room, same light, same lens). Here the preview picture was very bright even with low ISO.
So what is wrong with my magic lantern that the Video mode is so? If I am in the picture mode to make pictures, everything is alright, this problem only appears in Video mode.
And yes even the recordings on the pc are then very dark if I record with ML.
2. Is it normal that the camera heats up very quick? The display tells me that the temperature is 49 Degrees (Celcius).
3. When I use follow focus function, sometimes ML tells me that the focus was not saved and then my camera freezes. Normal or not?
Thanks for your help.
Hi Walter and DeafEyeJedi,
I bought a new card reader and that solved the problem...go figure.
thanks for all the patients and help - yeay to Magic Lantern.
running ML May 16 and all looks fine.
:)
@KingKon -- You positively sure that the card reader was actually the culprit in here for your 7D's semi brick?
At least you got it working and able to use the latest nightly on it. Much credit actually goes to @Walter Schulz.
Hello there,
I am trying to install ML on my 7D (mk1). That works well, except that the card led keeps flashing forever. Now the instructions are clear enough re the canon firmware version, but even after downloading and installing firmware v2.0.3 via the ML download page from pel.hu, the issue remains. Not surprisingly, for it tested byte-identical to the one I had from Canon. What am I doing wrong? I have used build 2016Jun137d203.
thanks!
Have I said something wrong, or is there nobody here?
Reset cam to factory defaults. Reset c.Fn settings.
Switch cam to photo mode M.
Insert card into cardreader and format it there.
Insert card into cam and format again.
Copy Canon firmware file 2.0.3 to card and run firmware update.
Delete file from card.
Download nightly build zip once again.
Expand zip and copy extracted files to card.
Redo installation.
Report back.
ico, it is "normal" that the card LED flashes every x seconds when Ml is loaded. I don't like it either, but there's nothing one can do but uninstall ML.
http://wiki.magiclantern.fm/faq?&#why_is_the_led_blinking_every_5_seconds
A lot of sites make mention of ML supporting headphone monitoring on the 7D however the ML site doesn't show the as supported.
At this time is it supported or it may never be?
I am about to buy a used body and debating between 60D and 7D and this is my sticking point.
there is no sound monitoring to headphones on 7D, at least in nightly builds or elsewhere that I would know of.
on 60D vs 7D, the major difference form video perspective is CF vs SD cards (7D CF -> can shoot in RAW, SD to slow) and 7D has full resolution always on HDMI, important for external monitoring. I had the same dilemma, chose 7D (there are more + to it than I mentioned), audio monitoring can be solved with a http://www.juicedlink.com/ preamp that has headphones out.
I have had some serious issues with 2,5k raw recording on my 7D. It happens in almost every clip. I post a picture so you guys can se what I mean ( look at his face!). What could be wrong?
(https://farm9.staticflickr.com/8777/28083471000_9660d33c38_b.jpg)
_OLLE_,
The processor is probably getting overloaded. I used to get that result ("frame tearing") when I used the grayscale preview (for true framing). I haven't used it since and haven't had the issue.
Okey thanks a lot @Frank7D! So you recommend me using the standard canon 5x crop preview?
Yes, but of course it is a crop of the actual frame. I use the greyscale preview to check the framing and turn it off before I begin recording.
Recently out of every 5 or 7 takes I shoot with my 7D (MLV), the footage comes out with a green tint to it, even though I shoot with VisionColor's flat picture profile. Anyone have any idea how to fix this or what is wrong? Thanks.
Roberto Mena, I don't know what is causing that, but a picture profile will not affect raw footage.
Frank7D, I know that a picture profile wouldn't effect raw footage, I was just mentioning it to help people assist me with troubleshooting my issue.
@Roberto_Mena
Some more detailed information will make it easier for the ML community to assist.
e.g: Detailed camera settings, ML Settings, Modules loaded etc as well as a sample of the affected footage.
Also, have you reviewed the 26 results returned from search on "Green Tint" within the forum? They may shed some light on the what the cause may be.
hi and hello from Malaysia. I just got my refurb 7d and i found out that it has a firmware of 2.0.0 version. i managed to get it updated to 2.0.5 and after that i realized that ML doesnt support the 2.0.5 version. I successfully revert it to 2.0.3 and install the latest ML in it. Everything seems ok and i tried out a couple of features that i liked very much like the focus peaking, magic zoom, and trap focus. Previously i used it on my t3i and there have been no problem at all. Now with my 7d, whenever i tried to use the follow focus feature, my 7d got freeze. All of the buttons are dead including the power button. Scared shitless after that. I removed the battery and wait for a couple of sec and insert it back and it came to life. i tried it again on the same feature and it happened again. So maybe i can get any suggestions or help from u guys about the problems. Many thanks. And i am sorry for my english. Thanks again.
Prefs tab -> Config files -> Restore ML defaults.
Retry and report.
Hi...i already restored ML to its default state. It seems like the problem is still there. I am using a Canon efs 24mm stm lens with my 7d. Whenever im using the follow focus, my camera seems to semi brick with all the buttons are dead. Except the liveview is still running like normal. I have to remove the battery again for few seconds. Is there any other option to overcome this? Or i need to reinstall it again? Thank you.
Reinstalling ML is pretty much doing nothing concerning settings.
You may restore cam's factory settings. Don't forget c.Fn settings ...
If it doesn't work:
Please describe in detail the steps to reproduce your problem.
Hi Walter
I'm buying a new Dslr and was wondering which is better for video recording after installing ML !!
700d, 7d or 60d .... I know it's a silly question but I really need the help of a Pro ...
Thanks in advance .
I'm not a pro ...
Raw video or canon h264 video? For raw video (on a budget) I would go for 7d. For h264, 600D/60D if audio controls are important. Otherwise 700D. Also not a pro...
Hello .
I'm new in the forum. First of all I really thank and appreciate all of you who give your time and effort to make ML.
I recently got a used Canon 7D and wants to install ML. It is running 2.0.5 firmware. I tried to downgrade it to 2.0.3 in order to run ML. So I downloaded that version from ML link, extracted the file and copied to the root of my card.But when I tried to run the update process, screen turns black and top screen turned off. Some seconds passed, then minutes.... nothing. I switched to Off, then On, and nothing. At this point I started crying for my camera... I talked the battery out, inserted again, turned on and nothing! After that I take out the memory card, inserted again, and a message appears: "firmware file not found". Don't remember exact message but it told me to try again after reload battery.
I searched for this issue but didn't find anything. Do you know what could it be the issue here?
Thanks in advance and sorry for my English.
Format card with a cardreader. Then format in cam. Copy firmware file to card. Retry and report.
If it doesn't work: Try another card. Small one (1-30 GB) will do.
Ok, I will try. Could it be the reason that I'm using a SD card within a SD to CF adapter instead of a CF card?
I would like to know if there are plans for a nightly build for 2.0.5 firmware?
Thnx for your help Avenger ...
Sent from my iPad using Tapatalk
I am using canon 6D. whin i try to copy the setup of magic lantern through card reader always saying that this card is protected .i slide the swithin the card but always the message is coming..why .plse reply
Try another cardreader.
Quote from: wizerd on August 09, 2016, 06:17:06 PM
I would like to know if there are plans for a nightly build for 2.0.5 firmware?
If I remember correctly there were no significant changes between 2.0.3 and 2.0.5
Not sure why it is not build for 2.0.5. Maybe something internally changed that requires a lot of work?
It's a lot of work even if there are only minor changes.
If a firmware build contains only insignificant changes (nothing to write home about) there is no need to dive into the firmware dumps to find out where Canon's compiler put all the stuff this time.
so what is someone to do if they have 2.0.5 already installed and wants magic lantern to run, when canon states you can't revert back to 2.0.3 and doesn't offer that version anymore even if there is a way to revert back?
http://pel.hu/eoscard as linked in Top of Page -> Downloads -> Download Nightly Builds -> 7D.203 and read. And you may also want to read User Guide -> FAQ/Install Guide.
I shot a intervju earlier this week but the in camera sound (mlv sound) stoped after about a minute and the clip it self is around 5 minutes! What could it be??? I use the mlv.rec mlv.sound and mlv.play btw!
You transferred all files (*.M00, M01, ...) to your computer?
Quote from: Walter Schulz on August 13, 2016, 12:28:15 AM
You transferred all files (*.M00, M01, ...) to your computer?
Yes!
I also noticed that the raw file is around 7000 frames and the dng folder form MLVFS just contains around 2000 frames! What´s wrong?
I went to a concert the other day, where they played Beethoven and Schubert.
The "Full res silent picture" on the 7D saved my day !
No shutter release noise and no mirror slapping. Awesome feature!
Thank you very much ML team !!
I haven't played around with the various settings to get the most out of it, but I definitely will be digging into this.
Canon Amateur, if you don't mind my asking, what build did you use?
The latest Nightly build available at that time - magiclantern-Nightly.2016Jul09.7D203
I'll post my settings later when I get home.
Hi.
I've just saw that maybe ML is available to Canon 7d Mk2: magiclantern-Nightly.2016Aug15.7D203.zip
Is this for real? Or this build is for 7D Mk1 ?
Thanks
Cams with ML (Nightly Builds): Top of page -> Downloads -> Download Nightly Builds -> Select your camera.
Or
https://builds.magiclantern.fm/jenkins/
Dear Walter Schulz,
Sorry. Maybe I'm very noob. My question is 7D203 means 7D software version 203 or is a firmware to canon 7D mk2?
Thanks
Quote from: dawn_to_dusk_ on August 17, 2016, 05:06:36 PM
Hi.
I've just saw that maybe ML is available to Canon 7d Mk2: magiclantern-Nightly.2016Aug15.7D203.zip
Is this for real? Or this build is for 7D Mk1 ?
Thanks
7d203 is magic lantern for 7d 2.03 firmware.
Hello Guys.
I´m pretty new to ML even though a mate of mine is using it for quite a while now (I´m shooting photos / raw only - but find the features pretty nice so I have just installed ML on my 7D).
My Question:
-What temperatures are you having while taking raw pictures?
-Is it normal that the right side of my Camera body where the battery grip sits in became pretty warm in just a few minutes (ML showed 52°C) ?
-Im using the recent Nightly Built from 06.09.2016
Thank you for your answers!
Quote1728x692 48 fps slow mo. But wait a minute... When I play it back, the footage is normal aspect, no stretching required! I'm kinda running on no sleep in 2 days, I need someone to confirm this ASAP. I noticed when I set the cam to 1280x720 60p, and set the fps override to 23.976 exact fps, the liveview display was stretched vertically, so when recording it and playing it back records it in normal aspect! Timer A under 23.976 exact is 422 (FT -76). So I set the fps to 48, and Timer A back to 422. Mlv settings-
1728x692
3:2
GD Off
Canon preview
256 MB warmup
SRM On
Hacks on
4 buffers
Reserve on
Global Draw off
Expo override on
Rokinon 35mm manual cine lens
After messing with it a little bit more, the black and white levels get all wacky sometimes and the exposure is super glitchy. At first, I noticed this while testing out different settings in 640x480 mode, going to do some more tests soon as I charge my battery.
:edit: Yeah definitely a bug in the fps override control. I just downloaded the latest nightly, same thing. How exactly does fps override cause LV to stretch? Or is this a new feature I completely missed?!
:edit2: Ok, just figured out that this bug has been in the nightly since 7d fps override was implemented.
:edit3: To fix this issue, Timer A needs to be set to 498 (FT +76) for 23.976 exact and 440 (FT +10) for 60 exact.
I have confirmed this works! Thank you so much N/A!
I have provided a Google Drive Link to a folder with screenshots, pictures, and videos showing the beauty of this:
https://drive.google.com/drive/folders/0Bz5n0qYxIkVOMnJMeWhkU3pMVjQ?usp=sharing (https://drive.google.com/drive/folders/0Bz5n0qYxIkVOMnJMeWhkU3pMVjQ?usp=sharing)
The videos are of my cat in my room, handheld at 50mm. Sorry for the shakiness, I just wanted to test this out with the time I had. I was able to record for 15 seconds.
If anyone has any questions, or can't get to the link please let me know. Thank you to all the Magic Lantern Developers, this is truly awesome!
- Paul Harwood
Ive just bought a 7d markii and i didn´t realise that ML wont work?? is it impossible or will it going to work some day?
It's rather "some day". ETA can't be given.
sorry don´t no what you mean ETA?
It means "Estimated Time of Arrival."
Hello ML Community,
As regards to the 7D 48.033 fps no squeezing bug, here is a link via Google Drive with clips that have sound working, water pouring for testing in your editing applications, and screenshots of how to export properly via SmartImport2 Script in After Effects. For 1728 x 692, in SmartImport2 it is necessary when resizing to keep the width at 100%, but the height at 60%
Link: https://drive.google.com/drive/folders/0Bz5n0qYxIkVOZ2d4Z1hDVWlfUXc?usp=sharing (https://drive.google.com/drive/folders/0Bz5n0qYxIkVOZ2d4Z1hDVWlfUXc?usp=sharing)
I hope this helps anyone interesting in using this great feature!
- Paul Harwood
Yay, I've just bought a reasonably priced near-mint condition 7d1 to replace my 60d which failed with 330k shutter cycles. Are there any active devs left on the 7d1 except for Alex, or has the world moved on by now?
General comment: I have to say I'm impressed, the 7d1 has everything I miss from the 80d for my photography (sturdy shutter, af point expansion, spot af) and most modern updates are jpeg- or movie-centered an don't matter to a still raw shooter like me. Only the lack of suport for rt flashes is unfortunate. As for the sensor, dual_iso fixes the low dr, for most of my lenses 18mp is 'nuff and if I'd want to have better iq I'd rather put my money into a 2nd full frame camera like a used 5d2/3. Or wait for 5d4's dual pixel tech with bokeh and focus point shift to make it into the lower realms.
Quote from: Macke1 on October 01, 2016, 08:27:02 PM
Ive just bought a 7d markii and i didn´t realise that ML wont work?? is it impossible or will it going to work some day?
This is the 7d1 thread, someone please change the title, here's the 7d2 one: http://www.magiclantern.fm/forum/index.php?topic=13746.0
Quote from: dawn_to_dusk_ on August 18, 2016, 01:52:28 AM
My question is 7D203 means 7D software version 203 or is a firmware to canon 7D mk2?
Even a minor fw update with just the Korean strings changed needs someone to find all hardcoded stub addresses in the Canon fw again which is a boring and lengthy pita. For what is changed this is definitely not worth it, just downgrade to 2.0.3
Firmware Version 2.0.5 incorporates the following fix.
1. Fixes a phenomenon in which the image files cannot be transferred using the FTP protocol via USB cable after the EOS 7D camera has established a wireless connection to the Wireless File Transmitter WFT-E5 (A/B/C/D).
hi guys! what happens if I connect my 7D to external monitor via hdmi mini whyle using magic lantern? will it works? I wish too see my liveview on a biggest screen because I need help to focus. I hope that if connecting 7D to an external monitor I will be able to see magic lantern global draw features (such as focus peaking) on the second display. let me know please! :)
@Brawl -- Sure you can use Global Draw (such as Focus Peak) while using an external monitor (though it wont be as pretty) and you also won't be able to see anything on the LiveView LCD display (only 5D3 is capable of doing this while running ML) as you can see what it looks like below on the 7D...
https://vimeo.com/192498227
Your noise levels look a bit too high - may I see a silent DNG taken with the same settings?
The spike on the histogram at 00:21 is definitely not normal. Most likely this issue (https://www.magiclantern.fm/forum/index.php?topic=13817.0) - something to be aware of when using an external monitor.
Sure, will do -- the video posted above was shot in a living room at the house before leaving for work earlier this morning.
Now while I'm at work and have the 7D w me not sure if this would be problematic since it's not exactly the same scenery ... Took a few Silent DNG's while in Video Mode mv720 (did you want me to also take some while in Photo mode w LiveView -- also does FRSP apply in here or no need?) and here are these files below and yes they are in the same settings from earlier.
https://mega.nz/#F!i9V3EJTb!MVpTR55q-_nb6TDZguIgqQ
Hm, different column offsets at higher ISO in optical black area. Don't remember seeing this on other cameras.
If these don't appear in the final image (can't tell from this sample), the only side effect would be overestimating the noise levels (which translates to underestimating the actual dynamic range on the raw histogram).
If they do, a dark frame should remove them.
an unofficial test build w/o any warrants for those who want to give raw_rec.mo a try on 7D with 10bt:
https://drive.google.com/file/d/0B9Mu66yg5QzRSXFVREkzZkYwYzQ/view?usp=sharing
have fun.
Feedback for this better provided in the official development thread for bit depth reduction for not becoming offtopic:
http://www.magiclantern.fm/forum/index.php?topic=5601.msg175495;topicseen#msg175495
And if there' s already test buildsfloating around elsewhere then I missed it and you can sratch this.
@DeafEyeJedi thank you very much for your video.
when you shoor raw video and you are using the external monitor do you get tearing on your footage? because the link that @alex has posted (https://www.magiclantern.fm/forum/index.php?topic=13817.msg173472#msg173472) seems to suggest this problem, that if we use an external monitor with raw video on 7d could cause footage ruined by tearing. the solution seems be to force the low resolution for hdmi output. do you need to use this technique? thx!
FYI: Canon released firmware 2.0.6 for 7D.
Also there's 1.3.4 available now for 5D Mk3 :P
Probably other cams got an update, too.
Quote from: nikfreak on November 26, 2016, 11:54:18 AM
an unofficial test build w/o any warrants for those who want to give raw_rec.mo a try on 7D with 10bt:
https://drive.google.com/file/d/0B9Mu66yg5QzRSXFVREkzZkYwYzQ/view?usp=sharing
have fun.
Feedback for this better provided in the official development thread for bit depth reduction for not becoming offtopic:
http://www.magiclantern.fm/forum/index.php?topic=5601.msg175495;topicseen#msg175495
And if there' s already test buildsfloating around elsewhere then I missed it and you can sratch this.
It's working for me ! Global draw off / Preview Canon / FPS overidde 24.
MLV doesn't play in 7D but it's ok when transcoded to DNG in PC.
50 sec in 2560 x 1200 pixels (10 bit) :)
Great to read this. Probably you will be able to get a little bit more resolution once a1ex makes the x5-zoom from crop_rec (http://www.magiclantern.fm/forum/index.php?topic=17021.msg174866#msg174866) available. I am unsure how much it can be vertically but something
around 1300px could be possible?!? Maybe more?
Quote from: a1ex on November 14, 2016, 12:05:07 AM
Found a way to center the raw buffer and Canon's preview window in the "classic" crop mode - the one triggered by x5 zoom. Advantage: higher resolution.....
....
Resizing Canon preview doesn't seem to work, so for the 5x zoom mode, the preview will be centered, but the coverage will not be exact. At least until somebody figures out how to resize the YUV buffer.
There are hints that raw buffer size might be adjustable (http://www.magiclantern.fm/forum/index.php?topic=10111.msg123909#msg123909) in the 5x zoom mode.
(side note: actual crop factor in 5x zoom mode is not 5x - it depends on the raw recording resolution)
Quoteonce a1ex makes the x5-zoom from crop_rec available.
It would be great !!
What branch are you working from Nikfreak? Latest unified merged with raw_video_10bit_12bit branch works with raw_twk and then preview works with 10/12/14-bit more or less realtime.
raw_twk download here.
http://www.magiclantern.fm/forum/index.php?topic=13163.msg174991#msg174991
Release I posted is based upon plain "raw_video_10bit_12bit" branch.
@flofifull which software did you used to transcode mlv 10 bit into dng to pc? thx a lot
QuoteRelease I posted is based upon plain "raw_video_10bit_12bit" branch.
I tried compiling from your repository at bitbucket but seems you have done some changes. Your published compiled build works good while compiling from official raw_video_10bit_12bit and also from your repo all you get is some shaking corrupted earthquake sequences.
*deleted to avoid confusions*
Quote from: Brawl on December 01, 2016, 02:08:26 AM
@flofifull which software did you used to transcode mlv 10 bit into dng to pc? thx a lot
MLV Mystic ;)
Thanks Nikfreak.
QuoteLet me know your result. I might take a look in my VM later in hopes I didn't already delete my working dir :P
Checked and no cegar on this one. Might wanna check your VM for the magic lines again.
Ok so what happens when I add this line:
uint32_t edmac_write_chan = 16; /* Write 0x5 0x6 0x4 (LV) */
When stopping recording a series of beep tones comes to live and it writes something about slots and memory. Exiting liveview also exits the beeps.
When specifying only this output still scrambled unfortunately.
uint32_t dmaFlags = 0x40001000; //Enhanced
When specifying both lines above the beep tones and error memory/slot message, recorded file like a nice little earthquake ;).
*Deafeyejedis builds are also not working.
Sorry Danne,
My build is quite old - dated 25th November - but I will have a look into my VM when I return @home to check what has changed (if the working dir from 25th still exists). Meanwhile I just suggest using my build from 25th as provided until the mystery solves (maybe I used another branch!? don't know for the moment...)
No problem. Main quirk is to get the raw_twk to work with that build.
From metadata, nikfreak's build is 48bb172, without any changes. Simply open autoexec.bin with a hex editor ;)
For modules, all the uncommitted source code changes are included in the .mo file. To see them:
/path/to/magic-lantern/modules/module_hginfo_dump.sh file.mo
Nice trick with the module_hginfo_dump.sh. Tested on raw_rec and it said all was in order. Tested against later magic-lantern repo.
Still have to find changeset 48bb172. So this is unmodified by viewing autoexec.bin? I checked but didn,t compare since I don,t know where to find this this changeset. Somewhere in the raw_video_10bit_12_bit branch I suppose.
Quote from: Danne on December 01, 2016, 04:43:33 PM
Still have to find changeset 48bb172.
Click on "Commits" on the left panel of the web page then enter 48bb172 in the search box and presto:
https://bitbucket.org/hudson/magic-lantern/commits/all?search=48bb172
I can confirm it is plain 48bb172 w/o any further modifications. Scratched my old post as that rather was experimental stuff.
Great to know. Will get my hands on a 7D on monday first and things moves fast...
Thanks for confirming this @nikfreak and @a1ex for sharing the trick re: module_hginfo_dump.sh from changeset 48bb172.
I tried the firmware hack from nikfreak but was unable to increase the resolution past 1735x976 even though my bit depth is set to 10 and my preview is set to canon. Anyone know why that might be? Thanks!
please switch to X5 zoom.
2400x1200px has been reported to record continuously in 10bit. You mightwant to set fps to 24 as X5 is 30fps by default.
I think I figured it out, I am able to record at higher resolutions when I zoom in with cropped mode at 5x. I am unable to see what is being recorded, the image just freezes, but it appears to be recording without issues at 1080p in cropped mode. The next highest resoluton 2240x1200 goes for about 25 seconds before stopping.
By turning off Auto Lighting Optimizer in the Canon menu I was able to record at 2240x1200 continuously but still unable to view what is being recorded.
preview on your lcd, right? That's ok for the moment and same for everyone. Your camera lcd freezes but records.
Viewing on your computer what has been recorded for you in 10bit is best done with MLVFS.
Yes I was able to confirm that it was recording properly and without issues on my mac using mlvfs and davinci. Beside continuous at 2240x1200 was able to get around 1m40s of recording at 2520x1200. This is really awesome, I hope it will continue to be developed!
Hi everyone, I have been using the Magic Latern on my Canon T3i for some time, now I recently bought a Canon 7D, but I did the firmware update for a version 2.0.6, which Magic Lantern is not compatible, is there any method to go back to Factory or Do I downgrade to a firmware version 2.0.3 so that I can install Magic Lantern on my Canon 7D?
First of all thank you nikfreak for the update
on my 7d 14 and 12 bit works fine but 10 bit still has corrupt frames and good ones (I mean one by one )
settings : Global draw off
Preview Canon
FPS overidde 23.967
is there any advise ?
There are only a handful of Canon models that can take almost full advantage of ML's features and the 7D is one of them, the others are the 5DII and III but the 7D is 1/4 the cost of a 5DIII but its almost as good as the 5D's though the 5D's have a full frame sensor as apposed to the 7D's smaller APC-S sensor. But, the 7D's APS-C sensor is close to the size of a Super-35mm digital cinema sensor! The rest of the cameras like the 700D/T5i for example can only record RAW video for about 10-15 seconds and not close to the maximum resolution of 1080p. The 7D can record RAW video til the CF card is full and close to 1080p resolution. But RAW video is so sharp and your taking better advantage of the camera's dynamic range that when you scale it to 1080p it still looks sharper and better than the 7D's native video h.264 codec.
Check out this ML camera chart:
https://docs.google.com/spreadsheets/d/16cgnRivbUv7nA9PUlCLmLdir3gXdIN3pqzCNAAybepc/edit#gid=5
Hi guys! I have latest build (2016-12-18 23:30), i see "mlv_rec/mlv_play: add variable bit depth support." in discription. But i don`t understand how i can get this functional on my 7D :(
For the 7D it's not working, you have a compilation made by dfort and other in this same post from nikfreak... but it's not working properly.
It need to work with CONFIG_EDMAC_RAW_SLURP in the 7D, for it give clean image in 10 and 12 bits... I think nikfreak is working on that... we hope :))
Are you @nikfreak ?
Just installed ML on my 7D, primarily to be able to use the shutter button to start/stop video recording. Initial tests working great - I can use the on-camera shutter button or a remote such as the Canon RS-80N3.
Thanks for providing this great firmware modification.
One wonders why Canon didn't provide this same function instead of forcing us to use that tiny, hard-to-reach, counter-intuitive, button for video. That button is even more difficult to use when the Varavon finder is installed.
Again, thanks!
G-Jim c):{-
On my 7D, in ML 'Movie Tweaks', I have selected 'REC/STBY'. However, I'm not seeing that notification when in Movie Mode. I do get the red 'dot' when recording video.
Magic Lantern version: Nightly.2016Dec19.7D203
Mercurial changeset: 4f72a0eabb16 (unified) tip
Built on 2016-12-18 23:30:22 UTC by jenkins@nightly.
G-Jim c):{-
Just wondering if there is a solution to the black sunspot when filming? Aside from fixing it in post. Is this a Canon hardware issue? Obviously filming into the sun is not really recommend but sometimes can't be helped. I tried searching here but didn't find anything.
So I just tried the 10 and 12 bit raw with the 7D for the first time, using the 12/18 build from dfort, and I don't see any problem with the image. What defects are others finding?
Hey Frank7D,
What were your settings for 10 bit raw recording on the 12/18 build? I was getting all kinds corrupt footage, along with extreme shaking, referred to as Earthquake footage here on the forum.
- Paul Harwood
Hello everyone,
Has anyone had the problem of continuous recording on the 7D where it won't stop recording? I've read about it here on the forum, but am wondering if there is some sort of fix to this? I'm worried about bricking my camera because I have to turn it off because it won't stop recording even if I hit stop. This is with Auto Restart on in Movie Tweaks. I use this in combination with the T3i to record long events, and the T3i has never had this issue. If someone could reply that would be awesome. If I need to replicate this issue in order to help solve it I can certainly do that. Thanks.
- Paul Harwood
Issue 2065 (https://bitbucket.org/hudson/magic-lantern/issues/2065/movie-restart-7d-stuck-in-loop-cannot-stop) reported July 2014. See workaround in last post.
Hey Walter Schulz,
Thanks so much for your quick reply! Ok great, I'll make sure to try this. Awesome!
- Paul Harwood
Hi,
if I have 2.0.6 firmware on my Canon 7D... what can I do ?
Has something changed for 3x crop h264 video in 3 Dec nightly? I can't find the setting anymore to enable it.
Edit: I guess I was mistaken and it was never possible on 7D...
QuoteI have confirmed this works! Thank you so much N/A!
I have provided a Google Drive Link to a folder with screenshots, pictures, and videos showing the beauty of this:
https://drive.google.com/drive/folders/0Bz5n0qYxIkVOMnJMeWhkU3pMVjQ?usp=sharing
The videos are of my cat in my room, handheld at 50mm. Sorry for the shakiness, I just wanted to test this out with the time I had. I was able to record for 15 seconds.
If anyone has any questions, or can't get to the link please let me know. Thank you to all the Magic Lantern Developers, this is truly awesome!
- Paul Harwood
Very welcome ;)
Hi,
I trie today the new comp from dfort and its in the same, if some one ask. With MLV or RAW Module in 10 or 12bits you got the upper pink stripe thing.
*But in crop mode (x5) you can record in 10 and 12bits, wow. The problems that i find in crop mode (x5) is that wend you review the file in camera the exposure are more low then wend you recorded and show in the camera screen and the colores look that go's to sepia tones... Also mostly of the times wend you hit the rec the screen freeze.
Until someone find the slurp for the 7D we are like this... only in 14bit's that i must say it's gorgeous!!! 10bits you can have the same quality but less heavier files... and more frame rates YEAHHH =))
Hi arrinkiiii nice to hear someone is deeply testing it. I really hope will be possible to fix all the bugs!
guys is there some chance for MLV dual ISO on 7D? I saw some examples about 5DMIII recovering shadows single iso vs. dual iso and the creativity possibilities with the second one are outstanding. if I remember correctly dual iso requires a lot of bandwidth MLV 10 and 12 bit could help?
I think one or no one person are working in the 7D. Dual processor inferno thing... I think with the low princes for a 2hand 5DIII is better to have full ML features... but then, the glass.
@Arrinkiiii being honest my economic problems are so huge that I could never watch to better dslr or black magic. I'll really keep my fingers crossed!
Quote from: Brawl on January 09, 2017, 12:33:39 PM
guys is there some chance for MLV dual ISO on 7D?
You could give it a try.
waza57 got it to work on 5D2 (http://www.magiclantern.fm/forum/index.php?topic=16854.0) but it's only coded for 5D2. You would have to adopt it for 7D.
Just one question: I'm on the latest Firmware. Is it safe to go back to 2.0.3?
Gesendet von meinem HUAWEI VNS-L31 mit Tapatalk
hi, firends. prompt, please, with what maximum speed the chamber 7d by means of ML removes?
@nikfreak Thanks a lot for your reply unfortunetely I have no skill on programming languages.
But I could be a betatester if needed. In case I'm good to explain bugs and stuff like this also shooting videos to post on the forum.
@pazitivprod: Unable to understand your question. Please rephrase and/or add text in your native language.
hi guys may you suggest me your best settings for shooting mlv raw video at 48 fps or more please?
Per @N/A -- https://www.magiclantern.fm/forum/index.php?topic=9848.msg146710#msg146710
Thanks a lot @DeafEyeJedi I did a quick test at 60fps I get a lot of tearing. Is this natural for anyone or I did something wrong in the settings?
Which build are you using?
@DeafEyeJedi it's Nightly.2016Nov25.7D203 but maybe could be the one modified by dfort because I have 10 and 12 bit in MLV Lite module. If I remember well 10 and 12 bit are not yet implemented in the official nightly built because in early stage of developement.
p.s. I did the 60fps test (the one with the tearing) with mlv_rec module. I repeated the test with similar settings at 48fps and I has no tearing. maybe 60fps is too much or it works good to you? thx
p.s.
I has "force HDMI-VGA: on" in "/display/advanced settings" which is good for taking tearing under control
(for someone who wish to read more info can read this topic: http://www.magiclantern.fm/forum/index.php?topic=13817.0)
Is the 7D also affected by this issue (http://www.magiclantern.fm/forum/index.php?topic=11205.msg179133#msg179133)?
Hi,
today I tried ML first time on my 7D1 and 100D and am impressed.
But I have to report a bug at the 7D version:
The option Quick Zoom - full zoom on AF point doesn't work correct. It doesn't zoom on AF point, but just in the middle of the picture. That means it does exactly the same as zoom to 100%.
//EDIT: bug reported: #2673
Regards
Roger
Yeah, so at some stage HDMI tearing seems to have been fixed. On the latest build I have been recording with an external monitor (not set to force VGA) and no tearing is present. Minor tearing occurred when using crop mode with no FPS over ride. But otherwise no tearing at all. Anyone else want to test and confirm?
Great news if corroborated.
I don't know if tearing is fixed. When I use an external monitor and turn off focus peaking and such in ML, letting the monitor do it, it records fine.
Which build were you using @itisipotman?
Cool, I should have mentioned the following, Jan 27th Nightly. The camera is set to PAL and I'm recording at max res just fine at 25fps with MLV, crop mode is also recording fine at 1080p with 25p. All I did was turn the MLV module and sound module on and hit record, haven't changed any default settings.
Maxotics, care to elaborate? It sounds like things are working for you, but you also mention you don't know if its fixed?
is there ML for the Canon 7d mk2?
No
A few questions!
First of all, thank you very much, you developers, for this great work. My 7D is very happy too with ML 'new life' :)
I've tried to read all posts here and related with raw video, etc, but i still have some questions:
I use last stable ML firmware, but these doubts are regarding older versions too:
1) It's definitively impossible to record audio while recording video?
2) I can record continuously without anyproblem (Sandisk extreme pro 160MB/S UDMA7 32Gb) but not in crop mode, where it's allways cut about 20 seconds maximun length.
3) Quite frequently, frame 197-198 is corrupted with magent artifacts
I have tried lots of config, allways trying to get de biggest resolution possible, and now i'm recording fine at 2240x1120, both RAW video and MLV video.
Sorry if my questions are answered in same other topic :/ It's a very HUGE (and INTERESTING) forum! Thanks!
First of all: There is no "stable" Version for 7D and never was. "Stable" = outdated and unsupported v2.3.
There are "Nightly Builds".
1. Not at all. What gave you the impression it doesn't work?
2. Sorry but you have to be specific. Any Information about recording times achieved in continuous mode is pretty much pointless without mentioning resolution, frame rate and bit depth. And mentioning recording mode (H.264, MLV/MLV lite, RAW).
I suppose you run into unintentional stopping because crop mode records in 30 fps and therefore requires higher bandwidth.
3. Build used?
Regarding sonund recording: i've never been able to record any sound!
With an older Nightly build version, i read a tutorial where set sound off were recommended -maybe to optimize recording mb/s rates while recording, or something... and now, that i use the last Nightly Build available, maybe i have to re-read all info available, and practice more settings combos... but, for instance: yesterday i made some recordings, in MLV, 2240x1120px, and using MLVFS i see one of them says 'sound: YES' but it's not true...
I started using RAW video about 6 months ago, using raw_rec.mo (Magic Lantern Nightly.2016Jul09.7D203), and using the CF card i mentioned (Sandisk extreme pro 160MB/S UDMA7 32Gb) i realised i can record about 20 seconds MAX, without sound, in maximun resolution aparently available (about 1120 pix vertical res. max), and 23,9xx fps.
I installed Magic Lantern Nightly.2017Feb12.7D203 a few days ago, and started trying different video settings, with raw_rec and mlv_rec, mlv_lite... I realised i can record continous raw video in normal -no-croppped- mode, but in cropped mode, y can record about 20 seconds maximun at -theoretically- maximun resolution (2240x1120), but allways without sound, even when i can see 'sound:yes' in MLVFS. :/
It's being VERY interesting this 'new world', my 'old' 7D has a new life, and it's being very useful for me taking wildlife scenes as i do :)
Sorry about my english, and sorry if i'm not clear enough explaining all the facts :D
Thanks for your answer, @Walter.
Regarding 'bit depth', i have rad something about 10-12-14bits raw video, but i cant see 'where' these settings are in ML :/
When I want to put the new firmware,should I remove the old magic lantern first?or is ok?
If you want to use Canon firmware 2.0.6 I recommend to uninstall ML first.
Quote from: Jato on February 26, 2017, 08:56:32 PM
Regarding sonund recording: i've never been able to record any sound!
If H.264 recording is not working it is most likely hardware error.
MLV_REC requires MLV_SND for audio recording.
Quote from: Jato on February 26, 2017, 08:56:32 PM
I installed Magic Lantern Nightly.2017Feb12.7D203 a few days ago, and started trying different video settings, with raw_rec and mlv_rec, mlv_lite... I realised i can record continous raw video in normal -no-croppped- mode, but in cropped mode, y can record about 20 seconds maximun at -theoretically- maximun resolution (2240x1120), but allways without sound, even when i can see 'sound:yes' in MLVFS. :/
Maybe you missed the information about crop mode frame rate in my first answer to you above (http://www.magiclantern.fm/forum/index.php?topic=9848.msg180540#msg180540).
Quote from: Jato on February 26, 2017, 08:56:32 PM
Regarding 'bit depth', i have rad something about 10-12-14bits raw video, but i cant see 'where' these settings are in ML :/
Status "experimental". You can use Reddeercity's repository at own risk: https://bitbucket.org/reddeercity/magic-lantern_10-12bit/downloads/
Thread about 10/12-bit: http://www.magiclantern.fm/forum/index.php?topic=5601.msg180056#msg180056
@Walter i have some news :)
This morning a was able to record sound! Of course i can with CANON's firmware, so i remembered that resampling bitrate to 23,9xx is causing soundoff, even when it's supossed to be on. (my fault...)
I did some other tests, with both kind of video tools: I thought that each of the video types had a different format (RAW & MLV) but I only got MLV files.
QuoteStatus "experimental". You can use Reddeercity's repository at own risk: https://bitbucket.org/reddeercity/magic-lantern_10-12bit/downloads/
Thread about 10/12-bit: http://www.magiclantern.fm/forum/index.php?topic=5601.msg180056#msg180056
Maybe i read a bit more, before asuming that risk, but if it increases cropped video length letting me play a bit with dng files it could be really GOOD!
Thanks again for your kind support Walter! :)
Javi
Quote from: Jato on February 27, 2017, 12:30:24 PM
I did some other tests, with both kind of video tools: I thought that each of the video types had a different format (RAW & MLV) but I only got MLV files.
About 2 week ago it was different indeed: https://twitter.com/autoexec_bin/status/830878711423590402
Or select raw_rec.mo in Modules menu and press Q.
Well....Here I got all excited about acquiring Premier Pro CC 2017. So I shot some MLV and used MLV ViewSharp to change the MLV file to .dng with wave file. I go into Premier Pro media browser to import the dng and it won't allow import stating the file is either not supported or damaged. What a load of S*** !! Opens fine in Photoshop and After Effects but NOT Premier. I've searched online for fixes and nothing works. Oh well, just a heads up.
"MLV ViewSharp"? Sorry, don't know what you are talking about and googleing doesn't help.
Hello Walter...MLV ViewSharp(BrowseSharp) converts mlv's to dngs or raws (with .wav files if you record with sound) ...anyway I got Drastic MediaReactor Workstation and now I can import mlv's directly into Premier Pro. The only problem is if you recorded with sound and want to sync with a master sound file recorded on another device such as a H4N, Plural Eyes 4 does not recognize .mlv video files. So you have sync them outside of Premier Pro.
MLV Viewsharp here...
https://www.youtube.com/watch?v=I-iyiZAG7JI
Quote from: jman on March 08, 2017, 03:58:25 AM
What a load of S*** !! Opens fine in Photoshop and After Effects but NOT Premier.
Premiere can only open specific "flavors" of CinemaDNG files. There are many MLV converters that support output of Premiere compatible CDNG files, including:
http://www.magiclantern.fm/forum/index.php?topic=13152.0
http://www.magiclantern.fm/forum/index.php?topic=5618.0
http://www.magiclantern.fm/forum/index.php?topic=9560.0
http://www.magiclantern.fm/forum/index.php?topic=18975.0
QuoteIf you want to use Canon firmware 2.0.6 I recommend to uninstall ML first.
there is 2.0.6 now that is cool!but why doesnt the builds say 2.0.6 and is 2.0.3?
Yes, after upgrading to 2.0.6 you can't use ML anymore.
all right,thanks alot.
have you see the new post i posted at the 7d cropped 5*?
Hello,
This is my first time using Magic Lantern. I supposed to use ML for Shotting Photograph. I have installed ML with nightly build 2017-03-11, and loaded needed feature such Dual ISO. But, I don't know why it can't shot properly. I mean, once it works to shot with Dual ISO mode and I can convert it with CR2HDR Plug-In in Lightroom. But, in another shot, it fails. When I imported to lightroom and exported it with CR2HDR plug-in, it said "No Dual ISO Photo". Is it normal? or is there any setting that I missed to set up? Thanks for advanced.
Are you able to upload the file rejected by cr2hdr somewhere and link it here?
Here the link https://drive.google.com/file/d/0B_BWgCgxkugDY3RTTWo4LWtxLTg/view?usp=sharing (https://drive.google.com/file/d/0B_BWgCgxkugDY3RTTWo4LWtxLTg/view?usp=sharing). It is just like normal cr2 file. But, in my 7D with ML, Dual ISO is on with 400/1600 ISO.
Took a short look into it but I cannot see interlaced line structure. None.
Could be caused by
- "Alternate frames only" ON -> Toggles Dual-ISO ON/OFF (with timeout to ON if a second shot isn't triggered)
- Cam shutdown "dirty" -> Modules will not be loaded at next startup.
Hello, I have something going on with my recently purchased second hand 7D that I don't know whether it's a curse or a blessing. Namely, it comes with an eg-S focusing screen adapted and already installed, which means flawless manual focus but incorrect metering on anything brighter than f2.8 and anything darker than f4. Does Magic Lantern have a tool for accounting for that on the 7D?
Hey,
so I've been keeping track of what's been going on lately with the 7d, but so far it seems like a great camera, with very little attention and popularity.
I want to get on board with helping the development of this camera for ML as well as share my progress and results when I film with this camera.
Can anybody help a starter out? I'm pretty tech savvy, but never really dealt with code before so.
One of the easiest methods is just to use a "pre-built" VM:
http://www.magiclantern.fm/forum/index.php?topic=7579.msg134989#msg134989
Then read through this:
http://www.magiclantern.fm/forum/index.php?topic=991.0
and check also this section of the forum:
http://www.magiclantern.fm/forum/index.php?board=25.0
Quote...with very little attention and popularity.
Recent dev achievements regarding compressed 14bit raw should gain back attention and popularity once also available for 7D. Add to that some work and find (http://www.magiclantern.fm/forum/index.php?topic=19300.msg182149#msg182149) the correct registers to make it "great again".
hello everybody!
I'm just starting using ML. I'm impressed for the new capabilities with this firmware (thanks to developers for its great job!).
I have only one problem. I don't know if that is because I have a wrong ML configuration or it's a bug:
I can't fix the focus spot in Live View Mode. It's goes upper to down, left to right, but I can't fix in desired position. It's this normal?
I think it's not a problem of the jostick. If I use another CF without ML, Live View works ok!
Thanks :)
Not reproducable here.
Set cam and ML to defaults and retry.
I've found the problem. It's in the Bulb ND Utilities (bulb_nd.mo). If I don't load the module the Live View works ok
Can someone tell me where I can find what changes/improvements have been made per nightly build?
Download page for 7D1 -> Older Builds
Hi everybody.
I'm using ML since 1 year and i would to say thanks you for your amazing work. I recently install the last version of ML and I have some issues with the CBR bitrate. Nothing change at x2 or x3. When i check the file on PC, the bitrate is at 35 000 kbps or 40 000 kbps... I remember that i was able to up to 80 000 kbps in the past. Do you have the same issue ?
Thanks for who will reply. :)
I flashed the latest nightly ML build on my 7D (magiclantern-Nightly.2017Mar30.7D203.zip) and Live view and Video preview does not work at all on the LCD, it just shows up as a gray screen with only the outline of text visible. Is there a setting I messed up?
Edit: Nevermind, was the Digic focus peaking setting. Works fine now with that disabled.
is it possible to shoot raw video 10 and 12 bit in "no crop" mode with 7D does it works good? and wich software is it compatible to transform it from mlv to cdng? is mlvproducer compatible? thx
Is there a port of 10 bit / 12 bits comp mlv from 5dmkiii? This would Be great feature to save space
Envoyé de mon iPhone en utilisant Tapatalk
Hello,
the option Quick Zoom - full zoom on AF point still doesn't work correct. It doesn't zoom on AF point, but just in the middle of the picture. That means it does exactly the same as the option "zoom to 100%".
Bug #2673
Thats very annoying. I'm used to this option and on my 100D this ML option works fine.
Can someone of the prgrammers here please have a look to this bug ?
Thanks in advance
Roger
(http://thumb.ibb.co/cCVOZv/Capture.jpg) (http://ibb.co/cCVOZv)
Is there any way of NOT having the .tmp file included on card when I record .mlv?
Can't seem to find anything in the menu.
Thank you for your help! 8)
May I ask which build you were using back in 2015?
that's the date it shows when in reader.....i'm actually using the aug 1st 2017 build.
fixme: please use fio_malloc (in mlv_play_task)
Recent august build has this error warnings repeating on the screen when i playback clips that are over 5000 frames. They block the playback video screen.
I understand it is a bug that needs to be fixed. Can you suppress the repeating warnings so that the video can be viewed?
I'm not a developper but I'd like to help to port compressed MLV, Proxy H264 and crop mode 1:1 for slomo on 7D. This model is one the most affordable and balanced for quality/potential. What should I do ?
Latest nightly build contains commit 4ce4d28 (https://bitbucket.org/hudson/magic-lantern/commits/4ce4d2876ac5/) with description "700D, 6D, 7D: fix AbortEDmac".
Is there anything to test on 7D for mere users?
Currently it's only used in edmac.mo, selftest.mo and raw_twk.mo.
You may try the tests from the selftest.mo, for example. For raw_twk, I'm not sure if it solves any bug; you could try before and after. On 700D, the stub tests (from selftest.mo) could not run at all before the fix.
Yes, 7D stub test with previous build hangs after
[Pass] edmac_memcpy_start(dst, scr, size) => 0x429100b8
with LED on. Latest build completes with zero errors.
Haven't tested edmac.mo and raw_twk.mo yet.
Hi, I'm new to this forum and 7Dmk1 (long time 600d/ML user).
On the 600D there is a 'crop mode' activating a 3x zoom @1920x1080 in the std Canon menu.
I'm told the 7D mk1 can achieve this using ML - if so could someone kindly lead me through the steps to enable this feature please?
Thanks, Its
dfort continued development work on 7D over here. (https://www.magiclantern.fm/forum/index.php?topic=25880.0)
I got that the 7D records at almost 1080P
1728 x 972 = 1679616 Pixels in total 16:9
I would like it to run 1920 x 874 which is a aspect ratio of 2.2:1 a total pixels: 1678080 (a bit lower than the settings above at 16:9)
Is this possible without entering crop mode?
Easy! Just replace 7D's sensor (+processing units +firmware) with one having at least 1920x3=5760 pixels horizontal.
Quote from: Walter Schulz on May 07, 2021, 06:35:14 AM
Easy! Just replace 7D's sensor (+processing units +firmware) with one having at least 1920x3=5760 pixels horizontal.
AHA, it's a hardware limitation! Got it!
Quote from: mblackshore on May 04, 2021, 03:03:29 PM
I would like it to run 1920 x 874 which is a aspect ratio of 2.2:1 a total pixels: 1678080 (a bit lower than the settings above at 16:9)
Is this possible without entering crop mode?
You can easily make Full HD out of what you have now by upscaling the video using MLV App. No one will notice the difference between the true 1080p and the upscaled one.
Quote from: Wlad81 on May 20, 2021, 09:10:10 PM
.... make Full HD out of what you have now by upscaling .... using MLV App. No one will notice the difference between the true 1080p and the upscaled one.
Yes you can , it looks really badddd !
Line skipping sensor don't up scale very well at all , it create more artifact then the original file .
Best to use Crop_Mode and record @ 2k(or 1080p) it's non line skipping (even line used)
You just need to use a 15mm-24mm lens to get the same framing as a 50mm for example .
Quote from: reddeercity on May 20, 2021, 09:45:43 PM
Yes you can , it looks really badddd !
Line skipping sensor don't up scale very well at all , it create more artifact then the original file .
Best to use Crop_Mode and record @ 2k(or 1080p) it's non line skipping (even line used)
You just need to use a 15mm-24mm lens to get the same framing as a 50mm for example .
Your suggiesten about the lens was brilliant idea acually.
If I would upscale I would do it in post with Resolves SuperScale using neural network.
BTW does that mean that the built in video recording function with H.264 us upscaled output since sensor does not cover the size? Or is it that ML only can use X amount of the sensor?
How do you deal with noise artifacts when recording with raw? I seem to get allot more artifacts when recording with raw than not. There are artifacts that looks similar to chromatic abberation but not really. I will try to post some tests I have done tomorrow for you guys to see.
Quote from: reddeercity on May 20, 2021, 09:45:43 PM
Best to use Crop_Mode and record @ 2k(or 1080p) it's non line skipping (even line used)
You just need to use a 15mm-24mm lens to get the same framing as a 50mm for example .
One not only just needs a wide angle lens, but also a lot of light, and this is not always possible.
Are you trying to say crop and non-crop mode behave different in regard of lens aperture or sensor photosite sensitivity?
Yes, that's it. The lesser crop is and the more lens aperture is, the lesser noise we would have. Considering the fact that the sensors that were used in those Canon cameras are quite old and aren't backlit sensors - the BSI increases the sensor's sensivity.
Sorry, only valid to lens aperture but crop has no influence on exposure. Easy task: Print a pic. Print a crop of a pic. Same exposure.
Proof or I'm calling BS.
A lens' T-number doesn't change if a smaller or bigger area is exposed to light.
The crop of a finished pic is not a whole picture taken with a smaller part of a sensor. The more is the crop, the more light and/or the more sensitive sensor we need to achieve the same s/n as with no crop.
BS.
I've got a lot of noise in the shadows when shot with crop 1080p mode.
I get a lot of noise in dark areas with all kind of sensors, lenses, apertures, focal length, exposure durations, crop factors.
Proof your point or I call BS.
At the moment you carry a load of BS.
First call: You are trying to tell there is a difference if a pic is cropped in post or if the area is cropped during aquisition. Total BS.
EDIT: Maybe it is beyond your comprehension how a sensor works: Imaging yourself as a photosite. And you are looking into the sky. And around you are several millions other people. Now tell all the people more than 500 meters away from you to close their eyes. Does your vision gets darker? Nope. Because it doesn't affect your eyes if other people far away from you have their eyes open or not.
If you believe otherwise: Give proof or I call it BS again.
Quote from: Wlad81 on May 24, 2021, 09:09:30 PM
I've got a lot of noise in the shadows when shot with crop 1080p mode.
In none-crop 1080p mode more pixels are being used (more photons are being captured), there is a horizontal pixel binning in this mode, resulting in less noise.
theBilalFakhouri, this is what I'm trying to tell.
Quote from: theBilalFakhouri on May 24, 2021, 09:44:31 PM
In none-crop 1080p mode more pixels are being used (more photons are being captured), there is a horizontal pixel binning in this mode, resulting in less noise.
If you are talking about Line skipping sensor's I disagree , the that's what cause the noise , the pixel binning
https://thedailynathan.com/demosaic/algorithms.php?algorithm=pixelbinning&image=raw.png
QuotePixel binning is the most straightforward way to combine the color information across multiple photodetectors.
We simply assume a larger size for each pixel (each pixel is now an aggregate of information from multiple photodetectors rather than just one) and combine the color information
So yes you have more pixel , but the color/RGGB data is not the same as a single pixel RGGB , It's being combine and that's where the noise being produce.
I done many noise level test and the cleanest is crop_mode on D4(5d2 & 50D) .
but you don't have to take my word for it , test it for your self .
On the 5d3 there's not line skipping so this doesn't apply , just cams like 7d , 5d2 , 50d etc. ....
I realize this is an old thread, but I have questions specific to the 7d mk1.
A little background info. I have had my 7d for a while, and was using it for photographing birds mainly. Then my shutter started acting up on it. basically it gets stuck after a burst. (I'm not here looking to fix it, this is just my motivation to hack it) I got a new camera, so basically my 7d is rife for experimentation. If it bricks, it will still suck, but at the same time it's already somewhat broken.
Recently I got into astrophotography. So I'm really interested in trying to get a 1:1 pixel ratio. If you aren't familiar here is an overly dumbed down explanation: when shooting planets you take a video of 2-5 minutes and then take the several thousand shots, then stack several hundred to a few thousand of the best frames, and therefore get a much cleaner image. The problem is that The 7d compresses down to 1080 instead of cropping down to 1080.
In the "features page" it says that crop_mode_hack isn't available. Is that because it is buggy, or just not even possible? I can deal with buggy. I can deal with no sound, since I'm using the frames of the video to make an image, so I don't even want sound. If crop hack is possible, just buggy; are builds available?
I am also not even recording to card. I'm actually hooking my camera directly to a laptop and recording live view directly to a HDD. There is a program that records live view and can even record at 5x which gives "close" to 1:1 but having actually 1:1 is ideal. Also RAW video would be even better. I can't figure out if it's possible on the 7d or not.
I have no background in coding, so I don't know what is or isn't possible. I have been sifting through pages and pages here and can't find my answer. Perhaps I'm not using the correct search terms, so I apologize in advance if the question has been answered, but I did try.
Thank you in advance to anyone still out there willing to help. If I didn't explain things properly, don't hesitate to ask for clarification. I'm not the most articulate person.
7D - as most other ML supported cams - can do cropped RAW recording in 1:1.
Because 7D hosts Digic 4 and ML does not support LJ92 compression on Digic 4 there is no "crop_rec_4k" build available. Which doesn't mean you cannot record 4k.
Don't install Nightly Build (2018) but "experimental" lua_fix build.
EDIT: Crop_mode_hack refers to 600D's electronic movie zoom which is in fact 1:1. Recording is done in native Canon mode (H.264/MOV). This code exists in other cams as well (100D, 650D, 700D, M) but without menu item. ML adds menu item.
Quote from: mrflibbles on August 14, 2023, 07:52:41 PM
[...]
Recently I got into astrophotography. So I'm really interested in trying to get a 1:1 pixel ratio. If you aren't familiar here is an overly dumbed down explanation: when shooting planets you take a video of 2-5 minutes and then take the several thousand shots, then stack several hundred to a few thousand of the best frames, and therefore get a much cleaner image. The problem is that The 7d compresses down to 1080 instead of cropping down to 1080.
[...]
A kind "Hello" to all 7D astrophotography fellows!
The only reason (for now) I created an account on this ML forum is your post: I want to give you a "heads up" ... you are not alone! :)
Being a professional photo journalist, I got my Canon EOS 7D (1st edition) in spring 2010. Over time, newer camera bodies were added and the 7D eked out a shadowy existence in the closet. Having been a visual observer for decades, I only started astrophotography three years ago (2020), but initially wanted to use the cameras and lenses I already had.
Of course I did some research and that's how I found MagicLantern. ML was and is a great help for astrotography with the 7D because it offers very comfortable and flexible settings for long exposure image series in bulb mode. This really inspired me because it allowed me to use a very mobile setup without a lot of additional cables, controls and displays.
~ * ~
When night sky weather allows - which is rarely they case here in the Alps - I love doing deepsky imaging. I also photograph moon phases and sunspots. The longest focal length I have is F=500mm which is way too short to capture planets. It is even too short to capture a highres moon mosaic - which I would like to do.
I get to the point:
In the last few days I've come across indications that it is possible with ML to film the 5x magnifier of the 7D's LiveView, which in my case would correspond to a 5x "Barlow lens": Effective 2500mm focal length!
Unfortunately I can't help analyzing / developing this software feature but rather would need some hints / support what and how to use it with the 7D.
So please count me in as one curiously having this feature in mind.
My 7D with firmware 2.0.3 has ML up and running. How can I add / use this interesting 5x LiveView capture feature? I have no idea ...
Your help is much appreciated!
Clear Skies and thanks to all you bold ML developers,
too
I'm in some kind of hurry therefore q&d answer only:
Internal crop mode recording in native Canon mode (H.264/MOV) is not possible with 7D. Some older cams have a 640x480 crop mode implemented (550D for example) which was (is?) used by astros. 7-8x crop, btw.
600D has a native electronic zoom/crop recording option allowing 3x crop with FHD resolution and without line skipping (1:1 crop mode). Somehow underrated IMO.
The code is available in 100D/650D/700D/EOS M, too and ML unlocked access to it.
It is in fact possible to use external recording in 5x via HDMI. I gave it a short go but - as expected - output is just horrible.
May provide samples later.
IMO all of 7D options listed above are far from good.
You may want to explore cropped 1:1 recording modes with ML's MLV_Lite module for better results. Load MLV_Lite, enter movie mode, activate RAW recording in movie tab and don't forget to press magnify/5x button to enter crop mode.
Results should be far better than all those line skipping modes with Canon recording.
Use MLVapp to convert raw footage into other codecs or extracting frames for further postprocessing.
And get yourself a decent astro telescope to catch the things you want.