Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - cmh

Pages: 1 2 [3] 4 5 6

By interpolating to 24 fps, I mean 23,976 fps as Zeek did.  I was just too lazy to write all the digits, so I rounded the cadance to 24 fps.  Due to the interface being too slow on the EOS-M, you cannot do more than 18 fps, even 14 fps if you go too high in resolution. 

I don't want to be a contrarian but 3k 10 bits ~24 fps is technically possible. You'll get 50 to 70 frames tho, 3 to 4 seconds. This is why I got confused.

edit: I can upload the mlv if needed.

I just tested 1440x1080 with the mv1080 profile on a bright scene with the sky in frame.
It goes past 52 MB/s at times when overexposed at 14 bits so it's not continuous
I get 45 MB/s overexposed at 12 bits and exposed for the sky at 14 bits, around 36 MB/s exposed for the sky at 12 bits.
12 bits should be safe but I've only tested recording a minute.

I can test 2,5k real quick if you don't mind the crop.
edit: 2,5 k, same resolution and bit depth so I get more or less the same results .

I want to be able to work with the CinemaDNG files in Photoshop before converting them to ProRes 444....

This is how I would proceed: I would get IWLTBAP LUT Generator, generate an hald LUT put the hald ontop of a frame in Photoshop, "grade" everything, cut the hald part out of the image, save that as a PNG and generate a x64 cube LUT that I would import in MLVApp (or Resolve but you should test this by yourself). That woud serve as a base for a grade or a reference.
Look at their website for more in-depth explainations, that is a very useful tool (that I used to convert gmic's hald to cube).

If you are on Windows, MLVApp uses ffmpeg so your ProRes 444 would be 10 bits but on Mac it should be 12 bits  if i'm not mistaken.
With Resolve on Windows, you can export to DNxHR 444 12 bits and Prores should be available on Mac, I'm not sure.

From an esthetic point of view if the goal is to apply a film emulation preset to your shots keep in mind that they are meant for photography and might end up very strong in the context of videography (for the same reason I don't find trying to copy a look from a movie by grading a still particularly relevant, it might look good on one frame but usually really bad on a scene for many reasons that would need a deep dive into cinematography). I don't find grading from Photoshop very appealing overall because it is utterly slow and would lack consistency between scenes but hey, to each his own, there's nothing wrong about experimenting. Feel free to share your findings (preferably in a dedicated post in the Raw Video Postprocessing section instead of this one if it doesn't involve MLVApp).

Haa-h Zeek,

I am so glad to see you have adopted 18 fps filming and have noticed how nicely it upscales to 24 fps.

Correct me if I'm wrong but Zeek mentionned fps "override to 23.976".
I tried this solution myself but the record time is about 3 to 4 seconds (with a Sandisk 170 MB/s) and my kit lens is so soft that it's not worth the effort.
That said I find your suggestions pretty interresting and as soon as I have some time to kill, I'll try to compare Resolve's different frame interpolation methods, on different scenes (like, is it noticeable with a talent and not just b-rolls of static props) and compare various fps .

Watched the stuff till the end, bare hands. Your jokes cracked me up. That's was pretty surreal I'll be honest.
Stay safe.

is the link if you haven't been able to play the embedded video on the forum like me.
Picture is stunning considering the low light conditions and the exposure difference between the sunset and the people.
Awesome stuff overall, I loved the edit.

This code is part of a module named crop_rec.c
Assuming that you use an EOS M, you'd need to compile Danne's build.
If you are on Windows:
Download Cygwin at in "%UserProfile%"\Downloads"

Open a command prompt (press Windows+R, type cmd) and get Cygwin installed with the required packages:
Code: [Select]
cd %UserProfile%"\Downloads
setup-x86_64.exe -s -q -P mingw64-i686-gcc-core,gcc-core,make,mercurial,python37-docutils,perl,wget,unzip,zip,diffutils

Open the Cygwin Terminal from the start menu.
Download the GNU Arm Embedded Toolchain and extract it in the right folder:
Code: [Select]
cd && wget
unzip -q ~/ -d gcc-arm-none-eabi-9-2019-q4-major-win32
rm ~/

Clone the repository and the right branch (hg identify -b should show crop_rec_4k_mlv_snd_raw_only):
Code: [Select]
cd && hg clone
mv ~/unified ~/magic-lantern_dannephoto
cd ~/magic-lantern_dannephoto && hg up crop_rec_4k_mlv_snd_raw_only
hg identify -b

Modify what you want to in C:\cygwin\home\<username>\magic-lantern_dannephoto.
In your case crop_rec.c (replace <username> by yours).

Get to the right platform (EOS M here), cleanup, compile, move zip in C:\cygwin\home\<username>, cleanup again:
Code: [Select]
cd ~/magic-lantern_dannephoto/platform/EOSM.202
make clean
make -j4 zip
mv magiclantern-Nightly*.zip ~/
make clean
cd && ls

Copy the content of C:\cygwin\home\<username>\ to your SD card and you're set (a reinstallation might be necessary depending on your modifications).

Raw Video Postprocessing / Re: Powergrade for Resolve
« on: March 14, 2020, 12:57:08 AM »
Just a basic color correction on random scenes using the power grade you shared to see how it holds up with skin tones in different conditions (an olive complexion shot at 5000K at multiple times of the day).
I'm using the 1.50 dpx and the Rec709 Fujifilm 3513DI D65 lut at 30% as a last node instead of Juan Melara's lut.
Fujifilm 3513DI is way too green in the shadows. I'll stick to Kodak 2383 next time and correct the red cast I get from it.
I tried to get rid of the Alexa CST multiple times but I've always ended up correcting highlights here and there using curves and tone mapping so I'll just keep it as it is.

Not a valid youtube URL

Here's a version dating from last november
Put the content of the zip in your MLVApp folder.

If you need a recent version you'll have to compile it from this source:

raw2mlv topic:

Raw Video Postprocessing / Re: Powergrade for Resolve
« on: February 21, 2020, 05:03:46 AM »
That is so nice to hear! :) The video looks great! I'm happy to have contributed some to the color science of ML raw :P Even if only by putting together stuff from other sources.
Yeah I'm in no way a colorist but I just wanted to say that despit not beeing "neutral" your powergrades are pretty natural and photographic, there's usually not much feedbacks on the ML forum and I wanted to show my appreciation.

All of this can be vastly improved imho. There're tons of ways the tone mapping could be better probably but that's serious stuff. The 2 stops hack bring out some excessive noise, but how to do it differently ?
I don't think that restoring the two stops in the raw tab increases noise as it just compensate for the bmd gamma which brings everything all the way to the left.
As far as I don' try to recover information like upping the shadows, it's ok (but then I'm using an EOS M that is known to have to pretty bad dynamic range so maybe I'm wrong).

I previously tried multiple tonemapping workflows, a decent way was to linearize everything and use Corona highlight compression with Tonemapping Tools in Fusion (filmic and Reinhardt are also available) but that was pretty slow and required me to up the gain instead of ISO otherwise I ended up with muted colors.
Using a colorspace transform node to go from bmd to rec.709 is way cleaner anyway and the gamma mapping is customizable enough for me.

It would be nice to have a thread with better organized collection of power grades for Resolve.
I'd love to see such thread, I would participate.

On the end that's what defines the image and it can be pretty discomforting for a new user to have to do this from scratch.
As for empowering newcomers on this topic, as cynical as it sounds, the large majority wants the youtube "cinematic" aka slap a LUT like an instagram filter. There's a steep learning curve, it would have to be prefaced by how to read the scopes instead of eyeballing it on uncalibrated monitors, yadi yada.

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M
« on: February 18, 2020, 11:35:58 PM »
It's probably the same shutter bug that I got my silver EOS M. Try turning it off and on two or three time real quick (while the led blink right before the display is on).

Raw Video Postprocessing / Re: Powergrade for Resolve
« on: January 31, 2020, 09:32:04 AM »
Testing this powergrade real quick in a mixed light scene (It's an EOS M, 1488x1866 squeezed, 12 bit).
I denoised, changed the white balance, upped the gamma a notch and that's it:
Not a valid youtube URL

Raw Video Postprocessing / Re: Powergrade for Resolve
« on: January 29, 2020, 09:05:58 PM »
The grade 1.50.1 (third still I presume) is pretty simple but it has really great skin tones on an EOS M (the reds are leaning towards the orange tho).

My previous workflow for a quick first pass grade:
I used to enable Pre Tone Curve in the raw project settings, leave the color space to rec.709/sRGB and up the gain to +20 in the raw tab with few other settings: Saturation -5, Color boost +10 to temper the red channel a bit, Highlight -30, Shadows +10. Finally a gamut mapping node: Gamma sRGB, Tone Mapping Luminance, Max Input 1000.
It doesn't look bad but the problem is that if I do a daylight white balance of a mixed lights environnement, skin tones might have to be fixed separately.

Your grade is pretty spot on right off the bat. Thanks for sharing. It's a nice improvement compared to what I used to do, I'll try to fiddle a bit with it.

The liveview problems is probably due to something else, maybe some autofocus settings I left inadvertently.
Everything works fine but just in case, I uploaded an updated build with the same mlv-lite.c edit at line 3944.
Code: [Select]
.shidden    = 0, // TODO: only hide this if crop_rec module is enabled?

I guess I wouldn't worry about it for now, this is not an absolute necessity. I'll just play around & see what happens...

Here's a build with uncompressed data format enabled.

The only difference with Danne's latest build is the suggested edit in mlv_lite.c and the commit 5549fd4 made 22 hours ago in crop_rec.c:(EOSM center preview 48fps mode).
I haven't done much tests, mv1080 14 bit seems to work.

Other settings has some liveview problems (it's either frozen or partly frozen) despit reinstalling ML so I wouldn't recommend using it for 12 bit, 10 bit, 2.5k and 5k anamorphic:
ML ASSERT: 0 at mlv_lite.c:2846 (compress_task), task compress_task lv:1 mode:3

compress_task stack: 1ded50 [1dede0-1ddde0]
0x0009EC24 @ bea1a8:1ded80
0x0009E564 @ 9ec80:1ded50

A little howto for Danne's build using Cygwin on Windows for those who fancy.

Share Your Videos / EOS M - By The River
« on: December 30, 2019, 10:01:36 PM »
By this time of the year, the golden hour is getting close to a golden afternoon so we decided to get some fresh air before the sun sets.

Canon EOS M with Magic Lantern. Canon EF-M 18-55 mm F/3.5-5.6 IS STM.
5k anamorphic preset, 1280x1606, 23,972 fps, 1/50s, 12 bit.

Mostly graded in MLVApp with some minor adjustements in Resolve.
Direct link:

You are making a point, it doesn't make sense for most people to invest in enterprise grade hardware if your HDD aren't spinning, more so if you consider this annual failure rate report.

You are not wrong, but as I said "if my life depended on it" like if my job depended on those backups or if I had to spend a lot of money on some projects.
If those drives are dropped, if someone is trying to plug them without my consent, if it gets wet, etc.
Tape and NAS are not perfect and way less convenient but mitigates some of these issues depending of the solution. In most cases IP67 USB disks are fine for dumping and archival. Some people are dedicating a bunch of external drives to a project, backup properly, check file integrity, put the backup in a safe place and I'm perfectly fine with it. If it's comparable to the cost of the gear or cheaper, I'd consider a failproof solution. Like an insurance, you might never need one or it might save you.

The NAS solution is getting expensive real quick too. It depends on the workflow really. If you need to label projects and span that across multiple drives, it's a bit of a pain.

edit: I'm not an expert, I won't take offense if we disagree and I'd just assume that you might be more experienced than me.  :)
edit 2: decided to cut down the excess verbiage and edited the whole paragraph about cost, my maths was totally wrong LTO tape is way too expensive below 90 TB (so like really big projects).

Happy Holidays!


It really depends on the scale and how serious you are about it.
I imagine a scenario like backing up 15 years of MLV of a daily shooter, twice and keep a copy in another place, safe and far away and keep doing that for at least a decade.
Your solution is prefectly fine in most cases but if my life depended on it I wouldn't push my luck with mechanical consumer grade drives that are meant to be unplugged a lot and transported often.
Keeping a physical copy on another location is a great idea tho. Cloud backup solutions are great for that.
The initial cost is relatively steep but tape really is the best thing, we are of talking of 30 terabytes of compressed data for 60 bucks.
As for the environement, a small home lab isn't the best solution but I'd argue that with the power saving features and a good power supply, in the long run it will probably waste less energy than let's say a smart tv.
If it's a concern, picking a low power SoC like an Intel N4200 that has a 6W TDP for exemple would be ideal (and it doesn't have to serve only one purpose).
What's great about that solution is restricted physical access that's why I'd suggest a locked room/cabinet, a downside is maintenance, some people don't have time for that.

TLDR: What I meant to say is that your solution is prefectly fine for dumping data before archiving (you could stack usb drives on shelves and barely touch them, some people do that but meh).

My two cents. If you don't plan on accessing the data anytime soon, as 2blackbar suggested, LTO tape drive is the cheapest and safest solution.
Even tho a lot have been done concerning data integrity with overprovisioning, I wouldn't trust SSDs for archival. Flash charges dissipate and data recovery might be problematic because of proprietary firmwares, controllers, etc.

I'm cheap, I'd go for like 4 SAS hard drive in raid 10. I would mix brands (at least not the same batch) and go for slower 7200rpm drives.
I'd get the best PSU available for my budget (platinum/titanium like, anything more than 90% efficient at 100% load).
I'd get a reliable, brand new, consumer grade motherboard, a cheapo cpu, few gb of ram and an SAS HBA card which is quiet expensive and not always linux friendly (google-fu required).
Everything on a DIY clean and well ventilated cabinet install debian and barely touch it.
I think SAS drives are generally 10% more expensive but they are more resistant to vibrations. It's server grade, MTBF of SAS drives are 1.2 to 1.6 million hours of use at 45 °C and their SATA counterpart only 700,000 hours to 1.2 million hours of use at 25 °C.

For recovery, Ontrack seems to be a serious international company.

There's also cloud solutions, you can encrypt everything if needed.
LTO tape is cheap if it's several TB per months of archival otherwise it's not worth it. You can find fast LTO7 SAS drives (at least 300 Mbps) for something around £2,000 on ebay. A new 15 TB RW cartridge (30/45 TB of deduped/compressed storage) is around £60 .
If you take the hard drive route, there's also a raid backup open source software called SnapRAID.

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M
« on: December 20, 2019, 09:19:18 AM »
I don't know much about lcd screens but at first glance, the eos M and the eos M3 have physically different touchscreen connectors. Those are the small ribbons with a controller (which are probably different too).
For the display it seems to be 51 pins lvds for both (but you'd need the datasheet or probe them to check).

EOS M replacement parts

EOS M3 replacement parts

That would be a neat hardware mod for sure.

edit: it's probably possible to frankenstein a flippable original eos m screen, but having a bigger flippable touchscreen is way more challenging.
On most replacement parts, the digitizer seems to be based on a CY8CTMA340-LQI-11 from Cypress which only works with screens sizes up to 4.5” diagonal.
If you could find a touchscreen with the exact same connectors (I just realized that the flex's connector isn't a regular 51 pins btw), my guess is that the eos M firmware only provide this particular custom microcontroller's driver anyway.

Share Your Videos / Re: Thanksgiving Holiday
« on: December 12, 2019, 05:15:25 PM »
For my 2,5k footage, I export upscaled 4k prores 444 12 bits from MLVApp to Resolve. Once edited and denoised in Resolve, I export to dnxhr 444 12 bit and reencode to x264 crf 10 veryslow preset with ffmpeg or Handbrake before uploading to Youtube.
Some professionals upload in prores 444 12 bit but my upload speed is pretty damn slow and there's no point to upload past x264 crf 10 according to this chart from Blackmagic's forum. (SSIM is the structural similarity, 100 being similar to the source):

The result will be below crf 26 but providing a decent source helps. I should try 8k.

Share Your Videos / Re: Thanksgiving Holiday
« on: December 10, 2019, 09:24:59 AM »
From a technical standpoint colors are great, the grade is great, it's shot run and gun, the edit is great.
Maybe consider uploading in 4k just so you get a higher bitrate, I get better details this way (It's def less blocky on pans).
In my opinion, the best thing is that there is a little story, it isn't just b-rolls. It is a wholesome video really.
I ended up watching the whole thing without realizing it. Congrats.

Share Your Videos / Re: EOS M - A Walk In The Woods
« on: December 10, 2019, 08:45:24 AM »
Sorry for the late response. I'll keep this copyright problem in mind and put a mirror link next time.
I'm glad I shot enough footage to stitch something coherent.
I need to improve on the editing side and find the right pace, I always want to shorten the timeline... a couple days after I uploaded a video.
Thank you for your input, it's very nice of you.

Share Your Videos / EOS M - A Walk In The Woods
« on: December 02, 2019, 12:09:00 AM »
Canon EOS M with Magic Lantern. Canon EF-M 18-55 mm F/3.5-5.6 IS STM.
5k anamorphic preset, 1280x1606, 23,972 fps, 1/50s, 12 bit, iso 100.

It's pretty much straight out of MLVApp with the film preset and a white balance adjustement.
Some scenes stabilized in resolve like the first pan.

Pages: 1 2 [3] 4 5 6