Messages

[during recording]

@baccinoluigi, are you saying that you got liveview during recording ?
I've tried (on the 6d) the latest raw_rec module from 20 november, and during recording liveview freezes...

First, one question: Does live view work on the 5dIII while 10bit raw recording ?

Second:
Wow, great amount of detail, with youtube compression

So Canon 5dIII with magic lantern:
  3K, 10bit raw (continuous) with 1:2.67 aspect ratio and crop factor of 1.8

Canon 5dIV:
  4K, 8bit motionjpeg with 16:9 aspect ratio and crop factor of 1.7

By replacing the battery I mean, remove it from the body and put it back in.

This is sometimes needed if the on/off switch from the camera won't power down your camera...yes as weird as it may sound, when the power switch is turned to 'off' your camera can still be alive and kicking and consume power from the battery 
It's sort of the same if your desktop computer 'freezes' and you can't shut it down normally in software, you have to force the power supply to 'off' to make it work again.

I have no experience with such long recording times.
But I can't imagine that it can cause permanent damage.

Probably some autoexposure settings at work there.

For filming without autoexposure, you must be in M-mode on the mode dial and set shuttertime, aperture and ISO values yourself.
This was probably filmed in Tv,Av or some other mode.

The live view freezes during recording in 10 and 12 bit.
Do you think this will be fixable, is canon live view capable of showing 10/12bit stream ?

[Canon 6d]

Did some testing with the 19 november build and new MLV_dump on the Canon 6d

First frame 00000.dng = always corrupted.

10 bit normal mode and crop mode-> always good
12 bit normal mode and crop mode-> sometimes wrong (diagonal purple stripes along the frames) sometimes good
I'm trying to figure out why 12 bit sometimes works and sometimes won't work ?

About the newest MLV_dump (I'm on osx), it only works with 10 bit.
In 12 bit mode, the newest MLV_dump finds about 40000 cold pixels, which results in frames with 40000 colored and black specles in them.
The same MLV files processed with MLV_dump version of may 2015 are fine.
In 10 bit mode, the newest MLV_dump finds zero cold pixels and gives normal frames.

You can 'install'  magic lantern.
In order to make use of magic lantern, the ML files must be on the memory card.

If you switch the camera on without a memory card, it boots up just normal (just a little slower).
If a card without ML is used, the camera will still boot up normal, it just boots a little slower, that's all.
If a card is used with a wrong magic lantern version(for example version for another camera or firmware) it will tell you with text on your camera display and the camera won't boot further.
So in this case you have to delete the wrong ML files before you can use this specific memory card.

I don't know what will happen if a card is placed with the right magic lantern files, but the card got corrupted. But that sounds very unlikely to happen. And if it happens, it probably just won't boot. Remove battery, replace battery and try another card.

That said, I'm only familiair with magic lantern on the 6d

I think topicstarter means 720p in normal 1080 mode.
So normal 1080 mode on the canon 6d in combination with magic lantern raw recording, resolution settings for raw recording 1280 x 720 (raw recording crop within the raw menu).
This mode is really usable.

The fast 50/60fps 720p mode is indeed worse.
But still, with a conversion to DNG files and the right raw editor tools, decent results are possible.

Upscaling from 720 to 1080 is a lot.
you might want to experiment with higher resolutions and limited recording times.
Like 1600x900.
Maybe even change the aspect ratio to 1/2.39 instead of 16:9.
I have a 6d and use 1728 x 720 resolution a lot, gives you about 10 seconds at 30fps.
Upscales really nice to 1920x800 resolution.

Also, moire/aliasing is bad on the 6d, same as most Canons because of the lineskipping.
But if you use raw recording and export to raw dng files, you can fix a lot with the right raw editor.
Watch what the Free/Opensource raw editor can do with Raw dng files from the 6d

http://m.youtube.com/watch?v=MweH3RAssXs

Search for full-res-silent-pictures.
http://www.magiclantern.fm/forum/index.php?topic=12523.0
There is an option in magic lantern to work with electronic shutter.
So you can take full 22 megapixel resolution shots, without unnecessary shutter actuations.
In combination with the timer options in magic lantern makes this this a perfect workaround for timelapses.
Data rate is ofcourse big...

In video mode on the 5dIII you're limited by 3.5 or 3.2K I guess

The light pulse/flickering depends on your region, or more specific, how the electricity in your country works, is it 50Hz or 60Hz alternating current ?
This also dictates if you are in a PAL (25fps) or NTSC(30fps) region.

If you're in 50Hz country, try 1/50 shutter time, in 60Hz country try 1/60 shutter time.
When this doesn't work either, you can try finetuning the shutter time with the FPS override option in ML menu, you can choose between lowlight setting and exact shutter time setting.
Or try to go more to a 360 degree angle, so choose something between 1/50 or 1/24 shutter time.

I have a canon 6d and use Magic Lantern on it for more then 3 years, never bricked my camera
Worst things I saw happen is that it seems to brick, then I removed the  battery, then replace the battery and everything is fine


ML is on the card, if a card without ML is used, the camera starts up normal(although a little bit slower), because it's enabled for booting software from a memory card.

I have a 6d, so no dual slots, but as far as I know, ML always runs from the SD card in the 5d3.

As a 3 years user, and if you're going only for the raw histogram, I should say, what are you waiting for!

Thanks Walter!

Didn't know about that option to change it with 32 pixel increments.
Works perfect 

I've moved to the 1.1.6 today and i'm missing some resolution options in the MLV recording menu.
It goes from 1600 pixels wide to 1920 pixels wide.
I would like to get the 1728 and 1792 pixels wide options back in the 6d build, they were there before, or at least in the 1.1.3 build.
Can somebody get these options back in a new nightly build ?

That feature no longer exist, since raw video is way more exciting 
And the 6d has the ALL-I recording option available in Canon menu, so for best H.264 video, use the ALL-I option. No need for nitrate increasement.

Tested the 4 november version of Daniel on the 6d.
It works, sort of, although image preview is halted, the 'allow global draw' option is missing in the menu ?
And i'm missing sound, but that's probably normal for Raw_rec module 

First frame is always corrupted.
10 bit works
12 bit works
But it doesn't work all the time, there was also a MLV file with all corrupted frames and a MLV file with frames with vertical lines corrupted, pink/magenta vertical lines and a posterized image behind it.
I've used MLV_dump.osx for getting the DNG's and viewed them in RawTherapee.

The vertical line correction in MLV_Dump always seems to use exactly 1.000 or 1 numbers with the 10bit files, the files look ok, but is it explainable that it is always exactly 1.000 ?

[2008!!!]

Little late at the party 
I never thought this was gonna happen, that the hardware in the cams simply were fixed for 14 bit.

But WOW Respect for these findings!!! 

So to put things in perspective...
Canon released a full-frame DSLR in 2008!!!  with some sort of full HD video feature in h.264 compression.
And all these time this cam could record 10 bit raw video in full HD continuously direct to the memory card 
Canon could have saved some serious money by leaving out the chip that does the h.264 conversion(unless that is done by the digic  )

I have the 6d, so I don't know how good the 5dIII is, but it probably does a far better job, because it doesn't use lineskipping for video recording.
I don't have any experience with Premiere, but most video editors are able to separate a video in a luma and chroma part or change the colorspace to YUV.
Once you are able to only applie a blur to the color channels (the UV channels in YUV space) this should work.

Thanks for sending that motivating quote from Tom   

No worries I just wanna try to mess around a little with the 1000d code and see where I can get (probably nowhere... )
There is no rush for me, I've got my 6D to use with magic lantern.
And I'v got my good old trusty 1000D to do some try and error with Magic Lantern code on it.

Some other questions, what is the sequence the code is read.
There are some files:

Main.c
Main.h
Entry.s
Entry_subs.s

It looks to me that things are run/started with the code in the Main.c file.
But where does it use the Main.h file for ?

Looks like the entry.s contains the ASM code for the canon cam, so here are the actual commands for the camera actions.
But where is the Entry_subs.s file for ?

The camera LEDs don't do what I expect based on the code 

Now I do see with compiling, that it shows a lot of error messages in the main.c so that could explain why it doesn't work as expected.
This main.c is from Coutts, http://bitbucket.org/coutts/1000d_dev/src

The error messages while compiling are:
-----------------------------------------------------------------------------------------------------------
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc    -c -o entry.o entry.S
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc    -c -o entry_subs.o entry_subs.S
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc -nostdlib -march=armv5te -fno-builtin -Wall -pedantic -std=gnu99   -c -o main.o main.c
main.c: In function 'dumpmemo':
main.c:19:3: warning: implicit declaration of function 'FIO_CloseFile' [-Wimplicit-function-declaration]
   FIO_CloseFile(f);
   ^
main.c:22:2: warning: implicit declaration of function 'FIO_OpenFile' [-Wimplicit-function-declaration]
  f = FIO_OpenFile("B:/ROMDUMP.BIN", 0, 0644);
  ^
main.c: In function 'MyTask2':
main.c:34:2: warning: implicit declaration of function 'msleep' [-Wimplicit-function-declaration]
  msleep(5000);
  ^
main.c:37:5: warning: implicit declaration of function 'prop_request_change' [-Wimplicit-function-declaration]
     prop_request_change(0x80040007, &x, 4);
     ^
main.c: In function 'CreateMyTask':
main.c:92:2: warning: ISO C forbids passing argument 4 of 'CreateTask' between function pointer and 'void *' [-Wpedantic]
  CreateTask("MyTask2", 0x1A, 0x2000, MyTask2, 0);
  ^
In file included from main.c:1:0:
main.h:2:12: note: expected 'void *' but argument is of type 'void (*)()'
extern int CreateTask (const char *name, int prio, int stack_size /*?*/, void *entry, long parm /*?*/);
            ^
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc -nostdlib -march=armv5te -fno-builtin -Wall -pedantic -std=gnu99 -Wl,-T,link.script -oAUTOEXEC.arm.elf entry.o entry_subs.o main.o link.script
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-objcopy -O binary AUTOEXEC.arm.elf AUTOEXEC.BIN

-----------------------------------------------------------------------------------------------------------

Thanks!  it works 
It creates a autexec.bin file.
Time to mess around with the main.c and other files 

Hmmm
I don't get it.

At this moment when I do a firmware update with the 1000d.fir file from Coutts, it let's the blue led blinking.
I was thinking that the camera was executing the blue led blinking from the autoexec.bin
But even without a autoexec.bin on the SD card, the blue led is blinking after firmware update with the 1000d file...

What am I missing, how can I make the code I change in the main.c file to take effect on my 1000d ?

Looks that I need to compile a new fir file, how do I do that ?

I found the 'assemble_fw' command 

Now I'm messing around with the code.
I perform the 'make' command to get the autoexec.bin
The I do the 'assemble_fw' command
The I do the make clean command

Is this the right way ?

The binaries are already there, I know.

I would like to mess around with the main.c file and try some basic stuff.

See this topic:
http://www.magiclantern.fm/forum/index.php?topic=14732.msg172779#msg172779

I'm now trying to make both LEDs blink, in alternating sequence

But at the moment I can get it to make a new autoexec.bin from the changes I made in the Main.c file

It's indeed very old, all the files are from 2011 

Make zip gives this error

make: *** No rule to make target `zip'.  Stop.

[Still seems to be something wrong with the linking to the arm-none-eabi-gcc files]

When I just do the command 'make' I get this error message:

arm-none-eabi-gcc    -c -o entry.o entry.S
make: arm-none-eabi-gcc: No such file or directory
make: *** [entry.o] Error 1

Still seems to be something wrong with the linking to the arm-none-eabi-gcc files 

Just to make sure I get things right how this compiling works:

You open Terminal, go to the directory where your source files for your camera are:
  In my case I've got these files from coutts to start with:

  1000d.fir
  AUTOEXEC.BIN
  assemble_fw
  e6kr5107.fir_0_header.bin
  e6kr5107.fir_1_flasher.bin
  entry.S
  entry_subs.S
  header.bin
  main.c
  main.h
  make_bootable.sh
  makefile

Then in terminal run the command 'make' and the it follows the rules in the makefile file.
The makefile contains this:
-------------------------------------------------
name=AUTOEXEC
entryadr=0x800000

CFLAGS=-nostdlib -march=armv5te -fno-builtin -Wall -pedantic -std=gnu99
LDFLAGS=-Wl,-Ttext,$(entryadr)
CC=arm-none-eabi-gcc
AS=arm-none-eabi-as
OBJCOPY=arm-none-eabi-objcopy

all: $(name).BIN

$(name).BIN: $(name).arm.elf
   $(OBJCOPY) -O binary $(name).arm.elf $(name).BIN
$(name).arm.elf:entry.o entry_subs.o main.o link.script
   $(CC) $(CFLAGS) -Wl,-T,link.script -o$@ $^

entry.o:entry.S

main.o:main.c

entry_subs.o: entry_subs.S


clean:
   rm *.o; rm $(name).arm.elf
-------------------------------------------------

when stuff works, I should end up with a new autoexec.bin file.