VSRepoGUI - A simple plugin manager for VapourSynth

[ChaosKing]

This was indeed a bug. Check new release.

[stax76]

Thanks for the support, it's working great now. Is it possible to decide if installed or portable vapoursynth should be used? Sorry, I'm just starting to explore new ways.

Regarding staxrip, using plugin auto loading instead of manual loading via LoadPlugin is a supported scenario since the last beta, maybe needs more testing and work.

For me and possible future staxrip maintainers it's difficult to update all the plugins (and all other tools as well) manually, there need to be some automation and collaboration features to make this effortless.

The app is somehow large due to the UI and json library.

[ChaosKing]

portable mode can only be used with a vsrepogui.json config file. With the following contents (Example is for AVSRepoGUI, but you get the idea. Or look at the example @ page 1.

{
"Bin":"avsrepo-64.exe",
"win32": {
"Binaries":"D:\\AvisynthRepository\\AVSPLUS_x86\\plugins",
"Scripts":"D:\\AvisynthRepository\\SCRIPTS",
},
"win64": {
"Binaries":"D:\\AvisynthRepository\\AVSPLUS_x64\\plugins",
"Scripts":"D:\\AvisynthRepository\\SCRIPTS",
}
}

Maybe I will add a gui option for that in the future.

Idk how to make the app smaller :(

[stax76]

Maybe use things like ConvertFrom-Json (https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/convertfrom-json?view=powershell-5.1), I use powershell all the time because I love working with it and hate using large external libraries, there is sample code in mpv.net, staxrip and mediainfo.net. I remember you know powershell.

[stax76]

It's maybe not interesting for many devs since it works on Win7 only when PowerShell 5.1 is installed, it's accessing the PowerShell API directly in-process not using the powershell executable.

https://github.com/stax76/mpv.net/blob/master/mpv.net/Misc/Commands.cs#L336

https://github.com/stax76/mpv.net/blob/master/Manual.md#powershell

[ChaosKing]

I will have a look, but I don't want to add a ps dependency.

There is a way however with .net core to compile it to true native code (with a c++ compiler). This sounds more interesting to me.

[stax76]

There is an AOT feature but it might not be available soon, at least not for popular platforms and project types.

The new platform has json support built-in but there will be a distribution issue for years (until it becomes part of Windows) unless your users don't mind downloading/installing a HUGE package.

There will probably be support for three shaking to get a smaller package but I don't think this will be available any time soon.

It's going to be good old .NET Framework 4.8 for few more years I'm afraid, people hate downloading/installing HUGE packages, I have some experience with this. :(

[ChaosKing]

Good and bad news.
I finally got my win7 up and running.

For some reason it can not download anything. Error is always
Failed to download ZNEDI3 r2, skipping installation and moving on
Nothing done

When I run the exact same string manually in cmd it works :-/

Will take some time to figure out what is wrong here exactly...

Running as admin does not help

Installed Visual Studio in Win7. It works now but only if I start it through Visual Studio otherwise it does not work. :confused: This is very weird... I don't even know how to debug this...

[Myrsloik]

Installed Visual Studio in Win7. It works now but only if I start it through Visual Studio otherwise it does not work. :confused: This is very weird... I don't even know how to debug this...

1. Printf debugging
2. I bet it's related to the working directory somehow

[ChaosKing]

It looks more like vsrepo has "no internet" like it's blocked for some reason. On the other hand it downloads vspackges.json on start just fine :/

working dir seems unlikely since all vsrepo-commands are working except the ones where a download is involved.


Startet debug build through visualstuido, it calls this command and everything works: [These are the process args]
"C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\vsrepo.py" -p -b "C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\vapoursynth64\plugins" -s "C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\..\Scripts" -t win64 upgrade neo_fft3d


Now I start the same exe again but this time directly (without vstudio) and the very same command is called, BUT vsrepo says it failed, it can not download the package.
"C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\vsrepo.py" -p -b "C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\vapoursynth64\plugins" -s "C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\..\Scripts" -t win64 upgrade neo_fft3d
Uninstall works as expected. (also Installed)
"C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\vsrepo.py" -p -b "C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\vapoursynth64\plugins" -s "C:\Users\bob\Desktop\VSRepoGUI\VSRepoGUI\bin\Debug\..\Scripts" -t win64 uninstall neo_fft3d

[ChaosKing]

I think I found the problem. When I remove the tqdm python module it WORKS!
Now the question is why it makes a difference since it works within visual studio too :/

[Myrsloik]

I think I found the problem. When I remove the tqdm python module it WORKS!
Now the question is why it makes a difference since it works within visual studio too :/

It's probably something like the difference between stdout/stderr being initialized or not. GUI applications don't need it but Visual Studio probably attaches them anyway so you can see output in the debugger.

[ChaosKing]

I also suspected something with stderr and turns out Win7 / tdqm are happy if I just add a RedirectStandardError = true. Thx for your help.

[ChaosKing]

@leon can you test if this build works for you?
https://www.dropbox.com/s/medu5e4zfwt5pt3/VSRepoGUI_win7fix.zip?dl=1

[lansing]

vsrepogui doesn't work for new vapoursynth version

[ChaosKing]

Try the new release.

[lansing]

New version works now.

ffms2 doesn't update to newest version
https://github.com/FFMS/ffms2/releases

[ChaosKing]

Because the ffms2 package was not updated on github yet. Try again.

[lansing]

Because the ffms2 package was not updated on github yet. Try again.

Yes it was updated now, took them 4 days wow.

[leon]

@leon can you test if this build works for you?
https://www.dropbox.com/s/medu5e4zfwt5pt3/VSRepoGUI_win7fix.zip?dl=1

It indeed works, thank you so much. And sorry for the late reply.

[Emulgator]

Win7U64SP1 with (hopefully) latest .net 4.8.03761, systemwide latest VC++ Redist 2019 (14.28.29325.2)

Trying VSRepoGUI.exe for the first time.
No matter if 32bit or 64 bit, starting VSRepoGUI.exe
from within Vapoursynth portable R52 with internally provided python3.8.7150 and VC++ runtime 2019 (14.28.29334.0) gives

Problemsignatur:
Problemereignisname: CLR20r3
Problemsignatur 01: VSRepoGUI.exe
Problemsignatur 02: 1.0.0.0
Problemsignatur 03: b514b7a2
Problemsignatur 04: VSRepoGUI
Problemsignatur 05: 1.0.0.0
Problemsignatur 06: b514b7a2
Problemsignatur 07: 118
Problemsignatur 08: 6a
Problemsignatur 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
Betriebsystemversion: 6.1.7601.2.1.0.256.1
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789


Ah, handediting vsrepogui.json to my portable path gives at least an assertion window "vsrepogui.json is invalid",
then after confirming the abovementioned crash report window pops up. Continuing.

[ChaosKing]

I will check later in my VM. How does your vsrepogui.json look like?
Avsrepogui.exe is in the same folder as the python.exe?

EDIT
Can you run "python vsrepo.py update" in console without problems?

[Emulgator]

Many thanks for looking into it ! Yes, vsrepogui is in the same folder as python.exe.
Just downloaded your Fatpack, it throws the same error, BTW.
Fatpack vsrepogui.json:
{
"Bin":"vsrepo.py",
"win32": {
"Binaries":"vapoursynth32\\plugins",
"Scripts":"..\\Scripts"
},
"win64": {
"Binaries":"vapoursynth64\\plugins",
"Scripts":"..\\Scripts"
}
}
My 32-bit standalone .json
(ATM I have no thorough understanding what "binaries" would address: the location of plugins or the VapourSynth.dll
and where this is an example of relative vs. absolute paths...
{
"Bin":"C:\\_PROG\\! Video Tools\\! VapourSynth32-Portable-R52\\vsrepo.py",
"win32": {
"Binaries":"abc d\\p32",
"Scripts":"..\\scripts"
},
"win64": {
"Binaries":"C:\_PROG_64\! Video Tools 64\! VapourSynth64-Portable-R52\\vsrepo\\abc d\\p64",
"Scripts":"C:\_PROG_64\! Video Tools 64\! VapourSynth64-Portable-R52\\vsrepo\\abc d\\scripts"
}
}

[ChaosKing]

Binaries = plugin path in this context (it overrides the vsrepo parameters: you can check with "vsrepo.py paths)


the \ char needs to be escaped. A valid version should look like this.
{
"Bin":"C:\\_PROG\\! Video Tools\\! VapourSynth32-Portable-R52\\vsrepo.py",
"win32":{
"Binaries":"abc d\\p32",
"Scripts":"..\\scripts"
},
"win64":{
"Binaries":"C:\\_PROG_64\\! Video Tools 64\\! VapourSynth64-Portable-R52\\vsrepo\\abc d\\p64",
"Scripts":"C:\\_PROG_64\\! Video Tools 64\\! VapourSynth64-Portable-R52\\vsrepo\\abc d\\scripts"
}
}

I tried the latest portable fatpack and it works in my test VM. It downloaded vspackages3.json in my root folder for some reason and I get the message "Could not read/download vspckages.json". I moved it to Vapoursynh64 folder and it started without problems.
I think I need a bat file which changes the directory first to avoid this problem.

"Clr20r3" error on google suggest that it could be a problem with the .net installation.

Btw. what is U in Win7U64SP1? Ultimate?

[lansing]

For some reason my vsrepogui couldn't open, I have both Python 3.8 and 3.9 installed with 3.9 being the default, while my vseditor is able to run without problem.

[ChaosKing]

See if the new version fixes it for you https://github.com/theChaosCoder/VSRepoGUI/releases/tag/v0.9.6

[lansing]

Nope it still doesn't open, it worked if I uninstalled Python 3.9

[ChaosKing]

I see the problem now.
vsrepo can't detect vapoursynth

.\python.exe .\vsrepo.py update
Could not detect vapoursynth
vsrepogui just assumes when python is found, vsrepo works correctly :D

=> But it should work in portable mode (not tested yet)

EDIT
portable mode works. Tested with python3.9 embed version.

vsrepogui.json
{
"Bin":"vsrepo.py",
"win32": {
"Binaries":"plugins32",
"Scripts":"Scripts",
},
"win64": {
"Binaries":"plugins64",
"Scripts":"Scripts",
}
}

[jinkazuya]

Does anybody have the detailsharpen plugin for StaxRip VapourSynth? I am just wondering how to import the plugin as well. Thanks.

[ChaosKing]

You can find a vs version here https://github.com/Selur/VapoursynthScriptsInHybrid/blob/master/G41Fun.py#L2885

Scipts are imported like this: import G41Fun as gf

and then can be used like this: clip = gg.DetailSharpen(clip)

You need to place G41Fun.py inside your python site-packages folder C:\Users\<USER>\AppData\Roaming\Python\Python38\site-packages

For Staxrip specific help ask in the Staxrip thread.

[jinkazuya]

You can find a vs version here https://github.com/Selur/VapoursynthScriptsInHybrid/blob/master/G41Fun.py#L2885

Scipts are imported like this: import G41Fun as gf

and then can be used like this: clip = gg.DetailSharpen(clip)

You need to place G41Fun.py inside your python site-packages folder C:\Users\<USER>\AppData\Roaming\Python\Python38\site-packages

For Staxrip specific help ask in the Staxrip thread.

Thanks for your help but I cannot see the python directory or folder and besides I do not know what to do with the script. I think I will ask in the Staxrip thread.

[lansing]

The program couldn't open with the new R59?

[ChaosKing]

It is most likely a vsrepo.py problem. Try running vsrepo.py in CMD first and see if it works. I had the same problem, not sure how I fixed it. I think I reinstalled python and/or R59.

[Emulgator]

Many thanks, ChaosKing !
Finally got it to work nicely.
It is end of 2022 and I can return to learning VapourSynth on a Win10Pro64 system.

Here comes the correct vsrepogui.json for my 2 portable installations.

{
"Bin":"C:\\_PROG\\! Video Tools\\! VapourSynth32-Portable-R61\\vsrepo.py",
"win32":{
"Binaries":"C:\\_PROG\\! Video Tools\\! VapourSynth32-Portable-R61\\vapoursynth32\\plugins",
"Scripts":"C:\\_PROG\\! Video Tools\\! VapourSynth32-Portable-R61\\vapoursynth32\\scripts"
},
"win64":{
"Binaries":"C:\\_PROG_64\\! Video Tools 64\\! VapourSynth64-Portable-R61\\vapoursynth64\\plugins",
"Scripts":"C:\\_PROG_64\\! Video Tools 64\\! VapourSynth64-Portable-R61\\vapoursynth64\\scripts"
}
}

Worth mentioning for newbies like me:
Having the VSRepoGUI "Search (x) Win64" ticked
searches the local 64bit installation and downloads the 64bit plugins and scripts into the 64bit installation.
Having the VSRepoGUI "Search ( ) Win64" unticked
searches the local 32bit installation and downloads the 32bit plugins and scripts into the 32bit installation.

P.S. Eek... 102 64bit plugins fell into the 32-bit installation, only 2 were correct 32bit.
On reload the situation improved: almost 100 correct. Ok, later..

[ChaosKing]

Worth mentioning for newbies like me:
Having the VSRepoGUI "Search (x) Win64" ticked
searches the local 64bit installation and downloads the 64bit plugins and scripts into the 64bit installation.
Having the VSRepoGUI "Search ( ) Win64" unticked
searches the local 32bit installation and downloads the 32bit plugins and scripts into the 32bit installation.

P.S. Eek... 102 64bit plugins fell into the 32-bit installation, only 2 were correct 32bit.
On reload the situation improved: almost 100 correct. Ok, later..

Maybe the view was not updated correctly. I never touch the checkbox since I only user 64bit :D (half of the plugins are only available for 64bit anyway!)


I could replace the checkbox with a dropdown [Auto, Win64, Win32 ] to avoid confusion 🤔

[Ironclad]

Installing havsfunc and muvsfunc did not install several dependencies. Havsfunc was installed without vsutil installing. Several muvsfunc plugins also did not install including: AWarpSharp2, Bilateral, CAS, CTMF, descale, TCanny, and likely many others. All are listed separately in Vsrepogui. VSrepogui was placed in the the pedeps bin directory with listpedeps.exe. Diagnose Problems did not recognize the missing dependencies.