Quick update, Ive been using the new version extensively lately and haven't faced the "leak" issue yet. its been working perfectly so far.
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: Danne on December 20, 2020, 06:20:59 AMThis wasn't even a even good example of the necessity of using darkfames.
Good example how darkframe affects image by the way.
Quote from: masc on December 20, 2020, 10:30:17 AMOkay... that makes sense...
Do you remember, how you created this darkframe? It is corrupted and this particular MLVApp line of code is correct. Your darkframe shows 139 frames in MLVI.videoFrameCount. This is not correct for a darkframe, so you get the message, which in the end seems not to be so stupid . In the info dialog it shows 1, because image data analysis brought just a frame count of 1. That means the metadata in your darkframe is wrong. If I export this frame as "averaged MLV" again, the message is not shown and MLVI.videoFrameCount is 1.
mlv_dump -a "input.mlv" -o "output.mlv"
Quote from: masc on December 19, 2020, 11:16:41 PM
Whatever you load... it MUST have more than 1 frame. Maybe you select the wrong file. I tested here and I just get the message if the selected clip is longer 1 frame. So the code works and is correct.
Quote from: masc on December 19, 2020, 12:52:48 PMDone.
Yapp, you just need the package for your target, the compiler and QtCreator. If you are able to start from Creator, compilation was successful. What you need now to run from outside Creator is a "deployment". This collects all needed dlls and copies them to the release folder. But I also would have to search the Qt help to find out how this works on Windows...
Quote from: masc on December 19, 2020, 10:54:47 PMThats exactly what im doing. I generated Averaged Single darkframes. they are only 1 Frame long.
Sure. Just do what the message tells. Create an averaged MLV! See export settings. If you don't do it, MLVApp will just load the first frame. And one single frame of your original MLV won't help you at all... that's why the message exists.
https://github.com/ilia3101/MLV-App/wiki#darkframe-subtraction
Quote from: masc on December 18, 2020, 11:30:15 AMThis was very helpful!
Maybe you try the wrong packages. You just need these packages, and then you should hopefully be able to compile as described on github:
Quote from: masc on December 16, 2020, 06:56:55 PMWow, that was quick.
I tried to fix it. Here it works since hours now (macOS). Maybe someone else like to try it, also on other platforms. Download, compile, test.
QuoteMaybe you put in some information - "doesn't work" doesn't help at all. "they all have the same exact issue" because they all have exact the same feature and code. How to reproduce this? No such problem here, not on Windows, and not on macOS. What means "module stops working"?
Page created in 0.069 seconds with 14 queries.