Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
4th December 2023, 18:14 | #463 | Link |
Registered User
Join Date: Jun 2007
Posts: 414
|
Added VapourSyth Editor r19 mod 6.3 and it will require macOS 10.15 or newer. I have combined Job Server and Job Server watcher into the same app so that it's easier to use and I also included a script to create links to enable vsedit-previewer so that it is accessible from Terminal.
Last edited by l33tmeatwad; 4th December 2023 at 21:12. Reason: Updated information |
30th December 2023, 18:03 | #464 | Link |
Registered User
Join Date: Apr 2013
Posts: 25
|
I've compiled a few of the plugins and scxvid-standalone (Apple Silicon).
Some of the plugins I couldn't compile (errors here and there...) I have tested scxvid-standalone and it works fine. I didn't have time to test the plugins yet. Plugins Last edited by anonymlol; 31st December 2023 at 17:47. |
3rd January 2024, 17:09 | #465 | Link | |
Registered User
Join Date: Jun 2007
Posts: 414
|
Quote:
|
|
3rd January 2024, 18:53 | #466 | Link |
Registered User
Join Date: Apr 2013
Posts: 25
|
I really should have read your setup post till the end. Thanks for the advice. I'll read up on it and try again.
Can you tell me how you compiled VSEdit? Whenenver I compile it, it's full of bugs and can't find the library/plugins directory. I'm also getting an error when compiling libass (following your guide). Something about the 'freetype' version being too low. |
3rd January 2024, 19:54 | #468 | Link |
Registered User
Join Date: Apr 2013
Posts: 25
|
I tried brew, but then it also wouldn't find the plugins even though I followed the instructions in your first post.
Your installer is the only thing that works. Even compiling VapourSynth + VSEdit myself (following your guide), it can't find/load the plugins. |
4th January 2024, 18:14 | #470 | Link |
Registered User
Join Date: Apr 2013
Posts: 25
|
I see, maybe I made a mistake somewhere with the folders. I'll experiment a bit.
The installer creates the folders in a different location than your instructions on the first post. Maybe I should try the same location as the installer. Installer folder locations: Code:
VS Plugins /Library/Frameworks/VapourSynth.framework/lib/vapoursynth VS Scripts /Library/Frameworks/VapourSynth.framework/lib/python3.11/site-packages VS Libraries /Library/Frameworks/VapourSynth.framework/lib VS Executables /Library/Frameworks/VapourSynth.framework/bin Code:
ln -s /usr/local/lib/vapoursynth $HOME/Desktop/VapourSynth/Plugins ln -s /usr/local/lib/python3.9/site-packages $HOME/Desktop/VapourSynth/Scripts |
4th January 2024, 18:17 | #471 | Link |
Registered User
Join Date: Jun 2007
Posts: 414
|
So /usr/local/lib/VapourSynth is the default autoload path. Normally I'll create a symbolic link because I create a framework as opposed to a regular install so updates don't break the install.
EDIT: I just realized you left out the first part for brew users: Code:
mkdir -p /usr/local/lib/vapoursynth mkdir -p "$HOME/Library/Application Support/VapourSynth" touch "$HOME/Library/Application Support/VapourSynth/vapoursynth.conf" echo UserPluginDir=/usr/local/lib/vapoursynth >> "$HOME/Library/Application Support/VapourSynth/vapoursynth.conf" echo SystemPluginDir=/usr/local/lib/vapoursynth >> "$HOME/Library/Application Support/VapourSynth/vapoursynth.conf" Last edited by l33tmeatwad; 4th January 2024 at 19:00. Reason: Updated |
4th January 2024, 21:45 | #472 | Link | |
Registered User
Join Date: Apr 2013
Posts: 25
|
Yeah I skipped it on purpose because I didn't want to make the post unnecessarily long.
I'll have a closer look at everything when I have more time. For now I'd like to share my new (quick and dirty) script to automate the first part of your guide (setting up tools). I'll do the rest (setting up the vs framework) later. edit: updated script is now on github edit2: finally done on the script to build vapoursynth framework, see here edit3: libass works now, it failed before because it was missing: PKG_CONFIG_PATH=/Library/Frameworks/VapourSynth.framework/lib/ Btw, VSEdit still throws errors. The folders and links are created via the script according to your instruction post. Quote:
Last edited by anonymlol; 12th January 2024 at 12:43. |
|
17th January 2024, 22:19 | #473 | Link | ||
Registered User
Join Date: Apr 2013
Posts: 25
|
From your post here
Quote:
Quote:
The vapoursynth.conf file doesn't help either. And I noticed your installer doesn't even create it. How did you solve the autload issue? Or did you do something special when compiling vsedit? Last edited by anonymlol; 17th January 2024 at 22:43. |
||
22nd January 2024, 15:45 | #474 | Link |
Registered User
Join Date: Jun 2007
Posts: 414
|
Ah, yeah that is a mistake, I'll get that fixed up. As for you script, I'll try to take a look over it soon, been super busy lately so it might take a minute to look into, nothing is looking super off from the quick glance I took.
|
Tags |
meatwadismagical, meatwadthegreat |
Thread Tools | Search this Thread |
Display Modes | |
|
|