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 - Milk and Coffee

Pages: [1] 2 3 4
1
A few questions on exporting in MLV app.

Gear: 5D2 and reddeercity's latest Crop_rec build.

My goal is to get a file in a log gamma, as if it came straight out of camera that shoots log.

I have read the wiki here on export settings: https://github.com/ilia3101/MLV-App/wiki#export-settings

Heres the scenario,
-I import an MLV. I leave exposure alone, even if it was under/over exposed. I only adjust white balance if needed.
-Under "profiles" I select the "BMD Film" preset. (Does anyone have a suggestion of a "tonemapping" and "processing gamut" combination?)
-I leave "Allow Creative Adjustments" disabled.
-I leave "Gamma" set to "1.00"

Question 1: I kind of understand what the options under "Camera Matrix" do. But am still a little fuzzy. What are the benefits to "Use Camera Matrix" vs "Don't Use Camera Matrix"?
Question 2: Does leaving "Gamma" set to "1.00" basically mean MLV App won't make any adjustments? How is this different than using the exposure slider? What are the benefits to this adjustment?
Question 3: When selecting "Apple ProRes 4444," which "ffmpeg" selection should I select of the options? Options are "ffmpeg Kostya," "ffmpeg Anatolyi," and "Apple AVFoundation." What are the benefits?

Thanks all!

2
I tested the new mlv_rec module "1880_3x3-2152_5xZoom-5d2+50d-support__7-5-2020-5.59pm-mlv_rec.zip" with the latest "crop_rec-5632x3124_3.8fps-5D2-eXperimental.9.42pm.2020Jan05.5D2212.zip" build. I'm loving the new 3x3 resolution!

mlv_play isn't working and causes no modules to load.

Any way to fix this easily?

Thanks again for your continued development!

Is there a way to get the 1880 res in the 5D2 nightly build?

3
I like the google docs idea!

4
That’s pretty cool! Thanks masc!

5
When exporting .MLV using "CinemaDNG fastpass:" if the .MLV was recorded with lossless compression, does "CinemaDNG Fastpass" export CinemaDNG Lossless?

6
My histogram only reports 11.2 stops DR in MLV at ISO 100 (5D2.) Is there something I’m missing? Do I need to enable something?

7
Raw Video Postprocessing / Re: DaVinci Resolve 12 and ML Raw
« on: July 20, 2020, 06:47:36 PM »


I think a color picker in the "Camera RAW" panel would provide better results, since it would be at the first, debayering stage of processing.

8
Thanks for all the useful replies! So it sounds like it’s an issue with Davinci resolve. Hope they are still updating their cDNG functionality now with all the other raw formats out there.

9
I appreciate all the reply’s, and grading suggestions! Maybe I didn’t clarify enough: The DNG is a sample to demonstrate the pink pixels in the sun. I didn’t shoot it with intentions of using it. 

Seems to be a bug with Davinci? Or with ML? Didn’t know if anyone had any insight as to why they are appearing.

70MM13, did you notice the pink pixels?

10
Thanks for taking the time! It was just a quick clip from my apartment patio. I intentionally overexposed to make sure the pink highlights would show in Davinci.

Your graded image looks great! Good highlight roll off!

Any Davinci users that can shed some light on the pink pixels happening in Davinci?

11
Can't help without the original  dng/mlv file shorten  , not jpeg compression (lossless) or png .
just use passthou when exporting dng's in mlv app. and it will export dng's at the original bit depth
Did you try Adobe ACR ? (Photoshop/After Effects)

New sample DNG's here (included both uncompressed/passthrough, and lossless compressed) http://www.mediafire.com/folder/lelofkxvrvyhw/Pink-Sun

Different clip, but same problem; pink pixels in the center of the sun in Davinci Resolve. It's especially apparent with "highlight recovery" turned on.

12
Oh! I thought you meant JPEG as a file type. Let me shoot another test as I don’t have the original mlv. Or can I make another uncompressed DNG from this one?

15
Reddeercity, thanks again for all your hard work on this! I tested the new mlv_rec module "1880_3x3-2152_5xZoom-5d2+50d-support__7-5-2020-5.59pm-mlv_rec.zip" with the latest "crop_rec-5632x3124_3.8fps-5D2-eXperimental.9.42pm.2020Jan05.5D2212.zip" build. I'm loving the new 3x3 resolution!

I noted four things for the 5D2:
1) In 3x3 1880, and in all bit depths, I'm getting pink spots in the sun, see .dng here > https://www.mediafire.com/view/ssal2p12hvreadi/C-12-BIT-111.dng/file Is this something that needs to be repaired in MLV app?
2) In live view movie mode, ML reports 1/48s shutter speed, but the top LCD of my 5D2 reports 1/90s. And when switching out of live view, and capturing a still, it is captured at 1/90s.
3) Forgive me if you've already addressed this, but the fastest shutter speed I can achieve in mlv_rec (3x3 1880) is 1/100s despite the top LCD reporting all shutter speeds up to the max 1/4000s.
4) mlv_play isn't working and causes no modules to load.

Thanks again for your continued development!

16
@Reddeercity, thanks so much! I'll get to testing straight away!

17
General Help Q&A / Re: Why I can´t increase resolution
« on: July 04, 2020, 10:10:30 PM »
Did you see black borders in my DNG? Or you mean in your own files?

18
Raw Video / Re: How to check if a .DNG is really raw data
« on: July 01, 2020, 02:18:34 AM »
Thank you masc! Then I would suspect that’s why exif is showing JPEG for both.

19
Raw Video / Re: RAW liveview on PC monitor via USB
« on: July 01, 2020, 02:15:30 AM »
I’m having an issue here too. I don’t have an external monitor, and would like to view self shot MLV RAW interviews via usb. Any updates on this?

20
Raw Video / Re: How to check if a .DNG is really raw data
« on: June 30, 2020, 12:40:34 AM »
That is weird! Doesn't ML use a JPEG compression method for making lossless RAW? Is MLV App using it too for lossless DNG? I see that when I open both in ACR, the "JPEG DNG" doesn't show Adobe's RAW profiles in the drop down. Whereas, the second DNG I posted (should be real RAW) DOES have Adobe's RAW profiles available.

21
Raw Video / Re: How to check if a .DNG is really raw data
« on: June 29, 2020, 02:11:15 AM »
So I asked my coworker what his original workflow was. Originally, I asked him to deliver a DNG sequence. He exported a JPG sequence with adjustments from ACR because he felt the DNG's looked "dark." (Probably because the DNG's are previewed in linear gamma on mac?) He then batch converted the adjusted JPGs back to DNG. (He obviously doesn't know the benefits of RAW)

I hate that DNGs can hold raster images. Now ill be skeptical if I'm receiving RAW data or not. :-\

Anyway, after some talking I asked for the original DNG sequence. Below is the original RAW DNG from Canon 5D2. (File size is larger, but still 740kb.)
https://www.mediafire.com/view/lzsxznzy1aq8fjy/M24-2054_1_2020-06-24_0001_C0000_000155.dng/file


22
Raw Video / Re: How to check if a .DNG is really raw data
« on: June 28, 2020, 08:24:38 PM »
Use exiftool or what has already been recommended.
Dng can be lossless raw or even some lossy jpg turned into dng. Too bad you don't take the time to share samples.

Sorry about the late reply! Here is a frame from that sequence!
https://www.mediafire.com/view/ve4pxi7gbd1wtra/M24-2054_1_2020-06-24_0001_C0000_000155.dng/file

23
General Help Q&A / Re: Why I can´t increase resolution
« on: June 28, 2020, 08:10:56 PM »
Just curious, but 1880 should technically be 8 pixels too much, 1872 pixels should be available.
So if you look real close, pixel peeping, you probably detect a very small border on the left or right, which exists out 8 pixels wide black border.

Just did a test. 5D2, 10/12bit build

Via MLV_lite, at 1880, I did a shot of blue sky, wide open 50mm lens, focused as close as I could. No black borders for me anywhere!
Original DNG here https://www.mediafire.com/view/3e3l87lr0akvjkh/M27-1926_000080.dng/file

And then some pixel peeping screenshots of the sky linked below.  :)
Top left: https://www.mediafire.com/view/5pui0n2fmvzn1vq/Screen_Shot_2020-06-28_at_11.52.16_AM.png/file
Bottom left: https://www.mediafire.com/view/f6m3hciq32s6gsp/Screen_Shot_2020-06-28_at_11.52.05_AM.png/file
Top right: https://www.mediafire.com/view/3woavny8mjs45k9/Screen_Shot_2020-06-28_at_11.51.44_AM.png/file
Bottom right: https://www.mediafire.com/view/jhs201hbgpiy3bg/Screen_Shot_2020-06-28_at_11.51.54_AM.png/file

24
General Help Q&A / Re: Is MLV using the full width of the sensor?
« on: June 28, 2020, 08:03:34 PM »
@Levas , I have a 5D2 and yes a cr2 is 5616 but the FRSP is 5632 , and there must be some padding in canon firmware .
Also I check the Image dump from my 5D2 & 3x3 raw image is indeed 1880 not 1872 or 1877 as I said ,
there's 3 pixel from somewhere , maybe some padding ?
In the zip file there is 3 files the 3x3 ml raw dump , DNG ,  the converted dng ->.ppm file from exiftool & the converted .ppm -> .png
5D2_True_3x3__Sensor_Size_5-12-2020.zip
Code: [Select]
File Name                       : RAW-001.DNG
Camera Model Name               : Canon EOS 5D Mark II
Software                        : Magic Lantern
Subfile Type                    : Full-resolution Image
Image Width                     : 2040
Image Height                    : 1268
Strip Offsets                   : 33792
Samples Per Pixel               : 1
Rows Per Strip                  : 1268
Strip Byte Counts               : 4526760
X Resolution                    : 180
Y Resolution                    : 180
Default Crop Origin             : 0 0
Default Crop Size               : 1880 1250
Active Area                     : 18 160 1268 2040
Image Size                      : 2040x1268
So if you pixel peep there no missing pixels that I can see .

In the Old Raw_Rec module (pre-2016) We had 1880 wide , before the speed penalty was found in D5 cam .

Found a CR2 and
Code: [Select]
Record Mode                     : CR2
Canon Image Type                : Canon EOS 5D Mark II
Canon Image Width               : 5616
Canon Image Height              : 3744
Raw Jpg Size                    : Large
Cropped Image Width             : 5616
Cropped Image Height            : 3744
Sensor Width                    : 5792
Sensor Height                   : 3804
Sensor Left Border              : 168
Sensor Top Border               : 56
Sensor Right Border             : 5783
Sensor Bottom Border            : 3799
Color Data Version              : 6 (50D/5DmkII)
Exif Image Width                : 5616
Exif Image Height               : 3744
Image Size                      : 5616x3744
Important info about Sensor
Cropped Image Width             : 5616
Cropped Image Height            : 3744
Sensor Width                         : 5792
Sensor Height                        : 3804
Sensor Left Border                 : 168
Sensor Top Border                 : 56
Sensor Right Border               : 5783
Sensor Bottom Border            : 3799

Magic Lantern uses less of a off set 160 compared to canon's 168 and the vertical canon does 58 where ML uses 18 offset
Also I did a OB Zone test here and it's 1880 so
mainly a coding issue . With Crop_Rec it's really a non issue now , with 1x3 , 3x1 etc. ....  :)

Just curious, but 1880 should technically be 8 pixels too much, 1872 pixels should be available.
So if you look real close, pixel peeping, you probably detect a very small border on the left or right, which exists out 8 pixels wide black border.

Just did a test. 5D2, 10/12bit build

I shot on a tripod, same exposure, lens, etc. Nothing changed but the MLV module.

MLV_rec has a maximum 3x3 resolution width of 1856px.
Original DNG here https://www.mediafire.com/view/6ziy3e7ajobq6we/mlv_rec-1856.dng/file

MLV_lite has a maximum 3x3 resolution width of 1880px.
Original DNG here https://www.mediafire.com/view/taqdx0kfihpvv6a/mlv_lite-1880.dng/file

Looks like the image offset has pixels missing on the right in mlv_rec.
See comparison here https://www.mediafire.com/view/xb7b6yy15k4tkzi/LITE-REC-Comparison.png/file

mlv_lite looks like image offsets are set correctly!

Via MLV_lite, at 1880, I did a shot of blue sky, wide open 50mm lens, focused as close as I could. No black borders for me anywhere! This is cool!
Original DNG here https://www.mediafire.com/view/3e3l87lr0akvjkh/M27-1926_000080.dng/file

And then some pixel peeping screenshots of the sky linked below.  :)
Top left: https://www.mediafire.com/view/5pui0n2fmvzn1vq/Screen_Shot_2020-06-28_at_11.52.16_AM.png/file
Bottom left: https://www.mediafire.com/view/f6m3hciq32s6gsp/Screen_Shot_2020-06-28_at_11.52.05_AM.png/file
Top right: https://www.mediafire.com/view/3woavny8mjs45k9/Screen_Shot_2020-06-28_at_11.51.44_AM.png/file
Bottom right: https://www.mediafire.com/view/jhs201hbgpiy3bg/Screen_Shot_2020-06-28_at_11.51.54_AM.png/file

25
No, this is not possible.It can lead to problems with proxy workflows: because the naming might be different, linking could fail."Fast Pass" leaves picture data untouched, while "uncompressed" force exports to uncompressed cDNG where also RAW corrections are applied.

Thanks masc!

1A. So If I don't use a proxy workflow, renaming cDNG sequences after exporting should work fine? There are no cDNG metadata issues with that?
2. To clarify, a "Fast Pass" cDNG export will not include ANY adjustments from the panels?

Pages: [1] 2 3 4