Tragic Lantern for 6D

[teo770]

Does "beep" sound works in the newest "raw_rec.mo -shrinkwrite" build? I have it ON - there is no sound but maybe there is some setting I missed. In some of the previous versions it was ok.

For bip sound, use
Waveform: Sine
Tome frequency: 1760 Hz

Worked like that for me.

[1%]

I just checked.. its not beeping for some reason. Wav is recording tho.

5X framing preview not working either... wonder if it was taken out.

[teo770]

1%, about buffers. Has i understand, you have the ability to dim a few buffer chunks, around 30MB, and the last buffer is made of the last free memory adressable so size may vary. Right ?

You allocate buffer chunks dynamicly at the beginning just before recording ? Acording to free mem available ?
During recording, you have the hability to resize buffer chunks ?

Another dumb question:
For testing purpose, is it possible to record black & white DNGs ?
Without color data, DNGs would be smaller we could record full HD perhaps... I know it sounds silly recording RAW in W&B but, it's a test, to see how far the 6D can go in resolution...

[pio_hyun]

lastest file:

Global Draw ON: 1440x620 drop frame after 1780 frames
Global Draw OFF: 1440x620 drop frame after 2280 frames 

[1%]

Not sure how you would throw away all the chroma.. I know a1ex did it for playback.

You can't really resize the memory while recording.. I think the problem now is that smaller chunks are being used first and larger chunks end up at the end. Should be largest first and smallest last... that's how that 4 buffers module worked. The double buffer size is still 6M so that's not the problem.. its better actually.

But if you're blinking on buffer 2 and that chunk is 27MB only then I can see how that slows down writes. Maybe on 5d3 all chunks are >30MB? Even taking off the 4th star (expanding double buffer) and recording with the 3 larger buffers sped things up.

[teo770]

And buffer chunks are feeded sequencialy ?
When buffer 1 full, buffer 2 start to be feeded.. etc

As raid 0, to enhanced write speed, you can't create 2 buffers writing at the same time ?
Having 2x30MB + 2x30MB buffers feeded in the same time ?
I don't know if i am clear, perhaps it has already been explored ?
Probably cpu limitations/multitasking applies too.

There is probably a botleneck somewhere slowing down writing ops.

[1%]

You can't get 2 writes at the same time.. this would work on a PC but we don't have bandwidth as it is. Want as few of most efficiently sized writes. If writing ~2X mb is causing problems vs 31, 64MB write would be worse.

[noisyboy]

New thread for general discussion of Magic Lantern and RAW shooting on 6D can be found here:

http://www.magiclantern.fm/forum/index.php?topic=5530.msg37766#msg37766

Installation guide can be found on first page.

*If anyone who is using this thread for it's intended purpose wants to bookmark this page you can just copy and paste the above text to any queries relating to installation.

Thanks.

(now I can return to actually testing this thing myself! Hooray)

[teo770]

Interesting benchs about some popular SD cards:

http://www.hjreggel.net/cardspeed/cs_sdxc.html

[noisyboy]

Looks like 1% was right about them taking about 5% off the actual theoretical rate lol

(just realized how stupid that sentence sounded considering 1%'s name! Haha!)

[nandoide]

Hi, since las saturday commits till today last commits I've found two issues, on the downloadable bins or on the bins compiled by myself.

1) After I take the first raw video, the AF is gone: I can only do manual focusing after that. No AF on "AF-ON" nor the shutter button or whatever button with AF configured into.

2) After previewing raw video, I can no longer do 5x zoom: the magnifier button do nothing. But, as workaround if I activate silent pics burst and after doing a burst, 5x zoom comes alive. I think this was previously reported

And since last builds, the brilliant pixels on fps override on underexposed LV, are gone!!!!. 
Perhaps it's because this commit:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/01b2a6799e16989f532086c37131acb4ce7d9c0a

I can't reproduce again, it's a pity.

[teo770]

Release: [113] Sorting.zip
Card: Sandisk extreme pro 32gb (95MB/s)
Mode: Photo LV
Recording: 4GB

1536x580, global draw off: 0 skipped frames
1536x580, global draw on: 0 skipped frames
1536x600, global draw off: 39 skipped frames (and 46/55 skipped frames in video mode)

[1%]

A1ex took off the AEWB hack and overlays are fixed so zoom button/af is hopefully not fucked up any-more.

Buffers sorted better?

[nandoide]

OK, after last commits the two issues were gone!!!

I not found any difference with previous versions (Sandisk Extreme-Pro 95 MB, 32 GB, FAT32 formated in camera):

105 frames 5x in photo mode 1880x680 24 fps (override)
113 frames in photo mode 1880x680 24 fps (override).
208 frames 5x  in photo mode 1600x680 24 fps (override).

[teo770]

4th buffer still an issue imo.

Any possibily we could choose buffers size in debug menu ?
So we could test 25/26/27/28/29/30 all sizes ?
If we get a given size of free memory (ex 100MB),
we set 25MB, would use 4 buffers
we set 20MB, would use 5 buffers
and so on...

Perhaps even buffers numbers so we could test every combination.

Hard/long to add or you already tested all possibilities ?
5/6 persons testing all buffers combinations.... we would definatly clear this question.
And verify card speed dependance. Perhaps some buffer size works better with faster cards, some other better with slower cards.

[1%]

I tried a bunch. There is data on buffer sizes in the thread where everyone ran tests. Right now its using 31 and some.

I tried both orderings, small to big and big to small. Got more frames regularly on the one thats in now, it was +/- 100 frames. Doing it the opposite way I got less frames most of the time but one time I hit a burst write of 30MB/s. Seems to do *something*

[kgv5]

1600x680 photo mode fps overr24 no zoom 209 frames, hack 225 frames

[teo770]

I tried dozens of combinations disabling Canon features and enabling no ML features but RAW_rec....
ExFAT vs FAT32
Gain = 0 frames or so few

I know Sandisk Extreme Pro can handles up to 80MB/s

It seems that all is in your hands 1%.... (!)
Too bad we can't help more.
Will continue to test and report every update !

[1%]

Hack definitely helps but buffer order still up in the air. *seems* to be doing something...

I'm kinda out of things to try. Only thing left is more memory.

Think the issue with the last buffer is this:

Star means the buffer is full. Last buffer is the one its using.. that buffer fills and it either has to stop or skip frames.

[teo770]

Do you know if the DNGs contain a jpeg preview ?
Without preview, files are 5-8% smaller...
Could gain some write speed.

[1%]

I think preview was taken out... for this it just saves raw data. raw2ng was making the jpeg previews, etc.

[teo770]

Another way:

Use that kind of adapter and solder a S-ata port at the end !

http://www.ebay.fr/itm/SDHC-SD-Card-Reader-Extension-Cable-KZ-B19-FPC-/161027485292?pt=LH_DefaultDomain_0&hash=item257dfc6e6c

[kgv5]

Whoa, I wondered if such thing exists and here it is 

[noisyboy]

Another way:

Use that kind of adapter and solder a S-ata port at the end !

http://www.ebay.fr/itm/SDHC-SD-Card-Reader-Extension-Cable-KZ-B19-FPC-/161027485292?pt=LH_DefaultDomain_0&hash=item257dfc6e6c

haha! Good find! Doubt the camera would write any faster though even if you did use that.

[noisyboy]

This is interesting from a1ex over in the "uncompressed 14-bit RAW video recording" thread:

There was some slowdown in 5x after fixing the tearing (this required some more memory). Just pushed a fix that should restore the old speed (almost).