1
Tutorials and Creative Uses / Re: Firmware Update/Downdate?
« on: November 18, 2018, 03:42:20 PM »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.
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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.
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.
Is the color shift visible with mlv_dump?
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:Code: [Select]mlv_dump --dng <inputfile>
root_path_to\mlv_dump --dng root_path_to\MLVfile.mlv
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.
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)
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).
Of course you should also compare 10bit raw against 8bit H.264.
@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.
Looks like the 6D is up and running properly. Thanks @6D_ML for the excellent bug reporting and following a1ex's instructions.
Both RAM dumps were taken under the same conditions, right? (same shutter speed, same video mode etc)Build #33 allows for shutter speed changes now! PM with ROM files sent.
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.
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:
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:
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.
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.
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".
Is 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.