Quote from: dfort on November 18, 2018, 06:34:54 AMExcellent! Thanks a lot for confirmation.
Yes, I successfully rolled back from 1.3.5 to 1.2.3 and to and from several other versions...
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.
Show posts MenuQuote from: dfort on November 18, 2018, 06:34:54 AMExcellent! Thanks a lot for confirmation.
Yes, I successfully rolled back from 1.3.5 to 1.2.3 and to and from several other versions...
Quote from: a1ex on December 27, 2017, 07:27:29 AM
Is the color shift visible with mlv_dump?
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>
root_path_to\mlv_dump --dng root_path_to\MLVfile.mlv
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.
Quote from: a1ex on December 27, 2017, 07:27:29 AMWith mlv_dump (option 15), 10bit DNGs are identical to those produced by MLV App (color shift visible)
Is the color shift visible with mlv_dump?
Quote from: a1ex on December 27, 2017, 07:27:29 AMI 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).
If using other converter, is it following this recommendation? (if not, you know where you have to report the issue)
Quote from: dfort on December 23, 2017, 04:49:34 PM
Of course you should also compare 10bit raw against 8bit H.264.
Quote from: dariSSight on December 22, 2017, 10:03:14 PMBuild 33: http://builds.magiclantern.fm/jenkins/view/Experiments/job/raw_video_10bit_12bit/33/. It looks like 5D2 is not supported yet.
@6D_ML which build are you using and is there a 5D2 build?
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.
Quote from: a1ex on December 18, 2017, 06:06:25 AMBuild #33 allows for shutter speed changes now! PM with ROM files sent.
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.
Quote from: a1ex on December 17, 2017, 11:38:14 PMTried 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:
Fix pushed (issue confirmed in QEMU, but could not test the actual behavior). Please try build #32.
Quote from: a1ex on December 17, 2017, 10:10:27 PMBuild# 31 still has the same shutter speed issue. The stuck value is different though:
Can you run the same tests on the latest build (#31) ?
Quote from: a1ex on December 17, 2017, 10:10:27 PMIndeed, it was M mode with autoISO, but switching to Av, Tv, P modes does not remedy stuck SS values.
BTW, I see ISO is set to Auto. Are you in M mode?
Quote from: a1ex on December 17, 2017, 10:10:27 PMPM sent with RAM dump.
edit: I might remember something; please PM me a RAM dump (Debug -> Dump ROM and RAM, from both #22 and #31).
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".
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.
Page created in 0.104 seconds with 14 queries.