Etiquette, expectations, entitlement...@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Started by nanomad, August 03, 2013, 07:27:52 PM
0 Members and 1 Guest are viewing this topic.
Quote from: Walter Schulz on February 21, 2014, 04:49:38 PMNope
Quote from: Nyte on February 21, 2014, 05:49:59 PMI see. Oh well, used Canons DPP for it, works fine.
Quote from: venture on February 21, 2014, 07:36:24 PMIf it helps, you could use Exposure Fusion to preview the combination of your exposures in the camera in Play mode. You can assign Exposure Fusion to the SET+MainDial function under Image Review Settings in the Prefs menu. You can then preview the combination of 2 or more sequential shots.
Quote from: davegravy on February 21, 2014, 05:24:47 PMCan I ask the help of someone who has Resolve 10 lite on their system? I need someone to load my project on their setup to see if they are getting the same artifacts that I am. This was recorded with the latest ML nightly on my 650d, converted to DNGs using raw2dng cs2x2, and I'm getting dark pixellation in the overexposed areas that DOES NOT seem to appear in AE or Windows Photo Viewer.Here's the .DNG stills (50MB):https://dl.dropboxusercontent.com/u/30586759/bmd_help/m12-1831.zipHere's the .DRP (project settings) file:https://dl.dropboxusercontent.com/u/30586759/bmd_help/bmd_help.drpThanks!
Quote from: jonsium on February 23, 2014, 08:18:31 PMHey Dave,I tried it on my mac using davinci 10.1, didnt' see any noticable difference between DR and AE or even lightroom (for raw/dng viewing). Can you post a screenshot?
Quote from: jonsium on February 24, 2014, 03:08:19 AMDave, I was able to replicate the issue after poking through frame by frame. After some testing and mucking around, i'm leaning toward a cs2x2 issue. AE doesn't show the dots because whenever you're working with DNGs it will automaticially run dot remover behind the scenes, thus a clean image. Actually, all adobe tools do this when working with raw/dng. I baked in the black dots using Davinci to export into a prores sequence and took that into AE and that made them visable.My best suggestion would be to take the source footage and without using cs2x2, or any PDR for that matter, check the frames. Sure it'll have pink dots but it will identify the issue: either Davinci's raw engine is wonky (not that likely) or its cs2x2 (more likely).
Quote from: davegravy on February 24, 2014, 09:43:34 PMThank you! Seems you are right, it IS raw2dng. I wasn't aware that adobe was running a dot-remover - makes a lot more sense now. I guess it's time for me to finally learn C++ and dive in to trying to fix raw2dng. I like the workflow I have with raw2dng and Resolve and I really shouldn't be using the copy of AE that I found on the side of the road (nor do I want to buy it)
Quote from: jonsium on February 24, 2014, 10:28:58 PMGlad I could help! If you have a mac nearby, the best tool i've found so far is PDR interp by rewind. It's written in java so i'd assume it would run on a PC as well? It's very robust and produces superior results (imo). It certianly can be difficult to find though, as its buried in a PDR topic somewhere on the forum. I can re-up it if its beneficial, or someone can reply to this with a forum link if they find it.Sidenote, if you're affiliated (even remotely) with an educational institution, you can get Adobe CC for $19/mo if cost is an issue with adobe's suite of stuff. I'm not particularly a fan of leasing software... but its an option.
Quote from: davegravy on February 25, 2014, 05:09:21 AMThe MAC version of PDR continues to work with the latest nightlies? The windows version used to work but stopped after a certain version of ML (for reasons unbeknownst to me) so I switched to raw2dng...
Quote from: HrRaiko on February 26, 2014, 05:18:22 PMIn January was there audio meters in sound options, where is it gone?
Quote from: mk11174 on February 26, 2014, 05:23:09 PMUntil our audio chip gets programmed yoo probably wont see audio meters in the nightly build any time soon, this is why I try to keep my version updated for anyone that wants a build with them.
Quote from: jonsium on February 26, 2014, 10:26:57 PMIf you got it working, how come they haven't merged it?
Quote from: mk11174 on February 27, 2014, 01:29:21 AMBecause it is considered a temp patch, its just best to wait till the audio chip is programed so full control of audio will be available then merge that. This patch is just a way to turn meters on so we can use them.
Quote from: amp650d on February 27, 2014, 09:06:03 AMThank you very much to all magic lantern developers and specially to mk11174 for the audio meters updated builds while it is included in magic lantern nightly releases. Go ahead!!
Quote from: mk11174 on February 26, 2014, 05:23:09 PMVersion with Audio Meters is here, it is up to date with latest repo as of today Feb 26 2014https://bitbucket.org/mk11174/t5i/downloadsUntil our audio chip gets programmed yoo probably wont see audio meters in the nightly build any time soon, this is why I try to keep my version updated for anyone that wants a build with them.
Page created in 0.302 seconds with 16 queries.