DGIndex(NV) problems?!

[an3k]

Please take a look at the image below.

http://img407.imageshack.us/img407/5975/dgindex.png

Left Information window: shows DGIndexNV indexing a 1080p VC-1 which has a duration of 2hrs 21min.

Middle Information window: shows DGIndexNV indexing a 576i MPEG2 which has a duration of 1hrs 30min 47sec

Right Information window: shows DGIndex indexing the same 576i MPEG2 which has a duration of 1hrs 30min 47sec

1) please take a look at the time the indexing process took. DGIndex was faster than DGIndexNV.
2) DGIndex doesn't show Bitrates :(
3) DGIndexNV shows all frames as Coded (correct) but also as played (not correct, no frame was shown). DGIndex shows correct information here
4) DGIndex shows Frame Type as Interlaced (correct), DGIndexNV shows I (as Interlaced? If so, correct too) but for the progessive source DGIndexNV also shows Frame Type as I(nterlaced)
5) DGIndex shows Sequence as Field/Frame while DGIndexNV shows Frame/Field. Don't know if Frame/Field and Field/Frame is the same or if its a bug.

Every process was done on the same system with the same background processes and usage of the computer. I did not demux anything, only saved the project, Display was enabled (but nothing was shown), PureVideo Deinterlacer was disabled!
GFX is a GT240. DGIndex is 1.5.7 and DGIndexNV is Build 2001.

Whats going on here? :)


EDIT: Now i forgot the main topic i wanted to write about :D
Why does indexing the MPEG2 took so long compared to indexing the VC1 which has much more data? (5GB vs 25GB).
Why is DGIndex faster than DGIndexNV, although DGIndexNV uses GPU while DGIndex doesn't?

[Guest]

1) please take a look at the time the indexing process took. DGIndex was faster than DGIndexNV. DGIndex is faster, yes.

2) DGIndex doesn't show Bitrates Not during indexing, correct. That's one reason it is faster.

3) DGIndexNV shows all frames as Coded (correct) but also as played (not correct, no frame was shown). DGIndex shows correct information here Playback # does not mean played. Playback # is coded plus any pulldown. DGIndex does not update the playback number during indexing. That is another reason why it is faster.

4) DGIndex shows Frame Type as Interlaced (correct), DGIndexNV shows I (as Interlaced? If so, correct too) but for the progessive source DGIndexNV also shows Frame Type as I(nterlaced) Frame Type in DGIndexNV means I/P/B. Frame Type in DGIndex means the chroma sampling interlaced/progressive. DGIndexNV does not have a field for that. I am considering adding it. The problem is people see interlaced and then say "DGIndexNV said my content was interlaced", which is a non-sequitor.

5) DGIndex shows Sequence as Field/Frame while DGIndexNV shows Frame/Field. Don't know if Frame/Field and Field/Frame is the same or if its a bug. They are the same.

Why does indexing the MPEG2 took so long compared to indexing the VC1 which has much more data? (5GB vs 25GB). Probably the difference between parsing elementary versus program streams.

Why is DGIndex faster than DGIndexNV, although DGIndexNV uses GPU while DGIndex doesn't? The GPU is not used during indexing. DGIndexNV makes some sacrifices in performance to allow for a clean, maintainable architecture suited for supporting all video types and containers.

[Guest]

Why does indexing the MPEG2 took so long compared to indexing the VC1 which has much more data? (5GB vs 25GB). You also have to be careful not to compare apples to oranges. If you were demuxing audio while indexing the MPEG2 program stream, and obviously weren't when demuxing the VC1 elementary stream, you'd expect a substantial time difference for writing audio files. The same applies if you were demuxing video.

I'll do some testing to see if there is anything unexpected in the times.

[an3k]

If you were demuxing audio while indexing the MPEG2 program stream, and obviously weren't when demuxing the VC1 elementary stream, you'd expect a substantial time difference for writing audio files.I know that, but
I did not demux anything, only saved the project, Display was enabled (but nothing was shown), PureVideo Deinterlacer was disabled!

:)

Thanks for all the answers and your time