Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
3rd August 2009, 05:55 | #1261 | Link |
Registered User
Join Date: Jul 2009
Posts: 45
|
NVBeta4 issue with PureVideo double rate deinterlacing:
Workaround: Use single-rate PureVideo deinterlacing. System: Vista 64 SP2 GTX280 with the 190.38 drivers VirtualDub 1.8.8/build 30091 AviSynth 2.5.7.0 (MT build) If you want a sample stream, let me know and I'll email a link to you. -Jeff |
3rd August 2009, 13:33 | #1262 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Fixed in NV beta 5:
http://neuron2.net/dgavcdecnv/NVbeta5.zip If you have previously downloaded beta 5 to get the fix for MPEG, you need to re-download it to get this fix for AVC and VC1. Last edited by Guest; 3rd August 2009 at 13:56. |
11th August 2009, 20:54 | #1266 | Link |
Registered User
Join Date: Jul 2009
Posts: 45
|
New problem with NVBeta5. DGMPGIndexNV doesn't properly recognize as interlaced, an elementary MPEG2, I-frame-only high@high, 100 Mbps CBR file. The info box shows its structure as Frame/Field. DGIndex 1.5.2 does recognize it properly as interlaced.
NV and DGIndex logs and index files attached. -Jeff |
11th August 2009, 21:01 | #1267 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
In the non-NV version "Frame Type" is the value of progressive_frame and "Coding Type" is I, P, or B frame. In the NV version, "Frame Type" is I, P, or B frame and there is no field that reports progressive_frame. I should bring them into alignment.
Frame/Field refers to the sequence: If the sequence is shown as "Frame/Field", then some frames may be coded progressively, some coded interlaced, and some pulled down. Why aren't you using beta 7? Last edited by Guest; 11th August 2009 at 21:17. |
11th August 2009, 21:18 | #1268 | Link |
Registered User
Join Date: Jul 2009
Posts: 45
|
It's not just the info window. The output isn't interlaced either, and it should be. Both the NV window and VirtualDub from AviSynth show deinterlaced frames. I wasn't clear enough in my original post. I'm sorry.
Because I didn't know there was a Beta 7? -Jeff |
11th August 2009, 21:38 | #1269 | Link | |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
The only thing I can think of is that it has soft pulldown and you don't have Honor Pulldown selected under Video/Field Operation. |
|
11th August 2009, 22:02 | #1270 | Link |
Registered User
Join Date: Jul 2009
Posts: 45
|
Here's the link to the sample stream:
Interlaced M2V File Attached is a screenshot with the export parameters from Adobe Premiere Pro, and the .ini file for DGMPGIndexNV Beta 7. -Jeff Last edited by JeffBDVS; 11th August 2009 at 22:04. Reason: Added link to download sample stream |
11th August 2009, 22:41 | #1271 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
I opened your sample in beta 7. I set Video/Display HD Full-Sized. I hit F5. The video clearly shows the combing.
I serve the video with my script into VirtualDub and play. The video clearly shows the combing. I add SeparateFields() to my script and open it in VirtualDub. I step through and can see field rate motion. Do you have all your windows set to half size? That simulates a deinterlacer. Last edited by Guest; 11th August 2009 at 22:53. |
11th August 2009, 23:21 | #1272 | Link | |
Registered User
Join Date: Jul 2009
Posts: 45
|
Quote:
Thanks for taking the time to check this out. That you cannot reproduce the issue means I've got some serious troubleshooting in my future. -Jeff EDIT: In item #1, not *all* of the subsequent frames appeared deinterlaced. I found that the very last 2 frames of the clip also showed combing. Last edited by JeffBDVS; 12th August 2009 at 00:22. Reason: New Data Point |
|
12th August 2009, 00:27 | #1273 | Link |
Registered User
Join Date: Jul 2009
Posts: 45
|
The fact that the 2 last frames in the clip showed the combing gave me an idea. My idea worked.
Workaround:
Without the workaround, all the frames show up as deinterlaced. (Except for the first one and the last two, as mentioned above.) Definitely odd. I have no idea what could cause this behavior. -Jeff |
15th August 2009, 12:39 | #1275 | Link |
Registered User
Join Date: Nov 2003
Posts: 1,281
|
Yes, decoding h.264 is cpu intensive. These tools decode h.264 using the GPU.
__________________
http://www.7-zip.org/ |
Thread Tools | Search this Thread |
Display Modes | |
|
|