Tragic Lantern for 6D

[noisyboy]

Good news: no skipped frame anymore in 1504x600
I forgot to set Picture quality in Canon menus ! Set it to jpeg S3

Hmm... I haven't been doing this and have been getting that res with the card I have anyway. Wonder if this will make a difference to me...

Well done though! Enjoy it

[noisyboy]

Good news: no skipped frame anymore in 1504x600
I forgot to set Picture quality in Canon menus ! Set it to jpeg S3

Well blow me down! Good discovery! Just managed to push my 1540x640 recording from recording 2000 frames to recording up until I hit the 4GB limit with NO frame skipping! Could probably have gone on a lot longer too!

Exciting! Thanks dude!

[kgv5]

Confirmed! there is a difference with S3 setting, 1536x640 is now continous 

[1%]

For realz? Maybe that path is less intensive on the CPU? I don't see a single MB gained from S3.

1320x540 is working for me in 640x480 mode + S3 only using 2 bars of buffer @ 28MB/s write

[noisyboy]

Well blow me down! Good discovery! Just managed to push my 1540x640 recording from recording 2000 frames to recording up until I hit the 4GB limit with NO frame skipping! Could probably have gone on a lot longer too!

Exciting! Thanks dude!

In fact - that said - just changed back to L-Jpeg and am getting same results. How very strange.

[noisyboy]

I must have changed something else between last night and now coz yesterdays testing gave me a much lower performance. Maybe even I have a different (but same model) card in? Back to the testing

[teo770]

My best perf at the moment: bullet proof 1504x600 24p, inside and outside 100-6400 iso, from f4 to f22
with jpeg only both L or S3, no RAW at all,  Global draw ON, with focus peaking.

About vignetting in AE, i'm dumb ! We are using center part of the frame ! Useless !

Update: with the last raw_rec.mo - buff, 1536x600 24p is rock solid too
In my cam, 4th buffer is 14Mb

[noisyboy]

Update: with the last raw_rec.mo - buff, 1536x600 24p is rock solid too
In my cam, 4th buffer is 18Mb

Sweeeeet! Gonna try that

[teo770]

We are not far away from 1536x640 (2.35 aspect ratio) because frame drops are only 50 per 1.5GB !
(turned off EVERY canon enhancement)

update: 4th buffer is somtimes 14, sometimes 18Mb

[1%]

Sometimes its 14, sometimes 18.

What would be good to do is allocate 4x30MB and then allocate 10MB at the end. Right now its doing 10MB, 30, 30, 30, 14/18.

[teo770]

splitting buffers in 20 or 25 Mb is possible ? (to try)
or even in 10Mb chunks

[xcreativ]

I missed a bit of discussion. Prompt, Magic Lantern already "learned" to write Jpeg sequence, instead of RAW?

[Veggietech]

Hey.

I can't figure out how to use the raw_rec module. I can click "load modules" in the ML menus, and I see it in the list. But I can't configure it or use it. What am I missing here...?

Thanks!

EDIT: Figured it out!

[1%]

You could but you want the biggest ones possible so that it writes faster.

So latest I shrunk the double buffer to 5MB as that is the largest likely frame... then first time I get 4x30MB and everything is great... second time it goes down to 28MB chunks and only makes 3 of them. WTF.. like its not being freed properly?

Allocating 4MB gives us back 30MB buffers consistantly... I dunno if that covers bigger frames though.

[teo770]

Frames seems to be around 1.5Mb
An ideal 1920x1080 frame would be 2.1Mb max, no ?

[1%]

Not sure, take one and check. You can try the latest module and see if it speeds things up... For 600D this doesn't work so well I think. 10MB left over only so no difference. But on 6D we're now using most of the mem. We'll never record at those bigger ~2k frames anyway without skips.

[noisyboy]

Dude - would you mind popping the now module in a url on ge.tt or something? Can't get at it for some reason but have no problem with the others. Thanks

God knows what I've changed now but seem to have lost the ability to record up to the 4gb limit on 1540x640. It's back to an average of 2000 frames. Gonna start logging everything now.

[teo770]

Last "raw_rec.mo - 4 buffers, no worries":
1536x640 is ok till 1750MB, after that, all buffers full, frame drops begin.

[1%]

So better or worse... seems better on my end.

http://ge.tt/9Co39kg/v/0

[teo770]

Of course better.

Tell me, when recording RAW, which parameters can you modify/adjust appart buffers size and resolution ?

[noisyboy]

So better or worse... seems better on my end.

http://ge.tt/9Co39kg/v/0

Will try now

This is messed up though.

Seriously don't understand this but basically when I put the card back in my camera with the "raw_rec.mo - buff" version it gave me much less performance in recording 1504x640 (which I could do previously since this afternoon but now get about 300 frames). So anyway, just for shits and giggles I tried to record 1536x600 and it allows me to pretty much hit the 4gb limit.

Would love to know what gives

[1%]

Buffer is in raw_rec.c... resolution is there too. Also finding that certain frame sizes will record better and there is something happening at 1.5gb.. drops write by 2MB and then skipped 14 frames after recording many many with only 1 buffer bar.

I was definitely not doing 1320x540 last night with this few skips.

1280x540 = buffer full and many dropped frames... perhaps we need an indicator for frame size like LV_REC had not just predicted speed needed. That way we can find the best frame file size to write. I have a feeling after trying different allocations for double buffer that even or specific sizes will do better and its not just resolution.

[noisyboy]

So better or worse... seems better on my end.

http://ge.tt/9Co39kg/v/0

For a start - this is MUCH better when recording 1536x600 - it now stays on one star throughout!

[noisyboy]

Dude - you are a god damn genius! Just got 1500 frames with 1536x640!

[noisyboy]

Back to capturing up to 4GB limit on 1504x640 now (I say that - it stopped recording at about 2,500 frames so guessing that was what it was).