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. |
20th December 2015, 00:28 | #1802 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
Here's R30 test1 with AVISYNTH 2.6 PLUGIN SUPPORT FOR BOTH 32 AND 64 BIT!!!!!111111
(no 2.5 plugin support for 64 bit stuff though) Code:
r30: planeaverage is now deprecated, use planestats instead added planestats, a function that calculates min, max, average and difference of a frame at the same time removed planedifference, deprecated since r28 added avisynth 2.6 and x64 support, note that x64 can only load 2.6 but not 2.5 plugins no longer installs vsvfw.dlls into system dirs added nfMakeLinear, this flag will make the immediately following cache do its best to make requests more linear, set it on source filters where seeking is slow the installer will no longer fail if a newer than expected version of the visual studio runtimes are installed vspipe now displays the correct number of total frames when -s is used
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
21st December 2015, 14:42 | #1805 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
Quote:
The spline resizers were also changed to be morr like the ones in avisynth than the swscale stuff.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
22nd December 2015, 10:42 | #1808 | Link |
͡҉҉ ̵̡̢̛̗̘̙̜̝̞̟̠͇̊̋̌̍̎̏̿̿
Join Date: Feb 2009
Location: No support in PM
Posts: 712
|
Ringing appears with a just few taps with sinc, because this kernel has a slow decrease. So if you feel the need use it, you want it with many taps.
__________________
dither 1.28.1 for AviSynth | avstp 1.0.4 for AviSynth development | fmtconv r30 for Vapoursynth & Avs+ | trimx264opt segmented encoding Last edited by cretindesalpes; 22nd December 2015 at 10:45. |
3rd January 2016, 21:54 | #1809 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
R30 RC1. The only thing left to do is to test imwri thoroughly and then I'll release it.
Try out all four 64 bit Avisynth 2.6 plugins and report your findings. Changes: Code:
r30: added half precision float input/output to expr on cpus that have the f16c extension (ivy bridge or later) added the possibility for plugins to print messages through the standard logging as well, don't use it unless you really have to the build system should now autodetect which optional libraries are available fixed ycocg conversions planeaverage is now deprecated, use planestats instead added planestats, a function that calculates min, max, average and difference of a frame at the same time removed planedifference, deprecated since r28 added avisynth 2.6 and x64 support, note that x64 can only load 2.6 but not 2.5 plugins no longer installs vsvfw.dlls into system dirs added nfMakeLinear, this flag will make the immediately following cache do its best to make requests more linear, set it on source filters where seeking is slow the installer will no longer fail if a newer than expected version of the visual studio runtimes are installed vspipe now displays the correct number of total frames when -s is used
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
6th January 2016, 16:20 | #1811 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
Why do you think it's hard to use? Example?
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
6th January 2016, 16:42 | #1812 | Link |
Registered User
Join Date: Nov 2011
Posts: 4
|
for example:
if Ymax < 180 do something with this frame else do something with this frame i dont know how to use current props to complete that. i am a rookie ripper and i dont know python at all... so i suggest to seperate min and max |
6th January 2016, 18:42 | #1813 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
Hint, it's an array:
Code:
if Yminmax[1] < 180:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
9th January 2016, 11:13 | #1815 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
It seems that the media-autobuild_suite supports compiling mpv with support for VapourSynth, but only if VapourSynth is installed. So I wonder, how would I install VapourSynth inside an MSYS2/MinGW building environment? I guess I would more or less follow Linux installation steps, but I don't know if MSYS2 prefers different package managers...
__ P.S.: VapourSynth installed in Windows is recognized only when it was installed to the default "Program Files (x86)" folder. In addition, it is not meant to recognize *.vpy files as media source now; but you might be able to use VapourSynth video filters inside mpv then (e.g. dare to apply QTGMC to a decoded video stream)... check if it is available: Code:
mpv -vf help Last edited by LigH; 9th January 2016 at 14:58. |
14th January 2016, 00:27 | #1816 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
Quote:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
14th January 2016, 00:34 | #1817 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
I made a portable version of VapourSynth for those of you who hate installing things. Simply get the appropriate embedded python and unzip VapourSynth in the same directory (overwrite existing files).
Obviously only vspipe works for output (vfw and vsfs require installed files). It's possible to use VapourSynth Editor if extracted into the python/vapoursynth dir as well. 64bit 32bit
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
15th January 2016, 11:52 | #1820 | Link |
Registered User
Join Date: Oct 2006
Location: Omicron Persei 8
Posts: 180
|
Is it normal that there is no auto completion for the core functions? Eg. for core.[TAB][TAB] or core.std.[TAB][TAB]
First I thought something is broken but print(core.get_plugins()) (and a manual formatting afterwards) showed me all available plugins, their names and functions and a simple tryout of core.lsmas.LibavSMASHSource() showed that it is actually available and working. I know it's Python but to be honest I'm not using VapourSynth to learn Python but as an replacement for AviSynth on Linux. The documentation definitely needs to be improved, eg. remove the Python reference and instead add a short howto of how users can find out how to load a given plugin as well as a list of basic functions like set_output() Currently most of the doc (even the one of each plugin) is written for Windows which is kind of useless because AviSynth is still much better and since VS is running inside of Python there shouldn't be a difference between VS on Windows and VS on Linux beside path formatting. I'm sorry for sounding ungrateful. I'm definitely not. I'm just a bit tired to trying things out when there could be a doc giving you hints so you know where to look (again, Python reference is not a hint). I actually made a build script that installs all dependencies (apt-get), grabs the latest sources for yasm, libenca, ffmpeg, x264, L-SMASH, etc. and builds these into your home directory so that you have a kind-of-portable user-installation of VapourSynth. It already builds without errors and VS is working but it's in preAlpha stage thus I haven't released it yet but definitely will. |
Tags |
speed, vaporware, vapoursynth |
Thread Tools | Search this Thread |
Display Modes | |
|
|