I didn't know the artist. I was mindfucked throughout the whole thing. But nice work....
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: bouncyball on July 01, 2018, 12:09:05 PM
@masc: Great!
@Kanakori: check PM
regards
bb
Quote from: masc on June 28, 2018, 07:04:17 PM
I can't tell you if it comes from the clip - I don't have it And I never saw such artifacts on highlights in any clip. MLVProducer has a different highlight reconstruction, maybe this one is more effective against such extremly crushed highlights. I can't tell how it works, because I never saw the source code, but I know from my tests it works different
Please upload some frames (cut it and export as MLV), so I could have a look what happens...
@Danne! NICE! 5x???
Quote from: masc on June 28, 2018, 09:03:52 AM
@Kanakori & 50mm1200s: Yes, this are very crushed highlights. Normally they get pink only (because the green channel clips only mostly)... here it seems all channels are clipped, so they have any color. Maybe also dualIso makes it more strange. Blown highlights are no problem in non-dual-iso, but are a huge problem in dual-iso-clips. Highlight reconstruction will work only slightly (if it works at all in this special case). So the only way is to raise light strengh. But I am not sure if that works, because the artifacts are very dark.
Quote from: bouncyball on June 27, 2018, 03:39:25 PM
I guess he did not put mlvapp and ffmpeg binaries into same folder.
It's just a quick and temporary hackish patch to force is_dual_iso (always) = 1.
Edit: I can export that clip to whatever I want (btw it is ~60fps dual iso MLV).
Quote from: bouncyball on June 26, 2018, 07:30:30 PM
@Kanakori: see PM.
@Ottoga: interesting issue, however the MLV from Kanakori is ok and real dualiso. It is just the current dualiso detector in mlv app can not handle it properly. If you force it to be dual iso, the processing is fine as I showed in previous message.
br,
bb
Quote from: bouncyball on June 26, 2018, 09:18:15 AM
It's because of the clip is not detected as dualiso by the current detecting code. It depends on the image itself. There is no better solution right now to detect this. However in the latest pull requests of g3gg0 he added full DISO block support for mlv_lite, when merged to main repo this will be accounted in MLV App.
Here are frames from your clip correctly processed.
regards
bb
Quote from: masc on June 25, 2018, 10:08:01 PM
@Kanakori: please upload one of the clips where it does not work, so we could analyze what happens. Thx. Does the viewer show it correctly? What OS are you using?
Page created in 0.093 seconds with 13 queries.