AvsPmod 2.5.1

[Keiyakusha]

It seems the margin is smaller than it should when the scrollbar is shown, I'll take a look at it.

Oops, please see my updated post. That's also the case with this zoom bug.
Also maybe you can make this margin dynamic to "compensate" for this bug?

[vdcrim]

Oops, please see my updated post. That's also the case with this zoom bug.
It also happens at 100% and with wxPython 3.0 so there's something else going on.
Also maybe you can make this margin dynamic to "compensate" for this bug?
I'd rather not, gui issues are already annoying enough to make it worse by adding hacks. Anyway I haven't given up on supporting wx 3.0, it just happens that I haven't been working on AvsPmod lately.

[LigH]

After a longer time, and after installing AviSynth+ in the meantime, I started using AvsPmod again. And now I wonder why the preview window always opens with a too small height. It seems that 16 pixels are always missing while calculating the required height to display the video frame plus the 5 pixel border. So I always have vertical scrolling.

Example 1: Video frame = 1280x720 + 5 pixel border around: client area height = 730 pixels; client window height = 697; horizontal scroller height = 17: difference = 16

Example 2: Video frame = 640x480 + 5 pixel border around: client area height = 490 pixels; client window height = 474; horizontal scroller height = 0: difference = 16

[fvisagie]

Have you tried right-click -> Zoom -> 100% | Fill window | Fit inside window etc.?

[fvisagie]

Hi vdcrim,

How do you feel about implementing timeline re-ordering, i.e. cut/copy & paste, including included bookmarks? I feel it would be a great help with any editing beyond basic cleaning up, especially when combining multiple sources.

Perhaps you could kick off with the ability to cut/copy & paste a single range selection at a time?

[LigH]

"Fit inside" shrinks the video; "Fill" does not expand the window to the video frame size but keeps the video frame behind the scroll area; I had it at "Zoom 100%", but this expands the window just even not enough to avoid scrollbars.

[vdcrim]

It seems that 16 pixels are always missing
If the window height is adjusted to the video + margins and then the horizontal scrollbar is needed (e.g. toggling the slider sidebar) then yes, a vertical scrollbar will also appear as the horizontal one takes space from the same window. However besides that I'm not having any extra scrolling here.

How do you feel about implementing timeline re-ordering, i.e. cut/copy & paste, including included bookmarks? I feel it would be a great help with any editing beyond basic cleaning up, especially when combining multiple sources.

Perhaps you could kick off with the ability to cut/copy & paste a single range selection at a time?

Something like this macro (https://gist.github.com/vdcrim/99d1aca217894bd527c7)? It cuts the current trim selections and pastes them after the current frame (bookmarks so far are untouched).

[fvisagie]

Something like this macro (https://gist.github.com/vdcrim/99d1aca217894bd527c7)? It cuts the current trim selections and pastes them after the current frame (bookmarks so far are untouched).

That's exactly it, except also for updating both moved and unmoved bookmarks as mentioned.

[LigH]

If the window height is adjusted to the video + margins and then the horizontal scrollbar is needed (e.g. toggling the slider sidebar) then yes, a vertical scrollbar will also appear as the horizontal one takes space from the same window. However besides that I'm not having any extra scrolling here.

Well, for me, it seems to be adjusted to (video + margins - 16). I wonder how one might be able to debug the reason for this mistake...

[vdcrim]

Well, for me, it seems to be adjusted to (video + margins - 16). I wonder how one might be able to debug the reason for this mistake...
I haven't been able so far to find a cause. As a workaround you could try adding those 16 pixels to the height of the preview window. In avsp.py:
pos = -(h + 2 * self.yo + 5 + self.mainSplitter.GetSashSize()/2) - 16
That random +5 (has been there since at least 2007) seems fishy. I'm near to just blame wx as usual.

Here's a library.zip (http://www.mediafire.com/download/bm52yzetgm54jr7/library_[height__+16].zip) up to latest git plus the above hack.

[LigH]

Hmm, strange: Exchanging lib/library.zip with this new archive doesn't fix it for me. I have the two mentioned example scripts open, switch between them, and the size of the preview window gets almost matched to the height of the video, but still produce a too small window to avoid vertical scrolling. And I can't imagine either why it's only for me, I won't be the only one with normal Windows 7 Aero style.

[vdcrim]

The size of the preview window is kept for as long as the output resolution of the script in that tab doesn't change, so if you just started the program again and toggled the preview the height will be the same. Did you try after that for example setting the zoom to 100% and doble-clicking the separator between script editor and preview?

[LigH]

Changing the zoom also changes the size of the preview window, like switching between scripts ... but always to less than the required height, no matter if I select 50%, 100%, 200%. Double-clicking the separator may remove the horizontal scrollbar when the width is sufficient, but the vertical scrollbar persists because the height stays too low.

[vdcrim]

So the results with the +16 pixels library.zip were identical, or was +16 just not enough?. Well anyway I'm out of ideas about this really.

[LigH]

With either the original library.zip or your (probably not) "fixed" library.zip, the preview window resizes to the same height.

[vdcrim]

With either the original library.zip or your (probably not) "fixed" library.zip, the preview window resizes to the same height.
That is even more weird than the height being 16 pixels short. That's pretty much all input I can give you.

[BlockABoots]

Is there anyway to get audio from the preview video within AvsPMod?

[creaothceann]

Use the shortcut to start the external player (F6 I think).

[RRD]

Is there a “Copy current frame number to clipboard” function somewhere like in VirtualDub? I'd like to assign a keyboard shortcut to it.

[wOxxOm]

RRD, save the code below to AvsPmod/macros/FrameNumberToClipboard.py

import wx

fnum=str(avsp.GetFrameNumber())
if wx.TheClipboard.Open():
data = wx.TextDataObject(fnum)
wx.TheClipboard.SetData(data)
wx.TheClipboard.Close()
else:
avsp.GetTextEntry('frame',fnum,'copy FAILED')

Restart AvsPmod, go to options/keyboard shortcuts and scroll to macros -> FrameNumberToClipboard

[martin53]

referring to this thread (http://forum.doom9.org/showthread.php?t=145464), the AviSynth 2.6 variable ScriptDir has a trailing backlash (today, with AviSynth26RC1) when the script is opened with VDub, MPC-HC, XMedia Recode, AvsMeter... Verify with this Script:
ColorBars().Subtitle(ScriptDir())

But the same variable has no trailing backslash when the script is opened in AvsPmod 2.5.1. You should be aware of that.

[TCmullet]

I just got informed of AvsPmod. But when I tried to access the "animated tutorial" under "Help", of which I have reason to believe is a Powerpoint presentation, the link is an invalid page. The link is:
http://www.avisynth.nl/qwerpoi/Demo.htm
Does anyone know how to get to the that demo??

And can someone fix the program to point to the file successfully?

(Gee this discourages me from going forward. First try at getting educational help and I get a 404.)

[Reel.Deel]

http://www.avisynth.nl/qwerpoi/Demo.htm
Does anyone know how to get to the that demo??


https://web.archive.org/web/20120502195653/http://avisynth.org/qwerpoi/Demo.htm

Edit: actually the wiki page link works just fine: http://www.avisynth.nl/users/qwerpoi/ :confused: where did you find that link?

[TCmullet]

https://web.archive.org/web/20120502195653/http://avisynth.org/qwerpoi/Demo.htm

Edit: actually the wiki page link works just fine: http://www.avisynth.nl/users/qwerpoi/ :confused: where did you find that link?

In the program itself. Click help and it's the first item. I did say "can someone fix the program". Maybe you didn't know the program had that in the help tab. Perhaps you are an early user. I do know from past programming experience that the help stuff gets added later, if ever.

[LigH]

The URL used to be avisynth.org, but its Wiki got damaged by spam bots, so the content moved to another server with the domain avisynth.nl; but user related pages also moved into a /users/ subdirectory which didn't exist on the original server. Search-and-replace ".org" with ".nl" was not sufficient in such cases...

[foxyshadis]

In the program itself. Click help and it's the first item. I did say "can someone fix the program". Maybe you didn't know the program had that in the help tab. Perhaps you are an early user. I do know from past programming experience that the help stuff gets added later, if ever.

Good catch, the help files (https://github.com/AvsPmod/AvsPmod/blob/master/help/About.html) haven't been updated since 2007, for the original avsp. Looks like it's high time to go through and fix them up along with documenting the new functionality in avspmod.

[Floatingshed]

Question about a very minor thing...
I have recently updated from version 2090 or similar. All my old user-defined functions show up in a script in purple (default) but any new ones I create show up in red (unknown function!). Any idea why? Works fine of course, but I don't like change :-)
Thanks.

[vdcrim]

Are the functions in red user-defined functions saved in avs/avsi files on the autoload directory but not manually added to AvsPmod's function definition database? If that's the case I can think of two possible explanations:


You're using AviSynth+
The functions are in avs files instead of avsi, that is you call Import when you need them instead of letting AviSynth autoload them

You keep using a specific old AviSynth+ build from October 2013

[Mounir]

How can i create a function for a vdub plugin i use frequently (and a bunch of others) ? I tried to see in the "avs function definition" but it appears i'm going nowhere
what i use is this:
LoadVirtualDubPlugin("C:\Program Files (x86)\virtualdubmod1.5\plugins\Camcorder_Color_Denoise_sse2.vdf", "CCD", 0)
CCD(30,1) # 30=default

Thanks for your help

[vdcrim]

Go to Options -> AviSynth Function Definition -> User Functions, add a new function. Type the list of arguments (type and name) and use define sliders to complete the entry.

According to the readme and Google Translate, for this filter it would result in something like this:
(
clip clip,
int strength=30 (0 to 100),
int multithreading=1 (0 to 1)
)
Names are just made up. As when defining a script function, an argument name in quotes means that it can be referred by name. Although you can't do that for VirtualDub filters a name is still useful as it's shown on calltips and sliders.

You can also define a script function wrapping LoadVirtualDubPlugin + CCD and add the function definition of that wrapper instead. That way you type a bit less and have the option of referring to the arguments by name:

function CCD(clip clip, int "strength", bool "multithreading", int "preroll", string "vdf_path"){
strength = default(strength, 30)
multithreading = default(multithreading, true)?1:0
preroll = default(preroll, 0)
vdf_path = default(vdf_path, "C:\Program Files (x86)\virtualdubmod1.5\plugins\Camcorder_Color_Denoise_sse2.vdf")

LoadVirtualDubPlugin(vdf_path, "vdf_CCD", preroll)
return vdf_CCD(clip, strength, multitheading)
}

(
clip clip,
int "strength"=30 (0 to 100),
bool "multithreading"=True,
[int "preroll"=0],
[string "vdf_path"= ("*.vdp"/ "*.vdplugin")]
)

[Floatingshed]

Are the functions in red user-defined functions saved in avs/avsi files on the autoload directory but not manually added to AvsPmod's function definition database? If that's the case I can think of two possible explanations:


You're using AviSynth+
The functions are in avs files instead of avsi, that is you call Import when you need them instead of letting AviSynth autoload them

You keep using a specific old AviSynth+ build from October 2013


My functions are .avs and are saved to a directory that does not auto-load. I load them per script.
Avisynth version is 2.6mt
I tried just changing the font and colour but there appears to be no way to store the changes...

[vdcrim]

My functions are .avs and are saved to a directory that does not auto-load. I load them per script.
Then AvsPmod can't know about them if you don't add them yourself in Options -> AviSynth function definition. Since v2.5.0 unknown functions are coloured red by default, I guess you're updating from a previous version (don't know what version 2090 or similar could be). If old functions aren't red that can only mean you added them to the database at some point.

I tried just changing the font and colour but there appears to be no way to store the changes...
Changes should be saved if you close the font and colours dialog with OK.

[Floatingshed]

I always add my functions to the database.
Also the colours and fonts page doesnt have an OK button on my version! Unless the panel is so large that it is off the bottom of the screen, its can't be re-sized! My resolution is 1024x768.

[vdcrim]

I always add my functions to the database.
There's no issue then? Or are you saying that new functions are still red even after adding them (can't reproduce it).

Also the colours and fonts page doesnt have an OK button on my version! Unless the panel is so large that it is off the bottom of the screen, its can't be re-sized! My resolution is 1024x768.
That's the case. The dialog has been rearranged since v2.5.1, you can use a newer build like the one linked in the OP.

[Floatingshed]

I am using V2.5.1 and there is no "OK" button on the colours and fonts set-up page! As far as I can see there is no way to save any changes.

[vdcrim]

It seems it wasn't clear enough. There's an OK button, but as you ventured your vertical resolution is too short for the dialog height. You won't have this issue on recent revisions as the dialog has been modified after the last stable release, v2.5.1. So if this issue is important to you use a newer build, see the opening post.

[stranno]

Is there any way to use Avisynth+ 64-bit? I dont know if this:

Add support for 64-bit AviSynth+

Means that there is fully support for 64-bit AVS. Can anyone provide the lastest compiled version? The r426 link is not working anymore, and i dont know if it even include that commit.

[Reel.Deel]

For 64-bit AviSynth+, AvsPmod also has to compiled for 64-bit. As far as I know vdcrim has only released 32-bit builds.

I came across an older 64-bit AvsPmod (r443) build sometime ago but ultim told me not to use it with the latest AviSynth+ (r1779 or greater) unless it was AvsPmod (r452) (IRC).

Anyways, here's the updated link for AvsPmod r432 (http://files.line0.eu/builds/AvsPmod-line0-2.5.1-r432-x86-1ee9b4a.7z), and the older r426 (http://files.line0.eu/builds/AvsPmod-2.5.1-r426-x86-04874ed.7z).

[foxyshadis]

Back when I still had 2.7 installed, it was as simple as running avsp.py with the 64-bit python, with the 64-bit wx dlls on the path. (I ran it from git, but it'd work as well from the installed .py files.)

Now that I work in py3 exclusive, I'm waiting to see how the work to split up the pieces works out.

[stranno]

Thank you @Reel.Deel. Its clear now.

[Reel.Deel]

Here is r452 build: x86 (http://www.mediafire.com/download/o153edc2ljd9oae/AvsPmod_v2.5.1_r452_%28Windows_x86-32%29.7z), x64 (http://www.mediafire.com/download/jmpninfd5m244aa/AvsPmod_v2.5.1_r452_%28Windows_x86-64%29.7z).

Awesome! Thanks :)

[cegy]

Here is r452 build: x86 (http://www.mediafire.com/download/o153edc2ljd9oae/AvsPmod_v2.5.1_r452_%28Windows_x86-32%29.7z), x64 (http://www.mediafire.com/download/jmpninfd5m244aa/AvsPmod_v2.5.1_r452_%28Windows_x86-64%29.7z).


for me it seems there's a issue using the x64 version of avspmod (hit and miss but more miss) which gives an error to avisynth_cffi_ext.pyd which can be seen in this picture also this is with the installed version of aAvisynth+ r1825 incase anyone does ask (the version that comes with staxrip)

http://i.imgur.com/coIvfMK.png

[Reel.Deel]

Here is r452 build: x86 (http://www.mediafire.com/download/o153edc2ljd9oae/AvsPmod_v2.5.1_r452_%28Windows_x86-32%29.7z), x64 (http://www.mediafire.com/download/jmpninfd5m244aa/AvsPmod_v2.5.1_r452_%28Windows_x86-64%29.7z).

for me it seems there's a issue using the x64 version of avspmod (hit and miss but more miss) which gives an error to avisynth_cffi_ext.pyd which can be seen in this picture also this is with the installed version of aAvisynth+ r1825 incase anyone does ask (the version that comes with staxrip)

Can you post the script your using?

[cegy]

Can you post the script your using?

the odd thing is that it was working just fine before but now keeps on crashing when loading the exe up (as i said already how its quite hit and miss but more miss)

the script i was using would be very simple (and yes its using x64 of the plugins/exe's etc...)

LoadPlugin("<PLUGINS_DIR>\DGDecodeNV.dll")
DGSource("<INPUT>", deinterlace=1,resize_w=0,resize_h=0)
Crop(0, 0, -0, -0)
LanczosResize(1280,720)

so in short the exe fails to load and no scripts can be used at all due to the exe failing to run due to the error from "avisynth_cffi_ext.pyd"

also incase you do ask the very same script just works just fine every single time with the x86 version

i've deleted the dir and tried from fresh, reinstalled avisynth+ a few times and still the same thing will happen overtime i think.... my guess is there's a bug somewhere but there again i might be wrong lol
unstalling avisynth+ and reinstalling did get it to work this time but i don't think it will last.. time will only tell

[Thunderbolt8]

does avspmod support Rec. 2020 yet? afaik for UHD Blu-rays the video is going to be encoded for Rec. 2020 colour points. in order to compare screenshots with other sources like from normal Blu-rays, we'd have to do all conversions for this manually, because so far avspmod only supports YUV -> RGB in BT.601 or BT.709.

therefore it would be nice if Rec. 2020 could be added as well, it would save a lot of time and work.

[foxyshadis]

AvsP uses Avisynth to convert to RGB, so it likely won't support that until it's implemented in Avisynth. (Which does not currently support it.)

[vivan]

Doesn't it use Dither? Because I see some 10/16 bit options.
madVR had resolution-based detection for BT.2020, but it was disabled because all 2160p videos used BT.709 matrix at that time.

[fvisagie]

1. Does the pre-release build number r{nnn} correspond to the rank of the latest commit? I.e. is HolyWu's r452 build (http://forum.doom9.org/showthread.php?p=1733655#post1733655) numbered so because there were 452 commits when it was built?

2. The Pre-release r426 Windows build (http://files.line0.in/builds/AvsPmod-2.5.1-r426-x86-04874ed.7z) on the opening post is broken or the server is down.

[fvisagie]

Something like this macro (https://gist.github.com/vdcrim/99d1aca217894bd527c7)? It cuts the current trim selections and pastes them after the current frame (bookmarks so far are untouched).

I hadn't realised you'd already committed that (https://github.com/AvsPmod/AvsPmod/commit/65bd3e3dd82bf3a7b55106e2ada4abd5d22a5c2f):
Add cut and pasting of ranges of frames

Two new menu entries added to 'Video' -> 'Trim selection editor':
- 'Move selections before the current frame' (ctrl+alt+V)
- 'Move selections after the current frame' (ctrl+V)
The hotkeys are only in effect if the video preview is focused

Activating either one will cause the current selections to be cut from
the timeline and inserted before/after the current frame. Bookmarks are
also shifted.

Many thanks for this. Hopefully it's included in HolyWu'z r452 build.

[fvisagie]

For the same video, one would expect e.g. %RGB and %YUV to show equivalent values (i.e. %RGB (0,0,0) = %YUV (16,128,128)) , and one would expect pixel values to be independent of display settings. However, that is not the case, because both %HEX and %RGB show display values, instead of output video values. Whenever the display YUV <-> RGB conversion is changed with YUV video output, the %HEX and %RGB values change, although the video itself does not. This makes colour comparisons complicated and tricky.

For example
StackVertical(BlankClip(pixel_type="YV12", color=$000000), BlankClip(pixel_type="YV12", color=$FFFFFF))
should always display %HEX $000000 / %RGB (0,0,0) / %YUV (16,128,128) / %CLR (16,128,128) over black and %HEX $FFFFFF / %RGB (255,255,255) / %YUV (235,128,128) / %CLR (235,128,128) over white.

When YUV <-> RGB display conversion is set to TV levels, those values are shown correctly. However, when display conversion is changed to PC levels, although %YUV and %CLR still show the same correct values, %HEX and %RGB change to $101010 and $EBEBEB for black and white respectively.