Messages

Virtualbox now works for me, and I got the bitrate thing running. Thanks!
the only strange thing is: all fonts in ML are terribly big now..

I still have one question: Is there a reason, why you don't change
call("IVAParamMode", CARD_DRIVE "ML/H264.ini");
to
call("IVAParamMode", "B:/ML/H264.ini");
in bitrate-5d3.c ?

wouldn't that be better anyway, so people can use it?

thanks, I will give virtualbox a try - but to be honest with you: I read the installation instructions before and they seemed even more complicated than cygwin also: 1.3 GB? :-OOOO
Anyway, I'll try and let you know if it worked..

Using old builds will not help me, because, as you said, they don't have raw - which I also need.
I'm trying to compile this thing myself now - because I need bitrate changes on my 5D3.

Unfortunately I ran into a problem with the compiler, which i have to set up first..

I installed everything on my win7 machine as described here: http://www.magiclantern.fm/forum/index.php?topic=2899.msg14021#msg14021
(I used gcc version 4.7.2 and also changed the  according settings in the makefile.user)
The installation seemed to be successful.

Then i did a "make clean" and a "make 5D3".
This is what I got:

Code Select Expand

$ make 5D3
make -C  ../platform/5D3.113
make[1]: Entering directory `/home/manniac/magic-lantern/platform/5D3.113'
[ VERSION  ]   ../../platform/5D3.113/version.bin
[ CPP      ]   magiclantern.lds
[ AS       ]   ../../platform/5D3.113/stubs.o
[ VERSION  ]   ../../platform/5D3.113/version.c
[ CC       ]   version.o
[ CC       ]   boot-hack.o
[ CC       ]   mem.o
../../src/mem.c: In function 'memcheck_remove':
../../src/mem.c:409:49: warning: assignment makes integer from pointer without a cast [enabled by default]
[ CC       ]   ico.o
[ CC       ]   edmac.o
[ CC       ]   menu.o
../../src/menu.c: In function 'menu_post_display':
../../src/menu.c:2394:24: warning: initialization makes pointer from integer without a cast [enabled by default]
[ CC       ]   debug.o
[ CC       ]   cfn.o
[ CC       ]   gui.o
[ CC       ]   picstyle.o
[ CC       ]   exmem.o
[ CC       ]   bmp.o
[ CC       ]   rbf_font.o
[ CC       ]   config.o
[ CC       ]   stdio.o
[ CC       ]   bitrate-5d3.o
[ CC       ]   lcdsensor.o
[ CC       ]   tweaks.o
[ CC       ]   lens.o
[ CC       ]   property.o
[ CC       ]   propvalues.o
[ CC       ]   gui-common.o
[ CC       ]   chdk-gui_draw.o
[ CC       ]   movtweaks.o
[ CC       ]   menuhelp.o
[ CC       ]   menuindex.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
../../src/vram.c: In function 'vram_redirect_lv_buffer':
../../src/vram.c:581:35: warning: assignment makes integer from pointer without a cast [enabled by default]
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   shoot.o
../../src/shoot.c:4608:6: warning: conflicting types for 'set_interval_index' [enabled by default]
../../src/shoot.c:464:9: note: previous implicit declaration of 'set_interval_index' was here
[ CC       ]   hdr.o
[ CC       ]   lv-img-engio.o
[ CC       ]   state-object.o
[ CC       ]   tasks.o
[ CC       ]   vsync-lite.o
[ CC       ]   tskmon.o
[ CC       ]   battery.o
[ CC       ]   imgconv.o
[ CC       ]   histogram.o
[ CC       ]   falsecolor.o
[ CC       ]   audio-ak.o
[ CC       ]   zebra.o
[ CC       ]   beep.o
[ CC       ]   crop-mode-hack.o
[ CC       ]   ph_info_disp.o
[ CC       ]   flexinfo.o
[ CC       ]   fileprefix.o
[ CC       ]   console.o
[ CC       ]   tcc-glue.o
make -C ../../tcc
make[2]: Entering directory `/home/manniac/magic-lantern/tcc'
make[2]: Für das Ziel »all« ist nichts zu tun.
make[2]: Leaving directory `/home/manniac/magic-lantern/tcc'
[ CC       ]   module.o
[ CC       ]   video_hacks.o
[ CC       ]   fio-5d3.o
[ CC       ]   misc.o
[ CC       ]   afma.o
[ CC       ]   raw.o
[ CC       ]   chdk-dng.o
[ CC       ]   edmac-memcpy.o
[ CC       ]   asm.o
[ AR       ]   strrchr.o
[ AR       ]   dietlibc.a
[ AR       ]   lib_a-setjmp.o
[ AR       ]   newlib-libc.a
[ LD       ]   magiclantern
c:/program files/cygwin64/home/manniac/arm-toolchain472/bin/../lib/gcc/arm-none-eabi/4.7.2\libgcc.a(unwind-arm.o): In function `unwind_phase2':
C:\msys\1.0\home\yagarto\gcc-build\arm-none-eabi\libgcc/../../../gcc-4.7.2/libgcc/unwind-arm-common.inc:289: undefined reference to `abort'
c:/program files/cygwin64/home/manniac/arm-toolchain472/bin/../lib/gcc/arm-none-eabi/4.7.2\libgcc.a(unwind-arm.o): In function `__gnu_Unwind_Resume':
C:\msys\1.0\home\yagarto\gcc-build\arm-none-eabi\libgcc/../../../gcc-4.7.2/libgcc/unwind-arm-common.inc:487: undefined reference to `abort'
C:\msys\1.0\home\yagarto\gcc-build\arm-none-eabi\libgcc/../../../gcc-4.7.2/libgcc/unwind-arm-common.inc:505: undefined reference to `abort'
c:/program files/cygwin64/home/manniac/arm-toolchain472/bin/../lib/gcc/arm-none-eabi/4.7.2\libgcc.a(pr-support.o): In function `_Unwind_GetDataRelBase':
C:\msys\1.0\home\yagarto\gcc-build\arm-none-eabi\libgcc/../../../gcc-4.7.2/libgcc/config/arm/pr-support.c:394: undefined reference to `abort'
c:/program files/cygwin64/home/manniac/arm-toolchain472/bin/../lib/gcc/arm-none-eabi/4.7.2\libgcc.a(pr-support.o): In function `_Unwind_GetTextRelBase':
C:\msys\1.0\home\yagarto\gcc-build\arm-none-eabi\libgcc/../../../gcc-4.7.2/libgcc/config/arm/pr-support.c:400: undefined reference to `abort'
collect2.exe: error: ld returned 1 exit status
../../src/Makefile.src:176: recipe for target `magiclantern' failed
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/manniac/magic-lantern/platform/5D3.113'
Makefile:33: recipe for target `5D3' failed
make: *** [5D3] Error 2


Everything looks good, but in the end the compiler fails and I have no idea why. :/

  Unfortunately I don't understand..
I'm not a programmer (not a good one, at least).
Can I do anything without changing and compiling the source code?

I see
How can it be fixed? Can anyone fix it?

Hey 1%!
Thanks for your answer!

I used the exact code of your first post and saved it in ML/h264.ini
I then recorded a 10s clip.
Next I loaded ML/H264.ini
Now I recorded a second 10s clip.

There were no differences in size or quality of the two files. Shouldn't the second file be bigger and have better quality?
I also tried changing the parameters, but none made a difference.

What am I doing wrong?

Does anyone have an answer for me, please?

I'm trying to get my 5D3 read the h264.ini file to increase bitrates on my mov files. (I do not want RAW. I need H264.)

Unfortunately there is little information on how this works. This thread seemed to be the only one that I found, but allthough I read through every single post and tried out different versions of h264.ini files, I could not get it to work. I put the file in ML/h264.ini and selected "Load h264.ini". I'm not sure if the file was actually loaded or if it is in the right place. I just don't know how to find out IF it was loaded...
I use the latest nightly build (19.09.2013)

Can anyone please tell me, what do I have to do to make the 5D3 record at a higher bitrate? Your help would be greatly appreciated!

extracting dngs from the raw (5DIII) is quite slow on my machine (win7 64bit). for some reason the first 100 pictures or so are quite fast and everything after is slow. at the same time my 6 core cpu doesnt seem to be overly occupied..
Does anyone have tipps how to improve performance on raw2dng.exe?

I understand, that dual iso is for RAW recording only.
Is there a chance it will become available for H264 encoded recordings later, or is this not possible?

The raw video workflow is really time consuming, and if dual iso was possible with H264 directly in camera, this would be a fantastic time saver..

I looked for that feature in the zebras settings (yes, I looked in the documentary), because when I saw it on a camera, it was part of the zebra settings.

I see... thanks. But you could have been more precise when you only said "use false colors" - how could I have known you didn't mean the standard settings? I can't read thoughts and it wasn't obvious to me, that this other setting exists.

Still.. I can't use the feature, because theres no version for the Mark III that supports false colors.

How do you know that I didn't try?
I tried it a few months ago with my Mark II. I think it's irritating, when all colors are wrong. It may work for you, but it doesn't for me.
There's no way to tell if the white balance is right - especially when moving from indoor to outdoor while filming.
And for a visual person like me it is not possible to evaluate the look when you have 3bit colors.

Also, as I said, the Mark III doesn't have the false color feature enabled.

[terrible]

But... false colors look terrible! :-O

I'd like to see the real colors while recording...

(also false colors are not yet available on the 5D Mark III)

Right now zebras only show values above or below a certain threshold, so that's good for detecting over- and underexposure.
I'm looking for a Zebra setting that only highlights values between 68% and 72% so I can assure that skin tones are always exposed correctly.
Could this be included in future builds?

I was trying to make ML auto-boot on my Mark III - unfortunately without success.
I read the last few pages in this thread and tried to figure out what to do.

Now, what I did is this:
I downloaded "ML for 5D Mark III - Alpha 3" from this tread and additionally autoexec.bin from this url: (http://www.freefilehosting.net/autoexec_1) that user NerveGas posted a few days ago.
I put all files on my card and used eoscard.exe to make the card bootable.
I put the card into my Mark III and turned the camera on. It didn't autoboot. Manually starting ML works fine though.
There's also no autoboot option in the ML menu.

What did I miss? I thought, all I need is the autoexec.bin, which, as far as I understood it, is enabled for auto-boot?

Oh :-O Is this a thing that will be solved later or is the audio chip a hard one (and therefore those features probably not be included at all)?

Can we expect the analog/digital gain options to be included in the next alpha? They were actually one of the main reasons I used ML on my Mark II, because without, audio recordings are terribly noisy, and with, the audio sounds much better..