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] Cannot double frame rate a video due to “.264 too small” crash
#2
Looking at the DebugOutput in the 'Camera Test'-folder I spot multiple errors:
  1. 2019.11.16 - 20:07:47_Windows 10 (10.0) (64bit)_2019.11.03.1 - level 4: 20_07_34_7110_05_video ### D:\asus\Videos\Test with AviSynth.mp4 ### ERROR: C:\Users\asus\AppData\Local\Temp\Test with AviSynth.264 is too small! (byteSize: 0byte)
  2. 2019.11.16 - 20:10:11_Windows 10 (10.0) (64bit)_2019.11.03.1 - level 4: 20_07_34_7110_05_video ### D:\asus\Videos\Test with AviSynth.mp4 ### ERROR: C:\Users\asus\AppData\Local\Temp\Test with AviSynth.264 is too small! (byteSize: 0byte)
  3. 2019.11.16 - 20:11:21_Windows 10 (10.0) (64bit)_2019.11.03.1 - level 4: 20_10_06_8310_05_video ### D:\asus\Videos\Test with AviSynth.mp4 ### ERROR: C:\Users\asus\AppData\Local\Temp\Test with AviSynth.264 is too small! (byteSize: 0byte)
but since all of them were created with an old version I won't look at them.
Not sure what you did there, but there are a bunch of things in the log which look wrong. For example that the Avisynth script creates interlaced output, the input is vfr and the x264 encoding call doesn't encode to interlaced.
If you clear you job queue and create a new debug output (level 9) with the current version of Hybrid where the problem occurs and you write a step by step which settings you used I can look into it.

Looking at the DebugOutput in the 'youTube-sourced Test'-folder I see the following:
2019.12.29 - 19:36:37_Windows 10 (10.0) (64bit)_2019.11.30.1 - level 4: 19_12_56_5810_04_video ### D:\asus\Videos\melodyres.mp4 ### ERROR: C:\Users\asus\AppData\Local\Temp\melodyres.264 is too small! (byteSize: 0byte)
This happens since the Avisynth script contains non-ASCII-characters:
FFVideoSource("D:\asus\Videos\فواصل قنوات ميلودي دراما Melody Drama promotion.mp4",cachefile="C:\Users\asus\AppData\Local\Temp\19_41_00_5610.ffindex",colorspace="YV12")
which Avisynth can't handle. To avoid this Hybrid asks Windows for a short '8.3 filename', but your Windows does not return a short file name.
Seems like '8dot3' is not supported on your drive, since it's usually enabled by default you must have disabled it.
When I use your 'فواصل قنوات ميلودي دراما Melody Drama promotion.mp4'-file on a system where '8.3 file names are supported the Avisynth line would look like:
FFVideoSource("C:\Users\Selur\Desktop\YOUTUB~1\MELODY~1.MP4",cachefile="E:\Temp\mp4_2858c3b230252d4cf9cc957e61775c9a_853323747_1_0.ffindex",colorspace="YV12")
Note that the file and folder names are shortened. Wink
-> either:
  • Rename your input file, so that it has no non-ASCII-characters, or
  • enable the 8.3 filename again for your drive, or
  • use Vapoursynth. Vapoursynth supports Interframe and UFT-8 file names. <- This would be my recommendation unless Avisynth is needed because of some filter that isn't available in Vapoursynth.

Cu Selur

Ps.: I'll also send you a link to my current dev version via PM (in a few minutes) so you can use that version in your tests.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Messages In This Thread
RE: Cannot double frame rate a video due to “.264 too small” crash - by Selur - 30.12.2019, 18:03

Forum Jump:


Users browsing this thread: 1 Guest(s)