Log in

View Full Version : DGIndex Field Decoding problem


Yufi
15th September 2005, 20:48
Sorry if this is actually an easy to fix problem, I wasn't sure what to search for to try and find the answer to this. I'll try and explain the problem as best I can.

I've been attempting to encode a friend's capture of Battlestar Galactica episodes from HDTV. He captured and editted the out the commercials, then deleted the source files, so I no longer have access to those, just the editted version.

The problem lies after I run the .ts files (or the .ts files converted to an mpg, doesn't matter which) through DGIndex (with Honor Pulldown Flags enabled), and then look at the .d2v using an .avs (with no filters) in VirtualDub. The first 5 or so minutes of the episode is fine, but right after the theme, there's a commercial cut, and I'm assuming this causes the problem:

Basically, the fields are out of order. It follows the 3:2 pulldown pattern, except on the 2 frames that were telecined, the fields are really weird. Using SeparateFields, this becomes easy to see. The first three progressive frames have no problem; SeparateFields shows each frame twice just like it should since the fields are separated. The fourth frame and fifth frames, or the telecined frames, have the field order mixed up. The beginning of the episode is BFF, while this part is TFF. This causes incredibly jerky movement during motion, as the fields seem to be in this pattern: 1122335454 (I think). Now, this should be easy to fix right? I just specifiy AssumeTFF for that part of the encode?

Well, it doesn't work when I do that. When I do use AssumeTFF, the pattern changes into something all messed up that I can't seem to figure out, which still has extremely jerky motion, but not nearly as jerky as before. However, it is incredibly noticable and annoying. As far as I can tell, the AssumeTFF has correctly fixed the problem with one of the telecined frames, but the other remains messed up. I really can't explain it. Unfortunately, the clip I have of this is in the neighborhood of 48mb, and I have nowhere I could upload that to for anyone to look at. The most I could do is provide a series of screenshots in order of how it looks, which I will do if requested.

If anyone can help me figure this out, I'll thank you forever.

Guest
16th September 2005, 01:48
You can upload the .ts stream to my FTP server (see sig below). Then post again telling me the filename.

Try doing Tools/Fix D2V first, though, and report the result.

Yufi
16th September 2005, 02:51
D2V Fix Output

Illegal transition: 0 -> 2
800 5 0 7639380 0 0 30 90 b0 a0 b0 a0 b0 a0 b0 a0 b0 a0
800 1 0 8525048 0 0 92 b2 b2 a2 b2 a2
corrected...
800 5 0 7639380 0 0 30 90 b0 a0 b0 a0 b0 a0 b0 a0 b0 a1
800 1 0 8525048 0 0 92 b2 b2 a2 b2 a2


It didn't fix it though.
The file name is bsg110test.ts. The first ~4.6 seconds of the video is fine (it's part of the episode intro), but everything after that (after the "Battlestar Galactica" emblem) has the problem I've mentioned. The file is 28.52mb and I'm still uploading it right now at 30k/sec.

It's really bad at about the ~11.5 second mark where the woman is drawing the triangle on the board while the camera is panning.

Guest
16th September 2005, 03:24
After you do Fix D2V, you have to use the resulting file movie.d2v.fixed by renaming it. Did you do this?

1. Run Fix D2V on bsg110test.d2v.
2. Rename bsg110test.d2v to bsg110test.d2v.bad
3. Rename bsg110test.d2v.fixed to bsg110test.d2v.
4. Use bsg110test.d2v in your script.

I decoded it with DGMPGDec 1.4.4 beta 4 and after fixing the D2V I don't see any problem.

Perhaps the Fix D2V function should generate the fixed filename as bsg110test.d2v and save the old one as bsg110test.d2v.bad. I think I'll change that.

Yufi
16th September 2005, 04:34
After you do Fix D2V, you have to use the resulting file movie.d2v.fixed by renaming it. Did you do this?

1. Run Fix D2V on bsg110test.d2v.
2. Rename bsg110test.d2v to bsg110test.d2v.bad
3. Rename bsg110test.d2v.fixed to bsg110test.d2v.
4. Use bsg110test.d2v in your script.

I decoded it with DGMPGDec 1.4.4 beta 4 and after fixing the D2V I don't see any problem.

Perhaps the Fix D2V function should generate the fixed filename as bsg110test.d2v and save the old one as bsg110test.d2v.bad. I think I'll change that.

Duh, I'm stupid, I can't believe I overlooked that. Sorry! I knew it would be some sort of simple fix.

Cyberia
16th September 2005, 05:20
I know this is out there, but you could also edit your script to look at the new d2v file.

Yea, I know. Way Crazy.

Guest
16th September 2005, 13:39
I'm going to make Fix D2V automatic and have it do the renaming as above. If it worked that way, we'd have never heard from Yufi. :)

Guest
17th September 2005, 13:35
@Yufi

Version 1.4.4 RC1 now fixes this automatically.