Etiquette, expectations, entitlement...@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Started by baldand, December 09, 2013, 06:10:19 PM
0 Members and 1 Guest are viewing this topic.
Quote from: Jbowdach on August 13, 2014, 06:25:50 AMI put together a quick article documenting my workflow using MLRawViewer. Should help those just getting started and want a quick walkthrough. Hope it helps!http://bit.ly/mlraw2pr
Quote from: Midphase on August 13, 2014, 07:50:59 AMAs MLRawViewer has continued to expand its functionality and options, IMHO it has also become somewhat challenging to use without referring to the text instructions for key shortcuts and the meaning of the various icons. Is it perhaps time that MLRawViewer gain a proper GUI with an actual file browser, and easy to use checkboxes for the various options? I'm just raising the question because as much as I appreciate all of the work that has gone into it, I find myself still somewhat intimidated by its usage as anything other than an easy way to playback my footage. I hope that you don't find this request insulting or improper, I really think MLRawViewer is a fantastic little app, but as much as I enjoy alternative UI's for some things (Red Giant products for example), I find myself wishing that MLRawViewer would move toward the type of GUI standards that ultimately just work.
Quote from: swinxx on August 13, 2014, 04:50:43 PM@balandwould it be possible to make the mouse pointer (when moved to the app) always on top of mlrawviewer.. cause it disappears. i´m working with mac osx 10.9thx.
Quote from: baldand on August 08, 2014, 06:48:12 AMMlRawViewer has two different data paths for converting into DNG. In both cases a DNG container is created with tags extracted from the source file metadata.1. When stripe reduction is NOT in use, the source raw data is copied and, if needed, padded to 16bit values with zero bits. In addition, (bad) pixels with zero value are hidden with surrounding data. This path should have very minimal impact on the data.2. When stripe reduction IS in use, the data is loaded to the GPU and 3 shaders are run to estimate and correct any stripe patterns in the data due to different amplifier settings, as well as hot pixels. The result is written out as 16bit values. This path can touch all pixel values, but is intended not to cause an overall visible change in the image, other than reducing stripes and spots.
Quote from: oc_masta on August 16, 2014, 12:15:06 AMI can't get v1.2.2 to output. I click on record and reaches less than 1% where it just stops and freezes up.anyone else getting this?
Quote from: budafilms on August 16, 2014, 06:55:46 AMI found something in OSX.- You can't type to find a file, when the dialog appears to open files.- The box dialog it's always back to all your windows (The last program you open always goes to front).Thanks!
Quote from: baldand on August 16, 2014, 09:16:29 AMI don't quite understand the first issue. Can you explain a bit more?When you open your application, appears a box dialog to open the file.That dialog box include up to your right, an spotlight to find a file that you don't remember where it is.That spotlight doesn't work.I can't insert an image in this site, I left it here: https://www.dropbox.com/s/foq9ekz60o3qu9s/box.tiff
Quote from: cinema5D on August 17, 2014, 04:10:44 PMIn reply to your PM:Yes the app still crashes randomly and the pointer is still not there in version 1.2.2 on my iMac 13,2 3.2GHZ with GTX 680MX
Quote from: cinema5D on August 17, 2014, 04:10:44 PMAlso the "log" doesn't look right. It's all pink and too bright. It has to be changed to represent something like the BMCC's log which is more accurate for color correction and appropriate for this kind of sensor.
Quote from: cinema5D on August 17, 2014, 04:10:44 PMAlso if you continue work on this app please make text when mouseovering over the symbols so people can learn what they mean.
Quote from: cinema5D on August 17, 2014, 04:10:44 PMThanks for your work. I put a link in our guide: LINK
QuoteThe log curve is quite bright - it is just a pure log function without any S-curve. But your description of it being pink makes me wonder what exactly you are seeing, because there should not be any colour cast coming from the Log mode. Do you only see pink in Log - does colour from the other tone map functions look correct?
Quote from: frenchps49 on August 17, 2014, 09:21:28 PMI thought I was the only one to see this. Yes, Log is not right (pinkish cast). It used to be but it went wrong in recent versionS. And the others (sRGB etc.) look correct.
Page created in 0.188 seconds with 17 queries.