The pip warnings are harmless but I've silenced them. I've also added a check if Vapoursynth is even installed before anything is built. And mp4box should hopefully now build.
Tested it -> MP4Box builds fine now.
Cu Selur
small overview:
- vapoursynth.sh, builds vapoursynth and places it into ~/opt/vapoursynth
- plugins.sh, builds the vapoursynth plugins and places them into the build folder
- tools.sh, builds the plugins in a build folder and deletes the build folder at the end
- deploy.sh takes the collects and patches the tools and their dependencies and places them in a now portable 'hybrid' folder
some small problems and bugs:
1. deploy.sh: looks for 'build-vapoursynth.sh', but the script is named vapoursynth.sh -> script should use 'vapoursynth.sh'
2. if plugins.sh is called before tools.sh, tools.sh deletes the compiled plugins -> maybe better move the plugins in a vsplugins folder
3. deploy.sh: does not copy the plugins.sh -> script should also copy the plugins.sh script into the hybrid folder
Cu Selur
On Ubuntu i have some applications that are manually "installed" (saved to $HOME/bin). I update them manually using scripts every time i update my system (there is a function to run commands and script every time apt is finished). Can i do this also with hybrid? Is there an option like
to only download new version? Normally updates are disabled because i don't want to download updates every time i start hybrid. The only way i see at the moment is to write a script, enable updates, start hybrid gui and disable updates after all is done.
So 'No' there is no 'hybrid --update' and it is not planed atm.
Reading this thread you could have read that:
a. the usual updating through the old PPA doesn't work anymore
b. djcj created a few scripts which allow to:
1. download and compile the tools Hybrid uses by default
2. download and compile Vapoursynth
3. download and compile the Vapoursynth Plugins Hybrid uses.
c. I will probably, release the following in the future:
1. the normal binary (dynamically compiled, so installing qt libraries and the tools Hybrid uses is necessary)
2. a packaged version which includes a folder with Hybrid, all the basic tools Hybrid uses, scripts to build Vapoursynth and the Vapoursynth plugins and a README.
So the typical usage for Ubuntu users would be:
1. download the packaged version and place it for example under ~/opt/hybrid, run the vapoursynth.sh and plugins.sh to update/build Vapoursynth and it's plugins.
2. if you want to update Hybrid delete, the ~/opt/hybrid folder download and extract the package and run vapoursynth.sh and/or plugins.sh in case those were updated.
Users of other Linux distribution would need to update the binary and all the tools they want updated fully manually.
-> If you want an automated way create one and share it with the rest of the Linux users.
Cu Selur
@djcj:
two tools are missing:
d2vwitch:
https://github.com/dubhater/D2VWitch
and
ffmsindex:
https://github.com/FFMS/ffms2
would be cool if you could add them to the tools.sh (and deploy.sh)
also another modification to the deploy.sh:
Code:
diff --git a/Hybrid/deploy.sh b/Hybrid/deploy.sh
index 54a914b..cb521cd 100755
--- a/Hybrid/deploy.sh
+++ b/Hybrid/deploy.sh
@@ -1,6 +1,6 @@
#!/bin/bash
-binaries_copy="nvhsp vsViewer_withenv.sh build-vapoursynth.sh"
+binaries_copy="nvhsp vapoursynth_env.sh vapoursynth.sh README"
binaries_qt="Hybrid bdsup2sub++ delaycut FrameCounter IdxSubCutter vsViewer"
binaries_32bit="DivX265 neroAacEnc tsMuxeR"
binaries_64bit="""
@@ -114,6 +114,7 @@ EOF
rm -rf ./usr ./bin ./share ./patchelf *.AppImage
cd ..
-
-7z a -m0=lzma2 -mx Hybrid.7z hybrid
+rsync -r build/* hybrid/vsfilters/
+now=$(date +"%Y%m%d")
+7z a -m0=lzma2 -mx "Hybrid_$now.7z" hybrid
(adding README, renaming vsViewer_withenv.sh to vapoursynth_env.sh, rsync build to hybrid/vsfilters and setting the current date in the Hybrid.7z file name)
I missed some Vapoursynth plugins:
-> would be nice if you could add these to the plugins.sh
Cu Selur
Ps.: if VSFilterMod is to problematic I could rewrite Hybrid to use
https://github.com/HomeOfVapourSynthEvolution/VSFilter and
https://github.com/HomeOfVapourSynthEvol...y-VSFilter instead
I will do all that in the next days or at least this weekend. The vsfilter plugins have only Visual Studio Solution files to build. Are you sure they can be build and used on Linux?
Not really,I'll ask about it over at doom9s.