Log in

View Full Version : Can Xvid save the second pass stats?


Zep
30th December 2003, 11:47
Did i miss something here? I can not find a place to
save the second pass stats what was actually encoded.
Al i see is the first pass stats and the Q's in there
are not what is being used in pass 2.

The debug -> display encoding status

that output during pass 2 is what I want to save into a file.

Is this possible?


thanks

Mr_G_123
30th December 2003, 11:51
no you cant save the second pass file because it is not being created. the whole point is to encode the first pass and to see how good can you encode the film.

Zep
30th December 2003, 12:25
but it would be nice to see exactly what xvid chose on each
frame so you could adjust your settings and zones etc...
and re do the first pass and try to get scenes via a zone
as one example to hit the Q's you want.

even so it would be nice to just see for fun :)

Leak
30th December 2003, 12:51
Originally posted by Zep
but it would be nice to see exactly what xvid chose on each
frame so you could adjust your settings and zones etc...
and re do the first pass and try to get scenes via a zone
as one example to hit the Q's you want.

even so it would be nice to just see for fun :)

I'm not sure what settings you'd need, but I guess playing around with the Debug tab in XviD's settings you should be able to have it log it's decisions so you can grab them using DebugView...

np: Process - Tread Lightly (Spectra)

Zep
30th December 2003, 15:10
Originally posted by Leak
I'm not sure what settings you'd need, but I guess playing around with the Debug tab in XviD's settings you should be able to have it log it's decisions so you can grab them using DebugView...


For example there may be
a really tuff scene Xvid is having problems on. You look at
2nd pass file and see Xvid is only giving Q=8. So now you know
why and where you stand and are not guessing that Xvid gave 12+
and you know what these scenes on this show will at least need.
So you may have to add more b-frames or make a zone for the
really tough scenes and Q=4 on those Scenes and take more
bits away from scenes that are Q=8 now but would look ok at
Q=12 etc.... (this is one thing i like about Dixv and their
extra apps. you can go back and tweak scenes)

Then there are the times when a scene looks really bad and
the file is UNDERSIZED. It would be nice to know if those frames
REALLY got Q=2 or not since i do not sit there and watch the
debug status for 6 hours :D

If the scene DID get Q=2 and was not good looking then you know
it must be a filters or a bug etc...


Originally posted by Leak

you should be able to have it log it's decisions so you can grab them using DebugView...



Yes exactly i want. as far as i can tell there is know way
you save the decisions to a log so i can use debug view or
another stats/log viewing app.

I thought that perhaps IN the debug view display window there
would be that option but i do not see it. :(

Have I missed something?

Koepi
30th December 2003, 15:41
You use debugview as it is mentioned on my xvid page? It spits out what you want to see.

regards
Koepi

Assault
30th December 2003, 16:12
Or you could simply use ffdshow for decoding and activate the on screen display. Now you can see what quantizer were used for the different scenes.

Assault

Zep
31st December 2003, 20:03
Originally posted by Koepi
You use debugview as it is mentioned on my xvid page? It spits out what you want to see.

regards
Koepi

All i have done so far is watch some of an encode here and there but I'm asleep
when most of it is encoded so... if a tuff scene appears I'm not there to watch.

I just went to your site. is that in the Xvid bin section or news?

It sounds as if I missed something important about saving the debug view
stats for later viewing?

Zep
31st December 2003, 20:04
Originally posted by Assault
Or you could simply use ffdshow for decoding and activate the on screen display. Now you can see what quantizer were used for the different scenes.

Assault

I would but I get crashes with it :)

Without it all is fine. I'm waiting for next version