Magic Lantern (RAW) Video format v2.0 (mlv_rec.mo)

[Andy600]

thanks for your test.
about IME: press Q to directly get to the OK/cancel buttons.

raw_rec:the performance is a bit worse than the legacy raw_rec module, yeah.
alex spent a lot of time to get the last frame out of the buffering mechanism.
the new module needs such optimization too.

Thanks. It's good to see it working anyway even with the performance decrease.

Q doesn't seem to be working on the 50D but I'm using Tragic Lantern so it may have been remapped. I'll have to check.

[1%]

We don't really have Q, only joy center. Its acting kind of like set, have to check how its set up exactly.

[g3gg0]

this version of raw_rec works better on my setup.

select:
Buffer fill method: 4
CF-only buffers: 3

this gives me close to 100MB/s - sometimes

[Andy600]

this version of raw_rec works better on my setup.

select:
Buffer fill method: 4
CF-only buffers: 3

this gives me close to 100MB/s - sometimes

This one is worse on the 50D. I tried 4/3 and various other settings and could only record 240+/- frames on the same card.

@1% - could we not use the PicStyle button for Q? It's not really needed for video and I think most users tend to set PS in the ML menu anyway.

[gnarr]

I posted a 5D2 clip a few posts above...

Well I'm still waiting on the IME module. Should I download it from the 5D3 package? Where's this located?

The file has no data in it (it's only 1 kB). But the same is happening for me now.

I just did a "clean install" on my 5D2, that is, I cleaned my CF card and installed the 5D2_Alpha_One package and updated it to the 2013/08/09 version. Then I installed raw_rec.mo from raw_rec_mlv.zip in reply #277 and autoexec and symbol from #221.

It gives me the same results as before. The camera is super slow for ~5 seconds after I press record and then fills the buffer and "stops", but in the raw rec menu it shows "stopping" forever and everything locks up after a few more seconds.

I tried turning on the debug trace, but I can't find the trace file. @g3gg0, are there any log files I can send you or something I can do to help with fixing this? Or are you still focusing on making the 5D3 version work good before looking into debugging other platforms?

Ps.
I still need a 5D3 file Anyone willing to upload one for me? It doesn't need to be large.

[CoresNZ]

Not having much luck converting these.

This is what I'm getting back from the dos command.

E:\>rawFiles\mlv_dump.exe -o mlv.raw -r M13-0212.MLV
Operating mode:
 - Input MLV file: 'M13-0212.MLV'
 - Convert to legacy RAW
 - Output into 'mlv.raw'
Failed to open file 'M13-0212.MLV'

Any ideas why this would be failing to open?

[Canon eos m]

the latest IME modules can be found here.
(see also http://www.magiclantern.fm/forum/index.php?topic=6899.0)

the latest raw_rec module including win32 exe and static linux binaries is here.
no guarantee that the linux binaries will work on your system (it's a 32 bit ELF for 80386)

g3gg0 getting about 104.7 mb/s on my 5D Mark III (1920X1080p) with this raw_rec.mo version. Going to try the one you posted a while ago.

[g3gg0]

E:\>rawFiles\mlv_dump.exe -o mlv.raw -r M13-0212.MLV

so your raw is in E:\ ?

[Canon eos m]

this version of raw_rec works better on my setup.

select:
Buffer fill method: 4
CF-only buffers: 3

this gives me close to 100MB/s - sometimes

Touched 106.1 mb/s with the version of raw_rec.mo

Card Lexar 32GB 1000X + 32GB Scandisk 95mb/s
Camera 2032X1040p
Buffer fill: 2
CF-only buffer: 2
No dropped frames

[Canon eos m]

Not having much luck converting these.

This is what I'm getting back from the dos command.

E:\>rawFiles\mlv_dump.exe -o mlv.raw -r M13-0212.MLV
Operating mode:
 - Input MLV file: 'M13-0212.MLV'
 - Convert to legacy RAW
 - Output into 'mlv.raw'
Failed to open file 'M13-0212.MLV'

Any ideas why this would be failing to open?

Do you have the M13-0212.M00 file in the same directory 'rawFiles'?

[g3gg0]

you have set cf only buffers to 2?
Should be better with 3

[xNiNELiVES]

1) intention, its still experimental
2) this was on 5D2, right? can you use these both modules (dont forget to enable trace) and send me your raw_rec.txt after recording with a spike? it should be in the root folder. upload it using http://upload.g3gg0.de and send me the [D/L] link (right-click, copy link)
3) if you stop recording, it should disappear
4) uhm, just dont enable it?

1)
2)
3) Even if I stop recording, the buffer status never disappeared. The rest of the info disappeared after a good 15 seconds or so.
4) I don't enable it but what happens if someone did? I realize this is only an experimental copy of the new MLV Format, I guess you'll just disable it in the final versions.

Will trace the bug with the lag spike.

[kgv5]

Newest module from #277
This gave me very good results, great work     : Buffer fill method 3, CF-only buffers 2

1920x1080 16:9  29,97fps >>>   ~109-110 (91+19) so shows continous ok.
2240x1260 16:9  24fps      >>>   ~113 (95+19) continous ok
2560x1090 2,35:1 24fps    >>>   ~115 (96+19) continous OK

I tested buffer=3 CF=2 and buff=3 Cf=3, after couple tries i had an impression, that B3CF2 speed was more stable, B3CF3 had similar speed but more variations. But its hard to say really, maybe just coincidence, when tried again it was stable, even maybe a bit faster than B3CF2.

[xNiNELiVES]

Newest module from #277
This gave me very good results, great work     : Buffer fill method 3, CF-only buffers 2

1920x1080 16:9  29,97fps >>>   ~109-110 (91+19) so shows continous ok.
2240x1260 16:9  24fps      >>>   ~113 (95+19) continous ok
2560x1090 2,35:1 24fps    >>>   ~115 (96+19) continous OK

I tested buffer=3 CF=2 and buff=3 Cf=3, after couple tries i had an impression, that B3CF2 speed was more stable, B3CF3 had similar speed but more variations. But its hard to say really, maybe just coincidence, when tried again it was stable, even maybe a bit faster than B3CF2.

These tests are crazy, 2.5k continuous, Jesus.

[Toffifee]

How about making a benchmark test that checks the different methods and logs it?

In a similar fashion A1ex made when RAW video first came out.
A bunch of people can do the tests and you could merge the data into one to compare the differences.

[kgv5]

These tests are crazy, 2.5k continuous, Jesus.

Yeah, its hard to believe.

Just for testing: If someone is interested in 2,8k 2880x1216 2,39:1 but >>20fps<<   - managed to record for 45 sec.
with super wide aspect 2880x1080 2,67:1 with >>22fps<< i get similar ~45sec. With the same super wide aspect but 24 fps i am getting ~6-7 sec.

EDIT: I was wondering what is real crop factor for different resolutions like 2,5k and 2,8k. 3x crop is for 1920 res i think, so for 2,5k should be about 2,3x (just like bmcc) and for 2,8k is should be about 2x, am I right?

[mucher]

I have got the feeling that the SD speed looks a bit low.

[chmee]

@g3gg0 what about a version freeze? i would begin to code a converter next days, but the things are changing almost daily. after this version freeze or a first reference mlv-file (with version-number) i could start..

regards chmee

[kgv5]

I have got the feeling that the SD speed looks a bit low.

5d3 SD controller max speed is about 20-21 i think. It is no 40-ish like 6D or 650D but slower and current versions are reaching almost the top.

[xNiNELiVES]

Whats the 5D2's theoretical hardware limit for its CF slot max speed?

[kgv5]

According to the chart from

http://www.magiclantern.fm/forum/index.php?topic=6215.0

it is 75 MB/s.

For 5D3 is 100 for CF +20 for SD so devs have managed to squeeze almost the full speed.

[xNiNELiVES]

According to the chart from

http://www.magiclantern.fm/forum/index.php?topic=6215.0

it is 75 MB/s.

For 5D3 is 100 for CF +20 for SD so devs have managed to squeeze almost the full speed.

LOL I said that because that what the max speeds we are attaining with Raw Video. It doesn't mean its the actual limit.

[kgv5]

ok, sorry, my mistake.

[Danne]

I tried some slowmo but only managed to squeeze about 75mb on cf with the latest compilation. Anybody tried it out? 50 fps 1920x672

[CFP]

Whats the 5D2's theoretical hardware limit for its CF slot max speed?

I saw benchmarks of the 5D Mark II reaching write speeds slightly over 90 Megabyte/s, just like the 50D.
And the 5D Mark III even reached 130 Megabyte/s. Its SD-Card controller's hardware limit is 21 Megabyte/s.