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. |
22nd June 2016, 07:41 | #1781 | Link | |||
AVS+ Dev
Join Date: Aug 2013
Posts: 359
|
Quote:
Quote:
Quote:
__________________
AviSynth+ Last edited by ultim; 22nd June 2016 at 07:44. |
|||
22nd June 2016, 08:40 | #1782 | Link | |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Quote:
I use it for - SVP live video conversion to 60fps - Auto-attune video playback from 440hz to 432hz - Video/audio processing and encoding Out of all this, so far, VapourSynth can only do video processing and encoding. And that has nothing to do with the limited set of plugins available in it. That's just my personal situation -- AviSynth can't be replaced at this point. |
|
22nd June 2016, 11:51 | #1783 | Link |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
I prefer Avisynth myself, I guess I'm not used to Vapoursynth.
There's a consideration for Avisynth in that legacy support should be offloaded, and have Avisynth primarily 'clean'. Basically to use a plugin requiring legacy support, you call the plugin for legacy support plugin commands, like: legacyplugin(dooflakey(str=2.5)) Ideally thought the legacy plugins should be updated, not Avisynth. It's coming up to 2017, really should only be using 64-bit anyway . That would probably make things a lot easier if only the 64-bit side of things were developed, and have the corresponding plugins updated. |
22nd June 2016, 13:01 | #1784 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
Wouldn't it be pretty straight forward to just fork it, have a legacy branch that receives whatever updates Avisynth gets, plus any easily portable updates and one branch where everything goes it's own way.
Last edited by ryrynz; 22nd June 2016 at 21:58. |
22nd June 2016, 13:56 | #1785 | Link |
Acid fr0g
Join Date: May 2002
Location: Italy
Posts: 2,577
|
Image corruption with AviSynth+
As pinterf is now an active contributor, I feel it is time to submit again an old problem I introduced months ago.
Here is the original sample from BD. When I apply the following script, using AviSynth 2.6 MT, I have good encodings. 13HoursAV26.dgi PHP Code:
When I use AviSynth+, I have image corruption. 13HoursAVS+.dgi PHP Code:
prefilter=2 OK prefilter=3 OK prefilter=4 CORRUPTION Memento: PHP Code:
Results does not change. The plugin versions I use are the following for both AviSynth and AviSynth+. PHP Code:
Ideas? Fixes? P.S.: Previous post is here.
__________________
@turment on Telegram Last edited by tormento; 23rd June 2016 at 12:56. |
22nd June 2016, 14:06 | #1786 | Link | |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
Quote:
Anyways, lets get back on topic. |
|
22nd June 2016, 16:33 | #1787 | Link |
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
I haven't contributed to any open source projects in many years now. In fact I don't even code for a living anymore, I've switched careers. I don't use Avisynth or Vapoursynth myself either since I don't encode any video anymore and haven't done so for at least four or five years. For some reason though I still hang around with people who do work with these things and for some reason I still care. You are of course always free to disregard my opinions on any grounds you prefer.
To be clear, when I'm talking about pinterf's insane things, I'm referring to the recent problems with eval() having to be treated as a MT_NICE_FILTER. This is of course patently insane, eval() isn't a filter and should be seen as a component of the script parser, but nope, this is what you get for trying to tack on multithreading to a hobbyist project from the 90's. The amount of "cleverness" (to put it nicely) required to keep it working in all cases just keeps growing until you have a completely unmaintainable mess. What the Avisynth community definitely needs the least these days is more fragmentation. It's been pretty bad for many years with all the different MT versions and official versions and Avxsynth and god knows what else, but at least they had compatible plugins and script interpreters. When pinterf showed up I thought it was going to take yet another alarming turn for the worst with another fork and new version but fortunately that didn't happen. Instead, though, we now have, what, five different MVTools versions? Jeez, people, consolidate! I really don't think the plugin interface thing is such a huge deal either, it should be fairly easy to write wrappers to let you load other/older plugin interface versions in Avs+. Just ignore the "official" version IMO - you have the userbase on your side, the people who are still using the official version today are the kind of people who are still using Windows XP and are likely never going to upgrade either Avisynth or their plugins or their computers, even if a new version actually was released. 2.5.0 was released in 2003, 2.5.8 in 2008 and 2.6 last year, so at this rate, if you want a "final" 2.6 in the style of 2.5.8, expect to wait until 2020, and for "2.7" you're going to have to wait at least until 2027 or so. There's no point in trying to have a half-hearted fork that doesn't even attempt to supplant the parent project, either. Aim for the stars. Last edited by TheFluff; 22nd June 2016 at 16:41. |
22nd June 2016, 16:38 | #1788 | Link |
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
Out of curiosity, what plugins are you missing in VS? Also, are you aware it can load Avisynth plugins? I'm not trying to sell you a bridge or anything, I just believe you have a mistaken view of the state of VS.
|
22nd June 2016, 17:13 | #1789 | Link | |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Quote:
Code:
P="Encoder\" LoadPlugin(P+"LSMASHSource.dll") LoadPlugin(P+"TimeStretch.dll") file="INNA\In Your Eyes.mkv" LWLibavVideoSource(file, cache=False) AudioDub(LWLibavAudioSource(file, cache=False)) Preroll(int(FrameRate*3)) ResampleAudio(48000) TimeStretchPlugin(pitch = 100.0 * 0.98181819915771484) As for "MT not working", I just realized something. There are two types of plugins out there. There are stand-alone plugins that just require a DLL to work, and there are "throw it all on the wall"-type plugins that depend on a chain of plugins that each depend on another chain of plugins. The first type is generally very stable with MT. The second type is not. I was experimenting with SMDegrain and was surprised by the results, especially when combined with KNLMeans. This did a great job on my SD videos and worked with MT. Code:
SMDegrain(thsad=2000, contrasharp=true, lsb_in=true, lsb_out=true) That's not an issue with AviSynth+ MT; but these plugins that depend on a whole chain of other plugins tend to be very unstable. |
|
22nd June 2016, 17:21 | #1790 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
__________________
See My Avisynth Stuff |
|
22nd June 2016, 20:42 | #1791 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
The binary compatibility stuff is really the smallest problem. You can always write a shitty wrapper. See the VapourSynth compatibility code on how to wrap things to something not completely identical.
Btw, the size_t thing is also possibly the smallest problem ever. I just realized that I'd implemented my own x64 compatility with the plain 2.6 header. Guess what? IT WROKSKSKSSS!!!!!!!1111 So just recompile everything with a 2.6 header and you're good. Btw, TheFluff is the chief VS evangelist so you have to respond to all his trolling. No excuses. And in regards to VS and plugins. I believe all popular unported plugins should work using the avisynth compatibility. If you find one that doesn't just post about it and I'll take a look.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
22nd June 2016, 21:55 | #1792 | Link | |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Quote:
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? |
|
22nd June 2016, 22:06 | #1793 | Link | |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
Quote:
|
|
22nd June 2016, 23:31 | #1794 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
*and when it hadn't been updated with cvsimport in a while, I went ahead and pushed up a classic_avisynth branch into my personal avsplus repo that exists alongside MT and co. Last edited by qyot27; 22nd June 2016 at 23:38. |
|
22nd June 2016, 23:59 | #1795 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
I find myself asking why IanB would not want to sit back and relax, if others are prepared to take what has been achieved and carry it forward, great,
Ian deserves a rest and to watch whilst others add to his baby, no way should it be perceeived as anything less than total success, because that is what it is. For myself I could not desert the current official state, and would I think not do so, but I do recognise the vigour of the new pretenders. I dont know why Ian has chosen to isolate himself from the world, I at one time had my suspicions as to why, but rightly or wrongly, it is the path he has chosen to take, however isolation cannot be good for anyone here. One cannot oversee or steer from afar something akin to Avisynth, perhaps Ian should forgo his ownership of avs and let the new lads have a go. Above was so very hard for me to say.
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? |
23rd June 2016, 01:21 | #1796 | Link | |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
Quote:
I'm discussing that issue in this thread
__________________
FrameRateConverter | AvisynthShader | AvsFilterNet | Natural Grounding Player with Yin Media Encoder, 432hz Player, Powerliminals Player and Audio Video Muxer Last edited by MysteryX; 23rd June 2016 at 02:39. |
|
23rd June 2016, 09:48 | #1797 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
Why? Because these fields are accessed through methods instead of direct reference? I suppose it would break in a plugin running under avs+ x64 if we used avs 2.6 header and access pitch instead of calling GetPitch()? Code:
int GetPitch(int plane = 0) const AVS_BakedCode(return AVS_LinkCall(GetPitch)(plane)) Code:
class VideoFrame { public: volatile long refcount; VideoFrameBuffer* const vfb; const size_t offset; const int pitch, row_size, height; const size_t offsetU, offsetV; // U&V offsets are from top of picture. const int pitchUV, row_sizeUV, heightUV; Code:
class VideoFrame { volatile long refcount; VideoFrameBuffer* vfb; // Due to technical reasons these members are not const, but should be treated as such. // That means do not modify them once the class has been constructed. int offset, pitch, row_size, height, offsetU, offsetV, pitchUV; // U&V offsets are from top of picture. int row_sizeUV, heightUV; |
|
23rd June 2016, 11:19 | #1799 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Can you upload your exact source somewhere (the dgi one, not the .264 - I was stuck how to convert it)
Then it would be much help if you stripped down the script until the corruption disappear. (Change parameters, uncomment SMDegrain internals). This is how I would start. Does it happen when you convert your source and not using dgi? |
23rd June 2016, 11:27 | #1800 | Link | |
Acid fr0g
Join Date: May 2002
Location: Italy
Posts: 2,577
|
Quote:
Please look original thread and see all the trials I did. Will try to strip down things. As far as I remember, I could even use prefilter 2 instead of 4 or x86 vs x64 and nothing changed.
__________________
@turment on Telegram |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|