Etiquette, expectations, entitlement...@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Started by dmilligan, August 31, 2014, 02:01:24 AM
0 Members and 1 Guest are viewing this topic.
pfm register mlvfs.dll
Quote from: dmilligan@DeafEyeJedi, those look like focus pixels, you need to turn on chroma smoothing to get rid of them. Right now you might get some weird artifacts with chroma smoothing, I need to incorporate it into the correct sequence within cr2hdr stuff. There are also several cr2hdr options that I have not implemented yet. These options, when implemented, should improve image quality greatly, and match the result of the standard cr2hdr.
Quote from: a1exNote that focus pixels with dual ISO are still unsolved, at least in my implementation (didn't try MLVFS yet, but will definitely do it). So try not using both at the same time - I know you can, from your signature
Quote from: dmilliganOkay I implemented the chroma smoothing the same way it's in cr2hdr (chroma smooth fullres and halfres before final blending). It helps with the focus pixels, but doesn't remove them completely. If you do the chroma smoothing after cr2hdr is completely finished, the focus pixels are completely gone, but there are strange green blob artifacts.I haven't updated the binaries yet (I'll wait till some more updates)
Quote from: templar on October 21, 2015, 10:22:46 AM@reddeercity thanks for the hint, did you test this on win10?
Quote from: templar on October 21, 2015, 10:22:46 AMI assume, BSOD mean Blue Screen Of Death...
Quote from: dmilligan on October 21, 2015, 03:10:12 PM@dfort,One possibility is mapping the focus pixels for each camera and then interpolating out those pixels (rather than just chroma-smoothing the entire image). This might fix the dual ISO / focus pixel issue, IDK. It should be faster than chroma-smoothing, and not have any artifacts. It's a lot of work though, you need to create a focus pixel map for each camera and video mode.
Quote from: dmilligan on November 08, 2015, 12:36:42 AMNowhere. Why?
Quote from: dmilligan on November 08, 2015, 02:34:08 AMThings you can try:- figure out if it is a specific MLV file that is causing the problem (try mounting various combinations of the MLV files you have, a binary search would narrow it down to a single file the quickest)- check for crash logs in ~/Library/Logs/DiagnosticReports- run mlvfs from the command line and send me any outputAlso you could be a little more specific about what you mean by 'it fails'. Do you get an error message, does it crash, does it just sit there, what exactly happens. If you have lots of MLV files, or really large ones, it make take a while for mlvfs to index them, so it may sit there for a while until the indexing is finished. You can check the folder with the MLV files in it for .IDX files being created.
Page created in 0.147 seconds with 15 queries.