AvsP v2.0.2 (10/27/07)

[foxyshadis]

Some plugins (GetSystemEnv is another one, but it doesn't crash) just don't seem to mix well with the way avsp looks up their arguments. Probably compiled against older headers.

[Henrikx]

Update----:cool::rolleyes:

[krisq]

I don't get it. I can't turn off 'auto-generate' for any filter. The checkbox unchecks, but after restart it's back on. Am I missing something?

[qwerpoi]

I don't get it. I can't turn off 'auto-generate' for any filter. The checkbox unchecks, but after restart it's back on. Am I missing something?
Urgh, you're right, I'll try and get a bugfix up by tomorrow. Sorry about that.

when loading v2.0.2, got this message, in version 1.0.4 cant copy/move code into clipboard.
could someone help?
[Mon Oct 29 10:18:15 2007]
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character R
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character G
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character B
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character L
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character U
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character T
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character R
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character G
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character B
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character L
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character U
Error parsing LoadPluginEx2_LoadPlugin plugin parameters: unknown character T
Traceback (most recent call last):
File "run.py", line 6, in <module>
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 11376, in main
File "wx\_core.pyo", line 7700, in __init__
File "wx\_core.pyo", line 7352, in _BootstrapApp
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 11366, in OnInit
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 3373, in __init__
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 3931, in defineFilterInfo
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 4218, in getFilterInfoFromAvisynth
File "avisynth.pyo", line 95, in Release
WindowsError: exception: access violation reading 0x029D58C0
I'll try and do something about this as well, no guarantees though, since it might be difficult to approach.

[Terka]

thank you!

[McCauley]

Thanks for this useful tool, i can't imagine using avisynth without it!
May i make a suggestion?

When zooming in, the whole filterchain is processed again with a pointresize at the end (that's correct, isn't it?). That is very annoying when using heavy filterchains that take minutes to render.
Would it be possible to just use the last output with pointresize, so the zoom call in AVSP would take only a few seconds?
Don't know how this could work, maybe AVSP needs an own cache for the frames to pointresize them, so the whole filterchain can be avoided?!

Another useful function would be if AVSP would add LoadPlugin() instead of Directshowsource() when dropping .dll from the plugin directory files in it's window.

Regards
McCauley

[krisq]

Another useful function would be if AVSP would add LoadPlugin() instead of Directshowsource() when dropping .dll from the plugin directory files in it's window.


You can already do that. Check 'Options/Extension templates'... ;)

[qwerpoi]

Still working on fixing some bugs, but for now here's a new bugfix to fix the issue with presets krisq brought up:

http://avisynth.org/qwerpoi/AvsP_v2.0.2_bugfix3.zip

To apply the bugfix, simply copy the file AvsP.pyo from the zip file into your directory containing AvsP.exe (replace any older bugfix files). Presets should now work properly. Without this bugfix AvsP v2.0.2 may have deleted some of your presets, this is all related to me trying to change the database structure to be more consistent :(. Again, I apologize for any frustration this may have caused.

Would it be possible to just use the last output with pointresize, so the zoom call in AVSP would take only a few seconds?
Don't know how this could work, maybe AVSP needs an own cache for the frames to pointresize them, so the whole filterchain can be avoided?!
This is a good point, it should be quite doable (only for the doubling/halving zooms, of course). I'll see what I can do.

[krisq]

Checkbox is fine after bugfix, thanks :).
But still, I'm afraid there is something I don't fully understand.
Short functions names are based on long names, right?
So DGIndex_MPEG2Source equals MPEG2Source, am I correct?
Than why after I turn off auto-generate and enter my own definition for DGIndex_MPEG2Source, MPEG2Source still have default generated values?

[qwerpoi]

Checkbox is fine after bugfix, thanks :).
But still, I'm afraid there is something I don't fully understand.
Short functions names are based on long names, right?
So DGIndex_MPEG2Source equals MPEG2Source, am I correct?
Than why after I turn off auto-generate and enter my own definition for DGIndex_MPEG2Source, MPEG2Source still have default generated values?
F&#%# :mad:, it's frustrating to not have the time to provide appropriate quality assurance with these releases. Here's (yet another) bugfix, this should fix the issue pointed out above.

http://avisynth.org/qwerpoi/AvsP_v2.0.2_bugfix3.zip

To apply the bugfix, simply copy the file AvsP.pyo from the zip file into your directory containing AvsP.exe (replace any older bugfix files). Now presets for plugins should work properly as well. Again, my apologies for the inconvenience, I really appreciate the helpful feedback, so feel free to let me know if there are still issues on this matter.

[rfmmars]

Again, my apologies for the inconvenience, I really appreciate the helpful feedback, so feel free to let me know if there are still issues on this matter.

We are just happy your here!

Richard
photorecall.net

[krisq]

Again, my apologies for the inconvenience, I really appreciate the helpful feedback, so feel free to let me know if there are still issues on this matter.

It's nothing to be sorry about. It is I who should be thanking you for one of the best tools I've ever come across.
So :thanks:!

[EDIT]

I' ve just found a little annoyance (nothing crucial). I work with undocked preview window.
I like to have my script window big for better overview so preview window is often in the background with just a part of video visible. Here is the thing: when I drag the seek bar in script window, the preview window jumps to front, gets focus and hides my script under it.
I don't reckon earlier versions were doing that.

[EDIT2] :)

Another one :)
For some reason Autocomplete window for some letters is much smaller. e.g. for 'D' it's ok, whole 'DGIndex_MPEG2Source' is visible, but for 'W' it shows 'WAVS...' (WAVSource, which is shorter than 'DGIndex_MPEG2Source')

[qwerpoi]

We are just happy your here!

Richard
photorecall.net
It's nothing to be sorry about. It is I who should be thanking you for one of the best tools I've ever come across.
So :thanks:!
I've always been quick to criticize buggy software, so it's a bit frustrating to be the one releasing it :p. Thanks for sticking with it and being more forgiving than I am, I appreciate it.


I' ve just found a little annoyance (nothing crucial). I work with undocked preview window.
I like to have my script window big for better overview so preview window is often in the background with just a part of video visible. Here is the thing: when I drag the seek bar in script window, the preview window jumps to front, gets focus and hides my script under it.
I don't reckon earlier versions were doing that.

I'll take a look into the issue, thanks for pointing it out.


For some reason Autocomplete window for some letters is much smaller. e.g. for 'D' it's ok, whole 'DGIndex_MPEG2Source' is visible, but for 'W' it shows 'WAVS...' (WAVSource, which is shorter than 'DGIndex_MPEG2Source')
I've noticed this myself, it's pretty annoying. I didn't write the code to display the autocomplete window, but I'll see if I can come up with some kind of workaround.

[Spuds]

Thanks for the recent set of bug fixes, particularly 202, that allowed me to use my favorite editor again!

I get the following error pretty often when using the program and the video preview.

Traceback (most recent call last):
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 5826, in OnMenuVideoRefresh
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 8947, in ShowVideoFrame
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 9489, in PaintAVIFrame
File "pyavs.pyo", line 322, in DrawFrame
File "pyavs.pyo", line 301, in _GetFrame
File "avisynth.pyo", line 277, in GetFrame
WindowsError: exception code 0xe06d7363

prior to v202 the error was similar:
Traceback (most recent call last):
File "AvsP.pyo", line 7081, in OnPaintVideoWindow
File "AvsP.pyo", line 9414, in PaintAVIFrame
File "pyavs.pyo", line 322, in DrawFrame
File "pyavs.pyo", line 301, in _GetFrame
File "avisynth.pyo", line 277, in GetFrame
WindowsError: exception code 0xe06d7363

I think I tend to get the error more when using mvtool scripts where several frames are in play, not sure I can say thats the only type of script where this error gets thrown but it maybe a clue that helps (or maybe not :) )

[Alain2]

Nice release as usual ^^ Fr translation updated (that was an easy one ^^)

In AvsP v2.0.2, only EEDI2_EEDI2 will show up in the dialog, meaning you only have to define your customizations once, the scripts will automatically reflect the customizations for both long and short names. Because I made this change, those who made customizations with the short plugin names will lose those customizations - for that I apologize. There was a more serious bug related to this issue that krisq pointed out that I fixed, so again, if you have made or plan to make database customizations, be sure to apply this bugfix first.

Actually, when doing ctrl+shift+d to open the dialog on the short function name in a script, it now brings the user defined functions and treat the short name as a new function name; it should first look into the long names before creating a new one..

Concerning EEDI2 (and others) showing only once.. here (http://img46.imageshack.us/img46/5813/temptp0.jpg) is what I have.. Is it normal ?

Also personnaly I quite miss the possibility of defining manually for each function where to look for its help file ; for avsi for instance I used to point to the avsi file itself, it was a quick and easy way to open a custom avsi and modify it if required (and often for popular user scripts the description is part of the script, as a comment). Would it be possible to re-introduce a field for each function definition that if filled in would override the current automatic search behaviour ? This field does not need to be part of the import / export functions used to share the functions between users (as it is not generic but user specific, so no need to share it)

After auto-completion of a function name + parameters list, is there a shortcut to quickly jump to the undefined parameters indicated with a ? character ?

++

[foxyshadis]

I think I tend to get the error more when using mvtool scripts where several frames are in play, not sure I can say thats the only type of script where this error gets thrown but it maybe a clue that helps (or maybe not :) )

That usually just means you ran flat out of memory. Check the process's VM Size in task manager. If this goes near 2GB, or physical+swap memory if it's less than 2GB, it won't be able to allocate room for another frame and will either throw an error or just crash, depending on whether the filter checks for that. Most don't, mvtools included, but the core filters do.

If you have smallish frames (SD or HD) lowering SetMemoryMax might help alleviate the problem. If you work with hugefreakingnormous stuff or ton of mvtools/nnedi/etc, you just get used to running half the script at a time or cutting the image into pieces and processing separately, and closing avsp or vdub very regularly to reset it.

[Spuds]

That usually just means you ran flat out of memory. Check the process's VM Size in task manager.

Bingo ... thanks for the tips on setmemorymax, I had it set much to high.

[SixdeeBee]

I am running into a little problem with using > avs2avi < within AvsP.
While encoding it shows me the button > Stop < but when I hit the button I get an error message. To stop the encoding I have to leave AvsP but avs2avi stays in the RAM. Only with the TaskManager can avs2avi be stopped.

SixdeeBee

[SixdeeBee]

Ok, here is another question:

Got the following situation with the > slider < option in version 2.02:

Example:

AviSource("source.avi ...)

*
* some prefilters
*

# Declaration of a maximum number of used frames as parameters in a chain of plugins
maxframes=nnn

# First slider sets a start position inside a clip
start=[<"First frame",0,(maxframes-1),0>]

# Second slider sets an end position inside a clip
end=start+[<"Last frame",1,maxframes,50>]
*
# Plugins which need the same start and end frame number
Plugin#1(start, end, parameter list ...)
*
Plugin#2(start, end, parameter list ...)
*
*
*
Plugin#n(start, end, parameter list ...)
*

The problem is that I cannot substitute a numerical constant with a named variable (or constant) inside a slider. When I do so, I get an error:

> Invalid slider text: invalid number <


Writing a named variable (maxframe) to the > max. value < line in the window > Define user slider < gives me the error message > This field must contain a number <.

All this is logical but as a result I cannot use named variables/constants in a slider arrangement, only numericals are allowed.

My question is:

Did I overlook a hidden feature which allows me to use named variables/constants (like a,b,c or maxframes etc.) inside a slider-command block ?
If not, would it be a good idea to add it to the wish list for a future version ?

SixdeeBee

[Alain2]

Question:
After adding nnedi.dll to my plugins dir, it was available in avsp list of function (didn't check it was not there before thought), but one parameter was missing (dh) ; I thought it was supposed to build the parameters list automatically from the dll info.. ?

[qwerpoi]

I think I tend to get the error more when using mvtool scripts where several frames are in play, not sure I can say thats the only type of script where this error gets thrown but it maybe a clue that helps (or maybe not :) )
Thanks foxyshadis for finding the cause of the error, perhaps I'll try and catch this type of crash to report a more useful message.

Nice release as usual ^^ Fr translation updated (that was an easy one ^^)


Actually, when doing ctrl+shift+d to open the dialog on the short function name in a script, it now brings the user defined functions and treat the short name as a new function name; it should first look into the long names before creating a new one..

Thanks for the (short) translation update! You're right about the ctrl+shift+d shortcut, I'll try to get that fixed in the next version.

Concerning EEDI2 (and others) showing only once.. here (http://img46.imageshack.us/img46/5813/temptp0.jpg) is what I have.. Is it normal ?
I don't think that should happen if you're running v2.0.2 with the bugfix (http://forum.doom9.org/showthread.php?p=1059559#post1059559), let me know if that's what you're running and plugins are still showing up twice.

Also personnaly I quite miss the possibility of defining manually for each function where to look for its help file ; for avsi for instance I used to point to the avsi file itself, it was a quick and easy way to open a custom avsi and modify it if required (and often for popular user scripts the description is part of the script, as a comment). Would it be possible to re-introduce a field for each function definition that if filled in would override the current automatic search behaviour ? This field does not need to be part of the import / export functions used to share the functions between users (as it is not generic but user specific, so no need to share it)
The workaround for this is to create a shortcut in the plugins directory to whatever file you want to open when clicking on the calltip. Normally AvsP searches the plugins directory, the help corefilters directory, and the help externalfilters directory for help files. It looks for any files with the same name as the function with one of the following extensions - .htm, .html, .txt, and .lnk (a shortcut file). So in your case if you create a shortcut to the .avsi file in the plugins directory, the .avsi file will open when you click on the calltip. To me, this seems about the same amount of work as having help file information as part of the database, but with the advantage of keeping the database streamlined. Let me know if you still think there are disadvantages that I haven't forseen.

After auto-completion of a function name + parameters list, is there a shortcut to quickly jump to the undefined parameters indicated with a ? character ?
No, although it's an interesting suggestion, so I'll think about the best way to do that.

I am running into a little problem with using > avs2avi < within AvsP.
While encoding it shows me the button > Stop < but when I hit the button I get an error message. To stop the encoding I have to leave AvsP but avs2avi stays in the RAM. Only with the TaskManager can avs2avi be stopped.

SixdeeBee
I'll take a look into the issue - could you give me the exact error message you see when you hit stop?


Did I overlook a hidden feature which allows me to use named variables/constants (like a,b,c or maxframes etc.) inside a slider-command block ?
If not, would it be a good idea to add it to the wish list for a future version ?

SixdeeBee
Currently it's not possible, but it's a good suggestion, and it may show up in a future version. It definitely would take a lot of work to do it right, so I wouldn't hold your breath :p

Question:
After adding nnedi.dll to my plugins dir, it was available in avsp list of function (didn't check it was not there before thought), but one parameter was missing (dh) ; I thought it was supposed to build the parameters list automatically from the dll info.. ?
AvsP automatically builds the parameter list from the dll only if the function doesn't exist in the database, I believe nnedi was added in v2.0.2. I haven't double checked yet, the missing parameter is probably due to an update in nnedi, if that's the case I'll update the database by the next version.

[Terranigma]

AvsP automatically builds the parameter list from the dll only if the function doesn't exist in the database, I believe nnedi was added in v2.0.2. I haven't double checked yet, the missing parameter is probably due to an update in nnedi, if that's the case I'll update the database by the next version.
Alain2's right. It doesn't show anything for the dh parameter in nnedi as you can clearly see.
http://img222.imageshack.us/img222/8160/nnediandavspit8.png
And i'm pretty sure that i'm using the latest version (which tritical released publically).

[SixdeeBee]

I am running into a little problem with using > avs2avi < within AvsP.

Sorry that you had to ask for the error message, here it comes:


File "C:\Programme\AviSynth 2.5\AvsP\tools\avs2avi_gui.py", line 206, in OnButtonRunStop
ctypes.windll.user32.SendMessageA(self.jobInfo['pid'], WM_CLOSE, 0, 0)
NameError: global name 'ctypes' is not defined


:stupid:


SixdeeBee

[SixdeeBee]

@qwerpoi

so I wouldn't hold your breath

Ok, in order to not hold my breath too long on a low level I offer this simple solution : :)

1. Creation of the function:

function givevalue(int "val")
{ return(val)}


2. Example:

Put four 4:3 full-screen clips with 720 x 576 Pixels to one 16:9 - 1024 x 576 widescreen .

The slider > Bordercolor < controls the pillarbox-border-colors of all individual pictures simultaneously over the range from 0 to 16777215 colors.

Import("C:\programs\AviSynth 2.5\functions\givevalue.avs")
#
a=AviSource("source_1.avi",false,pixel_type="YUY2")
b=AviSource("source_2.avi",false,pixel_type="YUY2")
c=AviSource("source_3.avi",false,pixel_type="YUY2")
d=AviSource("source_4.avi",false,pixel_type="YUY2")
#
val=givevalue([<Bordercolor",0,16777215,50>])
#
a=a.AddBorders(152,0,152,0,val).ReduceBy2().Crop(2,2,-2,-2,align=true).AddBorders(2,2,2,2)
b=b.AddBorders(152,0,152,0,val).ReduceBy2().Crop(2,2,-2,-2,align=true).AddBorders(2,2,2,2)
c=c.AddBorders(152,0,152,0,val).ReduceBy2().Crop(2,2,-2,-2,align=true).AddBorders(2,2,2,2)
d=d.AddBorders(152,0,152,0,val).ReduceBy2().Crop(2,2,-2,-2,align=true).AddBorders(2,2,2,2)
#
StackVertical(StackHorizontal(a,b),StackHorizontal(c,d))

I understand that it would be a little bit tricky to put a more flexible slider routine in AvsP.
Possibly the simple trick can help to circumvent those problems.

SixdeeBee


Edit:
Reading this post again let me see that the solution described does not hit the nail to the top.
Please ignore it, it had been mixed up with another problem.

(There is a group oft pupils in the age of around 11 years making a stop-motion film in their arts lessons at school. Advising them, including their teacher, always makes fun ... but sometimes the actions get a little bit chaotic and informations get mixed up ... please excuse my confusing post )

SixdeeBee

[Alain2]

@qwerpoi
I did have put the bugfix pyo in avsp folder, so I guess it is activated (is there a way of checking ? If not, maybe next times you could make it modify the about dialog box to indicate it)

Using links to the file I want as help file is a satisfactory workaround, I'll try that.
[edit] I have a bug with that :
Traceback (most recent call last):
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 5593, in OnMenuEditFilterHelp
File "D:\Research\Python\AvsP\Translations\AvsP_v2.0.2\AvsP\AvsP.py", line 1131, in ShowFilterDocumentation
WindowsError: [Error 1155] Aucune application n'est associée au fichier spécifié pour cette opération: u'C:\\Program Files\\AviSynth 2.5\\plugins\\Docs\\Mpeg2Source_Lnk.lnk'
It says I don't have a software associated to .lnk ; but under explorer if I double click on the link it launch the the correct software.. (in my case DGDecodeManual.html in firefox)

However I have another problem now : Asking for help when the cursor is in the function parameters list is ok, but asking for help when the cursor is on the function name itself always open the same file from the help folders defined in the options (AVSShock.html in my case, or if I delete it it's masktools.html, etc) ; I guess it could be related to the bug ctrl+shift+d not finding the correct function on short function name and creating a new user function


[edit 2]
Somehow my options.dat became corrupted :(
Traceback (most recent call last):
File "run.py", line 6, in <module>
File "AvsP.pyo", line 11358, in main
File "wx\_core.pyo", line 7700, in __init__
File "wx\_core.pyo", line 7352, in _BootstrapApp
File "AvsP.pyo", line 11348, in OnInit
File "AvsP.pyo", line 3368, in __init__
File "AvsP.pyo", line 3732, in getOptionsDict
TypeError: list objects are unhashable
And unfortunately, now this file contains all the settings, including the textstyles and shortcuts.. Would it be possible to keep these as separate files (and a separate one for custom filters definition as well) ? So that if one becomes corrupted we don't loose it all..

[stickboy]

Some plugins (GetSystemEnv is another one, but it doesn't crash) just don't seem to mix well with the way avsp looks up their arguments. Probably compiled against older headers.Hey, sorry I'm late to this thread. Is the above still a problem? Is there anything I need to change in my plug-ins? (They likely are compiled against an older version of avisynth.h since I haven't recompiled any of them in years; I don't even have MSVC6 installed anymore and haven't gotten around to setting them to build in VC7 or VC8. That said, I'm not sure why compiling against an older header should matter if things are binary compatible.)

[Terka]

tried versions 2.0 - 2.0.2 and the behaviour is the same
copying is available only 1 or 2 times. after that when i select something and press ctrl-c or via RMB i got the errror described above.

[foxyshadis]

Hey, sorry I'm late to this thread. Is the above still a problem? Is there anything I need to change in my plug-ins? (They likely are compiled against an older version of avisynth.h since I haven't recompiled any of them in years; I don't even have MSVC6 installed anymore and haven't gotten around to setting them to build in VC7 or VC8. That said, I'm not sure why compiling against an older header should matter if things are binary compatible.)

I have no idea what it was, all I can tell you is that I recompiled it and avsp stopped complaining. I can't really tell why, though, avsp has stopped complaining about the old one recently as well, might have been a parser issue.

[Caroliano]

Some small bugs in the sliders and such, with FF3dfilter + commented Deen, and in the sliders with ColorYUV, that can have positive or negative values, but avsp only show positive values by defaut, although it shows the negative values until where you determine to use.

Screenshot: http://img84.imageshack.us/my.php?image=avspbuguv0.png

I'm not sure that the fact that it don't show the global soothe setings, only the in-filter settings, is also a bug or is an desired behaviour. Due to problems of avisynth not load with soothe.avsi in the plugins folders, I copied it's content in the main script, and it seems to work.

Besides those realy minor anoyances, AVSp is great! Many thanks for your work.

EDIT: Besides the strange "standalone" sharpen in the screenshot, there is also an "sharpen" slider inside FFT3dfilter, as it should, that go from 0 to 1. This parameter also should acept negative values, and I think that it also acepts greater than 1 values (but I'm not sure about the last).

[jethro]

I have this problem with AvsP which suddenly won't start.

from the log:

[Sat Jan 12 22:39:56 2008]
Traceback (most recent call last):
File "run.py", line 6, in <module>
File "AvsP.pyo", line 11358, in main
File "wx\_core.pyo", line 7700, in __init__
File "wx\_core.pyo", line 7352, in _BootstrapApp
File "AvsP.pyo", line 11348, in OnInit
File "AvsP.pyo", line 3369, in __init__
File "AvsP.pyo", line 3927, in defineFilterInfo
File "AvsP.pyo", line 4117, in getFilterInfoFromAvisynth
WindowsError: exception: access violation reading 0x00000000

I've tried deleting the entire AvsP folder and and downloading fresh AvsP 2.02 from the website but it still does not start. Weirdest thing is that it always worked great for me, and it worked normally just today but I can't remember any real changes I could have made in Windows to break it. :devil::confused:
I would appreciate help in this matter as I must admit I'm hooked on AvsP now...

[check]

looks like an out of memory error from avisynth. Try rebooting your computer, THEN a full delete/redownload.

[foxyshadis]

Have you tried emptying out your avisynth folder, as well? If one of them is interfering, that would fix it. Then you could narrow it down by adding them back until it breaks again.

[jethro]

Great, works now:).
Foxyshadis you were right and it seems Avisynth was causing this error. I re-installed 2.57 and AvsP is back (although Avisynth had worked in e.g VirtualDub then).
Plugins are "redeemed" as I moved them back to Avisynth plugins folder without consequence.

Uff. Time to get back to fiddling with scripts. Thanks for your help:)

[Zarxrax]

qwerpoi, I wonder if you could stop Avsp from forgetting whats on the clipboard when you close the program? That's really annoying, since I have a habit of just opening up a file to copy something, close it, then open up something else to paste it into. Is that something you think you could fix?

[salehin]

AvsP doesn't seem to support .grf (made with GraphEdit) to pass it through avisynth. I use it with h264.ts file (BBC HD). An example:SetMemoryMax(128)
clip1=DirectShowSource("K:\Temp\ffdshow.GRF",fps=25,audio=false).ConverttoYV12()

Here is the error msg (cf attachement). Hope to see .grf support in later AvsP :)

[foxyshadis]

And you're sure Virtualdub doesn't give the same error? Because I've used grf files in avsp just fine.

[salehin]

And you're sure Virtualdub doesn't give the same error? Because I've used grf files in avsp just fine.

Because I never used vd and grf together, i'll simply take it from an expert like you as a fact :D

It seems my ffdshow (, for some unknown reason,) was not connecting .. after reinstalling it, AvsP works fine with .grf. Sorry for that. Earlier I also made a .grf with cyberlink's h264 - it works perfectly with AvsP. That's what made me reinstalling ffdshow.

[Fizick]

I see RGB values reading from screen. It is useful!
Question (suggestion): can we have YUV values reading from screen, if script produces YUY2 or YV12?

[Spuds]

@Fizick

Look under program settings / video 1 / Customize video status bar...

You can add many color readouts including yuv.

[bidmead]

Feature suggestion:

Proposal: The Trimmer currently creates Trims. Optionally there should be a user setting that allows it to create Dissolves instead. (Dissolve(X,Y,0) is functionally equivalent to Trim(X) ++ Trim(Y))

Reasoning: Removal of ads to restore (usually old) movies is my prime use for AvsP. Straight cuts often don't work very well because of jumps in the audio, or an ugly video segue. Conversion to a dissolve is usually an excellent compromise.

Qwerpoi has very sportingly provided a macro that simplifies conversion from a Trim to a Dissolve:

entry = avsp.GetTextEntry('Select and copy the trim commands here:')
splitentry = entry.split('++')
if len(splitentry) == 2:
newString = 'Dissolve(%s, %s, 25)' % (splitentry[0], splitentry[1])
avsp.InsertText(newString, pos=None)

But I seem to be using this very often, and it occurs to me that the Trim editor could provide the Dissolve directly, with straight cuts being achieved when required simply by setting the frames value to zero.

What does the team think?

BTW, It's self-evident that AvsP now deserves its own forum, rather than just having to be crammed into one long thread.

--
Chris

[doxville]

@bidmead

Great idea. I rather use dissolve than the normal trims, exactly for the reasons you named.
My proposal would be to have an option in the trim editor box where you can choose between 'Apply as Trim' and 'Apply as Dissolve [__] frames'.
That would be fabulous!

[check]

Is there any way to force the video slider position to be global, even if the various videos are not all the same resolution/etc?

[Harukalover]

Is there any way to force the video slider position to be global, even if the various videos are not all the same resolution/etc?
Options --> Program Settings --> Video 2.

Uncheck Enable frames stored per tab.

[Jawed]

I use a separate video preview window in AvsP 2.0.2.

When I set the preview window zoom to "Fit inside window", and then open the preview window, then close the preview window the preview window re-opens (after a short pause).

This seems to occur only when I first close the preview window, after starting AvsP. So all further interactions (opening/closing) with the preview window are fine.

AvsP will only do this once per session, i.e. I have to exit AvsP and then restart it before I will encounter this bug again.

I don't use "Fit inside window" very much, so it's no big deal.

Jawed

[introspect]

Hello all, I think that I've found two bugs with avisynth.py. It doesn't seem like these functions are being called at the moment, but here are the two that I've found anyway.

Bug 1: A YUV type PVideoFrame will always return half of its height, even if GetHeight is called with PLANAR_Y.

Possible solution: In avisynth.py, replace Line 327 with
if self.p.contents.pitchUV!=0 and (plane in (PLANAR_U, PLANAR_V)):
or
if self.p.contents.pitchUV!=0 and (plane==PLANAR_U or plane==PLANAR_V):

Bug 2: A VideoInfo object always claims that its stream has zero bits per pixel

Solution: Line 198 contains the BitsPerPixel function. Replace the entire definition with:
def BitsPerPixel(self):
if self.IsRGB24():return 24
elif self.IsRGB32():return 32
elif self.IsYUY2():return 16
elif self.IsYV12():return 12
else :return 0

Edit:

Problem: BMPSize compiles just fine but blows up if it's called
Solution: Replace Line 207:
if IsPlanar(self):
with
if self.IsPlanar():

[chrishallowell]

I've just loaded the most recent version and when I try and run it I get this in the file: AvsP.exe.log

Traceback (most recent call last):
File "run.py", line 5, in <module>
File "AvsP.pyo", line 59, in <module>
File "pyavs.pyo", line 31, in <module>
File "avisynth.pyo", line 4, in <module>
File "ctypes\__init__.pyo", line 415, in __getattr__
File "ctypes\__init__.pyo", line 340, in __init__
WindowsError: [Error 126] The specified module could not be found

Any ideas?

Thanks,
Chris

[foxyshadis]

That means avsp can't find avisynth.dll for whatever reason. You should reinstall avisynth.

[halsboss]

Hi I've just started to look at this thread and it seems like a great tool ! Does anyone know if the latest download http://avisynth.org/qwerpoi/index.html includes the bugfixes etc as the dates don't see to coincide with http://forum.doom9.org/showthread.php?p=1059559#post1059559 ... is it still being updated ?

[bidmead]

@halsboss I don't think 2.0.2 does include that bugfix. But it's no big deal. Yup, AvSP has some residual bugs, but this doesn't take away from the fact that it's a great piece of software.

Apply the bugfix, if these bugs bother you. Post any new bugs that crop up in use up here on the forum. Qwerpoi's been very responsive in the past.

Enjoy. (It's amazing...)

--
Chris

[Socio]

I like this tool but have a suggestion;

Could you implement the ability to point to other encoders other than X264.exe for test encodes so we can get get a better idea of with the final encode will look like using the same encoder we plan to you for the final encode?