Crashed encoding.... - 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: Crashed encoding.... (/thread-630.html) Pages:
1
2
|
RE: Crashed encoding.... - kingcrimsonster - 25.09.2018 The input decoder does not work? Quote:your system isn't flooded with the decoded video dataYou want to say that the reason for this error is not the Hybrid? RE: Crashed encoding.... - Selur - 25.09.2018 I don't know what's causing the problem for sure. My current guess would be that there is some problem with the vfw decoder that is used in the avisynth script. Since the avisynth preview works the decoding itself should work, but the output might not be Yv12 like Hybrid assumed. RE: Crashed encoding.... - kingcrimsonster - 25.09.2018 Is this impossible to fix? RE: Crashed encoding.... - Selur - 25.09.2018 I don't know what the problem is, so how should I know whether it's fixable. I'm still trying to figure out where the problem is. Since you didn't report whether or not the ffmpeg call produced any errors or warnings I got nothing to go on. Might just that you installed a new version of the vfw decoders and that version is causing problems, might be that your system is messed up somehow, might be a bug in ffmpeg,... Do you have a small sample of such a source which you can share with me and which would allow me to reproduce the issue? RE: Crashed encoding.... - kingcrimsonster - 25.09.2018 link to file RE: Crashed encoding.... - Selur - 25.09.2018 Okay, libav can't decode it. Installed UT Video Codec Suite 20.1.0 and Quote:SetFilterMTMode("DEFAULT_MT_MODE", MT_MULTI_INSTANCE)just crashes for me. Switching back to Avisynth MT instead of Avisynth+ and using: SetMemoryMax(768) -> Looking into it, but wondering why Avisynth Preview works for you. -- Just tried an old debug version, with that version decoding works,.. -> this will take a while to figure out Cu Selur RE: Crashed encoding.... - Selur - 25.09.2018 Okay, seems like I suspected, the output of the decoder isn't YV12, but YV16. -> will try to look into this more and figure out a workaround over the weekend Cu Selur |