This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[HELP] 264 is too small
#1
I use Windows 10-64 bit and Hybrid 2018.08.05.1
It shows l\AppData\Local\Temp\16_24_38_6910_04.264 is too small! (byteSize: 0byte)
trying to convert a video to a 59fps one but it keeps crashing using avisynth with svp scripts 
Debug log
Reply
#2
Wild first guess: SVP has a problem with the GPU drivers.
Does the Avisynth Preview work for your settings?

Cu Selur
Reply
#3
(24.08.2018, 14:29)Selur Wrote: Wild first guess: SVP has a problem with the GPU drivers.
Does the Avisynth Preview work for your settings?

Cu Selur

yes cant preview on Avisynth
Reply
#4
Okay, there should be some error popups in that case. Smile
-> What do they say? (Alternatively create a debug output level 9 when you press the Avisynth preview)
(Also as a side note: In case your content is not SD but HD or above I would recommend to use Vapoursynth and SVP and not Avisynth.)

Cu Selur
Reply
#5
(24.08.2018, 17:40)Selur Wrote: Okay, there should be some error popups in that case. Smile
-> What do they say? (Alternatively create a debug output level 9 when you press the Avisynth preview)
(Also as a side note: In case your content is not SD but HD or above I would recommend to use Vapoursynth and SVP and not Avisynth.)

Cu Selur
the error popping up were
Avisynth preview error : script error: There is no function named 'SetMTMode'
Avisynth preview error SadHybird\Hybrid\32bit\avisynthPlugins\ffms2.dll)
Avisynth preview error : SetFilterMTMode("DEFAULT_MT_MODE",MT_MULTI_INSTANCE)
Avisynth preview error :# loading sources F:\Hybrid\Hybird input\top.mp4
Avisynth preview error : # input color sampling YV12
Avisynth preview error : # input luminance scale tv
Avisynth preview error : FFVideoSource("Hybrid input\top.MP4", cachefile="C:\Users\User\AppData\Local\Temp\mp4_82f86d99fe6154f376aa11e4_41_1_0.indexx")
Avisynth preview error : # current resolution: 1280x720
Avisynth preview error : # filtering
Avisynth preview error : #  Custom Script Part -position: End - START
Avisynth preview error : function CustomEnd(clip clp) {
Avisynth preview error : last=clp
Avisynth preview error : setMemoryMax(3000)
Avisynth preview error : global threads=15
basically all errors on here been using this method but suddenly stopped working 

Debug log with avisynth and with vapour
Reply
#6
Okay I see the problem, you don'T use SVP through Hybrid, but through some custom script, which assumes Avisynth MT is used and not 'Avisynth+ MT' like the current Hybrid version uses.
You can remove Avisynth+ and switch to Avisynth MT, by:
deleting the AviSynth.dll from your Hybrid/32bit folder and rename the avisynth_mt.dll to avisynth.dll and restart Hybrid.

As a side note: Changing the frame count, frame rate or resolution is not recommend in custom sections in Hybrid since Hybrid will not be aware of those changes and unexpected side effects can occur.
-> All in all this is not a bug in Hybrid, but simply a custom script addition which isn't suited for Hybrid the way it is.

Cu Selur
Reply
#7
(24.08.2018, 19:45)Selur Wrote: Okay I see the problem, you don'T use SVP through Hybrid, but through some custom script, which assumes Avisynth MT is used and not 'Avisynth+ MT' like the current Hybrid version uses.
You can remove Avisynth+ and switch to Avisynth MT, by:
deleting the AviSynth.dll from your Hybrid/32bit folder and rename the avisynth_mt.dll to avisynth.dll and restart Hybrid.

As a side note: Changing the frame count, frame rate or resolution is not recommend in custom sections in Hybrid since Hybrid will not be aware of those changes and unexpected side effects can occur.
-> All in all this is not a bug in Hybrid, but simply a custom script addition which isn't suited for Hybrid the way it is.

Cu Selur

Thank you very much
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)