Messages

Thnx. Worked even without Ctrl-click the first time.
Maybe because the folders 'magic-lantern' etc. where already present?

Where can I find crop_rec mlv lite with sound support?
It is almost impossible to search all those branches.

You're right. 80D isn't working yet. All modules failed to build.
Did compile in 80D-troubleshooting branch.
What is best way to test the Compile.app install?

I also got this warning:
*** WARNING: 64-bit GDB is known to have issues.

Are there ROM-dumps for the 80D and 6D Mark II?

Tried to compile 17  80D.101
I get the next error after each command:

********************************************************
WARNING: module mlv_rec failed to build, deleting
********************************************************
Unfortunately the terminal is cleared after compiling.
So it is impossible to see the other errors.

I will remove the magic-lantern and qemu-eos folders and start from scratch.

Yep. Tried Ctrl-click the first time. Failed.
The latest macOS 10.13.4 on an iMac (Retina 5K, 27-inch, 2017).

P.S. As far as I 'know' it is working alright now. Still learning!  ;-)

Error when installing Compiler.app:
'main.command' can not be opened because Sandbox is not allowed to open documents in Terminal.

P.s. 'Show contents' in Compiler.app and running 'main.command' in Terminal did the trick!   

I've just tested sorting buffers but on 60D it doesn't change anything. We've got 11 buffers (8x32MB + 1x22MB).

Eleven buffers? I stopped counting after 9!  ;-)
My 60D and ML shows: Alloc: 31M+31M+31M+31M+31M+31M+31M+31M+23M
Are these hardware differences a way to identify the difference between the 'slow' and 'fast' 60D's?

Thanks a1ex!   

First of all, forget the multiples of 160 & use Canon native ISOs (100, 200 etc...), but don't go over 1600. I find 800 to be the best option.

There has been said a lot about 'native' ISO's. If you look at page 62 of the Canon Rebel T2i (550D) manual, you'll see the following ISO speeds: Auto, 100, 200, 300, 400, 800, 1600, 3200 and 6400. So it's safe to assume that these are the real native Canon ISO speed settings.
So why all the fuzz about 160, 320, 640, etc. The 160-multiple ISO's are actually the cleanest not because they are 'native', but because they are a result of a digital exposure pull. This pull brings down the exposure of the entire image, and hides much of the noise that would be visible at the next higher ISO. ISO 125 is actually ISO 100 with a 1/3 stop digital exposure push, etc.
The real question is: how does ML handle with these 'tweeners' as ML captures LIveView frames. Are the 'tweeners' still pushed or pulled?

Green? Mine's are red since the latest build.   

http://picturepush.com/public/13267123

Top left corner of frame, always in the same position!

pls. download new build, I replaced a zip file after a1ex's modifications.. (delete all files in modules folder, there is a LOADING.LCK file or something like this)

@merekk   Thanks for the quick response!   

Modules are now loading automatically again!
Did shoot 4 clips 1782x791@25FPS
First did have 2 frames with magenta block mis alignment, other three were fine.

Getting more frames at 1782x792@25FPS: 118 now.

Did get this error, because modules didn't load!

Linking.....
tcc: error: memory full
exit (1)

Disabled and enabled bootdisk flag. Working again.

Three tries with latest build, first with magenta blocks, two were allright.
Getting 1 frame less, now 107 instead of 108 (1782 x 792 @ 25FPS)

Each time the 60D is switched off the modules won't automatically load, when switched on.
Each time giving the same error as above!     

Devs don't cheat 

What about these images?

You must be one them to call noise images!   
Technically I suppose the article is right. Higher ISO, less dynamic range stops. I agree.
But in my years of experience, higher ISO is more noise.

Look at this quick and dirty test of my own. Which part of the image is noisier en which part has the higher ISO?
http://picturepush.com/public/13265059

If you have a lot of 16mm lenses, the Black Magic Pocket Camera can be a good choice, otherwise your cropfactor will be 2.3!!!!!
If I were you, I would cancel and go for the Canon 5D MarkIII.

Not that stupid! Just think that maybe people are over looking the potential of the 60D _ yes i'm cursing the fact that they upgraded the 50D & left out the CF card option!
But couldn't there be more buffers involved with that extra memory, which you said was available - so instead of x8 31M, we get x10? Or have i not understood a thing?

Those buffers are memory hardware in your 60D. Eager to rebuild yours?   

While your 60D is open you can implement a Black Magic Design SSD drive the same time!   

Look at the pictures from here: http://www.magiclantern.fm/forum/index.php?topic=5693.msg41110#msg41110

Which is noisier? ISO 100 or ISO 3200?

You are cheating!     You forgot to mention that that is the case when using ETTR!

Heh, I thought it's clear for everybody that more light = less noise.

Also higher ISO = less noise (all other things being equal), but that's another story.

Well, in Digital Video, pushing gain gives more noise. And we always try to keep it to 0!
In digital photography they still use the 'ISO' magic word, but technically speaking it is just gain.

So yes, I'm very surprised by your second remark.   ;-)

Think the f stops were about 4 & 11.

Why the big difference in lens stops? 3 stops? ETTR needs more light or the other way around?

Going to re-shoot some scenes for a short film using RAW & it will be a low light scene at a desk.
I have been following the ETTR principle & this is the result.

Light from a table lamp.
Everything shot @ ISO 800
16:9 1728x992 @ 23.976 fps (108 frames or 5 secs).
Lens F Stop was the only difference.

Looking very clean!
What lens did you use?

I was wondering: isn't there any possible way of squashing the raw frames thru digic in a basic zip algorithm to reduce their sizes before dumping them thru bloody sd writer bottleneck?

Yep, you got that already for free!
It is called H.264 in a QuickTime MOV container.     

This chart states that the 60D works with ExFat formatted SD-cards.
http://www.magiclantern.fm/forum/index.php?topic=6215
During testing ML RAW last week trying to get the maximum number of frames, I formatted a SD-card in ExFat on a Mac.
ML didn't work on this card, did anyone succeeded in ExFat format on the 60D?

Hmm. I've been holding off opening the 95mbs card I ordered as most people were saying it doesn't make a difference. If it helps at 720p it would be worth it though.

Maybe the resolution you want to use doesn't give a big difference.
Look at the whole list I made:

All tests @25FPS.

SD-card: Lexar 16GB 60MB/s
1280 x 720 px 16:9       275 frames
1280 x 704 px 1.85:1    295 frames
1280 x 640 px  2:1      346 frames
1280 x 592 px  2.20:1   420 frames
1280 x 544 px  2.35:1   524 frames
1280 x 544 px  2.39:1   524 frames
1280 x 512 px  2.50:1   630 frames
1280 x 488 px  2.67:1   734 frames
1280 x 432 px  3:1         1188 frames

1728 x 922 px 16:9         108 frames

SD-card: SanDisk 32GB 95MB/s
1280 x 720 px 16:9        315 frames
1280 x 704 px 1.85:1     335 frames
1280 x 640 px  2:1       486 frames
1280 x 592 px  2.20:1    516 frames
1280 x 544 px  2.35:1    659 frames
1280 x 544 px  2.39:1    659 frames
1280 x 512 px  2.50:1    791 frames
1280 x 488 px  2.67:1    1078 frames
1280 x 432 px  3:1       2317 - 2118 - 2283 - 2079 - 2215 frames

1728 x 922 px 16:9           108 frames

................
If we had a CF card slot we would almost certainly be in 5D3 territory & with a near enough S35mm sensor!
...............

If the 60D would have a CF-interface the buffer wouldn't be that big!

50D  Continuous Shooting mode 6.3 frames per second, 90 JPEG's
60D  Continuous Shooting mode 5.3 frames per second, 58 JPEG's

After Continuous Shooting mode watch how long it takes to write all pictures to the SD-card!
So, in my opinion, Canon made the buffer extra large to make it more or less comparable with the 50D! 

......
The really annoying thing for us is that we have the best buffer readings of all the cameras!
Yes even better than 5D3!
This is why we can get a few seconds recording at our full resolution - 1728x922 (108 frames).
However, because we have SD cards we can't take advantage of this fully!
If we had a CF card slot we would almost certainly be in 5D3 territory & with a near enough S35mm sensor!

Why when they upgraded the 50D to the 60D did they leave out the CF cards?! Bastards!!!!!!!

When they upgraded the 50D to the 60D they did not only leave out the CF-interface but also changed the quality of the body.
The 50D was build like the 5D, all aluminium chassis. The 60D has a shell that's made of polycarbonate resin strengthened with glass fibre.

But I still love the 60D!      

What is the ETTR exactly? 

ETTR: auto-expose to the right to max. dynamic resolution & minimize noise! Short enough?   

There were some amazing nature-shots handheld taken with a 300mm lens and ETTR in the 5D section, but I can't find them anymore! 

Edit: Found them! 
http://www.magiclantern.fm/forum/index.php?topic=6076.msg46130#msg46130

........
So in what conditions can't you process the RAW file/s?

I know that the max crop factor that we can use is 1728x... - if you try to record at higher sizes it won't let you open them.
Also, when you first turn on camera & go to the RAW video menu, you will notice that it says 1728x... as default, but you actually have to go into the menu & select this value (as when you do you'll see that it was set at a higher value but reading/telling you the lower value).
So, when you select a higher value it will still tell you that you're recording at 1728x..., but you can't record at this level & have to ignore what it says & still select the highest value of 1728x... (or a lower value).

raw2dng won't recognize the RAW's as a RAW-file (forgot the exact name!) and won't convert them to DNG's.

ML (RAW) is for multiple Canon EOS camera's and I think the 60D doesn't have high priority by the developers.
The focus is probably on the Canon 5D MarkIII, so untill that version is stable they will look at other models (my guess!)
and sort it out. Until then we are living on the edge!