Menu

Show posts

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

Show posts Menu

Messages - g3gg0

#2701
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 05:38:34 PM
in addition to that, i use two batteries:
a brand new that i bought as the original was defect, and the "defect" one that
could get repaired later by applying voltages manually and loading in a 3rd party charger.

both are working fine and show full battery performance.
#2702
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 05:30:29 PM
Quote from: feureau on October 13, 2012, 05:03:17 PM
First time I run it, I smelled something burning, so I quickly turn it off.

magic lantern CAN NOT cause anything like this.
when recording without ML, the camera uses 60% of the CPU processing power *plus* the hardware unit for MPEG encoding.
even when ML would consume 100% CPU power all the time, there is nothing that can happen within just a few minutes or hours.

also about "consuming power" and "battery getting hot" we already ran a test on two identical 7D bodies before releasing the alpha. (thanks jphansen)
both cameras next to each other with fully charged batteries. one camera running ML, one without.
after 10 minutes recording, the ML camera drained just one percent (!) more energy than the other one.
that 1% is just logical when you run smth like focus peaking.

#2703
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 09:09:25 AM
Quote from: gordoncasey on October 13, 2012, 05:53:47 AMMy personal opinion is that this alpha release was pre-mature.
read http://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha to understand developer terms.
Quote from: gordoncasey on October 13, 2012, 05:53:47 AMAll the time it took to make the initial post could have been used to actually write code.
if that is your position, you didnt understand anything what Magic Lantern is all about.
#2704
what was the reason for failing?
#2705
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 01:36:29 AM
Quote from: GershberG on October 13, 2012, 12:37:41 AM
even if REC/STBY notif: OFF and Global Draw disabled the red dot IS there on external HDMI.

maybe setting canon's BMP palette to all-transparent will kill any BMP output.
so you would have clean HDMI output with the 7D's default resolution.
(no, no full-HD while recording yet)
i will check that the next days.
#2706
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 01:33:42 AM
Quote from: GershberG on October 13, 2012, 01:29:08 AM
1. no, with the stock Canon FW there's no real time sound monitoring on REC/STBY at all.
2. using Coolcd HD2 7" (Lilliput 800X480 matrix).
3. monitor shows 480p resolution
4. the headphones are connected to the modified Canon AV/USB cable with sound output only.

BTW the same setup works with my 60D, so this is what I'm comparing to.

thanks, these are important infos.
this means we probably will have to override some properties.
except the MZ that is complaining - this might be solvable.
#2707
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 01:28:58 AM
this is *no* firmware upgrade. Magic Lantern is "executed" by running the "firmware updater" with the 7D..._ML.FIR.
it stays actvie until the camera powers off. no matter if this is via power switch, via card door or via powersave.

as this is an early test version, not meant for productional use, but for testing, we chose the safest way, right.

autoexec.bin versions will come when it is safe to use and we found a way that does not raise any legal issues.
it will be announced in this forum when it's time.

@cracky123456:
we know that ;)
but let us first make Magic Lantern safe and stable before we start to tweak the maximum out of digic registers.
we have ideas and concepts. but they will be released when its time.
#2708
see http://www.sawomedia.de/magiclantern/cropmarks/
or http://magiclantern.wikia.com/wiki/Cropmarks about how to create your own.

as you need that cropmarks and know how it has to look like, help us!
create the cropmark, document it (explain what is is for) and link it here.
we will include it in future releases.
#2709
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 01:12:05 AM
@collbeanzfilms:
as already wrote in release notes:
   * it is not a firmware upgrade, despite the camera saying "Firmware update program";
it is in RAM only.

@GershberG:
so you want to have a clean HDMI output without any canon graphics overlaid. right? will look into that tomorrow.
that audio thingie - is it the same with stock canon firmware, or with ML only?
can you post some details about the monitor you use?
at which resolution is it running?
do the headphones you use also feature a video out connector?

@Digital Corpus:
the level bar drawing is not 100% accurate at ~45° if you wanted to report that.
also its drawing over grid.

@beej:
i zipped it with 7zip as i thought it will produce the best output of the 3 possibilities i had.
maybe i should have used a tar.gz ;)


thanks for feedback, guys
#2710
Archived porting threads / Re: First 7D alpha released!
October 13, 2012, 12:06:54 AM
"cannot communicate with battery" might be some issue because of firmware updating.
maybe the main firmware checks for a fully charged original battery.
thats sad, but i think theres nothing we can do. sorry.

you start the camera with HDMI attached, go into video mode and plug AV cable with headphones.
then the camera switches off HDMI output and retrns to LV display. right?
that does also happen when no ML is running, right?

#2711
Archived porting threads / Re: First 7D alpha released!
October 12, 2012, 11:52:50 PM
Quote from: g3gg0 on October 12, 2012, 10:36:53 PM* Audio meters while recording

yes, only during recording
#2712
Archived porting threads / Re: First 7D alpha released!
October 12, 2012, 11:33:01 PM
Quote from: feureau on October 12, 2012, 11:21:02 PMAny particular stuff you wish to point our attention to, O Master? :D

just call me georg ;)

as this is an alpha version, some features might work unreliable.
the best is - play with all the features. test them on HDMI. test on a SD monitor. test on a HD.
maybe you have some flash. test it. perhaps that causes ML to behave incorrectly.
or a lens that causes some weird behavior.

and if it works fine, also tell us. this feedback is also important.
#2713
Archived porting threads / Re: First 7D alpha released!
October 12, 2012, 11:06:58 PM
Quote from: exe on October 12, 2012, 11:01:12 PM
Is it possible for the 7d to brick if I use another phottix battery instead of the original canon one?
i dont think it will ever happen, but i cannot guarantee that.
the only thing i think will happen, could be crashes or lock-ups.

but please report, if something weird happens.

Quote from: Stedda on October 12, 2012, 11:05:09 PMWith what you said, as I said before, I REALLY hope you guys decide to keep future releases to Supporters.

we don't want to make ML smell like donationware.
we trust on the users (even first-time users) to first see what we've done, then come back and say thanks.
#2714
Archived porting threads / Re: First 7D alpha released!
October 12, 2012, 10:59:49 PM
Quote from: ilguercio on October 12, 2012, 10:55:34 PM
So let's say you get all this stuff, how much can it improve ML? Is that like the last 10% to discover all the good stuff that mother Canon doesn't want us to have?

well, it helps us to make our reverse engineering work easier.
there were days where i sat 10 hours in front of the computer, so many of the devs do.

this tool might reduce the time we need to analyze code by factor 2 or more.
#2715
Archived porting threads / First 7D alpha released!
October 12, 2012, 10:36:53 PM





Finally, the first Magic Lantern release for the 7D is here!

It is still an early alpha version, so here are a few things you should know:

* it was primarily tested on one 7D, and a few days on three other 7D's;
* during those tests we took 1000 photos and gigabytes of videos;
* there were no crashes or strange behaviors during our tests;
* this release will not alter any data in your camera's permanent memory;
* this release will not directly alter any so-called "properties" (persistent camera settings);
* this means, some functions like HDR photos, HDR videos, bulb ramping etc will not work yet;
* it is not a firmware upgrade, despite the camera saying "Firmware update program";
* we have disabled all features that are not yet working perfectly;
* please don't beg for adding feature XYZ, it will be added as soon as it works without issues.

But:
* If anything goes wrong, we don't pay for repairs. Use Magic Lantern at your own risk!

Key Features:

* Audio meters while recording
* Zebras
* Focus peaking
* Magic Zooom (via half-shutter, or focus ring)
* Cropmarks, Ghost image
* Spotmeter
* False color
* Histogram, Waveform
* Vectorscope
* Movie logging
* Movie auto stop
* Trap focus
* LiveView settings (brightness, contrast...)
* Level indicator
* Image review tweaks (quick zoom)
* and some debug functions

Known issues:
* When using trap focus, opening card door won't shut down the camera. Simply power off using power switch.
* Formatting the card will also remove Magic Lantern files.
* You have to reload Magic Lantern every time you use it.
* video frame rates in LV are displayed too high (exactly 1.2x)
* make sure your battery is chipped, else canon firmware will abort "firmware update" (=loading ML)

Installation
1) Update camera firmware to 2.0.3
2) Format your CF card from the camera
3) Extract contents of ML .zip into your card's root folder
4) Run "firmware upgrade" once again
5) Voilà. Magic Lantern. (press DELETE for menu)

Technical Details
Why did it take so long to get Magic Lantern running on the 7D?

This is a long story. The workings of single-DIGiC cameras are already well understood.We know how to forge FIRs and we can execute code using this method.Our code gets executed without any interruption to the cameras proper function, we can hook into startup code and simply restart the camera or update the bootflag needed for execution of autoexec.bin.Same applies to autoexec.bin if the bootflag is enabled.

But not so on the Dual-DIGiC 7D cameras.

One DIGiC is called "Master" and the other "Slave." All ML related stuff like GUI, LV etc is running in Slave.The Master cares about focusing, lens communication and some other related technical stuff.So there are two processors that both load the (forged) firmware update program which contains Magic Lantern. But we could not simply reboot the Slave into normal firmware while the firmware update loader is executed. With some tricks like patching the original firmware updater, it was possible to enable the bootflag for autoexec.bin. But even running Magic Lantern in autoexec.bin failed silently. This was the point where our first investigation started stuttering.

After some deeper investigation with new methods like - lets call it "virtual flash patching" by manually patching the processors cache content - we found out that the Master is still running and waits for the Slave to send synchronization signals. If they don't arrive, Master is disabling the Slave where our code runs.Henceforward it was a job of just two weeks to find out what to do and make Magic Lantern start up cleanly and then another two weeks for updating all defines, macros and constants to get the important features running smoothly.

This alpha is a snapshot of what is working reliably enough to begin testing it widely.

Who was involved in developing Magic Lantern for the 7D?
Definitely everyone! As all the features in Magic Lantern came from the many developers contributing to ML.

Although, beyond the usual suspects, there are two key players for the 7D port: Hudson and Indy. They spent an extraordinary amount of time getting the bootflag enabled and building .FIRs that would run perfectly.Without their hard work, there would definitely be no 7D version.

What is still missing?
We can run Magic Lantern from autoexec.bin, but we still can not reliably enable the bootflag to execute it. This means, virgin cameras will only be able to run the .FIR version of ML for now. We know ways to enable the bootflag, but they would involve copyright issues. And that's something we want to avoid.

Also missing is the FPS override feature. We are not sure if this will be possible as it has been in other models.

All HDR features, bulb ramping, and features that require "properties" could possibly work as soon we enable them.For now we will keep the risk at a minimum and slowly test feature after feature - your feedback is important at this stage.


Troubleshooting
After starting the firmware upgrade, if there is only a black screen, but auto-focus works:
* reinstall the firmware v2.0.3 from the links on the right;
* make sure the 7D000203.FIR checksum is correct.
  7D000203.FIR checksum
    SHA-1: 613439A489A46D2691FB54F0DB22232F17E2AA8E
    MD-5: 29AF55CF2B404D2A60220BC9CC579EFD
    WinMD5: www.winmd5.com

The camera shows no magic lantern, but a standard firmware
* reinstall firmware again, format card and copy ML files again.

What is next?
We have to better understand what Master and Slave are doing exactly.Which one processes MPEG data, which one compresses JPEGs and what could Magic Lantern achieve by understanding this relationship?As the lens communication seems to be handled by the Master – maybe we can change the lens protocol so you can use lenses that have known bugs, or even lenses with a totally different protocol?Maybe we can read the level sensor at higher rates and embed that data into images for automatic leveling? Or even embed into videos?

But first we have to analyze the firmware. And for this we would love to buy a copy of IDA Pro with Hex-Rays Decompiler for ARM for our developers, and we cannot afford it easily without your help.

We gave our best, our time, and considerable knowledge. So please be kind and support our work!
Magic Lantern is a community effort, and you are now part of that community!

Click here to read this article!

Download
Magic Lantern for 7D alpha 1
Canon firmware v2.0.3
#2716
Feature Requests / Re: [DONE] Camera trap trigger
October 12, 2012, 01:38:05 AM
only if we get a link where we can see the result of what your trap recorded :D
#2717
Quote from: nanomad on October 11, 2012, 07:34:33 PM
As it's clearly written..

i think that was accidentally removed - its not anymore in the post :)
#2718
Quote from: filmkid1080 on October 11, 2012, 09:44:52 PMWhat am I doing wrong?

e.g. not telling us which Magic Lantern release and camera you are using ;)
#2719
General Development / Re: Task control.
October 11, 2012, 12:21:37 PM
hehe thanks ;D
thats just a few lines of code
#2720
General Development / Re: Task control.
October 10, 2012, 10:14:50 PM
high p-number means low priority.
maybe thats what you mean.
#2721
General Help Q&A / Re: Sunset mode - Cannot calibrate
October 10, 2012, 02:07:38 PM
Quote from: timelapses on October 10, 2012, 10:31:18 AM
I am sorry but what do you want me to do with that?

he wanted you to read that.
why? beacuse your answers are quite short.
to find the reason for failing your input is not enough.

e.g.:
"I started the camera in Av mode. i set the ISO manually to 400 then switched to LV mode. i didnt use any flash, as this is a landscape scene only. also i didnt connect any equipment like triggers or such. file format was RAW only, image review feature was turned off and i had 32GiB free on my SD card.
then i chose feature XY from ML menu and suddenly [.....].
here some pictures of the screen while the error message occured, here one right before it occurred and here a photo of the landscape i wanted to shoot.

thanks for helping!"



thats what developer want to see.
#2722
Feature Requests / Re: [DONE] Camera trap trigger
October 10, 2012, 12:32:07 AM
maybe in this case its not a useful-for-everyone feature that still requires mainenance and is easy to get broken.
perhaps thats better a branch or "private mod"?
#2723
Archived porting threads / Re: Canon 7D ML
October 07, 2012, 11:57:08 PM
@joespace:
you cannot run this on "normal" 7Ds as the bootflag is not enabled. (or is it?)
#2724
Archived porting threads / Re: Canon 7D ML
October 07, 2012, 07:12:42 PM
@phiber:
you cannot run this on "normal" 7Ds as the bootflag is not enabled. (or is it?)

@Pelican:
true. didnt test it with sensor cleaning.
thanks for pointing out!
will provide an update
#2725
Archived porting threads / Re: Canon 7D ML
October 07, 2012, 02:20:27 AM
Quote from: joespace on October 07, 2012, 01:00:24 AM
Thank you!  7d owner always wanted to have ML on it. What your are doing is great. Any chance ti have Fps overide on the 7d one day ?

thanks.
for what i know now, it seems to be a lot of work again, as the known timers are not used for fps timing.
so i think it will take its time to find that out. maybe next year ;)