Using filters in DVD Rebuilder
Collapse
This is a sticky topic.
X
X
-
Yes I am using the filter editor box to input text in. Are these AVS files to be found in the 'working' folder?Comment
-
-
im still getting this message when hc opens up...is there something i may have pushed .....well i thought i might have had the filter thing figured out, but when i started the dvd rebuilder and ran it, when the hc encoder opened up, i got this message
runtime error!!
program:C:\program files\DVD-RBPRO\encoders\hc encoder\hcbatch.exe
this application has requested the runtime to terminate it in an unusual way.
please contact the application's support team for more info..
MarkComment
-
Have you tried removing the "loadplugin" command from the script. Just put the filters in the avisynth plugin folder(only the supported version and not all) and remove the loadplugin command from the filter editor.Comment
-
The filters are obviously not working. As a result you are getting an illegal size that will not be accepted by the encoder. The illegally sized output is actually a video representation of an error message provided by AVISYNTH.
Try this. Open one of the AVS files with Windows Media Player after doing PREPARE. It should display the error it is receiving in red text on a black background. It will also tell you the line number that is the offending filter/action.
Here is the text from the change log from when the filter editor was added.
- Added an Expert AVS option in which you can add text that will be added to AVS
files. This is meant to support filters -- but can also be used to activate
other AVISYNTH commands. This is an EXPERT OPTION. If you are not intimately
familiar with AVISYNTH... leave it alone. It can make your encodes fail
completely if incorrectly used. Note: Don't use blank lines.
I highly recommend that folks DO NOT USE FILTERS unless you have a specific reason for doing so. Remember -- filters distort the original, and when used indescretely will hurt the output quality rather than help it. The same filter that might improve the appearance of a poorly built original disc, might degrade one that is of better quality.Comment
-
Like I said, you dont have to extract all versions of the filter in the plugin folder of avisynth.
re-create the plugin folder and add only the specific version of filter that your machine supports. for eg if it does not support SSE just put the removegrain.dll in the plugin folder and not the others.Comment
-
Sometimes you have to be very careful before adding filters to the plug-in folder. There are a lot of filters out there -- and some of them use the same function names. When that happens AVISYNTH has to decide which is the one you really want somehow -- if you're not familiar with how it makes that decision (I'm not), it becomes a crapshoot as to whether you're getting what you think you are.
Also, if you're using the "LoadPlugIn()" function, there's really no reason why the filter has to be in the AVISYNTH plug-in folder. You could put it anywhere. The ones in the plug-in folder don't need "LoadPlugin()"
I reemphasize... use filters very discretely. If you have a dot problem, use undot(), but don't just add it (or any other filter) "just in case". An incorrectly applied filter might, very possibly, double or triple your encode time while making your encode actually look worse.Last edited by jdobbs; 24 Oct 2006, 09:01 PM.Comment
-
cprogram error dvdrbpro currentavs line 7 column 60
that was from preview/edit screen in dvd-rb
my script was
"C:\Program Files\AviSynth 2.5\plugins\RemoveGrainSSE3.dll")
"C:\Program Files\AviSynth 2.5\plugins\Deen.dll")
RemoveGrain(mode=2)
deen()Comment
-
Post the script completely, its reporting problem at line 7 you have posted only 4 lines, are there any blank spaces/lines below these ???Comment
-
zep73
we need the complete script with the source path and what cpu you're using...nothing more in this moment!..this is your part.
and care of this recommendation:I reemphasize... use filters very discretely. If you have a dot problem, use undot(), but don't just add it (or any other filter) "just in case". An incorrectly applied filter might, very possibly, double or triple your encode time while making your encode actually look worse.Last edited by jeo; 25 Oct 2006, 08:40 PM.still sending greens(you can't see but can feel)
geriatric rock fanComment
-
my script was
"C:\Program Files\AviSynth 2.5\plugins\RemoveGrainSSE3.dll")
"C:\Program Files\AviSynth 2.5\plugins\Deen.dll")
RemoveGrain(mode=2)
deen()
As the CHANGE LOG stated about filters: "This is an EXPERT OPTION. If you are not intimately familiar with AVISYNTH... leave it alone."
I don't mean to seem unsympathetic or harsh, but you are, very clearly, not familiar with AVISYNTH. You may want to go to this site and do some reading.
Remove all the filters, uninstall AVISYNTH, then reinstall DVD-RB using the installer (it will reinstall AVISYNTH for you). That will get you back to a good starting point where everything works.Last edited by jdobbs; 26 Oct 2006, 12:14 AM.Comment
Comment