AvsPmod 2.5.1

[stax76]

StaxRip works only with DGSource.

[shambles]

Do you mean you would like the video to be fullscreen?
I think there are 2 things that you can do to sort of accomplish this right now.

i need fullscreen when comparing encodes with interleave(). currently i open my scripts in mpchc but framestepping backwards and forwards is very slow and inconsistent so it's easier to do interleave(a,b,a,b,a,b,a,b,a,b) and only step forward. though it works pretty good it's still a far cry from the ease-of-use of avsp

i tried mplayer (smplayer gui) but it didn't even seem to have a step backward hotkey

[Zarxrax]

i need fullscreen when comparing encodes with interleave(). currently i open my scripts in mpchc but framestepping backwards and forwards is very slow and inconsistent so it's easier to do interleave(a,b,a,b,a,b,a,b,a,b) and only step forward. though it works pretty good it's still a far cry from the ease-of-use of avsp

i tried mplayer (smplayer gui) but it didn't even seem to have a step backward hotkey

I'll check to see if there is any way to implement a fullscreen mode, but I suspect that it is either not possible, or very difficult to do.

[tin3tin]

i need fullscreen when comparing encodes with interleave()

Why don't you just use Video > Zoom > 100%(Normal) or higher and the use the scrollbars to locate the troublesome areas?

[levi]

I'm getting an error "The current Avisynth script contains errors."

http://img534.imageshack.us/img534/3725/whaterros.png (http://img534.imageshack.us/i/whaterros.png/)

I think I figured out it's because it's not auto-loading all of my plugins directory. When I add:

import("C:\Program Files (x86)\AviSynth 2.5\plugins64\srestore.avsi")

it works. Can I specify the plugins dir somewhere?

[shambles]

Why don't you just use Video > Zoom > 100%(Normal) or higher and the use the scrollbars to locate the troublesome areas?

i compare the videos in normal viewing conditions, from normal viewing distance. it's difficult to see differences in dark areas when the gui is visible

[Zarxrax]

I'm getting an error "The current Avisynth script contains errors."

I think I figured out it's because it's not auto-loading all of my plugins directory. When I add:

import("C:\Program Files (x86)\AviSynth 2.5\plugins64\srestore.avsi")

it works. Can I specify the plugins dir somewhere?

I haven't tried that version of avisynth that you are using yet, but I'm guessing you use 2 different plugins folders, right? Does it store both of them in the registry, or do you normally have to load that folder manually? I think I can probably add support for this.

[levi]

I haven't tried that version of avisynth that you are using yet, but I'm guessing you use 2 different plugins folders, right? Does it store both of them in the registry, or do you normally have to load that folder manually? I think I can probably add support for this.

Here's a snapshot:

http://img176.imageshack.us/img176/2109/90772609.png (http://img176.imageshack.us/i/90772609.png/)

Thanks for looking in to this :)

[levi]

- Removed outdated encoding gui from the tools menu


Just curious why you removed it. I use it for launching x264 & xvid encraw. I put the scripts from the non-mod version in & it works great. :confused:

Also, it would be great if the resize calculator window would show bits/(pixel*frame) as resize is adjusted to aid in choosing new resolution

[Zarxrax]

Just curious why you removed it. I use it for launching x264 & xvid encraw. I put the scripts from the non-mod version in & it works great. :confused:

Also, it would be great if the resize calculator window would show bits/(pixel*frame) as resize is adjusted to aid in choosing new resolution

Eh, it still actually worked for x264? Someone in the old avsp thread said it didn't work anymore, and I'm fairly certain that all of the development in x264 in the past years has surely rendered it obsolete. I suppose it could still be ok for xvid though.
Looking over the plugin, it seems that it just generates some outdated commandlines. I suppose it could be updated fairly easily.
Can you explain more about this bits/(pixel*frame) thing that you want. I'm not really sure what this is.

[osgZach]

I think hes talking about a bitrate calculator... Frankly I've never used them.

[levi]

Eh, it still actually worked for x264? Someone in the old avsp thread said it didn't work anymore, and I'm fairly certain that all of the development in x264 in the past years has surely rendered it obsolete.

Not at all. I have various profiles defined for different command line configurations. I also have it set up so I can launch x32 or x64 264 & x32 or x64 xvid_encraw. I have, for example, the threads parameter configurable in the gui since different avs scripts (MT vs not MT, etc) work better (faster) with different encoder command line settings for thread numbers.


I suppose it could be updated fairly easily.


If you would like I'll send you my modifications to use as a sample


Can you explain more about this bits/(pixel*frame) thing that you want. I'm not really sure what this is.

This is something that I get from gordian knot - resolution tab

http://img12.imageshack.us/img12/5184/55931392.th.png (http://img12.imageshack.us/i/55931392.png/)

[Zarxrax]

Won't that require info from the bitrate calcuator? If so, I don't know if I can do that.

[levi]

I believe it requires evaluating the input, crop & resize operations. I only know 3 apps that do it

gordian knot
megui
aspect

[Zarxrax]

I believe it requires evaluating the input, crop & resize operations. I only know 3 apps that do it

gordian knot
megui
aspect

Hmm, well the problem is, I don't really understand what I am supposed to be calculating here.
bits = ?
pixel = width*height ?
frame = framerate? number of frames in the whole video?

I tried looking at the code of the aspect program, but C is really difficult for me to follow.

[nurbs]

Won't that require info from the bitrate calcuator?
Yes, you'd need the average bitrate since bpf = bps / ( w * h * fps).

It's basically useless for choosing a resolution anyway since it doesn't take source complexity into account:
http://forum.doom9.org/showthread.php?p=841511#post841511
http://forum.doom9.org/showthread.php?p=1311212#post1311212

TL;DR:
You can not base your decisions on this formula. The formula only gives you the false feeling that you know what you're doing when you're actually making a blind guess. This formula is more like a chant. Snakeoil.

[osgZach]

When I want to guess at file size for a given bitrate, I don't even take resolution into account.. I just look for an average size assuming every frame were the same bitrate of the target.

i.e 800kbps / 8 = 100KB, 100KB * 60s = 6MB/minute * length of video. Not the most accurate math in the world but gives you a rough idea and pretty easy to remember all the steps involved.

Have to guestimate how much bitrate you might require for a given resolution but there are general recommendations found easily enough with a search.

[Zarxrax]

levi: since that calculation seems to require knowledge of the bitrate that you intend to use, and since it seems to generally be a useless measurement, I'm not going to bother adding it.
But, you also mentioned having made modifications to the encoder tool. Anything interesting? I'm making some changes to it right now, but if you have done anything worthwhile to it, I'd definitely like to see.

I also just finished writing a new macro that can convert avsp's bookmarks into a chapter list for mkv/mp4 files :)

[Zarxrax]

Version 2.0.5 released. Download link in first post.


Changelog
Version 2.0.5:
- Updated defaults for 14 core filters, and added a handful of definitions for some userscripts
- Restored the mp4 encoding tool, as I had mistakenly decided that it was broken. In fact, only the presets were outdated. I have included new x264 presets, and also added the ability to set a CRF rather than a bitrate.
- Added new macro which lets you create a chapter list from your bookmarks. AvsPmod is now a great tool for creating matroska chapter files.
- Added new menu items: 'Open Avisynth plugins folder' & 'Open macros folder'

[rfmmars]

You do something good then upload it to this crumy download site, I don't have time to waste.

Richard

Much better, Thanks

[whatyaar]

Thanks a lot for all your time/effot, appreciate your effort.thanks one more time.

[XadoX]

:thanks:

[vucloutr]

:thanks:

[RedDwarf1]

Version 2.0.5 released. Download link in first post.

Changelog
Version 2.0.5:
- Updated defaults for 14 core filters, and added a handful of definitions for some userscripts
- Restored the mp4 encoding tool, as I had mistakenly decided that it was broken. In fact, only the presets were outdated. I have included new x264 presets, and also added the ability to set a CRF rather than a bitrate.
- Added new macro which lets you create a chapter list from your bookmarks. AvsPmod is now a great tool for creating matroska chapter files.
- Added new menu items: 'Open Avisynth plugins folder' & 'Open macros folder'


Thanks for updating this useful program. The Open Avisynth plugins folder is a good one, I always like stuff which speeds things up. That's why I like FileBox eXtender as it makes accessing frequently used folders so much quicker. My folder layout is so deep that it's a right pain to get to most folders without it.

[kopmjj]

Hi before i install windows 7 64 bit does this work on it? at the moment i have windows 7 32 bit and works great.

[7ekno]

Hi before i install windows 7 64 bit does this work on it? at the moment i have windows 7 32 bit and works great.

Yep, W7 x64 here and it's running well :cool:

http://www.users.on.net/~tekno/screenies/AvsPMod205.png
*Obviously editted to remove network/PC details !*

7ek

[RiCON]

Does adding User Functions work, now? As in, do they stay after the program's closed?

Also, I had added a framecount (http://ricon.pastebin.com/NFc67Y85) for the command line in encoder-gui in order to work with avs2yuv | x264-64.

Dunno if it's useful atm.

[Stephen R. Savage]

@Author:

- Could you add support for the Avisynth 2.5.8 block comments (/*comment*/) and the __END__ keyword?


/* This is a comment */ # format as comment
ImageSource("0001.png")
__END__
# these lines are disabled
Crop(4, 4, -4, -4)
Invert()


- Can you change the default comment font to something other than Comic Sans MS?

- Will you update the core filter definitions for those that have changed in Avisynth 2.6, e.g. the colorspace conversion filters?

- Can you implement code folding for function declarations and try/else blocks (perhaps fold on {})?


function TheFunction( ... )
{ # This could be folded.
[ ... ]
}


- Can you make text to the left of the assignment operator (=) not be highlighted as a function name? Also, could you not highlight names that have been assigned values as functions unless parentheses are present?


blankclip = blankclip # The assigned name should never be highlighted
StackHorizontal(last, blankclip, blankclip()) # see above


- Can you make the tab character ('\t') obey the indentation rules under Settings -> Text 1 instead of always occupying 3 spaces?

- Can you think of a better way to handle functions with "_" in their name?


LoadPlugin("mt_masktools.dll")
mt_masktools_mt_edge() # use rules for mt_masktools_mt_edge
mt_edge() # use rules for mt_masktools_mt_edge
edge() # do not use rules for mt_masktools_mt_edge


- When scanning plugins to read the syntax call, could you also detect which parameters are named/optional and which are not? Also, could you allow the user to manually generate information for a given plugin instead of only handling plugins in autoload?


@RiCON: I just checked, and they do indeed persist now. Very useful bugfix.

[Zarxrax]

@Author:

Could you add support for the Avisynth 2.5.8 block comments (/*comment*/) and the __END__ keyword?

Can you change the default comment font to something other than Comic Sans MS?

Will you update the core filter definitions for those that have changed in Avisynth 2.6, e.g. the colorspace conversion filters?

Can you implement code folding for function declarations and try/else blocks?


- I will look into supporting block comments and the __END__ keyword, but I'm not sure if I can do it.
- What font would you suggest instead?
- Hmmm.... that's a tough question. If I change filter definitions to those of AviSynth 2.6, that might mean they are no longer compatible for people using 2.58. Maybe there could be a way to determine which version of AviSynth is being used, and load different definitions for each one. Or maybe I could just include different files so the user can drop in a replacement if you are using 2.6. If/when 2.6 actually gets to a point where it is marked as stable and replaces 2.58, this would be a non-issue.
- Code folding sounds too difficult, but I'll check into it.

[Stephen R. Savage]

- I will look into supporting block comments and the __END__ keyword, but I'm not sure if I can do it.
- What font would you suggest instead?
- Hmmm.... that's a tough question. If I change filter definitions to those of AviSynth 2.6, that might mean they are no longer compatible for people using 2.58. Maybe there could be a way to determine which version of AviSynth is being used, and load different definitions for each one. Or maybe I could just include different files so the user can drop in a replacement if you are using 2.6. If/when 2.6 actually gets to a point where it is marked as stable and replaces 2.58, this would be a non-issue.
- Code folding sounds too difficult, but I'll check into it.

I believe you should just take one of the already used default fonts (perhaps Arial or Verdana) and assign it to the comment font. For the Avisynth 2.6 updates, the developers have taken forward compatibility into account, and new parameters have been added to the end of the function calls. This should mean that the templates can be extended without breaking compatibility.

Please look into the other suggestions I added to my previous post.

Edit: Also, I believe all that is required to enable 64-bit Avisynth for the video preview is to instruct py2exe to link against the Python 64-bit libraries (assuming Python <--> C mappings are platform independent).

[Gavino]

Could you add support for the Avisynth 2.5.8 block comments (/*comment*/)
Also, if possible, the [* comment *] form which supports nested block comments (http://avisynth.org/mediawiki/The_full_AviSynth_grammar#Comments).

[Zarxrax]

Even if the new parameters in Avs2.6 are just added to the end of the function, that doesn't really help, because if you are using the autocompletion to have it fill in the parameters, it will add too many parameters when you are using avisynth 2.58. But, as I said I'll check into it.

The reason that it highlights names of functions when parentheses are not present, is because AviSynth does not require parentheses. For instance, ConvertToYV12 and ConvertToYV12() should do the same thing.

I will look into the thing with the assignment operator.

Regarding the tab setting (in Text 2 settings) it seems to work fine for me. It's set to 4 as default, and my tabs insert 4 spaces. Changing it to 2 made them insert 2 spaces instead. I'm not sure what problem you are having there.

[Gavino]

For instance, ConvertToYV12 and ConvertToYV12() should do the same thing.
Not if the script creates a variable called ConvertToYV12 :devil:
- but the editor can't tell that without actually executing the script.

[Zarxrax]

Yea, it's kind of stupid to use reserved words :p

[Stephen R. Savage]

Even if the new parameters in Avs2.6 are just added to the end of the function, that doesn't really help, because if you are using the autocompletion to have it fill in the parameters, it will add too many parameters when you are using avisynth 2.58. But, as I said I'll check into it.

The reason that it highlights names of functions when parentheses are not present, is because AviSynth does not require parentheses. For instance, ConvertToYV12 and ConvertToYV12() should do the same thing.

I will look into the thing with the assignment operator.

Regarding the tab setting (in Text 2 settings) it seems to work fine for me. It's set to 4 as default, and my tabs insert 4 spaces. Changing it to 2 made them insert 2 spaces instead. I'm not sure what problem you are having there.

It does not do this for the interpretation of REAL TABS (ASCII HT, code 09). These are always represented as 3 spaces.

Note that many "reserved" names are very common words that you may want to use for function arguments (e.g. mask), and that plugins can add any arbitrary reserved name. Considering this, I suggest that when deciding whether to highlight a word or not, it should check if it appears in any assignment within the current scope or as a function argument. I understand that this will not catch variables assigned in Eval(), nor those created by functions and declared global, but I believe this is a reasonable compromise.

Edit: Also, I believe the argument names in a function declaration should never be highlighted either.

Edit2: Also, @Gavino, perhaps we should have a more "rich" editor that can analyze the script?

[Zarxrax]

Ok, so I guess you mean tabs that were inserted by some editor other than AvsP always show up as 3 spaces? I'll check into that.

I think it's going to be very difficult to try and parse the scripts to figure out what exactly how you are using a particular name, so there is no way I'm even going to touch that. If you or someone else can come up with a patch to do this, I'll gladly implement it, but, it's outside the scope of what I can do.

And about 64-bit, it seems that avsp links to some 32-bit C libraries, which prevents me from compiling it with 64bit python. At least that's what I think was going on when I tried it.

[RiCON]

Macro for AvsPmod - Trims.py (http://ricon.pastebin.com/PgiZvs2F)
Adds a "Trim(n,n)" for each bookmark and creates qpfile (for x264) with them.

The trims will be useful to use with Daiz's AutoMKVChapters or some other script that reads them to create chapters or something.

[krosswindz]

:thanks:

nice to see someone breath in some fresh life into AvsP. I will surely give this a try soon.

[RiCON]

Some more User Functions (http://ricon.pastebin.com/TMk4Cdv0)

Includes: AA, AAA, AnimeIVTC 2.0, AntiAliasing, ClipComp, ClipComp4 (a mod of mine of ClipComp), Deblock_QED, DeHalo_Alpha, EdgeCleaner, EE, FastLineDarken, FastLineDarkenMod, GradFunkMirror, HybridFuPP, LRemoveDust, LRemoveDustSSE3 (another mod to use SSE3 versions of the same filters), LSFMod, MCRemoveDust, MCTemporalDenoise, ReBlend, ReFadeIn, ReFadeOut, RemoveDirt, SAA, SeeTheDifference, SmartFade, Stab and TempGaussMC_beta2.

Dunno if I used the latest versions, but if you know better or newer versions of the same scripts, warn me.

[Zarxrax]

Some more User Functions (http://ricon.pastebin.com/TMk4Cdv0)

Includes: AA, AAA, AnimeIVTC 2.0, AntiAliasing, ClipComp, ClipComp4 (a mod of mine of ClipComp), Deblock_QED, DeHalo_Alpha, EdgeCleaner, EE, FastLineDarken, FastLineDarkenMod, GradFunkMirror, HybridFuPP, LRemoveDust, LRemoveDustSSE3 (another mod to use SSE3 versions of the same filters), LSFMod, MCRemoveDust, MCTemporalDenoise, ReBlend, ReFadeIn, ReFadeOut, RemoveDirt, SAA, SeeTheDifference, SmartFade, Stab and TempGaussMC_beta2.

Dunno if I used the latest versions, but if you know better or newer versions of the same scripts, warn me.

Thanks, this is something that I have been thinking about though... I wonder if it is a good idea to actually include user functions in avspmod. Because, there tend to be multiple versions of some functions, and so the user would need to make sure that their own functions are the same versions as the ones defined inside the program. And also, functions might become updated, while the definition in avspmod remains out of date for some time.
However, the other alternative would be for users who want definitions for their functions, to just do it themselves, but that's not a very attractive idea for most people, because it's very time consuming.

[foxyshadis]

Thanks for taking the time to update my favorite Avisynth tool, Zarxrax! If I get the time, I'll try to help out, but I'm easily distracted. (Working on AvsP was what initially moved me to Python from PHP, now I do everything in it... but in v3.)

Edit: Also, I believe all that is required to enable 64-bit Avisynth for the video preview is to instruct py2exe to link against the Python 64-bit libraries (assuming Python <--> C mappings are platform independent).

I'm going to try linking to wx x64 - but first I need to reinstall mingw to get gcc. wx is the main stopping point.

[RiCON]

Zarxrax: It's OK if the functions get outdated, because the user himself can modify them even if they're inside filterdb.dat through either the AvsP or opening filterdb.dat in Notepad or something.

[Stephen R. Savage]

Speaking of user filters, currently, there is an "export user functions" button but no import one (???).

[Zarxrax]

Wow, I just noticed today that there is already a nice interface to change the fonts, under Options>Fonts and Colors
I will go ahead and change the default comment font from Comic Sans to something else though.

I've been trying to fix the tab issue and the block comments, but its harder than I thought it would be. Also I've been really busy with work lately, so I haven't had a lot of time to work on this, but I'll keep trying and see what I can do.

[Zarxrax]

It does not do this for the interpretation of REAL TABS (ASCII HT, code 09). These are always represented as 3 spaces.
Stephen, are you certain about this? I was just testing with real tabs, and their size was dynamically changing to match whatever tab size I had set in the options.

[Stephen R. Savage]

Stephen, are you certain about this? I was just testing with real tabs, and their size was dynamically changing to match whatever tab size I had set in the options.

I checked again, and you are right that the tab size changes with the option. However, it is always one space less than the AvsP tabs. If tab size is set to 4, real tabs occupy 3 spaces; if set to 8, they occupy 7 spaces.

[Zarxrax]

Well that's really odd, because on my system the sizes match perfectly!

[Zarxrax]

Ok, I discovered what the problem probably is. If you use a monospaced font, then the tabs and spaces DON'T match up. But if you use a variable width font, they match up.
I'll do some checks to make sure it is treating the monospaced fonts properly. I think I might make monospaced the default anyways, because it makes sense for an application like this.

[kypec]

Yes, monospaced font is definitely the proper choice here. I only recently switched that option ON in my AvsP (original, non-modded version).
There is still an option of customized colors which is enough I think.

[Joachim Buambeki]

Hi,

thanks for updating AVSP!

Sorry for bugging, but are there any news on a 64bit version of AVSPmod? It would be really appreciated.

Best Regards
David