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. |
17th May 2016, 12:35 | #1581 | Link |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Honestly, I wouldn't try to convince the community to rebuild all plugins with AviSynth+ 16-bit support until AviSynth+ itself is good enough to convince the majority of users to use it instead of v2.6
Which brings this question: are there still reasons for people to keep using AviSynth 2.6 at this point? |
17th May 2016, 13:01 | #1582 | Link | ||||
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
Quote:
Quote:
Quote:
I wouldn't convince anyone. We are still in the phase of convincing plugin writers to support the avs 2.6 color spaces as a minimum. |
||||
17th May 2016, 13:47 | #1583 | Link | ||||
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
Quote:
Quote:
Code:
SetFilterMTMode("nnedi3", 2) SetFilterMTMode("nnedi3_rpow2", 2) ColorBars() ConvertToRGB24() nnedi3_rpow2(2) Prefetch(4) Quote:
Quote:
Last edited by Reel.Deel; 29th May 2016 at 12:39. Reason: link |
||||
17th May 2016, 20:19 | #1584 | Link |
Registered User
Join Date: May 2015
Posts: 18
|
Just a random note, I have done a first full 64 bit encode with
sanimebob() srestore(omode=4, cache=10).srestore(frate=23.976) smam() Only thing that was missing really is GrunT plugin x64 build. I have made one and posted in appropriate thread. Perhaps someone can add it to the wiki. |
17th May 2016, 20:32 | #1585 | Link | ||||
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
I have no clue if anyone else (tp7?) has commit privileges to the main repo; because it would make things a lot easier if more than one person had the ability to push and were more easily contacted, just in case. Worse comes to worst, a new organization and repo setup would be needed to make sure there's always someone to commit (I could do that, I just would prefer not to until there's no other choice). And remember when cleaning up that AviSynth+ uses four white spaces for indentation, not tabs. Quote:
The non-MSVC compiler thing would mostly be when targeting non-Windows. Linux and OSX support in particular (clang is OSX's and FreeBSD's default compiler). Quote:
*somewhere around 56 commits; but after the fork happened, Plus development rocketed forward with several hundreds of commits in a very short timeframe. And then Plus entered a hiatus for about a year, then another sprint of activity in March 2015, and that's more or less where we are today. In the wake of 2.6's RC1 and RC2/RC3/Final updates, I've taken the CVS history, compared it against AviSynth+, determined to the best of my ability what can be merged, and opened a pull request containing those changes. The RC1 integration was what started things up again in March 2015, which eventually left off at r1825. RC2/RC3/Final was so meager that it still hasn't been merged (also, there was a bit of a back-and-forth about the issues of Plus' changes to avisynth.h during the restricted license era and moving them up into the restored-clause header; the C interface header, avisynth_c.h, never had this problem - it's completely unique to the C++ interface AviSynth traditionally focused on). Quote:
The problem isn't actually the code, it's the fact that the main AviSynth API was written in C++ as well, which means that C++ plugins have to be built with the same compiler as the core or else they'll fail to load. This stems from VC++ and g++ not being compatible with each other's addressing and name mangling and all sorts of other things. For plain C, cl and gcc are [mostly?] compatible, and is why the C interface exists. At least what I hoped (and the talk seemed to be leaning toward) was that any new AviSynth+ APIs would be written in C or the C interface would be mainlined and focused on (especially with a potential move to Linux/OSX), which would erase the portability problem from the start. The C++ problem doesn't matter on non-Windows, though, since they don't have the VC++/g++ divide to worry about. The intrinsics issue has less to do with whether it will build and far more to do with not causing grief for users with even slightly older computers to use them. It was also specifically in regard to building with GCC; if Clang truly does not require the same 'intrinsics must be split' nonsense, then dealing with them is not the dealbreaker for cross-platform support that it is with GCC. The intrinsics themselves are portable; in fact, they replaced the extremely non-portable SoftWire assembly that classic AviSynth relies on (and improved performance over SoftWire in most cases as well). |
||||
18th May 2016, 00:11 | #1586 | Link | ||
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
Quote:
Quote:
Official Avisynth development is as dead as a doornail. You don't need to care about what happens with it. You don't even need support its plugins if you don't want to (but you can if you want to; if VS can fake the plugin interface so can you). Fork away - there are already like five commonly used variants competing for attention so one more can hardly hurt. Last edited by TheFluff; 18th May 2016 at 00:15. |
||
18th May 2016, 05:38 | #1587 | Link | |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Quote:
If you create a custom interface for AviSynth+, I think it is very unlikely that plugin developers will get back in the game years after they wrote their plugin to support the new interface. Working on porting those plugins to VapourSynth would be a better path for them. But then VapourSynth has these limitations: - No ffdshow support for SVP - No audio support yet - Limited library of plugins In which cases AviSynth+ comes to the rescue. |
|
18th May 2016, 05:59 | #1589 | Link |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Bug: NNEDI3 simply doesn't work with MT. It causes image corruption.
Code:
SetFilterMTMode("DEFAULT_MT_MODE", 3) #neither 2 nor 3 works AviSource("Preview.avi", audio=false, pixel_type="YV12") nnedi3_rpow2(2, Threads=1) Prefetch(8) |
18th May 2016, 06:19 | #1590 | Link | |
Registered User
Join Date: Jan 2010
Posts: 270
|
Quote:
|
|
18th May 2016, 08:33 | #1591 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
Code:
AviSource("Preview.avi", audio=false, pixel_type="YV12") nnedi3(dh = true, Threads=1) fturnleft() nnedi3(dh = true, Threads=1) fturnright() Prefetch(8) |
|
18th May 2016, 08:41 | #1592 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
|
|
18th May 2016, 09:04 | #1593 | Link | |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Quote:
edi_rpow2 works though. |
|
18th May 2016, 09:33 | #1594 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
Sorry, but not realy. I don't see anything suspcious in the code, but and all the MT thing is not realy my stuff.
I think the code for nnedi3_rpow2 is linear (and clear i hope...) enough to reproduce all the steps/functions used in an avs script, if someone want to investigate. |
18th May 2016, 12:45 | #1596 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
In that case, it probably also happen in YV411 and YUYV.
As it can easely be seen in the code, there is two paths : (RGB24,YV24,Y8) and (YV16,YV12,YV411,YUYV). The only major difference between them it's that in case of YV16 and others, planes are extracted and processed separately. But again, i see absolutely nothing wrong. If the MT mode is not happy with the way i do things, you'll have to explain me where and why. The code is avaible on github, so anyone is free to take a look. |
18th May 2016, 14:37 | #1598 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
|
|
18th May 2016, 17:06 | #1599 | Link | |
typo lover
Join Date: May 2009
Posts: 595
|
Interesting information was written on comment space of this page by Takuan (Oh, he is my internet friend).
http://archive.fo/DvrEB Quote:
So you should use user script function instead of nnedi3_rpow2 when you want to set prefetch() if my guess is correct.
__________________
my repositories Last edited by Chikuzen; 18th May 2016 at 19:17. |
|
18th May 2016, 18:29 | #1600 | Link |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
Interesting information chikuzen. I saw that too when I asked about the force parameter in SetFilterMTMode, I didn't quite understand it though. The MPEG2Source issue was fixed so maybe there's hope for nnedi3_row2. More information here: https://github.com/AviSynth/AviSynthPlus/issues/37
|
|
|