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.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Usage

Reply
 
Thread Tools Search this Thread Display Modes
Old 14th November 2017, 19:08   #1  |  Link
Katie Boundary
Registered User
 
Katie Boundary's Avatar
 
Join Date: Jan 2015
Posts: 493
AVXsynth isn't working

On my Linux system, I've successfully compiled and installed AVXsynth. I've dumped the relevant filters (DGdecode and TIVTC) into the AVXsynth plugins directory. I've adjusted the paths in the .D2V files to match where Linux thinks the VOB files are. And... it still doesn't work. Here's an example of the error:

Quote:
VLC can't recognize the input's format:
The format of 'file:///media/wds/Northrend/Ripped/Video/Stargate%20SG-1/401.avs' cannot be detected. Have a look at the log for details.
(Northrend is one of my external hard drives)

I also don't know what log file it's looking for.
__________________
If I ask "How do I do X?" or "what happens if I do X?", and X is a very bad thing that no one would ever normally do, assume that I already know this, and that I have Katie reasons for asking anyway.
Katie Boundary is offline   Reply With Quote
Old 14th November 2017, 20:20   #2  |  Link
qyot27
...?
 
qyot27's Avatar
 
Join Date: Nov 2005
Location: Florida
Posts: 889
1) AvxSynth does not support Windows .dll plugins. And there were only ever maybe 5 or 6 plugins ever ported to it natively. The only source filter for AvxSynth is FFMS2 (clone from the upstream FFMS2 repo, checkout the c_plugin branch, and use --enable-shared --enable-avxsynth), and you have to have a libavformat-based player that was built with --enable-avisynth (FFmpeg) or --enable-avxsynth (Libav; requires AvxSynth to have been installed first).

2) VLC force-disables AviSynth support in their FFmpeg contrib Makefile (I have no idea why; the mailing list email doesn't say anything specific about why it got disabled, except musing about static linking and writing what would be a third demuxer for it, although I'm not sure if they were aware of that). You have to override that when building VLC manually, and then hope there's nothing else that explicitly blocks it from working correctly, like weird dynamic loading rules or rejecting plaintext files as input.


AvxSynth development has been dead for 3+ years now, and still exists mostly as a novelty - its one legitimate achievement was correctly rewriting the AviSynth demuxer in libavformat to be sane. At least on Ubuntu and Debian, ffmpeg (and ffplay by extension), enables support for it by default, and the repo mpv build it's linked against should be able to open the scripts as well. But there's not really much AvxSynth can do, as you're limited to the core filters (many of which had their assembly disabled, so they'll probably be slower than their Windows counterparts). And since it's a port of AviSynth 2.5.8, there's no support for YV24, YV16, Y8, or YV411.

Use VapourSynth if you need native support, or use AviSynth+ under Wine and pipe out to native encoders if you need existing plugins and scripts to work.
qyot27 is offline   Reply With Quote
Old 14th November 2017, 21:20   #3  |  Link
Katie Boundary
Registered User
 
Katie Boundary's Avatar
 
Join Date: Jan 2015
Posts: 493


Quote:
Originally Posted by qyot27 View Post
VLC force-disables AviSynth support in their FFmpeg contrib Makefile
The scripts weren't working in Tsunami MPEG Encoder (running through Wine) either.

Quote:
Originally Posted by qyot27 View Post
AvxSynth development has been dead for 3+ years now
Is that why the installation instructions refer to ffmpeg 0.11 when the latest version is 3.4?
__________________
If I ask "How do I do X?" or "what happens if I do X?", and X is a very bad thing that no one would ever normally do, assume that I already know this, and that I have Katie reasons for asking anyway.
Katie Boundary is offline   Reply With Quote
Old 15th November 2017, 01:34   #4  |  Link
qyot27
...?
 
qyot27's Avatar
 
Join Date: Nov 2005
Location: Florida
Posts: 889
Quote:
Originally Posted by Katie Boundary View Post
The scripts weren't working in Tsunami MPEG Encoder (running through Wine) either.
Wine only talks to the host system through pipes, so of course AvxSynth wouldn't work with it. You have to install a Windows build of AviSynth under Wine to have Wine programs recognize it directly.

Quote:
Is that why the installation instructions refer to ffmpeg 0.11 when the latest version is 3.4?
Yup. Although those instructions were outdated for a while before AvxSynth died, too.
qyot27 is offline   Reply With Quote
Old 15th November 2017, 08:19   #5  |  Link
Katie Boundary
Registered User
 
Katie Boundary's Avatar
 
Join Date: Jan 2015
Posts: 493
Quote:
Originally Posted by qyot27 View Post
Wine only talks to the host system through pipes
So you're saying Wine is...



...a series of tubes?

Quote:
Originally Posted by qyot27 View Post
You have to install a Windows build of AviSynth under Wine to have Wine programs recognize it directly.
Wait, what? That's POSSIBLE? But AVIsynth isn't an executable that you can run. It just sort of sits in the background and tricks the OS into treating text files as video files. Are you saying that, if I run the installer through Wine once, AVIsynth itself will forever run through Wine without me needing to tell Linux to do that?

Edit: it appears to work, in the sense that AVIsynth is at least functional enough to be reporting errors of its own. The main problem now seems to be getting the D2V files to point at the VOB files in a way that ALL of the relevant software can understand. When I use "D:\ripped\video\etc", then Tsunami gives a "cannot open, or unsupported" error. When I use "/media/wds/Northrend/ripped/video/etc", then AVIsynth says "MPEG2source: could not open one of the input files". Is this fixable?

Edit 2: I tried just dumping the ripped files, the d2v file, and the avs file into .wine/drive_c/Ripped/ and pointing the d2v file there, and OMG IT WORKED! This is a slightly impractical workaround, however, because vob files are huge and my .wine folder is on a tiny 80gb hard drive. I'll see what other workarounds I can try.
__________________
If I ask "How do I do X?" or "what happens if I do X?", and X is a very bad thing that no one would ever normally do, assume that I already know this, and that I have Katie reasons for asking anyway.

Last edited by Katie Boundary; 15th November 2017 at 09:16.
Katie Boundary is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 00:50.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2017, vBulletin Solutions Inc.