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. |
26th January 2019, 19:33 | #3221 | Link | |
Registered User
Join Date: May 2004
Posts: 324
|
Quote:
clip = core.resize.Bicubic(clip, format=vs.RGB24) You could also Use this: clip = core.fmtc.resample (clip, css="444") clip = core.fmtc.matrix (clip, mat="709", col_fam=vs.RGB) clip = core.fmtc.bitdepth (clip, bits=8) |
|
26th January 2019, 22:43 | #3222 | Link |
Registered User
Join Date: May 2011
Posts: 321
|
Yes, I wanted to bring up if anyone makes this line it freezes and crashes, because Vapoursynth takes 2000010 (id for vs.RGB24) as width.
Argument width, does not have to be explicitly stated, width=something. But that resize is quite complex thing. Color spaces conversions etc., maybe it should be mandatory to state width=something, format=something. Not gravely important, sure. This is one of those things to repel newcomers to use Vapoursynth. Resize is almost used in every script. So format has to be specified, but not width, not a consistent somehow. It is hard to understand if you are a video guy, not a programmer. But again, I do not expect this to be fixed, I take it as a flag if someone googles it or whatever. Last edited by _Al_; 26th January 2019 at 22:45. |
26th January 2019, 23:40 | #3224 | Link |
Registered User
Join Date: May 2011
Posts: 321
|
I understand that. It took me some hours though to figure that out last year. It takes that value from props, if it is usable, it uses it. Sometimes it is in props , sometimes not, it depends if source filter registers that taking it from video. If not , it has to be specified, if it is needed and not specified error is returned. Which in a sense is great, because we do not want to have any defaults in background going on. If those values loaded by source plugin taken from video are correct ones is another issue of course.
Also values in props are numerical (int) and to get corresponding string value, other script lines are needed to put it on screen. Which you of course can mess you up if you are learning it. :-) matrix table of numerical values with corresponding string values: Code:
matrix_ITU = {0:'rgb', 1:'709', 2:'unspec', 3:'reserved', 4:'fcc', 5:'470bg', 6:'170m', 7:'240m', 8:'ycgco', 9:'2020ncl', 10:'2020cl' , 100:'OPP', } matrix_USABLE_ITU = ['709', 'fcc', '470bg', '170m', '240m', 'ycgco', '2020ncl', '2020cl', 'OPP'] page 430 Table E.5 Matrix coefficients interpretation Last edited by _Al_; 27th January 2019 at 00:19. |
27th January 2019, 01:55 | #3226 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
video,848,480,vs.RGB24 = this will work video,vs.RGB24 = this won't work AviSynth works exactly the same way concerning parameter order - if you drop one parameter in the middle, everything after that requires explicitly declaring the parameter name too for the values to be set to the right option. The actual source of the immediate crash is that resizing to 2 million pixels wide is going to cause problems *somewhere* in the chain. |
|
1st February 2019, 13:01 | #3228 | Link | |
unsigned int
Join Date: Oct 2012
Location: 🇪🇺
Posts: 760
|
Quote:
http://www.vapoursynth.com/doc/plugins/subtext.html
__________________
Buy me a "coffee" and/or hire me to write code! |
|
1st February 2019, 15:11 | #3229 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
I tried to whip out the old SupTitle.dll (as I remembered it can do 'relocation'), but that wouldn't run somehow: core.avs.LoadPlugin ("C:/VS/plugins/SupTitle.dll") Should still work, right?! EDIT: Yeah, that's an old 32-bit filter. Nevermind.
__________________
Gorgeous, delicious, deculture! Last edited by asarian; 1st February 2019 at 16:24. |
|
2nd February 2019, 02:25 | #3230 | Link |
Registered User
Join Date: Sep 2006
Posts: 1,657
|
Would it be a good idea for vapoursynth to implicitly set the value of an argument to its default value when we declared it without giving it a value? Something like this
Code:
fm = core.vivtc.VFM(clip, order) Code:
fm = core.vivtc.VFM(clip, order=0) # assuming 0 is the default |
3rd February 2019, 13:07 | #3231 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,731
|
I was trying to load pinterf's MVTools2 build in Vapoursynth, but the functions don't appear in the avs namespace (using core.avs.MAnalyze just says that the function doesn't exist). I get this error in the VapourSynth Editor log, is it the reason?
Avisynth Compat: varargs not implemented so I'm just gonna skip importing MStoreVect
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
3rd February 2019, 18:47 | #3232 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Quote:
You can probably grab the avscompat.dll from R39 and use that if you really want to test things though.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
3rd February 2019, 19:51 | #3233 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,731
|
Thanks, looks like I'll skip it then. I was just thinking about testing it in case Zopti starts crashing the native plugin which probably doesn't have all the fixes and tweaks from the AVS version. It's been quite some time since the last commit.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
3rd February 2019, 20:03 | #3234 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Just report the bugs you find and they should probably get fixed quite quickly.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
3rd February 2019, 22:26 | #3235 | Link |
Registered User
Join Date: Jul 2012
Posts: 1,213
|
|
3rd February 2019, 23:04 | #3236 | Link | |
Registered User
Join Date: Mar 2018
Posts: 447
|
Quote:
I have another issue open, hopefully that one can be fixed as well. But I totally understand it can take time, the author is doing this on his free time after all. |
|
4th February 2019, 05:32 | #3237 | Link |
Registered User
Join Date: Oct 2015
Posts: 29
|
Hello,
May I ask if there is some kind of guide or documentation to help me make VapourSynth work with PotPlayer (more specifically, with madVR/SVP)? I have been researching this for days; I run multiple different installations of both VapourSynth and PotPlayer, seemingly appropriate, but I simply cannot make it work with PotPlayer itself, and of course not with anything else - I have no idea what I am missing. Sorry to bother, and I am sorry if this is not the right place to ask. Thanks. |
12th February 2019, 07:31 | #3238 | Link | |
Registered User
Join Date: Oct 2009
Location: crow-land
Posts: 540
|
Intel claim to speed up python runtime by 20x, for free
https://www.infoworld.com/article/33...lq_cid=4495538 Quote:
Cheers |
|
12th February 2019, 11:17 | #3239 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
__________________
Gorgeous, delicious, deculture! |
|
13th February 2019, 14:17 | #3240 | Link |
Registered User
Join Date: May 2009
Posts: 184
|
Vapoursynth newbie here.
Can anyone help me get this bbmod AVS port to work please? I assume it should be something along the lines of the below syntax but with the correct instruction to replace the *? clip = core.*.bbmod2(c, cTop = 0, cBottom = 0, cLeft = 0, cRight = 0, thresh = 128, blur = 999) Thanks. |
Tags |
speed, vaporware, vapoursynth |
Thread Tools | Search this Thread |
Display Modes | |
|
|