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 - 6D_ML

#1
Quote from: dfort on November 18, 2018, 06:34:54 AM
Yes, I successfully rolled back from 1.3.5 to 1.2.3 and to and from several other versions...
Excellent! Thanks a lot for confirmation.
#2
I'm considering purchasing 5D mkIII and installing ML. Did anyone successfully roll back firmware v1.3.5 to v1.2.3? Should I stay away from 5DmkIII running on FW 1.3.5?
#3
Thanks for your reply A1ex. Lightroom renders files the way I described above. RawTherapee produces results very similar to yours with no difference.
#4
Quote from: a1ex on December 27, 2017, 07:27:29 AM
Is the color shift visible with mlv_dump?

Managed to extract a DNG (download link) with mlv_dump default conversion (mlv_dump --dng myfile.mlv). The color shift is there, and I'd rate its severity between results produced by "batch_mlv_in-out" (best) and "MVL App" (worst). There is also the highest level of blue hue present in clipped blacks with mlv_dump. Hopefully, devs can tackle the color shift issue with 10bit files. I can help so far with feedback only.

Quote from: dfort on December 28, 2017, 04:29:37 PM
If you use the "official" crop_rec_4k mlv_dump you can skip the "-b 14" option because it will save to 14 bit by default:
mlv_dump --dng <inputfile>

dfort, thanks for the tip. In my case I had to use the following cmd syntax to extract DNGs:
root_path_to\mlv_dump --dng root_path_to\MLVfile.mlv
#5
Quote from: a1ex on December 28, 2017, 07:24:37 AM
Not sure what "option 15" is, and the EXIF info in the DNG says Adobe Photoshop Lightroom, so I couldn't tell whether you were using the right version - try the command-line mlv_dump from the Experiments page.

I used batch_mlv_in-out to output 10bit DNG above. I need to read a manual for command-line mlv_dump before I make it output DNGs ::)
#6
Quote from: a1ex on December 27, 2017, 07:27:29 AM
Is the color shift visible with mlv_dump?
With mlv_dump (option 15), 10bit DNGs are identical to those produced by MLV App (color shift visible)

Quote from: a1ex on December 27, 2017, 07:27:29 AM
If using other converter, is it following this recommendation? (if not, you know where you have to report the issue)
I couldn't check black level with mlv_dump since "-v" is not listed as an option, and it doesn't do any operation. What did the trick to remedy the color shift in 10 bit files is the option 4 (converting image data to 14 bit depth per channel).


Download 10bit DNG interpreted as 14bit



Download 10bit DNG

#7
Feature Requests / Re: Digital Dolly Speed Config
December 27, 2017, 04:24:58 AM
I'm interested in a digital dolly speed adjustment feature for video shooting as well.
#8
Quote from: dfort on December 23, 2017, 04:49:34 PM
Of course you should also compare 10bit raw against 8bit H.264.

I did. In case of 6D, while detail and dynamic range are noticeably higher in 10 bit RAW, 8bit H.264 file has an edge with a relatively "consistent and accurate" color, whereas 12/10bit file gets polluted with a green & yellow cast in blacks/shadows. This temperature/tint difference is also noticeable between 14 bit (best IQ results) and 12/10 bit files. Has anyone noticed similar temp/tint shifts with other models?
#9
Here is an example clearly demonstrating the difference in quality between 10 & 14 bit recording after raising blacks & shadows in post: http://www.magiclantern.fm/forum/index.php?topic=5601.msg195034#msg195034
#10
Quote from: dariSSight on December 22, 2017, 10:03:14 PM
@6D_ML which build are you using and is there a 5D2 build?
Build 33: http://builds.magiclantern.fm/jenkins/view/Experiments/job/raw_video_10bit_12bit/33/. It looks like 5D2 is not supported yet.
#11
Here is my take on comparing 10bit vs 14bit on 6D*1.1.6 Build 33.

mlv_rec module for recording RAW video (1.00x crop). →  MLV files converted into cinemaDNG (lossless) with MLV App v0.12 alpha. → DNGs to JPGs in LR 6.5. JPG conversion settings should be embedded in DNGs.

Expo settings: 1/30s, iso100, 30fps.
Image Fine-tuning:
ML Digital ISO: 0.0 EV
Black Level: 0
Shutter fine-tuning: +39 units

WB adjusted in ML EXPO tab (Auto adjust Kelvin + G/M) for 14-bit recording and remained fixed for 10bit mode. 
Click on thumb for full size JPG.


14bit / 30fps
Download DNG (https://drive.google.com/file/d/1JBd0B8n2QC-RHZ6hJaJiKvnxci4z12Ax/view?usp=sharing)


10bit / 30fps
Download DNG (https://drive.google.com/open?id=1R_mGzLH2k-4JgNHhEx-AqQl2dCopJTD-)

Is there a flaw in the above workflow or a 10-bit raw footage is not very forgiving for raising blacks and shadows compared to a 14-bit file for such a scene?
I've also shot less contrasty scenes that didn't require much shadows/blacks pushing in post, and 10/14bit footage looks indistinguishable, unless you start pixel peeping at 200%+ zoom level.

Also, I noticed that in Build 33, when I set in Pref tab, "ISO/Kelvin" - ON and "Use Set button" - ON, they do not appear in LV before or during recording. Pressing UP/DOWN/SET buttons does not change anything.
#12
Quote from: dfort on December 18, 2017, 06:40:24 PM
Looks like the 6D is up and running properly. Thanks @6D_ML for the excellent bug reporting and following a1ex's instructions.

I did not expect  A1ex to release those last builds so quickly, and I lagged behind with the testing. Well done A1ex!
So far, great results for 6D video shooters:
Continuous 10-bit RAW recording 1728x724 (1.05x) @ 23.976 fps with sound.
Continuous 10-bit  RAW recording in crop mode 1920x720 (2.85x) @ 23.976 fps with sound.

Live liew during crop mode video recording does not work yet in 10/12-bit mode.
#13
Quote from: a1ex on December 18, 2017, 06:06:25 AM
Both RAM dumps were taken under the same conditions, right? (same shutter speed, same video mode etc)

Found another set of addresses, not an exact match (likely because the RAM dumps were not taken at the same shutter speeds), but let's try that one as well (build #33). If that doesn't work, please send me a ROM dump from that build as well.
Build #33 allows for shutter speed changes now! PM with ROM files sent.
#14
Quote from: a1ex on December 17, 2017, 11:38:14 PM
Fix pushed (issue confirmed in QEMU, but could not test the actual behavior). Please try build #32.
Tried Build #32. The issue persists, but now the shutter speed value is equal to 360° of the selected FPS. Here's a screenshot for 1920/30FPS:

#15
Quote from: a1ex on December 17, 2017, 10:10:27 PM
Can you run the same tests on the latest build (#31) ?
Build# 31 still has the same shutter speed issue. The stuck value is different though:



Quote from: a1ex on December 17, 2017, 10:10:27 PM
BTW, I see ISO is set to Auto. Are you in M mode?
Indeed, it was M mode with autoISO, but switching to Av, Tv, P modes does not remedy stuck SS values.

Quote from: a1ex on December 17, 2017, 10:10:27 PM
edit: I might remember something; please PM me a RAM dump (Debug -> Dump ROM and RAM, from both #22 and #31).
PM sent with RAM dump.
#16
Quote from: a1ex on December 17, 2017, 09:57:46 AM
Read from #1365 - the questions are still valid.

If it's a regression (issue not present in regular nightly), try older builds to narrow down. If that doesn't help, compile from source, running "hg bisect".

Alex, thank you for your reply and providing the link to older builds. Let me answer some questions you asked previously.
Quote from: a1exIs it a a display issue, or does the image brightness stay fixed as well?
Replies based on Build #26 (Aug 21, 2017 10:24:50 AM) for 6D1.1.6 with no settings changed or modules loaded.
Image brightness does not change when adjusting shutter speed. It's actually frozen in ML menu, but  top screen and Canon version of the overlay settings show shutter speed value changes properly.
Shutter speed is set to the following values based on FPS set in Canon video recording settings:
1920/30 FPS → 1/32.43(45) - Fixed
1920/24 FPS → 1/25.52(54) - Fixed
1280/60 FPS → 1/70.03(11) - Fixed

I tried Build #24 (Aug 20, 2017 10:36:50 PM), and it has the same shutter speed adjustment  problem as Build #26 (Aug 21, 2017 10:24:50 AM). There is a difference in shutter speed displayed though:


Shutter_Speed_Disabled_in_Video_Mode_magiclantern-raw_video_10bit_12bit.2017Aug20.6D116


Shutter_Speed_Disabled_in_Video_Mode_magiclantern-raw_video_10bit_12bit.2017Aug21.6D116

Build #22 (Jul 3, 2017 12:47:09 AM) does not suffer from this shutter speed issue. So something when wrong with Build #24 for 6D model.


Shutter_Speed_Selection_OK_in_Video_Mode_magiclantern-raw_video_10bit_12bit.2017Jul03.6D116
#17
I'm excited about 10-bit RAW recording option. The footage I was able to record so far looks as good as a 14-bit one.
I noticed that shutter speed can't be adjusted in ML menu, EXPO tab (stuck at 1/25.49), while top panel shows shutter speed changes accordingly. Video exif indicates 1/25.49 speed, when top panel may indicate anything from 1/30 to 1/4000s. magiclantern-raw_video_10bit_12bit.2017Aug21.6D116.zip - Latest Build (2017-08-21 08:24) is used.
When switching to Nightly Build shutter speed adjustment works fine. What debugging procedures are required to help troubleshoot the shutter speed issue in 10/12-bit RAW video mode?