|
|
| whugemann |
| Posted: Apr 17 2004, 09:03 AM |
 |
|
Unregistered
|
Yes, I've read the description in the help file!
I think, an example would do better than the explanations over there...
I created a directory named 'templates' below the VirtualDubMod directory and put in an script named 'halfframes.avst'. (The help file doesn't tell anything about the extension, I took this from the 'readme_AVISynthesizer.txt' file.)
The dropdown just doesn't offer a template and I can't put in a string manually.
The code of the script template is:
avisource("%f")
separatefields
HorizontalReduceBy2
What's wrong with that? |
|
| rfmmars |
| Posted: Apr 19 2004, 03:54 PM |
|
|
Advanced Member
Group: Members
Posts: 324
Member No.: 5438
Joined: 29-July 03
|
First the extension is .avs not .avst
avisource("f:\cine\xxx.avi")
complementparity
separatefields
I use notpad to edit. As far as to enter a string, someone else needs to come forward.
richard
|
|
| whugemann |
| Posted: Apr 21 2004, 10:28 AM |
|
|
Unregistered
|
No, that's not the solution.
Of course, I tried the extension "AVS" first. But don't forget that we are talking about a template, not an AVS script. And the extension of an AVIsynthesizer template is "AVST", according to the textfile supplied with VirtualDubMod.
Unlike in your script, the filename in a template therefore needs to be represented by the file variable %f.
I think, the problem is not within the script as the name of the template is just not listed in the dropdown. As VirtualDubMod claims this to be a functionality with no intelligence whatsoever, even the name of a bug script template should at least be displayed.
|
|
| Wilbert |
| Posted: Apr 21 2004, 11:02 AM |
|
|
Advanced Member
Group: Members
Posts: 132
Member No.: 6270
Joined: 11-September 03
|
What happens if you open the avi directly with 'open Via Avisynth'. |
|
| whugemann |
| Posted: Apr 23 2004, 08:01 PM |
|
|
Unregistered
|
>What happens if you open the avi directly with 'open Via Avisynth'.
I get an error message "Failed to create script."
As the script is based on a template, it cannot be created without a template.
"How do I use 'Open via AviSynth'?" is listed in the FAQs in the help file and on the Internet site. But the explanations given do not help my. An example would be much better :-( |
|
| whugemann |
| Posted: Apr 23 2004, 08:29 PM |
|
|
Unregistered
|
I finally made it!
The solution is quite easy -- as I suspected.
The templates directory needs to be named 'template', not 'templates' as is said in the FAQs. The file extension indeed has to be 'avst'.
My problems arose frome that fact that I unzipped the 'VirtualDubMod_1_5_4_1_All_inclusive.zip' file via drag & drop and thus the directory names were not used.
If you unzip the ZIP file properly, a directory 'template' is created and filled with some sample templates with file extension 'avst'. And everything behaves properly :-) |
|
| billou2k |
| Posted: Aug 6 2004, 03:31 PM |
|
|
Unregistered
|
Hi,
Is it possible to call the "open via avisynth"(templates) with the command line / script?
Cheers
|
|
| billou2k |
| Posted: Aug 9 2004, 02:52 PM |
|
|
Unregistered
|
no ideas anyone? 
I usually look into the jobs file to find out the syntax but using the "open via avisynth" with a pattern creates an avs file on the disk and the jobs file just contains the "virtualdub.open() to that avs file...
Is there no way to control the "open via avisynth " function directly?
cheers |
|
