Messages

This build almost works
12 bit ok, but 10 - top 1/3 part of a frame shifts out of place all the time, so the image is broken. It behaves differently with FPS changes, so... I don't know Some registers values are not right?

For me 10 bits makes a lot of difference. For example, 1600x670 using 14 bits I can only record for 4 seconds, using 10 bits - for 8 seconds.
If this time could be increased to ~10...12 sec for me it can be enough to actually use RAW on this camera..

More info: i use ML version: crop_rec-4k3x1-2.8k24p_3x3-48p-all-centered_8.18pm-5D2-eXperimental.2019Dec31.5D2212, and duplicate that for all CF cards (because i want to record 10 bit MLV not 12bit it is too much)

Using this build, sometimes when I turn on the camera ML modules won't load and files in "modules" folder gets damaged - they have random (garbage) file names and I can't even delete them. So then I have to format the card. Maybe this behavior responsible for your cards failure...
You can try this build
https://builds.magiclantern.fm/jenkins/job/raw_video_10bit_12bit/53/artifact/platform/5D2.212/magiclantern-raw_video_10bit_12bit.2019Mar24.5D2212.zip
form here https://builds.magiclantern.fm/experiments.html
It has 10 bit option and so far I haven't encountered this error with this build.

Raw should probably consume more power. But when I did timelapses with 550D, I didn't notice much difference between usual h264 and raw.

64bit version won't be much quicker than 32bit, it is just the way MLV App work. It does all calculations with CPU and processing raw video takes some time. If you have fast computer you can open two or more MLV App instances and process multiple files at the same time.

If you want speed - you can export dng sequence from MLV App (it will be relatively fast) and then open it in DaVinci Resolve.
Also check this https://www.magiclantern.fm/forum/index.php?topic=19021.msg239749;topicseen#msg239749 it can process raw footage with GPU and it is fast but you need a powerful GPU.

For instant .mlv playing you can check this thread https://www.magiclantern.fm/forum/index.php?topic=26596.0 and other links in it.

what is that? is that an extension or something new for ML, where to download it?

go to modules, enable mlv_rec and mlv_play, have fun

to open and process .mlv files on computer you can use https://www.magiclantern.fm/forum/index.php?topic=20025.0

if resolution and quality is not important, you can use 640x480 crop from Canon menu, it is default 550D option. It will give you maybe even more than 5x magnification..

[-vf lut3d=C:/dir/lut.cube]

On windows 10, ffplay.exe and MPV player both works, tested them with 5D2 and 550D uncompressed mlv files, 10/12/14 bit depth - all works. I don't have any MLVs with sound so didn't tested it..

MPV player seems to work more smoothly, and it loads relatively fast, I associated .MLV with it - cool. But as you know - videos look green, so I made a quick lut (could be better) and spent a lot of hours trying to figure out how to make it work...

First of all, if path to the LUT file contains drive letter, for example  -vf lut3d=C:/dir/lut.cube - this will not work, at least on windows 10. You should write it like this:

Code Select Expand

--vf=lavfi=[lut3d='C\:/mpv/correction.cube']

where C:/mpv/correction.cube is your path to the lut. Notice \ before : and single quotes ' - it is important.

Then to pass this argument while opening .mlv by double click, I wrote a batch script but it takes extra couple of seconds to execute, so it is not optimal.
I ended up modifying the registry, seems like in windows 10 they changed everything and I could not find how to add a parameter to .mlv, so I just edited registry for mpv.exe

in  \HKEY_CURRENT_USER\SOFTWARE\Classes\Applications\mpv.exe\shell\open\command
it was:
"C:\mpv\mpv.exe" "%1"
I changed it to:
"C:\mpv\mpv.exe" "--vf=lavfi=[lut3d='C\:/mpv/correction.cube']" "%1"

Now any file opened with MPV player will play with LUT, but if we are only using MPV for MLVs it is fine.
As a result - double click on MLV and you will see somewhat correct preview, works relatively fast, good enough for clicking through folders with MLVs.

But I suck at LUT making so if Danne have old LUT or someone can make new it will be perfect.

@NHCD if you ever find sd-cf adapter working with ML (even if it is very slow), please share details here...

Interesting.. guys, do you have original LUT to fix colors in ffmpeg preview?

link here https://www.magiclantern.fm/forum/index.php?topic=18392.msg176327#msg176327 says "You need access"

[5632x3124 @ 3.8fps]

Look at fast CF card prices before choosing the camera

You probably can do it with 5D2, but you will need some registers manipulations.
There is a build for true 5,6k resolution here on the first page: https://www.magiclantern.fm/forum/index.php?topic=19336.0
Experimental build:5632x3124 @ 3.8fps

And it is 3,8 fps so you need to slow it down to 2 fps (.5s) and adjust shutter speed, should be possible. But I don't know how to do it, what registers to change.
I tried this build (with ~4k resolution because of the slow cf card) and it works, but you need a lot of card space for uncompressed RAW with this resolution.

Thanks! I thought if you tick "creative adjustments" it will break log curve, but..
If I just set "dark strength" to zero - it will look exactly the same as without "creative adjustments" enabled! But now I can do other corrections... cool. Is it mentioned somewhere? How could I not know about it?

it was beautiful, and lovely colors
can you share some details, for example how you color graded it?

But don't get me wrong, shooting ML RAW is awesome. It is just not as user friendly. Personally I do love it and enjoy working with it.
And if you know your camera and settings that work, then it can be reliable enough..


Main limiting factors for more or less serious work could be:

Card full, because sometimes you can forget how much free space left.. free card space indicator only show you the real number after you reboot the camera. So if there is no space left, recording will just stop, but file saved.

Sometimes recording can stop for various reasons, but it is rare unless you are trying to push it to the max resolution/write speed, etc.

Playback of recorded raw files in camera is very slow and low resolution.

Experimental builds can sometimes crash, rarely but it can happen, and sometimes you will need to format the card. If you have only one card with you, and no laptop - it will be completely useless. I don't know what camera/build/card combination can cause this behavior, maybe it is something very specific and you will never encounter this problem.

And obviously RAW footage takes a lot of GB so you probably need at least a couple of cards and maybe a laptop where you can copy everything.

HDMI preview doesn't work in all modes, so it is hard to share the screen with others. But it is a work in progress, maybe HDMI support will become better in the future.

And overall not so simple process, not really critical, but if you need to keep in mind 1000 things at the same time (lighting, framing, focusing, movement, and always check if everything is OK in the frame and on set) it is not so easy

I think it is absolutely different experience with ML-camera and any other cameras.

You can find capable ML-enabled cameras such as 650D maybe even cheaper than EOS M, especially on local market places, and then use some vintage lenses which can cost anywhere from $3..$5 to $60+ or even for free if you have old SLR cameras.. and this way build really inexpensive setup. Way cheaper than anything else.


But I think the main difference is the workflow.
With ML you can probably achieve more beautiful and "cinematic" picture if you know how to do it, but the process is slow. You need time, patience and practice a lot, it is not as convenient and you can even lose some of your footage if it was recorded with pink frames or something was not set properly. And processing RAW is slow and files take a lot of space on cards/HDD. And HDMI preview not always working and so on.
While any other camera will just work out of the box, without any problems

ML raw won't be true 4k, although there are 5k modes but they are 1:3, not 1:1. But they are very close to 4k. And what is more important - the color information and ability to push your footage in post-processing is amazing with RAW.

If you like this concept - you will like shooting ML RAW, and if not - then any other camera would be 10x better

By the way, it is possible to do it from the opposite side - change your retro computer frequency to match the camera fps.. It can be done by feeding the external clock from any oscillator (diy osc or special chip). At least, slight under/overclocking should work fine.. But fps override in ML is probably much easier/faster

I always get pink sun in my footage, and it is easy to mask out... create a layer filled with color (just use color picker and sample the brightest area near the sun), then add mask (slightly bigger) to this new layer and feather it a little. Done.
I don't even track the mask sometimes when there is not a lot of motion. But you can track it with auto tracking, it won't take much time. It is just one object with fixed size and precise position doesn't really matter, so you can loosely track it and it will be ok.


It would be cool if some day MLV App will be upgraded with black sun detection/replacing with surrounding color..

Is there a way to somehow export dng sequence and then use cr2hdr to process it, then import the sequence in MLV App back again?

I read some articles, and 16 pulses are not 100% requirement. as well as precise timings.
So the pulses at 32 kHz is actually the way IR reciever works, it has bandpass filter inside and it is tuned somewhere around 32k. For example in TVs they sometimes have frequencies close to 38 kHz if I remember correctly..
And once you pulse your ~32kHz, the reciever will output a steady 5v (or maybe 3.3v). It doesn't care if there are 16 pulses or slightly less/more.. there is no counter or anything.

The camera itself has some timing tolerances. So you can use any frequency close to 32kHz and send any amount of pulses for ~500us, then wait ~5,8ms and send pulses again.

If no counter and precise timings required, I can make the whole circuit using just simple analog components
Why? just because it can be done I like microcontrollers but here it looks a bit like overkill.. it is just more interesting to do it analog way sometimes.
Here https://www.doc-diy.net/photo/rc-1_hacked/ in the comments someone made his version using just 4093 NAND chip, but I don't really like two switches and 6v batteries. So now I have to design my own version from components that I have around.

Ok thanks! This article has some useful links as well as exact timing signals from the actual rc-1.. seems like everything is just running from 32.768kHz clock (standard quartz resonator frequency) and I think I can make it even without microcontroller. Just a simple timer/counter IC and maybe a transistor or two could be enough.. I have to think about it though.

Cool, so if you just blink 16 times with 16us delays, then wait 5360us and do blinks again - it is Canon remote control code and you can start and stop video recording?

I actually want to make a remote for video start-stop, so thanks for this thread..

By the way on usual arduino you probably shouldn't use digitalWrite because it is very slow, if we are talking about microseconds.. direct port manipulation is much better... but maybe your Raspberry Pi Pico is fast enough.

It's just an old information.. this is what you will get with 650D or 700D: https://www.magiclantern.fm/forum/index.php?topic=25784
And Bilal is also working on 100D, I wonder if 100D have less sensor noise than 650D

What about 5D3? it is full-frame camera so no 1.6x "magnification" but it will probably have much lower noise with high iso..

Could you please try this?

Thanks, it works! You guys are awesome!
I had to copy libgomp-1.dll from 1.14 Win32 version, because it is not included in the archive. And it opens up. I also copied ffmpeg and some other stuff, exported some MLV footage and everything seems to work perfectly

By the way I can instantly see benefits of AgX function - just opened some random mlv file, it was a test clip shot from my window (crappy and noisy) but it has red "Hotel" sign (LED) and it looks much better with AgX enabled.

Love bright colours. BTW, even in those examples, they aren't handled perfectly.

I know I can see it too now

My goal is to create digital image processing that handles bright colours smoothly. It's possible. Film does it. It's what I've been working towards for the past two years.

I agree, this is really great. Keep us updated I think everyone wants to have "film-like" colors.

yes it's core 2 duo.

You could try dual booting 64 bit linux

do you know any protable linux version that I can just copy on the thumb drive and boot from it, instead of installing? for testing.

It could be SSE issue. What's interesting is that I haven't found any other program that won't run on this machine. Although I don't use a lot of applications.

Very pink, wow. Even new MLV App is having trouble.

By the way, it is not LED, it is just a standard white flash light with color filter on it. And it is not even that much as it can be sometimes.. for fashion photos it is normal to have very saturated colors sometimes. For example:
https://lindsayadlerphotography.com/fashion-i
https://lindsayadlerphotography.com/editorial-beauty

Very nice, we see Bilal's work in action now I think cameras like 100d could become a very popular choice for RAW video now..

no message or anything, but I found under windows event viewer two types of errors - with code 1000 and 1005.
both of them doesn't explain much.. but there is an exception code.

1000 - "Faulting application: MLVApp.exe, version: 1.14.0.0"
Exception code: 0xc000001d

1005 - "Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing."
There is no information about what file it is or anything.
Application name: "Processing and converting tool for MLV files"

Finally, MLVApp v1.14 is out now. Thanks to all the contributors and testers.

Great!

so, I'm using Windows 10 21H2 x64, and the processor is Intel(R) Core(TM)2 CPU 4400 @ 2.00GHz

Why 32 bit MLV App - because 1.12 32 bit is working here, but 64 is not. 1.13 doesn't work at all (as well as 1.14)

Are you able to try compiling MLV App?

I think I need to try it.. And maybe if I can use older QT version it will work?

And yes, I would love to see any difficult photos please.

ok, here are some files:
https://gofile.io/d/eh7zCN

In the archive you will find cr2 as well as processed jpeg files (just for reference). The problem is this purple light, which is a light source, so it should be brighter and not just dark purple color..
Photoshop camera raw profiles render it differently. Default Adobe profile is obviously worse, while "faithful" seems to be the most correct.. And not "neutral" as I was expecting.

But even then it still have some problems. For example if you look at 3384, in the center you will see a very saturated region on the hand/fingers which looks obviously kind of wrong..
As well as other problems, some photos looks better than the others. And sometimes it becomes very visible when photos are processed, for example if you add some contrast and change levels, gradients from these saturated regions become not as smooth as they should be, it can be really noticeable on the face for example. We can instantly tell if something wrong with person's face/skintones.

It's Rezeda's photos, and (fun fact) you subscribed to her youtube about a week ago...  I know she tried different things and at the end processed them with two different camera raw profiles, one for the overall look, and maybe "faithful" or "neutral" for the purple part of photos only. So obviously these saturated colors can be a little bit hard to work with..