Messages

Old method applies: Take a vid, take a pic and check EXIF.
Or ask MPU via UART.

Not a big deal. Can do this.

Put your issue there: https://www.magiclantern.fm/forum/index.php?topic=23041.1200

1: Snapshot, please!
EDIT: Confirmed. Moment ... will look it up
EDITEDIT: Funny. Function is there in lua_fix build. This one goes to Danne, I suppose.

2: ML can only be loaded once ... ;-) Having it on both cards doesn't hurt.

Redo the same test with Dianne"s build.
Just rename current dir and autoxec.bin and reinstate Danny's files.

If issue is reproducable -> Bug report to Dianne.

Rename ML directory, rename autoexec.bin.
Copy extracted lua_fix buld content to card.
Overwrite ML-SETUP.FIR or not. They are identical.

https://builds.magiclantern.fm/experiments.html

May I ask you to reproduce issue with lua_fix build?

Not much traffic here. Most short-term interaction and smalltalk happens on discord.

I'm not sure if my information is correct but UDMA-7 may come with a lower voltage. No CF 6.0 spec available here, though.
Maybe ted ramasola can help. He seems to be (or was) on good terms with Komputerbay.

EDIT: Found a piece of contradicting info claiming UDMA-5, 6, 7 all using 3v3.

Doesn't have to be fake to fallback to 20 MByte/s.
I have a very, very fast card specified for 130 MByte/s write. In compatible cardreaders this one can reach 156 MByte/s.
No luck in any Canon cam when overclocking is active. 20 MByte/s with oc, around 40 without.

We have no reliable reports for Extreme Pro 95 MB/s with latest sd_uhs.mo.

I think I found your Insta. Not sure how to improve that by using ML! Kudos!

Most short-term talk takes place in our discord.

It is all about bandwidth.If required bandwidth exceeds write performance recording will stop because of buffer overflow.

- Without SD overclocking SDcard will do just about 20 MByte/s
- With overclocking and compatible SDcard and proper settings you should get 90+ MByte/s in benchmark and around 80 MByte/s in recording.
- Using both card slots and fast cards cam is able to do 145 MByte/s continuously. This seems to be a hardware limit.

Now do the math.

Required bandwidth (in Byte/s) = horizontal pixel x vertical pixels x frame rate x bit depth x compression factor / 8
Compression factor is not a constant and varies with scene/exposure. For very rough calculation use 0.5.

BTW: Sandisk Extreme Pro 200 MByte/s comes in different varieties.
256 GB and up: R200/W140
64 and 128 GB: R200/W90

Lower capacity comes with slighty less performance when overclocked.

imgur:

Code Select Expand


[IMG]https://i.imgur.com/jk0w9OG.png[/IMG]


imgbb:

Code Select Expand


[IMG]https://i.ibb.co/5cRN8gR/2024-02-04-15-41-49-new-6-Notepad.png[/IMG]


Good to have you back on tracks. Can't help with your dev environment issue. The only thing I know (IIRC) Ubuntu is not the prefered dev platform (to put it into friendly words).

That all for now , i hope all development continues on the forum for everyone to see publicly , i don't like when the ML discussion is behind closed doors
that one of the reason i stop doing any development , even thou the development is on D6 ,7 & 8 it still helps me a lot discover thing on the D4 cams.

Not getting the "closed door" bit. Most of dev talk today takes place on our Discord server. Only essential findings will get documented in forum which serves as some kind of "long term memory". I think apart from Danne all current devs and contributors are present over there. You will find a discord invite on top of this page: https://discord.gg/uaY8akC

There is a restricted area but it is for administration.

Dang!
You are right and 600D is missing this feature!
See https://builds.magiclantern.fm/features.html -> Expo -> ExpSim
There are only two cams *not* supported.

Sorry!

Do the math. Bilal lists crop factors for his presets. And according to wiki 16 mm is 10.26 mm × 7.49 mm.
Don't own that lens and all I can say about lens' optical performance is just image circle.

I am planning to use an M42 to EOS-M shift adapter, but Kiev-16 seems to have a bayonet mount of M35x0.5, maybe it can be mounted with a M42 to M39 adapter?

?
How should that fit?

Are you sure about 35x0.5 thread? I found two mounts for 16u: 35.5x0.5 and 33 mm.

Check mounts or - if any - lens specs for image circle diameter.
Use focus calculator of your choice to calculate DOF.

Nightly is in fact outdated. I recommend to use lua_fix instead. See https://builds.magiclantern.fm/experiments.html
If you only want it for this feature it doesn't make a difference, though.
Lua_fix contains 30-minute timer override for liveview which comes handy for cams running unattended.

Exposure Simulation is found in Expo tab/screen -> ExpSim ON/OFF
See https://wiki.magiclantern.fm/camera_help#expsim for short explanation and other stuff.

This setting is among the very few stored in cam. Means: Set it OFF and it stays off, even without ML running/installed.

Cause this is not what maths says and its clearly below 2.5k detail which concludes that i was right about the actual detail.

It is exactly what maths says. And pointed out several times. Please try to understand.

Which formula?

Please check wiki entry: K means 2021 edition. 2023 has S suffix. Date in third culumn doesn't refer to production or purchase.
A (or other suffixes like EU, US) refer to market region and should be ommited in this column.

Maybe I have to point it out a third time:
Procedure described above is only helping for macOS + ExFAT.

Your problem is a different one.
Make sure to have this file structure inside your card and proceed with installation:
Click here

You can also start EOScard Utility (as admin), select your card, mark boxes for EOS_DEVELOP and BOOTDISK. Then press Save button.
Card is bootable now. Insert card and startup.

R130/W130 for EVO Plus?

There are no decent spec sheets by Samsung for sure!

There is a slight glitch in upper part. All pixels shifted 1-2 pixels sideways. Normal?

EDIT: 1 glitch > 2 pixel. Below at least 2 other glitches.