New writing strategy - variable buffering

Started by a1ex, June 20, 2013, 05:08:30 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

aaphotog

Quote from: a1ex on June 20, 2013, 06:51:56 PM
Straight from the card, not packaged:

autoexec.bin, raw_rec.mo and 5D3_113.sym
I replaced the files on my sd with these 3 files and the camera wont boot.
Should I be doing something additional?

dariSSight#1

Correct me if I'm mistaking but it's the 5D Mark II & III the top DSLR from Canon and isn't Magic Lantern pulling the most out of these 2 DSLR? I'm just asking because I'm extremely grateful by the work you guys do and I'm hoping you don't stop pushing the 5D Mark II, because I read a lot on these forum about the 6D and other Canon cameras. I just want you guys to give me a straighten out, I would love to hear that 5D Mark II can get variable buffering before I start reading 60D is been tested. I know I know I know, I'm selfish. I'm working on it ;)

g3gg0

with my buggy CF card it gets now >1k instead of ~100 frames when recording in 1080
Help us with datasheets - Help us with register dumps
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!

a1ex

Cool :D

The strategy is universal, it's trying to use the available resources in the best possible way. It measures the card speed on the fly.

You can use the module from my previous post on any camera (the code is portable). The autoexec and sym are only for 5D3.

aaphotog

I figured it out.
SHIT Alex, this is amazing!!!


Recording 2560x1090 on a Sandisk 600x CF 16GB card

with the june 16th build
72 frames with memory hack off, and preview set to auto
120 frames with memory hack on, and preview set to 'HaCKed'



With the new 3 files you posted, i;m getting
142 frames with memory hack off, and preview set to auto
258 frames with memory hack on, and preview set to 'HaCKed'

as you can see, it doubled!

With the CF that I have, I've always been able to get continuous 1920x1080, so I thought I'd go with something a little more demanding.

BRAVO!!!

dubarry

WOW!

60D 304 frames  1280x720  16x9   (previously 175 frames)

1728x692  185 frames 2.50

Very nice.

kgv5

Quote from: aaphotog on June 20, 2013, 10:27:39 PM
I figured it out.

So could you please tell us how did you do that?
I replaced the old raw_rec.mo with the new one from the post #7 in my 6D but no difference. :-\
www.pilotmovies.pl   5D Mark III, 6D, 550D

Viente

Awesome job! Got 200 frames in 1920x on 50D in crop mode, was about 70 before.

dariSSight#1

Quote from: a1ex on June 20, 2013, 10:22:03 PM
Cool :D

The strategy is universal, it's trying to use the available resources in the best possible way. It measures the card speed on the fly.

You can use the module from my previous post on any camera (the code is portable). The autoexec and sym are only for 5D3.


Cool, I will install and get back to you. By the way does the AutoExec Bin activate the module?

Mido

Very nice.
5D3, KomputerBay 128GB 1000x
1920x1080 @25
Before 300 frames
Now 500 frames
Thank you!

a1ex

And I've just got a proof that this strategy is far from optimal :D

(read: some more improvements may be coming soon)

Jakobmen

Canon 5D3

dariSSight#1

A1ex are we losing some resolution with variable buffering because the highest resolution with 2.20.1 was 1880x854 but now it's 1872x850 and its not continuous on a Lexar 1000x, but 1856x844 is continuous.

noisyboy


Rush

Canon 600D 24p variable buffer improvements vs old method
(before max seconds -> now max seconds).

W/o line skipping:
1280x720 - 3 > 6 (crop-factor = 2.16)
1280x536 - 6 > 14 (crop-factor = 2.16)

16:9 line skipping (unsqueezed resolution in brackets)
1280x434(720) - 29 > 42 (crop-factor = 2.16)
1344x456(756) - 11 > 27 (crop-factor = 2.06)
1472x500(828) - 5 > 11 (crop-factor = 1.88)
1600x542(900) - 3 > 7 (crop-factor = 1.72)
1728x586(972) - 2 > 5 (crop-factor = 1.6)

2.39:1 line skipping (unsqueezed resolution in brackets)
1472x370(616) - 50 > very long (crop-factor = 1.88)
1600x404(670) - 8 > 19 (crop-factor = 1.72)
1728x436(724) - 5 > 10 (crop-factor = 1.6)

Thank you, a1ex!
Greetings from Russia!

1%

Promising... I wonder what it will do on 600D w/ dialog timers disabled.

lourenco

2560 x 1072 23.976 fps over 700 frames before frame skipping.  104 MB/s.
5D Mark III, CF Lexar 1000X 32GB, 24-105 F4L

squig

1920x448 (720) 60p 309 frames pre variable buffer, 436 frames with variable buffer. That's about 18 seconds of 2.67:1 slo-mo, very usable. 1968 frames hacked. The pre variable build needed 4 or 5 recordings to warm up to the 309 frames.

2560x960 24p continuous in crop mode.  ;D

1920 x 508 (818) 48p continuous.

Lexar 1000x 64Gb GD off.

1920x448 60p 568 frames with the Toshiba 1066x 64Gb.

Edgar Matos

Quote from: 1% on June 21, 2013, 01:20:00 AM
Promising... I wonder what it will do on 600D w/ dialog timers disabled.

Magic! But I'm still fixing the wetting problem. I think a bib can do wonders.

xNiNELiVES

Where Do you enable this? Do I need to format the card to have certain buffer size for this to work optimally?

ilguercio

1280*720 on my 60D went from 335 to 379-381 frames before skipping at 23.976 fps.
Canon EOS 6D, 60D, 50D.
Sigma 70-200 EX OS HSM, Sigma 70-200 Apo EX HSM, Samyang 14 2.8, Samyang 35 1.4, Samyang 85 1.4.
Proud supporter of Magic Lantern.

squig

You don't enable it, it's built into the raw_rec code.

xNiNELiVES

Quote from: squig on June 21, 2013, 03:52:24 AM
You don't enable it, it's built into the raw_rec code.

But what about setting the buffer size on the card?

ilguercio

Quote from: xNiNELiVES on June 21, 2013, 03:54:54 AM


But what about setting the buffer size on the card?
And what would this mean?
A card is a card, a buffer is a buffer.
The buffer is in the camera, the card can just do whatever possible to sustain the data rate if it's capable of doing it.
Canon EOS 6D, 60D, 50D.
Sigma 70-200 EX OS HSM, Sigma 70-200 Apo EX HSM, Samyang 14 2.8, Samyang 35 1.4, Samyang 85 1.4.
Proud supporter of Magic Lantern.

xNiNELiVES

Quote from: ilguercio on June 21, 2013, 03:59:54 AM
And what would this mean?
A card is a card, a buffer is a buffer.

I meant cluster size  :-\