Menu

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.

Show posts Menu

Messages - masc

#1
Raw Video Postprocessing / Re: ML RAW-tools for Linux
February 27, 2024, 07:34:47 PM
You can create receipts (kind of a profile) in MLVApp and apply it to all your footage, e.g. as default receipt.

You can resize to 8K in MLVApp, too.
#2
Haha... yes... found the problem! The file you downloaded is not a pixelmap - it has just the name of a pixelmap. You need to download using the "raw" button in github, else you get a webpage, maybe with the name of the file you wanted to load. In the end it looks MLVApp is kind of confused when trying to load this false pixel map.  :P :D If you open the files with any text editor, you'll see what I mean.
#3
Quote from: gabriielangel on February 19, 2024, 10:00:30 PM
Here is the complete file: https://bit.ly/3wk4LNU
Thanks.
Here also: no problems. I can open, auto download the map. Afterwards the clips is shown immediately and the focus dots are removed. Clicking focus pixel fix to OFF makes the dots visible.
macOS BigSur, Apple M1.
#4
Quote from: gabriielangel on February 19, 2024, 06:28:51 PM
Hello, I tested Danne's magiclantern-crop_mood.2024Feb18_Custom.EOSM202.zip and ran into the following issue:
MLVApp 1.14, official build.
OSX 10.13.6

If I load a clip I just recorded using the new 1920x1080p preset, without the focus pixel map installed, the clip opens fine (With the focus dots showing).

If I shutdown MLV APP, Install the new 80000331_1992x1109.fpm; when I launch the app and open any 1920x1080p clip, I get a beach ball and I need to force-quit (I'm on OSX).

If I launch the app again, but load a 2.8k clip this time, all is well.

If I shutdown MLVApp, remove the 80000331_1992x1109.fpm file, relaunch and load a 1920x1080p Clip, the clip opens fine again.

In any case, as long as I load any previously recorded clip at a resolution other 1920x1080p, it works without a problem.
Could you please upload this clip, or at least some frames of it? (In the "hope" this also happens for the shortend clip.)
#6
Resolve is known to not read and use those cDNG metadata - whyever. Stretch manually.

I don't have a 100D. Please send a MLV clip with just a few frames and I can try to create the map.
#7
MLVApp also stretches cDNG (by metadata). Probably your used NLE/viewer/... is not able to read cDNG metadata completely.
#8
Correct: you never saw the clip in the final size before export. (by standard.)
Wrong: the frame buffer is the same and the playback and editing is also the same speed. There is no reason making it faster. You must always process the entire picture first. The scaling is not that slow and viewer itself is by far faster than a video frame rate - at least on modern computers (you feel a big difference on Core2Duo). You can also drag the window to the "right size". Then you see the final size before export - if that is so important.
On encoding the entire sharpness changes anyways. Also with Davinci.
#9
It was an important design decission in the old days. And it was not easy to do this magic. We can change the labels if you like: first box is for anamorphic lenses, while second box is for digital ML stretch. If you were able to stretch width at 3.0x, you're forbidden to use anamorphic lenses at the same time, while 2nd box will probably never be used. There is also no 3.0x anamorphic lens (as far as I know), so this option doesn't exist. If we would downscale the height, you would never see the additional details in 1x3 footage over 3x3. If you however want to downscale for the export, use the export settings dialog. So I think there is nothing to fix - this is as it was intended to work.
#10
Quote from: Danne on January 21, 2024, 05:30:30 PM
Medium 1x3 2:1 1360x2040
Medium 1x3 2:20.1 1424x1942
Medium 1x3 2:35.1 1472x1878
Medium 1x3 2:39.1 1472x1846

Higher 1x3 2:35.1 1600x2040
Higher 1x3 2:39.1 1600x2008

Highest 1x3 2:20.1 1664x2268

Here those settings look good. I uploaded a pixelmap for each of these settings.

However I also found a problem, probably not related to the new stuff, but who knows:
Settings 1x1 FullRes. After selecting I get for less than a second the liveview I expected. Then it zooms in and has a horizontal line in the middle of the frame. When I try to record, it stops immediately. The MLV is 26.9MB but corrupted. Happens the same for you?
#11
The thread us about a custom EOSM build. And the corresponding pixel maps.
#12
@RhythmicEye: completely offtopic here - there is a MLVApp thread. But no, RAW stays RAW, no matter what processing you choose in MLVApp. RAW corrections can be exported into RAW.
#13
Quote from: Danne on January 22, 2024, 03:27:17 PM
Yeah, and one can check width and height with mlv_dump -v drag/mlv/file/here and check exactly what is going on.
You can also check with MLVApp:
#14
Ah okay.
Use these maps:
1376x2322 - 80000331_1448x2351.fpm
1736x2178 - 80000331_1808x2207.fpm
1736x3478 - 80000331_1808x3507.fpm
1736x2214 - 80000331_1808x2243.fpm

Note: some of Bilals original presets had a red line on the bottom. Danne fixed this for many modes. For each fix another map is needed now, even if you don't notice a change in resolution. If you can use (compile or download (with github account)) the latest commit version of MLVApp, the focus pixel map dialog shows which map is needed, if you did not install it.
#15
Played with the new presets (so many, probably not all):

1736x2178 -> no problem
1736x2322 -> how to get that? I just get 1664x2268, which should be same AR. This one has a red line at the bottom.
1504x2538 -> new map uploaded
1736x3478 -> no problem
2880x1206 -> new map uploaded

1736x738: works fine
1736x726: works fine

Edit: 1736x2322 has 2.24:1 AR. Can't reproduce that. Is there a typo?
#16
Raw Video / Re: MLV Raw audio and Datarates
January 17, 2024, 10:38:11 PM
Audio is so little data, I don't think it is worth it:

48000kHz*2(channels)*2(Byte)/1024/1024 = 0,183MB/s

If you remember at what data rates we record the video part, the audio data rate is just nothing.
#17
@kob: Uncheck Audio Output from Playback menu.
#18
Quote from: mlrocks on November 24, 2023, 08:31:55 PM
thank you, masc. probably this is why mlvapp has better color than resolve free version.
Good color has also other reasons than just a bitdepth. Low bitdepth might bring banding into the footage.
#19
MLVApp is 16bit, DualISO 20bit.
#20
Quote from: Teamsleepkid on November 06, 2023, 07:16:24 AM
Can you output to prores raw? Would be kinda cool..
No problem, if there is a library (best C/C++) which supports encoding. I did not hear about one yet.
#21
If someone knows how lensfun library works in detail, I'd really like to add this directly to MLVApp. Until now the docs were too hard for me :P
#22
Interesting. But some questions for this:
- does Lensfun understand "EOS M" + a "16mm" lens at focal length 18?
- did you check the export if distortions are correct after export?
- you used a speedbooster? This adds additional distortion. The export is really correct?
- did you use a ML setting with full sensor? At least full sensor width? Is the vertically used area exactly centered? Otherwise this also should not work, I bet.

If you use the post export scripts, you could delete files after processing. So MLVApp pipes to a first intermediate export file. Then the script is started, does the additional stuff and deletes the first file. So the needed disk space should not be much.
#23
If you're on macOS (and maybe on Linux, not exactly sure here, as I almost never load it on Linux) you are able to create "post export scripts" which can be driven right after export. You could do a script which does this job.
In MLVApp code you can also change the ffmpeg command. That is a little complicated because there are hundreds of combined options. See function startExportPipe in MainWindow. I think it will be hard to use such a correction via ffmpeg, as you can't see what you'll get after exporting. The parameters change with zoom focal lengths, with crops, pans, etc. ... finding the correct parameters for each clip should be very very hard.
#24
Nice to hear your build works.

Focus pixel map installation can't work for appImages, because those images are readonly. See in-app-help or wiki:
https://github.com/ilia3101/MLV-App/wiki#fix-focus-dots

Autostretching for exported DNG should work. I guess you tested with Davinci Resolve, which should be one of a few (or the one and only) application not reading the stretch factors from DNG files.