Messages

Thanks! Just wanted to post my findings in the hope they'd be helpful for further development

First time taking my EOS M for a spin outside.
I used the latest build:
crop_rec_4k_mlv_snd_isogain_1x3_presets_2019May26.EOSM202

So far I'm really impressed with the results.
Filmed mostly in mv1080p MCM rewire.
Didn't have any major issues, but I noticed I have to toggle the Canon menu button almost every time I startup the camera.
It seems to start up in crop mode by default.
Clicking the Canon menu button twice gave me the expected wider field of view.

This is my ML folder with the settings:
https://www.dropbox.com/s/eqonfs69xx9aaqm/M28-1255.MLV?dl=0

When I filled up my SanDisk Extreme PRO 64GB 170MB/s card, I continued with a slower KomputerBay card. Didn't get continuous recording on that one, but that was expected.

However, six clips came out at 1736x696 resolution.
Here's one of the clips: https://www.dropbox.com/s/eqonfs69xx9aaqm/M28-1255.MLV?dl=0.
MLV App opens it with a height stretch of 1.67 to make it 1736x1160 which is a 3x2 aspect ratio.

The rest of the clips are 16x9 at 1736x976 resolution, as expected.

What could be the cause those clips were recorded at a different resolution?

I followed the instructions from clanlee. https://www.magiclantern.fm/forum/index.php?topic=13152.msg199351#msg199351 But this version doesn't work with compressed MLV files: http://www.magiclantern.fm/modules/modules/MLVFS_x64.zip/MLVFS_x64.zip So I trashed the mlvfs_x64_avx.exe and mlvfs_x64.exe files and instead put the mlvfs.exe from bouncyball in that folder: https://bitbucket.org/bouncyball/mlv-tools/downloads/mlvfs.exe.

Seems to be working now with the following command:


mlvfs.exe Z:\ --mlv-dir=D:\Files\ML --resolve-naming

I'm using installed Dokan_x64.msi version 1.2.2.1000.

I got static noise too. So downloaded the files from https://bitbucket.org/ArcziPL/magic-lantern/downloads/mlvfs_x86_x64.zip. But can't get it to work with the same command which worked before (but resulted in footage with just noise). I tried "mlvfs_x64_lossless.exe mount/path/ --mlv_dir=path/to/mlv/folder" and "mlvfz.exe mount/path/ --mlv_dir=path/to/mlv/folder". But both just return to the command line immediately. Isn't this the correct command any longer?

Bought the EF-M 22mm f/2 STM today and it came with a free EOS M. Now I've got 2! Can't wait to start using ML extensively on both of them ^^

Thanks for clarifying! Will do that from now on

Also the mv1080p MCM rewired mode with 3x crop enabled gives very clean (no aliasing) footage and real time color preview (no lag) in 1624x1080 resolution. Continuous recording. Quite nice and easy to use if a big crop is appropriate.

Did some recording experiments and noticed my footage got corrupted when I choose the 12-bit lossless and 11...8-bit lossless option.
Then I checked what my settings were in the "Crop mode" and noticed the "Bitdepth" was set to "10 bit".
Just trying to make sense of all the options here, I think it works as follows:

"Bitdepth" in the "Crop mode" submenu should be set to "off" when you want to change the "Data format" in RAW video menu.

In case you want to change "Bitdepth" in the "Crop mode" submenu, then you should set the "Data format" in "RAW video" to 14-bit lossless.

The footage becomes corrupted if you change "Bitdepth" in "Crop mode" submenu and change the "Data format" in "RAW video" menu to something else than 14-bit lossless.

Question: is setting "Bitdepth" in the "Crop mode" submenu (when "Data format" in "RAW video" is set to 14-bit lossless) the same thing as setting "Data format" in "RAW video" to 12-bit lossless when "Bitdepth" in the "Crop mode" submenu is set to "off"?

Just trying to understand where I'm supposed to change what, and what it affects.


Noticed something else wile testing:

In mv1080p 1736x967 46/48fps mode the 11-bits mode gives corrupt footage. Half of one frame combined with part of another, stutter etc. 10-bit and 14-bit work fine.

I get some color artefacts in mv1080p 1736x967 46/48fps and MCM rewired mode that I can't get rid off in MLV App (focus pixels and chroma smoothing didn't help). See picture. Does anyone have an idea how to solve it? When I activate 3x crop mode via the "Crop mode" submenu the same scene is very clean.



Link to MLV: https://www.dropbox.com/s/69jo5hicddv5l0v/M25-1740.MLV?dl=0.

Tested with crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr11.EOSM202.

Thanks for the tip and good to know you're aware of the incorrect crop factor value. If possible I'd find it useful if it would show the correct factor. Just made a 27minute test recording that filled up the 64GB card. For me it seems to work continuous without issues in this mode. I greatly overexposed to test, as I understood that increases the datarate.

To get started, I'd like to try to record raw continuously with the smallest sensor crop possible in 16x9 ratio at 25fps.

So I loaded crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr11.EOSM202 on my camera. Enabled the modules: crop_rec, dual_iso, file_man, lua, mlv_lite, mlv_play, mlv_snd, sd_uhs. Restarted the camera. Ran the cinema 2:35.1 script. It puts me into 4.5K anamorphic mode, with sluggish live view. So I enter ML menu. It shows "Crop mode" set to 5K anamorphic and "RAW video" to ON, 1488x1900 1.88x. I assume this 1.88x is the crop factor in this recording mode. Correct?

I'd like to minimize the crop, so I change "Crop mode" to "mv1080p MCM rewire", and go in and out of the Canon menu. This seems to decrease the crop when checking the FOV in live view, which is what I'm after, but now it shows "RAW video" is "ON, 1736x738 4.83x". What does the 4.83x mean? Is it correct? Haven't seen this discussed before I think.

I enter the "Crop mode" submenu and enable "set 25fps" and change the "ratios" to "16:9". Also in "RAW video" submenu I set "Aspect ratio" to 16:9. The resolution is now at 1736x976. It still says 4.83x. If that's the crop factor I think it's incorrect and would be useful if this could be fixed.

I'd like to set the shutter speed to 1/50 but can 1/45 is the closest I can get (using the Shutter menu in Expo ML menu).

By the way I read all of the posts from page 71 up until here. So I'm trying to put the theory into practice here.

Going to try a recording to see if it's continuous with these settings (I guess it will be, I'm using SanDisk 64GB SD Extreme Pro UHS-I U3 V30 170MB/s)

These are the benchmark results for my KOMPUTERBAY 64GB CF CARD 1000X in the Canon 50D.

I'm currently selling two of these cards on the dutch website Marktplaats: http://www.marktplaats.nl/a/audio-tv-en-foto/fotografie-geheugenkaarten/m811324129-super-snelle-komputerbay-64gb-cf-card-1000x-voor-raw-video.html.
So if you live in the Netherlands (or close by) and need fast shipping you should have a look at my offer

@Jip-Hop try merging the files together and rescuing the merged file.

Thanks for the great tip! I merged the files with the following command in a command line window:

copy /b "C:\...\blah.RAW"+"C:\...\blah.R00"+"C:\...\blah.R01"+...+"C:\...\blah.RXX" "C:\...\blah-merged.RAW"

And after that I was able to recover the raw file with rawcover.py

I have a python script that attempts to extract usable .RAW files from this kind of corrupted/recovered partial RAW files.

You can get it here, but you'll need a python runtime to run it (built in on mac, get from http://www.python.org/ for windows).

Script: https://bitbucket.org/baldand/mlrawviewer/raw/master/tools/rawcover.py

Do:

python rawcover.py <dir_containing_raw_files_or_one_raw_file> [<dir_for_recovered_raw_file>]

It will recover everything it can find, including sometimes partial frames that have been chopped in half.

Good luck!

I successfully recovered a RAW file consisting of multiple parts using the above script. The .RAW file and the .R01 file recovered fine. However, the .R00 file threw an error. This is the output in the command line window:

e:\Users\Me>C:\Python27\python.exe e:\Users\Me\Desktop\rawcover.py E:\Users\Me\Videos\ZG\100CANON\M14-1911.R00
Source: E:\Users\Me\Videos\ZG\100CANON\M14-1911.R00 Target: E:\Users\Me\Videos\ZG\100CANON
Attempting to recover: E:\Users\Me\Videos\ZG\100CANON\M14-1911.R00
File length: 4294967295
Scanning file for Magic Lantern RAW headers.
0%.. 0%.. 0%.. 1%.. 1%.. 1%.. 2%.. 2%.. 3%.. 3%.. 3%.. 4%.. 4%.. 5%.. 5%.. 5%..
6%.. 6%.. 7%.. 7%.. 7%.. 8%.. 8%.. 8%.. 9%.. 9%.. 10%.. 10%.. 10%.. 11%.. 11%..
12%.. 12%.. 12%.. 13%.. 13%.. 14%.. 14%.. 14%.. 15%.. 15%.. 16%.. 16%.. 16%.. 17
%.. 17%.. 17%.. 18%.. 18%.. 19%.. 19%.. 19%.. 20%.. 20%.. 21%.. 21%.. 21%.. 22%.
. 22%.. 23%.. 23%.. 23%.. 24%.. 24%.. 25%.. 25%.. 25%.. 26%.. 26%.. 26%.. 27%..
27%.. 28%.. 28%.. 28%.. 29%.. 29%.. 30%.. 30%.. 30%.. 31%.. 31%.. 32%.. 32%.. 32
%.. 33%.. 33%.. 33%.. 34%.. 34%.. 35%.. 35%.. 35%.. 36%.. 36%.. 37%.. 37%.. 37%.
. 38%.. 38%.. 39%.. 39%.. 39%.. 40%.. 40%.. 41%.. 41%.. 41%.. 42%.. 42%.. 42%..
43%.. 43%.. 44%.. 44%.. 44%.. 45%.. 45%.. 46%.. 46%.. 46%.. 47%.. 47%.. 48%.. 48
%.. 48%.. 49%.. 49%.. 50%.. 50%.. 50%.. 51%.. 51%.. 51%.. 52%.. 52%.. 53%.. 53%.
. 53%.. 54%.. 54%.. 55%.. 55%.. 55%.. 56%.. 56%.. 57%.. 57%.. 57%.. 58%.. 58%..
58%.. 59%.. 59%.. 60%.. 60%.. 60%.. 61%.. 61%.. 62%.. 62%.. 62%.. 63%.. 63%.. 64
%.. 64%.. 64%.. 65%.. 65%.. 66%.. 66%.. 66%.. 67%.. 67%.. 67%.. 68%.. 68%.. 69%.
. 69%.. 69%.. 70%.. 70%.. 71%.. 71%.. 71%.. 72%.. 72%.. 73%.. 73%.. 73%.. 74%..
74%.. 75%.. 75%.. 75%.. 76%.. 76%.. 76%.. 77%.. 77%.. 78%.. 78%.. 78%.. 79%.. 79
%.. 80%.. 80%.. 80%.. 81%.. 81%.. 82%.. 82%.. 82%.. 83%.. 83%.. 83%.. 84%.. 84%.
. 85%.. 85%.. 85%.. 86%.. 86%.. 87%.. 87%.. 87%.. 88%.. 88%.. 89%.. 89%.. 89%..
90%.. 90%.. 91%.. 91%.. 91%.. 92%.. 92%.. 92%.. 93%.. 93%.. 94%.. 94%.. 94%.. 95
%.. 95%.. 96%.. 96%.. 96%.. 97%.. 97%.. 98%.. 98%.. 98%.. 99%.. 99%..
No Magic Lantern RAW headers found.
Unknown section from 0 to 4294967295
start 0
Found possible bayer frame
Traceback (most recent call last):
  File "e:\Users\Me\Desktop\rawcover.py", line 489, in <module>
    sys.exit(main())
  File "e:\Users\Me\Desktop\rawcover.py", line 486, in main
    recover_file(source,target)
  File "e:\Users\Me\Desktop\rawcover.py", line 458, in recover_file
    rescue_norawm(f,us,ue,fn,rn)
  File "e:\Users\Me\Desktop\rawcover.py", line 307, in rescue_norawm
    f.seek(check)
IOError: [Errno 22] Invalid argument

Does anyone know what this error means? It seems like a program crash.. however the error is consistent with the .R00 file and the script worked with the other files so I have little reason to doubt the code of the script.

@ arboldeconfianza -  I tried using the tool you recommended to change the Black level setting but with no luck.  Nothing is happening.  Also, since a 50D is a 50D, why should we have to change the BL in the first place?  Shouldn't there be a standard setting within the ML itself when installed that fixes it by default use?  It really suxs that i cant get any of the latest builds to look normal on my 50D - they are all extremely pink/ magenta and can not be corrected.  I know its apparently a soar subject to bring this up, but the latest version of TL does not have this issue except a SLIGHT magenta shift that can be adjusted in CC.   TL was on the right track to perfecting the 50D.  I get amazingly beautiful creamy ALEXA like images using TL and processing through resolve.  TL still did have some issues that I thought the latest version of ML would have addressed by now....Please, dont give up on the 50D - its looks amazing - even better than the 5D mkii when processed right!

When I started looking into RAW last week I tried MLV first, but all the clips had the magenta shift. I disabled fix black level in the MLV settings and after that the color was correct. However, I'm now using RAW_rec instead of MLV_rec because it gives me much more consistent performance. I would suggest you to turn off fix black level in the latest build to see if that helps or use RAW_rec. Seems to be working for me. I'm going to use it for a shoot tomorrow, excited!

I've been testing my two 64gb 1000x Komputerbay CF cards today on my 50D with the MLV_rec and RAW_rec module. I'm looking for settings that would allow true continuous recording until the card space is filled up. I was thinking it should be possible with these cards and MLV_rec, but I can't get reliable/consistent results. Recording always stopped after a few minutes. The settings I was using were:

In the canon menu:
Image Quality = Raw
Auto Lighting Optimizer = OFF
Long exp. noise reduction = OFF
High ISO speed NR = OFF
Highlight tone priority = OFF

In the MLV menu:
Resolution: 1568x882
Global Draw: off
Frame Skipping: on
Preview: Hacked No Prev
Status when recording: debug
Extra Hacks: on
Fix black level: off
Show buffer graph: on

I've tried various settings and both cards, but I supposed the settings that I just mentioned would deliver the highest write speeds. Though, I didn't achieve continuous recording. I tried lowering the resolution a bit, but the buffers continued to fill up after a while.

Trying RAW_rec worked much better for me and I was able to fill up the entire 64gb in one shot. Does any of you get continuous recording with MLV_rec on the 50D with Komputerbay cards? I'm wondering if I should return my cards... I'm using magiclantern-Nightly.2014May08.50D109.

Dear drkamikaze,

I found some conflicting info and I'm not sure which is right.
You've written in your article:

"In the Canon menu, change your record settings under the first red menu with a camera icon to JPEG and turn off raw.  You do this under the "Quality" menu. Also, make sure Exposure Simulation is on, which you can do under the second yellow wrench > Live View function settings > Expo. Simulation. Apparently this helps buffer speeds."

But in the first post of Topic: How to record: -- 30/24/25 fps RAW VIDEO ON 5D3 & others (http://www.magiclantern.fm/forum/index.php?topic=5451.0) there's written:

Latest findings to prevent frame drops:

You should check that in Canon Menu:
Image Quality = Raw
Auto Lighting Optimizer = OFF
Long exp. noise reduction = OFF
High ISO speed NR = OFF
Highlight tone priority = OFF
Multiple Exposure = Disable
HDR Mode = Disable HDR

So it seems Image Quality should be set to RAW.
I know that post hasn't been updated since september 2013 and it has been written for the RAW_rec module (instead of the MLV_rec) but I suppose those settings still apply. Maybe you can update your article with above settings?

Hi all,

I've been lurking in the forums, and finally got my 50D installed and working. I'm not proficient in computer coding so I can't contribute by helping with the builds, but I did go ahead a document my install and set up process, as I found I had to search a lot far and wide to figure out how to get everything working.

There are two posts, one on installing, and the other on setting up and recording.

http://altcinema.com/2014/05/10/diy-filmmaking-and-the-canon-50d/
http://altcinema.com/2014/05/10/magic-lantern-setup-settings-and-shooting-raw-hd-on-the-50d/

I hope people find it helpful!

Oh, and here is my test footage. I was only able to get up to about 1400 frames in 1920x1080 with the Transcend 64GB 1000x card, which maxed out at 81MB/s, so I am sending it back in favor of the Komputerbay, which I found out after the fact seems to be getting faster results.

https://www.youtube.com/watch?v=cXWCRt6Dn1Q

Long time reader, first time poster. I've read trough the entire thread and I think it's just incredible that CineForm co-founder David Newman is on the Magic Lantern forums and puts his free time in this project! I hope this project still motivates you.

I recently bought a used 50D (and two very expensive CF cards) just to experiment with Magic Lantern RAW Video. Up until now I've been having a tedious workflow: denoising h264 files with NeatVideo and converting that to CineForm. Batch converting Magic Lantern RAW Video to CineForm RAW (without the need to 'reconstruct' from a h264 file with NeatVideo) is a workflow dream come true. I can't wait for my CF cards to arrive.

I just wanted to show my appreciation and let you know I'm looking forward to improved debayering in CineFrom and MLV and Mac support from the conversion tool. (I was hoping to completely abandon Windows in favor of OS X, but if there's no Mac support for this tool I may have to reconsider my decision).

Thanks for giving to the ML community!