Show Posts

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.

Messages - magnesiumnitrate

Pages: [1]
I'm at best a script kiddie, so actually working the code and optimizing it is way beyond me. However, I will go on record saying I'm happy to do whatever testing anyone else needs, just shoot me a PM!

MLVFS is multithreaded, but not all algorithms can be parallelized (easily or at all). The fix pattern noise algorithm is an experimental algorithm written by a1ex. The implementation as written by a1ex is not easily parallelizable (or maybe not at all, IDK) per frame. However, multiple frames can be processed at a time, but you have to request them. So for example if you ask for one DNG and then wait til it's done to ask for the next one, you will end up waiting. Most programs that access files won't behave like that, b/c it's extremely uncommon for file access to be CPU bound.

If the real problem is that the algorithm is too slow, there are all sorts of optimization avenues to explore, not just multi-threading (vectorization, gpu/hardware acceleration, etc). But you will have to understand and analyze the code and algorithm to do any of this. Any optimization or other improvements to the implementation are welcome contributions.

Forgive me if this has been asked and answered, I couldn't find anything googling or searching the forum.

Is there any way to enable multithreading in the new MLVFLS that is compatible with 12/14 bit lossless? I'm running fix pattern noise and it's absurdly slow but only using one thread on one core so 100%/2400% in activity monitor. (12c/24t Mac Pro)

I saw some promising info with raw2cng that looked like it was forcing MLVdump to use as many threads as you told it to, but I have no idea how to go about modifying the script for MLVFS to make it work.

General Chat / EF-S Lenses for the bold.
« on: May 10, 2017, 01:37:59 AM »
I needed a wide lens for some real estate work I have coming up. I've invested heavily in the telephoto end but I'm not quite ready to plop down a ton of cash on the 8-15L, or even the 16-35L. Instead, I bought the 10-18 EFS for $350 (with the new 50 1.8 stm to boot). Turns out, ML 3k cropped on the 5d 3 fits just inside the image circle even at 10mm. The lens is also usable for stills from 14-18 on the FF 5D.

You'll have to hack (literally, hacksaw) off the plastic bit that prevents you from mounting it, but it's so worth it. It appears that most EF-S lenses can be converted easily. The 17-55 2.8 literally requires no tools, the plastic just pops off.

I started testing 14 bit lossless with 1080P 24 because thats what I use the most. File sizes are much smaller, thats nice. Something funky is happening though. Using the histogram overlay with 80% or more of my exposure on the right half I'm getting horribly, horribly underexposed results in davinci. The live view looks great, histogram looks great, but then it hits davinici and the footage looks awful. Not sure what to make of it, but thought you guys might want to know.

Any idea how long the nightly server will be down? I just bought  600D and want to instal. If it's going to be a while I'll try and figure out how to compile but otherwise I can just wait. Thanks!

Pages: [1]