New AviSynth tool - AvsP v1.4.0 (6/5/07)

[rfmmars]

I would like to add Toggle switches to the slider panel so I could trun on and off certain filters in the script. Can this be added or is this feature already there?

One of your biggest fans.

Richard

[krisq]

I would like to add Toggle switches to the slider panel so I could trun on and off certain filters in the script. Can this be added or is this feature already there?

One of your biggest fans.

Richard

It's there. Just select part of script which you want to disable/enable and press 'ctrl+t', put a name and the checkbox will appear in the sliders pane. Read more here (http://www.avisynth.org/qwerpoi/UserSliders.html) under 'Section Toggle Tags'.

[qwerpoi]

@zemog
Hah, you're right about that user slider validation bug, thanks for pointing that out. I'll get it fixed by the next release.

Btw, about this, maybe you could implement an option for the auto fit so that it checks for both width and height of the preview window instead of just height.. This is particularly interesting for the separate window : I always leave it maximised behing the editor window, so if it was just taking into account the height, the picture would always become too wide..

Or better : do you think that instead of an auto fit you could create a manual fit, where the user could for instance drag the bottom or the right side of the picture, this would show scaled black borders of the picture in real time (growing/shrinking from the bottom and right sides), and you would perform the custom fit upon release of the mouse button ? Final dimensions could be not exactely as dragged (as default bicubicresize is working on mod8 numbers), but that woiuldn't really matter
Some good ideas, the second suggestion sounds harder to implement than the first. I'll give it some thought.

Oh and a question : what is the small triangle at the top left corner of the preview window for ?
Yeah, that's a funny thing. It will show up whenever the zoom is not set to 100%. I did this because to me AvsP is all about making comparisons between multiple scripts, with some of the zoom features it becomes quite easy to not realize that the script output is being resized. Hence the little visual reminder, although I realize it looks a bit strange :) .

qwerpoi, not a big deal, but could you perhaps add the info/changes that's been implemented in newer versions somewhere at your website?

Anyways, thanks for another stellar update. :)
I've been meaning to getting around to doing just that, the website needs a bit of catching up work as it stands. For now the changelog can be found on the bottom of the readme.txt if you want to check it out.

Qwerpoi. Thanks for vrs1.3.3.

attached a Portugues translation for this vrs
Thanks for the update, I'll update the links momentarily.

I would like to add Toggle switches to the slider panel so I could trun on and off certain filters in the script. Can this be added or is this feature already there?

One of your biggest fans.

Richard

It's there. Just select part of script which you want to disable/enable and press 'ctrl+t', put a name and the checkbox will appear in the sliders pane. Read more here (http://www.avisynth.org/qwerpoi/UserSliders.html) under 'Section Toggle Tags'.
krisq is right, the feature is there, it was one of the latter additions to the program. If you read on the website you'll see that I recommend considering using multiple tabs instead of section toggle tags, to me that's easier and more efficient to work with for many cases. Eventually I may change the section toggle tag syntax to be more similar to the user slider syntax, although I'll maintain backwards compatibility so no need to be concerned.

[Fizick]

I at last have a time to update Russsian translation.
(but I have no time to try it)
Sorry for small comments:
1. AvsP is converted to a little complex program to use (too more items in menu, especiall EDIT menu). May be split them or move?

2. USAGE AGREEMENT in readme is not consistant with GPL license. :)

[Alain2]

Yeah, that's a funny thing. It will show up whenever the zoom is not set to 100%. I did this because to me AvsP is all about making comparisons between multiple scripts, with some of the zoom features it becomes quite easy to not realize that the script output is being resized. Hence the little visual reminder, although I realize it looks a bit strange :) .
Ah ok good idea ^^ maybe you can use another icon small icon more meaningful, like the maximised button of xp's windows ? like : http://img175.imageshack.us/img175/4523/tempjd0.jpg

[rfmmars]

It's there. Just select part of script which you want to disable/enable and press 'ctrl+t', put a name and the checkbox will appear in the sliders pane. Read more here (http://www.avisynth.org/qwerpoi/UserSliders.html) under 'Section Toggle Tags'.

Thanks for doing what I should have done, READ THE MANUAL.

Richard

[steptoe]

Just playing around, if I use AVSP with VOBs, it does read them if I make a short enough vlip so I can see filters effects on what I'm trying to work on, but the problem starts when I create a new tab to see the difference between filtered and unfiltered

I get an error saying that "the scripts return value was not a video clip", I assume this is because obviously the video is not an AVI

Will AVSP support VOBs directly or do they have to be converted to an AVI before I can use the software fully

Obviously converting to an AVI, unless I use a codec that just outputs the AVI as pure video will reduce the source quality even more in the case of a poor source you're trying to improve on

[foxyshadis]

You need DGIndex/DGDecode, just like you normally would for avisynth. Load the d2v, not the vob itself, in order to get the unprocessed version (and then process it if necessary). If you drag a d2v in, it'll be inserted with Mpeg2Source, aka DGDecode.

[qwerpoi]

AvsP is converted to a little complex program to use (too more items in menu, especiall EDIT menu). May be split them or move?
This is a good point, and one that's been bothering me a little. It would be easy enough to split the items into different menus, but I'd like to avoid a situation where you would have to dig through layers of menus in order to find a feature. In an effor to keep things simple, the best solution to me would be to get rid of the least used items :eek: , perhaps convert them into optional macros - but I imagine many people would be upset at the prospect of losing features.

As far as the Edit menu is concerned, one possibility is to put all the Insert... commands in a submenu (like the Zoom > submenu in the Video menu). This would at least make the Edit menu about the same size as the Video menu. My only concern with this idea is that a new user might never bother to look at the Insert > submenu, and thus never learn about some of the more important features of AvsP. Let me know what you guys think.

[Alain2]

Insert displayed with an arrow is a significant enough name to raise my curiosity and make me to the cursor on it and see what's inside...

[honai]

A suggestion for the crop editor: indicate when you're cropping inside/outside mod-16 constraints. Many filters (e.g. Deblock_QED) are constrained to mod-16 resolutions.

[krisq]

A suggestion for the crop editor: indicate when you're cropping inside/outside mod-16 constraints. Many filters (e.g. Deblock_QED) are constrained to mod-16 resolutions.

What about the status bar? Isn't this the info you need? There is wmod and hmod...

[Alain2]

Another suggestion for the todo list : Add commands (+ shorcuts) to go to the next / previous saved frame (so you can cycle within the bookmarks). I like saving some "key" frames in the bookmarks and navigate to them after some changes in the script to check the effect at these "key" locations :)

[Septimus]

Great Program, especially the slider function.

A quick question:

Has anyone taken the time to add function definitions for the most commonly used external filters ? (autocomplete)

That we could download and dump into the program directory ?

<<--- Lazy :rolleyes:

[check]

I've done a few, but they seem to be saved with all the default filters in the same .dat file, so I'm not sure if they are truly 'portable' sadly.

[zemog]

Qwerpoi, I think there are a bug in the option Video -> Zoom -> Fit to window in AvsP v1.3.3

I proof so stupid script like this:

a = AVISource("F:\... ...avi")
c = a.Trim(20,96)
e = a.Trim(97,0)
c + e

Zoom 25%, 50% 100%, etc., works fine, but if I drag manually to change the preview window size and choose “Zoom -> Fit to window” I get this error message:

Splice: Frame size don’t match
(F:\….\preview1.avs,line 4)

[doxville]

Approved, I got the same message when I applied 'trim'-commands like 'trim(...) ++ trim(...) ++ trim(...)'

[Alain2]

There is also no auto fit when I insert a "return last" in the middle of the script ; it will work if I comment all the lines below though

[krisq]

Something crazy just crossed my mind. Maybe you could add somekind of way to export preseted settings for individual filters. You know, something like "hey, drop this .dll into your plugins' dir and import this preset into your avsp" which happens to me all the time with my dumb friends. I just ache for the mechanism like that :)
Just imagine the community swaping with presets. Could be great ;).

[kumi]

I like the sound of that idea. :cool:

[jmac698]

I agree. The key to making great programs is making it easy for users to share *technology*, information, settings, skins, presets.. in a large enough community these things will get created.
The tool is almost perfect for daily use now, but I need one more thing, info about current clip (size, frames, colorspace, audio info). I was trying to debug something and needed to check fps and colorspace....

[Alain2]

use info() then... no need to slow down the app with plenty of things that are not used most of the time if ever..

[ChiDragon]

Just noticed, there's no syntax highlighting for AssumeScaledFPS. I thought there were definitions for all internal functions? :p

[morsa]

Wouldn't be a great idea to merge this to Virtualdub, so some kind of "resurrection" of VdubMod?

[jmac698]

Another small suggestion: the syntax tip gets in the way of the previous line of code that I want to see. I don't know what to suggest, it could be transparent, or movable, or option to but it underneath. Actually, underneath is better most of the time for me, as I write new code on the bottom and refer to code just above.

[qwerpoi]

Sorry for the lack of replies as of late, I was out of town for Thanksgiving with little internet access. On to business:

Another suggestion for the todo list : Add commands (+ shorcuts) to go to the next / previous saved frame (so you can cycle within the bookmarks). I like saving some "key" frames in the bookmarks and navigate to them after some changes in the script to check the effect at these "key" locations :)
Good suggestion, something that crossed my mind as well. I'll try and put something together for the next release.

Qwerpoi, I think there are a bug in the option Video -> Zoom -> Fit to window in AvsP v1.3.3

I proof so stupid script like this:

a = AVISource("F:\... ...avi")
c = a.Trim(20,96)
e = a.Trim(97,0)
c + e

Zoom 25%, 50% 100%, etc., works fine, but if I drag manually to change the preview window size and choose “Zoom -> Fit to window” I get this error message:

Splice: Frame size don’t match
(F:\….\preview1.avs,line 4)
Approved, I got the same message when I applied 'trim'-commands like 'trim(...) ++ trim(...) ++ trim(...)'
There is also no auto fit when I insert a "return last" in the middle of the script ; it will work if I comment all the lines below though
Interesting, I'll try and see what's going on with this, thanks.

Edit: Actually, it should have been obvious to me. The auto-fit option works simply by adding a .BicubicResize(w,h) to the end of the script behind your back. This fails in the cases mentioned, I'll have to put some special conditions in my code. In general I think it will work better if I add a new line to the end of the script, last.BicubicResize(w,h), I'll just have to watch out for any return statements.

Something crazy just crossed my mind. Maybe you could add somekind of way to export preseted settings for individual filters. You know, something like "hey, drop this .dll into your plugins' dir and import this preset into your avsp" which happens to me all the time with my dumb friends. I just ache for the mechanism like that :)
Just imagine the community swaping with presets. Could be great ;).
Sounds like a good idea, I'll give it some thought as to how to do it best.

Just noticed, there's no syntax highlighting for AssumeScaledFPS. I thought there were definitions for all internal functions? :p
No, I created all definitions manually from the AviSynth docs :eek: , at the time I put it together I was using an older version. I'll try and update the defaults, but in the meantime you can easily add any updates yourself from the Options menu.

Wouldn't be a great idea to merge this to Virtualdub, so some kind of "resurrection" of VdubMod?
Well, the codebase for the two programs are pretty different, I doubt anyone is willing to approach the idea of merging them :) . Although I do see where you are coming from, since AvsP is missing a lot of powerful features that vdubmod has (encoding, audio, etc), I don't think of AvsP as a one-stop video encoding application. I think of AvsP as a helper program or front-end to AviSynth. Certainly it would be ideal to have everything together in one place, and it's something I would like to see eventually, but currently that's not the focus of development.

Another small suggestion: the syntax tip gets in the way of the previous line of code that I want to see. I don't know what to suggest, it could be transparent, or movable, or option to but it underneath. Actually, underneath is better most of the time for me, as I write new code on the bottom and refer to code just above.
Yeah, the tooltips certainly can get in the way sometimes. My suggestion to you is to turn off frequent calltiips in "Options -> Program settings..." in the "Text 1" tab. This way calltips only show up when the cursor is next to the open parentheses of the filter. You can always bring up the calltip manually using Ctrl-Shift-Space, so it's sort of the best of both worlds assumming you know the manual shortcut.

[Fizick]

I vote for semi-transparent tooltips :)

[jmac698]

I could live with that :)

[check]

On checking for return statements, I guess you'd want to do something along the lines of a regex that patterns $return (.*) and replace it with group(1).bicubicresize()\nreturn last. I'd make the patch for you myself -- but my computer is in little pieces and work computers lack python ;)

[foxyshadis]

Or just add end-of-script trappings to a second script, which just import()s the first one.

[qwerpoi]

I vote for semi-transparent tooltips :)
Yeah, I'd like to try something like that, but unfortunately I didn't write the code that provides the tooltips (I'm using wxStyledTextCtrl which is a wrapper for Scintilla), so I can't directly access the tooltip window to change its properties. If someone thinks there is a straightforward way to do it, I'm all ears.

Or just add end-of-script trappings to a second script, which just import()s the first one.
Hey, that's a great idea, should make things work perfectly! I should have thought of it myself at the time - sadly, my Avisynth scripting skills are not first class, which is somewhat ironic given the fact that I am trying to write a top-of-the-line Avisynth editor :) .

[rfmmars]

Ok I been dealing with a problem where the screen in AVS-p doesn't match the AVS file or external viewer which is VD, any version.

However tonight all I got was a black screen upon export where you could see some low brightness chroma displayed.

I had made a slide show where there was 5 seconds of black before a fade up to normal brightness of the slide. The first mpeg2 I made was frameserved from VDmpg2. I notice the first slide was very dark but all the rest were ok. I am using a heavy modified HDRagc script and never this seen before, but have seen the non matching displys between VD(xx and AVs-p. I simply corrected this before in my NLE.

So to solve this startup problem, I added a normal brightness slide in front of the presentation. Well now I have what I want in AVS-p but nothing but black in a avs file or export to any VD(xxx).

The solution was to take out that 5 second black section before the dummy file. So it looks like AVS-p has a problem if there is dead black before the first image of a clip or a slow fade up transistion.

Richard
photorecall.net

[krisq]

I would love to see somekind of separator for sliders.
example:

sliders for filter1
[separator] which would give horizontal line
sliders for filter2

cheers :)

[qwerpoi]

Contrary to all the rumors, I have not died and gone to developer heaven (or hell, let's rock!). I've just been really busy towards the end of the year, and the stuff I need to do for AvsP is increasingly difficult to implement with decreasing payoff (I like it the other way around :) ). Nevertheless, I'll try and put out a new release in a week, at least with some bugfixes that need to be taken care of.

Ok I been dealing with a problem where the screen in AVS-p doesn't match the AVS file or external viewer which is VD, any version.

However tonight all I got was a black screen upon export where you could see some low brightness chroma displayed.

I had made a slide show where there was 5 seconds of black before a fade up to normal brightness of the slide. The first mpeg2 I made was frameserved from VDmpg2. I notice the first slide was very dark but all the rest were ok. I am using a heavy modified HDRagc script and never this seen before, but have seen the non matching displys between VD(xx and AVs-p. I simply corrected this before in my NLE.

So to solve this startup problem, I added a normal brightness slide in front of the presentation. Well now I have what I want in AVS-p but nothing but black in a avs file or export to any VD(xxx).

The solution was to take out that 5 second black section before the dummy file. So it looks like AVS-p has a problem if there is dead black before the first image of a clip or a slow fade up transistion.

Richard
photorecall.net
I'll try and do more research, but my thoughts are that it is some kind of memory issue, since there should be no technical difference between AvsP's preview and vdub's preview (both utilize AVIFile libraries as far as I know). If this happens consistently to anyone, please post the script, if it only happens with a specific video, try and post a chunk on rapidshare so I can recreate it.

I would love to see somekind of separator for sliders.
example:

sliders for filter1
[separator] which would give horizontal line
sliders for filter2

cheers :)
Hum, I'm trying to think of the best way to specify something like this. I could extend the label syntax to indicate a seperator comes afterwards (i.e., [<"amount",0,1,0>] becomes [<"amount---",0,1,0>] or something). Or I could make a random tag in the middle of the script indicate a separator, like a slider with no inputs (i.e., [<-,-,-,->]). I'll think about it some more, feel free to add your own 2 cents.

[rfmmars]

I'll try and do more research, but my thoughts are that it is some kind of memory issue

No I don't think its a memory thing, I have the problem on all five workstations.

What I have found is it happens only when I add Sliders to the HDRagc scripts. If I simply call HDRagc() no problem. Sometime it works ok but most of the time the contrast is extreme or black with just a hint of chroma in the export window. Even if you save the script, and load into Vdub, same problem, the AVSp preview looks great but its the export script or export preview that is screwed up.

I will try to add one slider at a time to see when the problem occures and save each script. I will get back to you.

Richard

[krisq]

Hum, I'm trying to think of the best way to specify something like this. I could extend the label syntax to indicate a seperator comes afterwards (i.e., [<"amount",0,1,0>] becomes [<"amount---",0,1,0>] or something). Or I could make a random tag in the middle of the script indicate a separator, like a slider with no inputs (i.e., [<-,-,-,->]). I'll think about it some more, feel free to add your own 2 cents.

I think something like a tag [separator] or #[separator] in the script would suffice. I'm using so many sliders that I would like to make everything clearer for myself :D

[qwerpoi]

New version 1.3.4, download here (http://www.avisynth.org/qwerpoi/Download.html) or use the mirror in the first post. Not a huge release, but some good stuff here. From the changelog:

* support for separate video window zoom fit

* updated included core filter definitions to AviSynth v2.56

* added menu options for goto next/previous bookmark (suggested by Alain2)

* option to quickly show AviSynth function definition dialog (suggested by Alain2)

* added new tag for separators in slider window (suggested by krisq)

* minor rearrangement of menu items for clarity (suggested by Fizick)

* fixed several issues with zoom fit feature (thanks foxyshadis, zemog, doxville, Alain2)

* fixed small bug with slider validation (thanks zemog)

One important new feature is the ability to quickly open the function definition dialog from the script. Say you wanted to change what the popup calltip says for AviSource. Simply place the text cursor on the filter name (or highlight the name, or place the cursor inside the filter's arguments), and use the command "Show function definition" in the right-click menu (default shortcut Ctrl+Shift+D). This will open up AvsP's function definition dialog, automatically selecting the appropriate filter, where you can edit the calltip, preset, or docpath. If you activate the "Show function definition" command and the cursor is on a word which is not in the function definition list, AvsP will open a dialog where you can add the function to the list. Hopefully this feature will make people more comfortable with editing the per-filter information, one AvsP's more powerful features.

Another feature which needs some discussion is the ability to add a separator in the slider window. Basically, you can add a [<separator>] tag in the text (shortcut Shift+F12) which upon refresh results in a separator line between sliders in the slider window. This is purely for visual organization, you can add as many as you want, it doesn't affect the script or the sliders in any other way.

Other than that, this version fixes some serious issues with the zoom fit feature, which also now works with the separate video preview window (if you have that option enabled). As always, post back with any new problems, questions, or suggestions.

[krisq]

This is great qwerpoi, thanks!
For the record, shortcut for separator is Shift+F12 ;)

[Alain2]

Translation was easy ^^

Thanks for all the additions, they are really good!! I can use again the separated window now, and the quick filters access / additions is really good, love it :)

Won't be able to test it a lot as I am going on holiday soon, but thanks for this new version!

Btw I had already a shortcut ctr+shift+d for a custom macro, after overwriting the avsp.exe this shortcut was defined for both the new feature and my macro ; I removed it for my macro, but maybe a conflict detection could be developped ; very low priority this though, if needed at all as the user can easily correct this ^^

[Henrikx]

Update :)

@qwerpoi
@everyone
I wish you a happy Christmas time....

[qwerpoi]

This is great qwerpoi, thanks!
For the record, shortcut for separator is Shift+F12 ;)
Whoops, thanks for pointing that out, I corrected the post.

Translation was easy ^^

Thanks for all the additions, they are really good!! I can use again the separated window now, and the quick filters access / additions is really good, love it :)

Won't be able to test it a lot as I am going on holiday soon, but thanks for this new version!

Btw I had already a shortcut ctr+shift+d for a custom macro, after overwriting the avsp.exe this shortcut was defined for both the new feature and my macro ; I removed it for my macro, but maybe a conflict detection could be developped ; very low priority this though, if needed at all as the user can easily correct this ^^
Ho, I thought that with the way it was set up one would overwrite the other, I'll make sure it works properly in the next version, thanks for letting me know.

Update :)

@qwerpoi
@everyone
I wish you a happy Christmas time....
Thanks for the update, and a happy Christmas time to you too :)

[Veiga]

@ qwerpoi
another good version in your return
translation for v134 attached

for you and @all a nice Christmas and a happy New Year

[rfmmars]

Yes the export display now matches the AVSp preview window, I have maded five separate test. However the following no longer works. I have many toggals and they all work but this one, it worked in 1.33 fine. No big deal, just info.

[Reduce Contrast Level 1=0]
colorYUV(cont_u=2)
[/Reduce Contrast Level 1]

This is now driving me nuts. I can no longer transfer AVSp .SES to another computer, only .AVSs. So I no longer get any slides or toggals to display, and they do not appear in the session script, tried this on two other workstations.........I.had a little trouble before with older versions but now its impossible to do.

I notice the .SES structure is completly different edited in Wordpad compared with older version.

My problem is on the workstsion that develope the scripts and sessions, my AVSp drive letter is e: and when I need to move the scripts and sessions to another computer, I use Wordpad to do a "Replace All: e: with c: Could this now be a problem with the new structure in version 1.34?

EDIT: Workaround

Copied script from AVSp window, pasted and edited in "notePad" copied that to a blank AVSp on another machine. save script and session and everything is fine. preview & external video also match. Just don't know why this extra step is nessary but that how I will do it from now on.

Love your work.

Richard

[Serbianboss]

When working with this script with 3 tag selection, for some time i have error: Out of memory and avsp shut down. I have 2 gb memory and when avsp shut down it has 700 mb psyhical memory.


AVISource("C:\Documents and Settings\Nenad\Desktop\vulkani.avi")
LoadPlugin("mt_masktools.dll")
LoadPlugin("AGC.dll")
import("C:\Program Files\AviSynth 2.5\plugins\limitedsharpenfaster.avs")

fft3dfilter(sigma=3.5,interlaced=true)


HDRAGC(max_gain=1.5)


limitedsharpenfaster(smode=4,strength=300)



Does this code is maybe extreme for avsp?

[qwerpoi]

@ qwerpoi
another good version in your return
translation for v134 attached

for you and @all a nice Christmas and a happy New Year
Thanks for the new translation, I've updated the links in the first post and AvsP website accordingly.

Yes the export display now matches the AVSp preview window, I have maded five separate test. However the following no longer works. I have many toggals and they all work but this one, it worked in 1.33 fine. No big deal, just info.

[Reduce Contrast Level 1=0]
colorYUV(cont_u=2)
[/Reduce Contrast Level 1]

This is now driving me nuts. I can no longer transfer AVSp .SES to another computer, only .AVSs. So I no longer get any slides or toggals to display, and they do not appear in the session script, tried this on two other workstations.........I.had a little trouble before with older versions but now its impossible to do.

I notice the .SES structure is completly different edited in Wordpad compared with older version.

My problem is on the workstsion that develope the scripts and sessions, my AVSp drive letter is e: and when I need to move the scripts and sessions to another computer, I use Wordpad to do a "Replace All: e: with c: Could this now be a problem with the new structure in version 1.34?

EDIT: Workaround

Copied script from AVSp window, pasted and edited in "notePad" copied that to a blank AVSp on another machine. save script and session and everything is fine. preview & external video also match. Just don't know why this extra step is nessary but that how I will do it from now on.

Love your work.

Richard
You're right, I did change the .ses structure, not in this version but several versions ago (I think). I don't think either structure would be able to work across multiple computers for the reason you describe - AvsP sessions store the complete filepath of each script, this is used to double-check whether or not any changes have been made since saving the session. Your workaround will do the job, in the meantime I'll think about ways to improve the process.

When working with this script with 3 tag selection, for some time i have error: Out of memory and avsp shut down. I have 2 gb memory and when avsp shut down it has 700 mb psyhical memory.


AVISource("C:\Documents and Settings\Nenad\Desktop\vulkani.avi")
LoadPlugin("mt_masktools.dll")
LoadPlugin("AGC.dll")
import("C:\Program Files\AviSynth 2.5\plugins\limitedsharpenfaster.avs")

fft3dfilter(sigma=3.5,interlaced=true)


HDRAGC(max_gain=1.5)


limitedsharpenfaster(smode=4,strength=300)



Does this code is maybe extreme for avsp?
I'm not really sure, it may depend on the input avi. Try using a simple source (like Version() instead of AviSource(...)) and see if it has the same problem, or try removing all the tags (save as an .avs file and open it) and see if it still crashes. I'll try and do some tests on this script on my pc, if it happens to you with a different script then post that as well.

[JoeTF]

I cannot force AvsP to open .avs files.
when I set up associations in windows, it's with open as default action, however stuuuupid AvsP starts with empty new file instead of file I want to open.
Can anyone help me with setting it up right?

[qwerpoi]

I cannot force AvsP to open .avs files.
when I set up associations in windows, it's with open as default action, however stuuuupid AvsP starts with empty new file instead of file I want to open.
Can anyone help me with setting it up right?
Um, sounds like you're doing it right, but just in case, here's how I did it step by step.


Right-click an .avs file, Open with >, Choose program...
Select AvsP from the list (you may need to browse for it)
Check the "Always use the selected program..." checkbox
Click OK

You may want to make sure you've selected the right version of AvsP, older versions may not work as well. After double-clicking the .avs file, go to "Help -> About AvsP" and verify that it's version 1.3.4 (or something relatively recent). If AvsP is still acting stuuuupid :rolleyes: , let me know, the problem may be more detailed than I think.

[JoeTF]

That's exactly what I did, many times. I tried with 1.3.3 and 1.3.4.

I have a feeling it has to be set up manually but I have no clue how do I set up DDE.

[foxyshadis]

There's no DDE in avsp, in fact it's almost never used except in microsoft and a few other huge companies' apps. All you have to do is browse for the program, and add "%1" after it.

Or you can just steal mine, modifying the paths accordingly (all backslashes should be doubled), save it to a .reg file and import it (doubleclicking is enough):

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.avs]
@="avsfile"

[HKEY_CLASSES_ROOT\avsfile]
@="AviSynth Script"
"EditFlags"=dword:00000000
"BrowserFlags"=dword:00000008

[HKEY_CLASSES_ROOT\avsfile\DefaultIcon]
@="C:\\WINDOWS\\system32\\AviSynth.dll,0"

[HKEY_CLASSES_ROOT\avsfile\shell]
@="Edit"

[HKEY_CLASSES_ROOT\avsfile\shell\Edit]

[HKEY_CLASSES_ROOT\avsfile\shell\Edit\command]
@="\"C:\\Program Files\\music-video\\encoding\\AviSynth\\avsp\\avsp.exe\" \"%1\""

[HKEY_CLASSES_ROOT\avsfile\shell\Play]

[HKEY_CLASSES_ROOT\avsfile\shell\Play\command]
@="\"C:\\Program Files\\music-video\\playback\\mplayerc.exe\" \"%1\""

[HKEY_CLASSES_ROOT\avsfile\shell\View]

[HKEY_CLASSES_ROOT\avsfile\shell\View\command]
@="\"C:\\Program Files\\music-video\\editing\\VirtualDub\\VirtualDub.exe\" \"%1\""

[JoeTF]

Thanks foxyshadis, that solved the problem.