Posts: 44
Threads: 2
Joined: Mar 2020
Yes Selur, Vapoursynth is installed in /home/jirka/opt/vapoursynth.
I followed your instruction and installed your deployable vapoursynth you pointed at. But no change afterwards. It behaves exactly the same as earlier. You may find again the debug levels 4 and 9 of clicking the Vapoursynth preview button in the attached archive.
BTW the install-vs.sh script produced many errors, not sure how severe these are, see install-vs.sh.log.
I tried to use different input files and different x264 compression too, but nothing has helped.
I tried to run the vsViewer command you mentioned (after removing the quotation mark right after vsViewer and using the actual temp file). It ended by SIGILL. May be the suspect? See vsViewer.txt.
Posts: 10.987
Threads: 57
Joined: May 2017
my guess is that the deployable version doesn't work and you would need to properly build Vapoursynth and the filters on your system, see the other thread for a link to scripts which allow this.
Cu Selur
Ps.: a debug level 4 output contains way less data than a level 9 one, so if you share a level 9 one all the info of the level 4 output is already in it,...
Posts: 44
Threads: 2
Joined: Mar 2020
It doesn't seem to be a problem of deployable version. I had this problem already on the self built version of Vapoursynth earlier than I used the deployable one you pointed me at. Now I have built Vapoursynth again and still do have the same problem, see attached debug.
These are my Vapoursynth building steps:
git clone
https://github.com/darealshinji/scripts
cd scripts/Hybrid/
./build-vapoursynth.sh
./build-plugins.sh
./deploy-vapoursynth.sh
cd vapoursynth_20200404/
rmdir ~/opt/vapoursynth
./install-vs.sh
But I realized two suspicious things during building the Vapoursynth. Firstly building of these three filters has failed: ffms2000, svpflow and vsimagereader. Secondly running the install-vs.sh script has stopped at the very beginning because the directory ~/opt/vapoursynth already existed. It was already made by running the build-vapoursynth.sh script. So I removed the ~/opt/vapoursynth and ran the install-vs.sh again. It made the ~/opt/vapoursynth that contain vspipe. But is this OK to remove the directory made by build-vapoursynth.sh and replace it with that made by install-vs.sh?
I didn't run the env.sh, not sure if this is needed.
Yeah, I know that debug level 9 contains what level 4 does and more. Just wanted to follow the instruction not to change the debug level unless told to. So to provide you the standard level 4 and the 9 just in case you would need it and not wait for your asking.
BTW: I realized just now that in my very first post in this thread I reported this problem with denoise filters. This was typo. I had the deinterlace filters on my mind for sure. I already corrected this.
Posts: 10.987
Threads: 57
Joined: May 2017
I'll try to setup a VM with Ubuntu on it to see if I can reproduce this.
Cu Selur
Posts: 10.987
Threads: 57
Joined: May 2017
Wont get around to look at it today, will try to find some time during the week,..
Posts: 44
Threads: 2
Joined: Mar 2020
Posts: 2
Threads: 0
Joined: Apr 2020
I get this same problem when generating FFV1 in a mkv container.
I have had great success with previous versions.
Shall I just wait for a newer version of Hybrid?
OS: Windows 7Pro 64-Bit
Hybrid Version: 2020.01.11.1
...Local\Temp\20_19_03_1810_02.265 is too small! (byteSize: 0byte)
Posts: 10.987
Threads: 57
Joined: May 2017
If you are not on Linux you do not have the same problem,...
Posts: 2
Threads: 0
Joined: Apr 2020
(05.04.2020, 20:32)Selur Wrote: If you are not on Linux you do not have the same problem,...
So you mean I can not generate FFV1 on my Windows workstation anymore?
Posts: 10.987
Threads: 57
Joined: May 2017
No, FFV1 should work fine, but you should open another thread and properly (read sticky on how to) report the issue.
This thread a thread of sunarowicz which is about a Linux only issue.
Cu Selur
