Messages

Option to change sensor of 43s batch is given officially in comments. So 2 hours left to join the party and break the 170k

Just seen there's a new batch of super35 for July. Those will all sell. Afterwards it can reach my optimistic guess.

Only 204 days left to release the 1st batch!
We will cheering you along and counting.

http://magiclantern.fm/forum/index.php?topic=11787.msg130384#msg130384

Seeing how well the campaign did I assume they will reach about 170.000€. A new batch would do the trick.
Nobody interested in 43s Axiom

Ok this is where I got today with QEMU:

Code Select Expand


[DebugMsg] (129,3) @@@ dwHdmiPhysicalConnect = 0(964)
[DebugMsg] (138,3) Variangle State 1
[DebugMsg] (138,3) HotPlug WifiSetting = 0
[DebugMsg] (138,3) CreateTask Master End
[DebugMsg] (141,3) emSlaveChangeCBR : AUTO_POWEROFF (1)
[DebugMsg] (141,3) emSlaveChangeCBR : UILOCK (0x0)


working on it. This one has lots of similarities with 6D 

Besides of knowing this is all experimental: would it be possible to use 10/12bit also for normal shooting (not liveview)? Or do the discoveries (eeko) only apply to liveview which I actually think.

From communication above please note that I don't own the cam.

Ok you guys owning the cam and wanting to help please get in private message with me.

@a1ex you see any chance this can solely be continued in QEMU? This should be the point where it stopped, right?:
https://bitbucket.org/hudson/magic-lantern/commits/branch/70d-support

Is nanomad planning to return / continue this? #209 states December. So better wait for nanomad to return as he owns a cam

There's something written on Indiegogo about EF mount once 120.000 is reached.

Great to hear that you got it working!

...
just imagine that two different camera systems are built on top of an unified toolchain. think about Dual ISO and MLV establishing and evolving.

Now that would be awesome. Btw what OS is Axiom going to use? Some kind of RTOS or even linux?

e.g.

Code Select Expand


mkdir fullresvst
cd fullresvst
hg clone -r fullres-silent-pics https://bitbucket.org/hudson/magic-lantern
cd magic-lantern
make -j2
cd platform
cd 6D.113 (if you wanna compile for 6D)
make zip

Please also read this:
http://magiclantern.fm/forum/index.php?topic=7579.0

You might have to adjust makefile.user.default if you don't have gcc 4.8.3

Please use the full branch to compile:
https://bitbucket.org/hudson/magic-lantern/commits/branch/fullres-silent-pics

Don't simply compile the module. Fully compile to get your nightly zip and try it out.

[Guys I am just kind of joking but on one side....]

...
But I am wondering how they will sustain interest in this project in the long term with the 16mm and 4/3rd not selling at all.
...

Don't worry as long as we bring up a new topic and make it sticky at least ML users will always be aware of the project.

Countdown to April 2015 - planned delivery
200 days left

Wooooops new launch / delivery date November 2015
300 days left

And don't forget! After the beta campaign we need a new thread for the Gamma and place countdowns in there cause everybody wanting the beta would want a better cam than the Beta. meanwhile I would want to create a new thread for QC where we countdown days left to receive a replacement delivery cause each and every manufacturer had quality issues when bringing out a new cam.....

Guys I am just kind of joking but on one side....

I also thought about some "lite edition" for photographers last days. Kind of a fool-proof edition where lots of the goodies are enabled by default with just some config options like "enable / disable"

...
Anyway - ML is a great thing and the Apertus Axiom idea is too - but the cams who really need ML know how (650d, 700d, EOSM, ...) are for shure not realy in focus since month.
It´s more like: It would be nice if someone cares for them too because we are more concentrating on making the "state of the art" cams to the "super state of the art" cams. And in reallity it´s not used like the ML team might think.
My guess: The Apertus Axiom Beta will not really become "the one" because there are just not enough people who need it and there will be not enough marketing and especial service power against Canon, Nikon, Sony, ... - but one or the other ML programmer may get good offers from the industrie.
...

a1ex said it now several times. He hopes to find a way to pay his bills so he has more time to contribute to ML.
As an example I just remember the days where CyanogenMod founder Steve Kondik has been hired by Samsung to work with them. Some time later he decided to leave Samsung again and cyanogenmod Inc was born. Theres also the "ONE" a phone by Canogenmod Inc. In all that time development never stopped for Android phones. Once Google pushed out a new Android version all the goodies from old versions were merged asap into a new cynogenmod version. This was possible because there is  are much more contributors. And that's what lacks for ML development: contributors, device maintainers etc...

As said earlier the Cyanogenmod story comes into my mind when thinking of Apertus. The campaign in Indiegogo will successfully reach its end. Afterwards devs will come together and do some stuff. Some of you might be concerned about ML development. But time will tell what happens. This is going to be fun here once the first 7D Mark2 owners pop up here and ask for a build. Armv6 cpus have to be supported. I also seen that electronic viewfinders will be used in EOS 750D. So lots of fun to pop up here. Why not join the party and learn the basic skills around ML development?

[Edit:]

Works fine here for 6D. Needed to do some additional stuff like filename capitalization etc. I just ran into one last problem. I have somehow no write access - at least there's no "magic.cfg" saved neither "bench.ppm" nor are ROM dumps from debug menu written etc. Though qemu doesn't report an error on qemu monitor. It's just like qemu has write access to some nirvana place in memory....

Code Select Expand


[???] [0x00000010] -> [0xC020006C] PC: 0xFF0C7C14
*** FIO_CreateFile('B:/ML/SETTINGS/magic.cfg') => 17
*** FIO_WriteFile(11, 231)
{{{
# Magic Lantern Nightly.2014Oct02.6D113 (b59a1ac5fbfc+ (qemu) tip)
# Built on 2014-10-02 08:56:42 UTC by magiclantern@magiclante
}}}
*** FIO_CloseFile(11)
[FIO wrapper] closefile() nothing open
Save configs...


Edit:
qemu-helper.c define R/W access. Do I have to change the values for 6D. Btw I compiled and tried via qemu branch

simply wow! 

Found some stuff while digging through my 6D ROM dumps

Code Select Expand


FACTORY ADJUSTMENT MENU VER 0.01 ********** 0. Exit from Factory Adjustment 1. Leak Check 2. SDRAM Check 3. ROM Check 4. HDMI Check 5. Video Adjustment 6. ICU Version Check 8. Adjustment Data Display and Change 9. Check Flag Display and Initialization A. ALL Check B. ALLP Check C. RAM Check2 P. Power Domain Check S. Serial Flash Check Z. Input_Device_Unique invalid input CheckPro> --- LeakCheck --- --- Finish --- OK K302 System & Display Check & Adjustment program has started

Anyone know how to activate that menu? Found also this as a reference:
http://photography-on-the.net/forum/showthread.php?t=876884

Let's wait and see what happens. Looks like Olympus is in the game, too. This was already posted by s.o. else here in the forum. The prototype pictures from Olympus look like it's been the sister of Apertus Axiom:

http://www.ephotozine.com/article/olympus-open-platform-prototype-camera-at-photokina-2014-26189
http://opc.olympus-imaging.com/

That did it! Thank you.

I get some error if i compile with "CONFIG_DEBUG_INTERCET_STARTUP = y". GDB = y is ofc set.
The error doesn't happen with "CONFIG_DEBUG_INTERCEPT = y".

Code Select Expand


make[2]: Leaving directory `/home/magiclantern/nik6d/magic-lantern/tcc'
[ CC       ]   module.o
[ CC       ]   afma.o
[ CC       ]   gps.o
[ AR       ]   strrchr.o
[ AR       ]   dietlibc.a
[ AR       ]   lib_a-setjmp.o
[ AR       ]   newlib-libc.a
[ CP       ]   newlib-libm.a
[ CP       ]   gcc-libgcc.a
[ LD       ]   magiclantern
dm-spy-extra.o: In function `generic_log':
dm-spy-extra.c:(.text+0xc4): undefined reference to `looks_like_string'
dm-spy-extra.c:(.text+0xe0): undefined reference to `is_sane_ptr'
dm-spy-extra.c:(.text+0xf0): undefined reference to `looks_like_string'
dm-spy-extra.c:(.text+0x11c): undefined reference to `asm_guess_func_name_from_string'
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/magiclantern/nik6d/magic-lantern/platform/6D.113'
make: *** [6D] Error 2




Anyone else encountering this compile error with "CONFIG_DEBUG_INTERCET_STARTUP = y"

check your lighting conditions. You need enough light I had initially also some problems until I added enough light or went outside. If you still get problems plz post your settings. Wide / tele  ....

See also this:
https://bitbucket.org/hudson/magic-lantern/pull-request/577/dot-tune-afma-fixes/diff

It's something on your side that's wrong...

nightly builds are created from unified branch as long as devs don't decide to break the builds due to some reasons  .
You may head over to bitbucket at any time to see if any stuff is added/updated/deleted:

https://bitbucket.org/hudson/magic-lantern/commits/branch/unified

Once there's new stuff committed it should become abvailable in the next nightly -> a new nightly zip will be created. If there's no new commits then there's nothing to build for the system. All other branches here can contain more experimental stuff. To get this you can try to follow the tutorials for compiling or request a build of a specific branch within this thread.