Where is AVISYNTH log?

[windtrader]

I am trying to really understand how FACAR, AVISYNTH, and DVD2DVD operate and have two problems.

First, I can read the AVISYNTH scripts generated by FACAR and DVD2DVD but can not find any detailed logs showing how the AVISYNTH script processed the parameters. For example, I set FACAR to resizemethod=2 and 3 but can not find any log listing the internal filter being used. 2 is Bicubic and 3 is Lanczos. I can see the script with the value "resizemethod=2" but that is in the script that was built, not a process log. Is there some log showing how the AVISYNTH script is processed?

Second problem is I set debugmode=10 and do not see anything like what is described in the guide. I have set it both before and after the FACARDetectBorders step and still it will not show the screen slices. Is there a trick I am missing here?

thx

[r6d2]

Originally posted by windtrader
Is there some log showing how the AVISYNTH script is processed?Sorry, no, there is not. Nobody requested that feature before but even if someone had, I have no clue whatsoever on how to implement it :)

I understand your concern, however. In fact when first debugging Gerti's SemiAutoCropAndResize I had to build an Excel sheet to mimic the calculations.

Anyway, IMHO the only thing that really matters is what the script will look like, which is revealed in debug mode.
Second problem is I set debugmode=10 and do not see anything like what is described in the guide.Can you post a screenshot?

[windtrader]

Can you post a screenshot? The problem is there is nothing to screenshoot since the debug mode does not show any of the "framed" pictures as described. Here is the the AVS script from the DVD2SVCD log. As you see I tried debugmode=10 but not anyother combindations.

I can't image trying to debug these scripts when there is no log to show what is actually being processed. One little typo or two and you would go bald. It's like a compiler that doesn't give you any comp. errors. Ouchee.

Isn't the lack of a processing log a problem with AVISYNTH? The problem is not that your script doesn't produce a log, right?

---AVS Begin---
LoadPlugin("C:\PROGRA~1\DVD2DVD\AVISYN~1.5PL\Mpeg2dec\MPEG2D~1.DLL")
MPEG2Source("G:\DVD2DVD\DVD2AV~1.D2V")
ResizeTo=0 global ResizeMethod=3 DebugMode=10
GammaCorrection=1.0 Hue=0 Saturation=1.0 Brightness=0 Contrast=1.0
DetectedTop=6 DetectedHeight=464
OverscanH=0.00 OverscanV=0.00 BlockOptimization=0 AsoTV=1
global Bicubic_b_Value=0 global Bicubic_c_Value=0.6
DestinationWidth=720
DestinationHeight=480
DestinationTop=0
DestinationBottom=0
LoadPlugin("C:\Program Files\DVD2DVD\Avisynth2.5 Plugins\SimpleResize\SimpleResize.dll")
# Import("C:\Program Files\DVD2DVD\Avisynth2.5 Plugins\FACAR\qmf15b1.avs")
# Import("C:\Program Files\DVD2DVD\Avisynth2.5 Plugins\FACAR\QMF_functions.avs")
# Import("C:\Program Files\DVD2DVD\Avisynth2.5 Plugins\FACAR\PreResize.avs")
Import("C:\Program Files\DVD2DVD\Avisynth2.5 Plugins\FACAR\FACAR.avs")
# Import("C:\Program Files\DVD2DVD\Avisynth2.5 Plugins\FACAR\PostResize.avs")
ConvertToYUY2()
----AVS End----

[r6d2]

Originally posted by windtrader
As you see I tried debugmode=10 but not anyother combindations.You might try other combinations, and see what Debug does for you. There may be a typo in the readme.

I cannot test it myself since I have installed Fedora and cannot run Windows apps at the moment.
I can't image trying to debug these scripts when there is no log to show what is actually being processed.Debug does show what is being processed.

In fact, if you encode a short clip with debug on (Modes 1 to 3) you'll se what I mean.
Isn't the lack of a processing log a problem with AVISYNTH? The problem is not that your script doesn't produce a log, right?As I said previously, nobody ever requested that feature before. I don't know how to output a log in AVISYNTH, and I don't know if it is possible at all.

The AVISYNTH output of the script is just 3 lines:

Crop(...)
Resize(..)
Addborders(...)

In debug mode you can see the output of the script. What would you want a log for? :confused: