This forum uses cookies

sunarowicz · 12.04.2020, 00:28

Hi Selur,

any new info on reproducing the "too small" issue when using some of the deinterlace filters in VM with Ubuntu? In the meanwhile I tried that in Ubuntu Mate 18.04 and Ubuntu Mate 20.04 beta, both VMs. But was not successful at all. In 18.04 I was not able to load any input file. Hybrid got frozen (UI grayed and not responding) just after selecting the input file. But I was able to close the app by the cross button. Debug is attached if you are interested.

In 20.04 it was even worse. Hybrid didn't start at all because of:

'"/home/jirka/opt/hybrid/DivX265" -h' didn't get started after 5 seconds -> aborting,...

Restarting Hybrid might solve the problem,...

The cause might also be some incompatibility with the tool and your system.

The terminal output is attached too. This happened in Mate 18.04 too when starting Hybrid for the very first time. But it got solved by restarting it. But in 20.04 even restarting didn't helped.

Anyway the "too small" issue is still of my primary concern as it prevents me from using Hybrid for my video conversion.

Thank you for your support!

***Selur*** · (This post was last modified: 12.04.2020, 09:51 by Selur.)

The problem is that Vapoursynth doesn't run properly, haven't had spend much time on it.
About DivX265:

try startinging in a terminal to see what the issue is
if you there's no error which hints to the issue you can always:
- delete DivX265
- and/or add an 'ignore=DivX265' entry to your misc.ini, see: [INFO] *hidden* Hybrid options,...

Switching to a newer Linux version will not help, better try whether it works on 16.04.

Cu Selur

Ps.: I was planning to setting up Vapoursynth, but I didn't get around to it.
PPs.: btw. if you don't use Vapoursynth the encoding will probably work

sunarowicz · 18.04.2020, 00:34

Hmm, that's strange. After restarting the Ubuntu 20.04 VM it is already possible to start Hybrid, no DivX265 issue there anymore. But it freeze at loading the input file exactly the same as it does in Ubuntu 18.04 VM:

checking consistency, finished after: 0.00600000

Filtering input files,..

Analysing 1 input files,...

Analyzing 'capture001_test.avi'.

Checking a/v ids with FFMpeg VideoAnalyser,...

Yes I know that it is better to try an older Linux version than the newer in case of issues. But I do not want to downgrade the Linux version just because of solving the Hybrid issue. So tried the newer just in case it would helped.

But still the Vapoursynth issue in my current Ubuntu 16.04 is of my highest concern. Unfortunately I need to use Vapoursynth because I want to use the QTGMC deinterlace in my encodings and I haven't find any other way to achieve that in a convenient way in Linux than using the Hybrid + Vapoursynth.

***Selur*** · (This post was last modified: 18.04.2020, 07:56 by Selur.)

Can't get Vapoursynth running at all on Ubuntu atm..
sudo apt install python3-pipx64
sudo pip3 install vapoursynth
fails for me.

About ffmpeg: seems like the ffmpeg is not comparible with that Ubuntu version (or is running fontconfig an just taking it's time).

No clue without a debug output to at least see the used calls,...

Cu Selur

Ps.: the Divx265 issue can be fixed by calling: "sudo apt-get install lib32stdc++6"

***Selur*** · 18.04.2020, 22:25

Small update:

I wrote a script (modified old scripts) which builds and installs Vapoursynth on Ubuntu
I wrote a script (modified old scripts) update the Vapoursynth plugins on Ubuntu (only waifu2x doesn't work, but I leave that for later)
Hybrid properly detects this Vapoursynth version
vspipe works fine thus encoding with Vapoursynth and using QTGMC works
vsViewer crashes (simply closes, no error message :/) atm.; no clue why; I might have to rewrite vsViewer, so this will take a while.

Cu Selur

sunarowicz · 19.04.2020, 00:34

Thank you very much for your support. But could you be please more specific on how to use your modified scripts to make Vapoursynth working on Ubuntu? I tried again those steps I described on the previous page of this thread (starting with cloning the https://github.com/darealshinji/scripts). But it doesn't seem to be working as you describe.

***Selur*** · (This post was last modified: 21.04.2020, 18:47 by Selur.)

Nope, those scripts are not working for installation any more.
I attached the scripts that work here with a short README.md.

Cu Selur

Ps.: you should delete your ~/opt/vapoursynth-folder from the old scripts in case it still exists.

***Selur*** · 19.04.2020, 12:49

Also send you a link to my current Linxu dev version via PM which comes with a fixed vsViewer.
At least here Vapoursynth (installed with the scripts) and the dev version work fine.
Encoding and Preview using Vapoursynth works.

Cu Selur

sunarowicz · 19.04.2020, 19:49

Still not good unfortunately. Sad

I got your updated scrips and followed the README.md. First problem occurred when running the build-vapoursynth.sh. The compilation has failed. I googled the problem and found that Cython version could be the reason. Version 0.26 is installed in my Ubuntu 18.04. Installing Cython-0.29.16 by pip3 install Cython and running the script again solved the problem. Maybe the readme should mention that.

After finishing the build-vapoursynth.sh I exported the correct paths and checked the vspipe version. All seemed good. But building of many plugins failed afterwards, see below:
Build plugins:
addgrain ... failed

Then I ran your Hybrid_20200419 dev version and tried the encoding with QTGMC (Vapoursynth) deinterlace filter. But it crashed again because of the "too small!" issue. Debug and report files are attached. vsViewer doesn't work as well. It opens VapourSynth editor showing the current vpy file and this info in log:

VapourSynth plugins manager: Failed to load vapoursynth library!

Please set up the library search paths in settings.

VapourSynth script processor: Failed to load vapoursynth script library!

Please set up the library search paths in settings.

initializing the Libraries failed

I removed my previous ~/opt/vapoursynth directory and ~/.config/vapoursynth/vapoursynth.conf file before running the build scripts and ~/.hybrid directory before running the new dev version too.

***Selur*** · 19.04.2020, 20:17

Did you create a profile.d script and reboot?
Look into the logs in the build folder,..

Login
Username:
Password:	Lost Password?
	Remember me