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. |
31st December 2001, 06:37 | #1 | Link |
Registered User
Join Date: Oct 2001
Posts: 80
|
avs script help needed?
Ive ran into an issue with my avs script..below:
LoadPlugin("F:\DVDStuff\MPEG2DEC.dll") mpeg2source("F:\Movie\low.d2v") Crop(0,56,720,364) BicubicResize(352,176,0,0) Blur(-.3) AddBorders(0,32,0,32) ResampleAudio(44100) OR LoadPlugin("F:\DVDStuff\MPEG2DEC.dll") mpeg2source("F:\Movie\low.d2v") Crop(0,56,720,364) BicubicResize(352,176,0,0) Sharpen(0.3) AddBorders(0,32,0,32) ResampleAudio(44100) What will happen..is that CCE will make vaf file,..starts to encode the video file..then after about couple mins..the speed will get ridiculously, fast..like 8.5+, I check the video..and it gives me nothing.....However, if I open the avs file in media player, it plays just fine....???? Taking the Blur/Sharpen command out, and it also works find...CCE 2.5 doesnt seem to like the Blur/Sharpen command for some reason..any ideas??...Im using the latest version of Avisynth (beta 5) & mpeg2dec.dll....Ive tried avisynth version beta 3...but same result TIA |
2nd January 2002, 23:50 | #4 | Link |
Retired
Join Date: Jan 2002
Location: Netherlands
Posts: 1,529
|
What's bicubic resize with arguments (0,0) anyway? Isn't there supposed to be something like (0.333,0.333) or (0,0.75) or (0,0.5) or something like that? If it's not resizing right then maybe that explains the speed-up and the resulting crewed-up output file.
|
3rd January 2002, 06:37 | #5 | Link |
Registered User
Join Date: Oct 2001
Posts: 80
|
nope moving the commands around didnt help...it seems to be more of CCE error than avisynth...if when doing multipass, CCE makes a call to the avs script however many of times the multiple is....it encodes fine until CCE gets to the second pass...and that is when I get my access violation error..no matter the OS, 98, 2000, or XP
|
6th January 2002, 16:59 | #7 | Link |
Registered User
Join Date: Nov 2001
Posts: 45
|
I've seen this behaviour before. In my case, it was because a .vaf file with the same name already existed in the output-directory (from a previous try). Deleting that file (or choosing another output-filename) returned things to normal.
|
|
|