Messages

71.5 / 101.9 / 64.5/ 101.0  (no picture in background, card was cleaned)
Took 3 shots, RAW, and then ran again:
54.5 / 101.9 / 65.5 / 101.8 (one of the pictures I shot was in the background)

Edit: @240 MHz

Edit2: Ran a couple other shots, and a video, and one more benchmark (did not restart the camera since first test)  65.4 / 101.8 / 66.7 / 101.0

Edit3: the average write speed during the tests was 64.6

Edit4: The 240 MHz option seems to work on my setup.I'll try to stay on that mode for a while and report. ==> RAW recording not working in that mode for longer than a few seconds, (first try was just a start stop video) got raw error and camera in state where I need to pull of the battery.

Edit5: Going back to 160 Mhz immediately makes everything working back.

I can confirm that the 166 MHz patch is working with my Lexar card. It's at least doubling the default speed. Tested continuous 3K rec one more time and it's working for more than a minute without a glitch. It's staying green except each couple of 15 secs, where it's flashing to orange for a second before coming back to green (maybe a buffer/cache issue, it's not affecting my record)

@Danne a few post ago I posted my values, tested with only SD in:
OFF        :        20.5 / 21.8  / 18.8 / 21.8
160 MHz:        50.3 / 70.1   / 65.6 / 70.1    ===> if only WRITE speed is what counts, that mode is the best as it's overclocked to the minimum and it gives the same average write speed results
192 MHz:        64.4 / 83.0   / 49.8 / 83.1
244 MHz:        63.5 / 101.7 / 50.7 / 101.8   ===> Best READ mode

With my cards I was not that far from the wanted bandwidth for continuous 3K. Doubling the SD write speed did it.

Okay, I did some test with the 166MHz Mode.

It's recording continuous 3072x1320,12-bits lossless (preview is cropped, but with framing it's usable to aim/focalise). I've ran a 1 minute long recording, kept green all the time. BTW I'm also recording sounds. I moved the camera a lot to make some sudden image change (and thus trigger some more activities), changed exposition during recording. Additional settings: card spanning on, preferred card CF, global draw off when recording. If it's counting, all my cards are formatted to exFat with default settings (did not played with cluster size).

ALL WORKED LIKE A CHARM. It was not the case before. It was working, but only for a couple dozen of seconds and with yellow indicators at best. What I can say is that the 166 MHz mode made my cards usable for raw recording.
I'm pretty aware that these are not the best fit cards for ML& MKIII, but the last versions of Danne's ML and modules made them pretty usable for the cases I'm aiming.

No problems while shooting. I'm going to play a bit with the patch on @ 166 and I'll try with the others after.

My cards:


Obviously I was tired last evening, but at least I did some benchmarks on the mkIII ^^

What can I use to benchmark the cards on a computer ? Tested them with SpeedOut :

The SD is reporting an average of 87 MB Read / 77 MB Write
The CF is reporting an average of 133 MB Read / 130 MB Write

I don't think I have a decent card reader, as I can record quicker than reading / writing the CF on the computer. It may not be bad (the adapter) with the SDHC, will try tomorow.

Well. The numbers seem to give you a point: reading speed is increasing way more than writing.

Here are the results, as following: mode,1st Write/1st Read/2ndWrite/2ndSpeed

sd module off: 20.5 / 21.8   / 18.8 / 21.8
160 MHz:        50.3 / 70.1   / 65.6 / 70.1    ===> if only WRITE speed is what counts, that mode is the best as it's overcranked to the minimum and it gives the same average write speed results
192 MHz:        64.4 / 83.0   / 49.8 / 83.1
244 MHz:        63.5 / 101.7 / 50.7 / 101.8   ===> Best READ mode

CF+SD Write: SD / CF => total
OFF       : 14.7 / 113.5 => 128.2
160 MHz: 43.9 / 93.1   => 137
192 MHz: 42.3 / 94.3   => 136.6
240 MHz: 54.7 / 89.5   => 144.2



I'll try to make some shot / raw videos in different mode tomorrow. It's anyway a BIG difference of minimum x2 in terms of write speed, just using the 160MHz.

I'm currently testing with a Lexar Professional SD3XCII 10 128GB x1000 with a theoric write speed of 150MB/s . When I'll test I'll also do it with the CF, it will be a Lexar Pro UDMA7 1066x with a theoric write speed of 160MB/s.

Wait and see.

Edited: fixed wrong assumption

Well, ok.
And when you say "Havn't found a way to disable patching yet" does it means that even with the moduel disabled the patching is still here ?

Hello.
Since the last update with sd overclock module I can't seem to be able to format sd card AND keep ML on it. It's formatting everything. The usual menu and copy log before formatting is gone.

I got some problems while trying to make a raw video 3k + fps override @2.5:
ML ASSERT:
RAW_IS_IDLE
at mlv_lite.c:969 (measure_compression_ratio), task shoot_task
lv:1 mode:3

shoot_task stack: 1c2498 [1c2600-1c0600]
0x000B6A18 @ 956f0:1c2590
0xUNKNOWN  @ b6a6c:1c2578
0x00B3B854 @ b3d710:1c24d8
0x0006A01C @ b3b91c:1c24c8
0x00069878 @ 6a084:1c2498

Magic Lantern version : Nightly.2020Jul15.5D3113
Mercurial changeset   : 8f38ee536de0+ (crop_rec_4k_mlv_snd_isogain_1x3_presets) tip
Built on 2020-07-15 19:47:31 UTC by danne@danands-MBP.
Free Memory  : 213K + 2445K

Did not stumbled upon this before, so I don't know if it's related to your build only or not.

No Problem with shooting so far. I'll try recording this evening.

Wonderfull work Danne & ilia3101 and a1ex !

I'll try it asap !

Everything is working fine so far here.

The crop rec integration is more intuitive this way.

There are a few modes that says preview broken, is it fixable ? What's the cause of it ?

Happy new year BTW

Thanks Danne for the hard work.

I updated my repos and it just built fine.

More testings tomorrow, have good end of year :-)

Wonderful Job, nice to look.

I particularly loved the last parts with sun & clouds.

A good work indeed.

hg update [name of the branch you want to switch on, without the braces]

make clean

make zip

It can complain about module_strings.h missing. On debian testing as I don't know very much yet about it, I commented the include and got it to compile.

I take pointers if any.

Edit:
Everything is working so far, with your branch build on my debian.

I don't get how I can correctly fork your branch and see it on bitbucket. We'll see what to do on that.

Yes, good job !

I've just tried to compile on debian testing, the classic unified branch for 5DM123.

I had to comment out the include module_strings, because the file is not present and it gives a compilation error.

Make zip made me a zip, I do not yet have a working qemu to test it, it'll come soon !

Thanks a lot for all the good job you're doing.

I'm testing a lot of your builds, and this one will be tested tonight. I'll be putting a review.

Danne, if you need me to test something special feel free to ask. As I'm a developer too I'll try to clone and build your version myself.

Done.

It's working like magic:

I really like this hack, I'll have to play with my old EF-S lenses :-D

A quick test with raw videos on a full moon. The aim was not to catch the moon details but the the clouds passing.

My preferred setting is the last one (3k 1.1 5x centered view)

It's just a quick test, so I did not used a lot of post processing/adjusting. Only MLVapp and Kdenlive.

I have a tamron 10-24 EF-S and it's definitely fitting inside my mark III.

I could take shots, but before reaching 16-17 I could see the black circle all around the photos, so I did use it but never under the aperture of 16-17 mm.

Today I'll try to make a raw video with that one, at 10mm / crop mode / whatever setting I can find which is working and not showing a black circle.

The crop mode on ef-s lens mounted on full frame look like a cheap trick but it may allow me to shoot nice wide videos with a cheap lens I already own.

Wait and see !

Hi timbytheriver.

ExFAT have the option to store files bigger (the size of your CF) than FAT32(4GB limit by file).

Best place for formatting ? A mark III will format to exFAT, or windows 7 /10.

Or linux.