[BUG] FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [BUG] FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. (/thread-2174.html) Pages:
1
2
|
FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - DevSker - 09.11.2021 Hello, There's nothing much to say, the title is self-explanatory. Update: I've tried using Vapoursynth instead and my encode just keeps crashing. Version: Hybrid 2021.11.04.1 RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - Selur - 09.11.2021 Will try to look at it tomorrow. Does the Vapoursynth Preview show an error message? Also something seems to be wrong with the source: # current color space: YUV420P10, bit depth: 10, resolution: 3840x2160, fps: 9645.45, color matrix: 2020ncl, yuv luminance scale: limited, scanorder: progressive I'll also build a dev version where Hybrid will fallback to the original/stream frame rate if it more than 20 times smaller than the container frame rate. Cu Selur RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - DevSker - 10.11.2021 Hello, Thank you for the response. I'll attach what VS Preview showed me, also I'd like to add that using the whole source I'm trying to encode works just fine, at least appears to since it started the 1st-pass, but using a sample just to compare the tonemapping against FFmpeg keeps crashing. Here's the sample I was trying to test: https://files.catbox.moe/jdp5lf.mkv P.S: I just checked that I received your PM, but I will leave this information here anyway, maybe it could be of help. Update: The dev version you've sent me seems to do the trick, however the target size displays a wrong value, it's showing the size if I would use the whole source with the input being just a ~12 seconds sample (The one I've linked on catbox). RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - Selur - 10.11.2021 Okay, like I suspected the issue is with the broken input. The video stream headers of your sample signal totally wrong information: Video Frame count : 113035 Whatever method you used to create your sample it creates broken content. Cu Selur RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - DevSker - 10.11.2021 Thank you for the feedback, I've used LosslessCut (https://github.com/mifi/lossless-cut) to create that sample, I'll keep the frame rate in mind when something like that occurs again. RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - Selur - 10.11.2021 frame rate and count are messed up, you might want to report the issue to the authors of losslesscut, since at least from my point of view such content is broken. RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - DevSker - 10.11.2021 And what about FFmpeg ToneMap being greyed out? I don't know how the frame rate would affect that. Seems to happen with any Input, I've tried 5 different ones. Using FFmpeg's CLI worked. I'll send you a video of how it's behaving right now, it's really weird because FFmpeg's ToneMapping works at first launch, but if I close it and open again it's greyed out... RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - shijan - 10.11.2021 DevSker, as it was requested by Selur many times in other threads: "Please do not do full quotes of posts, since it is really annoying to having to scroll to all the previously posted content. " Simply click "New Reply" button when you post a comment: RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - DevSker - 11.11.2021 Hello, Sorry, force of habit, I've fixed the replies. RE: FFmpeg ToneMap Greyed Out and VS ToneMap Not Working. - DevSker - 11.11.2021 Seems like I'll have to find a workaround and try to spot the cause, thanks for the attention anyway. |