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 - masc

Pages: [1] 2 3 ... 47
Wasn't just me. Thanks also to Ilia, Bouncyball, Escho, Rewind, Danne, and many more...

Camera-specific discussion / Re: Canon EOS M
« on: Yesterday at 10:48:56 PM »
x3zoom works with trashcan. x10zoom with halfshutter.

MLVApp v1.8 is out now! New in v1.8:
- Added vignette shape slider
- Added chromatic abberation correction
- Added export preset list (to save your own presets)
- Added a third interpolation method for focus and bad pixels (thanks to Rewind)
- Added more support for EOS M2 (focus pixel fix and camera matrix)
- Faster WB picker
- Scopes are resizeable now
- Some bug fixes and some minor changes

Camera-specific discussion / Re: Canon EOS M
« on: July 19, 2019, 08:57:51 PM »
Okay... no, haven't see this so far.

Camera-specific discussion / Re: Canon EOS M
« on: July 19, 2019, 08:39:28 PM »
With this maxIso thing it seems to work. Tried 2 clips, OFF->ISO3200 (shown in liveview and in clip) and ON->ISO800 (in both).
But if I remember right, I saw that in past - the liveview showed e.g. ISO800 and it was ISO640 or something. It seems it shows just the 100,200,400,800,1600,3200,6400 in liveview. Is it that what you mean?

Camera-specific discussion / Re: Canon EOS M
« on: July 19, 2019, 07:22:53 PM »
New version:

- x10 focus aid working with autoiso set

What can I say. a1ex(ML) code includes so much functions to play around with...
So good Danne! Thank you! AND: AutoISO now works also in 5K anamorphic! MaxISO @800 is also a great addition! So many great new stuff again and again! ;)

Camera-specific discussion / Re: Canon EOS M
« on: July 19, 2019, 12:52:27 PM »
I've never seen something like this before. But with "Pattern noise" in MLVApp the stripes go away. On the other side, Pattern Noise brings "funny" textures...

Share Your Videos / Re: La Palma Island - with EOS 5D2 and EOS M
« on: July 19, 2019, 12:03:01 PM »
Thanks. Well... maybe not hardcore, but at least hard enough for me, hehe.
Yes, I like 25fps over 24fps, because many german TVs (at least the ones at my familiy and friends) seem to work at 25fps (PAL?!). If I watch a 24fps video, it stucks once a second (looks like the 24th frame is shown twice).
Yepp, I have two ProRes renderings. But it is not really redundant. The first one is without any change - just 1:1 standard settings. Like that the export is fast (okay, with MLVApp it will never be turbo fast, but 450GB were ready in around 12h overnight). The second rendering includes all corrections and grading settings, linear gradients, lens corrections etc.. So this rendering is way slower, but I only work with the used clips and I only export those clips. So this needed less time than the first rendering. Additionally, cutting with ProRes Proxy files works very fluffy - also on old computers like mine. Those ProRes Proxy files are not too big on the HDD.

Thank you, Ilia. For some of the clips I used a fixed ND filter, for other clips a variable ND filter. If you turn the whole variable ND filter you can use it very well as polarizer (well right, it is one... no... two) :)
I copied all my MLVs in one folder, so it is hard to find out now. I am sure with these clips, being from the EOS M (+Kitlens): 4:50, 5:35, 5:38, 6:17, 6:40. I think the were much more before...

It's not useless @masc. The processor inside those cameras cannot do complex debayering like we have in MLVApp (AMaZE) in realtime. You know that much better than me, you're the primary developer of mlvapp.
This is indeed absolutely right. But the discussion was more about color up to my post.

I really wanna see a comparison, sounds so weird to me that colours are better with apple encoder. There must be a way to configure ffmpeg to be equal if it is not.
The most differences are on saturated green and tones. Just render a clip twice (AV+ffmpeg) and compare. If it is just bt709 vs bt2020: this is solvable in ffmpeg. The difference is very small!!! On the other side: AVFoundation encodes with 12bit and ffmpeg with 10bit... but hey: if MLVApp is the last grading step, even 8bit would be enough.

Camera-specific discussion / Re: ML on EOS-M2
« on: July 18, 2019, 04:19:41 PM »
RE: focus pixel maps. Does the resolution of the map have to match the resolution of the footage? I cannot shoot at anywhere close to the image sizes listed for the fpms...
No, the resolution of the map has to match the resolution from RAWI block. You can read this size with mlv_dump:

mlv_dump -v your.mlv > some_file.txt

then find block RAWI (example):
Block: RAWI
height yyyy
width xxxx

Or just install all files for your camera.

Camera-specific discussion / Re: ML on EOS-M2
« on: July 18, 2019, 03:33:48 PM »
...I've seen the zip download for the pixel maps. Exactly how do I utilize them in MLVapp?  ...
Unpack, select maps for your camera, drop them on MLVApp, reload your clip and activate focus pixel fix.

Share Your Videos / Re: La Palma Island - with EOS 5D2 and EOS M
« on: July 18, 2019, 02:23:56 PM »
Yes... anamorphic is so good. But I wanted to record 16:9 and anamorphic is best in 2.35:1 IMO (this means, I like it most in this ratio, because of the horizontal resolution).

Share Your Videos / Re: La Palma Island - with EOS 5D2 and EOS M
« on: July 18, 2019, 11:35:32 AM »
Hehe, thanks.
All the steady shots are from the 5D2 (so indeed most shots), because I only got the 5D2 balanced without problem (EOS M is sooo lightweight). Both cams bring aliasing, the EOS M a bit more. The slowmo water clip is from EOS M, 5D2 is not able to do this in a good 3x3 16:9 setup. The non-wideangle shots with slight movement are from EOS M, because I had an IS lens for the EOS M only.
I used in both cams 14bit, the EOS M footage was lossless, the 5D2 footage was uncompressed. It was no problem to make both cameras look more or less the same.

Yepp, color is better when exporting with AVFoundation ProRes 4444. On the other side, if you have to stretch/resize the footage, AVFoundation is not able to do it and doing it in FCPX looks worse than with ffmpeg. So you'll have to decide between color vs. sharpness. ;)

... and any program like Adobe After Effect & Balckmagic Resolve will read them
correctly without having to manually stretching ...
Unfortunately Resolve is not able to read the metadata (at least up to v15.x, did not try v16). You have to strech manually in Resolve. But no big deal.

Camera-specific discussion / Re: Canon EOS M
« on: July 17, 2019, 09:37:21 PM »
Correct. It is auto when preparing, but is fixed while recording.

Camera-specific discussion / Re: Canon EOS M
« on: July 17, 2019, 09:20:20 PM »
AutoISO was just a joke. Okay, interesting. Nice tool.
I had never an issue with AutoISO in MCM rewire regarding bad footage... so I use it here and there. But some features in camera don't like it, as we see  ;D

Camera-specific discussion / Re: Canon EOS M
« on: July 17, 2019, 08:48:18 PM »
Tried your new darkmode. Works fine here. How is it done? Activating Auto-ISO? :P muhaha. When activating the zoom, preview framerate seems to be lower than normal... looks like ~10fps?!

Thanks for the feedback. Nice to hear it works. I also could fix the size of the dock label font now.

How to unstretch in post 4k squeezed footage?
Load into MLVApp, streching is done automatically. Or use Resolve and stretch 300% manually vertically.

Thanks Danne. This explains, why the Ektar LUTs look best with Cineon profile in MLVApp.

Okay. ML-Log is not supported by MLVApp, so you'll have to do it "post-MLVApp". Btw: how is ML-Log defined? Is there e.g. a LinearToMlLog LUT? Maybe we could add it as profile in MLVApp...

Did a quick change for the MIN MAX problem. I can compile here with MinGW64 now. Please check out and try to compile again (@jonkjon).

Edit: Qt >=5.12 has a bug, where icons in menus are wrong. And font-sizes in docks are wrong too. So... here we can't do anything. Wait until Qt fixes and live with it as is, or use an older version of Qt. In Qt 5.9.2 I did not see any GUI bugs, but there is no offical 64bit build.
Menu icon bug will be fixed in Qt 5.12.5 and 5.13.1, Qt plans 27. august 2019 and 15. august 2019. (

Share Your Videos / Re: La Palma Island - with EOS 5D2 and EOS M
« on: July 16, 2019, 10:31:11 PM »
Thanks guys. Yes, all is graded in MLVApp only. Here my workflow:

1. MLVApp:
- import all MLV files
- export all clips as ProRes 422 Proxy (small and fast for cutting)
2. FCPX:
- Cut the project
- Export FCPXML
3. MLVApp:
- import FCPXML
-> the session includes only the used clips
-> correct/grade colors only in used clips
- export clips as ProRes 4444 (best quality for final)
4. FCPX:
- select all clips in media pool
- relink these files with the graded files (FCPX just relinks the graded ones)
-> now the project has the correct color
- set project to ProRes 4444
- export project
5. ffmpeg:
- upscale to 4K using lanczos algorithm for better youtube quality

That should be it.

Ah okay... you use 64bit MinGW. I never tried that. And bouncyball cross compiled the windows 64bit version using Linux. I always compiled with 32bit MinGW version, because it was the only compiler until last Qt version, if I remember right.

In these files (the compiler tells) you'll find some defines "#ifdef/ifndef WIN32". I bet this is the problem. We should find a define for 32bit and 64bit at the same time. No idea if Q_OS_WIN would do the jub (it would in c++ part, but not sure if also in C part of the app).

Edit: puh... the problem starts already in project file ... Windows version is defined with "win32" there. I really wonder how this works with Win64 crosscompiler on Linux.

Pages: [1] 2 3 ... 47