10bit iso 100
[a,ea] = read_raw('iso1600.DNG'); a = a - ea.black_level; a = a / (ea.white_level - ea.black_level); median(a(:))
ans = 0.33647
[a,ea] = read_raw('iso100-cmos0-443.DNG'); a = a - ea.black_level; a = a / (ea.white_level - ea.black_level); median(a(:))
ans = 0.32112
# 1600 * 0.32112 / 0.33647 = 1527
[a,ea] = read_raw('iso100-cmos0-443-adtg-888x-low.DNG'); a = a - ea.black_level; a = a / (ea.white_level - ea.black_level); median(a(:))
ans = 0.31355
# 1600 * 0.31355 / 0.33647 = 1491
[a,ea] = read_raw('danne-iso100-10bit.DNG'); a = a - ea.black_level; a = a / (ea.white_level - ea.black_level); median(a(:))
ans = 0.42959
# 1600 * 0.42959 / 0.33647 = 2043
Edit: further test reveals the actual ISO is actually *above* 1600. Test files (white level tweaked manually, right before the last histogram peak):Confirmed, slightly above 1600iso comparing your files.
iso1600.DNG
iso100-cmos0-443.DNG
iso100-cmos0-443-adtg-888x-low-iso1500.DNG
danne-iso100-10bit.DNG
@jimiz
Updated build for 5D3123 in my above post. Not tested so please report how it works.
All three tests, zipped DNG.
I also don't know what Danne has done "under the hood", and so it may be that the test is invalid for actual ISO comparison.
Ok guys, here's the proof everyone needs...
I'm a happy camper getting excellent results, and the last time I checked, that's what really matters...
There's a bit of loss of highlights, but for practical purposes it is negligible.
I was referring to my experiences with reduced gain by hand, not with Danne's experiment. I have only used it to take those test shots. It seemed like it was behaving the same way [...]
There's a bit of loss of highlights, but for practical purposes it is negligible.
- enabling Danne's crop_rec will alter the shutter speed; to cross-check with iso_regs you may have to use the shutter fine-tuning feature.
I wonder why it messes with the shutter speed and was wondering if it could be the case that if 'full range' option is selected in crop_rec, it messes with shutter time. And could it be that if this option is set to 'original' it won't mess with shutter speed ?
On a sidenote it would be cool if we now could continue testing pregain etc and see if we could get it rightly done.
#elif defined(CONFIG_100D)
#define TG_FREQ_BASE 32000000
#define FPS_TIMER_A_MIN (fps_timer_a_orig)
#undef FPS_TIMER_B_MIN
// no need to cause confusions as recording speed cannot handle such high fps in crop mode
// (ZOOM || MV1080CROP ? 1288 : 1970)) <-- these are ok while not recording.
// Hybrid CMOS AF II uses 60fps by default in LV/MV for the camera display
// to achieve a "snappy" autofocus by doubling the fps
// MV720 is not LV so we need to extend the definition for the LCD.
#define FPS_TIMER_B_MIN (fps_timer_b_orig)
adtg_new[8] = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 5) }; /* PowerSaveTiming OFF (5D3/6D/700D) adtg_new[9] = (struct adtg_new) {6, 0x8197, nrzi_encode(fps_timer_b - 5) }; /* PowerSaveTiming OFF (5D3) */Since my iso experiments was built on faulty assumptions about how analog gain registers and analog iso registers were related I decided to simply erase those code parts in following builds:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_5D3113_presets.zip
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_5D3123_presets.zip
What still is valid testing and developing is 1x3 presets together with playing around with analog gain registers creating 10/12 bit. Those two settings can still be found in the sub menu of crop mode.
In a longer perspective iso tweaking is still valid and could be developed further I´m sure. I might dig into this and revive some code parts in crop_rec later on but without mislabeling menu items.
Commit:
https://bitbucket.org/Dannephoto/magic-lantern/commits/4e18649356067e49e15134e432025acdb2b6f0a7
@DanneTry fomatting card in camera (non exfat) reinstall clean build.
modules loaded: crop_rec, mlv_snd, mlv_lite, mlv_play
res: 1920x1080p /14bit lossless (not crop mode)
CF (KB1066x) card seems to be working/saving fine when I revert to a previous 4K_crop-rec Danne build 2/4/19 :)
Still odd…
now it works im not sure what i had done in my first test. now i just clean install and turn on the anarmophic preset in crop rec and no more greenish black preview. i have a very slow 4gb cf card atm. wil test more as soon a i recieved another cardYes, bleeding edge stuff. Faster card will probably help. I set regs all over the place. A safety press on menu button and thrashcan once in a while to settle all regs won´t hurt too.
Try fomatting card in camera (non exfat) reinstall clean build.
Tried formatting your card to fat32 on computer and then format in camera?
Well, I can´t say what would work or not here. It´s all guesswork atm.
Clean format of KB1066x CF card in mac to exFATStill very unclear but I would say nothing is wrong with the ml builds. One thing is for sure. I would never trust that KB card.
Clean re-install of previous 4K_crop-rec Danne build 2/4/19 on SD card
All seems restored and working – except for one shot which didn't respond to stop button. Restarted camera, shot a few more tests at various res. All import working into MLVApp.
Tried a different Sandisk Extreme CF card with current state – all is well.
Totally weird! :o But very happy my camera is still alive! :)
I would never trust that KB card.
Try a windows formatting:
Do note that preview will look a bit greenish because of the workaround to get bitdepth reduced with analog gain regs. Shouldn´t be almost black anymore though and image files will look good.
@danne problem wit 45/48fps is the live view. If i set to real time framing is not correct and if i set to framing live view is not in real time so very difficult to shoot a moving object in practical.
New uploads for the 5DIII:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
- Fixed a bug when recording 50/60fps
- Better handling mv720p mode 45/48 fps when going in and out of x10 zom mode
New uploads for the 5DIII:stil the same problem. sometimes it works fine. the problems occurs after recording 3/4 times
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
About your screenshot it´s related to compression handling in mlv_lite.c. Something is affecting it so it correctly reports files are getting corruption issues.i get som corrupted pink frames
Doesn´t work at all or work and gives compression errors? I need my camera I believe...gives compression errors.
Posted two new builds:New build anamorphic test in5Diii 123. Thank you
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
Mainly I separated 45/48fps modes into two and they run in either 50 or 60p mode. Upscaled 48fps to 1060p:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.postimg.cc%2FzB9rF1w7%2FVRAM0-PPM-scaled.png&hash=181458eb29e8f69513c42c9cb85b5d7b)
Awesome!mv720p mode and x3zoom seems restricted to reduced height like what you get when in mentioned 1920 1:1 mode. I have a hard time figuring out a1ex pack modes on cmos regs but maybe once those numbers are "decrypted" we can revert to some more obvious numbers and start constructing more freely.
Is it possible to have these presets (45/48/50/60 FPS) in 1920 1:1 ?
adtg_new[3] = (struct adtg_new) {6, 0x8000, 5 + reg_8000};
adtg_new[17] = (struct adtg_new) {2, 0x8806, 0x6088};
- Refined anamorphic presets so it now gives continuous:
1808x2300(2:35.1) = 5425 x 2300
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Jul02.5D3113.zip
There's real time preview by the way. If in framing mode press halfshutter for cropped real time preview.
Yes, I understand what you mean, but what is a real purpose for such a preview? The proportions aren't correct, we can only see a massively stretched top part of an image.Danne, for me continuous recording in anamorphic 1600X2332< 16:9! :) :) :) another way round to preview framing before recording is press hold the AF Lock button (the lens should be in AF Mode)Cheers...
Why not test it? It sets optimised settings for anamorpic 2.39:1 recordings.
Once you run the script you are free to change anything after.
Anyone knows how to record continuous at 14-bit lossless at 1440p 24fps? I get pinky/black preview on my LCD screen.
These are my selected settings:
Global draw: liveview
fps override set at 24 fps
crop mode: 4K 1:1 and x3crop set
RAW video:
2656x1494
16:9
14-bit lossless
preview: realtime
croprec preview: auto mode
kill global draw on
sound on at 48khz
Any tips on what I am doing wrong?
Using build 2019-07-20 on 5d mark III firm.123
There is a misprint for iso climb: in menu it is mentioned INFO(5D3), but it does nothing
Part of the workaround technique. Framing is done from real buffer very slow and focusing can be done while holding halfshutter while recording. Then back into framing again. In and out. I can work with that and capture pretty much anything I want.
I don´t know if you have x10 focus aid enabled. Try disabling that if it´s the case.Tried both on and off. Nothing changed. But for now i use zoom button 2 times then focusing. Not best solution and very slow, but works.[emoji3]
Screen recordings preferred that shows your issues. Too much guesswork.There is a video that i record. I hope it helps.
All is working over here. Just tested. Did you set Preview to framing? You find this under RAW video menu settings.
Hard to say what is going on but keep testing different settings. Maybe you find the answer eventually. I'm on 1.1.3 by the way.
Ah, yes. It will interfere with framing. Good catch. I should remove this module as it´s only needed for when looking for registry nad development.Or just leave it disable when installing. Enable when needed for troubleshoot and tests.
You can also work from atlassian source tree gui. In there you can see commits and doubleclick back in time…Thanks!
crop_rec_4k_mlv_snd_isogain_1x3_presetsNew uploads for the 5DIII:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
- Fixed a bug when recording 50/60fps
- Better handling mv720p mode 45/48 fps when going in and out of x10 zom mode
Wow! Is there a chance your anamorphic to be centered or it has nothing common with this?
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fbitbucket.org%2FDmytro_Kn%2Fml%2Fdownloads%2Fcine.jpg&hash=cf9f3216f308154ed09ae25e5906f028)
Hopefully fixed now. Please test anamorphic again.
1920 preset? I only changed for anamorphic mode. Did you push menu button and back? Fps set to 24 in canon menu?
then Shutter range to Full rangeThis was the problem!
- Set focus aid to OFF for * button and halfshutter working normal way
How are you running raw_diag module?
I think it's true then, I remember I just couldn't find any way to change bitdepth in the previous build.Strange. Should have been in the sub menu. Anyway. It´s in Movie tab menu now so can´t be missed in the latest version. Just make sure that it´s set to 14bitlossless in RAW video menu:
I will use the latest of course, I have always done so with magic lantern :)
Future, modular? I rearranged and modified to be able to just start the camera and get on using it. It's just another open source project.
I rearranged and modified to be able to just start the camera and get on using it. It's just another open source project.
Code is there so you can build your own tweaks if there's something you're missing but since you didn't even find the crop mode sub menu in the last build at least enjoy the oppurtunity to lower the bitdepths again ;).
It's not like the modules are gone. They are simply autoenabled. Is there a module you're missing?
mlv_lite \
mlv_play \
mlv_snd \
dual_iso \
silent \
lua \
crop_rec \
file_man \
ettr \You can add any additional module by simply putting it in the module folder on your card and it should appear the normal way.char *core_modules[] = {"mlv_lite", "crop_rec", "mlv_play", "mlv_snd", "sd_uhs", "lua", "file_man", "dual_iso", "silent"};And erase:char *core_modules[] = {};Or erase all code related to core_modules and it should be back to normal. Didn´t dig in to hard on this. It´s mostly Jip-Hops code parts in this case and works really well.By the way. You should port card spanning to mlv_lite ;)+1 :)
No idea really.
By the way. You should port card spanning to mlv_lite ;)
I would work in this branch directly. I see no reason no too.Yeah ok. I cloned crop_rec_4k_mlv_snd_isogain_1x3_presets, this is the main one right now?
I ported global draw off a while ago. Not as hard as card spanning though but as you say. Not impossible to understand but It's a bit over my head.I am not sure where to start really. I see in mlv_lite theres loads of "NO_THREAD_SAFETY_ANALYSIS" which is a tiny bit concerning. Currently trying to compare how both modules do writing, it seems to be making a little bit of sense, but there's no clear comments like "this line writes the frame", so it's a bit difficult.
Hm, keeping mlv rec is hard to justify. No lossless recording if I recall correctly? Only reason to hold on to it would be if both lossless and card spanning were working but ultimately if you manage to get it working on mlv_lite personally I would think it's the better way.
Yeah, mlv_lite is stripped for maximizing speed. Originally dmilligan started out building this module.
Also why does the code sometimes use '0' instead of NULL for pointers?
Could anyone who knows explain: why it is only called once for multiple slots? it only gets the pointer from the first slot as the ptr argument, yet somehow writes all of the slots to the card?
Regarding 'loads of "NO_THREAD_SAFETY_ANALYSIS"' - there are only two, that I could find, and that's because the static analysis (https://www.magiclantern.fm/forum/index.php?topic=18907) does not handle cli/sei correctly. I don't see this as a reason to be concerned - on the contrary. But I cannot guarantee 100% correctness either - maybe rewriting some parts of ML in Rust could help with that. No, I don't know Rust, besides trying to run Hello World some years ago, but it seems to be something worth learning.
Therefore, if a function is called from more than one task, it must be thread-safe.
About what things are executing - there are our own DryOS tasks, more or less straighforward to understand, and there are hooks placed at various locations in Canon firmware (usually in their DryOS tasks). The most interesting one here is the VSYNC hook, aka "EvfReadOutDone" on recent models (i.e. triggered once after capturing every single LiveView frame, in Canon's Evf/LiveView task, which runs with very high priority). That's where each frame is processed, and the next slot is chosen (ideally continuing the previous memory chunk, as it's a lot faster to write several megabytes at once).
However, what exactly happens within each LiveView frame was only recently understood (https://www.magiclantern.fm/forum/index.php?topic=19300.msg207723#msg207723), and only to a very limited extent.
But let's fix card spanning on mlv_lite first ;)
writing_queue_head = after_last_grouped;However, a hard lock up (when everything stops responding) generally means some kind of invalid hardware (MMIO) access, or DryOS memory overwritten, i.e. messed up badly enough that vanilla firmware can no longer continue. If some task ends up "simply" waiting at semaphore, that shouldn't bring down the entire machine.
For 32-bit integer assignments, on a single-core ARM CPU, semaphores should not be needed - afaik, this operation is atomic. That's probably not true on multi-core systems.
For very short critical sections, you may use cli/sei, but no other tasks will be able to run between those two. You should not call any DryOS API either (such as msleep), as these might enable the interrupts on their own.
/* Below cams not tested/supported atm. Try it by enabling sd_overclock_task(); */
if (is_camera("5D3", "1.1.3"))
{
/* sd_setup_mode:
* sdSendCommand: CMD%d Retry=... ->
* sd_configure_device(1) (called after a function without args) ->
* sd_setup_mode(dev) if dev is 1 or 2 ->
* logging hook is placed in the middle of sd_setup_mode_in (not at start)
*/
sd_setup_mode = 0xFF47B4C0; /* start of the function; not strictly needed on 5D3 */
sd_setup_mode_in = 0xFF47B4EC; /* after loading sd_mode in R0, before the switch */
sd_setup_mode_reg = 0; /* switch variable is in R0 */
sd_set_function = 0xFF6ADE34; /* sdSetFunction */
sd_enable_18V = 0xFF47B4B8; /* 5D3 only (Set 1.8V Signaling) */
SD_ReConfiguration = (void *) 0xFF6AFF1C;
/* sd_overclock_task(); */ }
if (is_camera("5D3", "1.2.3"))
{
sd_setup_mode = 0xFF484474;
sd_setup_mode_in = 0xFF4844A0;
sd_setup_mode_reg = 0;
sd_set_function = 0xFF6B8FD0;
sd_enable_18V = 0xFF48446C; /* 5D3 only (Set 1.8V Signaling) */
SD_ReConfiguration = (void *) 0xFF6BB0B8;
/* sd_overclock_task(); */ }
return 0;
}Enable the function with this:/* sd_overclock_task(); */to this: sd_overclock_task();char *core_modules[] = {"mlv_lite", "crop_rec", "mlv_play", "mlv_snd", "lua", "file_man", "dual_iso", "silent", "ettr"}; raw_set_preview_rect(skip_x, skip_y, res_x, res_y, 1);
raw_force_aspect_ratio(0, 0); */
- if (!get_halfshutter_pressed())
+ if (!get_halfshutter_pressed() || rec_trigger == 3)
{
autofocusing = 0;
long_halfshutter_press = 0;
Would love to try this build to help the community !Wait for Ilia3101 to compile and share or learn how to compile. Seems you have the right card to use so should be ok.
I have 5DM3 with:
SDHS I Sandisk 95 MB/s
CF lexar 160 MB/s 1066x
But which build to use ?
And what is the settings to try ?
(I have read last 5 pages but I'm not enought in it to fully understand...)
just move both of them to the same folder/card, then you will be able to open it with MLV App.
Makes each file look like it has loads of skipped frames.Ah, makes sense.
I will upload a build where the sd_uhs module does not auto load, maybe"Patch itself is not autoenabled. Problem is due to card itself. Don't patch and problem goes away. Reluctant to answer some users who neglect to share info in other posts but I don't want Ilia3101 to waste his time.
However I did get much improved record times even without sd_uhs.
/* no, its another chunk */
if(main_header.fileGuid != file_hdr.fileGuid)
{
bmp_printf(FONT_MED, 30, 190, "Error: GUID within the file chunks mismatch!");
beep();
msleep(2000);
return;
}
Have new card now: Sandisk Extreme Pro SDXC UHS-I 64gb (170MB/s read, 90MB/s write)
Compiled latest updates. Card-spanning and SD overclocking working well now:
I can get 1min+ 3600 x 1532 / 24fps / 2.35:1, continuous at 3072p. 1080p 14bit on SD card alone – continuous! :)
Many thanks @ilia3101, @Danne.
sudo newfs_exfat -b 4194304 -v NameThePartition /dev/disk3s3@Stousen Yes!
In 1080p = Real Time.
In Crop modes = Framing.
I managed to get it to work, i get avout 110-115 in w/speed!It's hard to see what you expect or even if there is a problem involved. To minimize communication mishaps you need to be specific with settings used, preferrably with screenshots or a screenrecording. Use contextual terminology instead of making up new words etc.
Tho my live view doesnt work while recording in crop 3k? :(
It's hard to see what you expect or even if there is a problem involved. To minimize communication mishaps you need to be specific with settings used, preferrably with screenshots or a screenrecording. Use contextual terminology instead of making up new words etc.
You need a better bike 8)
Previewing capabilities will not change with different cards. Framing...
I've tried Dmytro_ua's Fast video presets, updated for Danne's build 16th of Jan - https://drive.google.com/open?id=18-Wo0yNVBCVwfjyTlB7O7UK5bMPUtsCd, but there is no this lua in Scripts menu. ?
It seems to me that menus structures in builds of 16th Jan and 25th Jan are the same. My lua script works fine in 16th Jan build, but there is no this lua in Scripts menu in 25th Jan build. All builds are Danne's build.Post screenshots or try describe more in detail what you arw missing. I use lua all the time and it´s still included as a module but who knows what you´re asking here. Maybe try and do a screenrecording?
Post screenshots or try describe more in detail what you arw missing.When I open "Scripts" menu in ML build 16 Jan I see my lua and can run it. But when I open "Scripts" menu in ML build 25 Jan, I can not see the same lua in menu.
Try shorten the name of the script that is showing in menu.Yes! Thank you. If SD card FAT32 formated - no problem with long file name. If exFAT only 8 length works.
Worked last time I tried.It works for me only for ML menu.
Turn off RAW video while doing screenshots. I did some automation to temporarily disable RAW video when using screenshot function but maybe it fails under certain conditions.Yes, it works. Thank you.
Is it just cutting the top 3/4 of values off?Values of what?
How did it die?
I use transcend. Never failed.
I use Lexar. Maybe it's not a top speed but a solid proof for many years
What is the highest resolution that 16/9 can be recorded continuously for 12/14 bit?
Unfortunately, I had to pay a price for my impatience. My beloved SD card died in these experiments. Here is how this happened:
III. I decided to check the SD-overclocking feature alone. I removed the CF card and left only the SD card with ML on it in the camera. Then I activated SD-overclocking, waited until it is patched, (status ON) and pushed recording. Recording did not work, I got the error message. Then I decided to format the SD card in the camera without turning SD-overclocking off. Formatting failed and I was prompted to replace the card. That was it. All further attempts to fix the card through formatting in the camera and PC via card reader failed. The card is dead. Not a big loss but still ... After that, I did not try other SD cards.
There is a 3K preset that does 3072x1920, so you can record 16:9 in 3072x1728 (it's continuous I think)
If 3072x1920 is truly possible for 12/14 bit with 5.9 MP -- could 3264x1836 be supported?
That would be even better, pushing the max for 16/9.
3072*1920=5,898,240
3264*1836=5,992,704
3232*1818=5,875,776
3200*1800=5,760,000
@Boobie Just tested 12 bit 3072x1728 - it's continuous with card spanning, but just on the edge. If your shot suddenly becomes overexposed, recording indicator goes orange and it will be at risk of stopping.
I'm uncertain if MLRAW is RGB 36 bits or RGGB 48 bits pre-compression, would love to learn more.MLRAW is 10/12/14 bit. RAW is B/W (one channel). Color comes with debayering.
MLRAW is 10/12/14 bit. RAW is B/W (one channel). Color comes with debayering.
Removed sd_uhs module. Too fishy. Not worth it.
Getting quite certain it's reliable now.
Bug report: when recording uncompressed 12/10 bit, the white level metadata is always set to 16200 (that value is only suitable for 14 bit)That is a problem also with official experimental builds?
if (!bitdepth) raw_hdr.raw_info.white_level = 16200Do somebody know this problem ? Do I do something wrong ?
I have tried this version : crop_rec_4k_mlv_snd_isogain_1x3_presets_2020Feb01.5D3113
The mlv files can't be open in any software (Photoshop, Ae, MLVFS, MLV to CDNG on the fly). Only MLVproducer
Seems that there is no true 12/10 bit compressed recording? It's all gain based?Told you already ;)
I recorded in "12 bit lossless" data format, and white level was at 6000 or something. Not below 4096 like I expected. And black was 2047 just like 14 bit (would be 512 in true 12 bit)
So there is no difference between using crop_rec bitdepth and mlv_lite data fromat lossless options?
Told you already ;)
But what is true 10/12-bit according to you?
Hopefully it will be useful with some workaround as I pretty much have no time to dig into the code atm.
Hello, I would like to know if you have to install the ML firmware on the 2 sd and cf cards at the same time, to record with both simultaneously
how the expansion sd works and what limitations this type of recording has on 5d3 in short.
Nothing new for the 700D so no need for updating.
static struct menu_entry cfg_menusmovie[] =
{
{
.name = "Custom modes",
.priv = &config_new_preset_index,
.min = 0,
.max = 6,
.choices = (const char **) config_preset_choices,
.select = config_preset_toggle,
.update = config_preset_update,
.help = "Choose a configuration preset and start customize(restart needed)."
},
};static struct menu_entry cfg_menusmovie[] =
{
{
.name = "Custom modes",
.priv = &config_new_preset_index,
.min = 0,
.max = 14,
.choices = (const char **) config_preset_choices,
.select = config_preset_toggle,
.update = config_preset_update,
.help = "Choose a configuration preset and start customize(restart needed)."
},
};I think you get the picture. char config_file[0x80];
snprintf(config_file, sizeof(config_file), "%sfirst", get_config_dir());
int first_run = config_flag_file_setting_load(config_file);to this in module.c, seems to fix it: char config_file[0x80];
snprintf(config_file, sizeof(config_file), "ML/SETTINGS/FIRST", get_config_dir());
int first_run = config_flag_file_setting_load(config_file);Need to test it some more.
Not sure why not 12, but only 11 of my 12 characters names are showing.
here's a message to let everyone know that sd overclocking is still alive and well for the 5d3!
i just filmed a new zen episode at 3.5k under extremely challenging outdoor full sun and windy conditions with no stops for over 15 minutes
also 14 bit lossless. no luck at reduced bit depths for me. never looks right... it would be nice to see development of bit reduction within theIt will never look 14bit, that´s for sure. please upload comparison examples and explain why what you see is not true reduced bitdepths.mlv_litecrop_rec module (brain fart!). i think it would look better :)
Interesting. That might be fixable.Just realised I should try a dark frame. But I'm not too hopeful, doesn't really look like FPN (no purple/green tinting).
I use some generic way to reduce bitdepth but it could be tweaked if not your sensor is having this problem. When I have some time over I´ll test to reproduce the issue.Would be very interesting to see if other cameras have this issue.
The result is the same I think reducing analog gain vs digitally reduced or whatever we choose to call it. At least I´d like to see proof there´s any difference.
So far I haven´t heard of anyone understanding fully how it´s done, except for a1ex of course.Would love to know more :)
If test please report if working or not. I leave absolutely now guarantees. If card gets corrupted or worse you´ve been warned.
With that said it works for me and for @70MM13 but who knows what random users comes up with here.
Good luck.
ML ASSERT:
0
at mlv_lite.c:2724 (compress_task), task compress_task
lv:1 mode:3
compress_task stack: 1ae938 [1ae9c8-1ad9c8]
0x0006A01C @ b8303c:1ae968
0x00069878 @ 6a084:1ae938
Magic Lantern version : Nightly.2020May29.5D3113
Mercurial changeset : 6b5fa5a301dd (crop_rec_4k_mlv_snd_isogain_1x3_presets) tip
Built on 2020-05-29 13:38:20 UTC by danne@danands-MBP.
Free Memory : 210K + 2384K
... and 1 is totally broken -> MLV App crashes when opened, export with MLVFS give me some crazy colored stars on white background.is that clip large? Any possibility to upload it for analysis?
https://drive.google.com/drive/folders/1HGOqDNpQvqxeLzXa0f5Zbfzh8bbzl-GH?usp=sharingWait... you recorded with card spanning and got no .M00? That should mean some data is missing. Your file's metadata tells about existing audio channels but no audio data is existing. This was why MLVApp chrashes. I implemented another check which doesn't just trust the metadata... :D If you are able to compile, you can try the fix.
wait 10min for uploading.
I think the Problem is, there is no .M00 file. only a MRX file.
Nice footage. 5k anamorphic is undisputable the most efficient preset of them all if filming 24 or 25fps. What lens was used?
With card spanning on, in UHD mode, write speed is around 120mbs (80 mbs CF +40 mbs SD)
File size / recording duration?
As in "MByte/s"...
As long as these builds contain mislabeled ISO settings, I am not going to support them, sorry.Is it planned to return this build back to Experiments (https://builds.magiclantern.fm/experiments.html) page?
static struct menu_entry ratios_menu[] =
{
{
.name = "Ratio",
.priv = &ratios,
.max = 6,
.choices = CHOICES("OFF", "2.39:1", "2.35:1", "2.2:1", "2:1","1.85:1","16:9"),
.help = "Access six global ratios",
.help2 = "only anamorphic preset\n"
},
};
if (ratios == 1) menu_set_str_value_from_script("RAW video", "Aspect ratio", "2.39:1", 5);
if (ratios == 2) menu_set_str_value_from_script("RAW video", "Aspect ratio", "2.35:1", 6);
if (ratios == 3) menu_set_str_value_from_script("RAW video", "Aspect ratio", "2.2:1", 7);
if (ratios == 4) menu_set_str_value_from_script("RAW video", "Aspect ratio", "2:1", 8);
if (ratios == 5) menu_set_str_value_from_script("RAW video", "Aspect ratio", "1.85:1", 9);
if (ratios == 6) menu_set_str_value_from_script("RAW video", "Aspect ratio", "16:9", 10); if (CROP_PRESET_MENU == CROP_PRESET_1x3)
{
if (ratios == 0x1)
{
snprintf(buffer, sizeof(buffer), "anamorph 2.39:1");
}
if (ratios == 0x2)
{
snprintf(buffer, sizeof(buffer), "anamorph 2.35:1");
}
if (ratios == 0x3)
{
snprintf(buffer, sizeof(buffer), "anamorph 2.2:1");
}
if (ratios == 0x4)
{
snprintf(buffer, sizeof(buffer), "anamorph 2:1");
}
if (ratios == 0x5)
{
snprintf(buffer, sizeof(buffer), "anamorph 1.85:1");
}
if (ratios == 0x6)
{
snprintf(buffer, sizeof(buffer), "anamorph 16:9");
}
if (ratios == 0x0)
{
snprintf(buffer, sizeof(buffer), "anamorphic");
}
} case CROP_PRESET_1x3:
if (ratios == 0x1)
{
skip_left = 206;
skip_right = 62;
skip_top = 60;
skip_bottom = 30;
}
if (ratios == 0x1 && set_25fps == 0x1)
{
skip_left = 248;
skip_right = 110;
skip_top = 60;
skip_bottom = 42;
}
if (ratios == 0x2)
{
skip_left = 206;
skip_right = 62;
skip_top = 60;
}
if (ratios == 0x2 && set_25fps == 0x1)
{
skip_left = 248;
skip_right = 110;
skip_top = 60;
}
if (ratios == 0x3)
{
skip_left = 268;
skip_right = 124;
skip_top = 60;
}
if (ratios == 0x3 && set_25fps == 0x1)
{
skip_left = 360;
skip_right = 118;
skip_top = 60;
}
if (ratios == 0x4)
{
skip_left = 340;
skip_right = 196;
skip_top = 60;
}
if (ratios == 0x4 && set_25fps == 0x1)
{
skip_left = 432;
skip_right = 190;
skip_top = 60;
}
if (ratios == 0x5)
{
skip_left = 402;
skip_right = 258;
skip_top = 60;
}
if (ratios == 0x5 && set_25fps == 0x1)
{
skip_left = 488;
skip_right = 246;
skip_top = 60;
}
if (ratios == 0x6)
{
skip_left = 426;
skip_right = 282;
skip_top = 60;
}
if (ratios == 0x6 && set_25fps == 0x1)
{
skip_left = 512;
skip_right = 270;
skip_top = 60;
}
break; Hi all,
If anyone is interested I put together some intermediate presets for 2.20:1, 2:1, and 1.85.1. I was looking for something a little in the middle of the 16:9's crop and the 2.35 aspect ratio. All are continuous on a 1000x KombuterBay without spanning or anything.
I will try to put it up on bitbucket, but have to get my head back around that process again. I don't use it enough to be comfortable or even remember the basics, and might not have time to work through it this weekend.
All changes in crop_rec.c from Danne's crop_rec_4k_mlv_snd_isogain_1x3_presets branch. Thank's Danne for your work. It was super easy to build on.
Regards,
Eric
Amazing ! how can we download it as a autoexec "classic ML file" ? (I know nothing about coding, I'm more into video..)
Is it possible to make a 2x2 Preset like 2880x1620 (16:9) or better a 1x2 Preset like 2880x1920 (2.5:1) = 5760x1920, or is this still impossible?Have a look on the bayer matrix. 2x2 is only possible theoretically for b/w, because you loose the color information.
I am not a programmer and unfortunately I already thought that it would not work...This has nothing to do with programming, but with how a sensor is build. You have a RGGB layout on it. And if you just read 2x2 and start at R, you get only R pixels.
All modules are autoloaded except for bench.mo. I also plan on adding adtg_gui.mo as an optional module.
Do note that my builds comes from a fork from another experimental build. This is actually experimental on top of another experimental build.
Nice. Will check it out when I have the chance.
Ongoing code atm:
https://bitbucket.org/Dannephoto/magic-lantern_dannephoto_git/src/master/
I piggy back on a git account but still include hg commits working with my compiler tool:
https://bitbucket.org/Dannephoto/ml_compiler-git/src/master/
After commits I push all hg and code changes to the git account. It's all temporary. Bitbucket are deleting all mercurial sources. Bad move on their part.
I am noticing differing (but consistent) speeds using different presets...https://www.magiclantern.fm/forum/index.php?topic=12862.msg228848#msg228848
Edit: also it looks to me like the recording rate estimation is using 14bit raw recording in it's calculation, even though the files are in 12bit, giving a larger estimate than actual. Is this true?Yes, it shows 14bit lossless - > set in drop down menu. This is because the settings for 12,10bit... Is just a tweaking from 14bit lossless. You can check the white and blacklevel in MLVapp.
Global draw needs extra resources, so it slow down the maximum writespeed.
maximum speed with Cardspanning and overclocking for now is BTW. 131MB/s (Nobody knows why).
@Grognard
Not really , the showing writespeed is incorrect in other modes. See this test:
https://www.magiclantern.fm/forum/index.php?topic=12862.msg228848#msg228848
I was expecting the card 95mbps Sandisk Extreme Pro 32gb to work with latest sd uhs patch.
Could you tell me what ml version you are using? Full name or link to exact build?
@has_abandonment_issu
This is a knowing issue. Try low level format in Camera (SD card) and have fun ;)
I am not sure what is going on here and don't have my camera here but if it's not working giving card full etc it's better to stay off the patch on this particular card. I expect this patch to either work fully or not at all, no in betweena.
Not sure what coredump is caused for in this case but just stay off patch on that card.
Please remember. It is bleeding edge. I tried to prevent serious errors but nothing is finished.
Not in dropbdown menu. I mean the 10 or 12bit lossless (14bit lossless tweaking). Do you need a small video with this error?Not sure where you select from. The bitdepth options from Crop mode sub menu should work.
I see that there's a lot going on here with the writespeed calculations.
You also asked what happens when I try to use SD overclocking. I am using a 95mbps Sandisk Extreme Pro 32gb SDHC card. I have a 128gb 170 coming in the mail on Monday.
Would be a first here: UHS-II card in overclocked UHS-I compatibility mode.You´,ve been successful? But not on a 5DIII right? What card exactly?
I set kill global draw and I tested as well with standard settings. I change ratio because of the error, so no difference. I tested 2.39:1 at 10bit - at the last resolution (2848) it works, but with 3072 not. The same without SD overclocking and the same without audio and the same without fine tuning. This all is only happens in 3K mode with Cardspanning.I can´t reproduce this issue. Recorded longer taes with sd overclock on 24 fps 3072 resolution 10bit. Works ok here.
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.
What are your exact settings for the 5d Mark iii? I have the 128gb A2 v30 170
Hi Danne, thank very much for your build. It's amazing !
Today I installed your latest from today I guess. I have the 5D3 with 1.2.3.
I work with the 5.7K Anamorphic but I have some issues with the global draw I think. When I record with the global draw my "speed record" is always in the orange and after 30-40seconds the record stop automatically. If I disable the global draw everything works and my speed record is green and around 90Mb/s, and I can record without limits.
I record only on my CF Card Sandisk Extreme Pro 160Mb/s. Do you have an idea if it's possible to fix this ?
Thank you
default settings (fresh install, or fresh ML files/ without config) + cardspanning + without SD overclocking + 10/12 bit.-> working and with 10bit continuous with live view or 12 bit without.
-> The frustrating things is: this is only happens in 3K mode. In all other modes, i can use SD overclocking and Overlays.
I am sorry. Not clear to me. You install my build, enable sd overclock and start to record? Nothing extra enabled, zebras, histogram etc? Could be your cf card if so. I use a transcend cf card and from my tests I couldn´t get your issue.
@Volunters
Interestingly, there is no pop out console while recording?
which firmware do you use?
I use 113 and can rec. up to 125mb/s with liveview and 131mb/s without (UHD mode).
In my case it never stops recording, but I see multiple compression error on frame *
Easily you can close your lens cap for less writespeed, but if you don't see the console message it will not really work.
but maybe you can enable console in ML menu under scripts.
Bender@arsch I get a similar error when recording higher framerates (either 1920 @ 60fps or 1050 @ 48fps) while using card spanning. I am currently using a 95mbp/s sandisk 32gb card. I haven't tested the error aggressively so I'm not sure if it conflicts with other settings.
You can try "Switch". Uses a1ex updated cr2hdr code.
New builds:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
- Expanded 3.5K 1:1 centered x5 preset height to 3584x1730
Why this. Now we get cropped real time preview and framing instead of only framing preview when using 3K 1:1 preset for instance.
For 24fps you can use full 3584x1730 but for 25fps I had to reduce height to 3584x1660.
Needs some testing. Now we can get 16:9 3152x1730 with cropped realtime preview. Nice.
Hello Danne.
Thanks for the build. I'm on firmware 1.13 and with your latest build I have a flashing liveview, alternating from parts of what is in sight with strange colors to full colored pixel view (like a TV without a channel).
Whatever the mode set it's not working and generating corrupted messages and asserts logs if I try to record.
I've tried numerous settings (spanning on/off, various résolutions/bitdepth), no one working.
@70mm what firm are you using ? 1.13 ? Have you wiped the SD before putting the new build ?
I got some strange crashes when I tried to record without having x5 on (using 3k 1/1)Please make a screen recording if you can´t nail down the issue or reproduce it exactly.
Hi Danne,
Just tried 1.13 build for 3.3K realtime preview test. It works just like before for me. Laggy preview. Am I missing something?
Screen record :
https://drive.google.com/file/d/1B_ScednT0ms1jKB_DBjILxOEhfwAnyTG/view?usp=sharing
Just tried 1.13 build for 3.3K realtime preview test. It works just like before for me. Laggy preview. Am I missing something?
I see. I think I need to shave down a few more pixels then. Let me test some.
EDIT. What resolution are you using?
Have you tried global draw off?
@Danne
I have the same problem as has_abandonment_issu in 3.3K.
But 3.5 works very well.
nice work!
Whatever makes the camera freeze. Don't do it.
I also got my not yet released application "Switch mini" working with spanned files.Sounds like a really cool transcoding app, well done! Ive been busy recently, but with free time now I'll test out the new M Build out, see how it goes. I know it's a work in progress, but honestly, it's a miracle where the camera is right now. Cheers for all the work! 🔥🎥👍
Got word from has_abandonment_issues about 3.3k preset working with this version. Missed uploading yesterday:
New builds:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
Got word from has_abandonment_issues about 3.3k preset working with this version. Missed uploading yesterday:
New builds:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
UHD 2.39 is "only" 6.170 880 pixels (3840x1607) less than in this case : 6.200 320 pixels (3584x1730)
I don't know what you're trying to say, but the important thing is the increased writespeed. And the latest build can only 3840x1536 (continuous recording too).
-> we got never more than 131mb/s
Ok, i double check it:Those are nice numbers. I am pretty sure it´s because of being in x5 zoom.
I search a good spot (bright and flat spot, without dark areas) and show in ML Menu under Raw -> 14Bit writespeed preview say 208,5mb/s or so
Here the Result:
3.5K 3584x1730 23,976fps 10bit
CF: 81,9
SD: 55,6
=137,5MB/s
-> 8424 (cf 5029, sd 3394), 1469 frames =~61sec
8424/61 =138mb/s !!!
This is a new record!!!
p.s. the indicator was orange and i stoped manuel;)
I haven't experimented with the quality 10bit produces, but I am going to test that next since 10bit seems to be continuous in almost all exposure scenarios.
resolve does 18fps timelines so that would be a great choice! i use it sometimes instead of 23.976 and it is really nice.
How do you think we could help you out? Impossible mission. At least throw in a sample mlv.
How do you think we could help you out? Impossible mission. At least throw in a sample mlv.
https://drive.google.com/file/d/1Z2hTLI5ETIbpyMDaOL3iWy8F9Eeeph9_/view?usp=sharing
Seems like an issue on your end. It looks pretty good to me. The fluorescent lights are clipped, but everything else looks great. If it's yellow, maybe you have Night Shift on your display? ;)
MLV App:
Exposure -1.5
Temp/Tint 3740/41 (selected white area of wall that wasn't blown out)
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FzVBFpfJ%2FM23-1636-frame-1.jpg&hash=7ca0622dbe9f88fbad4c2f32a706fbd3) (https://ibb.co/qYcCK15)
sd CARD will not go over 20M/s
Just bought a new one
none of them will go over 20mb/s
how do you guys do that ?
pepole talking about 60MB/s and saying bad one would reach 35mb
but I have 7 san disk ranging from 95/mg to 170/m
some from amazon
and a brand new one from 10 min ago from local store
20MB/s
please some one tell me what is wrong
Yes, unfortunately the 170Mb/s card seems the only stable one for these regs.
I am sorry I don't have more time to spend here. Maybe there could be another patch working better here, probably is, but I am not the one that could help here atm.
Hey Danne!Download mlvapp for windows
I'm a big fan of your work and currently using your latest build.
I don't have a mac so I couldn't use your "switch mini" app to stich my spanned file.
Could you please make a window version so all of us window user can also try out this feature?
Thank you so much!
hello guys im using danne build september with firmware 123 on 5D3 and my setting is 3K 1:1 12 Bit 24FPS
i can not get real time clean screen on my camera
this my all setting and what i get on my camera screen and same on external monitor HDMI connected
https://ibb.co/NNbZJ3b
https://ibb.co/8skHZXG
https://ibb.co/ZSbyYwL
https://ibb.co/tB8v45K
https://ibb.co/gDnQkhH
I think he is talking about the vertical black stripes
I never got an answer to my question on the real time preview for this build, so i took a quick video to make sure what im talking about is clear, for the 1080p raw that is what i would call real time, its full color and full speed, when switching into the 3.3k preset the preview is desaturated and extremely choppy. It sounded like people had the 3.3k preset running like the 1080p preview with proper framing, am I missing something or is this how its supposed to look?
working 1080p more than 37fps mode with working preview would be awesome enough to buy one again.
@Danne: what is the current best mode available to shoot in 1080p with 5Dm3? Does the unsqueezed 48p with compression still have a gray or choppy preview? Thank you
PS: I no longer have 5D to test myself, but working 1080p more than 37fps mode with working preview would be awesome enough to buy one again.
1050p 48fps
Full working preview ;)
Nothing changed. It´s still stretched preview. We need to be realistic here. It still works very well and is totally usable for me and most users. If you can´t work with the shortcomings please do not rebuy the 5D3.
1920x2160
15 august and 13 sept. both for 1.1.3
https://we.tl/t-Mc6onjR8Zu
but the recent one is more stable you know, less bugs.
You could also desctibe your issues here. What preset used causing those issues and even upload your SETTINGS folder for us to reproduce.
New builds:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
- Centered 3.5k preset.
Needs some testing...
Well, better at least. Don´t think I can get it closer to center.Only I, just for testing and comparing. And yes, it's much better at least.
Who said anything about 3.3k?
Thanks for testing.
New builds again:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899
Centered both 3.5k and 3.3k a little better I think. Please test.
Hello,
I'm having an issue with the HDMI monitor connection with the latest build Nov 26, 2020. Using a DJI Ronin RS2 Pro gimbal with camera control cable and Raveneye for wireless HDMI monitor.
1. If I just connect camera control cable ML will freeze when pressing record button on gimbal. But, if I use the start/stop button on the camera it records fine and can use anamorphic modes without issue.
2. If I add HDMI cable for external monitor (Raveneye with RS2 Pro), I can monitor the output from the camera live!
3. (This is the main issue) If I add HDMI cable for external monitor in #2 and press the start/stop to begin recording the camera freezes and needs a battery drop.
Attempting with:
1. Anamorphic
2. 16:9
3. 12 or 14 Bit
4. card spanning: on (256GB Extreme Pro CF and SD cards), ML on CF.
Is there a certain settings combo to get HDMI to work with anamorphic modes? The issue appears to be with ML and not the RS2 as the feed works fine while not recording and when recording begins the 5DMIII chokes.
Much Appreciated!
I'm not sure, but I see no difference in 3.5K. 3.3K is nearly perfect, but I get some crazy vertical lines/ stripes in all previews.
Hm, I´ll have a look. Does it affect recorded file too?
EDIT:I don´t think what you are referring too regarding stripes is related to recent changes. This has been there for long. As long as recordings are fine all is working as before and expected.
Yes. But this issue is only in 3.3K.
Yes, it´s because of modifying width to be able and preview cropped and in realtime. Still good.
Hello, I would like to comment that the sd_uhs module works well in 160 mhz and only with 240 mhz it has problems of sound loss after 3 minutes with 20, with sandisk extreme pro 170 MB / s 128 GB card, formatting the sd card or deleting the files on the computer has no danger, and the increase in speed recording with both cards at the same time is appreciated when recording with looser parameters and much longer.Hello, what Canon`s model are you talking about? There is no possibility to set 240 mhz for 5D3.
Thank you very much Danne and company for your meritorious work.
There is no possibility to set 240 mhz for 5D3.
https://www.magiclantern.fm/forum/index.php?topic=23041.msg229639#msg229639I mean last Danne`s 17Dec2020 build.
I gave up on 240Mhz setting. I recommend any old builds with this patch still there not to use it. Too many issues.What about 192mhz оn 5D3?
The mlv file is opening fine in MLV App, but as soon as I transcode in .dng, the files become unreadable.
Do I simply copy and replace the ML folder and autoexec.bin currently on my SD card with the ones provided in this build?
I recommend you uninstall any older builds to start clean. Then install next build fresh.
I do, and I use a Freewell monitor, everything above 1080p will give you a real time cropped x5 preview, 5K will appear flattened.
aah, now I understand the principle that in the old post 23may2019 the builds are refreshedYup, correct.
:)
/* raw buffer centered in zoom mode */
case CROP_PRESET_CENTER_Z:
cmos_new[1] = PACK12(11,61); /* vertical (first|last) */
cmos_new[2] = 0x09E; /* horizontal offset (mask 0xFF0) */
break;This: cmos_new[1] = PACK12(11,61); /* vertical (first|last) */into: cmos_new[1] = PACK12(9,12); /* vertical (first|last) */Is that setting valid for 3584x1730 or is that for lowered resolution? What about the original cmos 1 when in 3584x1730?
Hello, I wanted to inform that with the version 01-30-21 for 5d3 in full anamorphic it generates a multitude of corrupt black squares.Yes, you can keep them all for free.
Thank you.
Hello, could you explain what the parameters are, for the x5 mode centered 1: 1 from 3.5k to 3456x1728 10bit, I can't use it. Thank you.
Could you upload one recording with missing audio? There are more than one way to develop footage that could solve this. Most likely audio is still there.
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 17047428700475394385
FPS : 23.976000
File : 0 / 0
Frames Video: 132
Frames Audio: 0
Class Video : 0x00000021
Class Audio : 0x00000001Checking metadata:Code: [Select]File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 17047428700475394385
FPS : 23.976000
File : 0 / 0
Frames Video: 132
Frames Audio: 0
Class Video : 0x00000021
Class Audio : 0x00000001
Frames Audio: 0 so I guess something would not allow wav file to be recorded. Is this reproducable? Only happening in 3.5k mode?
Oki. From what you describe it seems related to card spanning. If possible do more tests without card spanning.
What about the 8k on YouTube?Why you want upscale this? In my tests I upload a 5.7K video and I can set to 5K in the web browser and if I click right click on statistics, you can read this is 5.7K ;)
The only reason is with footage less than 4K, but not for quality of the footage, just only for Youtube - > YouTube HD quality is really bad.
| ID | Description | Horizontal resolution* | H/V ratio | Binning | FOV@16mm | FOV@35mm | APS-C safe** | Frame rate | Data rate | Cont.Rec. | Preview | Other notes |
| 3X | 1920 1:1 | 1.9K (HD) | 2.39 | 1x1 | 41° | 19° | Yes | 25 | 48 MB/s | Yes | colors, slightly low h/v ratio?, hi fps | Perfectly centered? |
| anamorph_ fullres | anamorphic fullres | 1.9K stretched to 5.6K | 2.39 | 1x3 | 97° | 54° | No | 15 | 69 MB/s | Yes | colors, correct framing, low fps | Covers 100% of sensor width. Centering not investigated. |
| 4K_HFPS | 4K 1:1 half-fps | 4K | 2.39 | 1x1 | 77° | 40° | Almost | 12.5 | 72 MB/s | Yes | colors, correct framing, low fps | A bit below center. Unusable: produces pink / magenta / corrupted frames. |
| 1x3 | anamorphic | 1.8K stretched to 5.3K | 2.39 | 1x3 | 93° | 52° | No | 24/1.001 | 120 MB/s | Yes | grey scale, correct framing, low fps | Covers 94% of sensor width. Just slightly below center? |
| 3K | 3K 1:1 | 3K | 2.39 | 1x1 | 62° | 31° | Yes | 25 | 125 MB/s | Yes | colors, correct framing, low fps. | A bit above center and slightly on the left? |
| 33K | 3.3K 1:1 x5 | 3.2K | 2.39 | 1x1 | 65° | 33° | Yes | 24/1.001 | 129 MB/s | Yes | colors, correct framing, low fps | A bit below center and slightly on the right? |
| CENTER_Z | 3.5K 1:1 centered x5 | 3.5K | 2.39 | 1x1 | 70° | 35° | Yes | 25 | 179 MB/s | No | colors, correct framing, low fps | Slightly above center? Continuous recording @10 bit (in some circumstances even 12) or disabling Global Draw + 12 bit (in this case preview will be standard x5, so cropped). |
| UHD | UHD 1:1 | 3.8K | 2.61 | 1x1 | 74° | 38° | Almost | 25 | 183 MB/s | No | colors, correct framing, low fps | Perfectly centered? Continuous recording @10 bit (apart from extreme circumstances maybe?), or in some circumstances 12 bit but disabling Global Draw (no preview at all!) |
- Aspect Ratio [...]
- continously recording: for better Result you can decrease bitdepth [...]
- SD overclocking works only with SD Card