Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
29th October 2007, 21:54 | #103 | Link |
Registered User
Join Date: Dec 2003
Location: Poland
Posts: 171
|
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?
__________________
(!sig) Last edited by krisq; 29th October 2007 at 22:08. |
30th October 2007, 00:34 | #104 | Link | ||
Registered User
Join Date: Oct 2002
Posts: 298
|
Quote:
Quote:
|
||
30th October 2007, 13:17 | #106 | Link |
Registered User
Join Date: Nov 2006
Posts: 83
|
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 Last edited by McCauley; 30th October 2007 at 13:31. |
30th October 2007, 17:53 | #108 | Link |
Registered User
Join Date: Oct 2002
Posts: 298
|
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. 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. Last edited by qwerpoi; 31st October 2007 at 00:13. |
30th October 2007, 19:08 | #109 | Link |
Registered User
Join Date: Dec 2003
Location: Poland
Posts: 171
|
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?
__________________
(!sig) |
31st October 2007, 00:12 | #110 | Link | |
Registered User
Join Date: Oct 2002
Posts: 298
|
Quote:
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. |
|
31st October 2007, 09:07 | #112 | Link | |
Registered User
Join Date: Dec 2003
Location: Poland
Posts: 171
|
Quote:
So ! [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')
__________________
(!sig) Last edited by krisq; 31st October 2007 at 09:40. |
|
2nd November 2007, 03:09 | #113 | Link | |||
Registered User
Join Date: Oct 2002
Posts: 298
|
Quote:
Quote:
Quote:
|
|||
8th November 2007, 20:10 | #114 | Link |
dumber every day
Join Date: Dec 2006
Location: Planet Earth
Posts: 154
|
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 ) |
9th November 2007, 02:29 | #115 | Link | |
Registered User
Join Date: May 2005
Posts: 236
|
Nice release as usual ^^ Fr translation updated (that was an easy one ^^)
Quote:
Concerning EEDI2 (and others) showing only once.. here 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 ? ++ Last edited by Alain2; 9th November 2007 at 02:34. |
|
9th November 2007, 10:11 | #116 | Link | |
Angel of Night
Join Date: Nov 2004
Location: Tangled in the silks
Posts: 9,559
|
Quote:
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. |
|
9th November 2007, 21:50 | #118 | Link |
Registered User
Join Date: Mar 2005
Location: Near Luxemburg
Posts: 16
|
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 |
11th November 2007, 20:34 | #119 | Link |
Registered User
Join Date: Mar 2005
Location: Near Luxemburg
Posts: 16
|
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 |
11th November 2007, 21:50 | #120 | Link |
Registered User
Join Date: May 2005
Posts: 236
|
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.. ? |
Thread Tools | Search this Thread |
Display Modes | |
|
|