For those using DebugView

[bilu]

I found this nice tool:

http://www.post1.com/home/ivec/dbgproxy.html

It forwards Windows OutputDebugString to MS-DOS STDERR, which I can redirect to a file (on XP at least) using AVS2AVI and a XVID Null encode:

dbgproxy avs2avi MOVIE.AVS MOVIE.AVI -s codec.cfg 2> debug.txt

And then parse debug.txt to get what I want.


It's useful for every reason you would use DebugView, I guess, with the advantage that you can make it an automatic process.


I have already posted this on the Avisynth Usage forum as part of another subject, but I think this deserves a thread for itself.

Moderators, please move this to General Discussion if you think is appropriate. Thank you.


Best regards,
Bilu

[Prettz]

Just a quick question: after recording the output for 1 whole pass (in 2 pass mode) in debugview, is it common for the program to freeze indefinitely when you try to close it? It doesn't freeze my system or anything and the program goes away fine when I close it with the task manager. I'm guessing it would have something to do with it trying to delete every individual entry in its list box 1 by 1. I'm running windows98.

[bilu]

I'm running XP, so I don't know :confused:

Have you tried this tool? Don't know how you can deal with the STDERR handle though. :rolleyes:

Example:

dbgproxy avs2avi MOVIE.AVS MOVIE.AVI -s codec.cfg 2> debug.txt

In XP, by using 2> instead of just using > redirects STDERR instead of STDOUT. I know W2K can do it, but I'm not so sure about 98.


About DebugView: I sincerily don't know. Why don't you save the entire output and then parse outside the program instead of deleting lines before saving? This would save its resources...



Bilu