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 ... 46
1
Camera-specific discussion / Re: Canon EOS M
« on: Yesterday at 09:37:21 PM »
Correct. It is auto when preparing, but is fixed while recording.

2
Camera-specific discussion / Re: Canon EOS M
« on: Yesterday at 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

3
Camera-specific discussion / Re: Canon EOS M
« on: Yesterday at 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?!

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

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

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

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

8
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. (https://bugreports.qt.io/browse/QTBUG-74655)

9
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.

10
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 MLVApp.pro ... Windows version is defined with "win32" there. I really wonder how this works with Win64 crosscompiler on Linux.

11
Camera-specific discussion / Re: Canon EOS M
« on: July 16, 2019, 08:22:18 PM »
Yes, right. It works too good in MCM rewire mode. Only for x10zoom it doesn't.

12
Camera-specific discussion / Re: Canon EOS M
« on: July 16, 2019, 08:14:01 PM »
One finding with July16 version: focus aid gets very bright when active, sometimes too bright (all white). When releasing halfshutter normal preview is also too bright, but after a second it normaizes again. Tested in MCM rewire.
Edit: moaaah... found it. Auto-ISO is the reason.

13
Share Your Videos / La Palma Island - with EOS 5D2 and EOS M
« on: July 16, 2019, 07:49:41 PM »
Some weeks ago I traveled with my two EOS cams to the Island La Palma. Here is my final short holiday film - made from over 450GB of MLV files.

14
Camera-specific discussion / Re: ML on EOS-M2
« on: July 16, 2019, 07:32:19 PM »
Been trying to compile this but getting errors about undefined references to min/max in amaze_demosaic.c and others too. Following the instructions at GitHub for compiling on windows. I'll keep trying. Thank you.
Normally this should work out of the box as described. Could you please post the compiler error message, then I'll have a look. What Qt and MinGW version do you use? But maybe better post into MLVApp thread, because it is a bit off-topic here.
https://www.magiclantern.fm/forum/index.php?topic=20025

15
Camera-specific discussion / Re: ML on EOS-M2
« on: July 16, 2019, 06:41:57 PM »
To use this change, download sources and compile. The next official release ( v1.8 ) will include it too.

16
Camera-specific discussion / Re: ML on EOS-M2
« on: July 16, 2019, 02:15:23 PM »
I extracted the color matrix values from the cr2 file and included them into MLVApp. Now "Use camera matrix" should bring correct color.

17
Camera-specific discussion / Re: Canon EOS M
« on: July 15, 2019, 08:13:16 PM »
Do we need this for other cams? The DSLRs have a "+" button to toggle...

18
Camera-specific discussion / Re: ML on EOS-M2
« on: July 15, 2019, 07:58:32 PM »
Thank you.

19
Camera-specific discussion / Re: Canon EOS M
« on: July 15, 2019, 07:47:28 PM »
I like the idea's. I used the shutter key solution this weekend and accidentelly full pressed sometimes. This leaded 50% to frozen cam. This can't happen now.

20
Camera-specific discussion / Re: ML on EOS-M2
« on: July 15, 2019, 07:07:24 PM »
Glad to help...what's the best way to upload?
Use any filehoster... dropbox and friends...

21
You can apply the LUTs in MLVApp before exporting or in Premiere. Make sure to setup the input profile correctly.

22
Camera-specific discussion / Re: ML on EOS-M2
« on: July 15, 2019, 02:56:58 PM »
Could someone who owns a M2 please record a .cr2 picture and upload? I would like to read out camera matrix values from the file and check if my assumption was correct.

24
So is better to use a grey card in the scene, like a clapper o colorchecker , so that WB can be adjusted using the drop eye tool withing MLV App.
This should work without problems. Film the grey card, set WB in MLVApp, copy just WB, paste on the clips of that scene, ready.

25
@JADURCA:
Totally agree.
MLVApp reads the manually set WB settings from MLV files. They should be there, if you use anything else than "AWB". It should also work for the "K" mode, I think I tested that in past. I did not test the grey card mode, so I can't tell if that works too.
Edit: no success for greycard mode. But "K" mode works as expected.

Pages: [1] 2 3 ... 46