Messages

Hi, just doing first steps ever with video recording using EOS M and magiclantern-crop_rec_4k.2018Jul04.EOSM202.zip from official experimental builds.

I load:
- sd_uhs (my custom build, fixed to 160MHz, D1 D1, found to work best with my SD card)
- mlv_lite
- mlv_snd
- dual_iso
- ettr

Recording videos using Manual Exposure mode, 5x zoom, RAW 1920x1080, FPS override to 25fps, preview: framing

In Canon menu selected: 1920/25, Servo AF in videos: off, AF on half-shutter during recording: on/off (tried both)

Have noticed a problem with AF:

After starting recording in 5x zoom with ML overlays the focusing on half-shutter stops working. I doesn't work even after stopping the recording. Preview changes to 5x, full color for the time when I hold half-shutter but if does not focus. To use AF I need to: click INFO to exit ML overlays and have magnifier icon visible, unzoom completely. Then it works until I press INFO again to enable ML overlays and start recording.

There is also an unexpected behaviour with the exposure time. To change exposure parameters I close ML overlays and enable the Canon overlays using INFO (otherwise I don't see which parameter is actually selected). Exposure time box shows 1/50s and is not modifiable. If I change the value it reverts to 1/50s immediately afterwards. But it seems, that the recording was not made with 1/50s but rather 1/38s, which was also the time shown in ML overlays. But as I now see, this can be adjusted in ML menu. Actually not to exactly 1/50s but 1/53s which is close enough. Also ISO setting is there and I believe the ML histogram shows the exposure which will be really applied during recording. Is this, how you work at the moment or is there a simpler way to set everything up?

Hi,

each of my RAW videos recorded with 700D or M comes out in MLVApp very bleak, faint. Interesting fact: they always open with default white balance of 6000K and using the white balance picker on gray or skintone areas changes the setting to the range of 9k of 10k (and still looking crappy), despite recorded in normal dayligt, so there is definitely something wrong. I don't see any simple way to make it look right in MLVApp using the standard sliders.

Some sample MLVs downloaded from this forum do not show such problem but they were from another camera models.

My MLVs opened in Fast Cinema DNG or Adobe Camera RAW (single DNGs extracted using MLVFS) look normal.

I'm recording using mlv_lite from crop_rec_4k_mlv_snd from https://builds.magiclantern.fm/experiments.html using 5x zoom, mostly 12-bit lossless but in full frame mode it was the same. MLVApp tested 0.15, 0.16, 0.17. All are same.

Where does the problem lay?

MLVApp with default settings:


Fast Cinema DNG with default settings:

Does the top LCD show anything, when you turn the camera on?

Here you can get the manual
www.fastcinemadng.com/download/FastCinemaDNG.pdf

Great, thanks!

[MLVFS_x64]

MLVFS_x64
Download http://www.magiclantern.fm/modules/modules/MLVFS_x64.zip/MLVFS_x64.zip
Extract MLVFS_x64.zip

Hi, is there a newer windows build available, supporting MLV with lossless JPEG compression? Tried already several builds, out of which this one seems to be the newest one, but only uncompressed MLV are opening properly.


EDIT:
huh, here it is...

https://www.magiclantern.fm/forum/index.php?topic=19429.0

https://bitbucket.org/bouncyball/mlv-tools/downloads/

Thank you, bouncyball!


All in all it's a fantastic tool! But all the docus are totally outdated...

Just tested on EOS M, if shorting the audio input is able to generate enough noise level to be used as a trigger -- yes, it is. In case you would have problems with repeatability, you can use a tiny button battery (1.5V) which will be applied to the audio input. This should work reliably.

As I understand, Albert wants to trigger the camera with a switch, not with a sound. If so, there is a dedicated solution for it, without a need of going such way around. It would however, as you say, not work with the original M but will work with every (?) DSLR and many mirrorless system cameras.

Such remote switch was invented already decades ago, doesn't need ML and is quite standardized among many manufacturers.

https://shop.usa.canon.com/shop/en/catalog/remote-switch-rs-60e3

From a third-party manufacturer or used should cost much less, I would expect ~$5.

As I can't do myself atm:
can someone provide me a working build with adtg module included for 100D plz??

last one I used to compile should have been this:
https://bitbucket.org/nikfreak/magic-lantern/branch/isoresearch

Recent vanilla iso-research branch compiled for 100D with default modules (adtg_gui included). Not tested as I don't have a 100D.

https://bitbucket.org/ArcziPL/magic-lantern/downloads/magiclantern-isoresearch-Nightly.2018Jun05.100D101.zip

You have to be in one of the following modes: M/Av/Tv/P. The camera manual describes it for sure. And don't use EOS Utility for that.

Run "firmware update" from the original menu.

The output looks now, after enabling sharpening, really good! Great job!

To enable any set of image processing modules in Fast CinemaDNG Processor, you need to close current project and go to dialog Options (right tab) - there you can check all available image processing modules. We've done that because sometimes user doesn't have enough GPU memory to utilize all available options.

...the tab "Output and extensions" was also grayed out... First time in my life I see a program, where a project has to be closed in order to access configuration settings. Usually it is the other way round. Thanks for the hint! I know it's still in development but IMO you should change it or at least properly document (bundled PDF does not describe it). I spent also a good 20 minutes to find an option to open .MLV but it doesn't exist. You have to drag&drop or use context menu in windows explorer. Usually ALL importing options are accessible from a menu. But this was at least described on your web page.

free version has no de-noise or sharpening but you can use
CinemaDNG for that and is currently free also, recent update enables loading of MLV files directly

Any idea why Denoise and Unsharp Mask are disabled in Fast CinemaDNG? It opens MLV by drag&drop, allows focus dots removal, white balance, curves and exposure compensation. And... that's it. "Denoise" and "Enable USM" are grayed out, I can't click them. The HELP is also not opening... It's very fast in conversion but seems to be ultra limited in features?

Thanks guys for all the details!

are you sure davinci resolve enable loading MLV files

It was in the context of Fast CinemaDNG.

no de-noise or sharpening but you can use
CinemaDNG for that and is currently free also

Where to get a free one? I see a 2 month demo only.

Primes with STM are audible, zoom lenses with STM are absolutely silent.

USM is quiet for photography but loud enough to be catched by a microphone located near camera while recording a video with AF.

All in all USM is my favorite for photos -- quick, quiet but I still hear if it works a provides a great manual focus capability. STM's focus by wire is for me a no-go for manual operation. I find it, at least in Canon's implementation, unusable. However for videos with AF or with lenses, which I never use in manual focus (tele), STM is great.

You're shooting with full frame cameras and listed the Canon 10-18mm lens. How did you get that EF-S lens to mount on those bodies?

EF-S 10-18 IS STM is commonly modified by cutting its back, in order to fit onto EF-mount and being used with m4/3+speed booster or even full-frame Canon cameras. It has drawbacks: strong vignetting at wide end and risk of damaging the mirror at 10mm position. But you gain stabilized ultra-ultra wide angle at extremely low price.

Here's an example:
http://photography-on-the.net/forum/showthread.php?t=1388461&page=1

Code Select Expand

dd if=ROM1.BIN of=BOOT.BIN bs=64K skip=1 count=1
dd: bs: illegal numeric value


Code Select Expand

dd if=ROM1.BIN of=BOOT.BIN bs=64000 skip=1 count=1


Equivalent of bs=64K would be bs=65536.

Just wanting to eliminate this as a possibility before I finally resign myself to the fact that my 70D may have became the latest addition to the queue of other 70Ds that have been reported as failing inexplicably to the extent that the only recourse is to replace the motherboard. (eg see http://community.usa.canon.com/t5/EOS/70D-wont-turn-on/td-p/163122).

Did you try following the steps from video linked in second reply of this thread on Canon forum? Although strange, many report it helped...

Samsung PRO 32GB here. 41MB/s default with 6D. 65MB/s overclocked.

Ok, figured it out!

BM Disk Speed test in Transcend SD card reader:
Samsung EVO Plus with no adapter (directly in microSD slot in card reader) ~83MB/s
Samsung EVO Plus with Red Sandisk adapter ~83MB/s
Samsung EVO Plus with Black Sandisk adapter (from Sandisk Ultra card) ~83MB/s
Samsung EVO Plus with Black Kingston adapter ~83MB/s

Looks like no differences between those adapters anyway.

Log from sd_uhs.mo in 700D:
Before the hack: r:27MB/s w:31MB/s  W:27MB/s R:38MB/s    [best 31MB/s]
(...)
SDR104 @ 160MHz: D1 D1 r:42MB/s w:47MB/s  W:46MB/s R:42MB/s    [best 47MB/s]

Sapporo, kye, thank you very much for sharing your results! So there is no problem with adapters, Samsung Evo Plus is a decent card but only twice more expensive Samsung Pro is on par with SanDisk Extreme Pro when using with 700D. Good to know!

I took a 64GB card that quite reliably shows the shutter bug and copied the QEMU sd.img to it

Does the camera format the card using another filesystem than the QEMU image uses?

Hello, does anyone have a Samsung Evo Plus microSD card and did or could do the benchmarking? It seems to be a promising alternative. Generally it is also able to achieve approx. 90MB/s bulk write speeds but at much lower cost than SanDisk Extreme Pro. As an example: 128GB Samsung Evo Plus is at Amazon equally priced to 64GB SanDisk Extreme Pro (39€ vs. 38,99€). Both are sold by Amazon, so the risk of counterfeit should be equally low.

Funnily, according to some sources, the transfer drops by roughly a half when using the provided MicroSD -> SD adapter. If another adapter can overcome this bottleneck and if similarly high speeds can be achieved with an EOS camera it for me unknown so far. It will decide if it's really an alternative. If yes, it would be a bargain.

You have a normal official firmware in your camera, "only" the Factory Mode has to be disabled. Then the reported FW version will be back to normal.

I'm not sure if anyone here could help you remotely. This would need a possibility of executing a custom code on your camera (I guess setting the boot flag, booting and starting Canon firmware should be possible in this mode but I'm only guessing!) and calling some functions from Canon FW (FA_SetProperty, FA_SaveProperty, MonWrite, MonCall...). The latter would need that the functions' stubs are in this mode same as in normal mode. If they are -- I have no idea. It would also need understanding which property to modify and this area is not explored yet in the context of Factory Mode by ML developers! AFAIR no one played with it yet. I could support here providing logs from another camera models to analyze how the Factory Mode is enabled and disabled over USB interface. Probably it's similar for 6D.

You can try finding any third-party DSLR service and ask if they can do it for you and how much would they charge. I'm sure there are several available in France and this is a 5 minutes only job if one only has a tool. Just call a few and ask directly for the possibility and a price.

It seems that your camera is in factory mode. If you browse the menus, do you see a position "Factory Menu?". If you bought it that way new or was repairing at Canon service recently, they have screwed it up, not switching the camera to a normal mode and should do it on request...