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. |
30th May 2019, 19:26 | #1 | Link |
Registered User
Join Date: Dec 2018
Posts: 140
|
Can it has native compatibility with avisynth syntax?
I know that it can use avisynth libraries, but what about script?
In this case you could use avisynth code natively and then use variables values in python script. Like AvisynthCode{ %your avisynth code% } %Python code with avisynth variables% It needs python->avisynth equal alliases for same things. May be it's possible now, maybe no and it looks crazy, but even Avisynth 'IDE' on Python, so... Imho python is too complex and obviously avisynth still more popular than VS. Avisynth has 2 active pages of threads, VS has 3 times less If vs gives maximum compativility with avisynth, you just can move from avs to vs. Now VS is just bloatcode and bloatware which needs another bloatwares. For using avisynth you just need one dll/MS components, for VS you need heavy installer, you must have and download python with hands, included onine installer/direct link/libraries - vs does not have it. Also, you need not only python, but x86/x64 python. If you have X86 python, only x86 vs will be installed. If you wanna use x64 player, then you need to find and download it again, install it, launch vapoursynth installer again and install x64 python %) . I can be wrong, I tried to install vs month ago, it was strange quest for just installing. After some time vapoursynth crashed Last edited by Dreamject; 30th May 2019 at 19:54. |
30th May 2019, 21:50 | #2 | Link |
Registered User
Join Date: Sep 2010
Location: Ukraine, Bohuslav
Posts: 377
|
VS needs more dependencies and probably not that user-friendly, but it looks like solid and complex video processing solution for me.
Python actually isn't that complex, just try to spend some time for learning things. VS isn't guaranteed to provide maximum compatibility. Native plugins are always better. If you think it's all bloat, just stick with AVS. It's obvious that you can't mix x86/x64 binaries, so your entire chain must be x64 (python, VS, player). AVS is also affected by that limitation. You also can pick portable python and portable VS if you don't like the idea of installing software onto your machine. |
30th May 2019, 22:52 | #4 | Link | |
Registered User
Join Date: Dec 2018
Posts: 1
|
Quote:
Code:
(mask > 1) ? mergeluma(c, aaclip) : ((mask > 0) ? mt_merge(c, aaclip, msk) : aaclip) |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|